Cut a recipe into numbered versions, collect the sign-offs each one needs, and set the one version your floor is allowed to run.
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 reworked your marinara to cut the sodium, saved it, and now you want the kitchen making the new formula — but not before your quality lead has looked at it, and not in the middle of a shift that's already weighing to the old target. Bettr keeps the two apart. A run only ever cooks the version your approvers signed off, so saving an edit never quietly changes what the floor is making today. You control that hand-off from the recipe itself, under Recipes.
Kitchen+Every time you save an edit, Bettr keeps it as a . A revision on its own is just history. To send a recipe up for sign-off you freeze one revision as a . Once approved, that becomes the recipe's .
Versions live in the Versions panel, at the bottom of a recipe's Last version tab. It lists every revision, newest first, and marks which ones have been frozen into a numbered version.
Open a recipe and find the Versions panel
From Recipes, open the recipe you want to version. Scroll to the Versions panel on the Last version tab and select Create version.
Pick the revision to freeze
Choose which revision this version captures — usually the most recent, at the top. Each revision can back only one version, so a revision that's already been frozen won't appear in the list.
Number it, then create
Leave Version number blank and Bettr assigns the next number in order, or type a higher one to skip ahead. Select Create version. The new version lands in the panel marked Pending — frozen, numbered, and waiting on its approvers.
Set your approver roles before you cut a version
A version needs at least one role to sign it off. If none are set, the Create version dialog prompts you to set them on the recipe's Edit page first. See Create a recipe for where approver roles are chosen.
A Pending version needs a decision from each of its approver roles. Select Details on the version to open its approvals panel: one row per required role, each showing whether it's Pending, Approved, or Rejected, and who decided.
Open the version's Details
In the Versions panel, select Details on the version. The panel lists every approver role and where each one stands.
Decide as a role you hold
If you hold one of the required roles and this is the latest version, Approve and Reject appear on that role's row. Approving records your sign-off for that role; someone who holds a different required role signs off on theirs.
When the last required role approves, the version flips to Approved. If the recipe was still a Draft, approving its first version also makes the recipe Active — ready to run. Only the latest version can be decided, so a change you're still working out never blocks the version the floor is on.
A rejection ends the version
Rejecting a version closes it for good — you can't revive it. To keep going, fix the recipe and cut a new version for a fresh round of approvals. That way the record shows exactly what was turned down and why a later version replaced it.
When you want to develop a change without disturbing what the floor is running, branch it instead of editing the live recipe. Branching opens an .
Branch a version
Open the recipe's R&D recipes tab. Under Branch a version, select Edit this version on the version you want to start from. Bettr creates an R&D recipe with the same ingredients, steps, and approver roles, and drops you into it.
Evolve it safely
Edit the R&D recipe, cut versions on it, and collect approvals — all the same way as the main recipe. Nothing you do here reaches the floor, because a run still pulls the main recipe's production version.
Copy it back to the main recipe
When the change is proven, open the R&D recipe and select Copy to main recipe. Its current ingredients and steps overwrite the main recipe as a new revision. The branch is left as it is and no approvals restart — so you then cut and approve a version on the main recipe to put the change into production.
Copying a branch back is one way to ship a change. The other is to point the floor straight at the branch. A branch that has its own approved version can take over as the production version, so you can cut over to a reformulated recipe without touching the main one.
Approve a version on the branch
On the R&D recipe, cut a version and get it fully approved.
Set the branch as production
Select Set as production. Runs now pull this branch instead of the main recipe, and its header is marked Production version.
Clear it to fall back
Select Clear production version to unpin the branch. Production falls back to the main recipe's approved version.
The main recipe is the production version by default
You only set a production version to promote a branch ahead of the main recipe. With no branch pinned, a run pulls the main recipe's approved version on its own — approving it is all it takes to reach the floor.
When you stop making something, deactivate it so it drops out of production. On the recipe's Edit page, select Deactivate — the recipe's status becomes Inactive and it stops feeding runs. Its history stays intact; nothing is deleted. To bring it back, use the Change status control on the same page to move it to Draft or Active.