A skincare line called Document Control™ — and not one document controlled the things that mattered.
Document Control™ passed every gate a careful prestige brand runs — supplier qualification, an ISO 22716 certificate, a safety file, stability, batch release, even a recall. Every gate certified something next to the risk: the supplier’s literature, the old formula, a convenient marker, the certificate’s scope. None tested the actual retinol level, the actual preservation on the shelf, or the actual safety of the delivery system.
A file like this follows a pattern we know well. Not this company — Luminae Skin Science, its people, its lot numbers are invented — but the pattern: a prestige line, an ISO 22716 certificate, a “clean beauty” reformulation, and a brand certain it had done the work.
The two things that made the serum unlawful — a drug-level retinol and an inflammation claim — were printed right on the panel. The thing that could grow microbes was a preservative swap nobody re-tested. Every check the company ran was built to read the certificate, the supplier’s literature, or the prior formula — never the product in the jar.
So we built the case, because the lesson is worth more than the recall it usually arrives with.
- You market a cosmetic that makes a claim near the drug line — “reduces inflammation,” “repairs,” “renews” — and no one has formally classified it.
- You reformulated to “clean” or “natural” preservatives and processed it as a minor change.
- You qualified an ingredient or a delivery system on the supplier’s marketing literature, not its own data.
- You hold an ISO 22716 certificate and treat it as proof the product is lawful and safe.
If two or more are true, this case is describing your operation, not an invented one.
The file, as it arrived
Every record behind the case — each one signed, formatted, and internally consistent. Each one, read on its own, looks like a company doing its job.
A product like this fails between documents, never inside one. Open the file and read what you’d catch — then see what we found, just below.
What the records showed, together
No single page is alarming — read apart, each record looks like compliance. Read together, the same evidence resolves into four threads, all turning on one decision: to certify the paperwork, never the product.
A cosmetic that was really an unapproved drug.
The serum made a drug claim — reducing redness and inflammation — and separately carried retinol above the level shown safe for leave-on use. Treated as a cosmetic at every gate, it was never classified, and the active was never measured in the finished product.
A “clean beauty” formula that could grow microbes.
The marketed rev B swapped the preservative system for a botanical one and was processed as an expedited “Minor” change. Its microbial control was demonstrated at no gate.
Every field signal read as an isolated accident.
When the product began failing in the market, each warning was closed on its own — never connected to the preservation gap that produced all of them.
Then they built a premium nobody proved.
The Liposomal Renewal Crème’s whole prestige rested on a delivery system carried as the supplier’s platform claim — and an open jar that was the worst case for everything inside it.
Read apart, every record was defensible — a signed certificate, a passing stability report, a closed complaint. Read together, they describe a product that was an unapproved drug at the first gate, under-preserved by the second, and failing in the field by the last — because every gate certified something adjacent to the risk: the certificate’s scope, the supplier’s literature, the prior formula, a convenient total-active number. The preservative swap was processed as “Minor.” The nano delivery system was onboarded as a “leveraged” line extension. The serious adverse event was filed “non-serious.”
None of it needed a new test to see. It needed one check built to look at the product in the jar — the actual retinol level, the actual preservation, the actual delivery system — the thing every other check agreed to skip.
What was at stake
A recall, an infection, and a Form FDA 483
An under-preserved “clean beauty” serum reached consumers, a documented eye infection went unreported, and an unsubstantiated nano claim invited a drug-by-effect reclassification. The 483 and the recall followed the same paperwork that had passed.
One review reads the product, not the file
A real cosmetic-vs-drug classification stops the launch on the claim and the retinol level; a finished-product preservative-efficacy test on the marketed formula shows the gap before a single jar ships.
If this is your operation
You don’t need us to find out whether your program has the same blind spot. Most of it you can check yourself, this week, with records you already have.
- Has anyone formally classified your product as cosmetic or drug?— or is a claim like “reduces inflammation” riding on a drug-level active no one measured?
- When you reformulated to “clean” preservatives, did you re-run preservative-efficacy testing on the new formula?— or was it processed as a “Minor” change and carried from the old one?
- Does your release test the finished product’s preservation and active level?— or only a T0 count and the input weight?
- Does your ISO 22716 certificate actually cover the claim, the safety, and the new delivery system?— or only the manufacturing system that made them?
Nothing here is built around this one brand — each door points somewhere bigger, and no one of them is the “right” one. The case is just where they all meet.
An ISO 22716 certificate was never the same thing as a lawful, stable product.