The kitchen

Menu: Catalog → Departments · Setup → Printers · Who: owner, branch manager Restaurants only.

A kitchen ticket is printed when the order is placed, whichever button placed it. A dine-in hold, a takeaway paid on the spot, a delivery — the cooks do not care which; they care that the food was ordered.

Turn the paper off entirely for a counter that hands the food over itself: Settings → kitchen.enabled, per branch.

Departments — where a dish is made

A department is where a dish is made: the grill, the bar, the cold station. Written once for the whole company and reused by every branch.

A department is not a menu category. "Pizzas" and "Burgers" are what a customer reads; Grill is where both are made. Keep the two lists apart, or one kitchen gets two tickets for one section.

Where a dish's department comes from: the product, else its category, else none. An unfiled dish is not a hole — it still prints, under Kitchen, on the branch's default kitchen printer. A dish reaching the pass uncooked because somebody forgot to file it is not a trade-off worth making.

Which printer

A department is a company list; a printer is a box on a wall. So the mapping is per branch: one Grill, three branches, three grill printers. Setup → Printers, on the branch.

Only a kitchen printer standing in that branch is offered. A commissary is refused outright — it has no till, so no order is ever rung there.

One slip or several

Settings → kitchen.ticket_mode, per branch:

A department with no printer of its own falls back to the branch's kitchen printer rather than going nowhere.

What is on the ticket

No money, ever. A kitchen ticket with prices on it is a receipt somebody will hand a customer by mistake. It says KITCHEN PRINT across the top before it says whose paper it is, so a slip lying at the pass beside a receipt is told apart at a glance.

What is on it is every detail of the dish: the quantity, the variant ("Pan · 12 inch"), every modifier under the group it was chosen from, every deal component with its own variant and modifiers, and the line's note.

Adding to a table that is already cooking

Recall a held order, add a drink, place it again — and only the drink is sent, headed ADDED TO ORDER so nobody starts the pizza again. Sellify works out the difference from what that kitchen has already been told, line by line.

Reprinting

Kitchen print on the order is the try-again button — a printer is a thing in a room, and it jams. A ticket is kept as the paper it was, so a reprint an hour later is the same slip, not a fresh reading of an order that has moved on.

A branch with no kitchen printer at all sends nothing and records nothing — so the day one is configured, the cooks get what they never saw.

Dine-in: place first, pay later

order.dine_in_holds_first (per branch, on by default) makes the till's big button Place order rather than Pay for a dine-in table. The order is held, the kitchen is told, the table is taken, and the bill is settled later by recalling it. A recalled order shows Pay again — they are settling, not ordering.

Switch it off for a food court that takes the money first.

Printing never rolls a sale back

A printer that is off, jammed or unplugged is reported on the screen and logged. The sale stands. Fix the printer and press Kitchen print.