Tables, courses and a kitchen that has to time them.

Full service asks more of a kitchen screen than a counter does. Here is what is in the product today, and the honest note about what is not.

A hand sets a plated duck dish on a wooden table, diners behind.

What matters here

The parts of the product that do this work.

If an appetiser has to land before a main does: Hold an order to a timer or to a clock time, and release it early by hand when the table is ready.
If one table's ticket arrives as two: Split one ticket into two, or merge two into one.
If grill, sauté and expo are separate screens: 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 a table's ticket and a take-out ticket should not turn red at the same pace: Timers change colour on your own thresholds, per order type, and the colours are colourblind-safe.
If your servers mark allergies on the ticket: Allergen highlighting is automatic, on every plan, and it cannot be switched off. It is a safety feature and we do not charge for those.

If your grill, sauté and expo are separate screens, that is three, plus one where the plates go out.

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.
Capability	Everything down	Internet down, local network up	Internet up
See orders already on the screen	Yes	Yes	Yes
New orders from a cloud POS	No	No	Yes
New orders over your local network	Yes	Yes	Yes
Bump, strike, hold, prioritize	Yes	Yes	Yes
Screens stay in sync with each other	Yes	Yes	Yes
Print	Yes	Yes	Yes
Reporting	Catches up later	Catches up later	Yes

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

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

From the pass

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.

Courses were the thing we could never keep straight on paper. Grill sees grill, expo sees the whole table, and the plates stop arriving at the wrong moment. That is the part my floor staff actually noticed.

Priya Raman Executive chef, Placeholder Table · Not a real city

Not your kind of kitchen? The other restaurant types