DSCSA Suspect and Illegitimate Product Investigation SOP
DSCSA Suspect and Illegitimate Product Investigation SOP template for quarantining, tracing, documenting, and escalating questionable drug product before it reaches patients.
Trusted by frontline teams 15 years of frontline software
Built for: Pharmaceutical Distribution · Hospital Pharmacy · Wholesale Drug Distribution · Specialty Pharmacy · 3pl Healthcare Logistics
Overview
This SOP template defines the end-to-end process for handling suspect and illegitimate drug product under DSCSA-style controls. It walks the user through identifying a concern, placing product in quarantine, capturing the initial facts, escalating to compliance leadership, investigating traceability and source, deciding whether the product is illegitimate, releasing verified product when appropriate, and sending trading partner and FDA notifications when required.
Use this template when a product cannot be confidently verified, when packaging or labeling appears altered, when chain-of-custody records do not reconcile, or when a trading partner flags a potential issue. It is especially useful for receiving teams, pharmacy operations, quality groups, and distribution centers that need a repeatable response with clear ownership and documentation.
Do not use this template as a generic recall procedure or as a substitute for routine inventory reconciliation. It is also not the right tool for simple temperature excursions unless the excursion creates a suspect product concern. The value of the template is that it forces a controlled hold, a documented investigation, and a formal disposition so product is not released by mistake.
Standards & compliance context
- This template supports DSCSA suspect and illegitimate product handling by requiring quarantine, traceability review, and required notifications.
- The recordkeeping structure aligns with ISO 9001:2015 documented information expectations by preserving evidence, approvals, and final disposition.
- If the investigation involves hazardous handling, add permit-to-work controls, PPE requirements, and escalation criteria consistent with OSHA process safety practices.
- If your organization uses serialized product controls, the template can be adapted to preserve traceability data needed for trading partner verification and audit review.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns a regulatory response into a repeatable sequence with clear actors, verification points, and escalation triggers.
-
Identify the suspect product
The receiving associate or pharmacist verifies the product against the purchase record, package labeling, lot number, expiration date, serial number, and physical condition. The role records any discrepancy that could indicate suspect product, including missing transaction data, damaged packaging, altered labeling, or chain-of-custody gaps.
-
Quarantine the product immediately
The receiving associate places the suspect product in a designated quarantine area and applies a quarantine label that clearly states ‘Do Not Use’ or equivalent restricted-status wording. The role separates the product from saleable inventory and preserves all packaging, labels, and shipping materials.
-
Document the initial finding
The receiving associate records the product name, NDC or product identifier, lot number, serial number, expiration date, supplier, date received, and the specific discrepancy observed. The role captures photos of the product, packaging, and any damaged or inconsistent labels when available.
-
Escalate the case to compliance leadership
The receiving associate notifies the Pharmacist-in-Charge, Compliance Manager, or designated competent person immediately after quarantine. The role provides the documented discrepancy, product identifiers, and location of the quarantined item for review and next-step authorization.
-
Investigate product status and traceability
The compliance manager reviews transaction information, product verification data, and any available EPCIS or pedigree records. The role contacts the trading partner or upstream source to confirm shipment details, verify the transaction history, and determine whether the product is suspect, illegitimate, or acceptable.
-
Determine whether the product is illegitimate
The compliance manager evaluates whether the evidence meets the criteria for illegitimate product, including counterfeit status, diversion, stolen product, intentionally adulterated product, or product that is the subject of a fraudulent transaction.
-
Release verified product from quarantine
The compliance manager authorizes release only after verification confirms the product is legitimate and the discrepancy is resolved. The role removes the quarantine label, updates the inventory record, and documents the basis for release.
-
Notify trading partners and FDA as required
The compliance manager notifies the relevant trading partners and submits the required FDA notification for illegitimate product within the required timeframe. The role includes product identifiers, investigation findings, quarantine status, and any known distribution impact in the notification record.
-
Close the investigation and retain records
The compliance manager finalizes the case file with the investigation summary, decision rationale, notification evidence, disposition of the product, and corrective actions if needed. The role retains records according to the company document retention policy and applicable DSCSA requirements.
How to use this template
- The compliance owner configures the SOP with site-specific quarantine locations, escalation contacts, notification channels, and required record fields before it is put into use.
- The receiving or operations role identifies the suspect product, stops movement, and places the item in a clearly marked quarantine area with access control.
- The investigator documents the product identifiers, source, observed deviation, photos, and any traceability records needed to support the case.
- The compliance lead reviews the evidence, determines whether the product is suspect or illegitimate, and assigns any required trading partner or FDA notification actions.
- The responsible role closes the case by releasing verified product, disposing of illegitimate product, and filing the final record with all approvals and follow-up actions.
Best practices
- Quarantine the product before any further handling so the chain of custody stays intact.
- Capture lot number, serial number, NDC or other identifiers, and the exact reason for suspicion at the moment of discovery.
- Photograph packaging, labels, seals, and any damage before the product is moved or repacked.
- Assign one case owner who controls the investigation, evidence log, and escalation path from start to finish.
- Use a clear verification step before release so no product leaves quarantine on verbal approval alone.
- Document every deviation from normal traceability, including missing records, mismatched identifiers, and unexplained transfers.
- Escalate immediately when the product source cannot be verified or when tampering, counterfeiting, or diversion is suspected.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this SOP template cover?
This template covers the full workflow for suspect or illegitimate drug product: identification, immediate quarantine, documentation, escalation, traceability review, disposition, and required notifications. It is designed to produce a defensible investigation record rather than a loose checklist. Use it when a product has an unknown source, suspicious packaging, broken chain of custody, or other DSCSA red flags.
Who should run this SOP?
A trained compliance, quality, or pharmacy operations role should own the investigation, with warehouse or receiving staff handling the initial hold and segregation. A competent person should review the evidence and make the disposition decision, especially when regulatory reporting may be required. If your organization has a designated responsible person for DSCSA issues, this SOP should route the case there immediately.
How often is this SOP used?
It is event-driven, not scheduled. You use it whenever a suspect product is identified, whether during receiving, inventory review, returns processing, complaint handling, or a trading partner notification. The template also works well as the basis for periodic drills so staff know how to quarantine and escalate without delay.
Does this template align with DSCSA requirements?
Yes, it is built around DSCSA-style suspect product handling, traceability review, trading partner notifications, and FDA reporting triggers. It also supports ISO 9001 documented information practices by requiring clear records, approvals, and retention of investigation evidence. You should still adapt the workflow to your company’s legal review and state-specific operating model.
What are the most common mistakes this SOP helps prevent?
The biggest failures are delayed quarantine, incomplete product identification, missing lot or serial data, and informal verbal handoffs that leave no audit trail. Another common problem is releasing product before the investigation is closed or before all required notifications are made. This template forces the team to capture evidence, assign responsibility, and document the final disposition.
Can we customize this for our warehouse, pharmacy, or distributor workflow?
Yes, and you should. Add your receiving locations, quarantine storage method, escalation contacts, trading partner notification paths, and any internal approval gates. You can also tailor the evidence fields for serialized product, returns, recalls, temperature excursions, or counterfeit indicators.
What systems should this SOP connect to?
It should connect to your quality management system, inventory or ERP platform, complaint log, and any DSCSA traceability or serialization tools you use. If your team tracks cases in a ticketing system, add the case number and required status changes so nothing is lost between departments. The template works best when the record in the SOP matches the record in the system of record.
How is this different from an ad hoc investigation?
An ad hoc response often depends on memory, email threads, and whoever happens to be available. This SOP creates a repeatable sequence with clear actors, verification points, escalation criteria, and documentation requirements. That makes it easier to prove you quarantined the product, investigated it, and notified the right parties on time.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
Discover how Problem Management, Change Management, and structured hiring records give operations teams the audit trails they need to stop repeating costly...
-
A roundup on retaining institutional knowledge, building trustworthy schedules, and keeping AI agents governed with permissions and audit logs.
-
A vendor-agnostic checklist covering architecture, frontline access, AI, compliance, and payroll to evaluate any scheduling platform.
Ready to use this template?
Get started with MangoApps and use DSCSA Suspect and Illegitimate Product Investigation SOP with your team — pricing built for small business.
