U.S. FDA Food Facility Registration and Compliance

Registration is the starting point, not the entire compliance program

Access to the United States food market can create major opportunities for companies in North America, Europe, Asia, Latin America and Africa. Cocoa processors in Ghana and Côte d’Ivoire, coffee exporters in Brazil, Colombia, Ethiopia and Vietnam, tea manufacturers in India, China, Sri Lanka and Kenya, wine and champagne producers in France, Italy, Spain, South Africa and Latin America, cheese producers in the European Union, olive oil suppliers in the Mediterranean region, palm oil refiners in Southeast Asia and West Africa, rice mills in Asia and the Americas, tropical fruit packers, and spice processors all face a common regulatory question: does the facility that manufactures, processes, packs or holds the food need to be registered with the U.S. Food and Drug Administration?

For many facilities, the answer is yes. The food facility registration requirement helps FDA identify facilities involved in the U.S. food supply and respond more rapidly to foodborne illness outbreaks, adulteration events, bioterrorism threats and other public health concerns. Registration, however, is not a product approval, import license, marketing authorization or evidence that FDA has reviewed a company’s labels, sanitation controls, preventive controls, hazard analysis, traceability system or foreign supplier verification program.

A compliant market-entry strategy therefore requires more than obtaining a registration number. Companies must accurately determine which locations need registration, obtain and maintain an acceptable Unique Facility Identifier, appoint a reliable U.S. Agent when the facility is foreign, renew during the biennial renewal period, protect confidential registration credentials, update material changes, comply with applicable food safety and labeling rules, and coordinate import documentation with the U.S. importer, FSVP importer, customs broker and logistics providers.

Biennial renewal and the 2026 renewal cycle

Food facility registration is not permanent. Facilities that are required to register must renew during the period beginning October 1 and ending December 31 of each even-numbered year. The next regular renewal cycle is therefore October 1 through December 31, 2026. A company should not wait until the final days of December to review its information, because unresolved UFI discrepancies, U.S. Agent confirmation issues, account access problems or outdated ownership information can delay completion.

Renewal should be treated as a compliance verification exercise rather than a simple administrative click. The facility should confirm its legal name, physical address, mailing address, parent company information, trade names, food product categories, emergency contact, owner or operator data, U.S. Agent information for a foreign facility, and the accuracy of the DUNS number used as the UFI. The company should also identify facilities that have closed, changed ownership, relocated or stopped making food for the U.S. market.

If a required registration is not renewed by the deadline, FDA may consider it expired. Food from a foreign facility without a valid registration can face import problems, including detention at the port of entry. Commercial consequences may also follow when importers, distributors, retailers, marketplaces or logistics providers cannot verify that required registration information is current.

Unique Facility Identifier and DUNS number accuracy

FDA requires each food facility registration submission to include a Unique Facility Identifier that FDA recognizes as acceptable. FDA currently recognizes the Data Universal Numbering System number, commonly called the DUNS or D-U-N-S number, for this purpose. The DUNS number is assigned and managed by Dun & Bradstreet.

The UFI is not merely an extra reference number. FDA uses it to verify that the facility-specific address associated with the identifier matches the address in the food facility registration. This address matching function is one reason companies should obtain the DUNS number for the actual physical facility, not for a different corporate headquarters, accountant’s office, mail-forwarding location or unrelated warehouse.

Common problems include abbreviations that do not match, translated street names, inconsistent postal codes, use of a parent-company DUNS number, old addresses remaining in D&B records, duplicate business records and confusion between a mailing address and the physical location where food is manufactured, processed, packed or held. Foreign facilities should review local address formatting carefully and allow sufficient time to correct D&B information before the renewal deadline.

• 01→ Verify that the legal business name in the DUNS record matches the registrant or facility information.
• 02→ Confirm that the physical address, city, region, postal code and country are consistent across FDA and D&B records.
• 03→ Do not substitute a mailing-only location when FDA is asking for the location of the food facility.
• 04→ Resolve duplicate or inactive DUNS records before submitting a time-sensitive renewal.

