33 · QSR & pizzeria vertical pack

1. Goal

2. Day-in-the-life flow

flowchart LR
  POS[Modern POS
fulfillment + builder + deals]
  SF[Storefront
restaurant mode]
  CART[Cart metadata
orderType · channel · guest]
  KDS[Kitchen tickets
orderId = cart id]
  EXPO[Expo board
all stations DONE]
  DEL[Delivery board
prep → ready → out]
  INV[Inventory burn
SKU or configurator]

  POS --> CART
  SF --> CART
  CART --> KDS
  CART --> INV
  KDS --> EXPO
  EXPO --> DEL
  CART -->|orderType delivery| DEL
          

3. Order fulfillment (POS cart metadata)

UI: Modern POS → Order fulfillment bar. API: PATCH /api/pos/carts/:id/metadata. Codes: backend/utils/orderFulfillment.js.

4. Product configurator (pizza builder)

• Catalog item metadata.configurator (sizes, crusts, sauces, toppings, half & half).
• Admin: /admin/catalog/configurator — attach builder + inventory Inv ID / SKU / burn qty.
• POS / storefront: ProductConfiguratorDialog → line name, base + modifierCents, mods[].
• Mixed carts: configured pizza plus normal inventory SKUs in one cart is supported.

5. Kitchen · Expo · bake timers

See also 15 · Floor · KDS · Beacon.

6. Delivery dispatch

Status: quoted → prep → ready → out → delivered (+ cancelled).

• UI: /pos/delivery (alias /pos/dispatch)
• Table: delivery_orders on tenant main
• Auto: send-to-kitchen on delivery cart → prep; Expo bag → ready
• QA: Admin Tools → Seed delivery board

7. Deals / combos (pilot)

GET /api/pos/deals · POST /api/pos/carts/:id/deals/apply · POS button Apply deals.

8. Shared storefront (not a pizza site)

• Admin → Storefront Settings → Business mode
• Fields: businessMode, verticalConfig on storefront_settings
• Guest: /{tenant}/store · paid handoff via storefrontKitchen.bridge.js

See 18 · Customers & Storefront.

9. Inventory on finalize

Util: backend/utils/configuratorInventory.js. Admin: Catalog → Configurator → Inv ID / SKU / burn. Detail: 25 · Inventory.

10. API map (quick)

11. Aggregator ingest (Phase 3a)

Generic third-party order webhook → same cart / KDS / delivery spine. Partner-specific DoorDash/Uber adapters and menu sync are still later.

Auth: staff session or X-Api-Key. Cart metadata: channel=aggregator, orderChannel=third_party, channelRef. Table: aggregator_order_refs. DoorDash / Uber-shaped JSON is auto-mapped. Optional HMAC: X-Integrations-Signature (+ tenant secret or env). Smoke: npm run smoke:qsr in app/backend.

Kitchen Displays includes an oven handoff toggle (ovenHandoffEnabled). Mobile POS supports seating when the device has the visualizer enabled.

Brand pack (3b): GET/PUT /api/admin/franchise · Storefront Settings → multi-unit brand metadata for this tenant only (locations under one business — not cross-tenant HQ menu push). Storefront card tries the payment orchestrator; ?demo=1 for simulate.

12. Operator pilot checklist

1. Kitchen Displays → Apply pizzeria stations · set oven handoff on/off.
2. Catalog → Configurator → BYO pizza + link toppings to inventory.
3. Optional: /admin/deals — custom fixed $ off + toggle builtins.
4. POS or Mobile POS → Build pizza + soda → fulfillment / seating → Apply deals → pay / send kitchen.
5. If ingredients short → add is blocked with shortfall message.
6. KDS → bump make → auto oven ticket (if enabled) → bump oven → Expo → Bag.
7. If delivery → ZIP for zone fee · /pos/delivery → assign driver → Out → Delivered.
8. Storefront Settings → Restaurant mode + zone rows → guest order on /{tenant}/store.
9. Tools → QSR smoke check (deals, burns, zones, oven setting, sample aggregator order, make ticket).
10. Optional: POST /api/integrations/orders with a DoorDash-like payload for channel testing.

13. File anchors

14. Related DocHub chapters