How to build a shortlist of co-packers, vet each one with a real question list, and set the relationship up in writing — starting with who owns the food-safety plan and who keeps each traceability record when someone else runs the line.
Do these first
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.
By the end of this lesson you can go from "a co-packer might be right for us" to three things you can act on: a short list of real candidates, a question list that separates the ones that fit from the ones that don't, and a written agreement that says — in plain words — who owns the food-safety plan and who keeps each traceability record. You already decided whether to hand off the making in what a co-packer is, and when it makes sense. This lesson is the practical next step: how to find one, how to vet it, and how to set up the relationship so the food safety and the traceability don't fall through the cracks between two companies.
There is no single directory of co-packers, so finding one is mostly legwork. A that fits your product usually turns up through a handful of channels, and none of them is better than the others on paper:
However you find them, vet every candidate the same way. How you got the name tells you nothing about whether the plant can make your product safely.
Before you fall for a plant, do the arithmetic on its minimum. A co-packer works to a , usually charges a setup fee for the first run, and quotes a lead time measured in weeks. Those three numbers decide whether the relationship is affordable, so get them in writing early.
The number that bites is the minimum against your cash. Multiply the minimum order quantity by your per-unit cost and you have the money tied up in a single run — money you don't get back until the product sells. So the real test is sell-through: can you move that run before it reaches its shelf life? A minimum you can sell through in a season is a working relationship. A minimum that leaves you sitting on stock until it ages out is a slow loss, however good the per-unit price looked.
Every minimum, fee, and lead time swings enormously by co-packer and by product. Treat any figure you hear — in a directory, from a broker, in a first call — as typical until a real quote for your product is in front of you, never as a fixed rule.
Choosing a plant is only half the setup. The other half is moving your recipe into it — the work called . This is where control quietly stays with you or quietly slips away, so it's worth doing deliberately.
What you hand a co-packer is not a recipe card — it's a written manufacturing specification precise enough for a crew you'll never meet to run without you standing there. That means exact quantities scaled to their batch size, the order and timing of every step, the target and limits for anything that matters (a cook temperature, a final pH, a fill weight), and the packaging spec. Turning a kitchen recipe into that kind of documented bill of materials and yield is its own skill; recipes, BOMs, and yield walks through it.
Two habits keep the product yours through the handover. Run a small first batch — a pilot — and taste and test it against your spec before you commit to a full run, because a plant that can't hit your spec at small scale won't hit it at large scale. And keep the final say in writing: you approve the specification, and no change to it happens without your sign-off. Whoever holds that final say is the one really in charge of the product. The next lesson goes deeper on turning a kitchen recipe into a documented, scalable, shelf-stable process — what you actually hand a co-packer — so treat this as the outline and that as the detail.
Vetting is just a good question list, asked before you commit and grouped so you can compare plants side by side. Work three groups.
Fit and capacity. Can you make my product and my process? What's the minimum order quantity and the lead time? Do you have spare capacity during my busy season? Who are two brands like mine I can call for a reference? A plant that makes your category every day is worth more than one taking you on as an experiment.
Food-safety credentials. What food-safety certification does the plant hold, and when was its last audit? Certifications like SQF, BRCGS, and FSSC 22000 are benchmarked by GFSI, and a buyer or a retailer may require a specific one for your finished product — but which certification you need, if any, is usually a customer expectation rather than a federal rule. Whether you even need a GFSI certification is its own decision. If your product carries allergens, ask exactly how the plant separates them from everything else it runs.
Ownership and records. Who owns and maintains the food-safety plan for my product's runs? Who keeps the lot records? And what are the recall roles — who runs a mock recall, who notifies whom, and who pulls product if it comes to that? These are the questions first-timers forget, and they're the ones the next section turns into contract language.
A certificate is a floor, not the whole answer
A plant can hold a current certification and still be a poor fit for your product — wrong allergen profile, no capacity in your season, a quality culture you'd fight. Read the certificate as the price of admission, then visit the plant and call the references anyway. The audit tells you the room passed on one day; the references tell you what running with them is like.
Here's the thread that runs through this whole course, now made practical: hiring a co-packer moves the making, not the owning. When someone else runs the line, two owners exist at once, and the co-packing agreement is where you name them — because a handshake won't hold up when a buyer or an auditor asks who kept which record.
The co-packer owns and runs the for its own plant. Inside those walls it works under federal Good Manufacturing Practices and, where the preventive-controls rule reaches the facility, keeps its own written food safety plan — the hazard analysis and preventive controls in 21 CFR Part 117 (verified July 2026). Where it buys ingredients to your spec, it also runs a supplier and supply-chain program for what it receives. None of that makes the whole food-safety story theirs. You still own your product's specification, your label, and your side of the traceability chain.
Traceability is the clearest case of two owners at once. Under the FDA's Food Traceability Rule (FSMA 204), each company in a supply chain keeps its own records for the events it performs and passes the required details to its partner so the chain links up — the co-packer records what it received and produced, you record what you received from them and shipped onward, and one party's records never cover for the other's (FDA, Food Traceability Rule, verified July 2026). That rule covers foods on the FDA's Food Traceability List, so whether your product is even on the list is the first thing to settle, and what FSMA 204 asks you to record is the detail.
The enforcement date has already moved once
As of July 2026, the FDA has said it will not enforce the Food Traceability Rule before July 20, 2028 — the original January 20, 2026 date was pushed back. The recordkeeping logic doesn't wait for the enforcement date, and the date itself has already changed once, so confirm the current one on the FDA's Food Traceability Rule page rather than trusting any single number.
So a has to name, in plain words: who owns the food-safety plan for your runs, who keeps which lot records, and who holds each recall role. Which party keeps which record is not something to assume — if it isn't in the contract, it isn't anyone's, and a recall is a terrible time to discover the gap.
You have the shape of the whole relationship now: find candidates, vet them with a question list, pin the ownership of the food-safety plan and the records in writing, and transfer your recipe without giving up the final say over it. What's left is the thing you actually hand a co-packer — a recipe turned into a documented, scalable, shelf-stable process — and that's where this course goes next.
Do this in your operation