Notifying Cosmetics in Thailand and Vietnam Step by Step

ASEAN has a shared cosmetic framework that member states are all supposed to be following, and on paper that should mean Thailand and Vietnam handle notification the same way. In practice, anyone who has actually filed in both markets knows the harmonization is real but incomplete, and the practical experience of getting a product notified differs enough to matter for a small brand trying to expand across the region.

The shared foundation

Both countries sit inside the ASEAN Cosmetic Directive framework, which was built to align member states around a common approach, similar in spirit to the EU's regulation, with local notification rather than centralized pre-market approval as the general model. That's the good news: you're not building a completely different ingredient philosophy for each country the way you might between, say, the US and Japan. INCI naming, ingredient restriction concepts, and general safety documentation expectations rhyme across the region.

The bad news, or at least the practical reality, is that "aligned framework" doesn't mean "identical process." Local language requirements, the specific notification portal or authority, processing timelines, and how strictly certain product categories get scrutinized all vary by country, and this is exactly where a maker who assumes ASEAN means one filing for the whole region gets tripped up.

Thailand in practice

Thailand's cosmetic notification runs through its own national authority process. A few things makers commonly run into:

• Thai-language labeling requirements apply to cosmetics sold in the local market, similar in spirit to how Canada requires bilingual English and French labeling, just with Thai instead.
• A local responsible entity or importer of record is typically the party who actually files or is accountable for the notification, which matters if you're exporting rather than manufacturing locally.
• Because the underlying framework echoes the ASEAN Cosmetic Directive, ingredient restriction logic will feel familiar if you've worked with EU-style ingredient lists, but the specific national list and any locally added restrictions need their own check rather than assuming full overlap with EU or ASEAN baseline lists.

Vietnam in practice

Vietnam also operates within the ASEAN framework but runs its own national notification process and authority, and the practical experience diverges from Thailand's in a few recognizable ways:

• Documentation and language requirements again mean Vietnamese-language labeling and supporting materials for the local market, not just an English dossier with a translation stapled on.
• Processing timelines and the administrative rhythm of the notifying authority can move differently than Thailand's, which matters for launch planning if you're coordinating a regional release date.
• As with Thailand, the shared ASEAN foundation means the overall shape of the notification, INCI-based ingredient declaration, safety information, responsible party identification, will feel structurally familiar, but the specific national requirements and any locally administered restricted substance nuances need direct confirmation rather than assumption.

Why "just follow the ASEAN directive" undersells the work

The honest way to think about this: the ASEAN Cosmetic Directive gives member states a shared architecture, not a shared filing. It's closer to how EU member states all operate under Regulation 1223/2009 but still each expect labeling in their own national language and engage their own market surveillance bodies. A brand that files once in one ASEAN country and assumes it has "done ASEAN" is making the same category of mistake as a brand that files once in France and assumes it's covered across the whole EU.

A side-by-side snapshot

Aspect	Thailand	Vietnam
Regional framework	ASEAN Cosmetic Directive	ASEAN Cosmetic Directive
Notification model	National notification, not central pre-approval	National notification, not central pre-approval
Label language	Thai required for local market	Vietnamese required for local market
Filing party	Often a local responsible entity or importer	Often a local responsible entity or importer
What still needs local confirmation	National list specifics, processing rhythm, local authority contact	National list specifics, processing rhythm, local authority contact

Practical steps if you're expanding into both

1. Build your ingredient list to INCI standard once, since that groundwork is genuinely reusable across ASEAN markets.
2. Treat each country's notification as its own project with its own language, authority, and timeline, rather than a copy-paste of the first market you entered.
3. Confirm current national restricted substance specifics directly with each country's regulator or a locally current source rather than relying on the shared directive alone.
4. Line up a local responsible party or importer of record early, since this is often a gating requirement rather than a paperwork afterthought.
5. Budget separate lead time for translation and local label artwork for each market.

If you're already using Cosmetic Comply for Canadian notification, the ingredient mapping and CAS work you've done there, matching INCI names, expanding supplier blends, carrying concentrations through, is exactly the kind of groundwork that carries over as more markets come online, so it's worth keeping that ingredient data clean and centralized rather than rebuilding it market by market.