Detained Without Physical Examination: How FDA Import Alerts Work — and What It Takes to Get Off the List

The email arrives on a Tuesday afternoon. Your customs broker confirms it: your shipment has been flagged under FDA Import Alert 66-40, detained at the port of Los Angeles, and will not be released without regulatory action. You’re looking at $4,000–$8,000 in monthly port storage fees, a supply chain that’s suddenly frozen, and a customer asking where their product is.

This isn’t a hypothetical. FDA maintains over 100 active import alerts at any given time, and firms from more than 80 countries appear on these lists. Once your facility or product is added, every future shipment clears customs through an automated flag — no physical inspection needed. The system is called Detained Without Physical Examination, or DWPE, and it’s one of the most operationally disruptive enforcement tools in FDA’s arsenal.

Here’s what most regulated manufacturers don’t fully understand until they’re already in it: getting on an import alert is often faster than getting off. The removal process is document-intensive, district-specific, and frequently mishandled by companies that treat it like a standard CAPA exercise. It isn’t.

How FDA Import Alerts Work — and Why DWPE Is Different From a Standard Detention

FDA’s import surveillance program runs through the Office of Regulatory Affairs (ORA), integrated with U.S. Customs and Border Protection (CBP) through the Automated Commercial Environment (ACE) system. When a shipment arrives, ACE cross-references the importer, manufacturer, product line, and entry codes against FDA’s import alert database. If there’s a match, the system automatically generates a detention notice — no inspector needs to lay eyes on the cargo first.

DWPE is the designation that makes import alerts particularly painful. Under a standard detention, FDA may physically examine samples before making a decision. Under DWPE, the agency has already determined it has sufficient prior evidence of a violation to detain automatically. That evidence typically comes from one of three sources: a history of analytical failures on sampled shipments, direct observation findings from a facility inspection (Form 483 or Warning Letter), or a pattern of adulteration or misbranding documented through agency records.

The most frequently cited import alerts for regulated manufacturers in the U.S. market include:

• Import Alert 66-40: Dietary supplements and their ingredients detained for apparent cGMP violations under 21 CFR Part 111.
• Import Alert 66-66: Articles that appear to be unapproved new drugs, triggering potential detention under the FDCA.
• Import Alert 99-32: Products showing evidence of contamination — filth, decomposition, or pesticide residues — under 21 CFR 402.

Each import alert has a charge code and a corresponding CFR citation. That specificity matters enormously when you’re building a removal package, because FDA’s reviewers expect to see corrective action mapped directly to the cited violation. A general quality improvement narrative won’t move the needle.

The Removal Request: What FDA Actually Wants to See

FDA’s official mechanism for getting off an import alert is the Request for Removal from Import Alert (RFRIA). The process is outlined in FDA’s Compliance Policy Guide (CPG) Sec. 9900.204, and the burden of proof sits entirely with the firm.

The agency’s threshold is “credible evidence” that the underlying violation has been fully corrected. In practice, that means a package that typically includes:

1. A detailed corrective action summary — not a CAPA form, but a narrative that explains what caused the violation, what systemic changes were made, and how those changes are sustained over time.
2. Updated and version-controlled SOPs — with training records demonstrating that personnel have been trained on the new procedures.
3. Independent third-party audit report — conducted by a qualified auditor against the relevant GMP standard. FDA district reviewers give substantially more weight to third-party findings than internal audit reports.
4. Analytical data for recent production lots — demonstrating that the specific quality failure (if the alert was triggered by analytical results) is no longer occurring.
5. A root cause analysis — not a one-sentence summary, but documented evidence that the firm dug to a true systemic cause rather than addressing surface symptoms.

Here’s where companies consistently underestimate the process: the RFRIA doesn’t go to FDA headquarters in Silver Spring. It goes to the district office that issued the import alert or that has jurisdiction over the firm’s geographic region. District reviewers have some latitude in how they weigh evidence, which means a package that satisfies one district may not satisfy another. Regulatory compliance consulting experience in navigating district-specific expectations is genuinely valuable here — it’s not something you figure out from the CPG alone.

Average processing time for an RFRIA, once submitted with complete documentation: 6 to 18 months. Firms that submit incomplete packages often wait out a denial and then restart the clock. And while your case is pending, every shipment continues to be detained automatically.

Where AI-Augmented Regulatory Compliance Consulting Changes the Math

The documentation burden of an RFRIA submission is, by design, substantial. A well-constructed removal package for a dietary supplement manufacturer under Import Alert 66-40 can easily run 300–500 pages — SOPs, training logs, batch records, analytical certificates, audit reports, root cause analyses, and a cover letter that ties all of it together coherently.

