A co-packing contract says what the product costs and when it's delivered. A quality agreement says who does what to keep the product right. It's a separate, shorter document, usually written as a table: a list of topics, and beside each, what the brand owner does and what the co-packer does. Who signs the specification. Who approves a change of supplier. Who releases a batch to ship. Who hears a complaint, who investigates, and how fast. Who decides on a recall. Most of it is never needed, until the day a run comes out wrong, and then it's the only page anyone wants. Below are 14 topics with example wording in plain English, the four that cause the arguments, and a file to adapt. It's a starting point, not legal advice.
The short version
- One table: topic, what the brand owner does, what the co-packer does.
- Every responsibility has exactly one owner. "Both" means neither.
- Put a clock on anything urgent: one business day, 4 hours.
- Product stays on hold until someone named releases it.
- Agree the recall roles before there's a recall, and practice once a year.
- TaroStack keeps each client's runs, lots and holds apart, and reports them. More below.
The topics
| Topic | Brand owner | Co-packer |
|---|---|---|
| 1 Products and specifications | Supplies and signs each specification | Makes to it |
| 2 Changes | Approves or refuses in writing | Asks before changing anything |
| 3 Ingredients and packaging | Approves suppliers of what it supplies; sends documents | Approves suppliers of what it buys; inspects everything |
| 4 Allergens | Declares every allergen in its recipe | Declares every allergen in the plant; controls cross-contact |
| 5 Lot codes and batch records | Agrees the code format | Codes every unit and case; keeps a batch record |
| 6 Testing and release | Releases, or names who does | Tests; holds until released |
| 7 Deviations | Decides what happens to the product | Tells the brand owner within one business day; holds |
| 8 Complaints | Receives them; sends the lot code | Investigates within 5 business days |
| 9 Recalls | Decides; notifies customers and regulators | Supplies records within 4 hours; holds stock |
| 10 Audits and inspections | Gives notice | Allows audits; reports regulators' findings |
| 11 Labels | Approves every label | Uses only approved labels; counts them in and out |
| 12 Storage and shipping | States conditions | Stores and ships as stated, oldest first |
| 13 Records | May ask for copies | Keeps records for the agreed time |
| 14 Contacts and review | Names a quality contact | Names one, with an out-of-hours number |
The file has example wording for each.
The four that cause arguments
Changes. A co-packer's oat supplier runs short and it buys from another. To the co-packer that's keeping the line running. To the brand owner it may be a different allergen statement, a broken gluten-free claim, or a changed taste. The clause says the co-packer asks first, in writing, and waits: for an ingredient, a supplier, a process step, equipment that touches the product, or the site. List them. "Significant changes" is an invitation to disagree about what's significant.
Release. Who says a batch can ship? If nobody is named, product ships when the truck arrives. The usual arrangement: the co-packer tests and sends results, the product sits on hold, and the brand owner releases it in writing. A brand owner who doesn't want that job can delegate release to the co-packer's quality person, by name, against a written checklist.
Deviations. A run finishes with a pH over the limit, or fifty cases with the wrong label. The co-packer's duty is to hold it and say so within a day. The decision (release, rework or destroy) is the brand owner's, because it's the brand owner's name on the pack. Who pays is for the commercial contract. A quality agreement that stays silent leaves the co-packer deciding alone at 6 PM on a Friday.
Recalls. Three questions, each with one answer. Who decides? Usually the brand owner. Who tells customers and regulators? Usually the brand owner. What does the co-packer do? Hands over batch and shipping records fast and holds everything affected. Put a time on "fast", and then test it: a mock recall, run together, once a year. The exercise is in mock recall and traceability exercise.
Clocks
| Event | Example time |
|---|---|
| Tell the brand owner of a deviation | 1 business day |
| Reply to a complaint investigation | 5 business days |
| Supply records for a lot in a recall | 4 hours |
| Report a regulator's finding that concerns the product | 1 business day |
| Notice before an audit | 10 business days; none for cause |
Promise only what you can do. A co-packer whose batch records are paper in a filing room shouldn't sign "4 hours" without trying it first.
What it isn't
It isn't the commercial contract: prices, minimums, payment and liability go there, in co-packing agreement template. It isn't the specification either. That's a document of its own for each product, in product specification sheet. The quality agreement points to both.
It also doesn't move legal duties around. Each side has its own obligations under food law whatever the agreement says, and a lawyer should read your version. What a co-packer is, and how to choose one, is in what is a co-packer and how to find a co-packer.
Get the template
Download the quality agreement template. Fourteen topics, each with what it settles, what the brand owner does, what the co-packer does, and example wording, plus a read-me. Change every name and time limit to your own. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. It's general information, not legal advice.
Where this stops working
The agreement says: batch records within four hours, product on hold until released, only this client's materials in this client's runs. Each of those is a promise about records. If the co-packer's holds are a sign on a pallet and its batch records are a clipboard, then "on hold" lasts until a forklift driver on the next shift needs the space, and four hours becomes a day in the filing room.
How TaroStack does it
TaroStack makes the promises in the agreement into things the system does.
Holds are real. A run on hold is kept out of what can be sold or released until someone releases it.
A toll run uses that client's goods and yours, never another client's, and records every material it used and whose each was.
Batch records note which lots were consumed, automatically, with your own checklist fields (pH, label check, sign-off) on the same record.
Releases. A client's goods go out only on a release to that client.
One report for a recall, in minutes: which lots went into which runs and where the product went. Timed, logged drills show that it works.
A monthly statement for each client, by lot.
| The promise | Paper | In TaroStack |
|---|---|---|
| On hold until released | A sign on a pallet | Held: can't be released by accident |
| Records within 4 hours | The filing room | One report |
| Only this client's materials | Care and labels | The run takes only that client's goods |
| A yearly mock recall | A day's work | A timed, logged drill |
TaroStack doesn't write agreements or decide a recall. Copacking is on Business, $89 a month, with 5 active clients; a brand owner keeping its own lots and recalls can start on any plan, from $9.99 a month. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
