The dual-model problem
A 503A pharmacy compounds patient-specific prescriptions under traditional pharmacy regulation. A 503B outsourcing facility manufactures sterile and non-sterile preparations for office use under FDA registration, with cGMP expectations approaching small batch pharmaceutical manufacturing. Many pharmacies operate both models. The ERP has to support both, on the same platform, without compromising either set of compliance requirements.
As Archer's compounding pharmacies industry page describes, compounding pharmacy operations run under some of the most detailed regulatory requirements in healthcare: USP 795, USP 797, USP 800, state board oversight, and for 503B facilities, FDA manufacturing-level scrutiny. NetSuite handles both. The configuration enforces lot tracking, beyond-use dating, USP compliance documentation, and FDA outsourcing facility reporting through structural features, not external systems.
503A and 503B run on different regulatory tracks. Configuring NetSuite to enforce both, on the same platform, is what separates a compliant operation from a finding during inspection.
Why generic ERP fails compounding pharmacy operators
Beyond-use dating
BUD is calculated against compound type, sterility, storage condition, and stability data. Generic inventory expiration dating does not accommodate the rules.
USP chapter compliance
USP 795 for non-sterile, 797 for sterile, 800 for hazardous. Each has documentation, environmental monitoring, and quality requirements that touch ERP records.
503B FDA registration
Outsourcing facilities operate under FDA registration with adverse event reporting, lot release documentation, and product labeling requirements approaching pharmaceutical manufacturing.
PCAB accreditation
PCAB accredited pharmacies maintain documentation standards that have to be supportable from system records.
How Archer configures NetSuite for compounding pharmacy
Beyond-use dating is configured as a calculated field on lot records, with rules driven by compound type, sterility, and storage. The system blocks dispense or shipment of expired lots at the transaction level.
USP chapter compliance documentation flows from approval workflows and audit trail configuration. Archer's Quality Management System module manages environmental monitoring data, personnel qualification, and corrective and preventive action records. Drug License App tracks state board licensure across multi-state operations.
503B configuration enforces lot release workflows that require quality unit approval before product is available for shipment. Approvals App routes the quality release decision with full audit trail. Adverse event reporting routes from customer complaint records to the regulatory reporting workflow.
PCAB documentation flows from standard reports configured against the accreditation criteria. Audit preparation moves from a project to a report.
Related on archerinsights.com
- Compounding pharmacies industry page. Archer's full configuration approach for 503A and 503B operations.
- Drug Stores and Pharmacies industry page. Adjacent retail and regional pharmacy operating model.
- Quality Management System. USP and FDA compliance workflows inside NetSuite.
- Drug License App. Multi-state pharmacy licensure tracking.
- Approvals App for SOX-ready workflows. Quality unit lot release approvals.
- Case studies. Documented compounding pharmacy engagements.
External references
- FDA Registered Outsourcing Facilities (503B)
- USP General Chapter 795: Non-sterile Compounding
- USP General Chapter 797: Sterile Compounding
- USP General Chapter 800: Hazardous Drugs
- PCAB Compounding Pharmacy Accreditation
Run 503A and 503B on the same NetSuite platform without compromising either
A discovery call with an Archer implementation lead. Bring your 503A and 503B mix and your current compliance approach, and leave with a clear assessment of NetSuite configuration gaps.