Toll blending and private-label formulas: whose data is it?

Who controls what in a toll blending relationship?#

In a toll blending relationship, control of each record follows who created it and what the agreement says about it. The customer brings the formula, the specification and often the raw materials; the distributor brings tanks, mixers, packaging lines, people and its own way of running them.

That produces three layers of records sitting in the same ERP, batch system and quality files. The table shows the usual starting position, which the contract can move in either direction.

Which clauses decide whether records can be reused?#

The clauses that decide reuse are the ones about use and ownership, not only the definition of confidential information. Many toll agreements define confidential information broadly, then add a separate promise to use it solely to perform the services, which can reach records the distributor generated itself.

When reviewing a toll blending agreement or private-label supply agreement, counsel typically looks at these provisions:

Purchase order terms deserve a look as well. Some customers attach standard terms to every order that claim ownership of all documents, data and improvements related to their products, and those terms can conflict with the toll agreement. Counsel decides which document controls; the operations team's job is to find every one of them.

• 1Definition of confidential information, including whether it covers information generated during performance.
• 2Use restriction limiting use to performing the services for that customer.
• 3Work product and improvements, including who owns process changes made to run the customer's product.
• 4Records and audit rights, which may require retaining batch records for the customer's benefit.
• 5Return or destruction on termination, and whether archived copies are allowed.
• 6Any carve-out for aggregated or de-identified operational data.
• 7Survival, assignment and change-of-control terms that apply if the distributor is sold.

Why batch records are the hard case#

Batch records are the hard case because a batch ticket that lists ingredient weights is the formula, whatever label it carries. Removing the customer name and product code does not help if the ratios, mixing order and hold times remain.

Trade secret law is part of why customers care. Under the federal Defend Trade Secrets Act, information is a trade secret only if its owner takes reasonable measures to keep it secret and it gains value from not being generally known. Confidentiality agreements with blenders are often part of how a customer shows those reasonable measures, so a distributor that reused batch content could put a customer's protection at risk as well as breach the contract.

The practical rule for most distributors is to treat any record from which a formula could be rebuilt as the customer's, and to exclude it from reuse unless the customer agrees in writing.

When the distributor owns a private-label formula#

A distributor may own a private-label formula when it developed the formula itself and sells the finished product under its own brand or a customer's label. Ownership then depends on how the formula was created and whether any customer paid for development or claimed the result.

The scenarios below show how the answer shifts. Each still depends on the actual documents, including purchase order terms that a customer may have attached to routine orders.

What a blending distributor can usually consider#

A blending distributor can usually consider its own operating records once customer formula content is stripped out. These records describe how a plant is run, which is the distributor's expertise rather than the customer's recipe.

Examples include changeover and cleaning logs, production scheduling decisions, quality hold and release decisions with formula details removed, deviation investigations written by the distributor's staff, and standard operating procedures it authored. Each still needs a check against the use restriction in every relevant agreement, because one broad clause can reach them.

Preparation for these records is mostly subtraction. Remove customer names, product codes, ingredient names, quantities and lot numbers that trace back to a customer order, replace them with neutral codes, and keep a log of what was removed and why. If a deviation report makes no sense without the formula, leave it out rather than redact it into fragments.

Illustrative: a specialty chemical distributor sorts its blending records#

Illustrative: a fictional specialty chemical distributor runs a blending and packaging plant. It toll blends coatings additives for several manufacturers and sells a private-label line of industrial cleaners it formulated in house. Batch tickets live in the ERP, quality results in a laboratory system, and procedures in a document control tool.

The general counsel sorts records by agreement. All batch tickets and lab results for toll customers are excluded, because the agreements use solely-to-perform language and require return of records on request. Changeover logs, scheduling notes and deviation reports are kept in scope after customer, product and ingredient details are removed, since the agreements reviewed do not claim them. The private-label cleaner line, formulated without customer involvement, is reviewed separately as the distributor's own.

The result is a narrower but defensible scope. No toll customer's formula leaves the plant, and the distributor has a written record of why each record family was included or excluded.

How SourceX approaches formula-sensitive records#

SourceX treats customer formulas as excluded by default and reviews blending records in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Records whose ownership depends on an agreement stay out until counsel has read it.

For anything the distributor approves, the SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization, including which customer agreements were checked. Under the SourceX Enterprise Data Value Framework, a high privacy burden and preparation cost reduce net value, which often makes heavily formula-entangled records a poor fit even before rights are settled.