# Create automatic WMS pick batches
URL: https://support.starshipit.com/articles/14700000000095-create-automatic-wms-pick-batches
Canonical: https://support.starshipit.com/articles/14700000000095-create-automatic-wms-pick-batches
Markdown: https://support.starshipit.com/articles/14700000000095-create-automatic-wms-pick-batches.md
Updated: 2026-11-08

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Configure an automatic batch recipe, choose order filters and timing, then test the batches created during its operating window.

Create pick batches automatically from eligible Pending orders during a daily operating window. Choose the filters, target size and maximum wait that match your warehouse run.

## Before you begin

You need settings-view and fulfilment-management access, importing WMS orders and a recognised account timezone. Eligible orders need full allocatable stock and no active hold.

## Create the batch automation

1. Go to **System > Automations** and select **New automation**.
2. Select **Create automatic batches** and enter a clear name.
3. Configure the settings below.
4. Leave **Enable after saving** off while reviewing the configuration.
5. Select **Save automation**.

## Choose filters and timing

Use this recipe to build pick batches from fully allocatable pending orders during a defined daily window.

| Setting | How it works |
|---|---|
| **Batch name prefix** | Optional text added to generated batch names so teams can recognise the workflow that created them |
| **Carrier** | Optional exact match against the carrier code or display name |
| **Service code** | Optional exact match against the carrier service code |
| **Order tags (optional)** | Separate tags with commas. Prefix a tag with `!` to exclude it. Orders must match any included tag and none of the excluded tags |
| **Order number condition** and **Order number prefix** | Choose **Starts with** or **Does not start with** to filter by the entered prefix. Matching ignores letter case and treats the prefix as literal text; orders without an order number are excluded when this filter is set |
| **Minimum total quantity (optional)** and **Maximum total quantity (optional)** | Inclusive limits on the sum of item quantities per order; enter whole numbers from 1 to 1,000,000, or leave either limit blank |
| **Target batch size** | Creates full batches when this many eligible orders are ready; enter 2 to 100 |
| **Maximum wait (minutes)** | Creates a smaller batch after the collection window has run for this long; enter 1 to 1,440 |
| **Window starts** and **Window ends** | Defines the daily period when WMS can create batches; both times must be on the same day |
| **Timezone** | Uses the timezone from your Starshipit account when you create the recipe |

![The automatic batch recipe editor showing order filters, target batch size, maximum wait and daily operating window](/uploads/articles/starshipit-wms/web/outbound-fulfilment/automation-recipe.jpg)

Filled filters are combined, so an order must match every filter you enter. Carrier, service code and order tag filters use exact, case-insensitive matching. For example, `!Express,!Personalisation` excludes either tag, while `priority,vip,!Express` requires `priority` or `vip` and excludes `Express`. Quantity limits apply to each order, not to the total batch. For example, set both limits to `1` to batch single-unit orders.

During the operating window, WMS checks the recipe about once a minute. It creates full batches as soon as the target size is available. If fewer orders are ready, the collection window starts when the automation first finds eligible orders. It creates a smaller batch when that window reaches the maximum wait. An older order does not skip the collection window simply because it was imported earlier.

Only pending orders without an active hold are considered. Each order must have enough stock for full allocation. Held, unallocatable, and non-matching orders remain pending for a later check.

## Test and verify

1. Limit the first run to a unique test order tag and a small target batch.
2. Create eligible test orders with that tag and enough pick-face stock.
3. Enable the recipe during its operating window.
4. Check **Latest run** and the linked batch, including orders and allocations.
5. Pause the recipe before removing the test restriction or widening its filters.

If no batch appears, check the operating window, complete filter matches, available stock, target size and maximum wait. A scheduled check still waiting for enough orders may leave Latest run unchanged. [Review shared automation history, pause behaviour and troubleshooting](/articles/14700000000039-automate-warehouse-work-in-wms) before retrying or changing the recipe.

## Related articles

* [Automate warehouse work in WMS](/articles/14700000000039-automate-warehouse-work-in-wms)
* [Pick orders in WMS](/articles/14700000000011-pick-orders-in-wms)
* [Manage orders and allocation in WMS](/articles/14700000000010-manage-orders-and-allocation-in-wms)