All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Bar & Beverage Management · Available now

Keep service, preparation and review on the same order.

Bar & Beverage Management keeps a venue's service order connected to its kitchen work, menu definitions, ingredient usage and outcome evidence. A service team records the requested portions, serving time and service location.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Meal Orders
Bar & Beverage Management · Meal orders

Open Meal Orders

Meal orders in one list

New meal order
Meal orders in view
6
Total net amount USD
3,360
Draft
2
Accepted
2
Draft2
Patio table 12 dinnerCourtyard patio
590
19 Oct
Lounge table 3 small platesUpstairs lounge
560
30 Oct
Add
Accepted2
Bar table 4 late supperSouth bar counter
280
15 Oct
Counter order for Avery RossUpstairs lounge
960
03 Nov
Add
Preparing1
Private tasting for eightMain dining room
400
30 Oct
Add
Ready1
Terrace table 7 lunchSouth bar counter
570
19 Oct
Add
Patio table 12 dinnerMeal orders · MO-42046
Draft
Serve at19 Oct
CounterpartyCourtyard patio
OwnerSamira Ali
Net amount USD590
Kitchen ticket reviewMO-42046 · Patio table 12 dinner

Supervisor reviews the ticket revision and records the reason.

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

Follow service from request to guest

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

Service orders

Keep requested portions, owner, location and serving time together through service.

  • Order header
  • Line scope
  • Location and owner
  • Meal orders
  • Meal lines
  • Service locations
  • Team members
  • Products
Explore service orders
OverviewMy Meal Orders
Bar & Beverage Management · Service orders

My Meal Orders

Meal orders

New
Record numberSubjectStatusServe atCounterpartyOwner
MO-80815Patio table 12 dinnerDraft12 OctUpstairs loungeImani Brooks
MO-33066Bar table 4 late supperAccepted14 OctSouth bar counterMina Chen
MO-26019Private tasting for eightPreparing20 OctCourtyard patioImani Brooks
MO-17020Terrace table 7 lunchReady11 OctUpstairs loungeNora Haddad
MO-23697Lounge table 3 small platesServed25 OctMain dining roomJavier Cruz
6 of 6 records
Patio table 12 dinnerMeal orders · MO-80815
Draft
Serve at12 Oct
CounterpartyUpstairs lounge
OwnerImani Brooks
Example screen with sample data
Process

One order through preparation and service

Order to reviewed service ships ready to use. One step needs a named approval before the work moves on: Kitchen ticket review (Supervisor).

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

  1. Order entry

    Record the location, owner, serving time and requested portions.

    Patio table 12 dinnerMO-42046 · Service Staff
    Order entryBy Service Staff
  2. Order acceptance

    Check the menu and capacity before the order is accepted.

    Patio table 12 dinnerMO-42046 · Service Manager
    Order acceptanceBy Service Manager
  3. Kitchen ticket review

    Supervisor decides on the submitted ticket revision.

    Patio table 12 dinnerMO-42046 · Supervisor
    Kitchen ticket reviewBy Supervisor
    ApprovalSupervisor reviews the ticket revision and records the reason.
  4. Preparation

    Record actual prepared work and ingredient use.

    Patio table 12 dinnerMO-42046 · Kitchen Lead
    PreparationBy Kitchen Lead
  5. Service

    Record the portions and time actually served.

    Patio table 12 dinnerMO-42046 · Service Staff
    ServiceBy Service Staff
  6. Evidence reconciliation

    Compare provider events and operation effects with the order.

    Patio table 12 dinnerMO-42046 · Finance Reviewer
    Evidence reconciliationBy Finance Reviewer
Inside a record

Keep provider and delivery evidence linked

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, Counterparty, Owner and Net amount USD.

  2. 2
    Fulfillment events

    Each line is linked to this meal order.

  3. 3
    Who works on it

    Admin, Service Manager and Service Staff, each with their own permissions.

  4. 4
    Process stages

    Order entry and Kitchen ticket preparation, with the role that acts.

  5. 5
    Approvals

    Kitchen ticket review, with who decides.

