Several brands, one kitchen, one board.

Delivery-only kitchens run more channels than seats. These are the parts of the product built for that shape.

Gloved hands lower a takeout bowl into a paper bag beside stacked boxes.

The parts of the product that do this work.

If you run more than one brand out of one room
Several brands and several locations, with each location's data kept to itself.
If orders should reach a station by channel as well as by category
Route by station, so prep, grill and expo each see only their own work, and send an order forward when your part is done.
If your channels do not all arrive from the same place
Connect the POS you already use, or type orders in by hand and use any POS at all.
If a take-out view suits your board better than a classic one
Four display modes: classic, tiled, split and a take-out view.
If a dropped connection means a missed delivery window
Orders already on the screen stay on the screen, every bump is recorded, and it syncs when the connection comes back.
Screen placement in a multi-pod kitchen An overhead floor plan. The room is deeper than it is wide, and its right-hand wall is notched twice so the space reads as a run of separate pods. Three filled rectangles stand on end against the left wall, one per pod, and a fourth lies flat against the top wall where orders are dispatched.
If you run more than one brand out of one room, one screen per pod and one at dispatch.

Everything above is on the features page, with the list of what is not built yet beside it. See every feature

What still works when the internet is out.

What keeps running in each of the three network states. The same table the features page publishes, negative cells included.
CapabilityEverything downInternet down, local network upInternet up
See orders already on the screenYesYesYes
New orders from a cloud POSNoNoYes
New orders over your local networkYesYesYes
Bump, strike, hold, prioritizeYesYesYes
Screens stay in sync with each otherYesYesYes
PrintYesYesYes
ReportingCatches up laterCatches up laterYes

What keeps running in each of the three network states. The same table the features page publishes, negative cells included.

Capability

Everything down

See orders already on the screen
Yes
New orders from a cloud POS
No
New orders over your local network
Yes
Bump, strike, hold, prioritize
Yes
Screens stay in sync with each other
Yes
Print
Yes
Reporting
Catches up later

Internet down, local network up

See orders already on the screen
Yes
New orders from a cloud POS
No
New orders over your local network
Yes
Bump, strike, hold, prioritize
Yes
Screens stay in sync with each other
Yes
Print
Yes
Reporting
Catches up later

Internet up

See orders already on the screen
Yes
New orders from a cloud POS
Yes
New orders over your local network
Yes
Bump, strike, hold, prioritize
Yes
Screens stay in sync with each other
Yes
Print
Yes
Reporting
Yes

We run these tests on every release and publish the results, failures included. None are published yet — the first land at launch. See how it handles an outage

What an operator on this kind of line would say.

We have no customers yet, so nobody has said this. The block below is a placeholder at the real size of the quote that replaces it.

PLACEHOLDER TESTIMONIAL — NOT A REAL CUSTOMER

This person does not exist and nobody said these words. MiniRestaurants has no customers yet. This block is here so the page can be built, reviewed and laid out at its real size; it is replaced by a real operator, quoted with consent on file, or it is deleted before this site is opened to search engines.

We run several brands out of one room, so the risk was always an order going out under the wrong label. Every ticket carries its brand on the board now and the packers stopped having to remember which is which.

AP Alina Petrova Operations lead, Placeholder Kitchen Collective · Not a real city

Not your kind of kitchen? The other restaurant types