Every field, badge, and state on the recipes list and a recipe's detail — recipe types, statuses, versions and approvals, allergens, and documents, and where each value comes from.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
You pull up your marinara to settle a question from the floor: is the kitchen weighing to the version your quality lead signed off, or an older one? The answer is in the badges — the recipe's status, its latest version, whether that version is the one runs are allowed to pull. A carries a lot of state, and this page is the key to all of it, so you can read one at a glance and know exactly what it will do on a run. Open Recipes under Production to read along. Kitchen+
The list holds every recipe in the company you're working in, one per row. The controls above it:
New sits in the top corner and opens the recipe form; it shows only if your role can create recipes. When the list is empty, it reads No recipes yet.
Reading a row left to right, then down:
Every recipe is one of two types, shown as the first badge on its row and in its header:
The status badge is the recipe's own lifecycle, separate from any version's approval state:
Selecting a recipe opens its detail page. Its header carries the same two badges the list does — the recipe's type and status — above a strip of tiles that gives the summary; the sections below hold everything a batch is built from.
The Ingredients section lists each line with a badge marking it a Product or a Sub-recipe, its quantity in the entered unit and in pounds, and — where some is lost in the make — a badge for the extra it adds to cover that loss. Alongside the heading, a running total cost and cost per pound or unit show what a batch costs. When a line is a sub-recipe, its own ingredients roll up under Compiled sub-ingredients.
The Allergens section is derived, not entered: Bettr reads the allergens off every ingredient product and sub-recipe and lists each one with the ingredient it came from, so a recipe's allergen profile always matches what's actually in it. Where allergens are set on a product is covered in the Products reference.
Production steps are the method, numbered in order. Each step shows its instruction and, where they apply, the equipment it runs on, whether it needs a weight capture, its batch weight range and temperature range, and an expected duration. A step can also carry , shown as thumbnails on the step.
Run configuration holds the rules a run enforces for this recipe:
A recipe holds up to four Documents, one per type: SOP document, Quality forms, Safety procedures, and Final product photos. Each shows its filename and opens the file. Links are external URLs — an SOP or a spec sheet — each with an In production badge when it's set to show on the floor. Attaching documents and step media is covered in Attach recipe documents and step media.
Editing a recipe never changes what the floor is making. Every save is kept as a , and to send a recipe up for sign-off you freeze a revision as a numbered version. The Versions panel, at the bottom of the Last version tab, lists every revision newest first and marks which ones have been frozen.
The badge on a version tells you where its approvals stand:
Only the latest version can be decided
Approvals happen on the newest version, so a change you're still working out never blocks the version the floor is on. The Approved version tab always shows the version a run pulls, even while a later one waits for sign-off.
A recipe's detail opens on one of three tabs:
By default a run pulls the main recipe's approved version. You can point it at a branch instead: a is set with Set as production and marked with a Production version badge in the header. Clear production version hands the floor back to the main recipe.
An R&D recipe is a branch you develop without touching what's running: Copy to main recipe writes a branch's ingredients and steps back over the main recipe as a new revision. The full flow is covered in Version and approve a recipe.
Access to recipes is set per role, under Production in the permission catalog:
Approving a version takes more than a permission. A signer needs Edit recipes and must also hold one of the approver roles chosen on the recipe, so who owns quality is decided recipe by recipe.
There is no delete
A recipe can't be deleted — every plan, run, and batch record points back to the recipe it was made from, and erasing it would break that trail. Deactivate it instead: its status becomes Inactive, it drops out of production, and its history stays whole.