Co-packing at 3PLs: who owns specs, bills of materials and run records?

Who owns co-packing records under a typical agreement?#

Co-packing record ownership is decided by the agreement, and most agreements split records by who created them and whose information they contain. The client typically supplies and owns the product specifications, artwork, labels, formulas and pack-out instructions. The 3PL or contract packager typically creates and holds its own production records: run logs, labor time, line setups, yields, scrap and exception notes.

The trouble sits in the overlap. A kitting bill of materials, a deviation report or a quality hold record often contains both the client's specification and the operator's own observations. Treat those as mixed records and decide field by field what each side controls, rather than assigning the whole document to one party.

Record by record: client-owned versus operator-held#

The table below reflects common positions in co-packing and contract packaging agreements, not a legal rule. Any single agreement can move a record from one column to the other, so use it as a checklist when reading your own master services agreements and statements of work.

Why bills of materials are the record both sides claim#

Bills of materials are contested because they are built in layers. The client's specification names the product components; the operator's BOM in its WMS or ERP adds packaging consumables, labor steps, substitution rules, case packs and pallet patterns that the operator worked out on its own lines.

A useful practice is to split the BOM into client-supplied fields and operator-created fields. Client component numbers, descriptions and quantities stay with the client's material. Routings, labor standards, setup notes and consumable usage are the operator's know-how, unless a work product clause assigns them to the client.

Watch for deliverables or work-for-hire language that assigns everything created in connection with the services to the client. Broad wording can sweep in operator methods that neither side meant to treat as client property, and the issue usually surfaces only when the relationship ends.

Contract clauses that decide ownership and reuse#

Ownership in co-packing is rarely settled by one clause. Read these provisions together, because a narrow ownership clause can still be undercut by a broad use restriction or a broad definition of confidential information.

• 1Definition of confidential information: whether it covers only what the client discloses or also what the operator observes and records.
• 2Client materials and specifications: what the client supplies and how the operator may use it.
• 3Work product or deliverables: what the operator creates that is assigned to the client.
• 4Know-how or residuals: whether the operator keeps general skills, methods and process improvements.
• 5Use restriction: whether client information may be used only to perform the services.
• 6Records, audit and retention: what the operator must keep, for how long and with what client access.
• 7Aggregated or de-identified data: whether combined data across clients is permitted, and for what purposes.
• 8AI and analytics: whether client data may be used to train models or build tools, which some newer agreements address directly.
• 9Return or destroy at termination: which copies come back, which are destroyed and what may be kept for legal reasons.

What a contract packager can usually reuse#

A contract packager can usually reuse its own know-how: line design, staffing patterns, changeover methods and general process improvements that do not reveal any client's specifications. Many agreements confirm this through a residuals or know-how clause, but silence in the contract is not the same as permission.

Operator records that stand on their own, such as line uptime, changeover times by equipment type or labor productivity across runs, are easier to reuse than records that name a client's product. Exception notes are the hardest case: a note recording that a client's carton failed a drop test quotes the client's spec and may be client confidential information.

If a record mixes both, removing client names and specification details may not be enough when the agreement restricts any use of client information beyond performing the services. Counsel should read that restriction against the specific use being considered.

Illustrative: a contract packager sorts its records#

Illustrative: a fictional 3PL runs kitting and display assembly for consumer brands from two buildings. Its WMS holds kitting BOMs, its line software logs run times and scrap, and its quality team keeps deviation reports and hold tags on a shared drive.

When leadership asks whether its operating history has value beyond the warehouse, counsel reads the master services agreements for its largest clients. Two define confidential information to include anything the operator learns about the client's products. The team sorts records into three groups: client materials, which are excluded; mixed records, which would need client consent; and operator-only records such as line uptime, labor standards and changeover logs, which can be assessed.

The 3PL proceeds only with the third group. It also adds a clearer know-how clause and an express statement on aggregated operating data to its renewal template, so the question has a written answer next time.

How SourceX approaches co-packing records#

SourceX handles co-packing records through the Rights step of the SourceX five-step transaction. Client specifications, artwork, formulas and anything the agreement defines as client confidential information are excluded unless the client gives written consent, and mixed records are reviewed field by field.

Operator records that clear review are prepared with client names, product identifiers and personal details removed. Each approved package carries a SourceX Evidence Packet documenting provenance, licensing rights, permitted use, the privacy record and release authorization. The operator approves every step, and records are licensed, not sold.