Kitchen Printer Setup: a No-Nonsense Guide

A kitchen printer setup that doesn't cause trouble comes down to four decisions: where the printer physically goes, how it connects (wired Ethernet, almost always), whether its network address can change (it must not), and how your POS routes tickets to it. Get those four right and a kitchen printer is boring for years. This guide walks through each one in plain terms, plus the trap that catches most restaurants the day a printer dies and gets replaced.

Placement: heat, steam, and grease decide for you

Before any network settings, pick the spot. Kitchens are hostile to electronics, and the two printer technologies handle it differently:

• Thermal printers (quiet, fast, no ink) print by heating the paper. Heat and steam are their enemies — mounted over a grill or dish pit, the paper darkens and tickets fade. Keep them at the pass/expo window, at the bar, or anywhere away from direct heat.
• Impact printers (the loud clack-clack ones with a ribbon) physically strike the paper, so heat and humidity barely bother them. They belong at the grill and fry stations.

Full breakdown with prices in our thermal vs impact comparison. Wherever it goes:

• Mount it above counter level, away from splash zones and direct steam.
• Leave clearance above for the paper to feed and be torn off with one hand.
• Route the cables so they don't cross a walkway or a wet area.

Connection: Ethernet beats Wi-Fi in a kitchen, every time

Kitchen printers come with a few connection options. Here's the honest ranking for a restaurant:

Two wiring tips that pay for themselves:

• Run the cable once, properly. A single Ethernet run to each station, stapled out of harm's way, outlasts every other part of the setup.
• Consider PoE (Power over Ethernet). Some printers and adapters can draw power through the network cable itself, which means one cable to the station instead of two and no hunting for an outlet behind the fryer. Check the printer's spec sheet for "PoE" before assuming.

The address problem: why tickets vanish weeks after everything worked

This is the single most common kitchen printer failure, so it gets its own section.

Every device on your network gets an address — an IP address, which looks like 192.168.1.240. By default, your router hands these out on temporary leases ("DHCP"). Temporary is the problem: after a power cycle or when a lease expires, the printer can come back with a different address. Your POS is still sending tickets to the old one. Nothing prints, nothing errors visibly, and it happens weeks after setup when nobody remembers touching anything.

You have two fixes. Either works; pick one and write it down.

Option A — DHCP reservation (do it on the router, recommended):

1. Print the printer's self-test page (power off, hold FEED, power on). Note its MAC address — a permanent hardware ID like A0:B1:C2:D3:E4:F5 — and its current IP address.
2. Log in to your router's admin page (the address and password are usually on a sticker on the router).
3. Find "DHCP reservations," "static leases," or "address reservation" in the LAN settings.
4. Add a reservation tying the printer's MAC address to its current IP address.
5. Power-cycle the printer and confirm the self-test still shows the same address.

Now the router always hands that printer the same address, forever, and the printer itself needs no configuration.

Option B — static IP (set it on the printer):

1. Pick an address outside the range your router hands out automatically (e.g., if the router assigns 192.168.1.100–199, use 192.168.1.240).
2. Set it using the printer's setup utility or button-menu (varies by brand — check the manual for "static IP").
3. Label the printer with its address on a piece of tape. Your future self will thank you.

Routing: which tickets go to which station

With printers placed and addressed, tell the POS who gets what. Every major POS has some version of this under names like "printer routing," "kitchen routing," or "prep stations":

1. Add each printer in the POS hardware settings by its IP address. Print a test ticket to each one and physically confirm which device printed it — it is very easy to add two printers and swap their names.
2. Create stations (grill, fry, salad, expo, bar) and assign each menu category to a station.
3. Decide what expo sees. Most kitchens send every item to the expo/pass printer, and only the relevant items to each prep station.
4. Test with a real multi-station order — an appetizer, a grilled item, and a bar drink on one ticket — and confirm each station prints only its part.

Re-test routing after any menu overhaul. New categories silently defaulting to the wrong station is a classic soft failure: food still gets made, just late and by shouted relay.

The swap-failure trap (read this before a printer dies)

Here's the field problem that industry guides flag over and over: the day a kitchen printer dies mid-service, someone buys or borrows a replacement, plugs it in — and nothing prints. The replacement has a different IP address, sometimes a different protocol dialect, and the POS is still configured for the old unit. Now you're editing POS hardware settings during a rush, possibly on a support call, possibly discovering your POS doesn't recognize the replacement model at all (many cloud POS systems only support a short list of certified printers).

Reduce the blast radius:

• Keep the address list current (see above). If the replacement can be given the dead printer's exact IP address, many POS setups resume printing with zero reconfiguration.
• Prefer same-model spares. A used unit of the same model is the cheapest insurance there is. If you're buying spares, our thermal vs impact guide covers what each class costs.
• Put a stable address in front of the printer. The structural fix: if the POS talks to an address that belongs to a small box in front of the printer rather than to the printer itself, you can swap the printer behind it — different brand, different model, even USB instead of Ethernet — and the POS never notices. The address it prints to never changed.

That last approach is what we're building. A ProxyNode is a small device (currently prototype stage — proven on the bench, pilot installs starting) that sits next to any printer and presents one fixed, standard network-printer address to your POS. Swap the hardware behind it and the POS keeps printing to the same address it always did. It also keeps the whole print path on your local network, which matters more than most people realize — see what happens to cloud POS printing when the internet goes down.

Setup checklist

1. Pick placement per station: thermal at pass/bar, impact at grill/fry.
2. Run Ethernet to each station; consider PoE to skip the power outlet.
3. Give every printer a permanent address (DHCP reservation or static IP).
4. Tape an address list inside the office cabinet.
5. Add printers to the POS by IP; test-print to confirm identity.
6. Set up station routing; test with one multi-station order.
7. Line up a spare-printer plan before you need it.
8. Once a quarter: reprint self-tests, verify addresses, re-test routing.

More operator guides live on our restaurants page.

FAQ

Frequently asked questions

Should my kitchen printer use Wi-Fi or Ethernet?

Ethernet, wired. Kitchen environments are hard on Wi-Fi — metal shelving, coolers, and microwaves cause dropouts, and a dropped ticket during a rush is expensive. Run the cable once and the connection is solved for years.

Why did my kitchen printer stop printing when nothing changed?

The most common cause is a changed IP address. Routers hand out addresses on temporary leases, and after a power cycle the printer can come back on a different one while the POS still sends tickets to the old address. Fix it permanently with a DHCP reservation on your router or a static IP on the printer.

What is the difference between a static IP and a DHCP reservation?

Both give the printer a permanent address. A static IP is set on the printer itself; a DHCP reservation is set on the router, which then always assigns that printer the same address. Reservations are usually easier to manage because everything is configured in one place.

Can I just replace a broken kitchen printer with any new one?

Often not cleanly. The replacement comes up on a different IP address, may behave slightly differently, and may not be on your POS provider's supported list. Keep an address list so you can reassign the old IP, prefer same-model spares, or put a fixed proxy address in front of the printer so the POS never sees the swap.

How many kitchen printers does a restaurant need?

Most full-service kitchens run two to four: an expo/pass printer that sees every item, plus one per busy prep station (grill, fry, sometimes salad) and often one at the bar. Small or low-volume kitchens run fine with a single expo printer.