We mounted a Zebra ZQ620 by the drink station last week and shaved 9 seconds off average car time during the 5–7pm rush — fewer remakes and better name use at the window. What models/settings are holding up to syrup and steam, and how are you triggering prints from KDS without slowing the lane?
We mounted a ZQ610 at the drink bar and, , steam wrecked paper until we swapped to Zebra PolyPro 4000D; running darkness 18, about 3 ips, and sleep off keeps labels readable through syrup. On the KDS side (Toast), we route Drinks to the printer and set it to “print on fire” via @ToastPOS Browser Print so the tag hits before the cup, not at bump — no lane drag. If you’re not on Toast, same idea works in QSR Automations; what are you using?
We run a ZQ620 linerless above the ice well with Zebra 8000D Linerless and the dispenser “peel mode” on; darkness 14 at about 2.5 ips has held up to steam/syrup and sticks on wet PET (plus no backing confetti). Prints fire from KDS via a tiny local proxy — KDS posts a webhook on “bev” items, proxy streams ZPL to the printer’s static IP over Wi‑Fi, so no Bluetooth wake lag. If you stay BT, bump sleep to 5 min and enable persistent bonding, but Wi‑Fi shaved about 0.3s per ticket for us; what KDS are you on, @lnewton88?
Nice win on the 9 seconds, @OP. One tweak that killed our first-label lag: our KDS pings the ZQ620 with a tiny ‘~HS’ status command every 30 seconds from 4:30–7:30, which keeps it awake so drink stickers fire instantly when items hit the drink station; battery takes a small hit but we still clear a full shift. If you’re on Toast KDS, the print profile lets you auto-print only when the order is marked Paid so edits don’t double-print; does your KDS support a simple keep-alive like that?
Shave the KDS hop by storing a ZPL format on the ZQ620 and having KDS send only variables with an ^XF call when the drink chit hits ‘bev fired’ — it’s giving the printer the Cliff Notes. Building on @kylie_hansen92, did you also disable Wi‑Fi power save on the printer to stop wake delays? That combo cut our send time from about 1.2s to under 300ms per label in the rush.