How to keep a trace and a quality release intact when production crosses into a company you do not own — who holds which lot records, who can release or hold product, and how lot data has to pass with every shipment both directions.
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.
After this lesson you can look at any co-manufacturing relationship and name the three things that keep it from breaking your traceability: who keeps which lot record, who can release product and who can hold it, and how lot data moves with every shipment in both directions. The aim is that a trace and a recall still run end to end even though the step where your product is actually made lives inside a company you do not own — and that the split of who-does-what is written into an agreement, not left to habit.
Everything in the last lesson assumed both ends of every move were yours. The moment you hand production to a partner, that stops being true. A transforms your inputs into finished goods on their floor, in their system, under their own records. You still own the product and answer for it to your customers and to a regulator. But you only half control the step where it is made.
That gap turns a single-company product into a . Your ingredients might go to the co-manufacturer, become a batch, ship back to you or straight to a distributor, and reach the retailer — three or four companies, each holding one link of the trace. The discipline is the same transfer-and-record shape you already keep across your own sites. What changes is that one link now sits inside records you cannot see into and cannot fix, so the connections between links have to be arranged on purpose, in writing, ahead of time.
Start from the floor you already owe. is kept by each company for its own moves. When the chain was all yours, those links joined up because you held both halves of every handoff. Across a company line, each side holds only its own half, and the trace runs end to end only if those halves connect.
The hard part is where the genealogy seam sits. The link that ties a specific ingredient lot to the specific finished lot it ended up in is created at the moment of transformation — the batch. In a co-manufacturing arrangement, the co-manufacturer runs that batch, so that link lives in the co-manufacturer's records, not yours. For foods on FDA's Food Traceability List this is written into the rule: under 21 CFR 1.1350, whoever transforms a listed food keeps the records linking the input lot codes to the new output lot code. That is your co-manufacturer, not you. (The FSMA-204 lesson works through those events and records in full; here the point is only where they sit when a partner runs the batch.)
So picture what you actually hold. When the co-manufacturer ships you the finished goods, you record a receipt — the finished lot code, the quantity, where it came from. That is your one link back: the finished lot came from this co-manufacturer. It does not tell you which of your ingredient lots went into it. If a supplier later calls about one bad ingredient lot, you can name the co-manufacturer it went to, but you cannot say which finished lots it became — because the batch record that would answer that is on the co-manufacturer's side of the line. Without an arrangement to pass that data, a trace that used to be a lookup becomes a phone call to another company, and a recall that should be narrow goes wide.
Because the genealogy seam sits with the co-manufacturer, the two companies have to agree, in writing, on who keeps which records and who hands what to whom. The legal floor is that each partner keeps its own records for its own events — the co-manufacturer keeps the transformation and its shipping records, you keep your receiving and your onward shipping records. But the floor only guarantees each pile exists; it does not guarantee they connect into one trace you can run. The contract is where you close that gap.
Who assigns the finished lot code, and how
One lot code has to identify each finished batch, and it has to be the code both of you reference. Usually the co-manufacturer assigns it at the batch; agree the format and that it appears on every case and every shipping document, so the same code threads through both companies' records.
Who keeps the batch genealogy — and whether it comes to you
The co-manufacturer holds the input-lot-to-finished-lot link by default. Decide whether that link is passed to you with each lot, or stays with them to be produced on request. Passing it means your own records can answer a trace without a call; leaving it means you depend on their speed when the clock is running.
Who holds the batch record, retention samples, and certificates
Batch records, retained samples, and any certificates of analysis are part of the trace. Name who keeps each, for how long, and how fast the other party can get a copy. For listed foods the record-retention and 24-hour production expectations of the Food Traceability Rule apply to whoever holds the record.
Who owns the food safety plan for the manufacturing step
This is the question co-manufacturing relationships most often leave fuzzy. The company running the process typically owns the hazard analysis and food safety plan for that step, while you may carry supply-chain responsibilities for controlling a hazard through them. Do not assume it — write down who owns which, and confirm at the source which requirements land on your operation.
A single company holds and releases its own product. A release chain has more than one company that can do either, and the two have to be wired to talk.
A is the gate at each link. Its mirror is a . In a chain these stop being purely internal. If the co-manufacturer's finished-product test comes back out of spec after they have shipped, they need a way to reach forward and stop the lot at your dock and at every customer downstream. If you find a problem after receipt, you need to reach back to the batch and forward to whoever you already shipped. A hold at any link has to be able to stop the product at every link downstream of it — that is the whole point of holding.
So two things have to be agreed. First, who holds release authority at each handoff: does product ship on the co-manufacturer's release alone, or does it wait for your sign-off too? Second, the notice path in both directions — how a hold or a withdrawal raised at one company reaches the others, and how fast. Slow notice is the failure mode. Your retail customers often expect you to trace a lot and reach everyone affected within a couple of hours; that is a customer and industry expectation, not a clock written into any certification standard — SQF Edition 9, for instance, requires that your recall system be tested and verified at least annually and trace one step each way, but it sets no two-hour limit. A chain fails that expectation the moment one company in it takes a day to answer.
The connective tissue of the whole chain is lot data riding along with each shipment. Treat every shipment across a company line as carrying two things: the goods, and the records that let the next company trace them.
The test is simple to state and worth actually running: pick one finished lot your co-manufacturer made and try to trace it end to end — back through the batch to the ingredient lots, and forward to your customers. Every place the trail crosses a company line is a place a shipment either carried the lot data or dropped it. Where it dropped, you have found a link to fix before an auditor or a recall finds it for you.
You have now reached the far end of scaling the operation. You can make the product and trace it, buy for it with discipline, scan it on the floor, and run it across more than one site and more than one company — including companies you do not own. The wheels stay on because every handoff carries its lot and every record connects to the next.
What is still missing is money. You can run all of this cleanly and still not know what a batch truly costs you or whether you are charging enough to keep the doors open. That is the next track: knowing your numbers — building true cost from your recipes up, and protecting the margin that all this operational discipline is meant to earn.
Do this in your operation