Drive-thru and curbside orders from online and app partners
If customers order through an online menu or mobile app that connects to POSaBIT, the order can tell the store how the customer is picking it up: in store, at a drive-thru window, or curbside. Budtenders can then see where to bring each order, and stores can offer discounts based on how an order was placed.
What your team sees on the POS
Orders show their pickup type on the POS Order Pad, so budtenders know where to bring the order.
Pickup type | What it means |
Pickup – In Store | The customer picks up inside the store |
Pickup – Drive Thru | The customer picks up at the drive-thru window |
Pickup – Curbside | The customer picks up outside, at their car |
Pickup – Kiosk | The order came from your in-store kiosk |
Pickup – Online | An online order with no pickup type |
You’ll see the pickup type:
- On the Order Pad.
- On the Open Existing Order window on the POS. See Opening a kiosk order from the Customer Queue.
- On the order’s picklist receipt, so the person pulling the order knows where it’s going.
Discounts by client type
You can set up a discount that applies only to orders from a specific client type (web, app, kiosk). For example, you could offer a discount on app or kiosk orders.
For these discounts to apply correctly, every POS terminal at your store must be on version 790 or higher and any 3rd party integrator must be submitting orders with the 'client_type' set.
See How to offer a discount on online and app orders.
For integrators
Integrators send pickup details through the POSaBIT Venue API v3 when they create an incoming order. See the Incoming Orders documentation.
Use these fields on POST /api/v3/incoming_orders:
Field | What it tells POSaBIT | Allowed values |
| Where the order was placed |
|
| How the order is fulfilled |
|
| Where a pickup happens |
|
For example, an app order for drive-thru pickup sends client_type: app, fulfillment_method: pickup and fulfillment_sub_type: drive_thru.
The older source and curbside fields are deprecated. Use client_type, fulfillment_method and fulfillment_sub_type instead.