Skip to main content
Order events use the same data shape.
Order event money fields are sent as decimal major currency units for most currencies. For example, Singapore dollars are sent as dollars, not cents.The one exception is payment_breakdown. Its money fields are sent in minor units, so Singapore dollars are sent as cents.

Event types

Payload

cart_id is the cart the order was created from. It is null when the order has no cart. It equals id on cart events for the same visit, so both event streams resolve to one check. notes is the free-text order note entered at checkout, for example on the POS or by the customer online. It is null when the order has no note. payment_breakdown shows how the order total is made up and how much is paid. amount_paid, amount_unpaid and refunds show the payment status. Its money fields are in minor units (for example, 2850 is S$28.50). order_items contains top-level items only. sub_items contains modifiers and nested components attached to a parent item. A sub-item uses the same fields as a top-level order item. The order_item_id field points to the parent order item, and modifier_id is present when the sub-item came from a modifier.

Channel-filtered payload

Some apps receive order events only for selected sales channels. These apps get a slightly different data shape. Compared with the payload above, a channel-filtered payload:
  • Does not include id. Use order_id instead.
  • Does not include user or order_source.
  • Does not include brand, sections or sub_items on order items.
  • Adds identifier, email, contact_number, created_at and updated_at to outlet.
All other fields, including notes and payment_breakdown, are the same.