Picking
Last updated
Last updated
A pick job is the main entity in the picking process. It contains all information that is important in order to carry out a picking task. A pick job is created automatically but can also be created via API. One of the cases when a pick job is created automatically is the outcome of an order routing decision. In that case an order was created, assigned to a facility, and a pick job was created. Furthermore, a pick job can be created due to a re-route, which also involves order routing.
The following picking methods are available:
Single Order Picking
If a picking task cannot be completed picked because some of the required items are unavailable, it is referred to as a .
Please go to the for more information on creating pick jobs and defining picking methods, short-pick reasons, scanning rules and more via API. Go to the section for more guidance on using pick jobs in our apps.
The defaultPickingMethod of the tenant can be set to one of the following values: SINGLE_ORDER, MULTI_ORDER or BATCH (see Configurations of Picking Methods for details). This configuration is considered a fallback configuration: It will only be used for new pick jobs if there is no facility configuration for picking methods in the target facility and no pick job specific configuration.
If the picking method should be different for each facility, it can be configured when creating or updating a . ThepickingMethods in the facility can be set to none, some or all of the following values: SINGLE_ORDER, MULTI_ORDER or BATCH. This configuration overwrites a potentially present tenant wide configuration.
The picking method can also be defined for an individual pick job. It is defined in the pick job itself (field preferredPickingMethods). The value is the outcome of the configurations on tenant and/or facility level and may be overwritten during creation of the pick job. Providing pickingMethods in the creation of a pick job overwrites any given facility specific or tenant wide configuration.
It is also possible to add picking methods according to tags in the pick job. This can be done via API. The corresponding tags must exist in order to apply the preferredPickingMethods in the configuration.
Batch picking is one of the available multi order pick methods of fulfillmenttools. In batch picking, a pick run is used to execute multiple pick jobs in one run. When two pick jobs of a batch pick run contain the same item, the two items are merged to one pick line item for the picker.
Example: Pick job A contains the item "apple" with a quantity of 3. Pick job B contains the item "apple" with a quantity of 5. A batch pick run of these two pick jobs would combine both pick jobs and results in three pick line items in the pick run.
After the picking process is finished, the picked items are separated by order and can be shipped or handed over to the customer.
Multi order picking is another available methods at fulfillmenttools to pick multiple orders in one run. The multi order fulfillment process involves consolidating multiple customer picking tasks into one pick run for efficient picking. Workers collect items for all tasks simultaneously and transfer them to a packing station, where packers organize, pack, label, and prepare the tasks for shipment.
A detailed description of multi order picking can be found in the use case section.
Substitute items are items that can be picked if the originally ordered items are not available. A list of potential substitute items can be defined for each product on network level via API. If an item could not be picked successfully, and the configuration is active, users have the option to choose one (or more) substitute item(s).
Substitute items are connected via matching tenant article ID with the originally requested item. They can be prioritized so that a more suitable candidate is offered to the user before less suitable ones are shown. If a corresponding listing exists for a substitute item, the stock of that listing is adjusted as soon as the task reaches end of picking.
Substitute items do not necessarily require an existing listing. As a result, unlisted products can also be picked as substitute items.
Picking substitute items is currently only available within the Operations Android App for single order picking.
With every order it is possible to provide information about items which must be weighed or measured during the picking process (for example fruits, liquids or fabric). It is possible to configure individual measurement units for each tenant, such as grams, kilograms, liters, milliliters etc. via API.
Optionally, it is possible to specify tolerance limits that must not be exceeded or undershot when picking these items. If a soft tolerance is defined, the picker just sees a hint, when entering more or less than configured. If a hard tolerance limit is configured it is not possible to enter more or less (except of 0) than configured.
In addition to a quantity of a line item, an order can also contain a second quantity and unit of this item, which leads the picker to enter a second quantity. This only works, if one of the two units were created as measurement units.
If you are interested in using this feature please get in touch with us.
A short-pick describes a case when an order could not be completely picked. This can happen when some ordered items were too low in stock or out-of-stock. Several configurations can be made for the case when a short-pick happens:
Confirm short-pick in Operations App
Short-pick reasons provide clarity on why specific picking tasks could not be fulfilled entirely. They can be added to the line items of each picking task.
Before using short-pick reasons during the picking process they must be configured via API. The reasons are constructed using a multi-language JSON format and are translated accordingly. Short-pick reasons will be translated into the required language. The language is determined either by the requested locale or the user's default locale. If neither is specified, the translation will default to the first available localized reason, or if unavailable, it will default to the localization for "en_US".
If a picking task is restarted or reseted, the short-pick reasons on the pick line items will be deleted.
Zone picking can be useful if certain workers in the facility are only to pick tasks in their assigned zones. Each user can carry at least one zone. After a zone was created, it can be assigned to any available user. For a user to be able to pick products from a specific zone, those products need to be linked to that zone. This linkage is achieved by using storage locations that have an associated zone. Consequently, products located on these storage locations will be automatically assigned to the respective zone.
Upon the zone's creation and its assignment to both a user and storage locations, it becomes feasible to generate picking tasks that can be executed by users assigned to that particular zone.
The picking task gets automatically assigned to a zone immediately after a product is allocated to a storage location within that zone.
Example:
Zones A, B and C are available in the facility
Picker is assigned to zone A and B.
Pick job with Zone A and B => picking task is pickable
Pick job with zone A, B and C => picking task is pickable
Pick job with zone C => picking task is not pickable
Pick job with zone B and C => picking task is pickable
When user do not have any zones assigned, they see every picking task.
If a user is NOT assigned to a zone, she will not receive notifications for pick jobs in that zone.
The configuration for (dis)allowing picking of substitute items can be made in the in the Backoffice.
The configured measurement units can be used to mark items of an order as “must be measured”. There is no check of completion for measuring items, which means that no will be triggered when the picked measurement is lower than the ordered measurement.