Co-Manufacturer Lot Code Linking: Solving the Traceability Gap in Outsourced Production

For CPG brands that use co-manufacturing partners, FSMA Rule 204 traceability creates a structural challenge that does not exist for vertically integrated manufacturers: a significant portion of the trace chain — specifically the transformation CTE, and often the receiving CTEs for raw materials — lives in the co-manufacturer's systems, not the brand's.

This is not a minor operational inconvenience. Under FSMA Rule 204, the brand (as the entity responsible for the finished goods lot) needs to be able to respond to an FDA trace-back request within 24 hours with records covering the complete CTE chain — including the production step that happened at the co-man's facility. If the brand cannot access or reconstruct those records within the 24-hour window, the response is incomplete.

This article addresses the co-manufacturer lot code linking problem in practical terms: what data the brand needs from the co-man, how to establish the data flow, and what the options look like for different types of co-manufacturing relationships.

What the Brand Needs from the Co-Man

The core data the brand needs from its co-manufacturing partner for FSMA 204 compliance falls into three categories:

Transformation CTE data

For each production run that produces finished goods under the brand's label, the co-man must provide (or make accessible) the transformation CTE record — specifically:

• Input TLCs: the lot codes for every FTL ingredient used in the production run
• Input quantities: how much of each ingredient lot was used
• Output TLC: the finished goods lot code assigned to the production run
• Output quantity
• Transformation date and co-man facility address

This is the record that creates the ingredient-to-finished-goods link. Without it, the brand's trace chain is broken at the production step.

Receiving CTE data for FTL ingredients

The co-man's receiving records for FTL ingredients are technically the co-man's obligation under the rule. But if an FDA investigation traces back through a finished goods lot to an ingredient lot that entered the supply chain at the co-man's receiving dock, the brand needs to be able to confirm that receiving CTE record exists — and potentially to have access to it for the trace-back response.

This is a more complex data-sharing ask than the transformation CTE data. Not all co-mans will be willing to share detailed receiving records — those records may include pricing information and supplier identities that are commercially sensitive. The practical minimum is confirmation that the co-man has receiving CTE records in a compliant format, and a written agreement that those records will be made available to the brand within a specified timeframe (ideally faster than 24 hours, to give the brand enough time to incorporate them into a trace-back response).

Shipping CTE data

If the co-man ships finished goods directly to the brand's distribution network — rather than shipping to the brand's 3PL or returning goods to the brand's control — the co-man is the shipper for those CTEs and is responsible for shipping CTE records. The brand needs access to those records to confirm which lot codes shipped to which distribution destinations.

For co-mans who ship finished goods on the brand's behalf (drop-shipping model), establishing access to shipping CTE data is a critical part of the co-manufacturing data relationship.

Three Models for Co-Man Data Sharing

In practice, brands and co-mans have adopted different models for addressing this data sharing requirement. The right model depends on the co-man's system capabilities, the volume and complexity of the relationship, and the brand's internal system architecture.

Model 1: Shared traceability platform access

The brand provides the co-man with portal access to the brand's traceability system. The co-man enters production run data — input lots, quantities, and output lot codes — directly into the brand's trace chain at the time of production. This approach creates the transformation CTE record in real time, in the brand's system, with no data transfer step.

The advantages of this model are reliability and immediacy — the brand's trace chain is complete as soon as the co-man logs the production run. The disadvantage is that it requires the co-man to adopt a new data entry process in a system they do not own and to maintain that discipline across all production runs.

This model works best when the brand has significant leverage over the co-man relationship — large volume or exclusive arrangement — and when the traceability platform has a co-man portal interface designed for external data entry with appropriate access controls.

Model 2: Structured data file transfer

The co-man exports a production run report from their own system (ERP, MES, or QMS) in a structured format — typically CSV or Excel — and transmits it to the brand after each production run. The brand's traceability system (or a manual import process) incorporates the data into the trace chain.

For this model to work, the structured data file must contain the required fields: input TLCs, input quantities, output TLC, output quantity, transformation date, and facility identifier. The brand and co-man need to agree on the data format specification and the transmission schedule (how quickly after a production run the file is provided — same day is the operational target).

This is the most common approach in practice because it does not require the co-man to use the brand's system — it works with whatever data the co-man can export from their existing systems. The failure mode is data quality: if the co-man's export does not capture input lot codes (because their system only records the production run at an item-level, not a lot-level), the file transfer approach cannot bridge that gap.

