A detention order has no docket to read

FDA Radar reads four sources every day: Federal Register notices, warning letters, device recalls, 510(k) clearances. A fifth enforcement action exists that touches none of them — older than all four, and never announced anywhere a reader could find in advance. An FDA investigator can walk out of an inspection and order a device held in place, the same day, under an authority that has nothing to do with a warning letter.

The trigger is an inspection, not a paper trail

21 CFR 800.55, adopted in 1979 and still current, lets an authorized FDA representative issue a detention order the moment an inspection gives them reason to believe a device is adulterated or misbranded. The statute behind it — 21 U.S.C. § 334(g), Section 304(g) of the FD&C Act — requires no finding beyond that belief, no warning letter issued first, and no sign-off from anyone outside the inspecting district. A warning letter is drafted, routed through review, and dated weeks after an inspection closes. A detention order can be handed to a firm before the inspector leaves the building.

What the order actually does

Once issued, the regulation is specific about what happens to the device: it may not be used, moved, altered, or tampered with by any person for the length of the detention, full stop. The period is capped at 20 calendar days from the order, extendable once by an FDA Division Director for 10 more if the agency needs the time to seize the device, open an injunction action, or decide whether to. Thirty days, at the outside, to go from “reason to believe” to a real legal action — and the firm holding the detained device has to hand over its own distribution records during that window, so FDA can trace where the product went if the clock runs out before a seizure does.

A warning letter is a claim FDA is prepared to publish. A detention order is a claim FDA is prepared to act on immediately, and publish nowhere.

Why none of the four sources ever carry it

A detention order isn’t a warning letter, so it never reaches CDRH’s warning-letter database. It isn’t a recall — nothing has been distributed to correct or remove — so it never reaches openFDA’s enforcement endpoint. It doesn’t touch a 510(k) number, and it is never itself a Federal Register document: individual detention orders are delivered directly to the firm, not printed for the public. FDA maintains no structured public database of administrative detention orders at all — nothing comparable to the warning-letter search page or the enforcement-report feed. A detention that never escalates into a seizure or an injunction — the far more common outcome, since the whole point of the 30-day cap is to force a faster decision — can close without ever generating a document any monitoring tool, including this one, would see.

The practice

This isn’t a gap a better feed closes, because the record it would read from does not exist in public form. The only reliable way to know whether a supplier, contract manufacturer, or co-packer has ever had product administratively detained is to ask them directly, as part of the same supplier-qualification conversation that already covers 483s and warning letters — because unlike those two, this one will never turn up in a search. Whether a specific detention, yours or a partner’s, warrants an injunction defense or a recall of your own is a determination for a regulatory or legal professional working the facts of that inspection, not a field any monitoring tool can fill in. This is regulatory intelligence about where the mechanism lives, never regulatory advice about what to do inside it.