Private-label manufacturing: whose design and warranty data is it?

Why private-label data ownership is harder than it looks#

Private-label data ownership is hard because two businesses share one product but keep different records about it. The brand owner sells, markets and often fronts the warranty. The manufacturer designs or builds, inspects and handles returns. Each side ends up holding records the other side helped create.

Programs also come in two broad shapes. In a rebrand program, the manufacturer puts the brand's label on a product it already designed and sells under its own name. In a custom program, the brand supplies a specification, formula or design and the manufacturer builds to it. The same record type can belong to different parties in each shape.

Ownership of records is also not only a copyright question. Many production and warranty records are factual, so the practical controls are usually the contract's confidentiality and use clauses, plus trade secret protection where it applies.

Who usually owns each record type?#

Usual ownership follows creation and contract: the party that created a record, or that the agreement names, typically controls it. The table below shows common positions, but any individual agreement can change them.

Which agreement clauses decide design and data rights?#

The supply agreement, quality agreement and any NDA decide design and data rights together, so read them as a set. Purchase order terms can add or conflict, which is why counsel often checks which document controls.

One point surprises many manufacturers. Under US copyright law, a commissioned work counts as a work made for hire only in certain statutory categories and only with a signed written agreement, so drawings a manufacturer's own employees prepare for a brand do not automatically belong to the brand. Most supply agreements address this with an express assignment, which is why the IP clause matters so much.

• 1IP ownership: who owns background IP brought into the program and foreground IP created during it.
• 2Improvements: whether changes to the brand's design or the manufacturer's process belong to one side or are shared.
• 3Confidential information: whether the definition covers all information generated in performing the agreement.
• 4Use restriction: whether information may be used solely to supply the products.
• 5Records and audit: what the manufacturer must keep, for how long and who may inspect it.
• 6Warranty administration: who receives claims, who holds registrations and how chargebacks are documented.
• 7Termination: whether records must be returned or destroyed when the program ends.

Warranty data is usually split between brand and manufacturer#

Warranty data in private-label programs is usually split: the brand holds the customer-facing records and the manufacturer holds the engineering records. The brand often runs product registration, consumer or contractor contacts and claim intake. The manufacturer receives returned units, performs teardowns and issues credits or chargebacks.

Holding a record is not the same as having the right to use it freely. A manufacturer's teardown findings may still describe the brand's specification, and claim records forwarded by the brand may contain end-customer names and addresses. Where personal data appears, state privacy laws may apply, and the brand's privacy notice to its customers matters too.

A practical approach is to separate the engineering facts, such as failure mode, build lot and corrective action, from the identities of the brand and its customers. Whether even the de-identified engineering facts can be used outside the program depends on the confidentiality clause.

Illustrative: a door hardware maker sorts two programs#

Illustrative: a fictional maker of commercial door closers supplies two retail brands. Program A rebrands its own catalog closer with the brand's label. Program B is a closer built to Brand B's specification, with Brand B's drawings attached to items in the ERP.

Leadership is considering whether production, quality and warranty return records could support a data license. Counsel reads both supply agreements. Program A's agreement treats the product design as the manufacturer's and restricts only Brand A's marketing information. Program B's agreement defines confidential information to include all specifications and all data generated in making the product.

The company scopes Program A's lot, NCR and teardown records as candidates, with brand and customer names replaced by codes. Program B is set aside unless Brand B agrees in writing. The decision is recorded program by program, so a future renewal of either agreement can revisit it.

Documents that answer the ownership question#

The documents that answer the ownership question are usually already in the contracts folder and the ERP. Gathering them per program, before any outside conversation, saves a great deal of back and forth later.

Where documents conflict, record the conflict rather than resolving it internally. A drawing legend that says property of the brand, sitting under an agreement that says the manufacturer owns its designs, is exactly the kind of question counsel should settle before any record leaves the building. Keep a one-page summary per program listing each document, its date and the clause that answers each record type.

How SourceX approaches private-label records#

SourceX handles private-label programs in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Each program is reviewed separately against its own agreements, and records tied to a brand's specification are usually excluded unless the brand consents.

For records that proceed, the SourceX Evidence Packet documents licensing rights, permitted use and the privacy record, including how brand and customer identities were removed. Nothing is shared during the initial fit check, and the manufacturer approves the final scope.