FAQ: Why a Compounding Pharmacy's Beyond-Use Date Is a Legal Argument, Not a Shelf Life
A compounding pharmacist extends a cream’s beyond-use date past USP’s default ceiling because years of practice say it’s still stable. Six months later, a state board inspector pulls the self-inspection form, points to the BUD field, and asks for the stability data behind that extension. There isn’t any on file. That single gap - a date without documentation - is a more common inspection finding than anything involving the drug itself, and it’s the moment a lot of compounding pharmacies start looking for software that can actually produce the paperwork an inspector asks for.
What are USP <795>, <797>, and <800>, and why do they matter to a pharmacy’s software?
<795> covers non-sterile compounding, <797> covers sterile compounding, and <800> covers hazardous drug handling across both. USP doesn’t enforce any of it directly - state boards decide which chapters to adopt, and several states now require strict compliance with all three. That means a pharmacy’s compliance software has to be configured to the specific combination its own state board enforces, not to USP’s text in the abstract.
Why is a beyond-use date a legal argument instead of a shelf-life number?
The default BUD is a conservative ceiling, not a measured expiration date. Extending it past that default requires documented stability or sterility data a pharmacy has to produce on request. State self-inspection forms ask directly whether an extended BUD is still <800>-compliant - inspectors aren’t checking the label, they’re checking the evidence behind it.
Why do sterile and non-sterile pharmacies need such different software?
A non-sterile operation under <795> alone needs sourcing records, formulation documentation, and BUD justification. Add sterile compounding under <797> and the software also has to track cleanroom monitoring, personnel certification, and media-fill testing on a schedule. Add a hazardous line under <800> and it needs closed-system device logs and ventilation records too. A pharmacy expanding categories usually learns its current software only covers the one it started with.
What makes a pharmacy actually start shopping for compliance software?
Almost never a proactive upgrade - it’s a specific trigger. A failed inspection finding on BUD documentation or hazardous-drug handling, a decision to add sterile or hazardous compounding to an existing operation, or a Joint Commission survey enforcing USP standards harder than the state board does alone. The same “it’s a specific gap, not a feature wishlist” buying pattern shows up in infusion clinics shopping for prior-authorization software - a different corner of the drug supply chain, but the same reactive trigger.
Does USP adoption mean the same thing in every state?
No - and that’s the hardest part of outbound into this niche. Some boards adopt all three chapters outright, some selectively, and some go further than USP on specific points, as Iowa’s board has on hazardous-drug handling. Software has to flex to the state board’s actual rule set, not just USP’s published chapters.
Talk to us if your outbound to compounding pharmacies is still pitching generic “USP compliance” instead of the specific chapter combination and inspection trigger that’s actually driving the buyer’s search.