Table token

The table token is the unique id inside each table’s QR URL, so an order from t/abc123 lands on table 4 and nowhere else. The URL pattern is /menu/{restaurant-slug}/t/{table-token}, and the token is the part after t/.

What it means in operation

Every table in the dashboard has a token generated at creation. The token is short, random, and stable, which means it does not change when you rename the table from “Window 1” to “Patio A”. The printed QR is a deep link to the token URL. When a guest scans, the menu opens scoped to that table: the right table session starts, the right id rides every order, the right cover count gets logged. If a table is decommissioned, its token is retired but never reused. The MobiTaste URL pattern is locked in production because printed QRs are in circulation and must keep working.

Why it matters

The token is the load-bearing piece that makes table-aware ordering work without guest logins. A guest does not pick the table number from a dropdown. The QR knows the table because the token is in the URL. That removes one step of friction and one source of error (the guest picking the wrong number). For owners, the token is also the audit anchor: every order is traceable to a specific QR, which helps when reconciling weekend service with the kitchen log.

Related terms

• Slug: the restaurant part of the QR URL.
• Table session: the session the token scopes.
• QR menu: the page the token loads.