FDA Affirmations of Compliance and Entry Data

An FDA entry is not supported by one “FDA number.” It is built from interconnected declarations identifying the product, the firms involved, the regulatory pathway, and the reason the shipment is entering the United States. Affirmations of Compliance, or AofC codes, supply qualifiers such as establishment registration, device listing, premarket authorization, or investigational exemption numbers. Some are mandatory for particular scenarios; others may help FDA verify the entry electronically.

The challenge is that every element must correspond across multiple records. The FDA product code should match the device’s classification and listing. The declared manufacturer and foreign exporter must be associated with the correct establishment identifiers. The listing must cover the product being shipped, and any clearance, approval, authorization, or exemption number must apply to that device and import scenario. A valid identifier can still fail if it is submitted under the wrong affirmation code, linked to another establishment, or inconsistent with the declared product.

Intended Use Changes the Requirements

The intended-use code adds another decision layer. It tells FDA why the article is entering—for example, commercial distribution, clinical investigation, component processing, repair, evaluation, or import for export—and influences which supporting data FDA expects. A marketed device, an investigational device, and a device imported solely for processing may be physically identical yet require materially different entry structures. Using a commercial intended-use code for a pre-authorization clinical investigation can cause FDA to evaluate the shipment against commercial requirements it was never intended to satisfy.

FDA’s screening systems compare entry declarations with registration, listing, authorization, and compliance records. Inconsistencies can trigger lookup failures, document requests, manual review, detention, or questions that a carrier or customs broker cannot resolve without regulatory input. The broker transmits the data, but the importer and manufacturer must first provide a coherent regulatory position.

MDD Options coordinates the manufacturer, product, authorization, intended-use, and entry data for medical-device imports and converts that regulatory structure into broker-ready instructions. Through its hybrid distribution model and clinical-investigation support capabilities, MDD Options can also align the declared import scenario with the activities occurring after release, reducing the risk that a lawful shipment is presented to FDA under the wrong regulatory framework.