Menu engineering

Cross-plots each item's popularity against its margin, which is the analysis behind deciding what to promote, reprice, rework or drop.

In the platform, Menu engineering is the menu-engineering module, served under /menu-engineering, with 8 HTTP routes (6 GET, 1 POST, 1 DELETE) — /menu-engineering is the one you will hit first. Of those, 2 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 earns its keep hardest in fine dining and fast casual, which is where the workflow it replaces is usually the most manual. 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 Menu management, Recipe management, Recipe scaling, 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 engineering is driven from the Tablezio interface rather than from the public REST API — the public API covers orders, menu, reservations, customers, loyalty, inventory, analytics, financial reports and webhooks, and this module is not one of them. If you need it programmatically, a webhook on the events it produces is usually the shorter path. See how it fits a whole operation on the fine dining and fast casual pages. 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.