Order Management
Overview
After a merchant connects one of your locations to Stream, they will be able to receive orders from Stream into your POS system via the Handle Order (Stream -> POS) endpoint.
As we process an order, there are multiple actions that may take place before the final fulfillment of the order.
Order Fulfillment Types
There are multiple types of fulfillment that can be submitted through Stream:
delivery: An order that is being delivered to a customermerchant_managed_delivery: An order that is being delivered to a customer by a merchant's employee/dispatch systempickup: An order that is being picked up by a customercurbside: An order that is being picked up by a customer at a curbside locationdrive_thru: An order that is being picked up at a drive thru windowdine_in: An order that is being taken at a dine in location
Order Source and Brand
Every order carries two fields that say where it came from:
source: the ordering platform, such asgrubhub,uberor a partner's slug.brand: the channel within that platform, such asseamlesson a Grubhub order,postmateson an Uber order, orcateringorkioskfrom a platform that sends separate channels.brandcan be missing; treat a missingbrandas equal tosource.
Use brand to give merchants separate visibility of each channel in your POS. For example, map it to a revenue center, order channel, payment type or reporting tag, so that catering or kiosk orders don't mix with the platform's other orders. Match on source when you want one mapping for everything from a platform.
Treating brand as a fixed list rejects or misroutes orders. The values listed in the API spec are examples, and a DSP can send any string. Fall back to source when brand is missing or you don't recognise it.
Order Flow Overview

The typical order flow includes:
- Order Reception: Stream receives order from DSP
- Validation: Order is validated against catalog and business rules
- Acceptance: POS accepts or rejects the order (see Order Acceptance)
- Status Updates: Order status is updated throughout fulfillment (see Stream Order Status Updates)
- Completion: Order is marked as completed or canceled
Related Topics
- Order Acceptance - How orders are accepted and validated
- Order Rejection & Validation - Rejecting orders with validation types and error handling
- Async Order Acceptance - Manual review and deferred acceptance
- Stream Order Status Updates - Stream order updates to the POS
- Order Cancelation - Handling order cancelations
- Order Adjustments - Removing, reducing, or substituting items on an in-progress order
- Order Pricing - Understanding order amounts
- In Store Orders - Understanding in-store order processing
- Example Order Events - Sample order JSON payloads for various scenarios