Questions, answered

Click Get started, then use Proto to configure Restaurant POS System for your business. Start with one service location, an active menu and a representative meal order from acceptance through kitchen review and service.

Service Lead checks the menu, portions, allergens and service capacity, then records acceptance and its actual time on the order.

Kitchen Lead prepares a ticket from the accepted order. Kitchen Supervisor reviews the submitted ticket revision before release.

A changed ticket needs review of its current submitted revision. Earlier decisions remain with the revision they covered.

Kitchen Lead uses the approved recipe revision for the product and records actual preparation on the meal line. Ingredient movements capture consumption and waste.

Record the actual served portions on each meal line. A correction reviews the remaining eligible scope while preserving the served history.

Finance Reviewer compares the provider-issued refund receipt with the parent order, provider event identity and amount before verifying it.

Operations Reviewer reads the operation receipt and linked effects first. The action is complete only when the expected effects match the recorded outcome.

Fulfillment events keep actual event type, quantity, time and external event identity against the meal order and product. Agree the delivery connection during setup.

Operations Overview has an exception queue that opens the underlying record. Operation Exceptions shows failed and review-needed receipts for follow-up.