Expanding from Australia into New Zealand creates an immediate technology question: should you add a New Zealand market to your existing online store, or launch a separate website?
A separate domain can look like the obvious way to establish a local presence. But the more important decisions sit behind the screen: who owns the stock, which business accepts the order, how prices are maintained and who handles delivery and returns.
OSE’s recommended starting point is to test whether your existing platform can support the required New Zealand experience. Create a separate commerce environment when the operating model needs meaningful independence—not simply because customers are across the Tasman.
This guide helps Australian retailers, wholesalers and commerce teams compare the options, including what changes when you add local stock, a New Zealand team or separate business processes.
The short answer: share where you can, separate where you need to
An extension of your existing store is usually the first option to assess when both markets share a brand, broadly similar products, central management and compatible fulfilment rules. You can still create a recognisably New Zealand experience through local pricing, market-specific content and an appropriate URL structure.
A separate store becomes more compelling when New Zealand needs independent merchandising, a substantially different catalogue, distinct customer relationships or integrations that cannot be managed cleanly within the shared environment.
Neither approach removes the need to resolve tax, payments, stock and support. Those requirements must work end to end, whichever storefront architecture you choose.
Separate the customer experience from the technology underneath
There are three practical patterns worth comparing.
1. One store with a New Zealand market
The existing commerce environment serves both countries, with selected settings and content adapted for New Zealand customers. Product information, administration and integrations can remain centralised where the platform supports it.
This can suit an initial launch with Australian fulfilment and a shared trading model. It also reduces the number of separate environments the team must maintain. The risk is assuming that a currency selector alone constitutes a complete market launch.
2. Separate storefronts on a shared platform
Customers see distinct regional sites, while the business shares part of the underlying platform and administration. This can provide more market separation without duplicating every technical component.
The exact boundaries matter. Confirm what is shared, what can vary and which changes affect both countries. Two domains do not necessarily mean two separate commerce systems.
3. Independent stores with connected business systems
Australia and New Zealand operate separate commerce environments. They may still share an ERP, product information system or integration service, but those connections must deliberately keep the required data aligned.
This supports greater independence, with additional responsibility for configuration, testing and synchronisation. For a broader platform comparison, see our guide to Shopify Plus and Adobe Commerce for multi-store retailers.
Start with the operating model
Before choosing a platform configuration, write down how a New Zealand order will move through the business. Start at product discovery and continue through payment, warehouse allocation, delivery, refund and financial reconciliation.
Ask five questions:
- Will orders ship from Australia, New Zealand or both?
- Which entity sells to the customer and receives payment?
- Will the same team manage pricing, promotions and customer service?
- Do both markets sell the same products, with the same stock definitions?
- Which system owns each piece of information, and where must it be reconciled?
For example, a brand testing demand with Australian inventory may need a localised buying experience but little organisational separation. A distributor with a New Zealand warehouse, account customers and local sales team may need different price lists, credit processes and fulfilment rules. These are illustrative scenarios, not OSE customer case studies.
The decision should follow those differences. A second store is justified when it makes the business easier to operate reliably, rather than when it merely looks more local.
What changes for the New Zealand customer?
Pricing and payment
Decide whether New Zealand prices are converted from Australian prices or managed as a deliberate local price list. Exchange rates are only one input: delivery cost, returns, competitor positioning and margin also influence the offer.
Specify what the customer sees on product pages, in the cart, at checkout and in confirmation emails. Test payment, settlement, refunds and reporting in the intended currencies. A local display price does not by itself prove that the financial workflow is correct.
Product range and merchandising
Identify products that should not be offered in New Zealand because of shipping restrictions, supply agreements, service limitations or unsuitable delivery economics. A market-specific range is often more manageable than launching the entire Australian catalogue.
Decide who owns local promotions and product content. If the same team updates both countries, shared management may help. If the teams regularly need different launch dates and campaigns, assess whether the platform can provide that independence without workarounds.
Delivery and returns
Publish delivery promises based on the actual dispatch location, service and destination. Confirm how rural addresses, bulky products, split shipments and failed deliveries are handled. Avoid implying local fulfilment when orders are dispatched from Australia.
Design the return journey before launch: where customers send goods, who authorises the return, how refunds are processed and when returned stock becomes available. Our eCommerce shipping guide and returns portal and RMA guide explain the wider operational considerations.
Tax and customer obligations
Do not copy the Australian tax configuration into a New Zealand market without checking the trading arrangement. Inland Revenue distinguishes between low-value goods sold from overseas and goods already held in New Zealand. That distinction can affect which GST rules apply. Have the proposed flow reviewed by your tax adviser before configuring it.
Customer-facing claims also need care. New Zealand Consumer Protection explains that the Fair Trading Act covers overseas businesses supplying into New Zealand. Ensure descriptions of prices, availability and delivery reflect the actual service. Treat legal and tax review as launch inputs, rather than assuming a new domain resolves them.
Local stock changes the integration requirements
Adding a New Zealand warehouse can improve the delivery proposition, but it also changes what “available” means. Stock held in Australia may not be immediately available to a New Zealand customer. Conversely, New Zealand stock might be reserved for local orders rather than exposed to every sales channel.
The integration design should identify:
- The market and selling entity on every order.
- The stock locations eligible to fulfil that order.
- How reservations and safety stock affect online availability.
- Which price list and tax treatment apply.
- How cancellations, refunds and returns reach the ERP and warehouse.
- Who investigates failed transactions and reconciles differences.
A separate website will not resolve ambiguous inventory ownership. A shared website will not remove the need for market-aware data. Both approaches depend on explicit rules and reliable connections.
Our article on connecting your online store, warehouse and ERP explains why physical quantities, reservations and saleable stock must be distinguished. Use that discipline when defining which products New Zealand customers can actually buy.
How Shopify and Adobe Commerce approach the choice
Shopify: assess Markets before adding another store
Shopify’s international sales tools support managing multiple markets from one store. Shopify also identifies independently managed regional operations as a reason to consider multiple stores.
For a New Zealand launch, document the specific pricing, product, content, payment and operational differences, then test them against the current plan and configuration. Avoid deciding from a feature name alone. Where a separate store is needed, include the work required to coordinate products, orders, applications and reporting in the comparison.
Adobe Commerce: define the right scope
Adobe Commerce and Magento Open Source use a hierarchy of websites, stores and store views. These levels control different configuration and catalogue boundaries. A shared installation can support multiple customer-facing experiences, but the intended separation must be mapped to the right scope.
For New Zealand, have the implementation team confirm the configuration needed for catalogue, pricing, checkout, customer data and integration routing. Verify capabilities for the exact Adobe product and deployment model under consideration; do not assume every Adobe commerce offering has identical architecture.
If expansion exposes wider platform limitations, our eCommerce replatforming guide can help assess the broader decision. Entering another market alone is not a sufficient reason to replace a platform that can meet the requirements.
A New Zealand domain does not require a separate store
Choose the URL structure alongside the customer and search strategy. A regional domain, subdomain or subfolder can make the market distinction visible, but it does not independently determine how many commerce environments you need.
Where you create separate regional pages, plan how customers and search engines find the appropriate version. Google documents hreflang annotations for language and regional variants. Include regional page relationships, indexability and canonical behaviour in implementation testing rather than simply duplicating the Australian site.
Also test market switching. A customer following a product link should be able to find the relevant New Zealand offer without losing their place or encountering a product that cannot ship to them.
Compare the full cost of both options
A shared store may reduce duplicated administration, but it can become expensive if the team must continually work around incompatible requirements. Independent stores may simplify local control while adding maintenance and integration costs.
Compare the same scope over the same planning period. Include platform and application fees, development, integration changes, testing, content management, monitoring, customer service and reporting. Add the time spent maintaining product data or reconciling orders manually.
Use an explicit margin model: net revenue less product cost, payment fees, fulfilment, delivery subsidy and expected returns and service costs. Model Australian dispatch and local fulfilment separately. An architecture that launches cheaply can still be difficult to operate profitably.
A practical launch sequence
1. Define a focused launch. Choose the customer group, product range, fulfilment model and commercial measures. Establish what would justify further investment.
2. Map the operational differences. Record market requirements, system ownership and decision-makers. Resolve tax, payments and customer-service responsibilities before development.
3. Test the shared-store option. Demonstrate the required New Zealand journey in the existing platform. Record any gaps and the consequences of addressing them.
4. Compare separation against those gaps. Assess a second storefront or independent store where it solves a demonstrated problem. Include ongoing coordination costs.
5. Rehearse complete transactions. Test normal orders, unavailable stock, rural delivery, mixed baskets, failed payments, cancellations and returns. Follow the transaction through to the ERP and financial records.
6. Launch with monitoring and review points. Track conversion, contribution margin, delivery exceptions, support demand and manual intervention. Use the results to decide what to improve or separate next.
Frequently asked questions about selling into New Zealand
Not necessarily. Start by checking whether your existing platform can provide the required New Zealand pricing, product range, delivery options and content. A separate store is worth considering when local teams, business processes or integrations need more independence than the shared setup can support.
Yes, provided your products, shipping arrangements and customer promises support that model. Confirm delivery charges, realistic delivery times, returns handling and applicable tax requirements before launch. You can assess local fulfilment later using actual demand, delivery performance and contribution margin.
Shopify provides international sales tools for managing multiple markets from one store. The right setup depends on your plan, payment configuration and required market differences. Test New Zealand pricing, product availability, checkout, refunds and reporting before deciding whether a separate store is necessary.
The integration must distinguish the market, selling entity, applicable pricing and eligible fulfilment locations for each order. If you add local inventory, define reservations, stock allocations, returns and reconciliation rules. Give staff a clear process for identifying and resolving failed transactions.
It can reduce duplicated setup and administration, but the full cost depends on your requirements. Compare platform and application fees, development, integrations, testing, content management and ongoing support. Include manual work and the cost of maintaining exceptions when assessing the shared-store option.
Which approach should you choose?
Assess an extension first when the brand, team, catalogue and operating model are largely shared and your platform can provide the required local experience. This can be a disciplined way to test New Zealand demand.
Assess a separate storefront or store when local teams, business rules or system boundaries need independence that the shared model cannot provide cleanly. Be specific about what the separation solves.
The strongest architecture is the one that lets your team make a clear customer promise and fulfil it consistently. Local pricing and presentation matter, but reliable stock, payment, delivery and support processes make the experience credible.
If you are planning expansion between Australia and New Zealand, speak with OSE about your commerce architecture and integration requirements. Start with the operating model, compare the viable options and build a launch plan that can grow with the business.