fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
      • Facility discounts
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Summary
  • Use case example
  • Configure multi order picking
  • 1. Configure the picking method for a warehouse facility
  • 2. Configure the maximum of tasks for multi order pick
  • 3. Create load unit types
  • 4. Create storage locations
  • How to fulfill a task in multi order pick
  • 1. Create a multi order pick run with the REST API
  • 2. Start the pick run with the REST API
  • 3. Patch load unit line items to load units with the REST API
  • 5. Create and store load units on the configured storage location with the REST API
  • 4. Finish the pick run
Edit on GitHub
  1. Use Cases

Multi order picking

Last updated 5 months ago

Summary

Multi order picking is a picking method where a picker simultaneously collects items for multiple tasks in a single run through e.g., the warehouse. This method increases efficiency by reducing the distance covered, as opposed to picking items for one task at a time.

Use case example

A company has established the following requirements for its operational picking process:

  1. Multi order picking is to be implemented exclusively for one designated facility, in this case a warehouse, while single order picking is to be utilized for all other facilities.

  2. No more than five tasks may be picked simultaneously to ensure efficiency and manageability.

  3. Picking operations are conducted using, with a total of five distinct load unit types available.

  4. Upon completion of picking, the load units are transferred to a designated station. The packing process begins from this location.

Configure multi order picking

1. Configure the picking method for a warehouse facility

Picking method MULTI_ORDER must be set in the designated facility with the , in this case the warehouse. The default SINGLE_ORDER applies in all other facilities, which is set in the .

2. Configure the maximum of tasks for multi order pick

The must be set to the following:

    "multiOrderPickingConfiguration": {
        "maxAmountOfPickJobsForMultiOrderPick": 5
    },

3. Create load unit types

4. Create storage locations


How to fulfill a task in multi order pick

When everything is configured, you are ready to fulfill your tasks with multi order picking.

  1. Create a multi order pick

  2. Start the pick run

  3. Add items to load units

  4. Store load units on the configured storage location

  5. Finish the pick run

4. Finish the pick run

OperativeContainerTypes must be created and defined in which fulfillment process step, so called allowedOperativeTypes are required. This happens with the .

This is the , where you store your load units at the end of the picking process. It can be created with the .

1. Create a

2. Start the

3. Patch

5. Create and

The pick run result can be finished by using the PickrunFinishActionParameter with the . After all that, you have successfully picked multiple tasks with the multi order pick method.

load units
packing
facility REST API
picking configuration
picking configurations REST API
operative container type REST API
storage location
storage location REST API
multi order pick run with the REST API
pick run with the REST API
load unit line items to load units with the REST API
store load units on the configured storage location with the REST API
actions REST API of the pick run