Practice·August 2, 2026 · 3 min read

Detention doesn't need a warning letter

FDA's device import alerts authorize border detention from a documented inspection finding alone, no warning letter has to exist before or after. The list that runs on is a set of static web pages with no API behind them at all.

By Connor Griggs — Regulatory & Quality Strategist

Every source this column has described so far arrives shaped like an event: a letter posted on a Tuesday, a recall classified this week, a rule with a comment deadline attached. FDA Radar’s four feeds are built around that shape — something dated, something new, worth a reviewer’s attention the week it posts. An import alert is not that shape. It is a standing list, and a firm can sit on one for years with nothing that looks like an event happening at all.

Detention without physical examination, in one sentence

The Federal Food, Drug, and Cosmetic Act gives FDA the authority, at 21 U.S.C. § 381(a), to refuse admission to any imported article that appears to violate the Act — the appearance standard, not a finding proven fresh at every border crossing. Import alerts are how FDA operationalizes that authority in public: a named list of firms and products FDA will detain without physically examining the shipment, because a documented pattern already exists. Import Alert 89-04, “Detention Without Physical Examination of Devices from Firms that Have not met Device Quality System Requirements,” is the device-specific version — appropriate, in the alert’s own language, once an FDA inspection has revealed that a firm is not operating in conformity with device quality system requirements, or once FDA receives inspection information from a foreign government under a formal agreement showing the same thing.

The list doesn’t wait for a warning letter

Placement on 89-04 is keyed to what an inspection found, not to whether that finding was ever escalated into a published warning letter. A firm can land on the list directly from an inspection’s findings, and it stays there, in the alert’s own words, “until such time as FDA is satisfied that the appearance of a violation has been removed, either by re-inspection or submission of appropriate documentation.” No warning letter has to exist at any point in that sequence, and nothing about the listing depends on one being published. A device team that reads every warning letter FDA posts and every recall FDA classifies can be current on both feeds and still miss a listing that is, right now, already deciding whether a supplier’s shipments clear a U.S. port.

A warning letter is a document FDA chose to publish. A listing on 89-04 is a condition FDA chose to impose. The second does not wait on the first, and can outlast it.

No API, because nothing here was built to be one

Every other source in this column’s corpus — Federal Register notices, warning letters, openFDA’s enforcement and 510(k) endpoints — exists as structured, queryable data. Import alerts do not. Each one, including 89-04, lives at accessdata.fda.gov as its own static page, organized into a Red List of firms and products currently subject to detention and, where FDA has granted one, a Green List of firms cleared out from under it. There is no JSON endpoint behind either list, and none of the four sources FDA Radar reads touches this one at all. The handful of tools that do track this space work by scraping the page, not by calling an API FDA publishes, because no such API exists to call.

The practice

A portfolio that depends on a manufacturing partner outside the United States has a check here that no warning-letter feed or recall feed reproduces: read the device-relevant import alerts — 89-04, and the rest of the 89-series — by firm name, directly, on a cadence of a reader’s own choosing. FDA Radar doesn’t monitor import alerts today; per what we monitor and how often, its four feeds are Federal Register, warning letters, and two openFDA device endpoints, and this sits outside all of them, same as it sits outside every other automated feed built on top of FDA’s structured data. Whether a listing changes anything for a specific supplier relationship is a judgment for whoever owns that relationship, on the facts of that relationship — this is a description of how one compliance action works, regulatory intelligence and method, never a determination about any firm named on these lists today.

Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.

