Structured or PDF: How to Submit Your Cosmetic Data

Once you've accepted that MoCRA means registering your facility and listing your products with the FDA, the next question is more mundane but genuinely trips people up: do you type everything into the portal field by field, or do you prepare a structured data file and upload it? Both paths exist for a reason, and which one makes sense depends almost entirely on how many products you're dealing with.

The two general paths

FDA's cosmetic registration and listing system is built to accept information in more than one way. Broadly, you're choosing between:

• Direct portal entry, where you log into the system and manually fill out fields for facility details, responsible person, and each product's category and ingredients
• Structured data submission, where you prepare your product and ingredient information in a defined electronic format and upload it, letting the system parse many products at once

Small businesses may also be exempt from registration and listing requirements entirely, so it's worth checking your business size and product category against the current exemption criteria before assuming either submission path applies to you at all.

Why the format choice matters

If you make eight products, portal entry is barely a decision. You sit down, fill in eight product records, and you're done in an afternoon. The structured file format would be overkill, since building and validating a data file for eight products often takes longer than just typing them in.

If you make eight hundred products, or you're a contract manufacturer listing on behalf of several brands, manual entry turns into a real operational cost. Every product needs its ingredient list, category, and responsible party details entered correctly, and doing that by hand at scale multiplies your error surface. A structured submission, prepared once from your internal product database and validated before upload, becomes the more sensible investment.

A rough decision guide

Catalog size	Update frequency	Likely better fit
Under 20 products	Occasional new SKUs	Direct portal entry
20 to 100 products	Regular seasonal additions	Either, depending on internal data systems
100+ products	Frequent additions or contract manufacturing for others	Structured data submission

Update frequency matters as much as raw count. A brand with 40 stable products that rarely change can live comfortably with manual entry, updating a record here and there. A brand launching 15 new SKUs a quarter, even from a smaller base catalog, starts to feel the benefit of a repeatable structured process instead of re-keying data every launch cycle.

What structured submission actually saves you

The value isn't just typing speed. A structured format forces consistency: the same ingredient naming conventions, the same category codes, the same responsible person details, applied uniformly across every product record. Manual entry, especially when multiple people at a company are doing it over time, tends to drift. One person names an ingredient one way, another does it slightly differently, and it becomes harder to reconcile records later or to quickly amend a whole line of products when a formula changes across several SKUs.

What doesn't change either way

Regardless of submission method, the substance of what MoCRA asks for stays the same. You still need:

• Facility registration with accurate site information
• Product listing that includes ingredients by their proper names
• A named responsible person
• Safety substantiation on file, even though that documentation isn't uploaded as part of listing itself
• Adverse event recordkeeping practices in place

The submission format is a delivery mechanism, not a shortcut around any of the underlying obligations. A structured file with sloppy ingredient names is just as noncompliant as a portal entry with the same problem, it just fails faster and at higher volume.

Practical starting point

If you're unsure which way to go, start by counting your actual SKU count and realistic launch cadence for the next year, not just where you are today. Brands scaling quickly often regret setting up manual entry as "good enough for now" and then having to rebuild a structured process later once the backlog piles up.

Cosmetic Comply is built around Canada's notification system today, with the US listing workflow on the roadmap, but the underlying discipline is the same everywhere: get your ingredients mapped cleanly to their proper INCI names and concentrations once, in a structured way, and every future submission, in any format, gets faster because you're not starting from a blank ingredient list each time.