Menu management

The single catalogue of items, categories and modifier groups that every channel reads — POS, QR, online ordering and the public menu page.

In the platform, Menu management is the menu module, served under /menu, with 19 HTTP routes (7 GET, 4 POST, 5 PATCH, 3 DELETE) — /menu/qr is the one you will hit first. Of those, 12 routes write, so the module is not a read-only report bolted onto someone else's data — it owns its records and the rest of the platform reads them. It belongs to “Menu & recipes”, one of the ten functional areas Tablezio is organised into.

It is not scoped to one kind of venue: it works the same for a single dining room as for a group. Because it runs on the same account, the same locations and the same guest and order records as everything else, there is no nightly sync to babysit and no second login to buy: the reason to replace three subscriptions with one platform is that the third one stops disagreeing with the other two about what happened yesterday.

Inside “Menu & recipes” it sits next to Recipe management, Recipe scaling, Nutrition calculation, and those share its records rather than copying them — the reason the category works as a unit and not as three products that happen to be sold together.

Menu management is one of the modules exposed on the public REST API, so anything the interface does here you can also do from your own code: the Menu API reference documents the request and response shape, the scopes and the cursor pagination. See the solutions pages for how the category fits a whole operation. Which plan includes it is listed on the pricing page: the free plan covers the digital menu, and each paid plan states exactly which modules come with it.