A private-label catalog can make a product appear ready for more than one region. That does not mean one formula, label, or compliance file automatically covers every destination. The practical unit of review is the exact product, its claims, its label, the business role of each party, and the country where it will be sold.
Selfnamed currently advertises more than 200 catalog products and fulfillment in the United States and Europe. Use those as planning inputs, then confirm availability, shipping origin, documentation, and regulatory status for the exact SKU and destination. (Selfnamed: How it works; Selfnamed product catalog; Selfnamed fulfillment and shipping)
Start with the exact SKU and market
Before using a platform’s country selector or shipping estimate, record the following for each product:
- exact SKU, formula, size, and product version;
- intended use and every express or implied claim;
- the target country and sales channel;
- the label and packaging planned for that destination;
- the business or person responsible for placing the item on that market;
- the supporting safety, notification, and product documents available;
- fulfillment origin, import route, delivery estimate, and returns process.
Do this separately for each market. A shared brand name or similar bottle does not establish that two products are identical or that one file covers both.
United States: classification and MoCRA roles
In the United States, cosmetics are regulated under the Federal Food, Drug, and Cosmetic Act, as amended by the Modernization of Cosmetics Regulation Act of 2022 (MoCRA). Product classification depends in part on intended use and claims. A product marketed to treat or prevent disease, or to affect the structure or function of the body, may be a drug even if it is also a cosmetic. FDA does not pre-approve ordinary cosmetic products or their claims before sale; cosmetic labeling must still be truthful and not misleading. (FDA: Is It a Cosmetic, a Drug, or Both?; FDA: Cosmetic labeling claims)
MoCRA assigns different duties to different parties. The “responsible person” is the manufacturer, packer, or distributor whose name appears on a cosmetic product label. Among other requirements, the responsible person must ensure adequate safety substantiation and handle serious adverse-event reporting. Facility registration and product listing also apply under the law, subject to specific exemptions and conditions. Do not assume that the brand, platform, and manufacturer have the same role; inspect the label, agreement, and product records to identify who is responsible for each obligation. (FDA: MoCRA; FDA: Registration and listing guidance)
Some small businesses may qualify for exemptions from facility registration and product listing. The exemption is limited: it does not erase every safety, labeling, or adverse-event duty, and certain product categories are excluded. The test depends on statutory conditions that can change or turn on business and product details. Check FDA’s current guidance before relying on an exemption; do not use an old revenue threshold copied from a blog as a substitute. (FDA: Registration and listing guidance)
European Union: responsible person, safety report, and notification
For a cosmetic placed on the EU market, Regulation (EC) No 1223/2009 requires an EU-established responsible person and a product safety assessment before the product is placed on the market. The responsible person must ensure that the Cosmetic Product Safety Report and Product Information File meet the regulation’s requirements and are available to competent authorities. Article 13 requires notification through the Cosmetic Products Notification Portal (CPNP) before placement on the EU market. The portal is a notification system; it is not a government certification or endorsement of the product. (Regulation (EC) No 1223/2009, Articles 4, 10, 11, and 13; European Commission: CPNP)
A platform may say it provides EU compliance support. Ask what that means for the exact product: who is the responsible person, who holds the PIF, who prepared the safety report, whether the product has been notified, and whether the supplied label matches the product version. Keep copies of the answers and the documents that apply to the brand’s sales.
Rules can change after a product launches. Under EU Regulation 2023/1545, since July 31, 2026, cosmetics that do not meet the expanded fragrance-allergen labeling requirements may no longer be placed on the market; products placed on the market before that date may continue to be made available until July 31, 2028, subject to the regulation’s conditions. Confirm the product’s placement date, fragrance composition, and label before relying on the transition period. (European Commission: Fragrance allergen labeling)
Sunscreen shows why markets need separate checks
Sunscreen is a clear example of different product frameworks. FDA regulates sunscreens marketed in the United States as over-the-counter drugs. In the EU, sunscreen products are cosmetics under Regulation 1223/2009, with separate requirements for claims and efficacy. A formula, active ingredient, label, or test accepted in one market should not be assumed to transfer to the other. (FDA: Sunscreen; European Commission: Sunscreen products)
The U.S. framework is also moving. In 2026, FDA issued a final order adding bemotrizinol as a sunscreen active ingredient and later issued another order removing PABA and trolamine salicylate from the monograph’s permitted ingredients. That is a practical reason to verify a sunscreen’s exact formulation and current market status before ordering labels or advertising the product. (FDA: OTC sunscreen regulatory actions)
Do not use the stricter rule as a shortcut
When a brand sells in more than one jurisdiction, “follow the strictest rule” is not a reliable compliance method. The stricter requirement in one market may not satisfy the product classification, ingredient permissions, responsible-person duties, or label rules in another. Instead, maintain a market-specific record for each SKU and let a qualified regulatory professional resolve borderline classifications or conflicting requirements.
A useful comparison sheet has one row per SKU-market combination and separate columns for:
- product classification and intended use;
- formula version and market-specific ingredient review;
- responsible person and manufacturer roles;
- safety evidence and required product files;
- notification, registration, or listing status;
- label language, claims, and required statements;
- fulfillment origin and importer responsibilities;
- effective date of the last regulatory and supplier check.
The point is to make differences visible. Do not infer that a product is available or compliant simply because the platform can ship to that country.
A practical pre-launch sequence
- Select the exact SKU and destination markets; record the formula and label version.
- Confirm product classification and permitted claims for each destination.
- Identify the responsible person, manufacturer, importer, and distributor roles from the label and written agreements.
- Obtain the relevant safety records, product file, notification or listing evidence, and current label for each market.
- Verify fulfillment origin, stock, delivery timing, returns, and any channel restrictions for the SKU.
- Review every product page, package, image, and advertisement for claims that go beyond the evidence or market authorization.
- Save the source, contact, and date for each confirmation, then repeat the review when the formula, claims, label, supplier terms, or law changes.
If the supplier cannot provide a clear answer for an item, treat the gap as unresolved. Pause that SKU in the affected market until the documentation and role assignments are clear.
Keep one compliance record for each SKU and market
Treat the U.S. and EU as separate launch workstreams. For every destination, keep the exact formula and label version beside the responsible-party assignment, required product file, claim review, notification or listing status, and source date. The output of this checklist is a market-specific launch record that can be refreshed when a formula, label, or rule changes.
