FAQs
Find answers and general information quickly about Curbit.
What is Curbit?
Curbit is a real-time order orchestration platform for multi-unit restaurants. It connects directly to a restaurant's Kitchen Display System (KDS) to read live kitchen speed of service, then uses that data to control when digital orders fire to the kitchen, generate accurate pickup time quotes, and send automated updates to guests and delivery drivers. The result is food that's ready exactly when it's needed — not sitting at expo, not late.
What problem does Curbit solve?
When digital orders fire to the kitchen too early, food sits and loses quality before it's picked up. When they fire too late, guests and drivers wait. Most restaurants rely on static quote times and manual throttling that don't reflect what's actually happening in the kitchen right now. Curbit closes that loop — connecting real-time kitchen data to the ordering channel so timing is always grounded in actual kitchen capacity.
How is Curbit different from the quote time settings in my ordering platform?
Ordering platforms set quote times based on static rules or averages — they don't have visibility into your kitchen. Curbit reads live KDS data and dynamically adjusts both the quoted pickup time and the moment the order fires to the kitchen based on what's actually happening on the line right now. It's the difference between an estimate and a real-time, capacity-aware commitment.
How is Curbit different from POS-based throttling?
A POS records what has happened — it's a transaction system. Throttling through a POS is a manual override, not an intelligent response to kitchen conditions. Curbit operates in real time, reading active ticket flow from the KDS and automatically adjusting order release timing without any manual intervention. No one on the line has to touch anything.
Does Curbit require new hardware?
No. Curbit works in the background through existing systems. Kitchen staff continue using their KDS exactly as they do today. The orchestration happens upstream — between the ordering platform and the kitchen — so there's no change to the line workflow.
What systems does Curbit integrate with?
Curbit integrates with major KDS providers including QSR Automations, as well as online ordering platforms including Olo, POS systems including Toast, NCR Aloha, Oracle, and Brink (PAR), loyalty platforms including Paytronix and Thanx, and SMS providers including Twilio for guest and driver messaging. A full list of supported integrations is available on request.
How does Curbit know when to fire an order to the kitchen?
Curbit reads every ticket moving through the KDS in real time — when it fires, how it progresses, and when it completes. From that continuous stream, it builds a live model of kitchen speed of service: how long items actually take to make right now, how the line is absorbing demand, and where capacity exists. It uses that model to calculate the precise moment to release each order so it's ready at the promised pickup time.
What is the Curbit Goldilocks Zone?
The Goldilocks Zone is Curbit's term for the window in which an order should complete — not too early (so food doesn't sit and lose quality) and not too late (so guests and drivers aren't waiting). Curbit's orchestration engine is designed to keep every order completing within this window by dynamically adjusting fire timing and quote times based on live kitchen data.
How does Curbit communicate with guests and delivery drivers?
Curbit sends automated SMS messages to guests and delivery drivers at key moments — order confirmation, when the order is being prepared, and when it's ready for pickup. If timing changes, Curbit updates them before they arrive. This reduces lobby congestion, eliminates unnecessary calls to the restaurant, and improves the pickup experience on both sides of the counter.
How long does implementation take?
Curbit's plug-and-play integration model is designed to minimize IT lift. Because it works via secure cloud-based APIs with existing KDS and ordering platforms, implementation does not require custom development or hardware installation. Specific timelines vary by tech stack, but the model is designed for low friction.
What results have Curbit customers seen?
Curbit customers have seen up to 84% improvement in order timing accuracy, 22% increase in repeat purchase rates, and 11% improvement in Google review ratings. Across its customer base, Curbit maintains a 100% customer retention rate. Customers include Cava, Dave's Hot Chicken, Smashburger, Jollibee, Mellow Mushroom, Starbird, Postino, and Boudin Bakery, among others.
How does Curbit start working with a new restaurant brand?
The first step is a read-only fleet assessment — no operational changes, no new hardware, nothing that touches the line. Curbit coordinates access to KDS and ordering channel data to produce a baseline view of where the pickup experience is breaking down and what it's costing: wait times by location and daypart, food dwell time at expo, kitchen performance variability, and correlation to guest sentiment signals including Google ratings. The assessment surfaces data most brands don't currently have, and becomes the foundation for any decision about what to activate and where to start.
Is Curbit right for my restaurant if I'm not running high digital order volume yet?
Curbit is built for multi-unit brands with active digital ordering channels — takeout, delivery, or both. If your operation is actively managing digital orders and experiencing variability in timing, wait times, or guest satisfaction, Curbit is likely relevant. The fleet assessment is a zero-risk way to find out what the data actually shows before committing to anything.
Who do I contact to learn more?
You can reach Curbit at info@curbit.com or by calling (805) 317-4484. To schedule a demo, visit curbit.com/book-demo.