Data inventory template for a food co-packer

What a co-packer inventory adds: the ownership column#

A co-packer data inventory works like any plant inventory, with one addition: an ownership value on every row. Because a co-manufacturer makes products to other companies' formulas, specifications and artwork, the same ERP can hold records that belong to a brand next to records that describe only the plant's own operations.

Filling in the ownership column early saves time later. It tells the owner which records are clearly the plant's own, which belong to customers and which need someone to read the co-manufacturing agreement.

• 1Walk the plant from receiving to shipping and list each record type at each stage.
• 2Name the system or location for each: ERP, line controller, spreadsheet, LIMS or paper binder.
• 3Record the earliest date each record is accessible today.
• 4Note the link key: ingredient lot, batch or lot number, line, SKU or pallet.
• 5Mark ownership as brand-owned, co-packer-owned, shared or unknown.
• 6List which co-manufacturing agreement governs each brand's records.

The template, by plant area#

The template below follows product through a typical food plant. Replace the systems with your own and add rows for anything specific to your process, such as retort logs, metal detector verifications or kill step records.

The lot number is the most important link key in a food plant, because it ties ingredient lots to batches, finished goods, holds and complaints. If lot codes changed format at some point, or rework was blended into later lots without a record, note it on the batching row; those breaks are where traceability and data value both drop off.

How to decide brand-owned versus co-packer-owned#

The co-manufacturing agreement decides ownership, and the template's defaults only hold when the agreement is silent. Read the confidentiality definition, any records or audit clause and any intellectual property clause together, since each can move a record from one column to another.

Where agreements differ by brand, the same record type can have different ownership values for different customers. Add a row per brand for the record types that change, rather than forcing a single answer.

Batch records are the row to read twice#

Batch records are the hardest row because they combine the brand's formula with the plant's execution. The target weights and ingredient list come from the brand's specification, while actual weights, mix times, temperatures, deviations and operator sign-offs describe how your team ran the batch.

When batch records are shared, a common approach is to separate the two layers: formula content stays out of any use beyond production, while timing, deviations and corrective actions may be usable once ingredient quantities and brand identifiers are removed, if the agreement allows. Food safety rules under FSMA may require you to keep certain records for set periods, so list retention obligations in the inventory and never delete records as part of this work.

Paper, spreadsheets and ERP exports#

Many co-packers keep their longest history on paper. Batch sheets, sanitation checklists and changeover logs are often signed on the floor and filed in binders or scanned later, so the inventory should record where the paper is, how it is filed and whether scans are searchable.

Check ERP exports before relying on them. Oracle's NetSuite documentation, for example, says its Full CSV Export does not currently export all data and lists what it covers, such as customers, items, transaction detail and vendors. Whatever ERP you run, note in the export method column which records come out cleanly and which need a report, a query or vendor help.

Line controllers and OEE software often keep detailed data only for a limited rolling period before summarizing it. Record the retention setting for each, and whether anyone saves shift reports, since those summaries may be the only long history of line speeds and stoppages.

Illustrative: a powder co-packer completes its template#

Illustrative: a fictional co-packer of drink mixes and protein powders for several consumer brands builds its inventory with the COO and the food safety manager. The ERP holds receipts, batch tickets and shipments, the blending room uses paper batch sheets that are scanned weekly, and sanitation and allergen changeover verifications are kept in binders by line.

Formulas and artwork are marked brand-owned. Sanitation, environmental monitoring, changeover and line performance records are marked co-packer-owned. Batch records are marked shared, and one brand's agreement assigns all product-related records to the brand, so that brand gets its own rows. The finished inventory shows years of connected changeover and sanitation history keyed by line and SKU that belongs to the plant.

How SourceX approaches a co-packer inventory#

SourceX reads a co-packer's inventory in the Supply step of the SourceX five-step transaction, using metadata only; nothing is shared during the initial assessment. The ownership column sets the Rights review: brand-owned rows are excluded, shared rows are checked against each co-manufacturing agreement, and Preparation removes brand names, SKUs and formula content from anything that proceeds.

The co-packer approves every step, keeps ownership of its records and licenses defined use only. A SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization for each package.