Voice agent, POS as source of truth on price: how PieLine never quotes a number until the POS says so

Why this matters before we trace the call

Every voice ordering vendor will tell you their agent “syncs with your POS.” That sentence describes about six different architectures, and only one of them produces a phone call where the price the customer hears, the price on the kitchen ticket, and the price on the receipt always match.

The cheap version is a nightly menu pull. The agent holds a local copy of every item and price, prices the cart in its own head during the call, says a number out loud, and posts an order somewhere else later. Sync ran at 3 AM. Owner raises lumberjack slam by fifty cents at 7 PM. Agent quotes $13.49 at 7:08 PM. Kitchen ticket prints $13.99. Receipt prints $13.99. Customer arrives, pays $13.99, asks why it is not the $13.49 they were quoted, gets a comp, and the operator absorbs the loss. Multiply by 200 calls a week.

The version PieLine ships is different in one specific way: the agent never holds a price during the call. It holds item IDs. The actual money number is computed by the POS, on the POS, at confirmation time, against the live catalog. That single design decision is what the rest of this page traces second by second.

The 102 second call, with the price moments marked

Below is the timeline of the public demo audio at aiphoneordering.com. The timestamps come from src/components/voice-activity-data.ts. Read down the column: there is exactly one place a dollar amount appears.

That is the entire story. From second zero through second 89, the agent is doing language work: enumerating required modifier groups, confirming back the cart, upselling a dessert, mapping “Coke” to the soft drink combo modifier. Zero arithmetic. The dollar amount enters the call only after the POS has computed it, only after the cart has been validated, and only as a verbatim readback of what the POS returned.

The four stages, written as a contract

If you are evaluating a voice ordering vendor, here is the shape to ask them to describe. PieLine’s implementation passes all four. Cheaper architectures fail at stage three or four because the local copy is on the pricing path.

Where everything the POS knows about price actually lives

The reason it is worth keeping the agent off the pricing path is that the POS knows a long list of things about money that the agent does not. Each row below is something Toast, Square, Clover, NCR Aloha, and Revel all model natively, and that an LLM holding a stale menu copy is structurally bad at:

Every one of those inputs can change between the morning sync and the 7 PM call. A daypart rule fires on the POS clock, not the agent’s clock. A tax rate ticks over at midnight. A special starts when the manager toggles it on the back office tablet. The only way the spoken number, the printed ticket, and the receipt all agree is to ask the POS for the number at the moment of confirmation, every time.

The minimal contract, drawn end to end

Same idea, drawn the other direction. Caller words land on the left, the price exits on the right, and the agent is never the one holding the price.

The 2.4 second silence

People who have not built voice ordering systems sometimes assume the agent should keep talking through the POS round trip to avoid dead air. It should not. The 2.4 second silence between “placing your order now” and “your total is $34.11” is doing real work, and on the caller’s end it sounds like a human cashier ringing in the order. Filling it with chatter would force the agent to talk through information it does not have yet.

The latency budget for that round trip is set by the POS, not by PieLine. Toast and Square both return a priced order in well under three seconds against a typical menu. Clover is comparable. When the round trip exceeds about four seconds the agent inserts a single short phrase like “one moment, finalizing your order” rather than narrating something the POS has not confirmed.

Share of calls handled end to end by AI at Idly Express, with edge cases routed to a manager. The reason the experience reads as natural is that the agent never has to hedge on a number it might be wrong about.

What this rules out

Three behaviors that look harmless in a demo and are actually disqualifying once you watch a hundred real calls:

• Running totals during the call.An agent that says “your subtotal so far is $18.50, anything else?” mid order is computing a price the POS has not blessed. The number can be wrong about a daypart rule, an active special, a tax rate, or a modifier delta. PieLine’s agent does not surface a running subtotal because there is no running subtotal in the agent’s state.
• Quoting a modifier upcharge on the fly.A caller asks “how much is extra cheese?” A weak architecture answers from the menu copy. A correct architecture either answers from a field that was pulled fresh at onboarding and treats it as a soft quote, or defers to the POS round trip. PieLine treats single item price queries as quotable, but never sums modifier deltas during the conversation.
• Predicting the total before posting the cart.Some vendors do this for a perceived UX win, then reconcile later when the POS disagrees. PieLine’s agent waits the 2.4 seconds. The customer hears the real number once, and that number matches what they pay and what the kitchen sees.