Last verified: 2026-05-19
Use POS (point of sale)
Take in-venue or counter orders through the storefront POS screen (staff-operated).
Path
/store/{slug}/pos — replace {slug} with the location slug (same as public storefront).
Requires staff (or admin) session with POS permissions (pos.read, pos.create_order, etc.).
Who can do this
| Role | Access |
|---|---|
| Staff | When POS permissions granted |
| Admin | Typically yes |
Steps
- Sign in as staff or admin.
- Navigate to
/store/{location-slug}/posfor the active branch. - Build an order using the POS catalog UI (categories, items, modifiers).
- Assign order type (dine-in, pickup, etc.) if prompted.
- Submit payment or mark order per POS workflow (cash/card integrations vary by merchant).
- Order appears in
/staff/ordersor/admin/ordersfor fulfillment status updates.
Status updates from POS
POS status changes may call /api/pos/order/status — fulfillment staff should still monitor the orders dashboard for Preparing → Ready → Completed transitions.
Verify it worked
- Order number appears in staff/admin orders list.
- Kitchen or customer displays update if configured.
Common issues
| Symptom | Likely cause | What to do |
|---|---|---|
| 403 / redirect | Missing POS permission | Admin updates role |
| Wrong location catalog | Wrong slug in URL | Use correct branch slug |
