Co-Packer Quality Agreements: What Food Brands Miss

The shipment arrived on time. The ASN had been transmitted four hours before dock. The pallets were built to spec. The following week, a $2,100 chargeback appeared on the Walmart remittance: label compliance violation, SSCC-18 mismatch.

The brand's ops team called the co-packer. The co-packer had applied correctly formatted GS1-128 labels with valid SSCC-18 values. The EDI 856 had also contained valid SSCC-18 values. They were different ones. The brand's logistics coordinator had generated the SSCCs for the ASN; the co-packer had generated their own for the physical labels. Nobody had specified whose SSCCs governed. The co-packer agreement covered IP protection, allergen controls, and recall procedures. SSCC-18 generation was not in it.

This is not a failure mode most food attorneys think about when drafting these agreements. They write to protect against IP theft, product liability, and food safety failures. Those risks are real. The operational requirements — label standards, identifier generation protocols, ASN obligations, fill rate commitments — tend to appear as a single sentence about "meeting retailer requirements." That sentence does not specify who generates which identifiers, what advance notice the brand needs before product leaves the dock, or who absorbs the compliance fine when the co-packer ships short.

The GTIN is yours only if you issued it

A co-packer that generates GTINs from its own GS1 Company Prefix owns those identifiers. The brand's product name and formula are on the label. The numerical foundation that describes those products in every retailer's system belongs to someone else.

When that relationship ends — whether the brand switches co-packers or the co-packer exits the business — the brand must assign new GTINs for every affected SKU and re-register with every active retailer and distributor. That means resubmitting to Walmart Item 360, UNFI Connect, and KeHE CONNECT. It means updating syndication through 1WorldSync or Syndigo. It means item setup from scratch at every DC whose system carries the old GTIN. The co-packer's GS1 prefix creates a dependency that isn't visible until the relationship ends and the reregistration work begins.

The brand should hold its own GS1 Company Prefix and issue GTINs for all its products. The agreement should state this explicitly — not as a best practice, but as a contractual requirement.

Beyond GTIN ownership: every case shipped to a major retailer requires a GS1-128 label containing an SSCC-18 pallet identifier. That SSCC-18 must exactly match the SSCC-18 transmitted in the EDI 856 ASN — this match is how the DC's automated receiving system connects the physical shipment to the electronic record. If the brand and co-packer are generating SSCCs independently, from different systems or different prefixes, every shipment carries a mismatch risk. Label quality failures cost $287–$317 per occurrence; missing required label information runs $424–$5,676 per shipment. One misconfigured label format, repeated across every case on every truck to that retailer, generates a structural deduction source rather than a one-time claim.

The agreement should specify who generates SSCCs, from which system, and how those values reach the brand before the ASN is transmitted.

The ASN the co-packer never knew to send

Walmart, UNFI, and KeHE require an EDI 856 Advance Shipping Notice transmitted before the truck arrives at the DC — typically one to four hours ahead, depending on the retailer. The ASN contains the SSCC-18 of every pallet, the GTIN and quantity per case, the PO number, and ship date. The DC's receiving system matches the incoming shipment against this electronic record.

The brand transmits the ASN. The co-packer does not. But the brand can only transmit it accurately if the co-packer has shared shipment details — quantities, pallet configuration, SSCC-18 values — before the truck leaves. Most co-packer agreements contain no such notification requirement. The brand often learns the truck shipped when a carrier tracking number appears in an email, sometimes hours after departure.

A shipment that arrives without a matching ASN produces a compliance failure. Invalid or late ASN generates penalties from $1,000 to $3,145 per occurrence at major retailers. It is also the same failure mode that generates an OTIF violation — the retailer's system records a shipment that didn't match its electronic record, and the fine follows regardless of whether the product itself was correct.

The agreement should require the co-packer to provide an itemized shipment notice — quantities, SSCC-18s, pallet configuration — no later than a specified number of hours before departure.

Fill rate fines land on the brand

A retailer purchase order holds the brand accountable for fill rate. Not the co-packer.

UNFI holds suppliers to a 95% fill rate standard, with a 3% service level fine below that threshold. Walmart's OTIF threshold sits at 98%, with a 3% penalty on the cost of goods for non-compliant shipments. When the co-packer ships 800 cases against a 1,000-case PO — because of a capacity constraint, a raw material shortage, or a quality hold — the brand's fill rate drops. The compliance fine arrives on the next remittance.

The brand bears the fine regardless of which party caused the shortfall. Standard co-packer agreements protect the co-packer from consequential damages, which means the retailer compliance fine is the brand's liability even when the co-packer's performance produced it.

The agreement should include a minimum fill rate commitment per purchase order and a clause that allocates retailer compliance fines to the co-packer when documented shortfall originates on their side. Without it, the brand absorbs the cost and litigates the recovery — if they pursue it at all. Most don't.

A formulation change no one registered

Co-packers substitute ingredient suppliers, adjust processing parameters, and modify pack configurations — sometimes because of supply constraints, sometimes because of cost pressure. Not all of them notify the brand before the change takes effect.

GS1 standards require a new GTIN whenever declared net content, pack configuration, or serving size changes. A co-packer that changes a pack configuration without notifying the brand has created two versions of the product: the one registered in Walmart Item 360, UNFI Connect, and KeHE CONNECT, and the one currently leaving the dock. The GTIN in the retailer's system describes the old product. The cases being shipped contain the new one.

That mismatch generates a chargeback. It also creates a potential labeling problem if the substituted ingredient affects allergen declarations or nutritional content. The operational failure and the food safety risk come from the same source: a change the brand didn't know about before it shipped.

The same product master fields that generate chargebacks when they're wrong in the item master are the fields the co-packer just changed without a GTIN update. The agreement should require written notice of any change to formulation, net weight, pack configuration, or key ingredients before implementation — with enough lead time to update all retailer portals before the changed product ships.

Audit the co-packer agreement before the next production run

Lailara reviews co-packer agreements against the operational requirements that generate retailer chargebacks — GTIN ownership language, SSCC-18 generation protocols, ASN notification timelines, fill rate commitments, and GTIN change requirements. The deliverable is a clause-level gap analysis against the brand's active retailer and distributor compliance obligations. Book a 30-minute scoping call.

See the methodology behind this post. The worked example — readiness across eight dimensions, GTIN validation against five retailers, EDI preflight, and a launch cash-flow model — is a live demo you can open and explore. Retail Readiness & Launch →

The Ten Decisions is the map behind this post. Every data problem a $25M specialty food brand runs into — chargebacks, deductions, launch economics, OTIF gaps — maps to one of ten decisions being made without adequate information. See the full picture →