Multi Order Picking
Last updated
Last updated
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 pick run
Add items to load units
Store load units at your storage location
Finish pick run
The pick run result can be finished by using the PickrunFinishActionParameter
After all that, you have successfully picked multiple tasks with the multi order pick method.
der Endpunkt hier ist deprecated. Was ist denn der Richtige?
The found load unit.
The date this entity was created at the platform. This value is generated by the service.
"2020-02-03T08:45:51.525Z"
The date this entity was modified last. This value is generated by the service.
"2020-02-03T09:45:51.525Z"
The version of the document to be used in optimistic locking mechanisms.
42
Attributes that can be added to the LoadUnit. These attributes cannot be used within fulfillment processes, but it could be useful to have the informations carried here.
the reference to the storage location this load unit as been placed into
the reference to the operativeContainerType
the reference to the stackRef this loadUnit is part of