Prep lists

Builds the day's prep from the menu and forecast, so what gets prepped is derived from what is expected to sell.

In the platform, Prep lists is the prep-lists module, served under /prep-lists, with 13 HTTP routes (5 GET, 2 POST, 4 PATCH, 2 DELETE) — /prep-lists is the one you will hit first. Of those, 8 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 “Kitchen operations”, 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 “Kitchen operations” it sits next to Kitchen display routing, Kitchen printer routing, Beverage program, 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.

Prep lists 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 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.