Start picking process for order

Summary

Allows partners to inform Deliveroo's internal systems that the picking process of an order has started.

Usage scenario

Site would like to indicate that the picking process for an order has been started.

Business constraints

  • Order has to be in the PLACED status.

Optional batch picking signal

The optional batch_context body lets partners flag whether the order is being picked as part of a batch. This is an analytics signal only — it is not consumed for operational decisions. Batch context is persisted and echoed back on prep-state responses on a best-effort basis; when persistence is not yet enabled for an order's site, the value is still validated but may not appear on subsequent GET /prep-state calls.

Operational constraints

  • There's a rate limit of 2 request per order per second. If you get over the limit, you'll get "Too many requests" error.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Related order id in format {market}:{order_uuid}.

Body Params

Optional. Sending an empty body or no body keeps the existing behaviour.

Optional body for PUT /picking/v1/orders/{order_id}/start_picking. Send an empty body or no body to start picking without batch metadata.

batch_context
object

Optional. Flags whether the order is being picked as part of a batch. Analytics signal only — not consumed for operational decisions.

Responses

Language
Credentials
OAuth2
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json