AURORA CROSS – selling on multiple markets in Magento 2
Open your Magento 2 store to another market, without building a second store from scratch.
AURORA CROSS uses the Magento Multistore architecture to launch further markets, language versions and local sales configurations inside one Magento 2 platform. For a fixed price.
- Magento 2
- market version
- currency and taxes
- payments
- deliveries
- translations
- 2 weeks
A new market only works once the whole sales process works
The customer has to see the right offer and price, pay with a local method and pick a delivery option, and their order has to reach the ERP, the warehouse and customer service correctly. That is why AURORA CROSS covers more than setting a language and a currency.
Offer and prices
We decide which products are to be available in the new market, and at what prices, in which currencies and under which promotion rules. We also configure the approved tax rules and the way prices are presented.
- local assortment
- currencies and price lists
- taxes and promotions
Purchase and payments
We adapt the checkout to the local language, addresses and way of buying. We connect the agreed payment methods and test the whole process, from adding a product to paying for the order.
- local checkout
- payment methods
- transactional messages
Delivery and returns
We configure carriers, pickup points, delivery costs and shipment statuses. We also prepare the technical data flow needed to handle returns and complaints.
- carriers and pickup points
- labels and shipment statuses
- returns and complaints
Data and support
We fit the new market into the company's current processes. Products, prices, stock levels, orders and statuses have to flow correctly between Magento 2, the ERP, the PIM, the WMS and the CRM.
- ERP, PIM, WMS and CRM
- one source of order data
- customer-service tools
Scope boundary
The client or their advisers define the local legal, tax and terms-and-conditions requirements. Aurora Creation translates the approved rules into Magento 2 configuration, integrations and the sales process.
Before the start, the store's and the operation's readiness has to be checked
We review the store's architecture, code, modules, integrations, data and the way orders are handled. The result says which elements are ready, which need a decision, and which have to change before selling starts.
Check your readiness to expand- Magento version and how it is maintained
- modules in use and customisations
- current architecture of websites, stores and store views
- quality of documentation
- limitations of the current hosting
- shared or local assortment
- source of descriptions and translations
- differing attributes, units or variants
- how data is fed from a PIM or an ERP
- currency
- price list
- promotion rules
- approved tax requirements
- how data reaches the accounting system
- local payment methods
- address format
- order of the purchase steps
- required consents and messages
- handling of declined payments and refunds
- carriers
- pickup points
- delivery time and cost
- labels
- shipment statuses
- returns and complaints
- ERP
- PIM
- WMS
- CRM
- carrier systems
- customer-service tools
- reporting
- domain or URL structure
- language versions
- hreflang
- indexing
- consents and analytics
- separating data between markets
Magento Multistore — multiple markets in one Magento 2 architecture
One store, a shared core, separate rules for every market. Another market uses the shared code, catalogue, integrations and mechanisms of a store that already runs, so the company does not have to maintain a separate platform for every country.
What depends on the market is configured separately: language, domain, currency, offer, prices, taxes, checkout, payments, deliveries, content and communication with the customer.
Before the work starts we agree what stays shared and what has to be managed locally. That decision drives the cost of further development, how quickly changes can be made and how easy the platform is to maintain.
The architecture is approved before configuration and development begin. A new market is built as part of one system, not as a set of exceptions added on top of the store.
Shared core
- the same code
- one catalogue
- the same integrations
- one admin panel
Magento 2
Market versions
Poland
- Polish
- prices in PLN
- 23% VAT
- BLIK and card
- InPost and DPD
Germany
- German
- prices in EUR
- 19% VAT
- Klarna and card
- DHL and Hermes
Czechia
- Czech
- prices in CZK
- 21% VAT
- card and transfer
- PPL and Packeta
Company systems
- ERP
- PIM
- WMS
- CRM
- carriers
- analytics
Website, Store and Store View in Magento 2 — how we organise different markets
Magento 2 has three configuration levels, one inside the other. Which level a new country sits on decides what that country has of its own and what it shares with the rest of the store.
Website
The level that separates selling
- payment and delivery methods
- currency and price scope, when they are to be run separately
- how prices and taxes are presented
- which products are assigned for sale
- customer accounts, when they are to be kept apart
- a domain of its own
Store
The level that separates the catalogue
- the root category, meaning the structure of the catalogue
- the range of products visible on the market
- the default market version inside the group
Store View
The level that separates presentation
- interface language and translations
- content, CMS blocks and transactional messages
- product names and descriptions in the market version
- the address the market version runs under
Another country does not always need a website of its own. If it sells the same range and uses the same payment and delivery methods, while the language, the content and the address change, a new store view inside the current structure is enough. That is the standard scope of AURORA CROSS.
We set up a separate website when a market is to have its own payment and delivery methods, its own prices, a different range of products or customer accounts kept apart. It is still one Magento 2 instance and one admin panel — what changes is the level the configuration is separated on, not the number of platforms. The decision is made before configuration, because moving a market up a level after launch means setting prices, payments and customer data again.
Adding another market to Magento 2 for PLN 8,000 net
AURORA CROSS has a fixed scope and a fixed price. Within 2 weeks we prepare another market version of a running Magento 2 store, on the basis of its current theme and architecture.
A new market version in Magento 2
- creating another language version or store view,
- connecting the store's current theme,
- language configuration,
- domain configuration,
- placing the new market version in the Magento 2 structure.
The new market is launched in the existing Magento 2 environment. It uses the store's current code, look and mechanisms, so it needs no separate platform.
Currency, taxes and sales settings
- currency configuration,
- configuration of the tax rates provided,
- basic sales settings,
- setting how prices are presented,
- assigning the configuration to the new market version.
We implement the rules approved by the client or their tax adviser. Aurora Creation is responsible for configuring them in Magento 2.
Baseline configuration of payments and deliveries
- assigning the available payment methods,
- basic configuration of the payment provider,
- assigning the delivery methods,
- basic configuration of the carriers,
- setting which methods are available in the new market.
We agree the data flow before a market goes live. Support, the warehouse and the customer should all receive consistent information about the order, the payment, the shipment and the return.
Translations and getting ready to launch
- preparing the files for translation,
- handing the files over to the client,
- importing the delivered translations into Magento 2,
- verifying the market version's configuration,
- preparing the market for publication.
The scope of testing follows from the market's configuration. The list of scenarios should be accepted before the launch, so the team knows which processes have been checked.
A new market version in Magento 2
- creating another language version or store view,
- connecting the store's current theme,
- language configuration,
- domain configuration,
- placing the new market version in the Magento 2 structure.
The new market is launched in the existing Magento 2 environment. It uses the store's current code, look and mechanisms, so it needs no separate platform.
Currency, taxes and sales settings
- currency configuration,
- configuration of the tax rates provided,
- basic sales settings,
- setting how prices are presented,
- assigning the configuration to the new market version.
We implement the rules approved by the client or their tax adviser. Aurora Creation is responsible for configuring them in Magento 2.
Baseline configuration of payments and deliveries
- assigning the available payment methods,
- basic configuration of the payment provider,
- assigning the delivery methods,
- basic configuration of the carriers,
- setting which methods are available in the new market.
We agree the data flow before a market goes live. Support, the warehouse and the customer should all receive consistent information about the order, the payment, the shipment and the return.
Translations and getting ready to launch
- preparing the files for translation,
- handing the files over to the client,
- importing the delivered translations into Magento 2,
- verifying the market version's configuration,
- preparing the market for publication.
The scope of testing follows from the market's configuration. The list of scenarios should be accepted before the launch, so the team knows which processes have been checked.
If the current platform will not handle the planned complexity, the right starting point may be a new platform delivered in the AURORA ONE model.
PLN 8,000 net per market
The price covers the full standard scope of AURORA CROSS. Before we start, the only thing we confirm is whether the current Magento 2 meets the conditions the service needs.
Custom integrations, new modules, theme changes and bespoke processes are not part of the fixed scope. We can quote them separately before the work begins.
A new market goes live in 2 weeks
AURORA CROSS needs no separate analysis project. We work to a fixed process, provided the current store meets the entry requirements and the client supplies the data and content needed.
- 01
Readiness confirmed
We check the Magento 2 version, the store's structure, its current theme and the availability of the payment and delivery modules the new market needs.
- 02
Configuration data
The client provides the domain, the language, the currency, the approved tax rules and the details of payments and deliveries.
- 03
Market version created
We add the new language version or store view, connect the current theme and configure the domain and the language.
- 04
Sales configuration
We set the currency, the taxes, the basic sales rules and the available payment and delivery methods.
- 05
Translations and verification
We prepare the files for translation, import the content delivered and check that the new market version is configured correctly.
- 06
Market launch
We publish the finished market version once the client has approved the configuration and the content.
Condition of delivery at the fixed price of PLN 8,000 net
The scope has to fit within the AURORA CROSS standard. If launching the market requires a new integration, a theme modification or a bespoke sales process, we will quote that work separately before delivery begins.
30 store views. 12 languages. One Magento 2.
Diablo Chairs runs D2C sales across many markets from a single Magento 2 environment. The platform covers 30 store views, 12 language versions and separate sites for the Kido and Brave brands.
- Sales model
- D2C sales run in parallel across many international markets, together with separate sites for the group's brands.
- Scope
- Delivery of a Magento 2 platform serving market, language and brand versions within one architecture.
- Architecture
- One Magento 2 instance covering 30 store views and 12 language versions.
- Operational effect
- Each additional market version uses the shared code, integrations and admin panel instead of a separate platform per country.
- 30store views
- 12language versions
- 1Magento 2 instance
See how we designed a Magento 2 architecture for managing many markets and brands.
See the Diablo Chairs case studyThe fixed price works when the new market fits the fixed scope
AURORA CROSS for PLN 8,000 net
- the store already runs on Magento 2
- the new market uses the current theme
- another language version or store view is what is needed
- the client supplies approved tax requirements
- the translations will be delivered by the client
- the payments and deliveries needed are supported by the current modules
- no new integrations or bespoke processes are required
A separate quote will be needed
- the current Magento 2 architecture has to be rebuilt
- the new market requires changes to the look or the checkout
- a new payment provider or carrier has to be implemented
- a new integration with an ERP, PIM, WMS or CRM is needed
- the sales process differs from the store's current model
- bespoke pricing or tax rules are required
- the current store has to be updated or stabilised first
Before we start, we confirm free of charge whether the planned market fits within the fixed scope of AURORA CROSS. If extra work is needed, you will know its scope and cost before you decide.
See the frequently asked questionsFAQ — Magento 2 on multiple markets
The Magento Multistore architecture, and the fixed scope, price and conditions for adding another market to Magento 2.
Let's discuss your plan for entering a new marketAURORA CROSS is a service for adding another market to an existing Magento 2 store. It covers creating a language version or store view and its standard technical configuration.
Magento Multistore is the architecture in which one Magento 2 installation serves many stores, markets and language versions. They all share the same code, catalogue, integrations and admin panel, and differ in their configuration at website, store and store view level. AURORA CROSS uses that architecture to launch further markets.
The website is the top level: it separates payment and delivery methods, prices, product assignment and — if we decide so — customer accounts. The store below it owns the catalogue, meaning the root category and the range of products. The store view is the presentation level: language, translations, content and the address of the market version. We place a new country at the level where it genuinely differs from the rest of the store.
AURORA CROSS costs PLN 8,000 net per market. It is a fixed price covering the whole standard scope of the service.
The price covers creating a language version or store view, connecting the current theme, configuring the language, the domain, the currency, taxes and basic sales settings, preparing the files for translation, importing the translations delivered and the baseline configuration of payments and deliveries.
The standard delivery time is 2 weeks from the moment we receive the complete data, access, requirements and content needed for the configuration.
Yes. The domain is assigned to the market version, and the currency and prices can be run separately as long as the price scope in Magento 2 is set at website level. AURORA CROSS covers configuring the domain, the currency and the tax rates provided; pricing rules beyond the standard configuration are quoted separately.
Yes. Payments and deliveries are configured at website level, so every market can have its own set — BLIK and InPost in Poland, Klarna and DHL in Germany. The fixed scope covers assigning and setting up the methods handled by modules already installed in the store. Implementing a new payment provider or carrier is quoted separately.
We prepare the files intended for translation and import the content delivered into Magento 2. Producing and approving the translations themselves stays with the client.
No. The fixed scope covers configuring the store's existing mechanisms and modules. New integrations, modules and bespoke processes are quoted separately before the work begins.
Yes. A separate brand runs as its own website, with its own domain, catalogue and sales configuration, inside the same Magento 2 instance. That is how Diablo Chairs works, where the main store stands beside separate sites for the Kido and Brave brands.
Magento 2 sets no practical limit here — what limits it is the performance of the infrastructure and how far the markets differ from one another. Diablo Chairs runs 30 store versions and 12 language versions on one Magento 2 instance.
The client or their advisers define and approve the tax, legal and terms-and-conditions requirements. Aurora Creation is responsible for implementing the rules provided in Magento 2.
Before we start we check the Magento 2 version, the store's structure, its current theme and the modules available. If a rebuild or an update is needed first, we present the scope of that work separately.
No Magento 2 yet? Look at delivering a new store in the AURORA ONE model.
Let's check what has to be ready before you enter a market
On the first call we go through the current platform, the planned countries, the order process and the integrations. After the call we'll say whether AURORA CROSS fits the situation and what data is needed to prepare a scope.
What to expect after sending your enquiry
- 1Contact within 1 business day and follow-up questions about the platform and the planned markets.
- 2A conversation about the current architecture, the order process and the integrations.
- 3An answer on whether AURORA CROSS fits the situation and what data is needed to prepare a scope.