Risk of virtual offices, mailboxes and non-operational addresses

Virtual addresses are often marketed as convenient solutions for forming companies, receiving mail or establishing a commercial presence. They may be legitimate for some corporate or correspondence purposes, but they create significant risk when used as the address of a food facility that is supposed to manufacture, process, pack or hold food.

A food facility registration is location-specific. If the listed address is only a mailbox, coworking suite, registered agent office or mail-forwarding service where no regulated food activity occurs, the registration may misidentify the facility. The UFI validation process may expose inconsistencies between the claimed facility address and the DUNS record. During an inspection, import review, outbreak investigation or enforcement inquiry, FDA may be unable to locate the actual operation. This can undermine confidence in the registration and complicate communications with the facility.

Domestic companies are not immune from this risk. A U.S. seller may form an LLC using a virtual address while the food is actually repacked in another state, stored in a third-party warehouse or made by a contract manufacturer. The company must evaluate which physical establishments perform regulated activities and which party is responsible for each registration. A corporate office that performs no food manufacturing, processing, packing or holding is not automatically the facility that should be registered.

Foreign companies face similar issues when attempting to use a U.S. Agent’s address as the foreign facility address. The U.S. Agent is a contact for FDA and is not a substitute for the actual foreign manufacturing, processing, packing or holding location. The facility address, U.S. Agent address and U.S. importer address may all be different, and each serves a different regulatory purpose.

FDA warnings about scams, credential theft and unnecessary registrations

Food businesses should be cautious when receiving urgent emails, invoices, renewal notices or requests for confidential FDA credentials. FDA has warned industry about phishing attempts and about private businesses that may imply an affiliation with FDA. FDA has also advised facilities to protect their food facility registration information after observing businesses registering when they were not required to do so, third-party registrars requesting registration numbers, PINs and FIS-FURLS credentials, and online marketplaces asking sellers for copies of registrations or private certificates.

The food facility registration number is confidential and is not part of a public FDA database. The PIN, account username and password are even more sensitive. A third party that obtains enough information may be able to link a registration to another FDA Industry Systems account, view data, change information or potentially cancel the registration. Businesses should never share their FIS-FURLS username or password. When additional personnel need access, the account holder should use authorized account-management features rather than sending login credentials by email.

Companies should also recognize the difference between an official FDA communication and a private service offer. A consultant may legitimately provide registration, renewal and U.S. Agent services for a fee, but must not represent that the private firm is FDA, acts on FDA’s behalf or can sell an FDA-issued certificate that does not exist. Urgent threats, payment demands to personal accounts, unofficial email domains, requests for passwords and claims that a certificate is legally mandatory should be independently verified.

Certificate of registration: what it means and what it does not mean

FDA issues a food facility registration number after a registration is completed, but FDA does not issue a certificate of food facility registration and does not recognize private certificates as proof of FDA approval, product status or regulatory endorsement. A private consultant may create a client-facing confirmation document summarizing registration information, but it must be clearly identified as a private document and should not use the FDA logo or imply that FDA issued, certified, approved or endorsed it.

This distinction is important because commercial partners sometimes ask for a “certificate” as part of vendor onboarding. The correct response may be to provide a carefully redacted private confirmation, a consultant letter or other commercial evidence, while protecting confidential information. Companies should not publish the registration number on websites, product labels or social media simply to satisfy a marketing request. Registration does not establish that a food is safe, that its label is compliant or that its claims are authorized.

A legitimate private confirmation should therefore use restrained language such as “registration submission confirmation” or “private registration status confirmation.” It should explain that FDA does not issue or recognize certificates of food facility registration and that the document is not evidence of product approval. Any customer or marketplace requesting a certificate should be educated about this regulatory limitation.

Food traceability rule and supply-chain records

