Real-Time Order Tracking for Restaurants — Live Demo, Setup, and What Customers Actually See

Every "where is my order?" phone call is a sign that the customer-facing tracking isn't doing its job. A real-time order tracker is one page (per order) that shows the current status, the timestamp of the last update, the ETA if applicable, and a live map for delivery orders. The customer doesn't install anything; the link they got in their confirmation SMS or email opens directly to this page and updates itself live.

This post walks through what the customer actually sees at each stage of an order, what powers the live updates technically, and how a venue admin enables this in roughly 10 minutes.

What the customer sees at each stage

0:00 — Order placed. Page shows "We received your order. Estimated ready time: 7:24pm." Status icon: pending receipt. Timeline shows one filled circle (placed) and three empty ones (preparing, ready, out for delivery).

+0:30 — Kitchen accepts. The same page, no refresh, the second timeline circle fills in. Status text changes to "Your order is being prepared." The ETA may shift slightly based on the kitchen's current load.

+12:00 — Marked ready. For pickup orders the page shows a large "Your order is ready for pickup" banner and the kitchen address with a map link. For delivery orders, the next stage triggers automatically.

+12:30 — Out for delivery. A map appears on the page showing the driver's position relative to the customer's address, updating every 10 seconds. The ETA recalculates based on the actual driver location, not a static estimate.

+17:00 — Delivered. The map closes, the timeline shows all four circles filled, and the page asks for a 5-star rating with one tap. That single rating-tap UX is the highest review-collection conversion we measure across the platform.

What powers it under the hood

Live updates use Pusher Channels — a managed WebSocket service. When the kitchen marks an order as "preparing", the admin app emits an event on a per-order channel. Any browser tab connected to that channel receives the event within ~200ms and re-renders the timeline. There is no polling; the customer's phone is not constantly hammering your server checking for updates.

For delivery tracking, the driver's phone (running the driver app) reports GPS every 10 seconds on a separate channel that the customer's tracking page also subscribes to. The position is shown on a map; the ETA is recalculated server-side using the venue's active routing.

The customer's tracker URL is signed with an unguessable token — the same Bill token pattern used throughout the platform. Without the token, the URL returns 404. So a customer can share their tracker link with a colleague without exposing anything about other orders at the venue.

Setup on a new venue (~10 minutes)

• •Enable "Real-time order tracking" toggle in venue settings (one click)
• •Confirm the tracker URL template is included in the venue's SMS and email order-confirmation templates (default is yes)
• •For delivery: turn on the driver app for at least one driver account and confirm GPS permission on their phone
• •For dine-in (waiter-mode): the same tracker URL can show table-level order progress, including which items are fired vs in the window — useful for venues that want to show customers their food is moving
• •Test by placing a real order yourself; watch the timeline advance on a second device as the kitchen progresses it through the admin panel

No code changes, no separate app to install. The customer never knows there is real-time tech involved — they just see a page that updates by itself.

When it pays off the fastest

High-volume delivery venues see the biggest reduction in support phone calls — the typical pattern is a 40–60% drop in "where is my order?" calls within the first two weeks. Pickup-heavy venues see a smaller call-reduction effect but a larger "customer arrived at the right time" effect (people leave home when the page tells them "ready in 3 minutes" instead of "ready in 15 minutes ± 10").

See the Real-Time Tracking feature page for the full screenshot walkthrough, the Order Notifications page for the SMS/email integration, or the "reduce where is my order calls" blog post for the customer-experience research that shaped this design.