All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Restaurant + POS + Inventory + Delivery · Available now

Keep the order, kitchen, ingredient-use and fulfillment story together.

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.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Meal Orders
Restaurant + POS + Inventory + Delivery · Meal orders

Open Meal Orders

Meal orders in one list

New meal order
Meal orders in view
6
Accepted
2
Preparing
2
Ready
2
Accepted2
Lunch delivery, Alder Street officesWillow Avenue pickup counter
18 Oct
Catering lunch, Harbor ClinicHarbor Clinic delivery desk
04 Nov
Add
Preparing2
Patio dinner, party of fourAlder Street office lobby
29 Oct
Dining room brunch, table 8Main dining room
17 Oct
Add
Ready2
Pickup order, Willow AvenueHarbor Clinic delivery desk
22 Oct
Dinner delivery, Bayview LoftsHarbor Clinic delivery desk
29 Oct
Add
Lunch delivery, Alder Street officesMeal orders · MO-41222
Accepted
Serve at18 Oct
OwnerTariq Mensah
CounterpartyWillow Avenue pickup counter
Review kitchen ticketMO-41222 · Lunch delivery, Alder Street offices

Kitchen Supervisor approves or rejects the submitted revision before release.

Waiting for Kitchen Supervisor
ApproveReturn
Example screen with sample data
Tables, ready to use
18
Saved views
13
Roles with set permissions
7
Reports and dashboards
9
Features

One order story from counter to service

Every feature works on the same records. Pick one to see the screen your team works in.

Order intake

Keep each meal order tied to its owner, service destination, lines and requested time.

  • One order, clear owner
  • Lines preserve detail
  • A durable action trail
  • Meal orders
  • Meal lines
  • Service locations
  • Organizations
  • Team members
  • Operation receipts
Explore order intake
OverviewMy Meal Orders
Restaurant + POS + Inventory + Delivery · Order intake

My Meal Orders

Meal orders

New
Record numberSubjectStatusServe atOwnerCounterparty
MO-65192Lunch delivery, Alder Street officesDraft13 OctElena ParkHarbor Clinic delivery desk
MO-43773Patio dinner, party of fourAccepted02 NovDev ShahBayview Lofts reception
MO-37529Pickup order, Willow AvenuePreparing04 NovLuca MorettiMain dining room
MO-73045Catering lunch, Harbor ClinicReady01 NovRafiq RahmanAlder Street office lobby
MO-91706Dining room brunch, table 8Served22 OctTariq MensahMain dining room
6 of 6 records
Lunch delivery, Alder Street officesMeal orders · MO-65192
Draft
Serve at13 Oct
OwnerElena Park
CounterpartyHarbor Clinic delivery desk
Example screen with sample data
Process

Follow every meal through its handoffs

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).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Draft meal order

    Record the guest request, destination, owner and meal lines.

    Lunch delivery, Alder Street officesMO-41222 · Order Manager
    Draft meal orderBy Order Manager
  2. Accept meal order

    Check menu, allergens, amount and service time before acceptance.

    Lunch delivery, Alder Street officesMO-41222 · Order Manager
    Accept meal orderBy Order Manager
  3. Prepare meal

    Record actual preparation against the accepted lines and recipe.

    Lunch delivery, Alder Street officesMO-41222 · Kitchen Operator
    Prepare mealBy Kitchen Operator
  4. Review kitchen ticket

    Have Kitchen Supervisor decide on the submitted ticket revision.

    Lunch delivery, Alder Street officesMO-41222 · Kitchen Supervisor
    Review kitchen ticketBy Kitchen Supervisor
    ApprovalKitchen Supervisor approves or rejects the submitted revision before release.
  5. Serve or fulfill

    Record served portions or follow the product's delivery events.

    Lunch delivery, Alder Street officesMO-41222 · Service and Delivery Lead
    Serve or fulfillBy Service and Delivery Lead
  6. Reconcile outcome

    Compare receipts and provider evidence with the actual effects.

    Lunch delivery, Alder Street officesMO-41222 · Finance Reviewer
    Reconcile outcomeBy Finance Reviewer
Inside a record

Keep provider and delivery evidence close

Open any meal order to see its fulfillment events, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Serve at, Owner and Counterparty.

  2. 2
    Fulfillment events

    Each line is linked to this meal order.

  3. 3
    Who works on it

    Admin, Order Manager and Kitchen Operator, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Review kitchen ticket, with who decides.

Open Meal OrdersLunch delivery, Alder Street offices
Restaurant + POS + Inventory + Delivery · Meal orders

Lunch delivery, Alder Street offices

Willow Avenue pickup counter · Accepted

Log activity
1
Record details
Serve at18 Oct
OwnerTariq Mensah
CounterpartyWillow Avenue pickup counter
2
Fulfillment events

Lunch delivery, Alder Street offices

ParentProductQuantity
Dining room brunch, table 8Citrus almond cake, slice720
Catering lunch, Harbor ClinicCharred broccoli side80
Dinner delivery, Bayview LoftsSpiced lentil soup, cup900
Fulfillment events
6
Total quantity
3,210
3

Who works on it

  • AdminManage Organizations, Users, team members, service locations
  • Order ManagerManage meal orders, meal lines, service locations
  • Kitchen OperatorManage meal lines, kitchen tickets, ingredient movements
5

Approvals

  • Review kitchen ticketKitchen Supervisor
    Approved
Example screen with sample data
Approvals

A clear decision before kitchen release

OverviewApprovals
Restaurant + POS + Inventory + Delivery · Overview

Approvals

