To map Shopify Markets to NetSuite OneWorld, decide which legal entity makes each sale, then link that entity to one NetSuite subsidiary. Currencies, prices and domains are set per market in Shopify. Subsidiaries, base currencies, tax nexus and intercompany rules live in NetSuite. The integration routes each order using the market and business entity.
This article covers the mapping in detail: EUR, GBP, CHF and SEK pricing, domains, Shopify business entities, OneWorld subsidiaries, customers, payouts and intercompany, plus the choice between one Shopify store and several expansion stores. Facts were checked against Shopify and Oracle NetSuite documentation on 1 November 2026.
Key takeaways
- A Shopify market is a selling configuration. A NetSuite subsidiary is a legal entity. They are not the same thing, so do not map one to one by default.
- On Shopify Plus, one store can sell through several business entities, and each order says which entity it belongs to. That field is the cleanest key for choosing the NetSuite subsidiary.
- Post orders in the currency the customer paid, and let NetSuite handle conversion to the subsidiary’s base currency.
- NetSuite’s Multi-Subsidiary Customer feature cannot be enabled alongside its EU One Stop Shop feature, which affects how you model consumers who buy from more than one entity.
- Expansion stores give each region its own store, but settings, products and inventory do not sync between them.
What does Shopify Markets control, and what does NetSuite OneWorld control?
Shopify Markets decides what a customer in a given country sees and pays: currency, prices, language, domain, shipping and duties. NetSuite OneWorld decides who owns the sale in the books. Oracle describes OneWorld as one account managing several subsidiaries, each with its own tax nexus and base currency. Oracle also notes that the Multiple Currencies feature is required for OneWorld and that a subsidiary’s base currency cannot be changed after the record is first saved, according to its page on multiple currencies in OneWorld.
| Shopify concept | NetSuite concept | How they usually relate |
|---|---|---|
| Market (for example “EU”, “UK”, “Switzerland”) | No direct equivalent | Used to pick entity, price list and tax treatment |
| Business entity (Plus) | Subsidiary | One to one |
| Presentment currency (what the customer paid in) | Transaction currency | Same value |
| Store currency | Usually the parent or main subsidiary’s base currency | Reference only for multi-currency orders |
| Catalogue prices per market | Price levels or item prices per currency | NetSuite feeds Shopify |
| Location | Location (belongs to a subsidiary) | One to one |
| Domain or subfolder | None | Not needed in NetSuite, but useful in reporting |
How do you map Shopify markets to NetSuite subsidiaries?
There are three patterns we see in Europe.
Pattern 1: one store, one entity, many currencies
A Dutch company sells across the EU, the UK and Switzerland from one Shopify store and one legal entity. Every order goes to the Dutch subsidiary, whatever the currency. The integration still sets the right OSS or local tax code per destination country. This is the simplest model, and many brands start here. The Netherlands page covers the local detail.
Pattern 2: one store, several business entities (Shopify Plus)
A group has a German GmbH for the EU, a UK limited company for Britain and a Swiss AG for Switzerland. Shopify now lets Plus merchants sell from multiple entities in a single store, each using Shopify Payments and paid out to a domestic bank account in its own currency. You assign each entity to markets. Shopify’s developer documentation says the Order, DraftOrder, Market and ShopifyPaymentsPayout objects expose a merchantBusinessEntity field, and order webhooks carry the entity ID. That gives the integration a direct key: entity in Shopify, subsidiary in NetSuite.
There are limits. Shopify says entities must be in countries where Shopify Payments is supported, that you cannot route orders to different entities based on the shipping address, and that the feature does not work with Managed Markets. Its developer page also lists third-party payment providers, subscriptions and reporting as available only for the primary entity. Check these against your setup before committing.
Pattern 3: one store per region
Each regional store belongs to one entity, and the integration maps store to subsidiary. Shopify Plus includes up to nine expansion stores on top of the main store at no extra Shopify cost. Shopify notes that each store runs separately, that products, collections and inventory are not synced between stores, and that apps and theme licences are billed per store. The integration therefore has to publish items and stock to each store from NetSuite.
How should EUR, GBP, CHF and SEK prices flow?
Shopify can convert prices automatically or use prices you set per market through catalogues. According to Shopify’s local currency guidance, the store must use Shopify Payments or Adyen to take payment in several currencies. If a currency is not supported, customers see the market’s base currency.
For European brands we usually recommend fixed prices per currency, managed in NetSuite and pushed to Shopify. Automatic conversion gives prices like CHF 47.83, which looks odd and changes every time rates move. Fixed prices let finance and merchandising agree a CHF 49 or SEK 549 price point once.
On the order side, every Shopify money field comes in two versions: shop money and presentment money. Post the presentment amount and currency to NetSuite as the transaction currency. NetSuite then translates it into the subsidiary’s base currency using its exchange rate tables. If you post the shop-currency amount instead, the receivable will not match what the customer paid, and the payout will not match the bank.
Two practical rules help:
- Make sure every NetSuite customer that receives Shopify orders has each currency it might transact in enabled.
- Agree one source of exchange rates. Shopify, your payment provider and NetSuite may each use a different rate, and the difference must land in a known account.
How do domains fit in?
Shopify supports top-level domains (example.de), subdomains (de.example.com) and subfolders (example.com/de-de) for markets, and you can mix them, as its international domains guide explains. NetSuite does not care which you choose. Domains matter for SEO and customer trust, not for accounting. We still pass the market name onto the sales order as a custom field, because finance often wants to report revenue by market as well as by subsidiary.
How do customers work across subsidiaries?
NetSuite’s Multi-Subsidiary Customer feature lets one customer record be shared with several subsidiaries. That sounds ideal for a consumer who buys from both the UK and EU sites. However, Oracle lists the EU One Stop Shop feature as incompatible with Multi-Subsidiary Customer: neither can be enabled while the other is on. Oracle also says tax information on the customer record defaults only to the primary subsidiary.
If you use NetSuite’s OSS feature, plan for one customer record per subsidiary for consumers, matched on email within that subsidiary. For B2B buyers, who often belong to one entity anyway, the choice is usually simpler. Our article on Shopify B2B and NetSuite in Europe covers company and location mapping, and EU VAT and OSS with NetSuite and Shopify covers the tax side.
What about intercompany?
Intercompany appears when the entity that sells is not the entity that owns the stock. For example, the UK company sells to a British customer, but the order ships from the German subsidiary’s warehouse. NetSuite has intercompany tools for this, including advanced intercompany journal entries and Automated Intercompany Management for eliminations at period end.
The integration should not invent intercompany entries on its own. It should post the sale to the selling subsidiary and record which location fulfilled it. Your accountants then decide whether stock moves by transfer order, intercompany purchase and sale, or journal. We write that rule into the mapping document so the integration and finance agree. Cross-border fulfilment can also change the VAT treatment, which is covered in inventory sync across EU warehouses.
How do payouts map to subsidiaries?
On the Advanced and Plus plans, Shopify Payments can pay out in several currencies, with one bank account per supported currency, according to Shopify’s multi-currency payout guide. With several business entities, each entity has its own payouts. Each payout should post to the bank account of the subsidiary that owns it, in that currency. See Shopify payouts and NetSuite reconciliation.
One Shopify store or expansion stores?
| Question | One store with Markets | Expansion stores |
|---|---|---|
| Catalogue management | One catalogue, prices per market | Products published to each store |
| Inventory | Shared locations | Not synced between stores; NetSuite feeds each |
| Several legal entities | Business entities on Plus, with limits | One entity per store |
| Different themes, apps or teams per region | Limited | Full control per store |
| App and theme costs | Once | Per store |
| Integration complexity | One connection, routing by entity | One connection per store |
Our default for most European brands is one store with Markets, plus business entities where the group has more than one company. We recommend expansion stores when regional teams genuinely run different assortments, apps or payment providers, or when an entity is in a country Shopify Payments does not support.
FAQ
Should each Shopify market have its own NetSuite subsidiary?
Only if each market is a separate legal entity. Many brands sell to all EU countries from one company and one subsidiary, using OSS for VAT.
Can Switzerland sit in the same Shopify store as the EU?
Yes, as its own market with CHF prices. Switzerland is outside the EU VAT system, so it needs its own tax treatment and often its own entity. See our Switzerland page.
Which currency should NetSuite record?
The currency the customer paid in. NetSuite converts it to the subsidiary’s base currency.
Do we need Shopify Plus?
For several legal entities in one store, or for expansion stores, yes. A single-entity business can run Markets and a NetSuite integration on other plans, within each plan’s feature limits.
Next step
The entity and subsidiary mapping is the decision that is hardest to change later. Our free NetSuite Shopify integration assessment reviews your markets, entities and subsidiaries and recommends a structure. For the wider picture, read the Shopify NetSuite integration in Europe guide or see how we build it on the Shopify NetSuite integration page.
