Skip to content
MasaKasa

Getting orders to the kitchen without paper tickets

5 min read

Short answer

A till that prints to a thermal printer at each station replaces the pad. The part that decides whether it works is splitting: one order often needs to reach both the kitchen and the bar, and each station should see only its own items while both carry the same order number.

The order pad works. That is worth saying first, because plenty of advice on this subject starts from the assumption that paper is obviously bad, and it is not.

Paper is fast, it never crashes, and every member of staff already knows how to use it. What it does badly is everything that happens after the order is written: the walk to the kitchen, the handwriting, the second copy for the bar, and the totting up at the end.

So the question is not really “how do I stop using paper”. It is “which of the things after the order is written do I want to stop doing”.

What actually goes wrong with pads

In a small café, the trouble usually shows up in the same three places.

The second station. A breakfast goes to the kitchen. The tea that comes with it needs to reach the bar. Someone has to either write it twice or shout. Both work until it is busy.

Amendments. A table changes their mind after the ticket has gone. Now there is a conversation at the pass, and whether it lands correctly depends on who heard it.

The bill. At the end, someone reads handwriting and adds up. Small errors here are quiet and constant, and they come out of your margin rather than showing up as a complaint.

If none of those three are hurting you, you may not need to change anything.

What replaces it

The mechanics are simple enough. A member of staff takes the order on a device. The software sends it to a small thermal printer at each station that needs it. The ticket comes out already legible.

The bit that decides whether this actually helps is splitting, and it is the bit most worth testing before you commit.

Splitting is the whole job

Take a real order. A Set 1 breakfast, which comes with a hot drink and a slice of toast. Plus a flat white with oat milk.

The kitchen needs: Set 1, and the toast.

The bar needs: the flat white with oat milk, and the tea that came with the Set 1.

Notice what has to happen. The tea was ordered as part of a breakfast, but it is made at the bar, so it has to be lifted out of the kitchen’s ticket and onto the bar’s. And when it arrives at the bar it needs to say what it belongs to, or the person making it has no idea which plate it goes out with.

Both tickets also need to carry the same order number. That is what lets the pass put the two halves back together.

Get that right and the paper problem is solved properly. Get it wrong and you have replaced a shouting problem with a printing problem.

Questions to ask a supplier

Bring your own menu to the demonstration, not theirs, and ask for these specifically:

  • Show me one order that has to reach two stations. What comes out of each printer?
  • An item included with a set meal is made at the bar. Which ticket does it appear on, and does it say what it belongs to?
  • Both tickets: do they carry the same order number?
  • Now amend that order. What prints, and at which station?
  • Now cancel a single item. What prints?
  • If the printer is out of paper when the order is sent, what happens? Does anything tell anyone?

That last question matters more than it sounds. A ticket that silently fails to print is worse than no system at all, because everybody believes the kitchen has it.

The hardware is the easy part

Most cafés already own more of this than they expect.

A standard thermal receipt printer is the usual choice, and if you have one at the counter now, it is very likely the right kind. Two stations means two printers, one at each, which is the main cost if you are starting from nothing.

One practical note from kitchens: thermal paper does not enjoy heat and steam. A printer at the pass in a café kitchen is normally fine. A printer sitting next to a fryer is not. Position matters more than model.

Changing over without a bad week

The mistake is switching everything on a Saturday.

Pick a quiet service. Run the new system and the pad together for a couple of days, with the pad as the safety net rather than the main method. Watch where staff hesitate; that is where the layout or the menu structure is wrong, not where the staff are.

Get your menu right before you start. Most of the pain in the first week is not the software, it is discovering that your option groups do not match how people actually order.

And keep the pads. Printers run out of paper, and knowing there is a fallback in the drawer takes the fear out of the change.

Where MasaKasa sits

This is the part of MasaKasa that took the longest to get right, because it is the part that decides whether a café keeps using it.

An order is split by station and printed. An item that comes with a dish but is made elsewhere is lifted onto the right ticket and marked with the dish it belongs to. Both halves carry the same order number. Amending or cancelling sends a fresh ticket to the same station under that same number, so the kitchen is never left working out what changed.

It drives a standard ESC/POS thermal printer, which is the kind most venues already have.

The short version

Replacing the pad is easy. Replacing it without creating a new problem at the pass comes down to how the system splits one order across two stations, and whether both halves stay tied together. Test that with your own menu before you decide.