Process picks asynchronously
Queue goods out orders for asynchronous pick list generation. This is the preferred method for processing orders as it runs in the background without blocking. Each order gets its own pick list unless using the consolidation endpoint.
Request Structure
Key Fields
| Field | Required | Description |
|---|---|---|
ids | Yes | Array of goods out order IDs to process |
Prerequisites
- Orders must be in PENDING or ALLOCATED status
- Account/warehouse permissions must allow pick processing
Behavior
- Returns process_references for tracking pick list generation
- Each order gets its own pick list (use
/process_and_consolidate_picksto merge) - Orders are grouped by warehouse
- Crossdock orders are processed separately from sales orders
- Pick type can be
standard(traditional picking) ortote(container-based batch picking)
Tracking Status
Poll for completion via GraphQL:pending, completed, failed
Error Codes
| Code | Symbol | Description |
|---|---|---|
| 36 | empty_ids_provided | No order IDs provided |
| 37 | invalid_ids_provided | Some IDs do not exist |
| 39 | not_enough_stocks_for_picking | Insufficient stock available |
| 59 | goods_out_already_allocated | Order already processed |
Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Body
Request body for asynchronous pick processing
Array of goods out order IDs to process
1Response
Pick processing queued successfully
Response containing process references for tracking pick processing status
Array of process reference strings for tracking the queued pick processing jobs via GraphQL

