# Restaurant Website, Mobile Ordering App and Desktop Order Queue

Canonical: https://uvilno.com/use-cases/restaurant-ordering-and-pos
Updated: 2026-11-07

Start with a restaurant website and a clear menu-to-order journey. Link a mobile customer companion and a desktop kitchen queue through the managed ecosystem backend. Specify order statuses, customer permissions and kitchen authority explicitly. Use test Checkout while validating the flow, and confirm production payments and POS requirements separately.

## Make the handoff visible

The customer needs a readable menu, modifier selection, an order summary and an honest fulfillment status. The kitchen needs a queue with received, preparing and ready actions. Both interfaces should read the same authorized order record after a committed change, with reconnect handling for interrupted service.

## Scope a POS release carefully

A desktop order queue is a useful first operational tool. Hardware terminals, card-present payments, receipt printers, tax rules and inventory integration add distinct requirements. Before taking live orders, test duplicate submissions, unavailable menu items, cancellations and who can perform each staff action.

## Platform plan

| Platform | Generated experience |
| --- | --- |
| web | Restaurant story, hours, menu, order selection and customer status. |
| mobile | A touch-first menu and pickup-status companion. |
| desktop | A kitchen queue with authorized preparation and ready actions. |

## Declared collections

| Collection | Fields | Access |
| --- | --- | --- |
| menu_items | name, modifiers, availability, price_reference | Customer-readable catalog and authorized staff updates. |
| orders | owner, line_items, pickup_time, status | Private customer status and explicitly granted kitchen operations. |

## Acceptance checks

- Send an order and verify it appears in the authorized kitchen queue.
- Change preparation status and observe the customer's refreshed view.
- Prevent duplicate submission when a network request is retried.
- Check order privacy and staff privileges using separate app accounts.

## Setup and launch boundaries

- A generated order queue does not supply payment-terminal or printer integration by itself.
- Live ordering, taxes and card-present payments need their own configured and tested release.

## Editable starting brief

Plan a restaurant ecosystem with a public menu and web ordering flow, a touch-first customer companion and a desktop kitchen queue. Start with a verified website workflow before generating companions. Declare menu_items and orders collections with customer ownership and explicit staff authority. Preserve modifier choices and avoid duplicate orders on retry. Include received, preparing, ready and cancelled states. Use only a clearly labeled managed Stripe test Checkout until live payment requirements are implemented and verified. Link companions to the same records through App connections and test a full kitchen-status handoff.

## Common questions

### Is this a complete certified POS system?

This blueprint scopes the web order flow and desktop kitchen workspace. Terminal hardware, printers, taxation and any regulatory requirements require separate evaluation and integration.

### Can a customer see every order in the database?

They should see only their authorized order records. Staff access must be granted explicitly and verified with different app accounts.
