Food Facility Registration: FDA Requirements Under 21 CFR Part 1 Subpart H
Understand FDA food-facility registration through its applicability rules, information requirements, renewal provisions, and practical controls for maintaining reliable facility records.

On this page · 11 sections
- 1What Food Facility Registration means—and what record it describes
- 2Who must register: facility activity, responsible role, and US market
- 3What information must be registered: a field-by-field map
- 4Foreign facilities: U.S. agent and emergency-contact information
- 5From initial registration to controlled change review
- 6The biennial renewal and the unchanged-information route
- 7A usable data model for facility identity, submissions, and reviews
- 8Worked cases: local processing, foreign holding, and changed records
- 9Integrations and exception recovery without blind data synchronization
- 10Common failure modes and the controls that expose them
- 11Implementation and review checklist: questions before authorization
How does Food Facility Registration apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What Food Facility Registration means—and what record it describes
Food Facility Registration is the FDA registration framework for facilities engaged in manufacturing/processing, packing, or holding food for consumption in the United States. Its activity-and-market scope is set out in 21 CFR 1.225(a).
This article addresses US food-facility registration, not registration generally for pharmaceuticals, medical devices, chemicals, or facilities serving other markets. Start product-classification questions with the applicable product and jurisdiction framework rather than assuming that every regulated manufacturer belongs here. For classification context, see medical food and FSMP terminology; for a separate market-specific topic, see GCC supplement registration. Neither is a substitute for assessing the facility's activities and intended market.
Separate the records by the question they answer
The following comparison is a proposed operational taxonomy, not an additional set of FDA requirements. It separates administrative registration information from site-management records, food-safety planning, and decisions about particular batches.
| Term | Record object | Operational question | Boundary |
|---|---|---|---|
| Food Facility Registration | Facility information submitted for FDA registration | What facility information does the registration represent? | Administrative record; keep separate from product-quality decisions. |
| Internal facility master record | Organization's maintained site profile | Which site identity and attributes should internal teams use? | Internal reference data, not the registration submission itself. |
| Food safety plan | Site-specific hazard analysis and control documentation | How are food-safety hazards addressed in the operation? | Safety-planning record, not a facility identity record. |
| Batch-disposition record | Evidence and documented decision for a particular batch | What disposition did the responsible reviewer authorize? | Batch-specific quality decision, not registration information. |
In this model, related records can share a site identifier without becoming interchangeable. A registration entry belongs with its submission history; a disposition decision belongs with the batch evidence and reviewer authorization. Keeping those relationships explicit helps staff retrieve the record that actually answers their question.
How to read the article's recommendations
The cited CFR provisions are binding US regulations concerning food-facility registration. Official guidance is a separate category and is not presented as law. The proposed workflows, controls, record structures, and software-support patterns in this article are nonbinding operational practice. Software support is an administrative aid in that model: human review and approval remain human responsibilities, and using a system is not a compliance determination.
02Who must register: facility activity, responsible role, and US market
For food intended for US consumption, 21 CFR 1.225(a) requires the owner, operator, or agent in charge of a domestic or foreign facility engaged in manufacturing/processing, packing, or holding that food to register the facility, unless it qualifies for an exemption under § 1.226.
Using the definition above, assess what happens at the site rather than relying on the company's commercial description. As a practical assessment method, describe the food handled, the activities performed, and the intended market. For a food-grade warehouse, start with its actual holding activities—not simply its description as a logistics business.
For domestic facilities handling food for US consumption, 21 CFR 1.225(b) requires registration whether or not the food enters interstate commerce, subject to the applicability and exemption assessment above. Local-only distribution is therefore not, by itself, a basis for concluding that registration is unnecessary.
| Facility context | Applicable question | Provision | Scope boundary |
|---|---|---|---|
| Domestic US-food operations | What manufacturing/processing, packing, or holding occurs? | 1.225(a), (b) | Interstate movement is not the deciding factor. |
| Foreign US-food operations | Does the facility perform these activities for food consumed in the US? | 1.225(a) | Assess US-food activities and exemption eligibility. |
| Claimed exemptions for US-food facilities | Does the facility qualify under the current exemption text? | 21 CFR 1.226 | Check current scope; do not infer eligibility from a business label. |
| Other products or markets | Which separate applicability assessment is needed? | Assess separately | Use the relevant reference, such as MoCRA facility registration, rather than extending this food-registration test. |
As an internal documentation practice, retain the applicability decision, its responsible reviewer, the activity description, and the reason for reopening the assessment after a business change. Suggested review triggers include changes in site activities, products, or intended markets. This decision record is a recommended control, not a prescribed FDA record format.
03What information must be registered: a field-by-field map
For domestic and foreign facilities subject to registration that handle food for US consumption, distinguish the facility’s identity from its mailing address, parent company and responsible-person contacts. The dictionary below maps these registration fields. Internal owner and Review source are suggested operating controls—not additional FDA registration fields or prescribed organizational roles.
| Field group | Applicable facility | Conditionality | Internal owner | Review source |
|---|---|---|---|---|
| Facility identity: name, full address and phone number | Domestic and foreign; food for US consumption | Required by 21 CFR 1.232(a)(1). | Site administration | Site identity record |
| Facility UFI | Domestic and foreign; food for US consumption | 21 CFR 1.232(a)(2) requires a UFI recognized as acceptable by FDA. | Registration coordinator | Facility identifier record |
| Preferred mailing address | Domestic and foreign; food for US consumption | Required if different from the facility address under 21 CFR 1.232(a)(3). | Site administration | Correspondence instructions |
| Parent company: name, full address and phone number | Domestic and foreign; food for US consumption | Required if the facility is a subsidiary under 21 CFR 1.232(a)(4). | Corporate administration | Corporate ownership record |
| Trade names | Domestic and foreign; food for US consumption | All trade names the facility uses under 21 CFR 1.232(a)(5). | Site administration | Trading-name register |
| Owner, operator or agent in charge: name, full address, phone number and email | Domestic and foreign; food for US consumption | 21 CFR 1.232(a)(6) requires these details; the email requirement has an exception where FDA has granted a waiver under § 1.245. | Registration coordinator | Responsible-person confirmation |
| Food product categories | Domestic and foreign; food for US consumption | 21 CFR 1.232(a)(7) requires applicable categories identified on Form FDA 3537 for food manufactured/processed, packed or held. | Operations | Site product scope |
| Activities by food product category | Domestic and foreign; food for US consumption | 21 CFR 1.232(a)(8) requires activity type for each category and permits multiple activity types per category. | Operations | Site activity map |
| Facility contact and emergency contact | Domestic; food for US consumption | 21 CFR 1.232(b) requires the facility contact person’s email, plus an emergency contact phone number and email address if different from that contact person’s email address. | Site administration | Contact directory |
As an operating control, keep category-to-activity assignments repeatable rather than forcing one activity into each category record. For a food-grade warehouse, review the site’s actual handling activities alongside its product scope instead of relying on the business label alone. Keep facility, corporate and personal contact records separately identifiable so a reviewer can reconcile each field with its appropriate source.
04Foreign facilities: U.S. agent and emergency-contact information
For foreign facilities handling food for US consumption, 21 CFR 1.232(c)(1) requires the U.S. agent’s name, full address, phone number, and email address. For these foreign food facilities, 21 CFR 1.232(c)(2) also requires an emergency contact phone number and email address.
As a contact-governance practice, use a role map rather than one undifferentiated contact field. These are separate data roles, not necessarily different people; the map does not establish additional legal qualifications or duties.
| Data role | Suggested record distinction |
|---|---|
| U.S. agent | Label the agent’s identity and contact details explicitly. |
| Emergency contact | Keep emergency phone and email fields identifiable. |
| Owner/operator/agent in charge | Identify this role separately from the U.S. agent role. |
| Authorized submitter | Distinguish the person submitting from the contact roles. |
When personnel or service-provider arrangements change, review contact reachability and role assignments. Confirm that phone numbers and email addresses still reach the intended contacts, and record who reviewed the mapping. Where one person fills multiple roles, preserve each assignment explicitly rather than assuming that changing one contact updates every role. This supports data integrity while keeping contact maintenance subject to human review.
05From initial registration to controlled change review
For facilities subject to registration that handle food for US consumption, 21 CFR 1.230(a) requires registration before manufacturing, processing, packing, or holding that food begins. For those US-market food facilities, 21 CFR 1.225(c) permits the owner, operator, or agent in charge to authorize an individual to register on their behalf.
For US-market food facilities, 21 CFR 1.232(a)(9) requires an owner/operator/agent-in-charge statement assuring that FDA will be permitted to inspect at the times and in the manner permitted by the Federal Food, Drug, and Cosmetic Act.
For US-market food facilities, 21 CFR 1.232(a)(10) requires the owner/operator/agent-in-charge certification that submitted information is true and accurate. For these facilities, that provision also requires another individual submitting the registration to certify accuracy and authorization, and identify the authorizer by name, address, and telephone number. For these US-market food registrations, it also requires the authorizer’s email unless FDA has granted a waiver, plus the submitter’s name and, for paper submissions, signature. Renewal-specific questions are addressed next.
Check the current text of 21 CFR Part 1 Subpart H for update obligations and timing. Change detection, assignment, human review, and reconciliation are proposed internal controls—not a substitute update rule or a renewal process.
Proposed coordination sequence: detect a change → assign a responsible person → prepare the record → designated people review and authorize → submit → record the response → reconcile discrepancies.
Keep this facility-level history separate from batch records, with designated people responsible for resolving discrepancies; see the data-and-evidence-model section below for the prepared/submitted/response-recorded state distinction.
- Assess scopeRecord facility activities, US market context, and exemption questions.
- Reconcile identityCompare facility information with responsible internal source records.
- Review rolesCheck contacts, assigned responsibilities, and submission authorization.
- Prepare snapshotAssemble reviewed fields and resolve outstanding discrepancies.
- Authorize ActionHave the designated person review the proposed submission.
- Reconcile responseAssociate submission and response references with the snapshot.
- Review changesRoute changes and renewal preparation to responsible reviewers.
06The biennial renewal and the unchanged-information route
For facilities handling food for US consumption and subject to registration, 21 CFR 1.230(b) requires renewal every other year, during the period beginning on October 1 and ending on December 31 of each even-numbered year. The renewal must contain the information required under § 1.232; use the field dictionary above rather than treating renewal as a calendar acknowledgment.
Renewal submission checklist
For these US-food registrations, § 1.230(b) permits authorizing an individual to renew on the responsible person's behalf. Its submission requirements are:
- Include the submitter's name; the paper option also requires the submitter's signature.
- If the individual submitting the registration renewal is not the owner, operator, or agent in charge of the facility, the registration renewal must also include a statement certifying that the information submitted is true and accurate, certifying that the submitter is authorized to submit the registration renewal, and identifying the authorizing individual.
- For that delegated submission, identify the authorizing individual by name, address, and telephone number; include their email address unless FDA has granted a waiver under § 1.245.
When abbreviated renewal fits
For facilities handling food for US consumption, 21 CFR 1.230(c) permits abbreviated renewal only when no information required under § 1.232 has changed since the preceding registration, registration renewal, or update. For those US-food facilities, abbreviated renewal requires confirmation of no changes and certification that the submitted information is truthful and accurate.
For these US-food abbreviated renewals, § 1.230(c) requires Form FDA 3537 and the submitter's name, with the submitter's signature for the paper option. For abbreviated registration renewals not submitted by the owner, operator, or agent in charge of the facility, the abbreviated renewal must provide the email address of the individual who authorized submission of the abbreviated renewal, unless FDA has granted a waiver under § 1.245.
Recommended internal practice: document a field-by-field comparison of current registration information against the relevant submitted baseline before choosing the route. An untouched internal record does not establish that facility information remains unchanged. Record the baseline, differences, reviewer, and route decision. Keep this registration review distinct from operational reviews associated with food preventive controls; the comparison supports the submission decision but is not itself a renewal.
07A usable data model for facility identity, submissions, and reviews
The following relationship map is a proposed internal model for food-facility registration administration, not an FDA form specification. Its purpose is to keep facility information, submission history, and review decisions distinguishable.
| Record | Suggested relationship |
|---|---|
| Facility | Stable internal identifier links identity records and information versions. |
| Role-based contact | Refers to the facility; records the person's role and contact-review record. |
| Product-category/activity association | Refers to the facility and links each category to its applicable activities. |
| Submission event | Refers to the exact information version submitted, with authorization and external references. |
| Review exception | Refers to the affected field and version, with a linked resolution record. |
Keep current operational data, the last submitted snapshot, and a proposed revision separate. Link the proposal to its baseline snapshot and record field-level differences. A reviewer can then identify what changed without overwriting the historical submission. This is a practical application of data integrity by design, rather than a prescribed database structure.
Separate internal record identifiers from external submission or response references. Use descriptive states such as awaiting response or response recorded, rather than an invented FDA approval status. Store the response reference and original message separately from the reviewer's interpretation and follow-up decision.
Suggested supporting records include submission authorization, contact review, field comparison, the submitted snapshot, response reference, and exception disposition. Link each to the relevant version or event so an audit trail review workflow can follow the decision sequence. These are administrative recordkeeping choices; this model assigns neither retention periods nor special legal evidentiary status.
Facility
Stores site identity separately from submission history.
- facility_id
- facility_name
- facility_address
- facility_phone
- fda_accepted_ufi
- preferred_mailing_address
Contact role
Associates people and contact details with responsibilities.
- contact_id
- facility_id
- role
- full_name
- postal_address
- phone
Activity Profile
Links product categories, activities, and trade names.
- activity_profile_id
- facility_id
- food_product_category
- activity_type
- trade_name
- reviewed_at
Submission Event
Links submitted information with authorization and response references.
- submission_event_id
- facility_id
- event_type
- submitted_snapshot_id
- submitted_by
- authorization_ref
- response_ref
Review exception
Tracks discrepancies through ownership and documented resolution.
- exception_id
- facility_id
- affected_field
- source_record_ref
- assigned_owner
- disposition_ref
08Worked cases: local processing, foreign holding, and changed records
These hypothetical food-facility scenarios serve the US market. Exemption eligibility is assessed separately. The unit of analysis is the facility record, not a product batch record. Decisions are qualitative; no dates, quantities, or fees are assumed.
Local processor: distribution is not the deciding factor
- Assumptions: A domestic processor distributes food only locally.
- Relevant record: The facility applicability assessment; the operator is its designated internal owner.
- Decision question: Does local distribution end the registration inquiry? No.
- Governing section: For US domestic food facilities, 21 CFR 1.225(b) requires registration whether or not food enters interstate commerce, subject to the exemption assessment covered above.
- Recommended internal action: Record a provisional registration-applicable decision rather than treating local distribution as an exemption.
- Unresolved issue: Does the facility qualify for an exemption?
Foreign holding: distinguish fields from people
- Assumptions: A foreign food-holding facility uses a third-party submitter.
- Relevant record: Facility identity, U.S. agent details, emergency contacts, and submission authorization.
- Decision question: Has the reviewer distinguished these roles without assuming each belongs to a different person?
- Governing sections: Apply the US food-registration role map above, including 21 CFR 1.232(c) for foreign-facility contacts and paragraph (a)(10) for submission certification.
- Recommended internal action: Map each field to its purpose and confirm authorization with the responsible facility representative.
- Unresolved issue: Are the contact details current and the submitter's authorization documented?
Changed records: address stability is insufficient
- Assumptions: The operating address is unchanged, but a required contact field has changed.
- Relevant record: Current information compared with the preceding submitted registration, renewal, or update.
- Decision question: Is the abbreviated renewal route still appropriate?
- Governing section: For US food registration, 21 CFR 1.230(c) conditions that route on unchanged required information.
- Recommended internal action: Flag the difference through an audit trail review workflow and prepare renewal information reflecting the change.
- Unresolved issue: Review the separate update question against the current applicable rule.
09Integrations and exception recovery without blind data synchronization
For internal registration administration, consider a field-level integration map rather than treating one system as authoritative for everything. This is a design recommendation, not an FDA-prescribed architecture:
- Facility master: proposed source for facility identity, site address and identifiers, with a named site-data owner.
- Contact directory: proposed source for contact details, with a responsible contact owner confirming role assignments.
- Product/activity records: proposed source for category and activity mappings, reviewed by the operations owner.
- Document repository: proposed source for authorized submission versions, correspondence and response references, maintained by the registration coordinator.
Map each field’s source, transformation and reviewer. Route source-system changes into a reviewed change queue; an operational edit is not an authorized change to the registration submission record. An implementation-dependent workflow could retain the comparison and decision in an audit trail.
For conflicting addresses, preserve both versions and the existing submission record, investigate whether they describe the site or a mailing destination, and assign a reviewer. Apply the submission-state and response-reference distinctions from the data-and-evidence-model section above before retrying or reconciling.
These exception-review controls imply no FDA API connection, direct submission integration, automatic registration validation or automatic exception resolution. People review disputed information and authorize subsequent actions; registration-data automation does not decide product release.
10Common failure modes and the controls that expose them
This qualitative risk analysis proposes administrative controls for food-facility registration records—not measured prevalence or FDA requirements. Use it alongside an internal failure-mode review to assign ownership.
| Failure mode | Observable signal | Suggested control | Responsible role |
|---|---|---|---|
| Facility-versus-parent address confusion | Unresolved discrepancy between site and corporate addresses. | Compare separately labelled address fields with site identity records. | Site registration coordinator |
| Incomplete trade-name coverage | An actively used name is absent from the registration working record. | Reconcile the trade-name inventory with commercial records; review differences. | Commercial data owner |
| Flattened product/activity associations | Categories and activities appear as unrelated lists. | Review category-by-activity pairs against actual site operations. | Operations reviewer |
| Stale contact roles | A departure or reassignment has no recorded review. | Route role changes to the coordinator; confirm replacement contact details. | Contact-role owner |
| Internal record differs from submitted snapshot | Baseline comparison shows differences but identifies no reviewer (see the snapshot/baseline model above). | Retain the submitted snapshot; assign and document discrepancy review. | Registration reviewer |
| Unclear submission state | See the data-and-evidence-model section's submission-state distinctions (prepared/submitted/response-recorded) for what evidence should exist. | Separate prepared, internally approved, submitted, and response-recorded states; retain supporting evidence. | Authorized submitter |
These are proposed internal record states, not agency-status definitions. Support traceability through contemporaneous recording. If a missed obligation is suspected, escalate to the responsible person for review of the current applicable rules and a documented decision on next steps.
11Implementation and review checklist: questions before authorization
Use these questions as a proposed internal readiness check for food-facility registration administration. Record the reviewer, decision and unresolved actions; checklist completion does not establish legal compliance.
- Is the applicability decision owned, with its assumptions and rationale recorded?
- Are facility identity and contact roles reconciled, with conflicting records resolved?
- Is the submitted baseline identifiable and distinguishable from working drafts?
- Are category/activity associations reviewed against the facility’s current operations?
- Is the renewal route justified by comparison with the baseline? Refer to the renewal section for conditions and timing.
- Are exceptions assigned to named owners, with unresolved items visible through exception-based review?
- Who authorizes the action, and where is that decision recorded?
- Has the submission-state and response-reference recordkeeping from the data-and-evidence-model section been followed for this submission?
- Who reviews discrepancies afterward, using an audit trail review workflow where appropriate? Refer to the lifecycle section for update scope.
Use the FAQs that follow for practical edge questions and decision reasoning, referring back to the relevant sections rather than repeating definitions or field lists.
Frequently asked questions
Q.How should a business document its reasoning when it believes a facility qualifies for an exemption?+
For US FDA food facility registration, 21 CFR 1.225(a) makes the registration obligation subject to qualifying exemptions. As an internal practice, prepare a decision memo identifying the exemption being assessed, actual site activities, supporting records, reviewer, and reasons for the conclusion. Describe operations specifically: a food-grade warehouse and a contract manufacturer need fact-specific assessments. Check the current exemption text before deciding, and identify operational changes that would trigger reassessment.
Q.Can a head-office mailing address replace the physical facility address in the registration record?+
No. For US FDA food facility registration, 21 CFR 1.232(a)(1) and (3) requires the facility’s full address and separately identifies a preferred mailing address if different. A head-office address used for correspondence therefore belongs in the mailing-address field, not as a substitute for the facility address. As a data integrity practice, label address types clearly in the site master record and review exported forms for accidental substitution before submission.
Q.How should a reviewer distinguish a new trade name from a change to the facility's identity?+
For US FDA food facility registration, 21 CFR 1.232(a)(1) and (5) lists facility details and all trade names separately. As a review practice, compare the proposed name against contracts, site records, and correspondence to establish what actually changed. Record whether it is an additional trading name, a correction, or part of a broader organizational change. Preserve the previous entry and rationale in an audit trail, linking relevant operational events from the process event log.
Q.Can the same person's contact details appear under more than one registration role?+
As an internal review practice, assess each role separately rather than rejecting a record merely because contact details repeat. Document whom the person represents, which responsibilities they perform, and whether the listed channels reach them for each purpose. Repeated details do not establish authority or suitability for another role. Use attributable recording to identify who confirmed the assignments, and refer unresolved role-eligibility questions to the regulatory reviewer before accepting the record.
Q.What should an internal review do when the UFI and facility identity records appear inconsistent?+
For US FDA food facility registration, 21 CFR 1.232(a)(2) requires the facility’s UFI recognized as acceptable by FDA. As an internal practice, investigate the mismatch rather than editing whichever record is easiest to change. Compare the identifier record with the facility name, address, and supporting site documents. Assign an owner, retain the conflicting versions, and document the resolution. A deviation workflow can structure that investigation without presuming which record is correct.
Q.How can a renewal reviewer substantiate a conclusion that registration information has not changed?+
For US FDA food facility registration, 21 CFR 1.230(c) requires an abbreviated renewal to confirm no changes since the preceding registration, renewal, or update and certify truthful, accurate information. As an internal practice, compare that submission with current records for every registration field, noting the evidence reviewed and unresolved questions. Use audit trail review to examine intervening edits and a second-person check for ambiguous comparisons. Record the reviewer’s conclusion, not merely a checked box.
Q.What should the team do internally when registration information changes after a renewal has been submitted?+
As an internal practice, retain the submitted renewal unchanged and open a separate change record. Capture what changed, when it became effective, who identified it, and which registration fields are affected through contemporaneous recording. Have the regulatory reviewer determine the applicable FDA update route and timing for the US food facility. Assign submission and follow-up responsibilities through the quality assurance process, retaining confirmation alongside the change record. Do not mistake an internal master-data edit for an external submission.
Q.How can a buyer use a supplier's registration record without treating it as a product-quality decision?+
As a purchasing practice, use the registration record to reconcile the supplier’s stated facility identity with the site named in purchasing and qualification records. Investigate discrepancies rather than assuming that a familiar corporate name identifies the manufacturing location. Keep this identity check separate from assessments of specifications, manufacturing controls, test results, and complaints. Document the buyer’s acceptance rationale under the supplier-qualification procedure; leave batch release decisions with the people authorized to evaluate the relevant product evidence.
Primary sources
Want to see how Food Facility Registration could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
