Four things should be decided before the first market is built: whether one store with Shopify Markets is enough or each region needs its own store, which domains and languages you use, which system owns prices and inventory, and how tax is handled per country. Germany and Austria share the euro and EU rules. Switzerland sits outside the EU and needs its own currency, tax and customs handling.
MYCR7 shows what that means in practice. The operator of the official CR7 online stores sold through physical retail and marketplaces and had no shop system of its own. We built mycr7.eu and mycr7.ch on Shopify Plus, with separate price lists and a checkout in CHF for Switzerland, and connected the client's proprietary ERP and warehouse system. The MYCR7 case study reports go-live after 6 weeks and revenue 120% above the level from retail and marketplaces.
Our page on Shopify internationalisation covers the build. The consulting work settles the structure first.
One store is enough while range, warehouse and team are the same across countries. Several stores make sense when markets have their own range, their own stock or their own teams. The question behind it is always the same: how much duplicated operation can your team carry.
Groundies, a barefoot shoe brand with eight-figure revenue, carried too much of it. The brand ran OXID for the US and Shopware for its international markets, with duplicated operations and long lead times for new storefronts and campaigns. The decision was one central Shopify Plus codebase and a staged launch, the US first and the international store 60 days later. According to the Groundies case study, consolidating the two platforms reduced costs by 50%.
Whether the enterprise plan is needed for your structure is a calculation of licence, apps, development and operations. We describe it on the Shopify Plus agency page.
Each data object needs exactly one owner. If an ERP or PIM already holds product master data, prices and stock, the store should read from it and write back only what originates in the store, such as orders and customers.
Hairshop Pro, a retailer for professional hair care, worked on Plentymarkets, and the system slowed down maintenance, campaigns and conversion work. The decision was to keep Plentymarkets as the PIM and place Shopify Plus in front of it as the storefront. An interface synchronises product master data, inventory, prices, orders and fulfilment status. The Hairshop Pro case study reports a 35% higher conversion rate and a 20% higher average order value from bundles and cart upsells after launch.
How the connection is built is described on the Shopify ERP integration page.
A roadmap exists once every item has a goal, an effort and a dependency. We separate what limits your growth from what is merely annoying in daily work. The first group goes to the top.
SMILODOX wanted to bring B2C and B2B onto one maintainable foundation. The work began with a review of the existing store, the customer journeys and the app stack.
An app audit assessed value and overlap, and a shared target picture defined which functions both sales channels really need. Only then were core pages and requirements prioritised. The SMILODOX case study describes the path from that analysis to go-live after two months.
Migrate when range, customer data and rankings should keep their value and the old system mainly costs maintenance.
Rebuild when the business model changes or the brand has never had a store of its own, as in the MYCR7 project.
For existing stores the migration audit establishes what is carried over, what is created new and which redirects are required. The Shopify migration page describes the move itself.
Shopify is the wrong platform when pricing, quotas or order logic form the core of the business and cannot be handed to another system. It is also a poor fit for products that are configured from thousands of valid combinations, and for industries with verification duties inside the purchase process.
If we reach that conclusion, it is written in the result. The platform comparison shows how Shopify performs against other systems.
NICCOS has been a Shopify Plus Partner since April 2022 and is an OpenAI partner. Our entry in the Shopify Partner Directory shows 19 reviews with a rating of 5.0. The experience we draw on is documented in 13 published case studies. The senior people from consulting and architecture stay responsible during the build and work closely with the delivery team.
We keep consulting and quoting apart. A quote describes what we would build. Consulting settles beforehand whether and what should be built, and its result can be used without us.
We assess Shopify, Shopify Plus and your current platform with an open outcome. Licence, apps, development, integrations and operations are compared over the same period.
We define how many stores your business needs and which system owns products, prices, inventory, customers and orders.
Market order, domains, languages, payment methods and tax are settled first. Every item on the roadmap gets a goal, an effort and a dependency.
Order, payment, shipping and returns run in the usual way. You do not pay to build basic functions yourself.
Markets, currencies, languages and local payment methods are platform functions and do not have to be developed.
Hosting, scaling and security sit with Shopify. Your team works on the store and not on infrastructure.
When a market, brand or channel has to be live soon, the platform standard is the shorter route.
Pricing, quotas or order logic form the core of the business and cannot be handed to another system.
Products arise from thousands of valid combinations and do not fit a model of products and variants.
Industries with proof or approval duties reach the limits of what the checkout allows.
If selling is only one part of a software product or platform, a connected storefront is often enough.
We record store, systems, data and processes. The result is a written finding that management and IT can both read.
We separate what limits your growth from what is annoying in daily work. Only the first group goes to the top of the roadmap.
For every open question we describe the viable routes with effort, risk, running costs and what the decision rules out later.
The decisions are made in a workshop with your team. We moderate and contribute experience from comparable setups. The decision is yours.
The decisions become an order of work with dependencies. Every item gets a goal it will be measured against.
On request we stay on as a sparring partner for technical reviews, tenders and decisions during operations, whoever builds.
Fits when you want to know where your store stands and what is really holding it back. Ends with prioritised findings.
Fits when the options are known and a decision has to be made. Ends with recorded decisions.
Fits when you need technical sparring over time without building an architecture team of your own.
Fits when a quote, an architecture or a platform recommendation should be checked from outside.
Several routes are plausible
Two or three viable options are on the table and your team does not agree on which one holds.
The decision is hard to reverse
Platform, domain structure and data model can later only be corrected through migration, redirects or duplicated maintenance.
The wish list is longer than the budget
There are more projects than capacity, and the order follows the loudest voice instead of the expected effect.
The last relaunch did not deliver
The store works technically, the expected effect did not arrive, and an independent assessment is missing.
The decision has been made
If platform, scope and order are settled, another analysis only costs time before the build starts.
To Shopify developmentThe question can be measured
Whether load time and Core Web Vitals are good enough is answered more precisely by measuring real user data than by a workshop.
To Shopify performanceIt is about the change of platform itself
If the only question is whether and how an existing store moves to Shopify, there is a separate entry point for that.
To the migration auditThe format depends on whether you need findings, a decision or sparring over time.
For merchants who want to know where their store and system landscape stand.
Ends with a written finding that management and IT can read.
For teams that have to choose between known options and cannot settle it internally.
Ends with recorded decisions and a roadmap your team carries forward.
For merchants who want technical decisions checked during operations.
Ends when your team carries the decisions itself or the build has been handed over.
Every figure appears in the case study, where you can verify it.
Groundies, MYCR7 and Gusti Leder are three of thirteen projects we have published with starting point, delivery and result.
Tell us where you are stuck. We will tell you whether an audit, a workshop or a second opinion answers the question.
NICCOS
The page could not be loaded.
Please reload the page. If an update has just gone live, this will load the latest version.
