Core label requirements
Return to identity, quantity, ingredients, business details, and warnings.
Updated September 29, 2026 · Official sources are linked where cited · Development guidance; no qualified legal or regulatory review.
COSMETIC CLAIMS
Whether a product is a cosmetic, a drug, both, or another regulated article depends on the applicable definitions and evidence of intended use. A familiar format such as a cream or serum does not settle the question.
Check exact claim wordingReview the product name, label, directions, website, marketplace listing, social posts, images, testimonials, comparison language, and any material supplied to retailers or influencers. Consider express wording and the message reasonably conveyed by the presentation as a whole. Keep the exact text and screenshot or artwork version with the review record.
A qualifier must be clear, close, and consistent with the main message, but a disclaimer cannot reliably erase an otherwise drug-oriented intended use. Likewise, avoiding one prohibited word does not make the overall presentation cosmetic. If classification is unresolved, keep the claim out of the release queue until the product and regulatory pathway are reviewed.
Fictional example: a serum label says “repairs eczema and stimulates collagen production,” while a nearby line calls the product a cosmetic. The disease-treatment and body-function messages still require classification review; the word “cosmetic” does not cancel them. Collect the label, product name, directions, website, marketplace listing, images, testimonials, formula, and substantiation before deciding the pathway.
A team might consider appearance-focused wording, but no replacement claim should be copied from this example or treated as approved. The revised message must accurately describe the intended cosmetic effect, match the evidence, and be reviewed again in its full presentation. Keep both the rejected and revised versions in the release record.
Return to identity, quantity, ingredients, business details, and warnings.
Find claim-context and version-control gaps.
Keep classification separate from registration, listing, safety, and adverse-event work.
Updated