Signed in as Kitchen Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • KT-92952Table 4
    Private event supper, garden roomRequested by Admin
    Submitted0dActions
  • KT-35314Table 8
    Pickup dinner, Cedar LaneRequested by Admin
    Submitted4dActions
  • KT-66503Patio 2
    Pickup order, Willow AvenueRequested by Admin
    Submitted5dActions
  • KT-62614Patio 6
    Private event supper, garden roomRequested by Admin
    Submitted3dActions

Who approves what

DecisionApprover
Review kitchen ticketHave Kitchen Supervisor decide on the submitted ticket revision.Kitchen Supervisor
Approve kitchen ticketsKitchen Supervisor
2 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Restaurant + POS + Inventory + Delivery to the work that is theirs. Pick a role to see what it starts with.

Admin

Sets up operating organizations, users, team members and access for the restaurant group.

  • Manage Organizations, Users, team members, service locations
  • View meal orders, operation receipts, review decisions
Reports

See what is due and what needs review

Answer service, kitchen, ingredient, payment and exception questions from linked records.

Overview
Restaurant + POS + Inventory + Delivery · Overview

Restaurant + POS + Inventory + Delivery dashboard

This quarter

Kitchen tickets in view
6
Total guest count
132
Submitted
6

Meal orders by status

How far records got this quarter

StageReachedStep
Draft37
Accepted1541%
Preparing320%
Ready133%

Number of meal orders by status

Sample counts per stage

0
-20Draft
-50Accepted
-20Preparing
-50Ready
-60Served
Example screen with sample data
  1. 01Meal order service status

    Group meal orders by status and requested service time to see the work still due.

  2. 02Order value by service location

    Sum meal order net amounts by destination and organization.

  3. 03Preparation and served portions

    Compare each order's meal lines, preparation times and served portions.

  4. 04Kitchen ticket review

    Show submitted, approved and rejected tickets with revision and decision time.

  5. 05Recipe ingredient requirements

    Show approved recipe versions and ingredient quantities per yield.

  6. 06Ingredient movement history

    Follow signed quantities by ingredient, source meal line and operation key.

  7. 07Payment evidence verification

    Group provider events by type and verification state for each order.

  8. 08Fulfillment event history

    Trace allocated, picked, shipped, delivered and returned quantities by order and product.

  9. 09Operation exception trail

    Show failed or review-needed receipts with linked decisions and attachments.

Controls

Trace revisions, receipts and decisions

Each stage, from meal order to verified service, names the role that acts and the status it records, so a change is never anonymous.

OverviewFrom meal order to verified service
Restaurant + POS + Inventory + Delivery · Process

From meal order to verified service

Each stage, the role that acts and the status it records

Process stages
9
Approval steps
1
Roles involved
6
Tables touched
10
Accept meal order
Order Manager
StatusDraft → Accepted
RecordsOperation receipts
Prepare meal
Kitchen Operator
StatusAccepted → Preparing
RecordsIngredient movements, Meal lines
Review kitchen ticketApproval
Kitchen Supervisor, Kitchen Operator
StatusDraft → Submitted
RecordsReview decisions
From meal order to verified service
  1. Start
    Accept meal orderDraft → Accepted
    Operation receipts
  2. Step
    Prepare mealAccepted → Preparing
    Ingredient movements
  3. Approval
    Review kitchen ticketDraft → Submitted
    Review decisions
  4. Step
    Release kitchen ticketApproved → Completed
    Kitchen Supervisor
  5. Step
    Serve or fulfillReady → Served
    Fulfillment events
Example screen with sample data
AI agent

Ask for the records behind a decision

Ask Proto to help your team find the right order and check its linked evidence.

It can

  • Order Manager: Show open orders due for service with their owners, destinations and meal lines.
  • Kitchen Operator: Find approved recipes and ingredient declarations for a menu item before preparation.
  • Kitchen Supervisor: Gather the submitted ticket revision, parent order and attachments for a review.
  • Service and Delivery Lead: Compare served portions with fulfillment event quantities for an order.

Stays with a person

  • A person must decide whether a guest request is feasible, whether a submitted ticket is approved, and whether a correction or refund is authorized.
  • Proto can gather records and explain the trail, while the responsible role checks the real service and provider evidence before changing an outcome.
Integrations

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
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 18 tables
18tables
  • Order intake6
  • Kitchen handoff6
  • Menu and recipes5
  • Inventory movements7
  • Payments and fulfillment6
  • Review and evidence6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Establish operating context

    Set organizations, time zones, currencies, service locations and team member identities.

  2. Prepare the menu

    Confirm active products, ingredient units and allergen declarations, then review recipe revisions, yields and effective dates.

  3. Configure responsibilities

    Assign order, kitchen, supervisor, inventory, delivery and finance access. Decide who may review a submitted ticket or compensating correction.

  4. Rehearse service

    Take a draft order through acceptance, preparation, ticket review and actual service or delivery events.

  5. Rehearse exceptions

    Compare a pending receipt with its linked effects, then test a partial-service correction and provider refund evidence.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Restaurant + POS + Inventory + Delivery.

All questions
How do I get started?

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.

How does the kitchen know which order to prepare?

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.

Can I track a dish that was prepared but never served?

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

Where do allergen details live?

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

How are recipe changes handled?

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

Who releases a kitchen ticket?

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

How do we track ingredient waste?

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.

What shows that a delivery happened?

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

How are refunds checked?

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.

What if an operation is pending or failed?

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

Set up Restaurant + POS + Inventory + Delivery your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appRestaurant + POS + Inventory + Delivery

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.