Multi-region, US vs EU vs JP streetwear sizing and customs?

Q: Multi-region, US vs EU vs JP streetwear sizing and customs?

Three real problems for global hype DTC.Sizing:US sizing is the global default for sneakers (Nike, Adidas).EU sizing dominates for streetwear apparel (Stone Island, ACRONYM).JP sizing is its own thing: cm-based for shoes (a US 9 is JP 27cm), S/M/L runs smaller than EU/US (JP-M ≈ EU-S).UK sizing for shoes is 0.5 below US (US 9 = UK 8.5).Magento setup: a single canonical size on the SKU (typically US for sneakers) + a configurable size-chart attribute that renders the locale-appropriate display per store view. Cross-reference table built from brand size charts. Hyvä storefront swaps the displayed size based on store-view geo.Multi-region inventory via Magento MSI: warehouses in NJ (US), Rotterdam (EU), Tokyo (JP), London (UK), Mumbai (IN-domestic only). Customer geo-routes to a stock; stock aggregates inventory from its sources. Drop allocations split across warehouses pre-launch.Customs, covered in the anti-counterfeit FAQ. Specifically for JP: Japan Post + Japan Customs requires HS code + JIS material declaration on the commercial invoice for apparel. Use Yamato Transport TA-Q-BIN for last-mile in JP; reliability is unmatched. For EU customs prepay duties via Zonos / Easyship so EU customers don’t get hit at the door, that’s the #1 complaint cause for US-origin streetwear shipping to DE/FR/NL.Payment: Stripe US, Stripe EU (separate Stripe account), Stripe JP (separate again for JCB + Konbini support), Razorpay India for INR. Different store views = different Stripe accounts = different payment-method mix per region.

Question

Accepted Answer

Three real problems for global hype DTC.

Sizing:

US sizing is the global default for sneakers (Nike, Adidas).
EU sizing dominates for streetwear apparel (Stone Island, ACRONYM).
JP sizing is its own thing: cm-based for shoes (a US 9 is JP 27cm), S/M/L runs smaller than EU/US (JP-M ≈ EU-S).
UK sizing for shoes is 0.5 below US (US 9 = UK 8.5).

Magento setup: a single canonical size on the SKU (typically US for sneakers) + a configurable size-chart attribute that renders the locale-appropriate display per store view. Cross-reference table built from brand size charts. Hyvä storefront swaps the displayed size based on store-view geo.

Multi-region inventory via Magento MSI: warehouses in NJ (US), Rotterdam (EU), Tokyo (JP), London (UK), Mumbai (IN-domestic only). Customer geo-routes to a stock; stock aggregates inventory from its sources. Drop allocations split across warehouses pre-launch.

Customs, covered in the anti-counterfeit FAQ. Specifically for JP: Japan Post + Japan Customs requires HS code + JIS material declaration on the commercial invoice for apparel. Use Yamato Transport TA-Q-BIN for last-mile in JP; reliability is unmatched. For EU customs prepay duties via Zonos / Easyship so EU customers don’t get hit at the door, that’s the #1 complaint cause for US-origin streetwear shipping to DE/FR/NL.

Payment: Stripe US, Stripe EU (separate Stripe account), Stripe JP (separate again for JCB + Konbini support), Razorpay India for INR. Different store views = different Stripe accounts = different payment-method mix per region.