All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Recipe Management System · Available now

Carry an approved recipe through the kitchen order.

Recipe Management System connects ingredient declarations and yield quantities to versioned recipe cards for sellable menu items. Recipe owners maintain the ingredient basis and effective recipe revision.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Production Orders
Recipe Management System · Production orders

Open Production Orders

Production orders in one list

New production order
Production orders in view
6
Draft
2
Accepted
2
Preparing
1
Draft2
Atrium lunch service, 80 guestsGarden Room service kitchen
03 Nov
Cedar Dining meal prep, TuesdayRiverside event kitchen
14 Oct
Add
Accepted2
Garden Room dinner, 42 guestsAtrium main kitchen
30 Oct
Riverside buffet, 55 guestsCedar Dining kitchen
25 Oct
Add
Preparing1
Conference breakfast, 65 guestsAtrium main kitchen
17 Oct
Add
Ready1
West Hall reception, 120 guestsEast Wing pastry kitchen
20 Oct
Add
Atrium lunch service, 80 guestsProduction orders · PO-96428
Draft
Serve at03 Nov
OwnerTariq Rahman
CounterpartyGarden Room service kitchen
Review batchPO-96428 · Atrium lunch service, 80 guests

Kitchen Supervisor reviews the submitted batch ticket revision and supporting evidence.

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

A clear view from recipe to service

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

Ingredients and yields

Keep ingredient declarations and recipe quantities together.

  • Ingredient identity
  • Yield quantities
  • Review context
  • Ingredient master
  • Ingredient yields
  • Recipe cards
  • Stock consumptions
Explore ingredients and yields
OverviewActive Ingredient Master
Recipe Management System · Ingredients and yields

Active Ingredient Master

Ingredient master

New
Ingredient codeNameBase unitAllergen declarationActive
ING-SQUASH-01Butternut squash, peeledkgContains milkYes
ING-CHICKEN-04Chicken breast, bonelessgContains tree nutsYes
ING-RICE-02Arborio rice, dryLContains wheatYes
ING-SALMON-03Salmon fillet, skinlessmillilitersContains fishYes
ING-TOMATO-07Roma tomato, freshportionContains sesameYes
6 of 6 records
ING-SQUASH-01Ingredient master · IM-42284
Yes
NameButternut squash, peeled
Base unitkg
Allergen declarationContains milk
Example screen with sample data
Process

Follow the meal from recipe to service

Recipe to reviewed service ships ready to use. One step needs a named approval before the work moves on: Review batch (Kitchen Supervisor).

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

  1. Maintain ingredients

    Set ingredient units, allergen declarations and recipe quantities.

    Atrium lunch service, 80 guestsPO-96428 · Recipe Owner
    Maintain ingredientsBy Recipe Owner
  2. Select approved recipe

    Recipe Owner checks the effective revision and yield before kitchen use.

    Atrium lunch service, 80 guestsPO-96428 · Recipe Owner
    Select approved recipeBy Recipe Owner
  3. Accept order

    Check the menu, portions, allergens and service capacity.

    Atrium lunch service, 80 guestsPO-96428 · Order Coordinator
    Accept orderBy Order Coordinator
  4. Prepare lines

    Record actual preparation and served portions against the accepted order.

    Atrium lunch service, 80 guestsPO-96428 · Kitchen Operator
    Prepare linesBy Kitchen Operator
  5. Review batch

    Kitchen Supervisor decides the submitted ticket revision.

    Atrium lunch service, 80 guestsPO-96428 · Kitchen Supervisor
    Review batchBy Kitchen Supervisor
    ApprovalKitchen Supervisor reviews the submitted batch ticket revision and supporting evidence.
  6. Verify completion

    Match operation receipts with decisions, local effects and external evidence.

    Atrium lunch service, 80 guestsPO-96428 · Reconciliation Analyst
    Verify completionBy Reconciliation Analyst
Inside a record

Keep the order and its evidence together

