Orders Manager (POS, BI & Reports)
Endpoints for applications that act on the merchant/store side of an order rather than as the ordering marketplace — typically Point-of-Sale (POS) systems, Business Intelligence (BI) tools, and reporting integrations.
This domain lets a merchant-side application retrieve a store's orders and manage them on the store's behalf as they progress through their lifecycle.
Notify the result of a Create Order event
Callback used by a merchant-side integration to acknowledge the result of an order-creation webhook it received. Send the `X-Event-Id` of the original webhook event so the platform can correlate the acknowledgement with the order it created.
Fetch order feed for a store
Returns a paginated feed of the store's orders, most useful for POS, BI, and reporting integrations that periodically poll for new and updated orders.
Fetch order with Manager Info
Returns the full detail of a single order for the given `source` (the ordering marketplace the order came from, e.g. `ubereats`), enriched with merchant-side information: the current POS `injectionState`, the `injectionEvent` that triggered it, any `orderIssues`, and cancellation details when applicable.
Request order confirmation
Confirms (accepts) the order for the given `source` on behalf of the store — the typical action a POS takes when the merchant accepts an incoming order. Optionally include `estimatedPrepTimeMinutes` to communicate how long the order will take to prepare. Processed asynchronously; returns `202 Accepted`.
Request order cancelation
Cancels (rejects) the order for the given `source` on behalf of the store. A `cancellationReason` is required; optionally include the `cancelingParty` to record who initiated the cancellation. Processed asynchronously; returns `202 Accepted`.
Mark an order as ready to pickup
Signals that the store has finished preparing the order for the given `source` and it is ready for the courier or customer to collect. Marks all of the order's station tickets as prepared. Processed asynchronously; returns `202 Accepted`.
Create a packaging component
Creates a packaging component (a packaging ticket) for the order of the given `source`, used by kitchen/station workflows to print or track packaging for the order. Returns the identifiers of the created order component.
Mark an order as fulfilled
Marks the order for the given `source` as handed off / fulfilled — the final operational step, once the order has been given to the courier or customer. Processed asynchronously; returns `202 Accepted`.
Mark a dine-in (open-tab) order as closed
Marks an open-tab dine-in order as closed. The closing party is always the merchant/POS (system). `RATE LIMIT: 32 per minute`
Update order customer items
Updates customer items for a dine-in order (quantity change, price adjustment, or add item). Only supported when integration slug is d2c-eater-website, order fulfillment type is dine-in, and the order tab is open (order is modifiable). Modifying party and modification request ID are set by the endpoint. `RATE LIMIT: 8 per minute`
Update order prep time
Updates the estimated preparation time (in minutes) for the order of the given `source`, e.g. when the kitchen revises its estimate after the order was confirmed. Unlike the other manager endpoints, this one uses the `orders.update` scope. Processed asynchronously; returns `202 Accepted`.