Kitchen printer setup for a restaurant: an architecture that survives Friday

Every restaurant's printing design looks fine on a Tuesday afternoon. Friday at seven — delivery tablet piling up, expo short-staffed, somebody vacuuming near the switch — is when the design gets reviewed. What separates a venue that absorbs a rush from one that loses tickets is not print speed on a datasheet. It is where the printers are, what they are plugged into, whose machine has to be awake for an order to reach the grill, and whether anyone notices when a station stops.

Why the counter and the kitchen are different machines

A front-of-house printer lives in air conditioning, three metres from a till, in a case chosen partly for how it looks on the counter. A kitchen printer lives in flour dust, grease mist, radiant heat off the pass, steam and the occasional wash-down, on a cable run that has crossed a room.

Dust and grease go where paper goes, which is into the mechanism: the intake sits next to the paper path, and a film of grease on the platen is a permanent jam generator. Sustained ambient above the rated range shows up as pale lower thirds on tall tickets and intermittent stalls, which staff report as the printer being temperamental.

So spec them separately: a counter unit where cosmetics and noise matter, and a sealed, wall-mountable 80 mm unit with a cutter for the pass. EDOO lists the ED808 as an 80 mm wall-mounted thermal bill printer for kitchen, front desk and ticketing, alongside counter units such as the ED809. Mounting is a design property, not a bracket: the door has to open with the unit vertical, the cutter has to shed offcuts away from the mechanism, and paper-out has to be visible from where food is checked.

The printer has to work when the POS PC does not exist

The most common architectural mistake in independents is a kitchen printer plugged into the till by USB. It works beautifully until someone puts that till to sleep, takes the machine away for service, reinstalls Windows, or closes the front-of-house PC at eleven while late delivery orders keep arriving.

The fix is two-part. Give the kitchen printer its own address on the network — Ethernet, or Wi-Fi only where the building genuinely permits it — so it is a peer of the POS server rather than an appendage of one desk. And make sure something spools: the queue belongs on a machine that stays up, and the printer should confirm it accepted the job so the server can mark it delivered. The failure you are designing out is the ticket the software believes it sent. Print a sequential number on every ticket and you can reconcile "we sent 214" against "the grill had 213", which is the only evidence that settles an argument about a missing order.

Star, ring, and where the cheap switch bites

Draw the physical network before you buy hardware, and draw it as a star: one switch per zone — front of house, kitchen, drive-thru — a single documented uplink between zones, every printer on its own port. A daisy-chain saves cable, but each device in the chain carries the next one's connectivity: unplug the bar's little unit and the pass and dispatch go dark with it. Worse, two accidental uplinks between the same switches form a loop, and a loop on an unmanaged switch is a broadcast storm that takes the whole estate down in seconds — the real explanation for "everything stopped at once".

The switch rarely fails on capacity; it fails on the corners. Consumer power-management on Ethernet ports negotiates oddly with a printer's fixed-speed port and gives a link that flaps under load, and tiny buffers with no flow control are exactly what a burst of tall ticket jobs tests. Buy a small managed switch for the zones carrying orders, disable energy-saving Ethernet on printer ports, and keep order traffic off the guest network on its own VLAN or at least its own SSID.

IP addressing discipline, and labels that outlive the installer

Every printer should be answerable by a name, an address and a switch port.

pool. Never a manual address the server also hands out — that is the Monday outage where the pass printer's address now belongs to someone's laptop.

in a hot kitchen, not in a spreadsheet at head office.

• Give each unit a DHCP reservation keyed to its MAC, inside the pool and documented, or a static address outside the
• Print the settings page after commissioning, so address, subnet and firmware exist on paper in the site file.
• Label the chassis with hostname, IP and asset number, and both ends of its patch lead. Labels are read on a ladder
• Name by role: KITCHEN-PASS-01, not PRINTER3. Staff report faults using the words on the label.

Paper stock, and the one-for-one ticket policy