Open any production order to see its batch tickets, 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
    Batch tickets

    Each line is linked to this production order.

  3. 3
    Who works on it

    Admin, Recipe Owner and Recipe Reviewer, each with their own permissions.

  4. 4
    Process stages

    Draft order, with the role that acts.

  5. 5
    Approvals

    Review batch, with who decides.

Open Production OrdersAtrium lunch service, 80 guests
Recipe Management System · Production orders

Atrium lunch service, 80 guests

Garden Room service kitchen · Draft

Log activity
1
Record details
Serve at03 Nov
OwnerTariq Rahman
CounterpartyGarden Room service kitchen
2
Batch tickets

Atrium lunch service, 80 guests

ParentStatusRevision
Riverside buffet, 55 guestsSubmitted210
Courtyard tasting, 24 guestsSubmitted780
Cedar Dining meal prep, TuesdaySubmitted710
Batch tickets
6
Total revision
4,150
3

Who works on it

  • AdminManage Organizations, team members, Users
  • Recipe OwnerManage ingredient master, ingredient yields, recipe cards, menu…
  • Recipe ReviewerApprove recipe cards
4

Process stages

  • Draft orderOrder Coordinator
5

Approvals

  • Review batchKitchen Supervisor
    Approved
Example screen with sample data
Approvals

Review the decisions that release work

Keep recipe preparation separate from recipe approval and ticket preparation separate from supervisor review.

OverviewApprovals
Recipe Management System · Overview

Approvals

Signed in as Kitchen Supervisor

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • BT-15897AT-01
    Riverside buffet, 55 guestsRequested by Admin
    Submitted2dActions
  • BT-48472GR-02
    Courtyard tasting, 24 guestsRequested by Admin
    Submitted4dActions
  • BT-87689WH-03
    Cedar Dining meal prep, TuesdayRequested by Admin
    Submitted2dActions
  • BT-16291CD-04
    West Hall reception, 120 guestsRequested by Admin
    Submitted4dActions

Who approves what

DecisionApprover
Review batchKitchen Supervisor decides the submitted ticket revision.Kitchen Supervisor
Approve recipe cardsRecipe Reviewer
Approve batch tickets, review decisionsKitchen Supervisor
3 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Recipe Management System to the work that is theirs. Pick a role to see what it starts with.

Admin

Manages organization setup, staff identity and controlled access.

  • Manage Organizations, team members, Users
  • View production orders, review decisions, operation receipts
Reports

Read yields, service and exceptions

Review recipe revisions, service progress and exceptions from their underlying records.

Overview
Recipe Management System · Overview

Recipe Management System dashboard

This quarter

Batch tickets in view
6
Total guest count
133
Submitted
6

Production orders by status

How far records got this quarter

StageReachedStep
Draft47
Accepted1634%
Preparing425%
Ready250%

Number of production orders by status

Sample counts per stage

100
-50Draft
-20Accepted
0Preparing
10Ready
-30Served
Example screen with sample data
  1. 01Ingredient declaration register

    List active ingredients with base units and allergen declarations.

  2. 02Recipe yield requirements

    Show recipe cards and their ingredient quantities, units and waste allowances.

  3. 03Recipe revision history

    Compare effective dates, yield and approval by menu item and recipe code.

  4. 04Orders by service state

    Group production orders by status, kitchen and planned service time.

  5. 05Ordered and served portions

    Compare ordered portions, prepared times and served portions by parent order and line.

  6. 06Batch release decisions

    Show submitted ticket revisions beside reviewer decisions and decision dates.

  7. 07Operation exception register

    List failed or review-needed receipts with operation keys and failure reasons.

  8. 08Consumption by ingredient

    Sum signed quantities by ingredient, unit and occurrence date.

  9. 09Unverified payment events

    Show provider events awaiting verification by type, amount and parent order.

Controls

Trace revisions and performed effects

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

OverviewRecipe to reviewed service
Recipe Management System · Process

Recipe to reviewed service

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

