503A or 503B: what a reviewer asks about your compounder

Two registration types, two sets of permissions, and a distinction that telehealth operators get wrong in their own applications more often than any other single fact. It matters because the certification reviewer will check, and because the answer determines what your partner may lawfully make for you and therefore what you may lawfully sell.

The distinction

A 503A pharmacy is a traditional compounding pharmacy. It prepares medications for an identified individual patient pursuant to a prescription. It is licensed by state boards of pharmacy, it operates under pharmacy compounding standards rather than manufacturing ones, and it needs non-resident licensure in the states it ships into.

A 503B outsourcing facility is registered with the FDA. It may produce medications in bulk without patient-specific prescriptions, and it is subject to current good manufacturing practice requirements and to FDA inspection.

The practical difference for a telehealth business is the model each supports. A 503A relationship follows the prescription: a patient is identified, a prescriber writes, the pharmacy prepares for that patient. A 503B relationship can supply stock, which is why it typically serves clinics and health systems dispensing from inventory rather than direct-to-consumer brands shipping to patients.

Where operators get it wrong

Calling a 503A partner a 503B because it sounds more regulated. Registration with the FDA does sound reassuring, and it appears in application copy that has never been checked against the partner's actual registration. This is a discrepancy a reviewer finds in one lookup.

Assuming a bulk supply arrangement is compatible with a 503A relationship. If your model involves product prepared ahead of an identified patient, the registration type that supports it is not the one you probably have.

Not knowing who actually dispenses. Fulfilment platforms sit between clinics and pharmacies, and the brand name on the platform is not the dispensing entity. The reviewer wants the entity, its registration and its state licensure, which is covered in your pharmacy partner is part of your application.

Treating registration as an answer to the claims question. Neither registration type makes a compounded preparation an approved product, and neither licenses a comparison to a brand-name drug. That is a separate issue and it is where most applications in these categories actually fail.

What the reviewer will establish

For whichever type applies: the legal entity, the registration or licence numbers, the states it is licensed to ship into, what it prepares for you, and whether that sits within its permitted scope.

Two derived checks follow, and they are worth running yourself first.

State coverage. The states you market in, against the states your prescribers are licensed in, against the states your pharmacy can ship into. Gaps between those three columns are questions waiting to be asked.

Scope alignment. What you sell, against what your partner is permitted to prepare. A product outside your partner's scope is a problem for both of you and it will not be resolved by an explanation.

Multiple partners, and changing them

Brands frequently use more than one, sometimes by geography and sometimes by product. That is unremarkable, but each relationship needs the same documentation, and your website should describe the arrangement accurately rather than naming whichever partner was first.

Changing partners while certified is likewise ordinary, and the obligation is disclosure rather than permission. What causes trouble is a quiet swap that leaves your own site describing the previous arrangement, which is a discrepancy sitting in plain view on a page a reviewer reads during monitoring.

Why this belongs in the file rather than in the correspondence

Every fact above is knowable before you submit and cheap to assemble. Supplied up front it is a section of the application. Requested during review it is a round trip that depends on a third party's response time as well as your own, which is the most avoidable kind of delay there is.

The rest of the document set is in what a complete file looks like. The eligibility question that sits underneath all of it, whether your product category can be certified at all, is compounded products and certification eligibility.

The five facts to have on file for each partner

Written down, kept current, and supplied with the application rather than after it.

• The legal entity that dispenses, not the trading or platform name.
• The registration type and the numbers that evidence it.
• The states it holds licensure for, including non-resident licensure.
• The specific preparations it makes for you, and the basis on which they sit within its permitted scope.
• The agreement, with the effective date and the termination terms.

If any of those takes more than a day to obtain from your partner, that is useful information about how a request for information will go while a review is open.

What your own website should say about it

Two disclosures, and both are ordinary rather than onerous. Name the pharmacy that prepares your products, and say plainly that the preparations are compounded.

Brands sometimes resist the first on the grounds that the relationship is commercially sensitive. In practice the relationship is discoverable, the disclosure is expected, and a site that avoids naming who makes its medicines reads exactly as evasive as it sounds. The second is not optional in substance: a compounded preparation described without the word compounded is a presentation problem before anybody gets to the claims.

Keep both accurate through partner changes. A site describing the previous arrangement is a discrepancy sitting in plain view on a page a monitor reads.