Food facility registration and traceability are separate but connected compliance topics. FDA’s Food Traceability Rule establishes additional recordkeeping requirements for persons that manufacture, process, pack or hold foods on the Food Traceability List. The rule is built around Critical Tracking Events and Key Data Elements, including information connected to harvesting, cooling, initial packing, shipping, receiving and transformation. Covered firms may also need a written traceability plan and systems for linking records to a traceability lot code.

The original compliance date was January 20, 2026. FDA proposed extending the date by 30 months to July 20, 2028, and Congress subsequently directed FDA not to enforce the rule before July 20, 2028. Companies should not interpret the enforcement delay as a reason to stop preparing. Traceability systems often require supplier agreements, lot-code design, enterprise software changes, warehouse procedures, record-mapping, staff training and coordination with importers and customers.

Not every cocoa, coffee, tea, oil, rice, fruit, cheese, wine or spice product is automatically on the Food Traceability List. Applicability depends on the food, its form, its ingredients, activities performed and available exemptions. Fresh tropical fruits, certain cheeses and foods containing listed ingredients may require closer analysis. Even where the additional traceability rule does not apply, other FDA recordkeeping, preventive controls, recall, sanitation, import and commercial traceability expectations may remain relevant.

• 01→ Determine whether any food or ingredient is included on the Food Traceability List in the form in which it is handled.
• 02→ Map each Critical Tracking Event performed by the facility and identify the required Key Data Elements.
• 03→ Develop a traceability plan, lot-code governance process and record-retrieval procedure.
• 04→ Coordinate data exchange with farms, suppliers, processors, packers, warehouses, importers and customers.

Foreign facilities, U.S. Agents, importers and FSVP responsibilities

A foreign food facility must designate a U.S. Agent for FDA communications. The U.S. Agent must reside or maintain a place of business in the United States and be physically present in the United States. The agent serves as a communications link between FDA and the foreign facility, assists FDA in communications, responds to questions concerning imported foods and may be contacted in emergencies.

The U.S. Agent is not automatically the importer of record, owner, distributor or Foreign Supplier Verification Program importer. These roles may be performed by different parties. A European cheese producer may appoint a U.S. regulatory consultant as U.S. Agent, sell to a U.S. distributor that acts as importer of record, and rely on another qualifying U.S. entity as the FSVP importer. An Asian rice exporter, African cocoa processor or Latin American fruit packer may have similarly divided roles.

Clear written agreements are essential. The foreign facility should know who controls the FDA account, who receives official communications, who maintains the registration PIN, who submits prior notice, who conducts FSVP activities, who holds customs records and who responds if FDA detains a shipment or requests documents. Misalignment among these roles can result in delayed entries, duplicate registrations, missed notices and regulatory disputes.

Build a registration record that reflects the real supply chain

U.S. FDA food facility registration is a foundational requirement for many domestic and foreign food operations, but its value depends on accuracy. A registration should identify the real facility, use a verifiable UFI, designate a legitimate U.S. Agent when required, remain current through biennial renewal and be protected from unauthorized access. It should not be treated as a certificate of approval or used as a substitute for food safety, labeling, FSVP, prior notice, traceability or import compliance.

Companies dealing in cocoa, coffee, tea, wine, champagne, cheese, olive oil, palm oil, rice, tropical fruits, spices and other foods should map every manufacturing, processing, packing and holding location before deciding which facilities must register. They should also examine contract manufacturers, co-packers, bottlers, warehouses and consolidation sites. A carefully structured registration program helps reduce avoidable import delays, data conflicts, credential misuse and last-minute renewal problems.

The 2026 renewal cycle creates an opportunity to clean up old records and strengthen controls. Businesses should start early, confirm their DUNS information, review their physical addresses, verify U.S. Agent arrangements, protect account credentials and assess whether traceability preparations are on schedule. Regulatory compliance is most effective when registration data, supply-chain reality and written procedures all tell the same story.