Picking Configuration
Last updated
Last updated
The picking configuration allows users to give more details on the process of picking orders and define rules. The picking configuration affects the whole system regardless of the user role or the facility.
Please go to the for more information on the picking configuration. The API documentation can be found here.
The picking scan code validation configuration determines whether the pick of an item is possible only by scanning a barcode (valid barcodes must be supplied in the field scannableCodes in the pickLineItem of a pick job) or whether it should be allowed to also scan other barcodes that are not known. The latter might speed up the process, but also theoretically allows for process errors.
Available options includeCODE_MUST_BE_KNOWN or NO_VALIDATION.
CODE_MUST_BE_KNOWN: Only the scan of a code that exists inside the scannableCodes array of the pick line item increases the pick count
NO_VALIDATION: The scan of any barcode will increase the count of the currently in the app selected pick line item
Setting this config to CODE_MUST_BE_KNOWN and having a pick line item without any code inside its scannableCodes array will result in not being able to increase the count of the item via barcode.
The scanning configuration defines scanning rules, scanning types and roles that are are allowed to overwrite the scanning rules.
This rule determines whether the pick line item, its storage location or both must be scanned. Also it states the order of the scans (storage location or item first).
Please note that if both item and storage location have to be scanned, the location has to be scanned only once per item independently from the priority.
This field can be set to one of the following values: MUST_SCAN_EACH, MUST_SCAN_FIRST, SCAN_NOT_REQUIRED.
MUST_SCAN_EACH: To increase the pick count of an item, the scan order determined in the scanning rule must be followed (except for the case, when ARTICLE as well as LOCATION are allowed) in order to increase the pick count.
MUST_SCAN_FIRST: To increase the pick count of an item, the scan order determined in the scanning rule must be followed only once. This "unlocks" the pick line and further items can be added without undergoing a scanning procedure - the count can be increased manually.
SCAN_NOT_REQUIRED: Increasing the pick count of an item can either be done by following the scan order determined in the scanning rule or manually.
rolesWithOverwritingScanningPermission: Contains the roles of users to whom the scanningRule and scanningType do not apply or in other words, they will be able to increase pick counts without adhering to the set rules. Roles can be:ADMINISTRATOR, SUPERVISOR or FULFILLER.
This configuration enables or disables the possibility of taking over tasks of other users.
Each task has a user field which is set by the last user that has edited the task. Editing means the increase of the object version (this happens, for example, when entering, leaving or finishing a task). The user is determined by the login credentials.
The selection of load units in the picking process can be set to before or after the actual picking or set to be disabled separately for each picking method like single pick (pickJob) or multi/batch pick (pickRun).
AT_START: The load unit assignment screen will be shown before the actual picking.
AT_END: The load unit assignment screen will be shown after the actual picking.
INACTIVE: The load unit assignment screen will not be shown at all.
DURING_PICKING: Currently not supported in our clients. This status will be handled the same as INACTIVE
This sets the default picking method tenant-wide. The field defaultPickingMethod can be: SINGLE_ORDER, MULTI_ORDER or BATCH.
The default picking method determines the preferred picking method of a single task, when there are no other settings (tags or facility-wide preferred picking method).
The configuration determines whether employees can confirm via a three-dot menu in the app if the stock level of an item was reduced to 0 during picking.
The configuration determines whether restarting a task in the Backoffice should be possible.