I have genuine respect for what Domino's has built. The Pizza Tracker, when it launched in 2008, was legitimately ahead of its time. And this week's Tracker update — AI-powered ready times, iOS Live Activities, GPS driver tracking — is impressive engineering. They deserve credit for it.
But reading this announcement as a CTO, I couldn't help but notice what it actually represents: an 18-year, multi-million dollar engineering investment, built on a proprietary operating platform called DomOS, to solve a problem that restaurants can solve today — without a custom OS, without a dedicated engineering org, and without ripping out a single piece of hardware.
That's not a knock on Domino's. It's a signal to every other brand still managing order timing with static quote times and manual throttling.
Before we talk about what Domino's built, let's talk about what's at stake across the industry.
Curbit recently analyzed public guest feedback across 136 restaurant brands representing more than 29,000 locations. The finding: over $150 million in annual revenue is at risk from a single upstream problem — food sitting at expo. Orders completed before the guest arrives, declining in quality with every passing minute, driving complaints that show up in Google reviews, delivery ratings, and repeat visit rates.
This isn't a niche issue. It's the single largest controllable variable in off-premise food quality, and most brands don't have visibility into it today.
The heart of this update is more accurate ready-time prediction. Domino's is now blending real-time inputs from store staff with machine learning models to surface better estimates of when an order will actually be ready for pickup or delivery. According to their press release, this runs on DomOS — their proprietary operating platform — and it's been 18 years in the making.
That's genuinely valuable. Inaccurate wait times are one of the top drivers of guest frustration in the off-premise channel. When a guest pulls up to a carryout window 30 seconds before their food is ready, that's a great experience. When they've been sitting in a lobby for 12 minutes watching a tracker that said "almost ready," that's a loyalty problem — and a food quality problem.
This is exactly the problem Curbit was built to solve. The difference is we solve it at the location level, for any brand, in weeks — not decades.
"The problem Domino's solved at enterprise scale with a proprietary OS is the same problem Curbit solves at the location level, for any restaurant, from day one — no hardware, no retraining, no custom dev required."
Here's something worth unpacking as a technologist: what Domino's updated is primarily the customer-facing view of order status. What the best-performing off-premise operations are focused on is something upstream from that — controlling when orders fire to the kitchen in the first place.
If an order fires to the kitchen the moment it's placed on a third-party platform, but the driver isn't arriving for 14 minutes and the food is ready in 8 — the tracker can say "ready!" all it wants. The food has already been sitting for six minutes. The guest experience, food quality, and likelihood of a repeat order have already been compromised. No amount of UI polish changes that math.
This is the upstream problem that Curbit's order orchestration platform was designed to address. We connect directly to the KDS — Toast, QSR Automations, Aloha, Brink — read live kitchen speed of service in real time, and use that signal to control when each order fires, so food is ready at pickup, not sitting at expo. We call it the Goldilocks Zone®: not too early, not too late, but just right.
The results are measurable and specific. California Fish Grill reduced food sitting at expo longer than five minutes from 61% of orders to 13% — across 67,000 orders in a controlled pilot. Call Your Mother Deli saw digital revenue increase 21.5% and delivery revenue increase 24.1%. Jollibee improved quote time accuracy from a 3.4-minute average miss to near-perfect — within six hundredths of a minute — in a 30-day pilot across 3,440 orders.
Brands like CAVA, Jollibee, Dave's Hot Chicken, Smashburger, Lazy Dog, and Mellow Mushroom are already operating this way.
🍔 Read more in our Smashburger case study →
Curbit doesn't replicate what Domino's built. We solved a different and more universal version of the problem: real-time fire-time control that works with any brand's existing infrastructure.
A few things stand out that the Domino's press release doesn't address:
No mention of upstream fire timing control. The updated Tracker tells guests when food will be ready. What's less clear is whether the system controls when orders release to the kitchen based on live throughput and actual driver arrival signals. Accurate prediction is valuable. Controlling the outcome is better.
No discussion of food dwell time. One of the most operationally meaningful metrics in off-premise quality is how long food sits between completion and pickup. Better timing estimates help guests plan their arrival. But the real win — the one that shows up in food quality scores, repeat visits, and revenue — is reducing that gap operationally. That requires live KDS integration, not just ML-based prediction.
The proprietary stack is both a moat and an obligation. DomOS is genuinely impressive. It's also a permanent maintenance and funding commitment. For Domino's, that's fine. For the vast majority of restaurant brands, owning and evolving a custom operating platform is not a viable model — and it shouldn't have to be.
If you're reading this and thinking "we'd love to have what Domino's just announced" — you can. The capability is commercially available, and it doesn't require building a proprietary operating system to get there.
If you're still relying on static quote times in your ordering platform or manual throttling at the POS, here's what that's costing you: food sitting at expo drives up waste, degrades food quality scores on delivery platforms, and directly suppresses repeat visit rates. Across the brands we've analyzed, the median brand with 200+ locations has north of $1 million in annual revenue tied to timing-related guest complaints alone.
We integrate directly with your existing KDS with no additional hardware or changes to kitchen workflow. The first step we take with every new brand is a read-only fleet assessment: no operational changes, no hardware, nothing that touches the line. We surface baseline data on wait times by location and daypart, food dwell time at expo, kitchen performance variability, and its correlation to your guest sentiment signals. Most brands don't currently have this data in one place. It's a zero-risk way to see exactly where the pickup experience is breaking down and what it's costing you — before committing to anything.
Domino's Tracker announcement is great news for guests who order from Domino's. It's also the clearest market signal yet that real-time kitchen intelligence is no longer a nice-to-have for off-premise operations. It's the standard. The question is whether you spend the next 18 years building toward it, or start closing that gap this quarter.
Ready to see what your locations actually look like?
Start with our zero-risk fleet assessment — no hardware, no operational changes, no commitment.
Book a Demo → Read the FAQKevin Pidduck is Co-Founder and CTO of Curbit, the real-time order orchestration platform for multi-unit restaurants. Before Curbit, Kevin was founder and CEO of a vacation rental technology platform. He and co-founder Scott Siegel built Curbit to give every restaurant brand access to the real-time kitchen intelligence that has historically only been available to operators large enough to build it themselves.
#RestaurantTech #OrderOrchestration #KitchenIntelligence #OffPremise #Curbit #HappyHandoffs