Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Restaurant + POS + Inventory + Delivery
- Payment provider
- Delivery partner
- Platform users
A restaurant team can keep a meal order, its lines, kitchen ticket and service destination connected from intake through service. The order records its owner, requested service time and amount.
Meal orders in one list
Kitchen Supervisor approves or rejects the submitted revision before release.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep each meal order tied to its owner, service destination, lines and requested time.
Meal orders
| Record number | Subject | Status | Serve at | Owner | Counterparty | |
|---|---|---|---|---|---|---|
| MO-65192 | Lunch delivery, Alder Street offices | Draft | 13 Oct | Elena Park | Harbor Clinic delivery desk | |
| MO-43773 | Patio dinner, party of four | Accepted | 02 Nov | Dev Shah | Bayview Lofts reception | |
| MO-37529 | Pickup order, Willow Avenue | Preparing | 04 Nov | Luca Moretti | Main dining room | |
| MO-73045 | Catering lunch, Harbor Clinic | Ready | 01 Nov | Rafiq Rahman | Alder Street office lobby | |
| MO-91706 | Dining room brunch, table 8 | Served | 22 Oct | Tariq Mensah | Main dining room |
Coordinate meal-line preparation with reviewed kitchen ticket revisions.
Approval conditions
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Private event supper, garden room | Submitted | 780 | Table 4 | 22 Oct | 35 | |
| Pickup dinner, Cedar Lane | Submitted | 90 | Table 8 | 12 Oct | 14 | |
| Pickup order, Willow Avenue | Submitted | 280 | Patio 2 | 12 Oct | 23 | |
| Private event supper, garden room | Submitted | 100 | Patio 6 | 21 Oct | 29 | |
| Dining room brunch, table 8 | Submitted | 80 | Garden 1 | 16 Oct | 19 |
Maintain products, recipe versions and ingredient quantities for the menu.
Products
| SKU | Name | Base unit | Standard price USD | Active | |
|---|---|---|---|---|---|
| BOWL-RP-01 | Roasted pepper grain bowl | each | 750 | Yes | |
| PLATE-LHC-02 | Lemon herb chicken plate | kilogram | 80 | Yes | |
| FLAT-MF-L | Mushroom flatbread, large | liter | 670 | Yes | |
| SIDE-CB-04 | Charred broccoli side | portion | 270 | Yes | |
| SOUP-SL-CUP | Spiced lentil soup, cup | gram | 730 | Yes |
Follow ingredient consumption and waste back to a meal line and operation.
Ingredients
| Ingredient code | Name | Base unit | Allergen declaration | Active | |
|---|---|---|---|---|---|
| ING-PEPPER-RED | Red bell peppers | each | Contains almonds | Yes | |
| ING-CHICKEN-THIGH | Boneless chicken thighs | kilogram | Contains wheat | Yes | |
| ING-MUSHROOM-CREM | Cremini mushrooms | liter | Contains milk | Yes | |
| ING-BROCCOLI | Broccoli crowns | portion | Contains sesame | Yes | |
| ING-LENTIL-BROWN | Brown lentils | gram | Contains soy | Yes |
Connect provider payment evidence and delivery events to each meal order.
Fulfillment events
| Parent | Product | Quantity | Event type | Occurred at | External event ID | |
|---|---|---|---|---|---|---|
| Dining room brunch, table 8 | Citrus almond cake, slice | 720 | Delivered | 27 Oct | dispatch_2026_1101 | |
| Catering lunch, Harbor Clinic | Charred broccoli side | 80 | Delivered | 14 Oct | picked_up_2026_1102 | |
| Dinner delivery, Bayview Lofts | Spiced lentil soup, cup | 900 | Delivered | 16 Oct | arrived_2026_1103 | |
| Dining room brunch, table 8 | Roasted pepper grain bowl | 170 | Delivered | 23 Oct | delivered_2026_1104 | |
| Dining room brunch, table 8 | Charred broccoli side | 960 | Delivered | 28 Oct | served_2026_1105 |
Keep decisions, guarded operation receipts and attached evidence with the order.
Operation receipts
| Parent | Operation key | Action | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| Pickup order, Willow Avenue | order-ald-1021-lunch | Accept meal order | Failed | 17 Oct | Ingredient stock is below recipe need | |
| Dining room brunch, table 8 | order-patio-1021-dinner | Release kitchen ticket | Needs review | 25 Oct | Delivery address is incomplete | |
| Catering lunch, Harbor Clinic | pickup-willow-1022 | Reserve ingredients | Failed | 17 Oct | Payment authorization expired | |
| Dinner delivery, Bayview Lofts | catering-clinic-1023 | Record pickup handoff | Needs review | 20 Oct | Kitchen ticket already released | |
| Private event supper, garden room | brunch-table8-1024 | Capture card payment | Failed | 28 Oct | Order was cancelled before dispatch |
From meal order to verified service ships ready to use. One step needs a named approval before the work moves on: Review kitchen ticket (Kitchen Supervisor).
Record the guest request, destination, owner and meal lines.
Check menu, allergens, amount and service time before acceptance.
Record actual preparation against the accepted lines and recipe.
Have Kitchen Supervisor decide on the submitted ticket revision.
Record served portions or follow the product's delivery events.
Compare receipts and provider evidence with the actual effects.
Open any meal order to see its fulfillment events, the roles that work on it, its process stages and its approvals on one page.
Serve at, Owner and Counterparty.
Each line is linked to this meal order.
Admin, Order Manager and Kitchen Operator, each with their own permissions.
Every status change, in order.
Review kitchen ticket, with who decides.
Willow Avenue pickup counter · Accepted
| Parent | Product | Quantity |
|---|---|---|
| Dining room brunch, table 8 | Citrus almond cake, slice | 720 |
| Catering lunch, Harbor Clinic | Charred broccoli side | 80 |
| Dinner delivery, Bayview Lofts | Spiced lentil soup, cup | 900 |
Signed in as Kitchen Supervisor
| Decision | Approver | |
|---|---|---|
| Review kitchen ticketHave Kitchen Supervisor decide on the submitted ticket revision. | Kitchen Supervisor | |
| Approve kitchen tickets | Kitchen Supervisor |
Everyone opens Restaurant + POS + Inventory + Delivery to the work that is theirs. Pick a role to see what it starts with.
Sets up operating organizations, users, team members and access for the restaurant group.
Owns the service plan and decides whether an order can be accepted or needs correction.
This is the first screen this role sees.
Kitchen tickets · Order Manager
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Private event supper, garden room | Submitted | 780 | Table 4 | 22 Oct | 35 | |
| Pickup dinner, Cedar Lane | Submitted | 90 | Table 8 | 12 Oct | 14 | |
| Pickup order, Willow Avenue | Submitted | 280 | Patio 2 | 12 Oct | 23 | |
| Private event supper, garden room | Submitted | 100 | Patio 6 | 21 Oct | 29 | |
| Dining room brunch, table 8 | Submitted | 80 | Garden 1 | 16 Oct | 19 |
Records kitchen preparation and the meal lines associated with a ticket.
This is the first screen this role sees.
Meal orders · Kitchen Operator
Independently reviews a submitted kitchen ticket revision and records the release decision.
This is the first screen this role sees.
Kitchen tickets · Kitchen Supervisor
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Private event supper, garden room | Submitted | 780 | Table 4 | 22 Oct | 35 | |
| Pickup dinner, Cedar Lane | Submitted | 90 | Table 8 | 12 Oct | 14 | |
| Pickup order, Willow Avenue | Submitted | 280 | Patio 2 | 12 Oct | 23 | |
| Private event supper, garden room | Submitted | 100 | Patio 6 | 21 Oct | 29 | |
| Dining room brunch, table 8 | Submitted | 80 | Garden 1 | 16 Oct | 19 |
Maintains menu and ingredient source records and investigates movement history.
This is the first screen this role sees.
Menu recipes · Inventory Manager
| Recipe code | Product | Revision number | Effective from | Portion yield | Approved | |
|---|---|---|---|---|---|---|
| BOWL-PEPPER-01 | Spiced lentil soup, cup | 70 | 31 Oct | 760 | Yes | |
| PLATE-CHICKEN-02 | Smoked tomato sandwich | 280 | 28 Oct | 630 | Yes | |
| FLAT-MUSHROOM-03 | Ginger pear iced tea, 16 oz | 770 | 14 Oct | 90 | Yes | |
| SIDE-BROCCOLI-04 | Roasted pepper grain bowl | 420 | 04 Nov | 760 | Yes | |
| SOUP-LENTIL-05 | Spiced lentil soup, cup | 250 | 28 Oct | 50 | Yes |
Records service outcome and follows fulfillment events for the destination.
This is the first screen this role sees.
Meal orders · Service and Delivery Lead
Checks provider payment evidence and operation receipts before financial exceptions are resolved.
This is the first screen this role sees.
Operation receipts · Finance Reviewer
| Parent | Operation key | Action | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| Pickup order, Willow Avenue | order-ald-1021-lunch | Accept meal order | Failed | 17 Oct | Ingredient stock is below recipe need | |
| Dining room brunch, table 8 | order-patio-1021-dinner | Release kitchen ticket | Needs review | 25 Oct | Delivery address is incomplete | |
| Catering lunch, Harbor Clinic | pickup-willow-1022 | Reserve ingredients | Failed | 17 Oct | Payment authorization expired | |
| Dinner delivery, Bayview Lofts | catering-clinic-1023 | Record pickup handoff | Needs review | 20 Oct | Kitchen ticket already released | |
| Private event supper, garden room | brunch-table8-1024 | Capture card payment | Failed | 28 Oct | Order was cancelled before dispatch |
Answer service, kitchen, ingredient, payment and exception questions from linked records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 37 | ||
| Accepted | 15 | 41% | |
| Preparing | 3 | 20% | |
| Ready | 1 | 33% |
Sample counts per stage
Group meal orders by status and requested service time to see the work still due.
Sum meal order net amounts by destination and organization.
Compare each order's meal lines, preparation times and served portions.
Show submitted, approved and rejected tickets with revision and decision time.
Show approved recipe versions and ingredient quantities per yield.
Follow signed quantities by ingredient, source meal line and operation key.
Group provider events by type and verification state for each order.
Trace allocated, picked, shipped, delivered and returned quantities by order and product.
Show failed or review-needed receipts with linked decisions and attachments.
See how Restaurant + POS + Inventory + Delivery fits your kind of team.
Each stage, from meal order to verified service, names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to help your team find the right order and check its linked evidence.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 18 tablesStart with one team and one process, then add the rest once the basics are running.
Set organizations, time zones, currencies, service locations and team member identities.
Confirm active products, ingredient units and allergen declarations, then review recipe revisions, yields and effective dates.
Assign order, kitchen, supervisor, inventory, delivery and finance access. Decide who may review a submitted ticket or compensating correction.
Take a draft order through acceptance, preparation, ticket review and actual service or delivery events.
Compare a pending receipt with its linked effects, then test a partial-service correction and provider refund evidence.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Scope, rollout and pricing for Restaurant + POS + Inventory + Delivery.
All questionsClick 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.
Start free, then use Proto to change fields, steps and approvals before your team goes live.