Standardise paper by the machine's real requirements: width, maximum outer roll diameter the bay accepts, core diameter. The cheapest roll is a false economy when it is a fraction of a millimetre thinner and rougher — the symptom is a slip-feed that eats the top of every ticket, and staff blame the printer. Re-test whenever the paper supplier changes, because that is an unannounced hardware change, and hold spare rolls where the printing happens, not in the office.

Then make the ticket policy explicit in the software rather than in staff habit: one print of each line at each station that needs it, and never a whole-order reprint because one item went missing. Undisciplined reprinting produces two chicken dishes and no lamb, which is worse than the ticket you lost. Route line subsets per station, mark manual reprints on the ticket with a reason, and print a fire ticket when a line is cancelled.

Placement: wall mount versus counter, and cable strain

Mount where the ticket is read, not where the socket is: above the pass, at eye line from the expo position, with the paper-out lamp visible without walking anywhere and the door clear to swing fully. Then the faults that come back. A lead pulled taut across a busy pass pulls on the connector, the connector goes intermittent, and the fault is reported as a network problem — leave a service loop and fix the run to something solid. And nothing goes directly above a fryer or in the splash line of a hose, where cable entries belong below the machine, not into the top of it. If the work is genuinely mobile, a handheld with a built-in printer is a different architecture: EDOO lists the EP600 as a 4G Android POS terminal with a high-speed 120 mm/s thermal printer, which puts the ticket in a hand and costs you paper capacity.

Alarms for courses with a deadline

A kitchen is loud and the expo is busy, so a silent printer is a stopped printer. Specify what the machine does when it cannot print, and check it from where the food is checked: an audible alarm on paper-out and error at the kitchen station so a fault is noticed in seconds, and the opposite at the front of house, where a suppressed tone and a lamp is what you want near customers — a per-SKU firmware profile, not a compromise. Ask for a near-end-of-paper warning rather than a hard stop, so the roll changes between courses instead of during one, and make the online, paused and error states readable at a glance from the pass.

Role versus recommended capability

Commission it before Friday, not on Friday

Four destructive tests, run when the room is empty. Print the worst realistic order — the sixteen-line basket with modifiers — on every station at rush rate, then read the tickets in that light and from that distance. Shut the front-of-house PC down and place an order: if the grill does not get it, you have a USB kitchen printer. Pull one zone's uplink mid-print and see what recovers on its own. Then stand at the pass, look away from a printer, and have a colleague empty its roll; if it takes longer than a course to notice, the alarm design is wrong. Write the answers up as the site template, because the hardware is the easy part and the design is the thing that shows up on a Friday.

FAQ

What is a kitchen printer and how does it differ from a receipt printer? A kitchen printer is a network-addressed, usually wall-mounted thermal unit that prints order tickets at the food preparation stations, differing from a counter receipt printer in its sealed housing, its tolerance of heat and grease, its auto cutter, and the fact that it must keep receiving orders when the front-of-house till is switched off.

Should kitchen printers be on the network or plugged into the till? On the network with their own address: a USB kitchen printer only works while the specific PC it is attached to is awake, correctly configured and running the right software, whereas a networked printer is a peer of the POS server and can be reached from any till in the venue.

Why do our kitchen tickets sometimes never print? Because the job died before it reached the mechanism — a till or server that was asleep, an address that changed when leases renewed, a link flapping on a switch with energy-saving Ethernet enabled, or a printer out of paper while nobody could see its lamp — and the answer is a spooling queue that confirms receipt plus alarms visible from the pass.

How many printers does a kitchen need, and does the paper matter that much? One per station that must act on part of an order — typically line, expo, bar and dispatch — because a shared device is one failure for three stations; and each needs the width, maximum roll diameter and core size the bay was designed for, since an oversized or thinner roll slip-feeds, eats the top of every ticket and jams the mechanism.

Related EDOO resources

All EDOO solutions · Receipt and label printers · services · Android PDA and POS terminals · Cashier · CashRegister · ODM / OEM services · Product documentation and SDKs · Contact EDOO