The connected restaurant platform
Every order.One connected restaurant.
Dira unifies delivery marketplaces, menus, POS systems, store operations, and finance in one digital platform, built for restaurant brands that operate at scale.
484
Across 3 channels
5
2 need action
5 / 7
1 paused · 1 degraded
17 / 21
2 paused · 2 attention
DR-48212
DoorDash · Legacy West · $19.15
- Webhook received11:42:03Signature verified
- Canonical order created11:42:03Idempotency key matched: new
- Menu mapping validated11:42:042 items, modifiers resolved
- Accepted11:42:05Status synced to marketplace
- POS injection failed11:42:06Store controller timeout
- Retry 1 of 511:42:36Backoff 30s
- Retry 2 of 511:43:36Store notified · manual entry available
Digital demand is growing. Operational complexity shouldn't.
Orders, menus, availability, store systems, and settlements often live in different places. Dira creates one connected layer across them, so brands can run digital commerce with more clarity and control.
Orders move together.
Every marketplace order follows one model from intake to the kitchen, so nobody re-keys a ticket or chases a tablet.
Stores stay in sync.
Menus, prices, hours and availability are set once and reach every channel and location the same way.
Performance becomes visible.
Operations and finance read the same order history, from the first webhook to the final payout line.
One order. Connected end to end.
Follow a single order from the marketplace to the payout. Choose a channel, click any step, or see what happens when a POS stops answering.
Dira Connect
Connect verifies the webhook, removes duplicates with an idempotency key and converts the order into Dira's canonical model. Menu mapping is checked before the order is accepted.
Explore Dira Connect- 11:42:03Webhook receivedSignature verifiedSignature verifiedsuccess
- 11:42:03Canonical order createdDR-48213 · idempotency key newDR-48213 · idempotency key newneutral
- 11:42:04Menu mapping validated3 items, modifiers resolved3 items, modifiers resolvedsuccess
- 11:42:05AcceptedStatus synced to Uber EatsStatus synced to Uber Eatssuccess
A unified order model connects intake, execution, visibility, and reconciliation. Illustrative flow · sample data.
Built for every moment behind a digital order.
Six products share one core: canonical orders, catalog, store identity, event history, adapters and controls. Use them together or start where the friction is.
Every delivery channel, one dependable order flow.
Connect receives marketplace orders, verifies them and turns each one into a single canonical order. Acceptance, status, cancellations and retries stay in sync without anyone re-keying a ticket.
- Webhook validation and idempotent processing
- Canonical event history for every order
- Scheduled orders and exception queues
Uber Eats integrated. DoorDash and Grubhub adapters in development, targeted next.
Explore Dira ConnectDR-48212
DoorDash · Legacy West
EVENT HISTORY
- 11:42:03Webhook receivedSignature verified
- 11:42:03Canonical order createdIdempotency key matched: new
- 11:42:04Menu mapping validated2 items, modifiers resolved
- 11:42:05AcceptedStatus synced to marketplace
- 11:42:06POS injection failedStore controller timeout
- 11:42:36Retry 1 of 5Backoff 30s
- 11:43:36Retry 2 of 5Store notified · manual entry available
- Toggle to mark an item 86 across every channel.
Classic chicken sandwich
itm-1042v42 draft vs v41 live
- 3 price changes · 1 new item · 1 item retired
- Approved by menu ops · awaiting publish
One catalog. Every menu. Every location.
Build items, modifiers, combos and dayparts once, then price them by channel and store group. Every change is versioned, validated and scheduled before it reaches a marketplace.
- Store-group and channel pricing
- Version history, approval and rollback
- Availability and 86 control in one place
From digital order to kitchen, without friction.
Bridge injects each order into the restaurant's POS through a gateway that keeps every POS behind its own adapter. When a POS stops answering, orders retry, the store is alerted and the order stays traceable until it is recovered.
- Order injection with tender mapping
- Retries, backoff and degraded mode
- Cancel and void sent to the kitchen
- +0msCANONICALOrder DR-48213 ready for POS3 items · 4 modifiers · prepaid
- +38msGATEWAYMapped to POS menu IDsTender: marketplace prepaid
- +212msADAPTERCheck openedPOS check #2041 · store S-0142
- +240msKITCHENFired to kitchenFire time aligned to courier ETA
- +9m 14sSTATUSReady event receivedSynced to marketplace and Store
Know what every order earned.
Reconcile imports marketplace payout reports and matches every line to the order behind it. Fees, adjustments and exceptions come with evidence before finance closes the period.
- Order-level payout matching
- Commission and adjustment tracking
- Journal export for your finance stack
$12,480.20
−$3,108.42
−$96.10
$9,275.68
- Close checklist: import done · matching done · review exceptions · export journal
Commission above contract rate
DR-47790- Expected
- Commission $6.12
- Reported
- Commission $7.34
EVIDENCE
- Contract rate on file for this store group
- Payout line 118 · order subtotal $24.48
- Canonical order timeline
New1
- UE#4821
Jordan M.
- 2× Classic sandwich
- 1× Large fries
Courier 6 min
Accept
In progress2
- DD#4819
Priya S.
- 1× Spicy sandwich
- 1× Peach shake
Courier 9 min
Entered manually · POS error
- GH#4817
Alex R.
- 3× Taquito combo
Courier 2 min
Ready1
- UE#4812
Sam T.
- 1× Classic sandwich
Courier arrived
Everything the store needs. Nothing it doesn't.
A tablet workspace gives each team its live order queue across every channel. Staff pause a channel, switch on busy mode or mark an item unavailable in one tap.
- Real-time order queue with alerts
- Manual entry when the POS is down
- Store and channel pause, busy mode
One clear view across your restaurant network.
Command brings stores, channels and orders into one operational view, from the whole network down to a single order. Exceptions arrive with context, and every change is recorded.
- Network to store to order drill-down
- Error queue with replay
- Roles and audit history
Command is where the other five meet. The next section shows how operations teams use it to find, act on and record what happened across the network.
A clearer view of every restaurant.
Command turns a network of stores, channels and systems into one place to work. Exceptions come with context, and every action leaves a record.
Explore Dira CommandOperational clarity
Network, region, store and order in one place, with the same status the store and the marketplace see.
Actionable exceptions
Each exception arrives with its evidence and the next step: replay, reassign or resolve.
Auditability
Every pause, publish, replay and override is recorded with who did it and when.
POS injection failed
Legacy West · S-0217 · DR-48212
- Last error
- Store controller timeout
- Retries
- 2 of 5 · backoff 30s
- Store notified
- 11:43:36 · manual entry offered
- System11:43:36
EX-3107 retry 2 of 5 scheduled
- M. Ortiz11:38:02
Paused Grubhub at Montrose · reason: staffing
- System11:20:45
EX-3098 duplicate webhook ignored
- J. Reyes09:00:00
Published catalog v42 to store group Gulf
Connect to the systems restaurants already run.
Built around adapters and documented interfaces, so a new channel doesn't require rebuilding your core.
See every integrationPOS
03- POS gatewayPlatform capability
- Brand POS connectorsScoped per deployment
- Store tablet appPlatform capability
Infrastructure
03- Google CloudReference deployment
- PostgreSQLPlatform capability
- Dira APIsPlatform capability
Finance / Analytics
03- Marketplace payout reportsPlatform capability
- Journal exportPlatform capability
- Operational analyticsPlatform capability
- Integrated
- Built into the current Dira release and in use on the platform.
- In development
- Adapter in active development and targeted next. Not yet live.
- Scoped per deployment
- Connected through Dira's adapter model and confirmed for each brand's systems during onboarding.
- Platform capability
- A Dira platform feature available to every deployment.
Marketplace names identify the services Dira connects to. They do not imply a partnership or certification.
Infrastructure you can build your future on.
Dira is built as a set of services around one shared core, with adapters at the edges. That shape is what lets new channels and systems arrive without a rebuild.
Read the architectureEvery capability sits behind strict, documented contracts. The store app, the consoles and every integration use the same interfaces you can.
- OpenAPI 3.1 contracts
- NestJS services in TypeScript
- Contract tests in CI
Reference deployment on Google Cloud. Other environments are evaluated and contracted separately.
Each marketplace and POS sits behind its own adapter, so a change at the edge never reaches the core.
Cloud Run · Pub/Sub · Cloud SQL · Cloud Storage · Redis · Docker
Designed around the realities of restaurant operations.
The same platform, arranged around the people who run it: operators, store teams, IT and finance.
Enterprise QSR
Govern channels, menus and change control across a large network, with roles, approvals and an audit trail IT can stand behind.
CONNECT · BRIDGE · CATALOG · COMMANDMulti-location chains
Set pricing, hours and availability centrally for each store group, and give every location a clear way to run its own day.
CATALOG · STORE · COMMANDDelivery and off-premise operations
Keep marketplace orders flowing into the kitchen, handle pauses and busy periods, and recover cleanly when a POS goes quiet.
CONNECT · BRIDGE · STOREFinance and reconciliation
Match marketplace payouts to orders, see fees and adjustments line by line, and export a clean journal to your finance stack.
RECONCILE · COMMAND
Make every digital order part of a better operation.
See how Dira connects your channels, systems, and teams.