Multi Order Picking
Last updated
Was this helpful?
Last updated
Was this helpful?
Multi order picking is a picking method where a picker simultaneously collects items for multiple tasks in a single pass through e.g. the warehouse. This method increases efficiency by reducing the travel time and distance covered, as opposed to picking items for one task at a time. Multi order picking is often optimized using advanced software systems that group orders in a way that minimizes picking paths and improves overall productivity.
The company has established the following requirements for its operational picking process:
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 facilites.
No more than five tasks may be picked simultaneously to ensure efficiency and manageability.
Picking operations are conducted using load units, with a total of five distinct load unit types available.
Upon completion of picking, the load units are transferred to a designated packing station. The packing process begins from this location.
PickingMethod MULTI_ORDER must be set in the designated facility, in this case the warehouse. The default SINGLE_ORDER applies in all other facilities, which is set in the picking configurations.
OperativeContainerTypes must be created and defined in which fulfillment process step, so called allowedOperativeTypes are required.
This is the location, where you store your load units at the end of the picking process.
When everything is configured, you are ready to fulfill your tasks with multi order picking.
Create a multi order pick
Start the pickrun
Add items to load units
Store load units at your storage location
Finish pickrun
The pickrun result can be finished by using the PickrunFinishActionParameter
After all that, you have successfully picked multiple tasks with the multi order pick method.
Provides Localized values. The key is the locale, the value is the translation. See https://docs.fulfillmenttools.com/api-docs/connecting-to-fulfillmenttools/restful-api/general-topics/localization#fallback-language-mechanism
{"de_DE":"Wert","en_US":"Value","ru_RU":"значение"}Provides Localized values. The key is the locale, the value is the translation. See https://docs.fulfillmenttools.com/api-docs/connecting-to-fulfillmenttools/restful-api/general-topics/localization#fallback-language-mechanism
{"de_DE":"Wert","en_US":"Value","ru_RU":"значение"}This value gives the priority of the respective operativeContainerType. The lower the value the higher is the priority, e.g. priority 1 is higher than priority 10. The priority can be used to order packingContainerTypes in the UI.
100Maximal weight in gramm(gr) the container can be loaded with.
2500Attributes that can be added to the operativeContainerType. These attributes cannot be used within fulfillment processes, but it could be useful to have the informations carried here.
The state of the PickRun
OPEN, IN_PROGRESS, CLOSED, CANCELED, OBSOLETEDeprecated: batchPick, use batch instead Deprecated: multiOrderPick, use multiOrder instead
multiOrderPick, multiOrder, batchPick, batchReference to the pick run you want to call the action for
Action to start a PickRun.
Action to finish a PickRun.
Action to cancel a PickRun.
Action to Remove a Pickjob from a PickRun.
Provide the localized names and descriptions for the routing configuration. If not provided the default locale is used., for example de_DE
Actions to patch a LoadUnit.
LoadUnit.
ID of facility you want to patch
The version of the document to be used in optimistic locking mechanisms.
42Who do the load units need to be assigned in pickJob (SingleOrderPick) and pickRun (MultiOrderPick)
Can this tenant use the backoffice for picking?
Creates a new storage location in this facility.
ID of facility from whom you want to create the storage location
The name of this storage location
The internal tenant id for this location
Describes the kind of a storage location:
SINGLE_STORAGE- it is only allowed to store stock with the same tenantArticleId hereBULK_STORAGE- stocks belonging to different tenantArticleIds can be stored hereSINGLE_STORAGE, BULK_STORAGEThe traits of this storage location, includes both local config and and defaults. Do not use to write to traits, use traitConfig instead.
The configuration of the traits of this storage location
Barcodes representing this storage location
The Sequence item/s of this location
The id of the Zone to which this storage location belongs
Esb20gpHBL94X5NdMp3CThe name of the Zone to which this storage location belongs
A free text information about this storage location, max length 1024
Attributes that can be added to the storage location. These attributes cannot be used within fulfillment processes, but it could be useful to have the informations carried here.