These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recipe / Formulation Mgmt
- Features
- Recipe versions
Recipe versions
Keep the formulation version, base yield and intended production work together for a reviewable batch basis.
OverviewRecipe Review Queue×
Recipe / Formulation Mgmt · Recipe versions
New
Recipe Review Queue
Recipe versions
| Id | Recipe name | Version | Base yield | Yield unit | Operational record | |
|---|---|---|---|---|---|---|
| IDD-720 | Recipe 629 | Rev A | 80 | YU-627 | WO-6415 | |
| IDD-690 | Recipe 645 | Rev B | 140 | YU-402 | WO-2624 | |
| IDD-103 | Recipe 910 | Rev C | 890 | YU-639 | WO-7093 | |
| IDD-757 | Recipe 580 | Rev D | 430 | YU-114 | WO-9907 | |
| IDD-437 | Recipe 797 | Rev E | 210 | YU-462 | WO-9411 |
6 of 6 records
IDD-720Recipe versions · RV-54565
ReviewRecipe nameRecipe 629
VersionRev A
Base yield80
Yield unitYU-627
Operational recordWO-6415
What you can do
Establish the formulation basis
A batch decision starts with knowing which formulation the team intends to use. The recipe version records its name and version alongside the base yield and yield unit. Its linked production work gives Production Planner the intended product and planned quantity to inspect before the operator records ingredient evidence.
Agree a version naming convention that staff can recognize during a shift. A familiar label does not replace the team’s review of its ingredients and yield basis. Use Draft while preparing the formulation, Review when it enters the agreed review route, and Released after the authorized decision. Keep Retired versions distinguishable when staff look back at earlier production.
How the work is organized
Production Planner prepares the definition and production link. Production Operator reads that basis while capturing ingredient evidence. Quality Reviewer inspects the version in its production context. Agree the recipe reviewer and rehearse submission during setup so each person understands where preparation ends and a decision begins.
- Version identity. Use the recipe name and version to identify the formulation being discussed, then open that exact record before recording work.
- Yield basis. Keep the base yield and its unit beside the ingredient amounts so the planner can explain the calculation for a planned batch.
- Production context. Follow the linked work order when reviewing the finished product, approved customer demand and intended production quantity.
What to agree during setup
Agree who maintains the version naming convention and who resolves contradictory ingredient declarations. Decide how the operator submits a version for review and how the reviewer records the outcome. Test the route with ordinary team accounts before using it for operating decisions.
Choose the quantity basis for each product. The planner should be able to explain what the base yield measures and how ingredient units relate to it. If a formulation uses liters while the finished product is planned in kilograms, obtain an agreed conversion basis from the responsible source owner before calculating amounts.
Check the handoff on an actual case
For a rehearsal, use a formulation with a base yield of 100 kg and linked production work planning 250 kg. Production Planner reviews a factor of 2.5 after confirming the product quantity uses the same unit. An ingredient amount of 20 kg for the base implies 50 kg for that plan. Check the calculation with the person who owns the formulation before releasing production work.
Repeat with a changed ingredient and a new version label. Open the original formulation and confirm that staff can still identify its yield basis and linked work. Ask the operator to show which version the new ingredient evidence belongs to. This catches a misleading handoff where the amount is correct but the record points to an earlier recipe.
Include a mixed-unit example in the rehearsal. The planner should flag the unresolved conversion, obtain the source basis and explain the reviewed result. Record the team’s naming and unit choices in the setup decisions so another shift can repeat the same interpretation.
What your team sees
- Recipe Version Register — Inspect the version, yield basis and status beside its intended production work.
- Recipe Review Queue — Review formulations marked Review using the team’s agreed decision route.
Follow the work through
Use recipe preparation to rehearse the version basis, then production release to check the work-order decision. Review the data model before importing version history.
What it keeps track of
Data model- Recipe versions
- Versioned recipe and formulation definitions with base yield.
- Recipe ingredients
- Ingredient quantities, units and allergen declarations per recipe version.
- Work orders
- Released production work for a product, order and resource.
- Items
- Materials, components and finished goods with standard cost and unit of measure.
Who uses it
Permissions- Production Planner
- , Production Operator, Quality Reviewer, Admin.
- Production Planner
- Owns formulation preparation; Admin coordinates account and review-route setup.
Set up Recipe / Formulation Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.