The dual model that defines compounding pharmacy operations
A compounding pharmacy can operate under two regulatory regimes. Section 503A under the Federal Food, Drug, and Cosmetic Act covers traditional pharmacy compounding for patient-specific prescriptions, regulated primarily by state boards. Section 503B covers outsourcing facilities that voluntarily register with FDA to manufacture compounded drugs without patient-specific prescriptions, regulated under cGMP requirements approaching pharmaceutical manufacturing.
Many pharmacies operate both. A patient-specific compound for a single prescription runs under 503A. A bulk preparation for office stock runs under 503B. The ERP has to support both, on the same platform, without compromising either set of compliance requirements.
Generic ERP implementations treat both models the same and fail both. The 503B side fails because lot release is not enforced and adverse event reporting is not connected to operations. The 503A side fails because beyond-use dating is not calculated correctly and state-specific licensure is not tracked.
NetSuite, configured for compounding, enforces both regimes through structural features. Archer's compounding pharmacies industry page describes the configuration approach. This post focuses specifically on the 503B side, the more complex of the two.
A 503B outsourcing facility operates closer to a pharmaceutical manufacturer than to a traditional pharmacy. The ERP configuration has to reflect that operational reality.
What FDA registration actually requires from the ERP
Per FDA guidance on 503B facility definitions, an outsourcing facility must comply with cGMP requirements, report adverse events, register with FDA on a biennial schedule, submit drug listings, and maintain inspection-ready documentation. The ERP has to support all of these as part of operations.
| 503B requirement | NetSuite configuration |
|---|---|
| cGMP-compliant production | Manufacturing module with batch record references, material genealogy, and deviation handling through QMS |
| Lot release with quality unit approval | Mandatory approval workflow through Approvals App with electronic signature and meaning capture |
| Adverse event reporting (FDA 3500A) | Customer complaint records route to regulatory affairs through configured workflow |
| FDA registration and drug listing | Item master fields hold NDC, drug listing reference, and registration cycle dates |
| Multi-state pharmacy licensure | Drug License App tracks licensure by state with renewal management |
| Audit trail under 21 CFR Part 11 | System Notes audit trail enabled and protected on all GMP-relevant records |
| Adverse event tracking | Customer complaint records with regulatory significance flag and FDA reporting workflow |
The lot release configuration that prevents shipment without quality approval
The single most important 503B-specific configuration is the lot release workflow. Lots manufactured under 503B registration must have documented quality unit approval before shipment. The standard pattern for enforcement in NetSuite:
Step 01: Manufacturing creates the lot
The work order completes and the lot is created with a default status of Manufactured. This status blocks all outbound transactions. The lot exists in inventory but cannot ship.
Step 02: Quality testing posts to the lot record
Sterility, potency, identity, and other specifications are tested. Results post to the lot record from the LIMS integration or through manual entry. QMS manages the test plan and the result review workflow.
Step 03: Quality unit review
Quality unit reviews the batch record, test results, deviations, and supporting documentation. The review is documented through Approvals App with comments captured and electronic signature applied.
Step 04: Quality unit release decision
The quality unit either releases the lot (status changes to Released) or rejects (status changes to Quarantine or Destroyed). The decision requires electronic signature with meaning per 21 CFR Part 11.
Step 05: Outbound transactions enabled
Only lots with Released status can ship. The constraint is at the transaction level, not a manual check. The system enforces the rule.
This pattern is auditable end to end. An FDA investigator asking how a specific lot was released can see the test results, the quality review notes, the signature record, and the date and time of release. No part of the answer lives in a separate system or in paper records.
Adverse event reporting that connects to operations
503B facilities must report serious adverse events to FDA on Form 3500A within defined timelines. The reporting requirement is regulatory; the operational source is customer complaint records.
The configuration:
- Customer complaint records carry a flag for adverse event significance. Complaints flagged for regulatory significance route to regulatory affairs automatically.
- The customer complaint links to the lot record, allowing investigation of whether the event is associated with a manufacturing issue, a labeling error, or product use outside intended conditions.
- The investigation outcome documents the root cause and the corrective action through QMS CAPA workflow.
- The 3500A report is generated from the customer complaint and investigation records. Submission to FDA happens through the appropriate FDA portal; the submission reference is captured on the record.
- Timeline compliance is tracked: each adverse event has a reporting deadline based on severity, and the system flags overdue submissions.
What changes for the 503A side
The 503A side uses the same underlying lot tracking with different enforcement. Patient-specific compounds are made against a prescription, dispensed to a specific patient, and tracked by lot for stability and recall purposes. The configuration:
- Prescription record links to the patient (PHI-protected) and the compound formula
- The compound is made, lot-numbered, and dispensed
- Beyond-use date is calculated based on USP 795 or USP 797 rules depending on sterility classification
- Hazardous drug handling follows USP 800 with PPE and containment requirements documented
- State board licensure for the dispensing pharmacist is tracked through Drug License App
The 503A workflow is lighter than 503B but compatible. A pharmacy operating both can use one NetSuite environment with role-based access controlling which workflow each user can execute.
PCAB accreditation documentation
Many compounding pharmacies pursue PCAB accreditation for credibility and payer recognition. PCAB documentation requirements overlap heavily with the records NetSuite maintains for 503B and 503A operations. The accreditation review uses the same system records, formatted as PCAB-specific reports.
Audit preparation for PCAB moves from a project to a report. The data lives in the system. The report assembles it.
Related on archerinsights.com
- Compounding pharmacies. Archer's full configuration for 503A and 503B operations.
- NetSuite for compounding pharmacy hub. Foundation configuration for compounding operations.
- Drug stores and pharmacies industry page. Adjacent retail pharmacy operating model.
- Quality Management System. GMP and USP compliance workflows.
- Drug License App. Multi-state pharmacy licensure tracking.
- Approvals App for SOX-ready workflows. Quality unit lot release approvals.