Open Meal OrdersPatio table 12 dinner
Bar & Beverage Management · Meal orders

Patio table 12 dinner

Courtyard patio · Draft

Log activity
1
Record details
Serve at19 Oct
CounterpartyCourtyard patio
OwnerSamira Ali
Net amount USD590
2
Fulfillment events

Patio table 12 dinner

ParentProductQuantity
Patio table 12 dinnerGinger pear cooler460
Counter order for Avery RossCardamom espresso fizz70
Terrace table 7 lunchGinger pear cooler460
Fulfillment events
6
Total quantity
2,930
3

Who works on it

  • AdminManage Organizations, team members, Users, service locations
  • Service ManagerManage meal orders, meal lines, kitchen tickets
  • Service StaffManage meal orders, meal lines
4

Process stages

  • Order entryService Staff
  • Kitchen ticket preparationService Manager
5

Approvals

  • Kitchen ticket reviewSupervisor
    Approved
Example screen with sample data
Approvals

Review the kitchen release

Service Manager prepares an order or ticket; Supervisor reviews the submitted revision and records the reason.

OverviewApprovals
Bar & Beverage Management · Overview

Approvals

Signed in as Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • KT-96444PATIO-12
    Counter order for Avery RossRequested by Admin
    Submitted2dActions
  • KT-23469BAR-04
    Bar table 4 late supperRequested by Admin
    Submitted2dActions
  • KT-63253TERRACE-07
    Bar table 4 late supperRequested by Admin
    Submitted4dActions
  • KT-86305LOUNGE-03
    Lounge table 3 small platesRequested by Admin
    Submitted4dActions

Who approves what

DecisionApprover
Kitchen ticket reviewSupervisor decides on the submitted ticket revision.Supervisor
1 approval rule · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Bar & Beverage Management to the work that is theirs. Pick a role to see what it starts with.

Admin

Maintains organization, user and location setup and grants scoped access.

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

Read the service outcome clearly

Compare order status, served scope, recipe versions and unresolved operation outcomes.

Overview
Bar & Beverage Management · Overview

Bar & Beverage Management dashboard

This quarter

Kitchen tickets in view
6
Total guest count
149
Submitted
6

Meal orders by status

How far records got this quarter

StageReachedStep
Draft26
Accepted1869%
Preparing1056%
Ready550%

Net amount USD by status

Sample totals per stage

10.0k0
9.0kDraft
10.0kAccepted
6.0kPreparing
4.0kReady
3.0kServed
Example screen with sample data
  1. 01Order service status

    Which orders are still draft, accepted, preparing or ready for a given serving period?

  2. 02Served scope by location

    What portions actually reached guests at each service location?

  3. 03Order net amount

    Sum net amount USD on meal orders by Status and Organization.

  4. 04Recipe approval register

    Which recipe revision and effective date apply to a menu product?

  5. 05Ingredient movement history

    Which signed quantities were recorded against each ingredient and source line?

  6. 06Kitchen ticket status

    Which submitted tickets were approved or rejected, and when was the decision recorded?

  7. 07Payment verification queue

    Which provider events remain unverified by type and amount?

  8. 08Operation exception aging

    Which failed or review-needed actions have waited longest for investigation?

Controls

Preserve revisions and operation results

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

OverviewOrder to reviewed service
Bar & Beverage Management · Process

Order to reviewed service

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

Process stages
9
Approval steps
1
Roles involved
5
Tables touched
15
Order acceptance
Service Manager
StatusDraft → Accepted
RecordsOperation receipts, Products
Kitchen ticket preparation
Service Manager
StatusDraft → Submitted
RecordsKitchen tickets, Meal orders
Kitchen ticket reviewApproval
Supervisor, Finance Reviewer
StatusSubmitted → Approved
RecordsReview decisions
Order to reviewed service
  1. Start
    Order acceptanceDraft → Accepted
    Operation receipts
  2. Step
    Kitchen ticket preparationDraft → Submitted
    Kitchen tickets
  3. Approval
    Kitchen ticket reviewSubmitted → Approved
    Review decisions
  4. Step
    PreparationAccepted → Preparing → Ready
    Ingredient movements
  5. Step
    ServiceReady → Served
    Fulfillment events
