Own-Label Distributor: Part 111 Duties for Supplement Brands

What an own-label distributor actually is

“Own-label distributor” names a business role; “private label supplement” describes a product or commercial arrangement. Neither expression, by itself, describes everything a firm does. A brand may buy finished bottles, arrange separate labeling, or hold stock before shipment. Those differences matter more to the operating assessment than the commercial title.

The following terms describe overlapping relationships, not mutually exclusive statutory categories. One firm can occupy several rows.

FDA’s guide on how the DS CGMP rule applies to specific operations explains that firms packaging, labeling or distributing another firm’s supplement must comply with provisions directly applicable to their operations. This is an operations-based explanation, not a blanket assignment of every manufacturing task to every distributor.

For practical role mapping, follow the physical product as well as the purchase order: who makes it, who labels it, and who stores and ships it? Compare the supplement contract manufacturing relationship with any separate packaging and labeling operations. A private-label arrangement may bundle these services commercially; the activity map should still identify each operator separately before duties are assigned.

Start with activities, not the name printed on the bottle. Under 21 CFR 111.1(a), a person who manufactures, packages, labels, or holds a dietary supplement is subject to Part 111, except as provided by paragraph (b). Paragraph (b) is narrow: the holding requirements do not apply to a person holding dietary supplements at a retail establishment for the sole purpose of direct retail sale to individual consumers, and a retail establishment does not include a warehouse or other storage facility for a retailer or one that sells directly to individual consumers. This is the starting point for mapping supplement current good manufacturing practice responsibilities.

FDA’s explanation of operations-specific applicability says firms must comply with provisions directly applicable to the operations they perform. Performing one operation does not mean inheriting every manufacturing provision. The guide explains FDA’s interpretation; guidance documents do not establish legally enforceable responsibilities.

Use the following map as a working allocation tool, not an exhaustive list of duties. The practical controls are operating recommendations, separate from the binding text and guidance identified alongside them.

FDA’s labeler example concerns an operator performing labeling; it should not be extended into a blanket batch-record requirement for every brand purchasing finished goods. For that operation, use the batch production record elements as the next reference point. For warehouse activities, continue with holding and distribution. Complaint responsibilities are addressed in the later complaint section.

In practice, complete the map before assigning documents to the brand or contractor. Record the activity, operator, location, relevant provision, procedure owner, and escalation contact. Where two firms describe the same task differently, resolve the handoff explicitly rather than assuming that either the purchase order or label ownership answers the operational question.

This article addresses dietary supplement operations under Part 111, not every obligation attached to a product or market. 21 CFR 111.5 requires compliance with other applicable statutory provisions and regulations under the act related to dietary supplements; Part 111 does not replace them. Its second sentence points importers of dietary supplements and supplement components to the foreign supplier verification program regulation in subpart L of part 1. That cross-reference alone does not determine an importer’s duties or exemptions.

As an operational scoping method, record product classification, destination market and the actual operator for each activity before approving the responsibility map. Resolve classification questions—including the sterile/aseptic supplement format boundary—rather than relying on a commercial product description. Carry those scope decisions into supplier qualification and the review of each contract supplement manufacturer. This is a practical review method, not a database format prescribed by Part 111.

In Example 3 of FDA’s Small Entity Compliance Guide, FDA describes a distributor that contracts for manufacture of a supplement distributed under its own label. The guide says that distributor has an obligation to know what manufacturing activities are performed and how. FDA connects that knowledge to deciding whether the packaged and labeled product conforms to established specifications and whether to approve and release it for distribution. This is FDA’s guidance explanation of the contractual relationship, not a separate regulatory checklist.

Operationally, distinguish the manufacturer’s disposition from the distributor’s evidence-based distribution decision described in the guide. Treat the former as an input to the latter, rather than silently substituting one for the other. Implementing this distinction should not become an assumption that the brand must repeat every manufacturing task, operate a second laboratory program, obtain every contractor record, or use a universal two-signature form.

An illustrative review package could connect each item to a decision:

• Applicable product specifications and label versions: identify the acceptance criteria and intended presentation against which the lot is evaluated.
• Supplier lot identity and lot pedigree: establish whether the documents concern the actual product received.
• Relevant test results: support comparison of measured attributes with the applicable acceptance criteria.
• Material deviations: identify departures that could affect conformity and whether their resolution supports distribution.
• Manufacturer’s disposition: show the contractor’s conclusion and any conditions that need consideration before the distributor decides.

