Home›Blog›DSCSA Exception Handling: Data Errors vs Suspect Product
Published: November 20, 2026Last updated: November 20, 2026

DSCSA Exception Handling: Data Errors vs Suspect Product

AC
Anshuman ChaudharyCo-founder & CEO, Zelthy
Share:
DSCSA Exception Handling: a serialized carton under a scanner with an amber alert, a quarantine cage and a response clock

A serialized carton arrives at a distribution center with no matching EPCIS data, and the receiving team has to decide whether it is looking at a clerical error or a suspect product. The Partnership for DSCSA Governance estimates 8 to 10 billion package-level transactions a year. At that scale, even a small error rate produces a standing exception queue.

This post sits under Zelthy's guide to pharmaceutical traceability and goes deep on one operational question: how DSCSA exception handling connects to the verification and suspect product investigation duties in section 582 of the FD&C Act. Zelthy is an AI-native Platform-as-a-Service for life sciences operations, built on the open-source Zango framework, and its Traceability & Supply Chain vertical covers serialized tracking, GS1 data, DSCSA traceability and track and trace workflows.

Below: when an exception becomes suspect product, a workflow table with every clock, how product identifier verification fits an investigation, and what to automate. As of November 2026, the FDA exemptions for manufacturers, repackagers, wholesale distributors and larger dispensers ended between May and November 2025, and the small dispenser exemption runs to November 27, 2027.

What is a DSCSA exception, and when does it become suspect product?

A DSCSA exception is a mismatch between physical product and its transaction data (missing data, wrong data, or data with no product). It is not, by itself, suspect product. Product becomes suspect only when there is "reason to believe" it is counterfeit, diverted, stolen, intentionally adulterated, fraudulent or unfit for distribution.

The law draws the line in the definitions. Under 21 U.S.C. 360eee, a suspect product is one "for which there is reason to believe" it is potentially counterfeit, diverted, stolen, intentionally adulterated, the subject of a fraudulent transaction, or otherwise unfit for distribution, with the adulteration and unfitness limbs limited to product that could cause serious adverse health consequences or death. An illegitimate product requires "credible evidence" of the same. The FDA's final guidance on definitions of suspect and illegitimate product (March 2023) interprets those terms.

Data exceptions are a different thing. FDA's January 2024 guidance on enhanced drug distribution security at the package level describes "a clerical error or discrepancy in the product tracing information that may not be indicative of a suspect product", such as missing product, extra product, duplicate data or missing data. HDA's Exceptions Handling Guidelines sort these into six categories:

  • Data issue: missing master data, malformed files, data that does not match the barcode.
  • Damaged product: damaged cases or labels.
  • Product, no data: overages, aggregation errors, missing EPCIS files.
  • Data, no product: shortages, cancellations, refusals, loss or theft.
  • Packaging and labeling: lot mismatch, unreadable DataMatrix.
  • Product hold: out-of-sequence events or serials on hold.

The joint PDG, HDA and GS1 US workshop report puts the principle plainly: "The exception handling process is, and must remain, distinct from the suspect product investigation process."

An exception should escalate when it carries a risk signal. FDA's guidance on identification of suspect product lists the signals that matter: a new or unsolicited source, a price that is "too good to be true", a product in shortage or previously counterfeited, altered seals, lot or expiry that does not match the outer container, and labels with misspellings or foreign identifiers. A verification request that comes back with no match also changes the status: under section 582(b)(4)(C), a manufacturer that finds the product identifier does not match must treat the product as suspect.

DSCSA triage gate: data exceptions go to correct and release; suspect product goes to quarantine and investigate
Most exceptions are data problems to fix and release. Only those with a risk signal enter the suspect product investigation.

The cost of getting this wrong runs in both directions. Treat every exception as suspect and product stops moving; treat every one as a data fix and genuine suspect product can leave quarantine with a corrected file.

DSCSA exception handling workflow: triggers, required actions and clocks

