Dira Command · Operations and administration
Your restaurant network, in focus.
Dira Command gives operations one view from the whole network down to a single order's event trace. Exceptions, channel controls, users, roles and audit history live in the same place, so everyone running the network works from one set of facts.
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
Running a network from five dashboards.
Every marketplace, POS and store tool has its own portal. Operations teams end up stitching the picture together while the lunch rush is already underway.
No single view of the network
Which stores are paused, busy or offline lives in different portals. Nobody sees all of it at once.
Exceptions surface late
A failed POS injection or an unconfirmed 86 is often found by a guest complaint, not by the team that owns it.
Ownership is unclear
When an issue appears, it is hard to tell who is on it, what was tried and whether it is fixed.
Changes leave no trail
Pauses, menu publishes and permission edits happen in many places, so explaining a bad hour means asking around.
Everything operations needs, in one console.
Command reads the same canonical orders, store state and event history as every other Dira product. What it shows is what actually happened.
Multi-location operations board
See every store's channel state, busy mode, pauses and open exceptions on one board, grouped by region or store group.
Region · store group · store
Order and store search
Find any order by ID, channel or store and open its full event trace, from webhook received to courier handoff.
Error queue with replay
Failed POS injections, menu mismatches and unconfirmed availability changes land in one queue. Assign an owner, replay the order or mark it handled.
Assign · replay · resolve
Real-time connection monitoring
Watch marketplace adapters and store POS connections as they report in. Late heartbeats and degraded POS states show up before orders back up.
Roles and audit history
Give store crews, managers, regional ops, finance and admins exactly the access they need. Every change records who made it and when.
Role-based access, store-scoped where needed
Analytics and channel profitability
Track operational KPIs by store and channel, and see channel profitability beside operations using the data Dira Reconcile matches.
Network drill-down
From the whole network to one order in four clicks.
Start with regions, open a store, pick an order and read its trace. Each level carries the counts and states that explain the one above it.
64
3
1 / 2
Select a region, then a store, then an order.
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
Counts you can open
Every number on the board leads to the stores and orders behind it.
One trace per order
Webhook, mapping, acceptance, POS and handoff events in the order they happened.
State, not screenshots
Busy, paused and POS degraded come from the stores themselves, not from a manual status board.
Every exception has an owner.
Problems from orders, menus, channels and POS connections arrive in one queue. Assign them, act on them and close them, with the history kept on each one.
- Raised by
- Dira Connect, Catalog, Bridge and Store, as events on the canonical order or store.
- Carries
- The store, channel, order or menu version involved, and what was already tried.
- Actions
- Replay to POS, mark manually entered, republish, resend availability or resume a channel.
- Closes with
- The person, the action and the time, kept in audit history.
POS injection failed
DR-48212 · Legacy WestStore controller timeout. Retry 2 of 5 failed. Store alerted with manual entry available.
OWNER
ACTIVITY
- Raised 3 min ago. No activity yet.
Administration
Access that fits the job. A record of every change.
Roles decide who can pause a channel, replay an order or publish a menu. Toggle a permission in the sample and watch it land in the audit history.
- Turn on busy modeOwn store
- Pause channelsOwn store
- Mark items unavailableOwn store
- Replay orders to POSAssigned stores
- Publish menusStore groups
- Resolve payout exceptionsAll stores
- Manage users and rolesNetwork
- 11:31Marked DR-48174 manually entered at Legacy WestL. Brandt · Regional ops, North · Orders
- 10:58Paused store · reason StaffingS. Ruiz · Store manager, Deep Ellum · Channels
- 10:34Paused Grubhub · reason Prep backlogD. Okafor · Store manager, Montrose · Channels
- 10:12Published lunch menu v14 to CentralK. Moreau · Admin · Menus
- 09:40Added J. Ellis to FinanceK. Moreau · Admin · Access
Roles
Store crew, store managers, regional ops, finance and admins each get their own permissions, scoped to a store, a group of stores or the whole network.
Audit history
Pauses, replays, menu publishes and permission changes are recorded with the person, the scope and the time, and can be filtered by type.
Built on the same core as every Dira product.
Command is a React console on the shared canonical order model, so the board, the queue and the audit history agree with each other.
- Console
- React enterprise console, served from the same platform as the store app and the other Dira consoles.
- Data model
- Canonical orders, store identity, catalog and event history in PostgreSQL logical schemas, with an event/outbox model.
- Channels
- Uber Eats is live. DoorDash and Grubhub adapters are in development, and appear in Command as they connect.
- Monitoring
- Marketplace adapters and store POS connections report state, so late heartbeats and degraded POS show per store.
- Replay
- Failed orders replay from the error queue through Dira Bridge. Idempotent processing keeps a replay from creating a duplicate order.
- APIs
- Strict contracts described in OpenAPI 3.1, behind adapter boundaries that separate marketplaces, POS and infrastructure.
- Access and audit
- Role-based access scoped to store, store group or network. Operational and administrative changes are written to audit history.
- Deployment
- Dockerized services with a Google Cloud reference deployment using Cloud Run, Pub/Sub, Cloud SQL, Cloud Storage and Redis.
Questions about Dira Command
See your network the way Command does.
We'll walk a sample network from region to order trace, including the exception queue and audit history.