This package is a practical evidence arrangement, not a prescribed document set. A certificate of analysis is useful only to the extent that its scope addresses the review question and it connects to the correct lot. For example, results for an earlier lot do not establish the current lot’s results; matching lot identification still leaves the reviewer to assess which attributes the certificate actually covers.

Use a quality agreement to coordinate the operations mapped above. The recommendations below are contracting practice, not a statutory template or a substitute for applicable duties. Assign task performance, evidence preparation, review and authorization separately. Name role holders and deputies; do not silently assign every responsibility to the brand’s founder.

Adapt this responsibility table to the actual operators. “Responsible party” identifies the performer and evidence preparer; “Review authority” identifies reviewers and decision-makers, not merely recipients copied on emails.

Through change control and document control, agree record formats, lot identifiers, revision identifiers, access permissions, notification triggers and response expectations. Define acknowledgment, containment and investigation milestones separately; negotiated deadlines are contractual expectations, not Part 111 time limits.

If the manufacturer will not share its complete production record, identify the information needed for the brand’s decision. Negotiate controlled access, relevant copies or sufficiently detailed summaries. Escalate unresolved gaps to both quality leads and defer affected distribution authorization when evidence is inadequate. Do not assume an unrestricted right to contractor records.

Cover contractor changes, subcontracted operations and termination: assign notification and approval routes, continuing record access, open-investigation ownership, inventory-status transfer and handover acceptance.

The following illustrative operating sequence turns the quality agreement into lot-level work. It is a practical workflow, not a prescribed regulatory sequence.

1. Establish the product baseline. Identify the agreed specifications, packaging configuration and label version against which the supplier lot will be reviewed.
2. Obtain batch evidence. Associate supplier records, test results and receipt details with the correct lot. Track documents as received, reviewed or awaiting clarification; uploading a file establishes receipt, not approval.
3. Resolve discrepancies. If receipt documentation names label version 4 but the baseline specifies version 5, preserve both entries and open an exception. Record the affected lot, owner, investigation and disposition; do not silently overwrite the received version or authorize distribution while the discrepancy remains unresolved.
4. Record the human decision. Identify the reviewer, evidence considered, conclusion and date in an electronic release record or equivalent controlled record. A reviewed document and a recorded approval are separate operational states.
5. Authorize distribution. Communicate the approved lot and any restrictions to the shipping operator, keeping shipment instructions distinct from evidence receipt.
6. Retain the shipment-to-lot connection. Link each destination, quantity and shipment reference to the supplier lot so lot traceability survives transfers between sites.

Worked case: bottle inventory reconciliation

Assume one supplier lot contains 12,000 bottles, with no losses or other movements during the reconciliation period. Warehouse A receives 4,500 bottles, warehouse B receives 7,200, and 300 remain at the origin site.

• Quantity balance: 4,500 + 7,200 + 300 = 12,000 bottles.
• Remaining at origin: 300 ÷ 12,000 × 100 = 2.5%.

This reconciles the stated quantities only. It does not establish specification conformity, resolve missing lot identities or demonstrate that the correct label was applied. Matching totals could still conceal a shipment assigned to the wrong lot. Treat the calculation as a consistency check supporting human review, not as a regulatory acceptance criterion or a substitute for the distribution decision.

Worked case 2 assumptions: a two-person supplement brand contracts manufacturing and labeling to one firm, sends finished bottles to an independent fulfilment operator, and receives customer messages through an online marketplace. Amazon FBA can illustrate this arrangement; no platform policies or provider capabilities are assumed.

Use the earlier activity map, not headcount or warehouse ownership, to assess scope. FDA’s guidance on specific operations explains that firms must comply with provisions directly applicable to their operations. Neither blanket exemption nor universal applicability follows from this scenario.

• Manufacturer/labeler: performs manufacturing and labeling; agree which lot records, test results and labeling records it supplies for the brand’s distribution decision.
• Fulfilment operator: performs holding and shipment; agree inventory-status reporting, shipment traceability and escalation contacts with the third-party logistics provider.
• Brand: receives marketplace messages; name the complaint reviewer and distribution decision-maker, with deputies and manufacturer contacts for investigation.

Build a handoff register linking manufacturer lot → receipt/shipment reference → fulfilment inventory identifier, alongside the marketplace product identifier. Keep product identifiers separate from batch identifiers: one listing may cover several lots. Record quantities in bottles, locations and inventory status. Agree how each party preserves these relationships; product and lot identification should support the mapping rather than collapse distinct identifiers.

