Change a recipe.
With a paper trail.
Propose a change to a recipe or a bill of materials, see its cost and allergen impact, collect role approvals, and apply it on a date. Orders already made keep the version they started with.
What you get
Change a recipe. With a paper trail.
Change orders
Propose a new recipe or bill of materials with a reason and an effective date; it moves draft, review, approved, applied.
Impact before approval
On submit, approvers see line differences, cost per unit and per month, allergens added or removed, and what depends on the item.
Role approvals
Required roles must sign off; nobody approves their own proposal except the owner; a stale base version is refused.
Version history
Each recipe lists its versions with the change behind them, and any version can be brought back as a new change.
Controlled recipes
Mark a recipe as controlled so its formula changes only through an approved change order, even outside the screens.
Effective-date activation
Approved changes take effect on their date; orders already made keep the bill they started with.
How it works
Three steps. That’s it.
- 1
Pick the item
Open Quality or Manufacturing, Changes, and choose the recipe or bill to change.
- 2
Propose and submit
Edit the proposed version, give a reason and an effective date, and submit for review.
- 3
Approve and apply
Approvers sign off by role; the new version goes live on its date.
Works with
Connected to the rest of STAK.
Your whole business. One stack.
Reserve your free workspace now. One main app free forever.