Questions
we hear often.

CRAVE is a quality management system (QMS) built specifically for 503A compounding pharmacies. It maps your regulatory obligations across USP 795, 797, and 800, automates attestation workflows, manages your SOP library, and generates inspection-ready evidence packets — continuously, not just before an audit.

The goal is simple: your compliance posture should be current every day, so an inspector walking in tomorrow finds the same thing they'd find if you had six months of notice.

General QMS platforms are built for broad healthcare or manufacturing settings. CRAVE is built exclusively around the compliance framework that governs 503A compounding — USP chapters, State Board rules, DEA requirements, and accreditation standards like ACHC-PCAB and NABP.

That means the workflows, obligation calendars, and evidence formats reflect how compounding inspections actually work — not a generic interpretation of quality management.

CRAVE is fully web-based — nothing to install, no IT department required. You access it from any browser, on any device. Your team can attest, review, and manage compliance from the dispensing counter, the cleanroom anteroom, or offsite.

CRAVE covers USP 795 (non-sterile compounding), USP 797 (sterile compounding), and USP 800 (hazardous drug handling). Obligations are mapped to your specific license type — so a non-sterile only pharmacy won't see 797 workflows, and a sterile facility gets the full category 1, 2, and 3 framework.

When USP chapters are revised, CRAVE maps the changes to your existing obligations automatically and surfaces the gaps that need attention.

Yes. State Board rules are layered on top of USP chapter requirements based on your jurisdiction. Because State Board regulations vary — and frequently differ from the federal baseline — CRAVE applies state-specific overlays to your obligation calendar so nothing falls through the gap between federal and state requirements.

Yes. CRAVE is designed with accreditation readiness in mind. The documentation, evidence trails, and SOP version control within the platform align with what ACHC-PCAB and NABP reviewers expect to see. You're not assembling a binder weeks before your survey — the documentation is current and organized every day.

Yes. DEA obligations relevant to 503A compounding operations are tracked alongside USP and State Board requirements in a unified obligation calendar — so nothing exists in a separate spreadsheet or manual process.

When a chapter is revised, CRAVE identifies the delta between the old and new requirements and maps it to your obligations. You receive alerts for gaps created by the revision — with enough lead time to update SOPs and workflows before the effective date.

You don't have to read a Federal Register PDF and figure out what it means for your specific operation. CRAVE does that translation for you.

Attestations are triggered automatically based on your obligation calendar. Staff receive notifications when attestations are due, complete them through CRAVE with a legally-compliant electronic signature, and the record is timestamped and stored immediately.

You see real-time status across your entire team — who has attested, who hasn't, and what's coming due — without chasing anyone down or maintaining a manual log.

Yes. All attestations and document signatures in CRAVE are compliant with the Electronic Signatures in Global and National Commerce Act (ESIGN) and the Uniform Electronic Transactions Act (UETA). They carry the same legal weight as a wet signature and are fully admissible in regulatory proceedings.

Evidence packets are generated on demand and formatted the way inspectors expect to receive documentation — organized by chapter and obligation, with timestamped attestations, SOP version history, training records, and environmental monitoring logs compiled into a single exportable package.

When an inspector arrives, you're not spending two hours pulling records from different systems. You generate the packet and hand it over.

CRAVE provides a centralized SOP library with full version control. Every revision is tracked with an author, date, and change log. Staff acknowledgments are captured electronically. When a USP chapter revision affects an SOP, CRAVE flags it for review so your documentation stays aligned with current standards.

CRAVE manages your existing SOPs — it doesn't replace them or dictate their content.

Yes. CRAVE supports role-based access for your entire team. Pharmacists-in-charge, compliance officers, and technicians each see dashboards and workflows scoped to their role. Owners and administrators have full visibility across the organization. Nothing is shared through a single login.

Most pharmacies are fully operational in under a week. You provide your license type, jurisdiction, and operational details — CRAVE maps your obligations from there. There's no lengthy implementation, no configuration project, and no IT team required.

You can bring existing SOPs and documentation into CRAVE, but you don't have to migrate everything before going live. Many pharmacies start with CRAVE handling new attestations and obligations while gradually importing their existing SOP library. We'll help you plan the right approach for your situation during onboarding.

Support is provided by people who understand the compounding compliance domain — not a general-purpose help desk. If you have a question about how a specific USP requirement maps to a workflow, or how to document a deviation properly, you'll get an answer from someone who has been on both sides of that conversation.

Absolutely. Non-sterile 503A pharmacies still carry substantial USP 795 and USP 800 obligations, State Board requirements, and DEA compliance needs. CRAVE scopes your workflows to your operation — you won't see sterile compounding requirements that don't apply to you, and the platform is fully functional for non-sterile only facilities.

Yes, if your in-house operation includes 503A compounding. The USP chapter obligations, State Board requirements, and inspection standards are the same regardless of the broader organization those operations sit within. CRAVE handles the compliance infrastructure for the compounding operation specifically — it works alongside your existing institutional systems, not in competition with them.

CRAVE was designed to reduce the burden on lean teams, not add to it. A small pharmacy where the owner is also the pharmacist-in-charge is exactly who benefits most from automated attestation triggers, real-time compliance scores, and evidence packets that assemble themselves. You shouldn't need a dedicated compliance staff member to stay inspection-ready.

Yes. Multi-site organizations can manage compliance across locations within a single CRAVE account — with location-specific obligation calendars that reflect each site's license type and jurisdiction, and consolidated reporting for ownership or compliance leadership who need visibility across the group.

Pricing is based on the size and configuration of your operation. We don't publish a one-size rate because the right configuration for a single-location non-sterile pharmacy looks different from a multi-site sterile operation — and we'd rather get that right than have you pay for something that doesn't fit.

Book a 30-minute walkthrough and we'll walk through your specific obligations and give you accurate pricing before you commit to anything.

We'll cover contract terms during the demo and scoping process — flexibility is something we build into our agreements. We'd rather earn your continued business by making CRAVE genuinely useful than lock you in through contract terms.