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
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.
Meal orders in one list
Supervisor reviews the ticket revision and records the reason.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep requested portions, owner, location and serving time together through service.
Meal orders
| Record number | Subject | Status | Serve at | Counterparty | Owner | |
|---|---|---|---|---|---|---|
| MO-80815 | Patio table 12 dinner | Draft | 12 Oct | Upstairs lounge | Imani Brooks | |
| MO-33066 | Bar table 4 late supper | Accepted | 14 Oct | South bar counter | Mina Chen | |
| MO-26019 | Private tasting for eight | Preparing | 20 Oct | Courtyard patio | Imani Brooks | |
| MO-17020 | Terrace table 7 lunch | Ready | 11 Oct | Upstairs lounge | Nora Haddad | |
| MO-23697 | Lounge table 3 small plates | Served | 25 Oct | Main dining room | Javier Cruz |
Review a submitted kitchen release against its parent order and supporting evidence.
Approval conditions
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Counter order for Avery Ross | Submitted | 410 | PATIO-12 | 09 Oct | 18 | |
| Bar table 4 late supper | Submitted | 520 | BAR-04 | 16 Oct | 26 | |
| Bar table 4 late supper | Submitted | 470 | TERRACE-07 | 19 Oct | 24 | |
| Lounge table 3 small plates | Submitted | 420 | LOUNGE-03 | 15 Oct | 33 | |
| Courtyard table 9 dinner | Submitted | 340 | COURT-09 | 13 Oct | 29 |
Keep active menu products and dated recipe revisions aligned with the kitchen's portions.
Products
| SKU | Name | Base unit | Standard price USD | Active | |
|---|---|---|---|---|---|
| DRK-SPRITZ-01 | Citrus rosemary spritz | Each | 610 | Yes | |
| DRK-PLUM-02 | Smoked plum old fashioned | Milliliter | 760 | Yes | |
| DRK-COOLER-03 | Ginger pear cooler | Gram | 170 | Yes | |
| FOOD-FLAT-04 | Charred pepper flatbread | Bottle | 640 | Yes | |
| FOOD-SKEWER-05 | Seared mushroom skewers | Portion | 760 | Yes |
Track ingredient declarations and signed consumption or waste against prepared work.
Ingredients
| Ingredient code | Name | Base unit | Allergen declaration | Active | |
|---|---|---|---|---|---|
| HERB-ROSEMARY | Fresh rosemary | Each | Contains tree nuts | Yes | |
| JUICE-BLOOD-ORANGE | Blood orange juice | Milliliter | Contains dairy | Yes | |
| SYRUP-SMOKED-PLUM | Smoked plum syrup | Gram | Contains wheat | Yes | |
| ROOT-GINGER | Ginger root | Bottle | Contains sesame | Yes | |
| PUREE-PEAR | Pear puree | Portion | Contains soy | Yes |
Tie provider payment receipts and delivery events to the order they describe.
Payment evidence
| Parent | Provider event ID | Type | Amount USD | Occurred at | Provider reference | |
|---|---|---|---|---|---|---|
| Counter order for Avery Ross | PAYEV-2026-8011 | Authorization | 80 | 27 Oct | CARD-746281 | |
| Counter order for Avery Ross | PAYEV-2026-8012 | Capture | 780 | 30 Oct | CARD-746282 | |
| Bar table 4 late supper | PAYEV-2026-8013 | Refund | 750 | 19 Oct | CARD-746283 | |
| Courtyard table 9 dinner | PAYEV-2026-8014 | Void | 70 | 18 Oct | CARD-746284 | |
| Upstairs room cocktail service | PAYEV-2026-8015 | Authorization | 860 | 31 Oct | CARD-746285 |
Keep supervisor decisions, order attachments and guarded operation outcomes traceable.
Operation receipts
| Parent | Operation key | Action | Result state | Expected revision | Occurred at | |
|---|---|---|---|---|---|---|
| Courtyard table 9 dinner | ticket:patio-12:accept | Accept kitchen ticket | Failed | 620 | 16 Oct | |
| Bar table 4 late supper | ticket:bar-04:serve | Start drink preparation | Needs review | 800 | 26 Oct | |
| Courtyard table 9 dinner | ticket:terrace-07:close | Mark plates ready | Failed | 550 | 20 Oct | |
| Counter order for Avery Ross | ticket:lounge-03:accept | Send order to runner | Needs review | 220 | 01 Nov | |
| Counter order for Avery Ross | ticket:court-09:serve | Record table service | Failed | 240 | 01 Nov |
Order to reviewed service ships ready to use. One step needs a named approval before the work moves on: Kitchen ticket review (Supervisor).
Record the location, owner, serving time and requested portions.
Check the menu and capacity before the order is accepted.
Supervisor decides on the submitted ticket revision.
Record actual prepared work and ingredient use.
Record the portions and time actually served.
Compare provider events and operation effects with the order.
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, Counterparty, Owner and Net amount USD.
Each line is linked to this meal order.
Admin, Service Manager and Service Staff, each with their own permissions.
Order entry and Kitchen ticket preparation, with the role that acts.
Kitchen ticket review, with who decides.
Courtyard patio · Draft
| Parent | Product | Quantity |
|---|---|---|
| Patio table 12 dinner | Ginger pear cooler | 460 |
| Counter order for Avery Ross | Cardamom espresso fizz | 70 |
| Terrace table 7 lunch | Ginger pear cooler | 460 |
Service Manager prepares an order or ticket; Supervisor reviews the submitted revision and records the reason.
Signed in as Supervisor
| Decision | Approver | |
|---|---|---|
| Kitchen ticket reviewSupervisor decides on the submitted ticket revision. | Supervisor |
Everyone opens Bar & Beverage Management to the work that is theirs. Pick a role to see what it starts with.
Maintains organization, user and location setup and grants scoped access.
Owns service order intake, capacity checks and exception coordination.
This is the first screen this role sees.
Kitchen tickets · Service Manager
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Counter order for Avery Ross | Submitted | 410 | PATIO-12 | 09 Oct | 18 | |
| Bar table 4 late supper | Submitted | 520 | BAR-04 | 16 Oct | 26 | |
| Bar table 4 late supper | Submitted | 470 | TERRACE-07 | 19 Oct | 24 | |
| Lounge table 3 small plates | Submitted | 420 | LOUNGE-03 | 15 Oct | 33 | |
| Courtyard table 9 dinner | Submitted | 340 | COURT-09 | 13 Oct | 29 |
Records service requests and actual served scope for assigned orders.
This is the first screen this role sees.
Meal orders · Service Staff
Checks the released work against menu definitions and records preparation.
This is the first screen this role sees.
Meal orders · Kitchen Lead
Makes the independent decision on submitted kitchen work and reviewed corrections.
This is the first screen this role sees.
Kitchen tickets · Supervisor
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| Counter order for Avery Ross | Submitted | 410 | PATIO-12 | 09 Oct | 18 | |
| Bar table 4 late supper | Submitted | 520 | BAR-04 | 16 Oct | 26 | |
| Bar table 4 late supper | Submitted | 470 | TERRACE-07 | 19 Oct | 24 | |
| Lounge table 3 small plates | Submitted | 420 | LOUNGE-03 | 15 Oct | 33 | |
| Courtyard table 9 dinner | Submitted | 340 | COURT-09 | 13 Oct | 29 |
Maintains ingredient and recipe quantities and reviews signed usage.
This is the first screen this role sees.
Menu recipes · Inventory Steward
| Recipe code | Product | Revision number | Effective from | Portion yield | Approved | |
|---|---|---|---|---|---|---|
| RCP-SPRITZ-01 | Salted citrus olives | 890 | 28 Oct | 920 | Yes | |
| RCP-PLUM-02 | Ginger pear cooler | 640 | 12 Oct | 410 | Yes | |
| RCP-COOLER-03 | Cardamom espresso fizz | 160 | 28 Oct | 50 | Yes | |
| RCP-FLAT-04 | Ginger pear cooler | 890 | 31 Oct | 760 | Yes | |
| RCP-SKEWER-05 | House tonic, 250 ml | 620 | 30 Oct | 890 | Yes |
Checks provider evidence, refund scope and unresolved operation outcomes.
This is the first screen this role sees.
Fulfillment events · Finance Reviewer
| Parent | Product | Quantity | Event type | Occurred at | External event ID | |
|---|---|---|---|---|---|---|
| Patio table 12 dinner | Ginger pear cooler | 460 | Delivered | 02 Nov | SERVE-2026-4801 | |
| Counter order for Avery Ross | Cardamom espresso fizz | 70 | Delivered | 02 Nov | SERVE-2026-4802 | |
| Terrace table 7 lunch | Ginger pear cooler | 460 | Delivered | 24 Oct | SERVE-2026-4803 | |
| Terrace table 7 lunch | Salted citrus olives | 360 | Delivered | 28 Oct | SERVE-2026-4804 | |
| Lounge table 3 small plates | Seared mushroom skewers | 710 | Delivered | 02 Nov | SERVE-2026-4805 |
Compare order status, served scope, recipe versions and unresolved operation outcomes.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 26 | ||
| Accepted | 18 | 69% | |
| Preparing | 10 | 56% | |
| Ready | 5 | 50% |
Sample totals per stage
Which orders are still draft, accepted, preparing or ready for a given serving period?
What portions actually reached guests at each service location?
Sum net amount USD on meal orders by Status and Organization.
Which recipe revision and effective date apply to a menu product?
Which signed quantities were recorded against each ingredient and source line?
Which submitted tickets were approved or rejected, and when was the decision recorded?
Which provider events remain unverified by type and amount?
Which failed or review-needed actions have waited longest for investigation?
See how Bar & Beverage Management fits your kind of team.
Coordinate orders, menu recipes and kitchen release across a dining service.
Keep service locations and accountable order owners clear across operating organizations.
Follow accepted orders to a service destination with reviewed release and delivery evidence.
Each stage of order to reviewed 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 prepare order, kitchen and evidence reviews for the responsible people.
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.
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.
Preserve organization and location codes, product and ingredient units, recipe revisions, customer references and provider event identifiers. Keep original source files for comparison.
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.
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.
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.
$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 |
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.
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.
Yes. Service locations identify the named destination and its organization, contact, address and active state. Each order links to a location and an owner.
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.
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.
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.
Supervisor reviews the submitted revision and records the decision and reason. The preparer and reviewer should be different people for the same revision.
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.
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.
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.
Start free, then use Proto to change fields, steps and approvals before your team goes live.