Provide a fallback complaint email or telephone channel. If a message omits the lot, request bottle photographs and order details, then reconcile dispatch dates against inventory movements. Treat unresolved matches as potentially involving multiple lots, not a guessed batch.

If the brand starts relabeling or storing bottles itself, add those activities, locations, personnel and records to its operating map. Revisit the earlier legal analysis before changing the workflow.

A distributor should not treat a complaint as merely a customer-service ticket. FDA's complaint-applicability explanation says that any person in the manufacturing chain receiving a product complaint, including a distributor, must comply with the product-complaint requirements.

Official guidance: review, investigation and approval

• FDA's explanation of 111.560(a)(1) calls for a qualified person to review all product complaints for possible failure to meet specifications or other Part 111 requirements.
• Under the guide's explanation of 111.560(a)(2), a qualified person investigates when that review determines the complaint involves such a failure.
• For 111.560(b), the guide describes quality-control review and approval of decisions whether to investigate, plus investigation findings and follow-up action.
• Its explanation of 111.560(c) extends complaint review and investigation to all relevant batches and records.

Practical failure controls

These hypothetical controls connect complaint management with deviation management and corrective and preventive action within the quality management system; they are operating recommendations, not additional regulatory requirements.

Worked case 3: a shared label revision

Assume a complaint names lot L101 and packaging records show L102 used the same questioned label revision. That shared revision is a reason to assess L102's relevance, not proof that both lots are defective. Compare the complaint allegation, actual labels and packaging records; document why L102 is included or excluded from further investigation.

Keep operational containment separate from final disposition: a temporary hold limits movement while facts are assessed; it does not decide acceptability. Record the reason, owner, affected identifiers, evidence reviewed and recovery authorization. Before resuming the affected activity, confirm that the immediate failure is controlled and assign any longer-term corrective action for follow-through.

Use a connected evidence model rather than separate folders for each firm. The following is a proposed information-management design, not a prescribed Part 111 database schema. Link each product to its specifications, each batch to the responsible parties and operating sites, and each human decision to the evidence reviewed. Connect shipments to batches and destinations; connect complaints to implicated shipments and lots, allowing one complaint to span several batches.

Keep identifiers distinct: product_id identifies the product; supplier_lot_id identifies the contractor lot; batch_id is the local linking key. Retain the contractor identity alongside its lot number to avoid collisions between suppliers. specification_version and label_version identify the applicable baseline, not simply the latest revision. Preserve these relationships when a lot moves between sites or ships in several consignments.

At each handoff, map manufacturer records and laboratory results to the batch, then connect brand review records and warehouse shipment data to that same identity. Electronic transfer, controlled file exchange and manual reconciliation are possible approaches. Agree field meanings, reference versions, expected evidence and receipt acknowledgments before exchanging records. These controls support data integrity regardless of the transfer method.

For missing identifiers, duplicate imports, conflicting revisions or delayed evidence: preserve the original submission, log the discrepancy, assign an owner, reconcile against the agreed reference and record the authorized correction. Do not silently overwrite a conflict or invent a missing identifier. Retain who changed what, when and why for audit trail review.

Track reconciliation status separately from disposition status. An import can become “reconciled” while the batch remains “on hold.” Closing an interface discrepancy should not change a quality decision; any disposition change needs its own authorized human decision and supporting record.

Use the legal and guidance distinctions above to review your operating arrangement. This is a suggested self-review checklist, not a list of additional regulatory duties. For each row, name an accountable person and identify a retrievable record; a department name or verbal assurance is not enough for this exercise.

For decision records, use a batch release checklist suited to the assigned roles. For recurring exceptions, examine the CAPA effectiveness check, rather than relying on a closed status alone.

Test one batch end to end

Select one distributed batch. Connect its supplier lot to the product baseline in effect, supporting evidence, dated human decision, destination shipments and any relevant complaints. Ask the responsible people to retrieve these connections through normal access routes. Record missing links, conflicting versions and unresolved quantities, then assign recovery actions and owners. This traceability exercise is an operational review, not a compliance certification.

Review the arrangement after relevant changes to supplier, site, label, specification, fulfilment arrangement or information interface, and at risk-based intervals chosen by the firm. Document the rationale for those intervals. Use management review to track unresolved gaps, responsible owners and completion dates.

Use that assembled evidence to support review—not as an approval in itself. In this operating model, designated people evaluate the record, resolve questions and make approval and batch release decisions. For an own-label brand, the practical boundary is clear: bringing records together helps people assess the batch; it does not transfer their decision-making responsibility to software or establish compliance.