# Phase Handover — 12.2 QR Menu & QR Ordering

## Metadata

| Field | Value |
| --- | --- |
| Phase ID | hospitality-12.2 |
| Title | QR Menu & QR Ordering |
| Status | Complete |
| Service(s) | hospitality |
| Version | 0.12.2.0 |
| Date | 2026-07-26 |
| ADR(s) | ADR-017 (no new ADR) |

## Summary

QR codes, guest menu sessions, ordering sessions, and cart/line shells on `hospitality_db`. Submit is status-only — **no POS/kitchen/payment**.

## Public APIs

| Method | Path |
| --- | --- |
| CRUD/list | `/api/v1/qr-codes`, `/by-token/{token}` |
| CRUD/list | `/api/v1/qr-menu-sessions`, `/by-token/{token}` |
| CRUD + submit | `/api/v1/qr-ordering-sessions`, `/{id}/submit` |
| CRUD | `/api/v1/carts`, `/api/v1/cart-lines` |

## Events

`hospitality.qr_code.created`, `qr_menu_session.created`, `qr_ordering_session.created|submitted`, `cart.created`, `cart_line.added`

## Migration

`0003_phase_122_qr_menu_ordering` (additive)

## Known Limitations

- No kitchen routing from submitted sessions
- No payment / Accounting journals
- Public unauthenticated guest auth via token only (tenant still required)

## Next Phase Entry

Phase **12.3 — Table Service & Reservations**

## Service Snapshot

Regenerated: `docs/service-snapshots/hospitality.yaml`
