One menu in. Every brand, every platform, priced right out.
The Kitchen Engine is the set of connected modules behind Essen4u. A single master menu feeds platform sync and the pricing engine, demand forecasts shape prep, and performance reports close the loop.
Central menu
Dishes, recipes, food cost and brand assignments live in one place.
Listings go out per brand and per platform, each with its own price inside your limits.
Demand forecast
Expected orders per dish and brand, by day part, turned into prep quantities.
Brand performance
Margin by brand and platform, feeding the next menu and pricing decisions.
Five modules
Use them together. Each one also stands on its own.
Every module reads from the same master menu, so a change made once shows up correctly everywhere it applies.
Why a loop
Pricing without reporting is guessing. Reporting without pricing is a spreadsheet.
A change starts at the master menu
Update a recipe cost or retire a dish once. Every brand listing that uses it is updated on every platform.
Prices respond to the channel
Commission and demand differ per platform, so the pricing engine keeps each listing above your margin floor.
Prep follows the forecast
Forecasts per dish and brand tell the line what to prep for each day part, across all brands sharing it.
Results decide the next move
Performance by brand and platform shows what to reprice, rework or remove from a brand.
One source of truth
No brand keeps its own copy of a dish. Costs and recipes are shared where the kitchen shares them.
Your limits, always
Floors, ceilings and approval rules are set by you and applied before anything is published.
Stock aware
Ingredient usage is tracked across brands so a shared item running low is visible everywhere.
Audit trail
Every automated change is logged with the reason, the rule that allowed it and the result.
Next ticket on the rail
See the engine on your own menu.
Sign up and connect your platforms, or ask for a margin audit and we will walk through it with your brands.