FDA Cosmetic Registration Verification: How to Build an Evidence File

An FDA cosmetic registration evidence file is a controlled set of records that supports specific statements about a facility, product, or exemption as of a defined date. It is not an FDA certificate, and it should not be presented as one.

FDA’s September 9, 2026 clarification says the agency does not issue certificates, letters, emails, or other documents to verify cosmetic facility registration, product listing, or exemption status. FDA also says registration and listing do not indicate approval. For brands answering retailer and ecommerce requests, the operational response is to keep source records current, indexed, and ready to export in a limited review packet.

Separate the master evidence file from the submission packet

The master evidence file is the controlled internal record. It can contain original portal captures, submission confirmations, identifiers, labels, supporting calculations, correspondence, and review history. Access may need to be limited because some records contain financial, formulation, contact, or account information.

The submission packet is a purpose-built export. It should include only the records needed to answer a named request. A marketplace reviewer usually does not need the company’s full accounting ledger, complete safety substantiation file, or unrelated product listings.

Use a simple eight-part file structure

1. 00 — Read Me and evidence index: scope, owner, version, last review, next review, and a row for every evidence item.
2. 01 — Requests: the exact marketplace or retailer prompt, account, product or category, date received, deadline, submission date, and outcome.
3. 02 — Entity and role: legal name, DBAs, addresses, label role, responsible-person mapping, contract-manufacturing relationships, and documents connecting different names.
4. 03 — Facility registration: FDA portal captures, FEI or registration number, operation type, submission confirmations, registration status, renewal date, and amendment history.
5. 04 — Product listing: Cosmetic Product Listing Numbers, product-to-facility mapping, submission records, annual update history, and the controlled label version.
6. 05 — Labels and classification: current label panels, claims review, product category, and notes identifying a cosmetic, drug/cosmetic, device, or other route.
7. 06 — Exemption support: signed self-attestation, three-year sales calculation, inflation source and method, excluded-product review, and approval history, if an exemption is claimed.
8. 07 — Submitted and superseded: the exact outward-facing packet, correspondence and decision, followed by prior versions retained under the company’s record policy.

Use file names that remain meaningful outside the folder. A pattern such as EvidenceID_EntityOrSKU_DocumentType_AsOfDate_Version is more reliable than final-final-2.pdf.

Make the evidence index the control center

The index should tell a reviewer or colleague what each file is and whether it is still usable. Recommended fields include:

• evidence ID;
• request or requirement answered;
• document title and file name;
• source system or issuer;
• entity, facility, brand, and SKU covered;
• identifier type and value;
• status shown;
• capture, submission, issue, and last-verified dates;
• renewal, expiration, or next-review date;
• document owner;
• confidentiality or disclosure level; and
• notes, including any name or address reconciliation.

Keep “document date” and “last verified” separate. A submission confirmation from 2024 does not show that the facility remained active on the day a marketplace asked in 2026. Conversely, a new screenshot should not erase the original submission history.

What a Cosmetics Direct screenshot should show

FDA’s Cosmetics Direct page says the facility homepage displays registration status and renewal date. For a current portal capture, show enough context to establish that the page is from FDA and make the relevant fields legible: establishment name, physical address, operation type, registration number, status, and renewal date where available.

Save the original image or PDF without editing. Record who captured it, the source URL or system, and the capture date. If disclosure requires redaction, preserve the original internally and create a separate, clearly labeled redacted copy. Never composite fields from different screens into something that looks like a single FDA document.

The FDA registration and listing guidance identifies the FEI as the facility registration number used for this purpose. Confirm that the identifier belongs to the physical establishment in scope; an FEI alone does not show every current registration field or prove product approval.

Connect product-listing evidence to the correct label

For each marketed cosmetic, record the product name exactly as it appears on the label, the responsible person, relevant facility or facilities, product category, listing number, submission type, submission date, and annual-update status. Link the row to the label version that was current for the submission.

FDA’s guidance says product listing numbers are not available for public disclosure. Therefore, preserve the first-party portal or submission record that associates a number with a product. Do not assume an external reviewer can validate it in an open database, and do not expose a full ingredient or formulation file merely to compensate for that limitation.

Maintain a change trigger for a new product name, formula grouping, facility, responsible person, label, or discontinuation. The regulatory assessment determines whether a submission update is required; the evidence file should make sure the change is noticed and assigned.

Build an exemption file with the same discipline

If the business relies on the MoCRA small-business exemption, place the signed, dated self-attestation at the front of the exemption section. Behind it, retain the three-year U.S. cosmetic-sales worksheet, the inflation-adjustment source and calculation, a product and facility inventory, and a review of the four categories that disqualify a business from the small-business exemption.

The conclusion should be scoped to named entities, facilities, products, and an “as of” date. FDA does not issue an exemption certificate, so never label the self-attestation “FDA exemption approval.” For the complete structure, use our MoCRA small-business exemption letter guide.

Add time and event controls

MoCRA evidence changes on more than one clock. Required facility registrations generally renew every two years. Required facility information must generally be updated within 60 days after a change. Responsible persons generally update cosmetic product listings annually. Marketplace invoice and screenshot freshness rules can run on different timelines.

Track both calendar dates and events. Useful triggers include a facility move, legal-name or DBA change, new contract manufacturer, new or discontinued SKU, revised claims, new label, material sales change, new excluded-category product, marketplace rejection, and FDA or platform policy update. Assign an owner and escalation path; a reminder with no accountable person is not a control.

Create a reviewer-ready export

A concise outward-facing packet usually follows this order:

1. a cover memo identifying the request, seller role, facility or SKU, and “as of” date;
2. a requirement-to-evidence map;
3. selected first-party records, labels, invoices, or self-attestation;
4. short, supported explanations for any name or relationship mismatch; and
5. a boundary statement that the packet is not an FDA certificate or approval.

Run a final quality check: correct account, correct entity, correct physical facility, correct SKU, correct identifier type, current status, readable files, unaltered originals, matching labels, no unsupported exemption, and no “FDA approved” language. Archive exactly what was sent and the platform response.

Install the controls without building from scratch

The Syntera MoCRA Marketplace Compliance Evidence Pack ($39) includes the facility-registration evidence checklist, Cosmetics Direct screenshot/status/renewal tracker, product-listing evidence tracker, FDA submission-confirmation log, marketplace-request tracker, portal-screenshot checklist, evidence index, last-verified controls, exemption self-attestation framework, and supporting-exemption-evidence checklist.

When the need extends beyond one evidence request, the Syntera MoCRA Compliance Evidence & Renewal Control System ($99) provides the full operating structure for recurring reviews and renewal control. Read our FDA MoCRA certificate explainer for the source issue this system is designed to address.

Syntera is an independent operational aid, not an FDA certificate, FDA verification, legal advice, filing service, or guarantee of marketplace acceptance. FDA does not charge a fee to submit MoCRA facility registrations or cosmetic product listings.

Frequently asked questions