The exemption verdict, the listing gaps, and the adverse-event clock — never the filing itself.
Tamats computes a US MoCRA small-business exemption verdict from the organisation's own sales band and any statutory exclusion category, tracks each product listing's status against a full safety-substantiation checklist, and logs adverse events with the statutory reporting due date computed automatically from the date received. Every field is read from the organisation's own saved MoCRA record — an unset sales band returns an honest 'cannot be determined' rather than a guessed exemption. Nothing here files with the FDA: facility registration, product listing submission and adverse-event reporting all stay outside the product, and every rule it applies links out to the primary FDA source behind it.
MoCRA turned what used to be voluntary cosmetic-safety practice into a set of real federal obligations, and most of the burden is administrative rather than technical — know your exemption status, keep the substantiation file complete per product, don't miss an adverse-event reporting deadline. That is exactly the kind of state that is easy to lose track of across products and easy to get right with a computed checklist instead of a memory of one.
What you do with it
Small-business exemption, computed honestly
The exemption verdict follows the statute's own logic — a legal exclusion category (the product contacts the eye area, is injected, is meant for internal use, or is applied without being washed off for an extended period) voids it regardless of sales; an unknown sales band returns an honest 'cannot be determined', never a default assumption either way.
Per-product listing checklist
Each product listing tracks against the same safety-substantiation checklist — ingredient safety, impurities, microbiological quality, stability, packaging compatibility, irritation data, exposure assessment, claims evidence, adverse-event process, and label review — with a running count of what's provided and what's still missing.
Adverse-event rollup with a computed due date
Open, serious and overdue adverse events are counted from the organisation's own log, and a serious event's statutory reporting due date is computed as business days from the date received, worked out in UTC with no holiday calendar assumed.
Every rule links to its primary source
Findings cite the actual FDA pages behind them — the MoCRA overview, the registration and listing rule, the adverse-event reporting forms — so the organisation can read the regulation itself rather than take the verdict on trust.
What it computes over
—The organisation's own saved MoCRA profile (sales band, exclusion category)
—The organisation's own product listings and their checklist state
—The organisation's own logged adverse events and their received dates
Where it stops
No electronic submission to the FDA — nothing here files a facility registration, a product listing, or an adverse-event report. It computes what those filings would need and links to where you actually file them.
The exemption verdict comes back as 'cannot be determined', not a guess, when the sales band is unknown — this tool will not assume exempt or not-exempt from missing data.
Safety substantiation is a checklist of what evidence exists, not the evidence itself or a judgement that it's adequate — that judgement stays with whoever files the listing.
Who picks it up from here
The organisation's own MoCRA responsible person or US Agent, who actually registers the facility, submits the listing and files any required adverse-event report.
Questions
Does Tamats file my MoCRA product listing with the FDA?
No. It tracks the listing's status against the safety-substantiation checklist and computes the exemption verdict and adverse-event due dates, but the actual facility registration, product listing submission and adverse-event reporting happen outside the product — Tamats links to the FDA pages where they're filed.
How does Tamats know if I'm exempt from MoCRA's small-business provisions?
It applies the statute's own logic to your organisation's saved sales band and any exclusion category (eye contact, injection, internal use, extended wear) — an exclusion voids the exemption regardless of sales, and an unknown sales band returns an honest 'cannot be determined' rather than a guessed verdict.
How is the adverse-event reporting deadline calculated?
As 15 business days after the event was received, worked out in UTC with no holiday calendar — a real date you can put on a calendar, not a rough estimate.