Classification of the feature
Shopify is expanding the capabilities of Shopify Payments for businesses with multiple legal entities within the same country. According to Shopify, this allows merchants to represent different legal entities within a country in a single Shopify setup, without necessarily having to operate multiple completely separate stores.
At first, this sounds like a purely accounting detail. In practice, however, it affects core processes such as tax logic, payout accounts, invoicing, risk and liability separation, and regional brand structures. This can become particularly relevant for international D2C brands, franchise models, B2B sales units, or corporate groups with multiple limited liability companies (GmbHs).
What’s important here: this feature does not replace an ERP structure, tax consulting, or clean governance. Above all, it reduces operational friction within more complex Shopify setups.
What the feature is – and what it isn’t
According to Shopify, the new model makes it possible to manage multiple legal entities within the same country using Shopify Payments. The main focus is on payment processing, legal attribution, and organizational separation within a commerce system.
The feature is not a fully fledged multi-company platform in the classic ERP sense. It therefore does not replace:
- Financial accounting
- Consolidation in accounting
- tax consulting
- complex intercompany processes
- individual compliance requirements per country
Likewise, the feature does not automatically mean that every combination of brand, inventory, domain, tax logic, and payment flow can be freely mixed and matched. As of today, many details still depend on Shopify Markets, Shopify Payments, regional availability, and the specific store structures.
A common misconception in projects: “An additional legal entity will automatically solve our organizational problems.” In practice, the complexity often just shifts from the shop structure towards data flows, governance, and reporting.
Requirements & Data Basis
Before larger shops actively start using the feature, the underlying data should be clean. Especially when there are multiple legal entities, inconsistencies between checkout, ERP, accounting, and support can otherwise arise quickly.
Particularly relevant are:
- accurate company data for each legal entity
- clear control logic
- consistent invoice data
- defined payout accounts
- clear assignment of orders
- clear country and market logic
- coordinated ERP interfaces
For example, if the same brand is sold in Germany through two different GmbHs, it must be clear from a technical and organizational standpoint:
- Which company sells which basket of goods?
- Which billing address applies?
- Which VAT ID is used?
- Which bank account will receive the payout?
- Which department handles returns?
- Which legal texts apply?
Especially with international shops, errors often don’t occur in the checkout itself, but later during exports, tax reports, or payment reconciliations.
Consent and customer data logics should also be reviewed. When customers move between markets or legal entities, it must be clearly defined which systems are allowed to use which data.
How to use it concretely in the Shopify admin
The specific setup depends on the existing Shopify configuration. According to Shopify, management is handled in connection with Shopify Payments and the respective market or organizational structures.
In practice, the following approach is recommended:
Document existing corporate structure
Before any technical setup, you should first create a simple overview:
- society
- Brand
- Market/Country
- Bank account
- Tax ID
- ERP assignment
- Domain/Subdomain
- Warehouse locations
Many problems arise later because these fundamentals were never properly documented.
Review Shopify Markets
The following should then be checked:
- Which markets already exist?
- Which domains are used?
- Which checkout flows are different?
- Are there local pricing logics?
For example, if Germany and Austria operate in a technically identical way but use legally separate entities, this exact allocation becomes relevant.
Check Shopify Payments configuration
This is followed by checking the Shopify Payments settings:
- available countries
- supported corporate models
- Bank account details
- Tax data
- payout logics
You shouldn’t “test live” here, but first work with test orders and clear scenarios.
Place test orders
Before go-live, at least the following scenarios should be tested:
- D2C-Inland
- EU foreign countries
- B2B with tax exemption
- Returns
- Partial cancellations
- Vouchers
- Mixed goods baskets
- different payment methods
Refunds in particular often show very quickly whether the company logic has been implemented correctly.
Practice logic that determines costs and quality
Technical enablement alone does not yet deliver any operational advantage. What is decisive is the underlying process logic.
When several companies sell the same products, questions often arise such as:
- Which company bears the payment risks?
- Who processes chargebacks?
- Which unit is responsible for support?
- What prices apply?
- Which return address is displayed?
Reporting also becomes complex very quickly. Many teams only realize months later that revenues were segmented incorrectly or that payment data no longer matches ERP reports cleanly.
Another point is operational transparency. When the same order runs through multiple systems or entities, the effort required for checks and the potential for errors increase significantly.
The larger the shop, the more important the following become:
- clear responsibilities
- clearly defined markets
- stable data flows
- comprehensible export logic
Typical practical applications
International brand structure with local subsidiaries
A brand sells across Europe but uses different legal entities in each country. The frontend presence remains consistent, while tax and financial processes stay separated locally.
Separation of D2C and B2B
A company operates a shared Shopify stack but legally separates D2C and B2B sales through different legal entities.
This often becomes relevant for:
- different payment terms
- separate accounts
- own sales units
Corporate groups after acquisitions
After acquisitions, existing companies should initially be retained without immediately carrying out complete system migrations.
The new model can help here to represent transitional phases in a more technically precise way.
Segment recipes for organizational separation
Market segment by company
If customers from Germany place an order, then:
- German society
- German tax logic
- German payout account
For customers ordering from Austria:
- Austrian society
- Austrian invoice data
B2B segment
If customers have valid company information and a tax ID:
- B2B company
- net price logic
- separate payment terms
brand segment
If certain product lines are managed as legally separate entities:
- own company
- separate billing details
- own payment allocation
Text / template examples
Brief communication becomes especially important when legal changes are involved. Customers should not suddenly see different invoice details without any context.
Invoice change
“Your order will be processed by our German sales company. You can find details here: /rechtliches”
market transition
“For orders from Austria, local invoicing and payment information now applies.”
B2B notice
Business customers receive invoices through our B2B sales unit.
Note on character limits: Especially in checkout or in automated emails, messages should ideally stay under 120–150 characters so they remain fully visible on mobile.
When it makes sense – and when it doesn’t
The model is particularly useful when:
- several societies really exist
- a tax separation is necessary
- there are different payment flows
- markets are managed separately from an organizational standpoint
- ERP and accounting processes are prepared for this
It makes less sense when:
- companies are created only as a “precaution”
- operational processes are not documented
- Reporting is already unstable today
- Teams have no clear responsibilities
Many medium-sized shops underestimate the additional governance effort. More legal entities almost always mean more coordination.
Mistakes to avoid
Define company logic only after go-live
If legal and technical responsibilities are only clarified after the launch, this usually results in manual correction processes.
Not testing return processes
Refunds, partial cancellations, or payment reconciliations in particular quickly reveal weaknesses in the setup.
Underestimating ERP integration
Many problems don’t arise in the Shopify frontend, but rather in exports, accounting logic, and payment allocations.
Building too many special cases
If every region gets its own exception, the setup will become difficult to maintain in the long run.
Moving Primates Perspective
In projects involving multiple legal entities, we often see the same pattern: the technical structure is planned relatively early, but operational responsibilities are defined very late. This is exactly where problems later arise with returns, payment reconciliations, or ERP exports. It becomes especially critical when the same brand is simultaneously serving D2C, B2B, and international markets. Our experience: the more simply the entity logic can be formulated, the more stable the setup remains in the long term. In most cases, it makes sense to have one clear rule per market or sales model instead of many individual special cases. Test orders for refunds, partial cancellations, and tax scenarios in particular should be mandatory before go-live.
Technical implications for larger shops
Larger Shopify setups should not look at this feature in isolation.
Often affected at the same time are:
- ERP systems
- Tax tools
- Invoicing services
- OMS/PIM systems
- BI and reporting layer
- Fraud and Risk Management
Particularly important are stable identifiers. Every order should be clearly traceable and assignable to a specific company.
Governance is also becoming more relevant:
- Who is allowed to change company rules?
- Who checks payment flows?
- Which test cases are mandatory?
- How are changes documented?
For enterprise setups, it is also advisable to use a separate staging or testing process with clearly defined test scenarios.
10-point checklist before go-live
- Societies and markets documented
- Tax data checked
- Payout accounts tested
- Invoice logic validated
- ERP exports checked
- Returns tested
- Partial cancellations tested
- B2B cases reviewed
- Payment methods tested
- Responsibilities documented
FAQ
How much does the feature cost?
As of today, this depends on the Shopify plan, Shopify Payments, and the respective market or company structures. For this, Shopify refers to the official documentation and individual availability details.
Do I need Shopify Plus?
For more complex multi-entity setups, Shopify Plus often becomes relevant. Which specific features are available should always be checked against the current Shopify documentation.
Can I manage multiple limited liability companies (GmbHs) in one shop?
According to Shopify, this exact type of scenario is part of the new range of features. However, how far the separation goes in technical and organizational terms depends on the individual setup.
Is this a replacement for an ERP system?
No. The feature supports payment and organizational logic within Shopify, but it does not replace a full financial or ERP structure.
When is that unsuitable?
When a company has no clear market, tax, or corporate logic. In such cases, operational complexity often increases more than the actual benefit.
Which data do I need in advance?
At least:
- Company data
- Tax information
- Bank account details
- Market definitions
- ERP mappings
- clear process responsibilities
Summary in bullet points
- Shopify expands Shopify Payments for multiple legal entities within the same country
- Especially relevant for international D2C, B2B, and multi-brand setups
- This feature does not replace an ERP or accounting solution
- Sound market and social logic is crucial
- Returns and refunds must be explicitly tested
- ERP and reporting processes are becoming more important
- More companies mean more governance effort
- Clear responsibilities reduce operational errors
- Simple rules are more stable in the long run than many special cases.
- Test orders before go-live are mandatory
- Particularly important are consistent data flows and clear order assignments.
List of links
Shopify Changelog – Multiple legal entities with Shopify Payments
Shopify Changelog – Sell from multiple legal entities in the same country using Shopify Payments
Official feature announcement in the Shopify changelog.
Shopify Help Center
Shopify Help Center
Documentation on Shopify Payments, Markets, taxes, and international setups.
Shopify Developer Documentation
Shopify.dev Documentation
Technical documentation on APIs, payments, markets, and enterprise integrations.
