Sell Globally (Multi-Country Shops)
Use Case Description
Some tenants find that in specific markets, it's not efficient to have a dedicated shop setup. This is often because the profits in these areas are lower compared to their main markets. Recognizing this, SCAYLE introduces a more streamlined approach: combining these markets into a single regional shop that shares settings, including language and shop preferences.
What are “multi-country” shops in SCAYLE?
Think of a muli-country shop as an e-commerce platform designed to operate on a global level, configured for particular markets like the EU. Instead of setting up separate shops for each delivery country, SCAYLE allows you to group them into one multi-country shop. Here, countries share key settings like, language, currency, payment methods, product range and delivery partners. It's SCAYLE's smart way of simplifying the way businesses serve multiple countries.
Currently, SCAYLE offers two multi-country shops:
Europe
- ISO custom country code AA
Global
- ISO custom country code ZZ
SCAYLE’s flexibility doesn’t stop there. If a tenant has a specific requirement, and it aligns with legal constraints, you can expand an existing shop by adding more billing and shipping countries. This transforms it into a multi-country shop. For example, if you add France, Netherlands, and Luxembourg to a Belgium Shop, these countries will adopt the settings of the original country shop (e.g BEL.)
Shared configurations in a multi-country shop
In SCAYLE's multi-country shop setup, you have the flexibility to define both billing and shipping countries. But what do these countries share when bundled under one shop setup? Here’s a breakdown:
Topic | Shared? | Comment |
---|---|---|
Product data (attributes, translations, custom data, prices) | YES | - You can only select one language, so translations are consistent. - Pricing structures must exist - Prices apply to all delivery countries. - A single tax rate is required. |
Shop categories and custom data (shared tree) | YES | The shop category tree, its translations and activation state are the same across all countries. |
Shop assortment | YES | Assortment settings apply to all delivery countries. |
Search settings | YES | |
Checkout (configurations and translations) | YES | Shop-specific configurations like dynamic fields, gift cards and translations etc. are shared. Address fields can vary and be set per delivery country. |
Carrier | YES | |
Shipping options | YES | Use the rule engine to set shipping options and costs for each country. |
Payment configurations | YES | Payment methods and their order is shared across countries. |
Delivery estimations in checkout | YES | |
Transactional mail stylings and translations | YES | |
CMS content | YES |
SCAYLE setup guide
Process flow
Step 1: Setting up the shop country
- Start by defining your regional shop’s delivery destinations.
- Create a shop country, like an EU shop delivering across Europe.
Step 2: Defining the shipping and billing countries
- Choose the shipping countries for the EU shop checkout.
- Define the billing countries to display in the EU shop checkout.
- Multi-country shops typically have shared settings. It’s common to either set up an EU shop or a global shop.
- Combining an EU shop (with a single tax rate) and a non-EU shop (displaying net prices) can serve a lot of use cases.
- AA is a common code for European shops, and ZZ for global ones.
- Use the country code in the config.json to update country specific settings (like links to terms and conditions.)
- Ensure all payment methods in the regional shop are accessible across all countries. You should avoid overcomplicating the rule engine with complex payment rules that can impact the CO response time. Plan and test your rule setup carefully.
- Different shipping costs? Use the rule engine alongside shipping options.
- Create one shipping option for each shipping cost.
- For each shipping cost, create a rule applied to a group of shipping countries. Ensure only the right shipping option for the specific delivery countries remains active, deactivating all others.
Best Practices
- Country code: AA
- Language Code: en
- Currency: €
- shop domain:
test-shop.eu/
- checkout domain:
checkout.test-shop.eu/
- Example: Tom Tailor EU
Europe Shop
- Country code: ZZ
- Language Code: en
- Currency: $
- Shop domain:
test-shop.com
- Checkout domain:
checkout.test-shop.com
- Example: About You Global
Global Shop
Example multi-country shop configurations: Europe and global shops
The remaining steps follow the usual shop configuration process.