# Every client recipe, every version kept.

For co-packers and co-manufacturers: keep every client recipe and every change, and trace each label back to its version.

[Start free](https://studio.bettermenu.live/signup) [Talk to a founder](https://cal.com/harit/bettermenu)

[See pricing](https://bettermenu.live/pricing/)

Studio, real UI: a sample recipe’s versions, two of them compared line by line

## What can a co-packer do in Formulate today?

Keep each client recipe with every version, check a swap before the run, and trace each label to its version.

Figure: A co-packer’s workflow: client recipes kept, an ingredient swapped as a new version, the two versions compared, the label exported with its version Four steps for a sample client recipe. 1. Keep: client recipes in one account, each with its versions (Granola for Client A at v4, Protein bar for Client B at v7, Cookie dough for Client C at v2). 2. Swap: before the run, sunflower oil becomes coconut oil, 30 g, saved as version 5. 3. Compare: version 4 and version 5 on the printed values: calories 250 and total fat 9g stay, saturated fat moves from 0.5g to 3g. 4. Export: the label, with a proof footer naming Granola, version 5.

[See how Prove works](https://bettermenu.live/formulate/prove/)

Free to start. No card needed.

[Start free](https://studio.bettermenu.live/signup)

[See pricing](https://bettermenu.live/pricing/)

## Which client recipes use an ingredient?

Each custom ingredient lists the recipes that use it, so a supplier change shows every recipe it touches.

Figure: One custom ingredient and the three client recipes that use it A custom ingredient, Rolled oats, Lot 22, added once from the supplier’s spec sheet. It lists the 3 recipes that use it: Granola for Client A, Oat Date Bars for Client B, Breakfast cookies for Client C. When the supplier changes the ingredient, these are the recipes to check.

[How custom ingredients work](https://bettermenu.live/platform/ingredient-data/#custom-ingredients)

## Can each client get a workspace and sign-off?

Each client’s recipes live in your one account, every version is kept, and each label’s proof footer names its version, on by default. For separate client workspaces, [talk to a founder](https://cal.com/harit/bettermenu).

Questions

## More questions

### How do I check a substitution before the run?

Change the ingredient, save, and compare with the last version to see the panel move. Restore it if the swap falls through.

### How fast can I enter a new client recipe?

Paste it. AI matches each line to a USDA food, estimates a weight only when none fits and, in Studio, suggests the added sugars. You review each one and change any, and the compliance engine does the math. We send recipe lines only to AI providers that do not train on them and keep none of them after answering.

### Can my clients sign in to see their recipes?

Not today. Send clients the exported label file itself. Its download link expires.

## Read next

- [Prove Every change is a version. Compare and restore.](https://bettermenu.live/formulate/prove/)
- [Security How your recipes are stored and who can see them.](https://bettermenu.live/platform/security/)

## Bring one client recipe.

Free to start. No card needed. For several clients or a team, talk to a founder. [See pricing](https://bettermenu.live/pricing/).

[Start free](https://studio.bettermenu.live/signup) [Talk to a founder](https://cal.com/harit/bettermenu)

Source: https://bettermenu.live/solutions/co-packers/