The problem isn’t generating the documents. Most quality systems already produce this material. The problem is coherence: FDA reviewers are looking for gaps between what your corrective actions claim and what your supporting documents actually demonstrate. And those gaps are remarkably easy to miss when a compliance team has been living inside the same quality system for months.

AI-augmented audit tools address this specific failure mode. At Aurora TIC, we use decision-grade AI to cross-reference CAPA documentation against the specific CFR citations in the import alert, flagging inconsistencies between claimed corrections and the underlying procedural records. The system reads across SOPs, batch records, and analytical data simultaneously — something that a human reviewer working under deadline pressure will simply not do with the same thoroughness.

Practically, this looks like: the AI identifies that your updated SOP 4.3 references a raw material specification limit that still appears at the old (non-compliant) value in three batch records from the past 90 days. That’s the kind of discrepancy that, if FDA finds it first, kills your removal request and forces you to restart the documentation process. If your team finds it first, it’s a fixable gap before submission.

We’ve also seen natural language processing surface inconsistencies in root cause analyses — places where a firm’s narrative describes a “human error” cause without any documented systemic change to prevent recurrence. FDA reviewers are experienced at spotting exactly this pattern, and they treat it as evidence that the correction isn’t sustainable.

Building a Package That Actually Gets Accepted

Beyond the AI-assisted document review, the structure of the removal request matters as much as its contents. A few principles that consistently separate accepted packages from rejected ones:

Lead with the regulation, not the story. Your cover letter should open by identifying the specific import alert number, the specific charge code, and the specific CFR provision cited. FDA reviewers process many of these submissions. A cover letter that makes them search for the regulatory hook signals a package that probably has similar organizational problems throughout.

Map every corrective action to a specific finding. If the import alert cited a failure to establish identity specifications for incoming ingredients per 21 CFR 111.70(b), your CAPA section should reference that exact provision and demonstrate — with specific, dated evidence — that the specification now exists, that it’s been implemented in at least three production cycles, and that testing records confirm it’s working.

Don’t lean on internal audit results. This is the most common mistake we see in self-prepared removal packages. An internal audit saying “all systems are in compliance” carries almost no evidentiary weight with FDA district reviewers. A third-party audit against the same standard — conducted by someone who has no institutional incentive to find you compliant — is a different matter entirely.

Include lot-specific data, not facility-level claims. If your removal relates to contamination or analytical failures, FDA wants to see test results from specific recent lots, with method references, lab accreditation documentation (ISO 17025 where applicable), and a clear statement of what specification each lot was tested against.

Request a voluntary meeting if your situation is complex. FDA’s Import Division will sometimes grant pre-submission meetings for firms with complicated compliance histories. This isn’t widely advertised, but it’s an option — and it lets you understand the reviewer’s specific concerns before you invest 90 days in document preparation.

The Bigger Point: Import Alerts Are a Lagging Indicator

By the time your firm is on an import alert, the compliance failure that triggered it is already months old. FDA didn’t add you to the list on the day of the inspection finding or the failed analytical result — it happened after a series of escalating signals that, in retrospect, most companies can identify.

That escalation path is predictable enough to interrupt. A Form 483 observation about raw material identity testing is a precursor to a Warning Letter about the same issue. A Warning Letter about identity testing, unresolved, is a direct path to Import Alert 66-40 for a supplement manufacturer.

The firms that don’t end up on import alert lists aren’t necessarily running perfect quality systems. They’re running quality systems with enough real-time visibility into gaps — and enough organizational discipline to correct findings before they compound — that FDA rarely finds the same observation twice.

AI-augmented regulatory compliance consulting is most valuable not at the removal stage, but six months before the inspection that would have triggered the alert. That’s when gap analysis against current cGMP expectations, combined with AI-assisted review of your existing documentation, can identify the observations a district investigator would find — before they find them.

If you’re currently on an import alert, the path forward is real but it’s not short. Build the documentation package correctly the first time, use independent expertise to close the gaps your internal team can’t see clearly, and map every corrective action to the specific regulatory citation that triggered your detention. Expect 12 months of committed work. And when you get off the list, build the monitoring infrastructure that keeps you off it.

Written by Sam Sammane, Founder & CEO, Aurora TIC | Founder, Qalitex Group. Learn more about our team

Reserve early access to our AI audit tools — including decision-grade document gap analysis designed for RFRIA submissions and pre-inspection reviews. Contact us

Related from our network

• Third-Party Laboratory Testing for Supplier Qualification — Qalitex Laboratories provides ISO 17025-accredited analytical testing to support import alert removal packages, including identity and potency verification for dietary supplement ingredients.
• Canadian GMP Compliance and NHP Testing — Androxa supports manufacturers seeking dual-market compliance across Health Canada and FDA frameworks, including documentation support for regulated product submissions.