Practice
Emergency use isn't defined in Part 812
Method
The two-year inspection clock is gone
Method
The PMA clock starts at the last module
Practice
The Q-Sub that doesn't buy you more time
Method
Lapsed and revoked end an EUA differently
Practice
A recall strategy has a grade. openFDA doesn't.
Method
A granted De Novo becomes a predicate.
Practice
Least burdensome changes the ask, not the bar.
Method
The lab is accredited. Not the device.
Practice
Breakthrough is law. STeP is a guidance.
Practice
MDSAP replaces routine. Not for-cause.
Method
No field on a 510(k) says what it treats
Method
Discretion is a policy. Exclusion is a statute.
Practice
Designated by one office. Approved by another.
Method
MedSun sits beside MAUDE, not inside it
Practice
The five-unit device never gets a K-number
Practice
Meeting the criteria isn't a tracking order
Method
The PMA clock doesn't stop at approval
Practice
The K-number doesn't track today's device
Method
A MAUDE report proves it was filed
Practice
Not every MDR starts with the manufacturer
Method
Completed. Not terminated.
Practice
The device-ban list has three entries
Method
The UDI exception has its own deadline
Method
MDUFA VI is being negotiated in public
Practice
The inspection manual changed, not the rule
Method
The count Congress had to legislate
Practice
The small-business rate isn't retroactive
Method
A detention order has no docket to read
Practice
PMA approvals moved off the Federal Register
Method
A citizen petition names names
Practice
A market withdrawal isn't a recall
Method
Not every device letter comes from CDRH
Practice
Closed on one device. Open on the rest.
Method
No IDE is confirmed until the PMA is
Practice
The remedial-action call sets the clock
Method
Jurisdiction is a letter, not a field
Practice
An address is not a footprint
Method
The final rule that isn't final yet
Practice
The special controls aren't in the record
Method
Exempt from GMP. Not from complaints.
Practice
The notify list isn't the shortage list
Method
A constraint can't be skipped. A script can.
Practice
No cron sends this. A person does.
Method
Corrected, not rewritten
Practice
Quiet is a finding, not a default
Method
The summary is public. The statement isn't.
Practice
A competitor's 513(g) leaves no trace
Practice
An empty response field proves nothing
Method
A petition is public. Its outcome isn't.
Practice
The panel is a category, not a meeting
Method
An accessory carries its own classification
Method
A TPLC report is a category, not a device
Practice
A 522 order is a question, not a verdict
Method
A PCCP change leaves no new record
Practice
Not every signal becomes a recall
Method
eSTAR did not remove the acceptance check
Practice
An early alert has no recall number yet
Practice
A consent decree isn't a database row
Method
The record has no cybersecurity field
Practice
Classification Change is not one event
Method
Publication date is not effective date
Method
One event. Many recall numbers.
Practice
Quantity is a sentence, not a number
Practice
How a firm told you is a field too
Method
A RIN outlives the document number
Method
The docket ID is not the comments
Practice
The 510(k) record doesn't name the predicate
Practice
The 510(k) FDA didn't review first
Method
The letter FDA doesn't have to post
Practice
Cleared doesn't say which track it took
Method
The clock stops. The calendar doesn't.
Method
Why a guessed match never reaches you
Practice
The standards list never names a device
Method
The guidance isn't in the Federal Register.
Practice
Filtered. Not discarded.
Method
There are two recall databases, not one
Practice
Breakthrough status is confidential by law
Practice
One MAUDE report is not one malfunction
Method
A supplement number is not a track
Method
Cleared is not approved
Practice
Nationwide doesn't mean your building
Practice
Not every correction reaches FDA
Method
Registered. Not reviewed.
Method
Contact ODE is not a pathway
Practice
Almost no recall is FDA-mandated
Method
FDA's device names read like a card catalog
Practice
openFDA is free. It is not unlimited.
Method
GUDID stores the model. Not the box.
Method
A Class I device, a Class I recall
Practice
21 CFR 820 didn't move. Its contents did.
Method
The product code that doesn't exist yet
Practice
The classification posts. The 483 behind it doesn't.
Method
A recall has three dates, and the pipeline had to pick one
Practice
The count is real. The rate is not.
Method
The firm on the record is not the firm on the box
Practice
Low confidence is an instruction, not a hedge
Method
The same company, spelled three ways
Practice
A device that was never a medical device
Method
FDA's warning letters, addressed by column number
Practice
Your regulation has a decimal. FDA's watch doesn't.
Method
Three letters is too short to search for
Practice
Most warning letters never close
Method
The guidance that skipped the draft
Practice
Ongoing, as of when?
Method
The least interesting fact in a 510(k)
Practice
No recall arrives with a product code attached
Practice
The deadline that doesn't email you
Method
The warning letter has two dates
Method
How to monitor FDA without drowning
Practice
Your predicate was recalled. Now what?
Method
Why no item reaches you without a human