One order, from the menu to the kitchen.

Plan a restaurant menu, mobile ordering companion and kitchen desktop workspace around shared order records, account scopes and test Checkout.

Review the prepared brief in Studio. A build starts when you send it.

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.

Give each screen its own job.

These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.

Plan the records and their owners.

Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.

CollectionSuggested fieldsAccess to decide
menu_itemsname, modifiers, availability, price_referenceCustomer-readable catalog and authorized staff updates.
ordersowner, line_items, pickup_time, statusPrivate customer status and explicitly granted kitchen operations.

Verify the outcome, then expand.

From this brief to your first version.

  1. Review the proposed workflow

    Start with this editable blueprint brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.

  2. Build and check the result

    Review the isolated preview and execute the checks listed on this page. Begin with Restaurant story, hours, menu, order selection and customer status. Resolve missing service setup and save verified progress before expanding the scope.

  3. Connect or export when ready

    Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.

Make the starting point your own.

Name your project and review the brief. Building starts when you send it.

Start at $0. Source unlock $4.99 once per project.Compare $10 Plus, $20 Pro and $60 Ultra monthly plans

Questions before you build.

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.

Read the public Markdown reference