# Can one Shopify store sell for multiple NetSuite subsidiaries, or does each subsidiary need its own Shopify instance?

Reviewed by Martin Dejnicki, Director of SEO & AI Search · facts verified October 11, 2026 · canonical: https://deploi.ca/shopify/faq/netsuite-multiple-subsidiaries-one-store

## Short answer

Yes, one Shopify store can sell for several NetSuite subsidiaries, but only with routing logic on top of the connector. Oracle's NetSuite Connector docs say to "use a separate connector account for each subsidiary" ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html), October 2026). Sharing a customer across subsidiaries needs Multi-Subsidiary Customer, which means tax defaults stay on the primary subsidiary ([NetSuite's limitations page](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html), October 2026).

- **Oracle's connector guidance:** One connector account per subsidiary. One of Oracle's two examples is two Shopify stores with a connector account each. One account syncing several subsidiaries "might get NetSuite errors" (October 2026). ([Oracle NetSuite Help Center, Setting Up Order Sync to Handle Multiple Subsidiaries in NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html))
- **Multi-Subsidiary Customer tax rule:** Tax defaults to the primary subsidiary. Tax information "defaults only to the primary subsidiary". EU One Stop Shop is incompatible, and credit limits per subsidiary are unsupported (October 2026). ([Oracle NetSuite Help Center, Multi-Subsidiary Customer Feature Limitations](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html))
- **Switching the feature off:** Reverse or delete secondary-subsidiary transactions. NetSuite's steps: reverse or delete those transactions, remove secondary subsidiaries from customer records, then clear the box in Enable Features (October 2026). ([Oracle NetSuite Help Center, Enable the Multi-Subsidiary Customer Feature](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460991.html))
- **Stores in one Shopify Plus fee:** Main store plus 9 expansion stores. Each store past ten costs $300 USD a month or a revenue share. Expansion stores must extend the main brand; separate brands need their own Plus contract (October 2026). ([Shopify, Shopify Plus pricing](https://www.shopify.com/plus/pricing); [Shopify Help Center, Overview of expansion stores for organizations on the Shopify Plus plan](https://help.shopify.com/en/manual/organization-settings/expansion-stores))

## Deploi's call

One Shopify store can sell for several NetSuite subsidiaries, but with Oracle's connector a store per country-split entity is the default. Decide the entity architecture in finance before you decide it in Shopify. Multi-Subsidiary Customer is close to permanent. It binds tax defaults, bank accounts and customer-facing account data to one primary subsidiary, so treat it as an accounting decision, not an integration setting.

**BUY: Give each subsidiary its own store when**

- Each subsidiary sells in its own country under the same brand. Shopify Plus pre-approves international expansion stores, and one Plus fee covers ten stores ([Shopify Help Center](https://help.shopify.com/en/manual/organization-settings/expansion-stores), October 2026).
- You run Oracle's own NetSuite connector, which says to "use a separate connector account for each subsidiary" ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html), October 2026).
- Any entity files through EU One Stop Shop (OSS), which NetSuite lists as incompatible with Multi-Subsidiary Customer ([NetSuite's limitations page](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html), October 2026).
- [Our multi-entity close record](https://deploi.ca/shopify/build-vs-buy/multi-entity-multi-currency-consolidated-close) scores one connector per store, each mapped to its own subsidiary, BUY (October 2026).

**CUSTOMIZE: Keep one store across subsidiaries when**

- The same customers buy from more than one entity, and finance accepts Multi-Subsidiary Customer's limits.
- One sentence states the routing rule, such as ship-to country, and every order's customer and items sit in the order's subsidiary ([Oracle NetSuite's mapping guide](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_163460310330.html), October 2026).
- Someone owns the routing logic on top of the connector, the case [our multi-entity close record](https://deploi.ca/shopify/build-vs-buy/multi-entity-multi-currency-consolidated-close) scores CUSTOMIZE (October 2026).

## Can one Shopify store sell for several NetSuite subsidiaries?

One Shopify store can sell for several NetSuite subsidiaries, but Oracle's own NetSuite Connector is built around one subsidiary per connector account. Oracle's docs say "you should use a separate connector account for each subsidiary", and give two Shopify stores, each with its own connector account, as one example ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html), October 2026). Syncing several subsidiaries through one account "might get NetSuite errors from referencing records in the wrong subsidiary".

The rule underneath is NetSuite's: "All records referenced in an order must be in the same subsidiary as the order" ([Oracle NetSuite's mapping guide](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_163460310330.html), October 2026). So a one-store setup needs a routing rule that sets the subsidiary on every customer, order and item, while a store per subsidiary needs none. Celigo's listing says it can "Sync multiple stores to one NetSuite instance" ([Celigo](https://apps.shopify.com/celigo-netsuite-smartconnector), October 2026). [Our NetSuite integration record](https://deploi.ca/shopify/build-vs-buy/netsuite-integration) already notes that Oracle's connector "thins out at kits, partial fulfillments, and multi-entity setups" (October 2026). This choice sits under [whether NetSuite is worth it at $20M to $30M](https://deploi.ca/shopify/faq/netsuite-overkill-vs-quickbooks-at-20m-30m-gmv).

## What does Multi-Subsidiary Customer cost you in the customer record?

Multi-Subsidiary Customer costs you per-subsidiary customer data, because tax defaults, bank details and self-service data stay with the primary subsidiary. NetSuite's feature "lets you share customer and sub-customer records with multiple subsidiaries" ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/bridgehead_N276747.html), October 2026), so it matters when the same customer buys from more than one entity. Administrators turn it on under **Setup > Company > Enable Features** ([Oracle NetSuite's setup page](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460991.html), October 2026). NetSuite's limitations page lists ([Oracle NetSuite limitations](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html), October 2026):

- **Bank Account and Customer Center:** each "supports data related to the primary subsidiary only".
- **Credit Limit per Subsidiary and My Account connected to SuiteCommerce:** unsupported, which matters if you [move the storefront off SuiteCommerce](https://deploi.ca/shopify/faq/netsuite-integration-changes-leaving-suitecommerce) but keep its account portal.
- **Tax information:** "All tax information from the customer record defaults only to the primary subsidiary, and is ignored when a secondary subsidiary is selected."
- **Tax Item field:** the default holds "for the primary subsidiary only"; with a secondary subsidiary, "the tax engine ignores the default tax item and performs a tax lookup".
- **Messages, Activities, Files and User Notes:** "available only for the primary subsidiary".
- **EU One Stop Shop (OSS):** listed as an incompatible feature.

So a brand selling into the EU through one storefront and two subsidiaries meets a tax default that covers one entity and a feature that excludes OSS.

## Can you switch Multi-Subsidiary Customer off later?

You can switch Multi-Subsidiary Customer off only after unwinding it. NetSuite's steps are to "Reverse or delete all transactions related to customers and their secondary subsidiaries", then "Remove all secondary subsidiaries from customer records", then clear the box in Enable Features ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460991.html), October 2026). There is a gate on the way in too: "You can't enable the Multi-Subsidiary Customer feature if any incompatible feature or functionality is enabled."

In our judgment, once a year of orders has landed against secondary subsidiaries, Multi-Subsidiary Customer is permanent in practice. That is not a reason to avoid the feature. It is a reason to decide it with your accountants in the room, rather than as a connector setting in week three of a build.

## Which store layout fits your NetSuite subsidiaries?

The store layout should follow how your NetSuite subsidiaries trade, because Oracle's connector maps one subsidiary per connector account and Shopify Plus keeps expansion stores for the main brand.

**Four Shopify store layouts and the subsidiary structure each one fits**

| Layout | How it works | Right when |
| --- | --- | --- |
| One store, one subsidiary | Every order posts to one NetSuite subsidiary; other entities don't sell through this storefront | In our judgment, most groups: one entity sells direct to consumers and the rest settle by intercompany allocation |
| One store, several subsidiaries | A routing rule, such as ship-to country, picks each order's subsidiary; shared customers need Multi-Subsidiary Customer | One brand and customer base, no EU One Stop Shop (OSS), and someone who owns the routing logic |
| A store per subsidiary | Each store syncs one subsidiary through its own connector account | Subsidiaries split by country under one brand, the setup Oracle's connector docs describe |
| One store on Shopify Markets, one subsidiary | Markets sells in several currencies while all revenue books to one entity | Entities exist for tax or holding reasons and need no order-level split |

Sources: [Oracle NetSuite Help Center, Setting Up Order Sync to Handle Multiple Subsidiaries in NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html); [Oracle NetSuite Help Center, Multi-Subsidiary Customer Feature Limitations](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html); [Shopify, Shopify Plus pricing](https://www.shopify.com/plus/pricing); [Shopify Help Center, Overview of expansion stores for organizations on the Shopify Plus plan](https://help.shopify.com/en/manual/organization-settings/expansion-stores). Verified October 11, 2026.

## Does each Shopify sale need a NetSuite subsidiary at all?

Each Shopify sale needs a NetSuite subsidiary only if your accountants require attribution per transaction rather than per period. Entity structures get created for tax residency, liability isolation, or because an acquisition came with one. Not every one of those reasons requires each sale to land in a subsidiary as it happens.

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 close. [Our multi-entity close record](https://deploi.ca/shopify/build-vs-buy/multi-entity-multi-currency-consolidated-close) makes the same point from the other side: "a second store per entity avoids the glue entirely" (October 2026). Ask your accountants whether attribution is required per transaction or per period, and take that answer before you configure anything.

## When should one Shopify store not sell for several subsidiaries?

One Shopify store should not sell for several NetSuite subsidiaries when tax, credit or branding has to differ by entity.

> **When not to do this**
> - **When any entity is in the EU and uses EU One Stop Shop (OSS).** NetSuite lists OSS as incompatible with Multi-Subsidiary Customer ([Oracle NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html), October 2026).
> - **When entities need different credit limits for the same customer.** "Credit Limit per Subsidiary" is unsupported under Multi-Subsidiary Customer.
> - **When customers self-serve in a SuiteCommerce site's My Account.** "My Account connected to SuiteCommerce" is unsupported under Multi-Subsidiary Customer. NetSuite's list doesn't say whether a standalone SuiteCommerce MyAccount portal counts, so ask Oracle before you pair one with Multi-Subsidiary Customer.
> - **When the brands are genuinely different.** Shopify says a company with several brands "will need a separate Shopify Plus contract per brand" ([Shopify](https://www.shopify.com/plus/pricing), October 2026), so separate brands already mean separate stores, as [Plus pricing for several brands](https://deploi.ca/shopify/faq/shopify-plus-contracts-for-3-brands) sets out.
> - **When nobody can state the routing rule in one sentence.** If the rule is "it depends", it will be built as "it depends", and it will be wrong in both directions.

## Deploi's point of view

**Where we disagree.** Integration vendors answer this question by saying they support multi-subsidiary routing, which can be true and is not the question. The question is what you lose in the customer record, and NetSuite documents the answer on a limitations page that integration datasheets rarely link to. Oracle's own connector documentation goes further and advises a separate connector account per subsidiary.

**What this page adds.** The parent decides whether NetSuite is worth it at $20M to $30M. This page takes the multi-entity case into Shopify: Oracle's advice of one connector account per subsidiary, what Multi-Subsidiary Customer binds to the primary subsidiary and what it takes to switch off, and when a Shopify Plus expansion store per entity fits.

## When this answer changes

- Oracle changes its NetSuite Connector guidance on syncing several subsidiaries through one connector account.
- NetSuite removes EU One Stop Shop (OSS) from the Multi-Subsidiary Customer incompatible list, or changes the steps to switch the feature off.
- Shopify changes the expansion store conditions, the ten-store allowance or the $300 a month price for extra stores.
- Your group adds an entity in a new country, or an acquisition brings a second brand.
- Your accountants rule that subsidiary attribution can be per period rather than per transaction.

## Sources

1. [Oracle NetSuite Help Center, Setting Up Order Sync to Handle Multiple Subsidiaries in NetSuite](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_164057356458.html), checked October 11, 2026
2. [Oracle NetSuite Help Center, Multi-Subsidiary Customer Feature Limitations](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460470.html), checked October 11, 2026
3. [Oracle NetSuite Help Center, Mapping a Subsidiary on Orders in NetSuite Connector](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_163460310330.html), checked October 11, 2026
4. [Oracle NetSuite Help Center, Enable the Multi-Subsidiary Customer Feature](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1509460991.html), checked October 11, 2026
5. [Oracle NetSuite Help Center, Assigning Subsidiaries to a Customer](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/bridgehead_N276747.html), checked October 11, 2026
6. [Shopify, Shopify Plus pricing](https://www.shopify.com/plus/pricing), checked October 11, 2026
7. [Shopify Help Center, Overview of expansion stores for organizations on the Shopify Plus plan](https://help.shopify.com/en/manual/organization-settings/expansion-stores), checked October 11, 2026
8. [Celigo, NetSuite Integration by Celigo on the Shopify App Store](https://apps.shopify.com/celigo-netsuite-smartconnector), checked October 11, 2026
9. [Deploi Build vs. Buy, Build or Buy a Multi-Entity, Multi-Currency Close on Shopify?](https://deploi.ca/shopify/build-vs-buy/multi-entity-multi-currency-consolidated-close), checked October 11, 2026, Deploi research
10. [Deploi Build vs. Buy, Should You Build or Buy Your NetSuite Integration on Shopify?](https://deploi.ca/shopify/build-vs-buy/netsuite-integration), checked October 11, 2026, Deploi research