Order Types
The order type tells us how the customer intends to receive their order, and it shapes almost everything that follows — which stores are eligible, whether a time can be scheduled, what extra information we need from the customer, and which fees apply. You set it on the cart as metadata.order_type.id, and the store tells you which ones it supports in its order_types list.
| ID | Order Type | Description |
|---|---|---|
| 1 | Dine-in (FS) | Order from your table in a full-service venue, served to the table. ASAP only. |
| 2 | Bill Settling | Pay an existing bill that was opened on the POS, rather than placing a new order. |
| 3 | Pick & Pay | Customer picks items up in store and pays for them through the app. |
| 4 | Dine-in (QS) | Order for in-store consumption in a counter-service venue. ASAP or in advance. |
| 6 | Takeout | Order for pickup. ASAP or in advance. |
| 7 | Delivery | Order for delivery to a specific address. ASAP or in advance. |
| 8 | Curbside | Order brought out to the customer's vehicle. ASAP or in advance. Requires a saved vehicle on the customer account. |
| 9 | Foodspot | Order for collection at a fixed foodspot, such as a locker or a pickup point, within a chosen serving time. |
| 10 | Catering Delivery | Catering order delivered to a specific address. |
| 11 | Catering Take-Out | Catering order collected in store. Sometimes referred to as Catering Pickup. |
| 12 | Drive-Thru | Order collected at a drive-thru window. ASAP or in advance. |
ID 5 is retired and is no longer used. If you receive it on a historical order, treat it as a Dine-in (QS) order.
Not every type can be ordered through the API. A Cart 2.0 cart accepts eight of them — 1, 4, 6, 7, 8, 10, 11 and 12. Bill Settling (2), Pick & Pay (3) and Foodspot (9) belong to other PAR Ordering channels and will be rejected if you set them on a cart, though you may still see them on orders that came from elsewhere.
A few types need more than just an ID on the cart. Curbside expects customer_account_vehicle_id, Foodspot expects foodspot_id together with a serving_time_id, and both catering types expect a catering_info object. The relevant ordering guide for each type shows exactly what to send.