An import alert flips the burden of proof

This blog has already covered how an Official Action Indicated inspection classification can lead to an import alert as one of FDA's follow-on actions, without covering what that alert actually does to a shipment once one is in place. An import alert doesn't inspect the next container that arrives. It tells the port not to bother inspecting it at all — because FDA has already decided, based on the pattern behind the alert, that the shipment is presumed to violate the FD&C Act until the importer proves otherwise. That's a different posture from an ordinary import exam, and a firm that treats an alert like a stricter inspection rather than a reversed presumption is answering the wrong question.

An ordinary import exam and a presumptive one run on opposite defaults

Section 801(a) of the FD&C Act lets FDA refuse admission to a device that appears to be adulterated, misbranded, or otherwise offered in violation of the Act — and ordinarily, reaching that appearance takes an actual look at the shipment, a sample, an examination, something specific to the goods in front of the inspector. Detention Without Physical Examination (DWPE) is a different mechanism entirely: a policy tool FDA's Regulatory Procedures Manual describes, not a separate statutory provision, that lets the agency detain a shipment without examining it at all, because the firm, facility, or product category behind it already carries a documented pattern of violation. The prior pattern does the work an individual exam would otherwise have to do.

An import alert is where that pattern becomes a standing instruction

When FDA identifies violations frequent or serious enough to justify that shortcut, it publishes an import alert naming the firm, product, or category the presumption attaches to. From that point forward, a shipment matching the alert's criteria is detained at the border on sight — not because that specific shipment was examined and found wanting, but because it matches a listing FDA has already decided warrants the presumption. Import alerts covering device firms exist for reasons ranging from refusing a foreign establishment inspection to shipping devices without a matching UDI and GUDID record, and each one names its own specific triggering condition rather than a generic “quality concern.”

21 CFR 1.94 sets the window to rebut it

A detained shipment doesn't sit in limbo indefinitely. FDA issues a Notice of Detention and Hearing naming the alleged violation and a respond-by date — ordinarily ten business days, extended in practice to around twenty calendar days to absorb weekends, holidays, and mail transit — during which 21 CFR 1.94 gives the importer the right to an informal hearing and the opportunity to introduce testimony contesting the appearance of violation. That testimony is commonly a private laboratory's analysis of the specific shipment, submitted as evidence that this particular entry doesn't carry the defect the alert presumes. Missing the respond-by date converts the detention into a formal refusal of admission, which is a considerably harder outcome to reverse than a timely response would have been.

The rebuttal has to answer the shipment, not the firm

The evidence that actually moves a detained shipment through 1.94's hearing is narrower than it sounds: it has to speak to the specific entry in front of the port, not to the firm's overall corrective action plan or its intentions going forward. A private lab report showing this lot meets spec can release this shipment even while the underlying import alert, and the presumption it carries for the next one, stays fully in force. Getting off the alert itself — so that future shipments stop needing this same rebuttal one entry at a time — is a separate, slower process aimed at the condition that triggered the alert in the first place, not a byproduct of winning any single hearing.

Where this meets the file

An import-compliance file needs to track an import alert as its own standing record — the specific triggering condition named in the alert, distinct from any individual detention it produces — alongside a per-shipment log of Notice of Detention respond-by dates and the evidence submitted against each one. Collapsing an alert and its detentions into a single “import issue” entry loses the distinction between the standing presumption and the one-shipment rebuttal that 1.94 actually decides. An import-readiness worksheet built around that split is previewed in the launch catalog. If your program has worked through a DWPE listing and tracks it differently, the shelf takes that correction directly.