# Picking {% hint style="info" %} This version is currently available as a [Beta release](/documentation/apps/mobile-app-availability.md) via the Google Play Store. To access it, you need to be enrolled in our beta program. If you'd like to participate, [contact us using our Support portal](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/11/create/39) to request access. {% endhint %} Picking starts when a pick job is selected from the order list. Depending on the configured picking method, the job either starts immediately or allows additional pick jobs to be added to a pick run before starting. {% hint style="info" %} For general information about picking and pick jobs, refer to the [picking documentation](/documentation/by-pillar/store-operations/picking.md). {% endhint %} ## Picking flow Depending on the configuration, a preparation screen may be shown before picking begins. This screen provides an overview of the number of items to pick and displays the recommended number of containers.

After the preparation step, the list of items to be picked is displayed. Items are organized in **Open** and **Done** tabs.

For batch picking, the item list is shared across all included orders. If the same article exists in multiple orders, the quantities are aggregated and displayed as a single line with the summed quantity. For multi-order picking, this aggregation doesn't occur. The items are listed separately. Items can be picked by scanning or by manually entering the picked quantity. As items are picked, they move from the **Open** tab to the **Done** tab. Items can be removed from the **Done** tab to be picked again. Once all available items are picked, the pick job can be completed using the slide-to-finish action. After completion, a summary screen is shown. The summary displays the successfully picked items, pickup information, prepared containers, selected substitute items, and available next actions.

For both multi-order and batch picking, the summary screen displays separate tabs for each order included in the pick run.

## Picking with containers and locations ### Containers Containers are used to collect items during the picking process and are referred to as load units. For more information, see the [operative container types article](/documentation/by-pillar/store-operations/packing/operative-container-types.md). When containers are enabled, picked items must be assigned to a container. An assignment can be performed by scanning a container or manually entering a container ID. Container usage is mandatory in multi-order picking. Each picked item must be assigned to a container. This enforces physical and system-based separation per order during the picking process. The user is guided through the process and can identify the correct container, as the Store Operations App recommends only containers that belong to the same pick job. Using a container from another pick job results in an error, indicating that the item can't be assigned to that container. A container that's already associated with another order can't be reused.

If more than one operative container type is available for picking, a container type must be selected. The container type defines the kind of container, such as a box or a bag.

Items assigned to a container can be modified by removing them from the **Done** tab and assigning them again. Items can be assigned to the same container or to a new container. When creating a new container, if multiple types are available, the container type must be selected again.

### Locations The use of locations depends on the configuration and is only available in combination with containers. It can be disabled, optional, or required. When enabled, containers can be assigned by scanning or by manual entry. Multiple containers can be assigned to the same location. Containers can be reassigned. During assignment, progress information is displayed to indicate which containers are already assigned and which are still missing a location.

After all required assignments are completed, selecting **Done** leads to the end-of-pick summary screen.

## Special cases ### Item not available The **Item not available** option is available for each item in the pick list. Selecting it indicates that the item can't be picked at its expected location. A selected substitute item is treated as a short-pick.

#### Storage location check Storage locations define where an item is physically stored and are displayed on the item card so that the picker knows where to go. An item can be available in one or multiple storage locations (see [inventory](/documentation/by-pillar/global-inventory-hub/storage-locations-and-zones.md)). When **Item not available** is selected, the app checks for alternatives. If one is available, the user is redirected to it and can attempt to pick from there. If no alternative is available, the item is recorded as a short-pick. The flow then continues to check if substitute items are configured and available.

#### Substitute item check If substitute items are configured, a selection screen is displayed when **Item not available** is selected. The screen lists available substitutes with product details. The user selects a substitute and sets the quantity. After confirmation, the substitute item is added to the pick list and marked with an icon to identify it as a substitute. The substitute item must be picked separately and may appear later in the picking sequence, depending on its location.

### **Short-pick** A short-pick occurs when the requested quantity of an item can't be fully met, including partially picked items and items for which a substitute was selected. The **FINISH** button is available at any point during the picking process. If short-pick reasons are configured, a screen is displayed after **FINISH** that lists all items that were not fully picked, including those for which a substitute was selected. #### **Reasons** Short-pick reasons allow operators to capture why an item wasn't fully picked. If short-pick reasons are configured, a bottom sheet is displayed with all predefined reasons (see [picking configuration](/documentation/by-pillar/store-operations/picking.md)).

There are two configurations available via remote config to control whether the reason needs to be captured as optional or mandatory (see [remote configuration](/documentation/by-pillar/store-operations/remote-configuration.md)). When set to optional, the confirmation button is active regardless of whether a reason was selected. When set to mandatory, the confirmation button becomes active only after a reason has been selected for each item. #### **Zero pick** Zero pick is a special case of a short-pick in which no items are picked. When **FINISH** is selected without any picked items, a confirmation dialog is displayed to alert the user. After confirmation, short-pick reasons are requested if configured.

### **Reroute** A reroute is triggered after a short-pick to check whether another facility can fulfill the end customer's order. The check is performed only if the reroute configuration is active and, if configured, after the reasons screen. If a reroute is triggered, the user is presented with a list of items that must be put back. The confirmation button becomes active only after the user confirms via a toggle that the items have been placed back. If no reroute is configured, the flow continues to the next step without interruption.

### **Recordable attributes** Recordable attributes are item-level attributes that can be captured during the picking process, such as serial numbers, best-before dates, or country of origin. If at least one item in the pick job has recordable attributes defined, a dedicated screen is displayed after the short-pick reasons screen and before reroute.

Attributes can be entered manually via the keyboard or captured via OCR, in which the app recognizes text through the camera, and the user selects the correct value. After all required attributes have been entered, the pick job can be completed.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fulfillmenttools.com/documentation/apps/store-operations-app-beta/beta-picking-android-app.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.