Multi-market ecommerce

Multi-market ecommerce is serving more than one country from a single ecommerce stack. The merchant operates one product catalogue, one stock pool, one team, one operational rhythm. The buyer in each country sees prices in their currency, content in their language, payment methods they recognise, shipping rates that match their delivery network, and tax handled correctly under their local rules. The complexity stacks across five axes. ## Language Each market needs the storefront content in the local language. Product names, descriptions, marketing copy, legal pages, transactional emails. Some content is translated. Some is rewritten per market. The CMS structure has to support both. ## Currency Prices show in the local currency on every product view. Conversion is either fixed (a price-list per market) or dynamic (a base price with FX conversion). Fixed is more common for B2B and considered ecommerce. Dynamic is more common for international consumer brands. ## Tax EU VAT is one bucket. UK, Norway, Switzerland, US sales tax, Japan consumption tax are all different. The storefront needs to apply the right tax at the right point in the buying flow, and the receipt needs to show the right breakdown. ## Payment Klarna in the Nordics. iDEAL in the Netherlands. Bancontact in Belgium. Multibanco in Portugal. Each market has its own preferred methods. The checkout needs to expose the right ones. ## Shipping Local carriers, local rates, local delivery promises. PostNord in Sweden. DHL in Germany. UPS in the US. The shipping calculator and the delivery options have to be market-aware. ## How Frntkey handles multi-market Frntkey is built for multi-market from the ground up. Storyblok manages content per market, with internationalisation features that let editors localise once and publish to many. The commerce backend (Norce, Shopware) handles pricing logic, market-specific catalogues, and tax. The frontend renders the right combination based on the buyer's market. Bread and Boxers runs eleven markets on Frntkey. Norce as the commerce engine, Storyblok for content, Junipeer for backend integrations, Frntkey for the storefront. The same operational team manages all eleven from one Storyblok space and one Norce instance. ## The common mistake The common multi-market mistake is treating each market as a separate site. Separate codebases, separate content, separate teams. The cost compounds. Every feature ships eleven times. Every bug fix needs eleven deploys. Every analytics dashboard needs eleven views. The packaged-frontend approach inverts this. One codebase, eleven configurations. Content authored once and adapted per market. Pricing computed at request time based on the buyer's locale. Shipping and payment configured at the commerce backend, exposed in the storefront automatically. ## The honest tradeoff A truly differentiated experience per market (different visual brand, fundamentally different product positioning, market-specific features) needs more work than swapping content per locale. For brands operating one positioning across many markets, packaged multi-market is most of the way there on day one.