What a co-packer actually needs from you, what you should never send, and how versioning, share links, and a batch record keep the formula yours while someone else makes it.
Published October 14, 2026 · By Formulate 360 Team· Topics: contract manufacturer cosmetics, co-packer formula, send formula to manufacturer, formula version control, batch record, private label skincare
The moment you send a formula to a contract manufacturer is the moment you stop being the only person who can make your product. That is the point, and it is also where most indie brands lose the plot: the formula goes out as a spreadsheet attachment, gets edited on both sides, and six months later nobody can say which version is in the jars on the shelf.
This is the handoff done properly. It is not complicated, but it has to be deliberate.
Spreadsheets have no memory. You can overwrite v3 without noticing, you cannot see what changed between two sends, and a shared Google Sheet means the manufacturer's edits and yours collide. A formulation workspace keeps every version, shows the diff between them, lets you hand out time-limited read-only links, and generates the batch record from the version the batch was actually pinned to. That last part is the one spreadsheets really cannot do: the batch record must reflect the formula as it was when the lot was made, not as it is today.
CONFIRMED In Formulate 360 every save that changes the formula creates a version with a diff you can read; share links expire, can be password-protected, and hide costs by default; and a batch is pinned to the version it was made from, so the batch record PDF prints what was actually manufactured. Start free.
Should I give the manufacturer my full formula or only part of it?
For them to make it, they need all of it. What you control is the form: read-only, versioned, without your costs and suppliers. If you want a partial disclosure, you are looking at a split-manufacturing arrangement, which is a different conversation.
What if the manufacturer wants to substitute an ingredient?
That is normal and often sensible. Treat it as a change request: they propose, you decide, and if you accept it becomes a new version on your side before they make anything with it.
Do I need an NDA?
Usually yes, and a good manufacturer expects it. An NDA covers the legal side; versioning and revocable links cover the practical side. Use both.
How long should I keep batch records?
Keep them for the life of the product on the market plus the longest period in which a complaint could reasonably arrive. For many brands that means several years. Storage is cheap; not having the record is not.
Keep reading