> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/apps/operations-app/picking/batch-and-multi-order-picking.md). # Batch and multi-order picking {% hint style="info" %} The Operations app has been replaced by the [Store Operations app](/documentation/apps/store-operations-app.md). See the [picking article](/documentation/apps/store-operations-app/beta-picking-android-app.md) for the new process. {% endhint %} ## Batch picking Tasks eligible for batch picking have a checkbox. All selected tasks are included in one pick run. Selecting the **TASKS SELECTED** button includes all selected tasks in the pick run and opens the picking interface. All subsequent steps are identical to the [single-order picking process](/documentation/apps/operations-app/picking.md).

## Multi-order picking Tasks eligible for multi-order picking have a checkbox. All selected tasks are included in a pick run. Tapping the **START PICKRUN** button proceeds to the next step.

Before picking begins, the system presents a preview, including the load units that may be required. The application suggests a number of load units to assist with planning the pick run.

The picking process begins, and the picking list is displayed. Each picking task (one per customer) is assigned at least one load unit, ensuring that by the end of the process, all items are organized by picking task, thus eliminating the need for an additional packing step. Before the assignment, the load unit is shown as N/A in the line item.

Once assigned, the ID of the load unit is partially displayed.

### Assigning load units by scan When a user picks the first item, the system prompts for a new load unit to be scanned or assigned manually. ### Assigning load units manually Tapping **Manually assign load unit** opens an input field for the load unit ID.

The user can enter a load unit ID that is 4 characters long.

If load unit types are defined, the system also prompts the user to provide this information.

Once this step is complete, the item is assigned to the load unit, and the process continues in the same way as the load unit scan process.

### Recommended load unit When picking an item for a task (customer) that already has an assigned load unit, the system recommends that specific load unit for scanning or manual assignment. If the recommended load unit is not suitable or is full, the user can scan a different, new load unit to assign the item automatically. This new load unit then becomes the recommended one for any subsequent items in that same picking task (customer).

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.fulfillmenttools.com/documentation/apps/operations-app/picking/batch-and-multi-order-picking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.