Skip to content

Kitchen printing that survives the internet dropping: stations, local tickets and replay

When the internet drops on Friday night, the dining room should not go blind. Route each item to the right station printer, store every ticket locally first, and replay it to the server when the line returns.

By Wameed field teamOnboarding and support

5 min read

In short: a resilient kitchen needsstation printers (grill, fryer, bar, desserts), each assignedmenu categories, that print aticket per station when a sale completes; alocal ticket store so a ticket is saved first and never lost to a dead printer or a missing uplink; aretry queue with a screen to reprint or dismiss; aLAN link from the till to the kitchen display that works without the cloud; anexpo (pass) screen showing when all stations are done; and anidempotent replay to the server when the internet returns. Kitchen printing is on Wameed’s Professional plan and above. Test it by unplugging the router.

A restaurant that cannot send tickets to the kitchen loses the dining room first and the customers’ trust second.

The problem

Kitchen systems that depend on the cloud fail when the internet fails: the screen stops updating, the printer waits, orders are shouted instead. Most Saudi restaurants have a connection that is good, but not perfect. The aim is a kitchen that does not notice.

Stations and routing

Astation is a place where part of the order is prepared: grill, fryer, cold section, drinks, desserts, pastry.

For each station you configure:

  • A printer profile: network (LAN), Bluetooth or serial.
  • The categories it receives: for example “Grill” gets burgers and kebabs; “Bar” gets drinks.
  • Copies, character width andauto-print.

When the sale completes, the tillsplits the basket by station and prints one ticket per station, with:

  • A bigorder number,
  • Order type (dine-in, takeaway, delivery),
  • Items with quantities,modifiers andnotes,
  • Arabic and English lines as you configure.

Seemodifiers and combos andcashier for restaurants and cafes.

Local first: never lose a ticket

Every ticket is storedfirst in a small local database on the device, then sent to the printer and, later, to the server. So:

  • Adead printer does not lose the ticket; it waits and retries.
  • Asleeping display does not lose it.
  • Amissing uplink does not lose it.

Printing uses aretry queue with back-off, so a printer that returns resumes.

The kitchen queue screen

Operators see what iswaiting for a printer or the server, whatfailed, and canreprint, retry or dismiss. A banner explains why the queue is not sending (plan, permission, session). Without this screen a dead printer silently loses tickets.

LAN mode: till to display

The kitchen display can run a smalllocal listener. The till pushes new tickets straight to it over therestaurant’s network, authenticated with a token, without going through the internet. If the LAN push fails, the local database is the fallback.

The kitchen display merges three sources and removes duplicates:

  1. Theserver (polling and real-time).
  2. Local and LAN tickets.
  3. Tickets that werereplayed.

Unconfirmed local tickets wear aLOCAL banner so staff know the server has not yet seen them.

The expo (pass) screen

An expo screen aggregatesevery station’s ticket for each order. When all stations mark done, the order is flaggedready to pass. This prevents a plate leaving with the burger but without the side.

Replay to the server

When the connection returns, queued tickets are posted to the server through anidempotent endpoint (each has a unique id per store), so a ticket is never created twice, and reports and delivery integrations see it. A permission controls who may replay, and replay is a till-surface function.

Hardware and network

ItemAdvice
Station printersThermal, 80 mm,Ethernet with fixed IP addresses; heat-resistant and splash-protected placement
Router/switchWired links for printers and KDS; a UPS for the router
Kitchen displayMounted away from heat and grease; a wipeable screen
PaperSpare rolls at every station
Buzzer or lightAn alert when a ticket prints

Seereceipt printer guide andkitchen display system guide.

Test it properly

  1. Print a test ticket from each station.
  2. Send a mixed order and check every station gets its items.
  3. Pull the internet cable and send another order. It should still print and show on the display.
  4. Unplug one printer and send an order; the ticket should queue and show in the queue screen.
  5. Restore and check replay.
  6. Do this in a rush, not a quiet hour.

Staff routine

  • Read the ticket aloud at the pass.
  • Bump items when ready.
  • Reprint instead of shouting.
  • Check paper and heat at the start of each shift.
  • Have a manual plan for total failure: handwritten pads and a runner. SeePOS downtime procedures.

Mistakes to avoid

  • One printer for the whole kitchen.
  • Printers on Wi-Fi.
  • No spare paper.
  • No queue screen to see failures.
  • Not testing offline.
  • Mixed Arabic/English with cramped print width.

Frequently asked questions

Does kitchen printing work without internet?

Yes; tickets print over the local network and are stored locally, then replayed to the server.

Can I route items to different printers?

Yes, by assigning menu categories to each station.

What if a printer dies mid-service?

The ticket stays queued; reprint or send to another station.

Which plan includes kitchen printing?

Professional and above.

  • #طباعة المطبخ
  • #طابعة المطبخ
  • #شاشة المطبخ دون إنترنت
  • #تذاكر المطبخ
  • #kitchen printer
  • #offline kitchen display
  • #kitchen ticket routing

Share this article

Ask about your own shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.

Keep reading