Questions, answered

Click Get started, then use Proto to configure Restaurant + POS + Inventory + Delivery for your business. Begin with one service location, a small active menu and an order that the kitchen can prepare and serve during a pilot.

Each kitchen ticket points to a meal order. The order’s meal lines show the requested items and portions, while the ticket holds the service details and revision for review.

Yes. Preparation time and served portions sit on the meal line as separate facts. The team can inspect the difference during a service issue.

Ingredients and meal lines carry allergen declarations. Check the active ingredient, approved recipe and specific meal line before accepting or preparing the order.

Recipes have revision, approval and effective-date information. Record the chosen recipe code and revision with order evidence before introducing a later recipe version.

Kitchen Supervisor reviews the submitted revision and records a decision. Completion follows the authorized release effects.

Ingredient movements carry signed quantities, units, source meal lines and operation keys. Record waste separately so it can be explained beside preparation and served portions.

A fulfillment event marked Delivered holds the product, quantity, occurrence time and external event identity. Compare it with the parent order and earlier events.

Payment evidence records provider authorization, capture, refund and void events with a verification state. Finance Reviewer compares that evidence with the actual served scope and prior receipts.

Inspect its operation receipt, expected revision and linked effects before repeating an action. The exception queue helps the team locate results needing investigation.