Scale
Set it once centrally, override only where a location genuinely differs — and let everything else inherit.
Which plan? Included in Chain
Downtown
breakfast + main menu
open menu →
Terrace
bar menu · after 18:00
open menu →
Chains fail at digital menus in one of two ways: either every branch is managed separately until they drift apart, or everything is forced identical until the branches resent it. Inheritance solves both. Define the menu centrally, and let a location override only the handful of things that are actually different.
01
Any field you leave blank on a location takes the general value. Fill it in and that location overrides it. There is no copying and no drift.
02
A bar menu after six, a breakfast-only branch, a different price in the airport location — all expressed as exceptions rather than separate menus.
03
Guests scanning a table code go straight to that location. Guests arriving from a general link get a location picker.
Three on the Chain plan, with additional locations available.
Yes, with permissions — a location manager can be limited to their own branch.
No. That is exactly what inheritance avoids: one menu, with exceptions where needed.
Daily traffic, an hourly heat map, a menu funnel, an interest ranking per dish and automatic notes written for you.
A read-only menu API, scoped keys and HMAC-signed webhooks when the menu changes.
Track ingredient levels by hand — anything below your threshold is highlighted in red, in the panel and in the app.
Free for 14 days, no setup fee. Cancel before the trial ends and you won't be charged.