Can one Shopify store sell for multiple NetSuite subsidiaries, or does each subsidiary need its own Shopify instance?
One Shopify store can sell for multiple NetSuite subsidiaries, through OneWorld's Multi-Subsidiary Customer feature, and the feature is close to a one-way door. NetSuite documents that tax information from the customer record "defaults only to the primary subsidiary" and that disabling the feature requires reversing or deleting every secondary-subsidiary transaction (Oracle, September 2026).
Yes, technically. The question is what it costs you in the customer record
NetSuite's Multi-Subsidiary Customer feature exists precisely so one customer can transact with more than one subsidiary. Enable it in Setup > Company > Enable Features, under ERP General, and a customer record can carry a primary subsidiary plus secondaries (per Oracle NetSuite documentation, September 2026).
What NetSuite also documents, in a page merchants rarely read before signing, is the list of things that stay bound to the primary subsidiary regardless. Quoting the limitations page directly (per Oracle NetSuite documentation, September 2026):
- Bank Account "supports data related to the primary subsidiary only."
- Customer Center "supports data related to the primary subsidiary only."
- My Account connected to SuiteCommerce is unsupported.
- Credit Limit per Subsidiary is unsupported.
- "All tax information from the customer record defaults only to the primary subsidiary, and is ignored when a secondary subsidiary is selected."
- "On the Financial subtab, the value in the Tax Item field is the default for the primary subsidiary only. For secondary subsidiaries, the tax engine ignores the default tax item and performs a tax lookup."
- Messages, Activities, Files and User Notes on the customer record "are available only for the primary subsidiary."
- EU One Stop Shop (OSS) is listed as an incompatible feature.
Read the tax lines twice. A DTC brand selling into the EU through one storefront and two subsidiaries has just met a feature that is incompatible with OSS and a tax default that only applies to one of its entities.
The one-way door
NetSuite is explicit about what it takes to undo this. To disable the feature you must first reverse or delete all transactions related to customers and their secondary subsidiaries, and remove all secondary subsidiaries from customer records (per Oracle NetSuite documentation, September 2026). There is also a prerequisite gate: "You can't enable the Multi-Subsidiary Customer feature if any incompatible feature or functionality is enabled."
Practically, once a year of orders has landed against secondary subsidiaries, the feature is permanent. That is not a reason to avoid it. It is a reason to decide it deliberately, with your accountants in the room, rather than as an integration configuration detail in week three of a build.
The four architectures, compared honestly
| Architecture | How it works | Right when |
|---|---|---|
| One store, one subsidiary | All orders post to a single NetSuite subsidiary; other entities do not sell through this storefront | The default, and correct far more often than the question implies. Most multi-entity groups have one trading entity for DTC. |
| One store, multiple subsidiaries via Multi-Subsidiary Customer | Order routing logic picks the subsidiary per order, usually by ship-to country or by a channel flag | One brand, one customer base, genuine entity split by geography, and no OSS requirement |
| Shopify Plus expansion stores, one subsidiary each | Separate storefronts per entity, each mapping cleanly to one subsidiary | Different brands, different catalogs, different currencies or different legal presentation. Shopify Plus includes a main store plus 9 expansion stores, with additional stores at $300/month (Shopify, September 2026) |
| One store, Shopify Markets, single subsidiary | One storefront, multiple markets, all revenue in one entity | The entity structure is for tax or holding purposes and does not need to be reflected transactionally at the order level |
The question almost nobody asks first, and should
Does the subsidiary split need to exist at the order level at all?
Entity structures get created for tax residency, liability isolation, or because an acquisition came with one. Not every reason a group has subsidiaries requires each sale to be attributed to one of them in real time. Some can be handled by an intercompany allocation at period end, which keeps the storefront and the order flow simple and puts the complexity in the place best equipped for it: the close.
Ask your accountants whether the subsidiary attribution is required per transaction or per period. If the answer is per period, the entire architecture question dissolves, and you should take that answer before you configure anything.
When NOT to run one store across subsidiaries
- When any entity is in the EU and you use OSS. NetSuite lists OSS as incompatible with the feature.
- When the entities need different credit limits for the same customer. "Credit Limit per Subsidiary" is an unsupported capability.
- When you are on SuiteCommerce for customer self-service. "My Account connected to SuiteCommerce" is unsupported, which matters directly to anyone moving a storefront while keeping SuiteCommerce MyAccount.
- When the brands are genuinely different. Expansion stores are cheaper than an irreversible ERP feature, and the operating model is simpler.
- When nobody can state the order-routing rule in one sentence. If the rule is "it depends," it will be implemented as "it depends," and it will be wrong in both directions.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Decide the entity architecture in finance before you decide it in Shopify. Enabling Multi-Subsidiary Customer is close to permanent, it is incompatible with OSS, and it quietly binds tax defaults, bank accounts and customer-facing account data to a single primary subsidiary. Those are accounting consequences that arrive dressed as integration settings.
- Where we disagree: Integration vendors answer this question with "yes, we support multi-subsidiary routing," which is true and which is not the question. The question is what you lose in the customer record, and the answer is documented by NetSuite in a limitations page that no integration datasheet links to.
- What this page adds: that NetSuite's Multi-Subsidiary Customer feature is effectively irreversible once transactions exist, that it is listed as incompatible with EU One Stop Shop, that tax information, bank account and Customer Center data stay bound to the primary subsidiary, and that Shopify Plus expansion stores are often the cheaper architecture for the same requirement.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.
Where we worked this out
Our decision records