Online store migration for a new country: how to prove it is necessary
A store is preparing to sell in another country, but a test order offers a shipping option that cannot be used to send the product. The contractor recommends a new platform; the operations team suggests another module. Online store migration is needed not simply because the business is entering a new market, but when a confirmed limitation of the current system prevents an agreed business operation from being carried out in an acceptable way.
First, establish where the process breaks down, whether the settings can be corrected, and what custom development would change. Below is a way to make a decision based on a specific order, rather than a promise that “the platform supports international sales”.
When online store migration really is needed for a new country
The basis for migration is a mandatory operation that the current implementation cannot support through available settings or a controlled extension. At the same time, the target system must demonstrate that it removes this particular limitation. Otherwise, the business moves an unresolved problem along with its products and orders.
A new country does not in itself prove that the platform is unsuitable. For example, Shopify’s official documentation describes managing international markets from a single store. This is an example of a possible approach, not confirmation that all payment methods, shipping options or features are available to every account. You need to check your store, your agreement with the service provider and the operation you require.
Separate market adaptation from the decision to rebuild. The article on localisation and entering foreign markets covers the broader preparations. The question here is narrower: does a specific failure require changing the store’s already functioning foundation?
How to turn a complaint into a verifiable blocker
A blocker should be described as a discrepancy between the expected and actual result of a single operation. “There is no proper shipping to Poland” is not enough for a cost estimate. You need the cart contents, address, shipping conditions and the point at which the system behaves incorrectly.
Prepare an operational blocker record that both the manager and the developer can understand. It should distinguish a business requirement from an assumption about the technical solution. “The customer must not see an unsuitable shipping option for this product” is a requirement; “this needs a different CMS” is a hypothesis.
- Which country, product group and agreed order fulfilment process are involved in the scenario.
- What outcome the customer should get and what data the processing team should see.
- What happens now and how to reproduce the failure in a test environment.
- Who confirms the rule: a logistics specialist, commercial manager, payment partner or another responsible person.
- Which workaround is acceptable during the pilot and which breaks the promise made to the customer.
The business and specialist advisers provide the legal and tax rules for the country. The technical team checks that approved requirements are implemented in the system; it does not certify the legal compliance of sales. These are different deliverables and should not be combined into a single “market ready” item.
Three approaches: configuration, extension or a new platform
Compare the approaches against the same blocker, not by the number of features in a presentation. The smallest change makes sense if it enables the required operation and has clear support arrangements. Migration becomes a candidate when simpler approaches fail to meet the agreed conditions.
| Approach | What to check on the same order | When to reject it |
|---|---|---|
| Configure the current system | Whether product, zone, warehouse and shipping method rules remove the error without new code | The required condition cannot be expressed, or the change disrupts existing sales |
| A narrowly scoped extension | Whether a supported module or a separate integration can pass the necessary data and enforce the rule | It requires a fragile workaround for critical logic, or no one is responsible for support |
| Migrate to another platform | Whether the scenario works on the target system, including passing data through to fulfilment | The demonstration only works without your exceptions, or the transition creates unacceptable operational risks |
A narrowly scoped extension means a change with defined inputs, an outcome and a responsible owner: for example, a shipping adapter rather than a rewrite of the entire checkout. Ask to see where this component ends and what will happen when it is disabled. If the answer covers half the store, the original scope of the custom development no longer reflects reality.
Establish whether the limitation concerns the platform, a module, the service plan or the provider agreement. Replacing the CMS will not automatically unlock a service unavailable to the seller. Nor does the absence of an option in the settings rule out a supported extension.
Hypothetical example: lamps for customers in Poland
In this fictional scenario, a store sells compact desk lamps and large floor lamps and is preparing to enter Poland. The business has agreed that compact items can be sent to a collection point, while large items require an agreed delivery service to the customer’s address. These are the conditions of the example, not universal rules for the country or a particular carrier.
A compact lamp checks out correctly for a test address in Warsaw. After a large item is added, the store still offers a collection point. The customer completes checkout, but the warehouse cannot fulfil the selected shipping method. The manager has to change the agreement after the sale: the problem now affects the promise to the customer, not just the administrator’s convenience.
What to check before commissioning custom development
First, check how products are assigned to shipping rules and the data that triggers those rules. If a large item has incorrectly inherited the conditions for the compact product group, correcting the configuration may be enough. After the change, test a mixed cart, not just each product separately.
The official Shopify shipping rate troubleshooting guide lists product data, markets, fulfilment locations, shipping profiles, packaging and carrier accounts among the causes of problems. An incorrect shipping option does not yet prove that a new platform is needed. Check the tools available to the particular store against the current documentation.
Where the boundary lies between an adapter and migration
An extension is appropriate if the current store provides a supported way to determine suitable services for the entire cart and save the result in the order. In the example, the adapter must exclude the collection point for a mixed cart and pass the address delivery method through to fulfilment. Changing only the label on the screen does not solve the problem.
If the required rule cannot be applied within the available checkout mechanism, the team records that boundary and tests an alternative. Evidence that migration is necessary here consists of a reproduced failure, tested simpler options and a working prototype on the target system. The absence of a ready-made connector in the module catalogue is not, in itself, such evidence.
Large lamps can temporarily be excluded from the international pilot. This is a compromise on launch scope, not the removal of a technical limitation. The owner must approve it.
What test provides enough evidence for a decision
An adequate test shows not just the correct screen but also an order that can be fulfilled. It is carried out using agreed test data, without accidentally charging money or making a real shipment. Both teams must assess the same scenario and the same exceptions.
- Record the original failure: cart contents, test address, expected shipping option and actual result. Do not include a real customer’s personal data in a shared demonstration.
- Check the basic configuration and repeat the scenario after correcting it. Record exactly which settings changed the result.
- For an extension, demonstrate both the working path and an external service failure. The system must not silently replace a missing result with an unsuitable shipping option.
- Compare the customer’s selection with the order data and the record in the fulfilment system. A seemingly correct button does not compensate for a lost service code.
- Repeat the check for the current market and the agreed edge-case carts. If migration is being tested, apply the same examples to the new platform.
The outcome should be a test report for the three approaches: what passed, what failed and where a business decision is needed. “Not tested” does not mean “not supported”. If access to the required mechanism is not yet available, the conclusion remains uncertain; it is not a ready-made justification for a major rebuild.
What to include in the timeline and cost of each approach
Compare not only initial development but also launch and subsequent maintenance over the same period. Configuration may be sufficient without new code, but it still requires checking dependencies. An extension adds component support; migration also adds data transfer and the transition between systems.
Timelines depend on test environment availability, product data completeness, provider responses and the ability to reproduce a failure. If the shipping service has not yet agreed terms with the seller, a development schedule does not resolve that dependency. Ask for the team’s working time to be separated from time spent waiting for access and external confirmations.
Include blocker analysis, implementation, tests, error monitoring setup and support in the cost of an extension. For migration, add data transfer, restoring integrations, operator training and handling old orders. Account for subscriptions and paid features under the actual terms of your account, rather than a universal price tag.
A separate item is the transition risk to existing sales. You need to know where orders opened before the switchover will be processed and how the team will track their status. Once the decision to migrate has been made, the article on store migration that preserves important data will be useful; it does not replace checking whether the transition itself is necessary.
Changing platforms also adds work to map old URLs to new ones so that customers arriving from search do not lose their way. An integration service needs controlled access to order data. An external calculation during checkout requires performance testing and checks of how it behaves under delay. These costs should be tied to the chosen approach, not added as a general surcharge for “going international”.
What decision to record before development
Agree on a tested approach with clear boundaries of responsibility, not a platform name. If configuration removes the blocker without disrupting existing operations, migration can be postponed. Record unresolved dependencies, their owners and the condition for reviewing the decision.
GL.ua (Glyanets) offers online store development with online payments and ERP integrations. If you are preparing to enter a new country, discuss the development of your online store with GL.ua using an operation that currently does not work as an example: what you promise the customer, where the failure occurs and what outcome the team needs. This provides a concrete basis for evaluating a change, without commissioning migration in advance.
Frequently asked questions
Should we immediately create a separate store for another country?
Not necessarily. A separate store is worth evaluating if the local team needs independent control over operations. A different country does not, in itself, determine the architecture; first agree which processes should be shared and which should be separate.
Who should check the contractor’s conclusion that migration is needed?
The business process owner confirms that the requirement is mandatory, while the technical lead confirms implementation boundaries and alternatives. For a substantial budget, you can commission an independent review of the blocker record and prototype without unnecessarily giving the reviewer production access.
Can a prototype be approved if there is not yet an active agreement with the carrier?
Some of the logic can be tested in an agreed test environment, if one is available. But this will not confirm the seller’s right to use the service or all the conditions of real operation; those dependencies remain open until confirmed.
What if the new country is generating few orders so far?
Compare acceptable manual processing during the pilot with the cost of automation. Define who will do it, which errors they will monitor and what change in workload will trigger a review of the decision. Do not promise the customer an automated service that the team cannot yet deliver.
Should we keep the old store after the transition?
Determine the need for access to historical records and open operations before switching the system off. Separately agree where the necessary data will be stored, who will view it and which old integrations can be stopped; do not keep an unsupported public store running solely for reference.
Just one step to your perfect website



