What hardware does Dira Store need?

Dira Store is a React app that runs in a modern browser and installs on store tablets as a progressive web app. Layouts are designed for landscape tablets read at counter distance, and device choice is agreed per deployment.

Does it replace the marketplace tablets?

Orders from connected marketplaces arrive in one Dira Store queue, so crews work those channels from one screen. Uber Eats is live today; DoorDash and Grubhub adapters are in development. Whether a marketplace device can be retired depends on each channel's integration and your agreement with it.

What happens if the store loses its internet connection?

Store actions are offline-tolerant. Taps queue on the device and sync when the connection returns, and Dira Command shows each store's connection state to your operations team.

What happens when an order doesn't reach the POS?

Dira Bridge retries the injection and raises an alert in Dira Store with the full ticket. The crew can key the order into the POS by hand and record the check number, which stops retries and keeps the order's event history complete.

Who can pause a channel or turn on busy mode?

Permissions come from roles managed in Dira Command. You decide which store roles can pause channels, extend prep times or mark items unavailable, and every change is recorded with the person and the reason.

Does marking an item 86 update every menu?

Yes. The change writes to Dira Catalog for that store and publishes to each live channel. Restoring the item works the same way.

Dira Store · In-store order operations

Give every store a clearer way to work.

Dira Store puts every marketplace order, prep timer and channel control on one tablet screen. Crews accept, cook and hand off orders in one place, and every tap syncs back to the channel and the rest of Dira.

Book a demo See how orders reach the POS

South LamarS-0142 Offline actions queue locally

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

Illustrative interface · sample data · Dira Store on a 10-inch landscape tablet

Busy stores don't need more screens.

Store teams absorb the cost of every disconnected system above them. Most of it shows up at the counter, at the worst possible moment.

A tablet for every marketplace

Each channel brings its own device, chime and workflow. Crews end up watching screens instead of food.

Pausing a channel takes a phone call

When the kitchen falls behind, slowing intake often means calling support or waiting for a manager to log in somewhere else.

Failed POS tickets go unnoticed

If an order never reaches the kitchen, the first sign is often a courier at the counter asking for food nobody started.

Sold-out items keep selling

An item runs out at lunch but stays live on every menu until someone updates each channel by hand.

Everything the store needs. Nothing it doesn't.

Six controls cover the moments that decide whether a digital order leaves the counter right.

One queue for every channel

Orders from each connected marketplace land in one real-time queue, grouped into New, In progress and Ready, with the source channel and courier timing on every ticket.

Real-time queue · audible alert on new orders

Accept, prep and hand off

Crews accept or reject with a reason, track prep against the quoted time, and mark orders ready and picked up. Each state change goes back to the marketplace through Dira Connect.

Status events: accepted · rejected · ready · picked up

Busy mode

Add prep time across every live channel with one tap when the kitchen falls behind. Turn it off, or let it end on a timer, when the rush clears.

Channel and store pause

Pause one marketplace or the whole store with a reason and a resume time. Operations sees the change in Dira Command, and the audit history records who made it.

Item availability from the counter

Mark an item out once and Dira Catalog takes it off every live channel for that store. Bring it back the same way.

One tap to 86 · one tap to restore

POS alerts and manual entry

When an order can't reach the POS, the store gets an alert with the full ticket. Crews key it in, record the check number, and retries stop.

Manual entry closes the Dira Bridge retry loop

Follow one order from chime to handoff.

Accept, prep, ready, picked up. Each tap moves the ticket on the counter and sends the matching status back to the marketplace. Try it on the sample order.

diraStore/ South Lamar · Order queue

NEW
IN PREP
READY
PICKED UP

Uber Eats#4821New

Jordan M.

2×Classic sandwichNo pickles on one
1×Large fries
1×LemonadeLight ice

Courier 6 min · quote 12 min prep

STATUS SYNCDR-48213

Order received11:42:03Uber Eats · canonical order created
Store alerted11:42:04Chime on tablet · waiting for crew

Every tap on the ticket becomes an event on the canonical order, visible in Dira Command.

Illustrative interface · sample data

Reject with a reason

If an item is gone or the kitchen is full, the crew picks a reason and the marketplace gets it with the rejection.

Prep against a promise

Accepting starts the prep timer against the quoted time, so the crew sees which ticket is closest to late.

One history, everywhere

The same events appear on the order's trace in Dira Command, so support and the store read the same story.

Control the rush from the counter.

Three controls for the moments when the kitchen is under pressure. Each takes a few taps, and each one shows up in Dira Command.

diraStore/ South Lamar · Busy mode

QUOTED PREP TIME

22min

Busy · +10 min

Add prep time

Ends

INCOMING ORDERSREADY BY

UE#4823Placed 11:4412:06
DD#4824Placed 11:4612:08
UE#4826Placed 11:4712:09

Applies to every live channel for South Lamar. Returns to 12 min at 12:14.