The DSCSA sets hard clocks only at a few points: 24 hours to notify FDA and immediate trading partners after an illegitimate determination, 24 hours for a manufacturer to answer a verification request, and 6 years of investigation records. FDA guidance adds a 10 business day target for resolving data discrepancies.

The table separates statutory duties from FDA recommendations. Section references are to 21 U.S.C. 360eee-1 (FD&C Act section 582).

Three details trip teams up. The 24-hour clock starts at the illegitimate determination, not at receipt. FDA's preferred route for Form 3911 is the CDER NextGen portal, FDA assigns an incident number, and terminating a notification requires consulting FDA first. And for cleared product, the statute requires notice to FDA only "if applicable", so settle with regulatory counsel when that applies.

FDA enforces these clocks. Its June 2023 warning letter to Safe Chain Solutions cited an SOP that told staff to notify FDA "within 3 days", plus no written record of what was held in or released from quarantine, and investigations limited to the firm and its attorneys instead of its trading partners.

Product identifier verification and suspect product investigation requirements in practice

A suspect product investigation under section 582 has a fixed shape: quarantine, validate transaction history and transaction information, verify the product identifier down to the package level, coordinate with trading partners, then conclude the product is cleared or illegitimate and act on that conclusion within the statutory clocks.

Verification means checking that the package's product identifier matches what the manufacturer assigned (statutory definition). An investigation runs in this order:

  1. Quarantine. The statute allows a "physically separate area" or "other procedures", so a documented electronic hold can serve when the partner lacks physical possession.
  2. Validate transaction data. Check transaction information and history against the physical goods.
  3. Verify the product identifier. FDA's 2024 guidance says trading partners should verify suspect product "down to the package level" and, where there is reason to believe a shipment is suspect, "should not infer that aggregated data reflects the physical shipment of product". Dispensers have a specific floor: verify the product identifier of at least 3 packages or 10 percent of the suspect product, whichever is greater. Qualifying small dispensers are exempt from this floor until 27 November 2027.
  4. Coordinate. Contact the manufacturer, which is usually best placed to judge authenticity, and other trading partners in the chain.
  5. Conclude and act. Clear and release, or determine illegitimate, quarantine for disposition and notify within 24 hours.
  6. Retain. Keep the full file for at least 6 years after conclusion.

For step 3, the industry uses the Verification Router Service (VRS), which routes a GTIN, serial, lot and expiry query to the manufacturer and returns true or false. A failed match is a starting point for an investigation, not a verdict.

The PDG's 2024 simulation exercises found that "No organization can do an investigation alone," partly because transaction information is only a change-of-ownership record.

Write the escalation criteria down. Left to the receiving dock, the easy call is to treat a risk signal as a data fix.

What to automate in DSCSA exception handling, and what needs human judgment

Automate detection, matching, routing, clocks and record assembly. Keep the suspect and illegitimate determinations, the decision to file or terminate a Form FDA 3911, and the disposition of product with named, trained people. The statute assigns those determinations to the trading partner, not to a system.

Exception volumes justify the automation. In a Cardinal Health pilot reported to FDA, 364 of 507 EPCIS data samples (72%) contained exceptions, and "product arrived before data" got the highest priority for resolution. Data quality has improved since that 2022 pilot, but at billions of transactions a year even a low exception rate keeps a queue open.

Automate vs human decision: a robot arm sorts cartons into trays while a scale weighs a flagged carton for a person to judge
Systems match, route and time-stamp. People decide whether product is suspect or illegitimate.

Keep root-cause data (supplier, packaging line, exception type): the long-term goal is fewer exceptions, not faster correction.

On Zelthy, teams can configure this as a workflow at the data, permissions and reporting layer: an exception queue fed by serialized receiving events, triage rules, role-based approvals for suspect and illegitimate determinations, and timers tied to each clock.

Zelthy's traceability solution lists verification scanning, suspicious activity detection, counterfeit incident management, and DSCSA and EU FMD event reporting. Its compliance solution adds CAPA workflows and a tamper-evident audit trail that can hold the 6-year investigation record. Zelthy does not print codes or sell serialization hardware.