Process stages
11
Approval steps
1
Roles involved
5
Tables touched
13
Accept order
Order Coordinator
StatusDraft → Accepted
RecordsOperation receipts
Prepare lines
Kitchen Operator
StatusAccepted → Preparing
RecordsStock consumptions, Production lines, Kitchens
Submit batch
Order Coordinator
StatusDraft → Submitted
RecordsBatch tickets
Recipe to reviewed service
  1. Start
    Accept orderDraft → Accepted
    Operation receipts
  2. Step
    Prepare linesAccepted → Preparing
    Stock consumptions
  3. Step
    Submit batchDraft → Submitted
    Batch tickets
  4. Approval
    Review batchSubmitted → Approved
    Review decisions
  5. Step
    Release and servePreparing → Ready → Served
    Fulfillment events
Example screen with sample data
AI agent

Prepare reviews with Proto

Ask Proto to prepare record reviews and exception checks for your team.

It can

  • Recipe Owner: Compare a proposed recipe revision with its ingredient yields and allergen declarations before human review.
  • Order Coordinator: Assemble the menu, portions, kitchen and planned service context for an acceptance check.
  • Kitchen Supervisor: Gather the submitted batch revision, supporting attachments and parent order for a decision.
  • Reconciliation Analyst: Compare a failed operation receipt with decisions, local effects and external references.

Stays with a person

  • Proto can organize the record context and prepare checks.
  • The named people retain recipe approval, batch review and correction decisions.
  • Provider and fulfillment outcomes require their actual evidence.
  • A prepared answer does not change a ticket to Completed until the effects have been persisted and verified.
Integrations

Connects to the tools you use

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

  • Recipe Management System
  • Payment provider
  • Fulfillment source
  • Identity
  • Files
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
  • Ingredients and yields4
  • Recipe cards and menu items4
  • Order acceptance6
  • Kitchen production6
  • Batch release5
  • Exceptions and evidence8
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 ownership

    Set organizations, kitchens, team members and the people who prepare, review and reconcile work.

  2. Prepare recipes

    Enter ingredient units and declarations, menu items, recipe cards and yield lines; review a representative revision.

  3. Run an order

    Accept an order after menu, allergen and capacity checks; prepare lines and record served portions.

  4. Review a batch

    Submit a ticket, record the independent decision and verify that release effects persisted.

  5. Reconcile exceptions

    Test a failed receipt, partial service, changed scope and a provider event before extending the operating cycle.

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 Recipe Management System.

All questions
How do I get started?

Click Get started, then use Proto to configure Recipe Management System for your business. Pilot one organization, one active kitchen, a small approved menu and one service cycle you can reconcile.

How are recipe revisions handled?

Each recipe card has a revision number, effective date, portion yield and approval state. Review the linked ingredient quantities before using the revision for new kitchen work.

Can a recipe be used before review?

The Recipe Reviewer reviews the preparation basis. Kitchen release follows the approved revision associated with the accepted order.

What does order acceptance check?

The Order Coordinator checks menu products, portions, allergens and service capacity, then records the accepted time and calculated net amount.

Is prepared food the same as served food?

No. Prepared time and served portions are recorded separately on the production line. Stock consumption records ingredient use and waste.

Who releases a batch ticket?

The Kitchen Supervisor independently decides the submitted ticket revision. The guarded release is completed after its effects have been persisted and verified.

What happens when an order changes after acceptance?

The team reviews the current revision, lines and performed scope before a compensating action. Original records remain available to explain the change.

How are refunds checked?

Provider issued refund evidence carries an event ID, reference, amount and verification state. The analyst compares it with the authorized scope before closing the result.

How are failed operations investigated?

Operation Exceptions shows failed and review-needed receipts. The analyst compares the expected revision and operation key with decisions, local effects and external references.

Can I bring existing recipe data?

Prepare stable ingredient codes, menu SKUs, recipe revisions, units, yields and approval context. Rehearse the migration on a small menu before adding historical orders.

Set up Recipe Management System 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 appRecipe Management System

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.