Regulatory Open Forum

 View Only
Expand all | Collapse all

Private Label Agreements

  • 1.  Private Label Agreements

    Posted 11-Jul-2016 18:25

    I'd like to hear from anyone that has extensive experience writing private label contracts. My company execs. want to add some of our private label customers to our current 510K's (same formulas as our own product's 510k, but would be labelled w/ our customer's labels). They are convinced that we can eliminate our liability as a manufacturer of private label products by entering into contractual agreements w/ our private label customers in which they agree to assume liability for product recalls, supplier controls, etc. even though these customers would be under our 510K number. I have not ever heard of such a thing & have assumed that we would ultimately be responsible for these things regardless of any agreements to the contrary due to the fact that we own the 510K. Any insight would be much appreciated. Thanks.

    ------------------------------
    Lauren Parker
    CA
    United States
    ------------------------------


  • 2.  RE: Private Label Agreements

    Posted 11-Jul-2016 20:10

    FDA typically regulates private label entities as wholesale distributors.  Domestic distributors are not responsible for the statutory/regulatory requirements applicable to the "manufacturer".  In other words, there is no U.S. statutory/regulatory basis for a private label entity to assume ultimate liability for the manufacturer's statutory/regulatory obligations (such as recalls and supplier controls).

    In order for FDA to hold the private label entity responsible for the manufacturer's obligations, the private label entity must itself become the statutory manufacturer by taking control/ownership of the specifications and the 510(k), and by FDA-registering itself as the statutory manufacturer, among other things.

    Moreover, there can only be one owner of a particular 510(k). Consequently, each private label entity who wants to own/control the specifications must hold its own 510(k).

    These statutory/regulatory requirements remain in force regardless of what contractual arrangements are in place between the firms involved. In other words, the FDA will still knock on the statutory manufacturer’s door when enforcing effectiveness of the recalls, supplier controls, etc., even if the manufacturer contracts / outsources handling of recalls, supplier controls, etc., to a third party.

    Hope this helps.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
    Principal Consultant
    ComplianceAcuity, Inc.
    Golden CO
    United States
    www.complianceacuity.com



  • 3.  RE: Private Label Agreements

    Posted 12-Jul-2016 06:54

    Kevin,

    I find your answer interesting, but it leaves me confused about another issue.

    You say, “FDA typically regulates private label entities as wholesale distributors.” A “Domestic Distributor that does not import device” according to the FDA website, does not have to register and list.

    However, I have always believe that if a company put a device on the market under its own name, but doesn’t manufacture the device, then it must register in some role. The most likely roles are specification developer or relabeler.

    Am I misunderstanding something here?

    The second issue comes up with the manufacturer’s listing. The FDA website (http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/HowtoMarketYourDevice/RegistrationandListing/ucm318796.htm) has an FAQ about registration with the following.

    4. We currently have our in-house brand and we private-label for a number of companies in the U.S. Do we need to include the proprietary names for each private-label device?

    Yes, your device listings should include all of the current proprietary names that are used to market the devices you make in the U.S.”

    From this, I infer that the private label company and the manufacturer would both list the device.

    The question came up, for me, in the context of UDI. I offered the opinion that the private label company is the labeler under the UDI rule because they “cause a label to be applied to a device”, and not the manufacturer. Consequently, the Device Identifier codes the identity of the private labeler (not the manufacturer) and the private label company is responsible to populate GUDID.

    ------------------------------
    Dan O'Leary
    Swanzey NH
    United States



  • 4.  RE: Private Label Agreements

    Posted 12-Jul-2016 14:29

    Thanks for the great questions Dan!

    Your question "Am I misunderstanding something here?":

    Specification development, relabeling, and repackaging are types of manufacturing.  So you are absolutely correct in that firms who are engaged in such activities must FDA-register and list.  This requirement is from section 510 of the FD&C Act [21 USC sec. 360(b), not to be confused with sec. 360b], and with implementing regulations at 21 CFR 807.20.

    But the application of these fundamentals to private label scenarios can easily lead to misunderstandings.  Remember that the FDA registration obligation is for non-exempt “establishments” engaged in the “manufacture, preparation, propagation, compounding, assembly, or processing” of devices.  And such establishments must also list the devices once in U.S. commercial distribution.

    In a nutshell, an “establishment” is a place where a device is manufactured, assembled, or otherwise processed [807.3(c)].  “Manufacture, preparation, propagation, compounding, assembly, or processing” means making devices by chemical, physical, biological, or other procedures [807.3(d)].  And as we both noted, manufacturing includes specification development and relabeling, thus requiring specification developers and relabelers to FDA-register and list.

    But a private label firm’s exemption from these obligations is based on the premises that the private label firm is not actually making (physically or virtually) the private label version of the device; is not actually engaged in relabeling or other manufacturing operation; and is not the specification developer.  Consequently, the private label firm’s establishment is not the place where the device is manufactured, assembled, or otherwise processed.  Instead, the manufacturer / specification developer has simply granted permission for the private label firm to distribute an identical version of the specification developer’s device, except that the private label version bears the name and branding of the private label firm instead of the manufacturer’s name and brand.  (To Judy’s great point, this can create even more confusion if one misappropriates requirements such as Europe’s “own branding” and MDD requirements, which cause a firm to become the “manufacturer” by simple virtue of putting a device on the market under its own name.)

    Confusion regarding U.S. private labeling can arise due in my opinion to the chicken-and-the-egg effect, where it might seem that the private label firm becomes the specification developer/manufacturer by having its name and branding on the device.  Yet as long as the original specification developer maintains ownership/control the specifications (i.e., the Device Master Record, including the labeling specifications for the private label variants), then the original specification developer remains the specification developer, and the private label firm’s ultimate role/function is effectively limited to that of a distributor.

    But this exemption ends if the private label firm sponsors/makes (either by actual or virtual means) the labeling changes independently (i.e., outside the control/authorization of the specification developer).  In that case, the private label firm does indeed become the specification developer / manufacturer.

    Your FDA registration/listing FAQ question "From this, I infer that the private label company and the manufacturer would both list the device.":

    When I consider FDA’s website registration/listing FAQ #4 in light of the premises I described above, I infer that “we” and “our” refers to the specification developer / manufacturer as distinguished from “a number of companies” who are the private label firms.  In FDA’s answer, I infer that “your” and “you” are likewise referring to the specification developer/manufacturer, but not the private label firms.  In other words, when a manufacturer/specification developer authorizes its devices to be distributed by other firms under private label branding arrangements (i.e., contracts), then the private label branded versions, in addition to the specification developer’s “in-house” brand, must all be identified in the specification developer’s device listings under its corresponding 510(k).  In fact, one of the first things that must be entered in the FURLS database when doing a device listing is the governing 510(k).  But if the private label distributor adheres to the aforementioned statutory boundaries, then there is no statutory/regulatory basis for it to register and list.

    For example, the FURLS system requires registrants to choose from the following categorizations when registering:

    • Manufacture Medical Device
    • Develop Specifications But Do Not Manufacture At This Facility
    • Manufacture Medical Device for Another Party (Contract Manufacturer)
    • Sterilize Medical Device for Another Party (Contract Sterilizer)
    • Reprocess Single-Use Device
    • Repack or Relabel Medical Device
    • Remanufacture Medical Device
    • Export Device to the United States But Perform No Other Operation on Device
    • Manufacture Device in the United States for Export Only
    • Complaint File Establishment per 21 CFR 820.198
    • Foreign Private Label Distributor

    So if a private label firm FDA-registers its establishment, then it would inevitably categorize itself as some type of manufacturer. Remember that the FDA considers manufacturers/specification developers to have ownership/control over the specifications, and/or device quality. Therefore if a private label firm identifies itself as a manufacturer via FURLS, then the FDA will (commensurate with device class) enroll the private label firm in the establishment inspection queue, consequently subjecting the private label firm to establishment inspections in order to enforce compliance with applicable good manufacturing practices, among other requirements. One of my private label distributor clients made this mistake [before they were my client of course :) ]. Because it registered itself as the manufacturer, FDA arrived in due course and performed a full GMP inspection of the firm’s facility. But the facility was just a business office and warehouse with no actual device development/manufacturing activities, and no ultimate ownership/control over such activities for the devices being distributed. This ultimately led to a lengthy GMP Warning Letter that proved to be rather tricky to get cleared.  In the end, the FDA ultimately accepted the re-categorization of the firm and its exclusion from FDA establishment registration and listing for the subject devices.

    Your question "The question came up, for me, in the context of UDI...":

    You are one of the foremost experts regarding UDI (and for many other topics too). So in my mind, your interpretation of the UDI requirements carries a lot of weight. Yet practicing UDI in the real world of OEM’s, contract manufactures, and private label firms can be a very convoluted maze. Heck, even FDA has had a hard time (in my opinion) getting a uniform grasp on all of the various practical permutations affecting UDI. Nonetheless, after carefully studying the UDI regulations and especially the Preamble, I've derived some basic guidelines that I use to decide who is the UDI “labeler” (which may not always be the person identified on the label).

    I’d be happy to share my corresponding thoughts with you and/or the Forum. But that will take some explaining, and seems to be outside the scope of this particular discussion thread. So I could add a response to the Forum thread to which I believe you’re referring. Or I could do that with you offline. Let me know which is preferred.

    All the best,

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
    Principal Consultant
    ComplianceAcuity, Inc.
    Golden CO
    United States
    www.complianceacuity.com
    Copyright 2016 by ComplianceAcuity. All rights reserved to credited usage within the RAPS Regulatory Forum.



  • 5.  RE: Private Label Agreements

    Posted 12-Jul-2016 15:34

    Thank you very much for the well reasoned and detailed answer. It will take me some time to digest it.

    ------------------------------
    Dan O'Leary
    Swanzey NH
    United States



  • 6.  RE: Private Label Agreements

    Posted 12-Jul-2016 16:12
    Edited by Kevin Randall 12-Jul-2016 16:13

    To help your digestion (I hope), here is related explanation that I received long ago from FDA, and that was “verified for accuracy by the appropriate CDRH Office or other FDA component.”:

     

    “…Company A is a registered medical device establishment with both a cleared 510(k), if product Z is not 510(k) exempt, and an active medical device listing (MDL) for product Z. Company A sells product Z labeled in part “Manufactured by Company A” with the product name X…

     

    …Company B can make arrangements with Company A to sell product Z labeled in part “Manufactured for Company B” or “Distributed by Company B” with the product name Y under Company A’s 510(k), if applicable, and MDL…

     

    …Company B is considered a private label distributor and is not required to register their establishment with FDA…unless they are not located in the USA. Furthermore, they are distributing product Z under Company A’s MDL so do not need to submit their own MDL unless they are not located in the USA…”

     

    Best regards,

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
    Principal Consultant
    ComplianceAcuity, Inc.
    Golden CO
    United States
    www.complianceacuity.com



  • 7.  RE: Private Label Agreements

    Posted 15-Jul-2016 02:53

    Dear Kevin,

    Thank you for the detailed discussion! I for one would be interested in your explanations about UDI labelers, as we are being asked many questions by private label customers in the USA who are confused about who should be entering what when they Import devices from us, a foreign manufacturer. Please let me know where I can find your UDI "thread".

    Thanks,

    Deborah 

    ------------------------------
    Deborah Ockert
    Regulatory Affairs
    DMG Dental-Material Gesellschaft mbh
    Hamburg
    Germany



  • 8.  RE: Private Label Agreements

    Posted 19-Jul-2016 13:52

    Guten Tag Deborah!  Another request for my UDI explanation has also been lodged, so I'll be certain to provide it for the Forum's consideration.  However, I have a few urgent client deliverables to which I must attend before I can provide the UDI explanation.  Thank you in advance for your patience in the meantime.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
    Principal Consultant
    ComplianceAcuity, Inc.
    Golden CO
    United States
    www.complianceacuity.com



  • 9.  RE: Private Label Agreements

    Posted 23-Jul-2016 15:09
    Edited by Kevin Randall 23-Jul-2016 15:15

    Thanks everyone for your patience waiting for my response to your private-labeler UDI questions.

     

    In order to define one’s UDI regulatory obligations (or for that matter, any other FDA regulatory obligations), it is crucial to understand and keep track of the responsibilities FDA assigns to each type of stakeholder based on the operations performed. A muddy confluence can occur where FDA’s regulatory requirements intersect with the dynamic business models often used in the medical device industry. Let’s look closer at what might be the most complicated UDI labeling scenario. Specifically, the scenario where:

     

    • The entity who owns/controls the finished-device specifications functions as a “specification developer” by way of arranging to have its finished devices fabricated by a contract manufacturer; and
    • Said contract manufacturer labels the devices with the specification developer’s original brand as well as one or more unique private-label, third-party brands.

     

    In this scenario, the FDA considers the specification developer to be the 830.3 UDI “Labeler” who is therefore ultimately accountable for assuring UDI compliance of all versions of the specification developer’s finished devices. This encompasses the specification developer’s original brand as well as any private-label variants. A fundamental reason is because the FDA requires the specification developer to own and control the specifications for the finished device, including the fabrication, labeling and packaging, regardless of who performs those operations.

     

    With refreshing coherence, FDA has woven this principle into UDI compliance by applying 21 CFR 820.50 (the regulations requiring a specification developer to control purchased or otherwise received services). This, and the Agency’s private-label policies I previously explained, are both echoed in the UDI preamble.  Specifically, the FDA stated (with my own notes for clarification purposes in square bold brackets):

     

    “…[UDI] Labeler—This term would mean any person who causes a label to be applied to a device, or who causes [i.e., authorizes] the label to be modified, with the intent that the device will be introduced into interstate commerce without any subsequent replacement or modification of the label…. In most instances, the labeler would be the device manufacturer, but the labeler may be a specification developer…The labeler would be responsible for meeting the UDI labeling requirements…”

     

    [BUT]

     

    “…The term labeler does not include a person [i.e., a contract manufacturer or private-labeler] who labels a device, or who modifies the label of a device, pursuant to the instructions of the person who actually places the device into interstate commerce. Thus, a contractor who labels a device, following the instructions of the specification developer…would not be the labeler…Instead, the person who ‘‘causes’’ the label to be applied or modified—the person who provided the labeling instructions…and who actually places the device into interstate commerce (FDA refers to such a person as a specification developer)—would be the labeler and would be responsible for meeting UDI labeling requirements…”

     

    [HOWEVER]

     

    “…The addition of the name of, and contact information for, a person [i.e., a private-label distributor] who distributes the device, without making any other changes to the label, would not be a modification…If a modification to the label extends beyond this narrow latitude, the person who causes the modification to be made will be a labeler and will be subject to the [UDI] requirements...”

     

    So to properly derive a particular stakeholder’s UDI obligations, it is critical to remember that the one who owns/controls the finished device specifications is the entity generally considered to be the 21 CFR 801.3/830.3 UDI “Labeler”.  And FDA’s preamble statements make it clear that the UDI Labeler is the party held ultimately accountable for assuring UDI compliance.

     

    Remember that, for practical intents and purposes, UDI compliance essentially boils down to:

    1. Assignment, documentation, and labeling of a proper UDI for the finished device; and
    2. Making the corresponding GUDID database entry.

    (As a side note, the integration of UDI operations into QMS procedures is a third task often strongly advocated, and understandably so. Yet the UDI regulations themselves don’t actually require corresponding QMS procedures to be established. Therefore I urge prudence in order to guard against unnecessarily bloating the QMS.)

     

    Regarding tasks 1 and 2, an important nugget I’ve taken from FDA’s preamble interpretations is that, as long as the UDI Labeler (i.e., the one who owns/controls the finished device specifications) maintains full control of assuring proper UDI compliance, then the Labeler may, per 21 CFR 820.50, delegate certain corresponding operational/implementing tasks. So now let’s take this down to the bottom line of DI’s, PI’s, and GUDID database entries.

     

    Perhaps the most straight-forward aspect of the aforementioned delegation would be generation of the UDI production identifier (PI) by the specification developer’s authorized contract manufacturer/labeler. That would just happen within the normal production and labeling procedures established within the contract manufacturer’s/labeler’s QMS, and would be ultimately supervised/assured by the specification developer via the specification developer’s 820.50 supplier controls.

     

    Much trickier is when the specification developer aims to delegate creation of the UDI device identifier (DI), and/or GUDID database entry. So we need to remember FDA’s preamble interpretations clarifying that the UDI Labeler is not the contract manufacturer/labeler or the private-labeler unless those entities perform the operations independent of the specification developer’s authorization and specifications. Accordingly, if a specification developer delegates to its contract manufacturer or a private-labeler the tasks of DI-generation and/or GUDID database entry, then the only way to do this without causing the contract manufacturer or private-labeler to breach the thresholds for “UDI Labeler” or “specification developer” is by ensuring that the Labeler code of the DI invariably remains that of the specification developer for all versions of its devices, including any and all private-label variants.  The device model code of the DI may however be variable as either the OEM’s model number or the private labeler’s model number.

     

    But if any contract manufacturer/labeler or private-label entity engages in fabrication and/or labeling (including UDI operations) not authorized and controlled by the specification developer (via the specification developer’s Device Master Record among other controls), then by default, the contract manufacturer/labeler or private-labeler itself becomes the specification developer (and consequently the UDI Labeler) of the resulting device. Likewise, if a contract manufacturer or private-labeler uses a DI wherein the DI labeler code is different than the device specification developer’s labeler code, then such an action signals to the Agency that the contract manufacturer or private-labeler is actually the UDI Labeler who, as emphasized in the aforementioned preamble narratives, owns/controls the finished device specifications. This in turn means the contract manufacturer or private-labeler would be held ultimately accountable for finished device quality, safety, etc., including burdensome responsibilities such as, but not limited to, design validation, complaint handling, failure investigations, and recalls. As evidenced by the corresponding pitfalls in the story I provided in my prior comments, such an arrangement doesn’t likely align with the actual intentions of the typical original specification developer, contract manufacturer, or private label entity.

     

    In the end, a specification developer is held ultimately responsible for ongoing sponsorship and coordination of UDI operations and compliance between itself and its contract manufacturers/labelers and private-label distributors. This should be accomplished via the contracts executed by the specification developer with its contract manufacturers/labelers and private-label distributors. The contract needs to carefully define the UDI roles and responsibilities so that unintended regulatory obligations and consequences are not triggered for the parties thereto.

    ------------------------------
    Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
    Principal Consultant
    ComplianceAcuity, Inc.
    Golden CO
    United States
    www.complianceacuity.com
    Copyright 2016 by ComplianceAcuity, Inc. All rights reserved to credited use within this Forum.



  • 10.  RE: Private Label Agreements

    Posted 12-Jul-2016 07:51

    It seems that your employers are confusing EU own-branding with US private-labeling.

     

    Judy Burton

    President

    Advena USA, LLC

    3010 LBJ Frwy

    12th Floor

    Dallas, TX 75234

     






  • 11.  RE: Private Label Agreements

    Posted 12-Jul-2016 16:48
    Lauren,

    I recently traveled to a firm and had a whole day meeting/discussion with a highly experienced litigation lawyer with few others. 

    Speaking of a contract that you refer to, provisions should include various aspects including, but not limited to the following:

    - FDA enforcement related issues (CGMP; complaint handling/MDR, recalls, etc.)
    - When product liability action is brought.

    As for complaint handling and MDR if duties and responsibilities are shared to some extent. you may submit an "Application for Variation" to the FDA. 

    In a signed agreement, details should be laid out.  

    Thus, you would need someone who can demystify all aspects of the CGMP/QSR, MDR, UDI and labeling with a lawyer who fully understands contract provisions with some level of CGMP understanding. 

    I know a corporate lawyer who has led to hundreds of recalls and consent decree including many deaths due to a total lack of awareness and understanding of CGMP requirements. 

    Thank you.  

    s/ David
    ______________________________________________
    Dr. David Lim, Ph.D., RAC, ASQ-CQA 
    Phone (Toll-Free): 1-(800) 321-8567



    "Knowledge is power only when it is practiced and put into action." - Regulatory Doctor

    NOTICE: This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying or distribution of this communication, or the taking of any action based on it, is strictly prohibited.





  • 12.  RE: Private Label Agreements

    Posted 19-Jul-2016 15:04
    Lauren,

    "They are convinced that we can eliminate our liability as a manufacturer of private label products by entering into contractual agreements w/ our private label customers in which they agree to assume liability for product recalls, supplier controls, etc."

    It is activity/action that is subject to regulatory control/requirements.  For your case, relationship should be well defined based on actual prospective activity within the meaning and scope of the application regulations.

    For example, 

    A distributor goes out and assembles a device and its components into a finished device on site. From the eyes of the QSR, the distributor can be viewed as a manufacturer based on the activity.

    In this case, some agreements need to be in place between the manufacturer and distributors.  

    Industry doesn't seem to best use the laws and regulations in view of their intended activity.  

    Thank you.  

    s/ David
    ______________________________________________
    Dr. David Lim, Ph.D., RAC, ASQ-CQA 
    Phone (Toll-Free): 1-(800) 321-8567



    "Knowledge is power only when it is practiced and put into action." - Regulatory Doctor

    NOTICE: This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying or distribution of this communication, or the taking of any action based on it, is strictly prohibited.