How does Dira control who can change menus, prices and store settings?

Roles define what each person can draft, approve and publish, scoped to brands, regions or store groups. Every change records who made it, who approved it and which version it replaced.

Can we roll a change out to part of the network first?

Yes. Changes publish by store group, so a pilot group can go first and later waves follow on a schedule. Rollback restores the previous version to any wave.

Which marketplaces and POS systems does Dira connect to?

Uber Eats is integrated. DoorDash and Grubhub adapters are in development and targeted next. POS connectivity runs through the Dira Bridge gateway, and specific POS connectors are scoped and validated for each deployment.

How is Dira deployed?

Dira runs as Dockerized Node.js and NestJS services with PostgreSQL. The reference deployment is on Google Cloud: Cloud Run, Pub/Sub, Cloud SQL, Cloud Storage and Redis. An Azure deployment can be evaluated as a separately contracted option.

What happens when a store's POS goes down?

Bridge holds the order, retries with backoff and marks the store as degraded on the network board. The store team can enter the order by hand, and the event history records both paths so nothing is entered twice.

Enterprise QSR

Govern every store, channel and change from one place.

Dira gives large quick-service brands one governed platform for marketplace orders, menus, POS connectivity and store operations. Roles, staged rollouts and a complete audit history keep every change across the network under control.

Book a demo Read the architecture

diraCommand/ Change control

Role: Brand approver

CHANGE REQUESTSTHIS WEEK

Breakfast pricing update

CH-1186 · Catalog · v42

Central metro
All channels
Prices only

APPROVALS

Menu editorDrafted Mon 09:12
Brand approverApproved Mon 14:30
Regional ops leadConfirmed waves Mon 16:05

ROLLOUT BY STORE GROUP

Pilot group6 storesPublished
Central wave 124 storesPublishing
Central wave 231 storesScheduled Wed 05:00

AUDIT HISTORY

Tue 05:00Published v42 to Pilot group · channel read-back matchedSystem
Mon 16:05Set rollout waves for Central metroRegional ops lead
Mon 14:30Approved 14 price changesBrand approver
Mon 09:12Created draft v42 from v41Menu editor

Illustrative interface · sample data

The situation

Built for: Quick-service brands running many stores across several delivery channels
Teams: IT, digital commerce, restaurant operations, finance and store teams
Marketplaces: Uber Eats integrated. DoorDash and Grubhub in development, targeted next.

Scale multiplies every decision.

A large quick-service network makes a constant stream of small digital decisions. A price, an opening hour, a sold-out item or a paused store each touches a marketplace, a menu, a POS and a store team. Most brands built those connections one channel at a time.

The cost shows up as lost control. Changes are hard to stage, local exceptions are hard to see, and every incident review starts by collecting evidence from several portals. Dira gives the brand one governed layer over channels, menus, stores and their history.

Built for: Quick-service brands running many stores across several delivery channels
Teams: IT, digital commerce, restaurant operations, finance and store teams
Marketplaces: Uber Eats integrated. DoorDash and Grubhub in development, targeted next.

Where large networks lose control

The trouble rarely comes from one system. It comes from the gaps between them, multiplied by every store.

Changes reach stores unevenly

A price or menu update lands in some stores and channels but not others. Nobody can say which until a guest or a store reports it.

Local exceptions become the norm

Store-level overrides pile up outside any policy. A few months later, no one knows which differences were intended.

Channel integrity is hard to prove

What the marketplace shows, what the POS rings up and what the store can make drift apart, one change at a time.

Audit questions take days

When something goes wrong, the answer sits across marketplace portals, POS reports and email threads.

How Dira connects the workflow

Follow one network-wide change from draft to every store, including the exception that arrives in the middle of it.

diraCatalog/ Core menu / v42 draft
Mon 09:12
Draft v42 · Central metro
14 price changes compared with v41
ITEMV41 TO V42
Breakfast taco plateAll channels$8.49 → $8.79
Sausage biscuitAll channels$3.99 → $4.19
Morning comboUber Eats channel price$9.79 → $10.09
Hash brown sticksNo change · inherited from brand$2.29
Draft saved. Nothing reaches a store or channel until it is approved and scheduled.
Request approvalCompare versions
Illustrative interface · sample data

diraCatalog/ Core menu / v42 draft

Mon 09:12

Draft v42 · Central metro

14 price changes compared with v41

ITEMV41 TO V42

Breakfast taco plateAll channels$8.49 → $8.79
Sausage biscuitAll channels$3.99 → $4.19
Morning comboUber Eats channel price$9.79 → $10.09
Hash brown sticksNo change · inherited from brand$2.29

Draft saved. Nothing reaches a store or channel until it is approved and scheduled.

Request approvalCompare versions

Illustrative interface · sample data

For IT and architecture

An adapter architecture IT can stand behind.

Every marketplace and every POS sits behind its own adapter. The core keeps one model of orders, menus and stores, so adding a channel or changing a store system never means rebuilding the platform.

CHANNEL ADAPTERS

Uber EatsOrders in, menus and status outIntegrated
DoorDashAdapter in developmentTargeted next
GrubhubAdapter in developmentTargeted next

DIRA CORE

Canonical ordersOne order model for every channel
Catalog and store identityMenus, prices, hours, store groups
Event history and outboxEvery state change recorded once
Roles and auditWho changed what, approved by whom
Error queue and replayFailed steps held, inspected, replayed

SYSTEM ADAPTERS

POS gatewayConnectors scoped and validated per deployment
Dira Store appStore tablets, pause, busy mode, 86
Enterprise consolesCommand, Catalog and Reconcile
Finance exportJournals into your finance process

Uber Eats is integrated. DoorDash and Grubhub adapters are in development and targeted next.

Contracts: Strict OpenAPI 3.1 contracts between services and adapters, checked by automated contract tests in CI.
Data: PostgreSQL with logical schemas and an outbox, so every state change becomes an event you can trace and replay.
Deployment: Dockerized Node.js and NestJS services. Google Cloud reference deployment on Cloud Run, Pub/Sub, Cloud SQL, Cloud Storage and Redis.
Resilience: Idempotent event handling, retries with backoff and degraded store modes, exercised by load and chaos testing.

Read the architecture See integration status

A role for every team

Each team works on the part of the network it is responsible for, with permissions to match.

IT and integration
Own the adapters, contracts and deployment. Validate POS connectors store by store, watch connection health and replay failed events.
- Command · Connections
- Bridge gateway
- OpenAPI contracts
Digital commerce
Run the marketplace channels as one program: menus, pricing by store group and channel, and publishing schedules.
- Catalog
- Connect
Restaurant operations
See every store's status, work exceptions by region and approve local changes such as hours or channel pauses.
- Command
- Store
Finance
Read order history and channel performance without asking for exports, and match payouts to orders.
- Reconcile
- Command · read-only
Store teams
Work incoming orders on a tablet, mark items unavailable, turn on busy mode and enter orders by hand when the POS is down.
- Dira Store

Questions enterprise teams ask

See how Dira governs a network like yours.

Bring your store groups, channels and POS landscape. We'll walk through rollout, roles and audit history on sample data.

Book a demo Talk to the team