Model 3: Co-man traceability documentation in the manufacturing agreement

The brand incorporates FSMA 204 traceability requirements into the co-manufacturing agreement — requiring the co-man to maintain FSMA 204-compliant CTE records for all production runs under the agreement, and requiring the co-man to provide those records to the brand within a specified timeframe (e.g., within 8 hours of a trace-back request).

This model shifts the operational responsibility to the co-man and creates a contractual basis for the brand to obtain the records when needed. It does not, however, put the records in the brand's hands proactively — the brand only receives them when they are needed for a trace-back response. This creates timing risk: if the co-man takes 10 hours to respond to a records request, the brand has only 14 hours left to assemble and submit its response to FDA.

Model 3 is a backstop, not a primary solution. It is appropriate as a supplement to Models 1 or 2 — ensuring legal recourse if the proactive data flow breaks down — but should not be the only mechanism for co-man traceability data access.

Lot Code Format Alignment

A practical obstacle in co-man lot code linking that often surfaces during implementation is lot code format alignment. The co-man typically assigns finished goods lot codes using their own format — often a combination of facility code, production date, and sequential run number (e.g., CHI-20251203-004). The brand may have its own lot code format that they prefer on the final case label (e.g., BD-2512-0047). These may or may not be the same code.

In cases where the co-man assigns the lot code that appears on the finished goods case label, that code is the TLC for the shipping CTE. In cases where the brand relabels product or applies its own case label over the co-man's, a new TLC may be assigned at the relabeling step — creating a transformation CTE for the relabeling event, linking the co-man's output TLC to the brand's finished goods TLC.

Either approach is compliant as long as the linkage is documented in the trace chain. The important thing is that there is a clear, documented relationship between every lot code the co-man assigns and the lot code that ultimately appears on the case label the distributor scans at receiving — and that this relationship is captured in the CTE records.

Practical Steps for Implementing the Co-Man Data Relationship

For brands working to establish FSMA 204-compliant co-man lot code linking, a structured implementation sequence helps avoid the common failure modes:

Step 1: Audit your co-man's current record capability. Before agreeing on a data sharing model, understand what your co-man's systems currently capture at the production run level. Do they record input ingredient lot codes in their batch records? Do they export lot-level production data from their ERP? What format is available? This assessment determines which of the three models above is feasible.

Step 2: Define the data specification. Document the exact fields required in the transformation CTE data you need from the co-man: field names, formats, required vs. optional, and the reference document (batch record or production order number) that connects to the co-man's internal records.

Step 3: Agree on the transmission schedule. Decide how quickly after each production run the data must be transmitted, and what the backup process is if the automated transmission fails.

Step 4: Test the linkage with sample data. Run a test trace-back using actual production run data from the co-man. Start from the finished goods TLC and verify that the system navigates backward through the transformation CTE to the input ingredient lots, and that those input lots link to the co-man's receiving records (or to your records if you supplied the ingredients).

Step 5: Formalize in the manufacturing agreement. Document the traceability data requirements, transmission obligations, and access-to-records provisions in the written co-manufacturing agreement or a separate data sharing addendum.

What to Do If Your Co-Man Is Not FSMA 204-Ready

Some co-manufacturing partners — particularly smaller regional operations — may not yet have systems capable of providing lot-level input ingredient records. If your co-man records production runs at the item level but not the ingredient lot level, the transformation CTE data needed for FSMA 204 compliance simply does not exist in their current process.

In this situation, the options are:

• Work with the co-man to implement a minimal FSMA 204 compliance process — even if just a structured paper batch record form that captures input lot codes and can be scanned and transmitted as a PDF (acknowledging that this is a transitional solution, not a long-term compliant format)
• Supply your co-man with Foodtrce portal access and have them enter production run data directly — this effectively teaches the co-man the compliant process while keeping the data in your system
• If the co-man produces FTL-covered products and is unwilling or unable to establish a compliant traceability process, assess whether this supplier relationship can continue to support your own FSMA 204 compliance posture

The co-man traceability data gap is a real operational challenge for many CPG brands, and it is one of the primary design priorities for Foodtrce's co-man data integration workflow. If you are working through this challenge with a specific co-manufacturing partner, we are glad to discuss the options and help identify the most practical path forward for your relationship structure.