Cashier Says A, Kitchen Hears B: How to Eliminate Front-Back Miscommunication

The Problem: Information Gets Lost in Transit

Customer tells the cashier: "Cappuccino with less sugar, please." Cashier nods. But what reaches the barista is just "1 Cappuccino." Result: a standard-sugar Cappuccino comes out, customer is disappointed, and the barista is confused about why they're being blamed.

This isn't a people problem — it's a communication system problem. Every time information passes from one person to another without a clear medium, there's a chance it gets lost or changed.

In small cafes, front-back miscommunication usually shows up as:

• Order modifications that don't reach the maker (less sugar, extra shot, no ice)
• Orders delivered to the wrong table
• Items missing from multi-item orders
• Dine-in orders packaged as takeaway (or vice versa)

Why Shouting Isn't Enough

In many small cafes, the "communication system" between cashier and kitchen/bar is shouting. "One Latte less sugar!" → barista says "Got it!" → done.

This works when:

• Volume is low (1-2 orders at a time)
• Cashier-bar distance is short
• Environment isn't noisy
• Orders are simple with no modifications

But once any of these conditions isn't met — and during rush hour none of them usually are — shouting becomes unreliable. A barista steaming milk can't hear details. A cook frying can't respond. And there's no record if there's a dispute later.

Fix 1: Printed Tickets = Source of Truth

The most reliable way to eliminate miscommunication: make written information arrive at the preparation station.

With a POS connected to a printer at the bar or kitchen, the flow becomes:

1. Cashier enters the complete order with all modifications
2. Ticket automatically prints at the correct station (drinks → bar, food → kitchen)
3. Maker reads the ticket — no memory needed, no shouting
4. After completion, ticket is spiked or crossed off — proof the order was made

Benefits of printed tickets:

• Nothing gets lost. All details — including modifications — are clearly written
• No reliance on memory. The barista can check the ticket anytime, no need to remember something shouted 2 minutes ago
• Clear sequence. Tickets come out in order — so makers know what's first
• Evidence trail. If there's a dispute ("I ordered less sugar!"), you can check the ticket. If the ticket says less sugar but it was made standard, the issue is in preparation. If the ticket has no note, the issue is in input

Fix 2: Standardize How Modifications Are Entered

Tickets are useless if the information the cashier enters is incomplete. Classic problem: the cashier remembers the customer asked for less sugar but forgets to input it because they're in a rush.

How to solve this:

• Make common modifications into POS buttons. Less sugar, extra shot, no ice, hot, iced — if these are tap-able buttons, cashiers are more likely to select them than to type manually
• Train cashiers to ALWAYS confirm modifications. "Cappuccino less sugar, right? Anything else?" Verbal confirmation + immediate POS input = natural double-check
• Establish the rule: if it's not on the ticket, it's not the maker's responsibility. Sounds harsh, but it creates discipline. Cashiers know that what they don't input won't be made — so they're more careful

Fix 3: Split Tickets by Station

If one order has both drinks and food, ideally separate tickets go to each station. The barista gets the drink ticket, the kitchen gets the food ticket.

Why this matters:

• The barista doesn't need to scan an entire order to find the drink items
• The kitchen isn't distracted by items that aren't their responsibility
• Each station can work in parallel without coordinating "which part is whose"

Fix 4: Clear Handoff Signals

After an order is prepared, there needs to be a clear way to signal it's ready. This is often the second point of miscommunication — the order is done but nobody brings it to the customer.

Options that work:

• Table numbers. Order done → find table number → deliver. Simple and no technology needed
• Call by name/number. "Order for number 7!" — works for counter-service cafes
• Bell or buzzer. Kitchen rings the bell = signal that an order is ready for pickup by a runner

The key: don't rely on telepathy. There must be a clear, consistent signal that an order has moved from "being made" to "ready for delivery."

Fix 5: A 2-Minute Daily Brief

Before the shift starts, gather all staff for 2 minutes. Cover:

• Any menu items that are unavailable today? (So cashiers don't take orders that can't be made)
• Any promotions or new items? (So the kitchen is prepared)
• What went wrong yesterday and how to prevent it today?

This 2-minute brief prevents 80% of miscommunication that comes from assumptions. "I thought we still had it" and "I didn't know about the promo" disappear when everyone starts from the same information.

Measuring Improvement

The simplest way to measure whether miscommunication is improving: count the number of remakes per day.

Before changes, track remakes per day for one week. After implementing changes, track again. If remakes go down, your communication system is working.

Realistic target: zero remakes is ideal but unrealistic for high volume. 1-2 remakes per day in a cafe handling 50+ orders is still acceptable. More than 5? There's a systemic issue that needs fixing.