Sell a burger,
a bun leaves
the stockroom.
A dish is made of things, and some of those things are themselves made of things. Until a till understands that, a café's stock figure never moves and the margin on the menu is a guess.
Nested,
because
kitchens are.
One sale on the till pulls every level underneath it out of stock at once, costed at what those ingredients are worth today rather than what they cost the first time you bought them.
Which means the margin on a dish is a number the system already knows, not something worked out on a Sunday with last month's invoices spread across a table.
Front of house.
The counter screen from the point-of-sale plugin, with the parts a room full of tables needs bolted on.
Tables and open tabs
A tab belongs to a table, stays open across courses, and closes as one sale — not as four sales that happened to be near each other.
Order types
Eat in, takeaway, delivery. The type is on the order, so the day's figures separate without anybody having to remember to tag anything.
Modifiers
No onions, extra cheese, oat milk. Priced or free, and carried through to the kitchen ticket so the person cooking sees what the customer said.
Kitchen tickets that age
A ticket colours as it sits. Not a badge somebody has to read a timestamp off — a screen that goes from calm to not calm on its own.
Courses
Send the starters, hold the mains. The kitchen sees what has been fired and what has not.
Split the bill
One tab, several tenders — cash from one person, a card from another, all recorded against the same sale.
About the
restaurant module.
Why does an ordinary shop plugin not work for a café?
Can a recipe contain another recipe?
Do kitchen tickets need a separate screen?
Is the restaurant module included?
The kitchen and the stockroom,
reading the same figure.
The restaurant module sits on the same till and the same stockroom as the rest of the suite.