What the evidence from Zelthy deployments does and does not show

Zelthy has no approved metric specific to DSCSA exception handling, so this post does not claim one. A supply chain platform deployed on Zelthy (a blockchain-based traceability build) recorded 15% fewer stockouts and 25% faster inventory turnover. A vaccine ordering portal deployed on Zelthy served 3,000+ clinics with 15% faster order-to-delivery. Across verticals, 300+ applications are deployed on Zelthy in 12+ countries.

What carries over is the pattern, not the numbers. For the implementation sequence, see the executive's implementation guide to complete traceability. Teams tracking enforcement timing can read the companion post on DSCSA enforcement discretion.

Designing a DSCSA exception workflow? Book a demo with Zelthy to see how it can be configured on the platform.

Frequently asked questions

Is a DSCSA data exception the same as a suspect product?

No. A data exception is a mismatch between product and transaction data, and FDA says such discrepancies may not be indicative of a suspect product. Product becomes suspect only when there is reason to believe it is counterfeit, diverted, stolen, intentionally adulterated, fraudulent or unfit for distribution.

How long do you have to notify FDA of an illegitimate product under the DSCSA?

Not later than 24 hours after determining the product is illegitimate. The notice goes to FDA on Form FDA 3911, preferably through the CDER NextGen portal, and to all immediate trading partners. The clock starts at the determination, not when the product was received.

How quickly should DSCSA data discrepancies be resolved?

FDA's January 2024 guidance recommends resolving errors or discrepancies in product tracing information within 10 business days. This is a nonbinding recommendation, and the product should not be sold to the next trading partner until the discrepancy is resolved.

How long must suspect product investigation records be kept?

The DSCSA requires manufacturers, repackagers, wholesale distributors and dispensers to keep records of a suspect product investigation for not less than 6 years after the investigation concludes.

Can DSCSA quarantine be electronic?

Yes. The statute defines quarantine as storage in a physically separate area or through other procedures that prevent distribution. A documented electronic hold can therefore qualify, particularly when a trading partner does not physically hold the product; where it does, segregate the product physically as well.

This article summarizes the DSCSA and FDA guidance as of November 2026 for general information. It is not legal advice; confirm obligations with your regulatory and legal teams.

Sources

  1. 21 U.S.C. 360eee-1, Requirements (FD&C Act sec. 582). US Code via GovInfo, 2021 edition.
  2. 21 U.S.C. 360eee, Definitions (FD&C Act sec. 581). US Code via GovInfo, 2021 edition.
  3. Enhanced Drug Distribution Security at the Package Level Under the DSCSA, Guidance for Industry. FDA, January 2024.
  4. Definitions of Suspect Product and Illegitimate Product for Verification Obligations Under the DSCSA. FDA, March 2023.
  5. DSCSA Implementation: Identification of Suspect Product and Notification (Revision 1). FDA, June 2021.
  6. Notify FDA of Illegitimate Products. FDA, updated June 12, 2024.
  7. Exemptions under the Drug Supply Chain Security Act. FDA, updated August 26, 2026.
  8. DSCSA Exemptions from Section 582(g)(1) and Other Requirements of the FD&C Act for Certain Trading Partners. FDA, October 9, 2024.
  9. DSCSA Exemptions from Certain Requirements Under Section 582 of the FD&C Act for Small Business Dispensers Until November 27, 2027. FDA, August 6, 2026.
  10. Warning Letter to Safe Chain Solutions, LLC (#636044). FDA, June 8, 2023.
  11. Exceptions Handling Guidelines for the DSCSA. Healthcare Distribution Alliance, April 2022.
  12. Exception Handling Workshop Report. Partnership for DSCSA Governance, HDA and GS1 US, 2023.
  13. Suspect Product Investigation Report Out. Partnership for DSCSA Governance, 2024.
  14. Interoperability Data Exchange Errors and Exception Handling: DSCSA Pilot Project Final Report. Cardinal Health, updated September 2022.

Similar Blogs