Example screen with sample data
AI agent

Prepare the review with Proto

Ask Proto to prepare order, kitchen and evidence reviews for the responsible people.

It can

  • Service Manager: List open orders for the next service period by owner, location and status.
  • Kitchen Lead: Compare an approved recipe's ingredient quantities with actual signed movements for a prepared line.
  • Supervisor: Summarize a submitted ticket revision, its supporting attachments and the parent order before a decision.
  • Finance Reviewer: Group failed operation receipts by parent order and identify the provider references that need checking.

Stays with a person

  • The authorized person decides whether a ticket or correction is approved.
  • Proto can organize the order, revision and evidence, but it cannot replace an independent reviewer or a provider's confirmation.
  • Keep the service team's record of actual served portions distinct from a preparation or delivery event.
  • Use the person's configured access when reading internal attachments and payment evidence.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Bar & Beverage Management
  • Payment provider
  • Fulfillment source
  • Identity provider
  • Menu source
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
  • Service orders5
  • Kitchen tickets6
  • Products and recipes5
  • Ingredients and usage5
  • Payment and fulfillment5
  • 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. Agree the operating boundary

    Choose the service locations, menu products and order types for the first cycle. Name the people who accept orders, review tickets, record preparation and reconcile payment evidence.

  2. Map the source data

    Preserve organization and location codes, product and ingredient units, recipe revisions, customer references and provider event identifiers. Keep original source files for comparison.

  3. Configure a bounded pilot

    Load an active menu and approved recipes for one location. Run orders from draft through actual served portions, with a submitted kitchen ticket and supervisor decision.

  4. Rehearse exceptions

    Reject a ticket with a mismatched guest count. Review a correction after partial preparation while keeping served history and waste. Repeat a provider event and verify it does not create a second effect.

  5. Reconcile and release

    Compare order scope, ingredient movements, provider evidence and operation receipts with the source. Have Service Manager, Supervisor and Finance Reviewer accept the result before adding another location.

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 Bar & Beverage Management.

All questions
How do I get started?

Click Get started, then use Proto to configure Bar & Beverage Management for your business. Begin with one service location, an active menu and a representative service period. Reconcile accepted orders, prepared lines, served portions and the related review evidence before expanding.

How does an order reach the kitchen?

Service Staff enters the order lines and serving time. Service Manager checks the feasible scope and prepares a kitchen ticket. Supervisor reviews the submitted ticket revision before released work is taken up.

Can we keep different service locations?

Yes. Service locations identify the named destination and its organization, contact, address and active state. Each order links to a location and an owner.

How are recipe changes handled?

Menu recipes carry a product, revision number, effective date, portion yield and approval state. Review the version used for accepted work before a later recipe revision becomes the basis for new preparation.

What is the difference between prepared and served?

Each meal line keeps its prepared time and served portions separately. The order keeps the actual served time. This makes a partial service visible when another line changes or is cancelled.

How are ingredient quantities recorded?

Recipe ingredients state planned quantity and unit for a recipe yield. Ingredient movements record signed actual consumption or waste with the ingredient, source line and operation key.

Who reviews a kitchen ticket?

Supervisor reviews the submitted revision and records the decision and reason. The preparer and reviewer should be different people for the same revision.

What happens after an uncertain provider result?

Finance Reviewer reads the operation receipt, expected revision and provider event reference, then checks the actual effects. A retry follows that comparison so an earlier successful action is not duplicated.

Can we import existing records?

Prepare stable codes for locations, products, ingredients and recipes. Keep order numbers, provider event identifiers and operation keys intact. Reconcile a pilot import against the source before opening regular service.

What drives the cost?

Ordinary manual use follows the platform policy. Agent execution, imports and connected machine work are metered; implementation is scoped separately. See pricing for current terms.

Set up Bar & Beverage Management 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 appBar & Beverage Management

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.