Multi-region, US vs EU vs Korea, different ingredient bans?
Yes, and this is where Magento beats Shopify by a wide margin for skincare specialty.
The ingredient-ban divergence:
- US (FDA + Prop 65 + MoCRA), ~50 banned, ~900 Prop 65 warning, ~10,000 self-regulated.
- EU (EC 1223/2009), ~1,300 banned, ~250 restricted-use. Strictest market.
- Korea (KFDA), closer to EU but allows some UV filters EU bans. Methylene-bis-benzotriazolyl tetramethylbutylphenol is the classic example: OK in Korea, banned in EU since 2024.
- Japan (MHLW), closer to Korea. Allows ~30 UV filters US FDA doesn’t yet (US FDA is famously slow on sunscreen approvals).
- Australia (TGA), closer to EU, but has its own AICIS chemical inventory.
Magento Multi-Source Inventory (MSI) + per-store-view product visibility solves this natively:
- Store view per region,
us,eu,uk,au,kr,jp. Each gets its own catalog visibility rules. - Custom attribute
allowed_regions, multi-select of region codes. A SKU containing methylene-bis-benzotriazolyl tetramethylbutylphenol getskr,jponly. EU store view hides it natively. - Geo-routing at the CDN level, Cloudflare worker routes traffic to the correct store view based on IP. Customer can override but defaults are sane.
Shopify Markets shares the catalog, you can’t hide a SKU per-market without Liquid scripting and the SKU still indexes in Google for the wrong country. Magento hides at the store-view level natively, no JS hack.