Switch e-commerce agency without losing orders or data
Kenneth Lyngshede 
Your e-commerce site takes orders, but every change gets stuck. The supplier is slow to respond, and your staff fix data that should flow through automatically. Now you are considering switching e-commerce agency, while sales have to keep running.
The hard part is working out what actually needs to change. A new supplier can take over a working solution. A platform change, on the other hand, means data, integrations and ways of working have to be tested again. Start by separating the problems before anyone prices a rebuild.
The first step is to measure where you are in numbers
The route through the switch starts with measurement and documented ownership. After that, you need to review the order flow, calculate the costs and plan the migration. Before the contract, ongoing management should also be described and the supplier should have answered questions about the handover.
The baseline decides whether you can judge the result. Pull organic search traffic for the last twelve months. It shows which landing pages and seasonal patterns need to be preserved. The conversion rate helps you spot whether customers find it harder to complete purchases after launch. Decide how each metric is calculated before you compare the old and new solutions.
Also measure the share of orders that need manual handling. It shows how much work ends up with customer service and finance. Record the number of errors in the order flow per month, and separate duplicates from wrong prices, missing order lines and failed transfers.
The time from a decided product change to publishing shows where work gets stuck. Add page performance and the time it takes to publish a completely new product. Get the data from the analytics tool, the business system's logs and customer service tickets. A shared working file is enough to start.
Separate sales from profitability. Higher net sales do not automatically mean higher profitability, so internal work and the cost of errors need tracking too.
The measurements usually point towards one of three paths. The solution can stay as it is, be sound at its core and need improving, or need rebuilding. Keeping what works usually needs the least change and can cost the least. The decision should rest on measurements and a technical review of what you already have.
Ownership of data and integrations decides whether you can switch
An agency switch transfers access and working responsibility. Ownership, however, has to be checked in the contracts. Make a written inventory of product data, images, product relationships, customer register, agreed prices, order history, analytics data and customer consents.
For each part, you need to know how a complete export is done. Also check source code, accounts, licences and documentation. A file of product names helps little if the relationships to spare parts and accessories are missing. A useful handover pack should make sense even after the previous developer has left.
Document which system is the source for product, price, stock, customer and order. Write down how often the data syncs and who acts when a transfer fails. If product information sits in several spreadsheets, you first need to decide where it will be maintained.
Svensk Handel's E-commerce Indicator estimated Swedish e-commerce turnover at SEK 166 billion in 2025. For your own sales, control over the data needs to be secured in the contract. Proprietary custom solutions can require extra documentation and handover work, especially when the next supplier has no access to the underlying code.
The order flow behind the login is where the friction sits
A polished home page says little about the work after the customer logs in. Follow a repeat buyer from login to delivery notification. That is where it becomes clear which functions need to work together.
The customer should land on the right company and see their agreed range. The price has to follow the right customer agreement, currency and order quantity. A colleague at the same customer may need different permissions, for example the right to prepare an order without the right to approve it.
Test the customer's whole task, including payment. That can mean invoice terms, quote approval or an order that has to be authorised. A demo should show what the customer can complete without calling you.
Say a manufacturer lets resellers order through a portal. The products can be found and the order is sent correctly. But when the delivery address changes, the reseller still has to email customer service, who then update the business system by hand.
That task needs to be visible when you assess order management in e-commerce. Otherwise a quote can cover the buy button while your staff keep handling the exceptions every week. Sales and customer service also need to see the same price and order status as the customer.
Have someone with buying experience run the scenario in a demo. Count the handovers, manual entries and moments where the person needs help. Then require the most important steps to be shown with relevant agreements and permissions in a working configuration.
Start with flows that are used often or cause costly errors. Reorders, address changes, agreed prices and order follow-up usually give a better basis for decisions than a tour of every available feature.
A cost calculation without ongoing management is always too low
A quote can be clear about the build cost and still leave large parts of ownership unpriced. For the CFO, comparison becomes hard when suppliers work from different assumptions. So split the calculation by when the work happens, from preparing the current setup to the years after go-live.
One-off work covers migration, data cleanup and integrations before go-live. Add the wind-down of old contracts, the handover and your own internal reconciliation. If the test migration shows incorrect product relationships, someone has to fix the source data and rerun the transfer. That time belongs to the switch even when no supplier does the work.
Running costs cover the work of keeping the solution working. Change costs arise when the business orders new functions or changed business logic. The line between the two needs to be in the contract. Otherwise the same work can be presented as maintenance during the sales phase and as further development when the invoice arrives.
Test the calculation against a hypothetical year with three larger changes. Ask each supplier to describe the cost of, for example, a new customer segment, changed pricing logic and a new approval flow. Include your own time for requirements, quote review, testing and approval.
Compare the same content over the same period. The cost lines in three items missing from your TCO calculation help you check what has ended up outside the build price. Glanser Care is a contracted responsibility at a fixed monthly cost that covers version tracking, compatibility through upgrades, maintenance of the integrations with the business system and bug fixing.
In the end, the calculation should show the supplier's costs, your working time and the remaining uncertainties. Write down who pays when an assumption turns out to be wrong. A fixed price only becomes useful when scope, exclusions and acceptance criteria can be read together.
Switching e-commerce agency needs testing and parallel running
The migration needs access to your people. Product managers need to approve data, finance needs to reconcile amounts and the business needs to decide on go-live. Book their time and set decision dates before the development plan is locked.

Let the migration plan follow a set order. Each step should produce material the next responsible person can check.
Start by mapping the flows: business system, PIM, customer management, payments and analytics. A common pitfall is scheduled exports that someone starts by hand. Then name the source for each piece of data, meaning where product, price, stock, customer and order are maintained. If several systems can overwrite the same field, correct data can be replaced after the migration.
Next, describe the interfaces with API contracts, field mapping, sync frequency and error handling. Without rules for interrupted transfers, the error queue quickly becomes manual work. Then run test migrations with representative product and order data, and repeat until the fields are right. Check history and relationships, which otherwise easily disappear behind correct item counts.
Acceptance tests should cover stock reservations, customer price lists, VAT, order status, returns and permissions. Also test idempotency, so repeated API calls do not create duplicate orders. Successful responses alone are not enough as test evidence.
Then run a limited period of parallel operation. Compare the website's order amounts with the business system's records and check the displayed stock levels. Decide which environment may create live transactions, or you risk duplicates. Finally, the cutover should have a stop point, a decision-maker and a rollback plan that also handles orders received after the cutover.
Put the after-sales flows in the same test plan. Test how a return or complaint is linked to the right order, how the return is registered and how the credit reaches finance.
Also test what information the customer gets at purchase. Document where the rules are handled and who may change them. Terms in the footer do not replace working routines for customer service and refunds.
Search traffic needs its own check. Export the URLs of the pages that received traffic during the measurement period. Map each old URL to a relevant new page with a permanent redirect, and test the redirects during the test migration. Also check page titles, indexing settings and that the analytics tool records purchases correctly.
Set a launch date outside your peak season. Put a fixed follow-up date in the calendar, when traffic and purchases will be compared with a relevant earlier period. At the same time, document changes to campaigns and the range that affect the comparison.
A small site without integrations can often be moved with a simpler plan. Many connections, on the other hand, need more decisions from you. The supplier can build the transfer, but your people have to judge whether customer agreements and financial records came out right.
Ongoing management after go-live decides whether the switch holds
After launch, an error in the order flow can start with a platform update, show up in the integration and end with the wrong price or stock status on the website. Troubleshooting then needs to follow the same path: check the change, trace the data through the systems and verify the fix with a test order.
The contract should state who receives the incident and how it is followed until the error is fixed and tested. Then the next step is clear even when several technical parts are involved. A maintenance agreement needs to describe how an error is resolved, from the first report to a verified fix.
Repeat the approved tests after relevant upgrades. Check, for example, that prices and stock show correctly, that the order reaches the business system and that the payment is registered. Save the test results and update the scenarios when functions or connections change.
How much ongoing management should cover depends on the scope of the solution and the consequences of downtime. State in the contract which upgrades, bug fixes and compatibility tests are included in the fixed cost.
Three questions to the next agency reveal more than the quote
A well-written quote shows what the supplier wants to sell. Your questions also need to show what work the supplier has prepared. Use concrete wording and make the answers part of the contract documentation.
Which fields are migrated, how are errors logged, how many dry runs are included and who is responsible for reconciliation against the business system before launch? A clear answer includes the field mapping, the responsible role and the approval criteria. A vague answer means both the effort and the cost are still uncertain. Ask for material you can check against your own examples.
Who owns the source code, data and documentation when the contract ends, and what does the handover cost? The answer needs to separate your content from licensed parts and the supplier's own components. It reveals what access the next agency actually gets and what work you will have to buy if you move.
Where are legally sensitive rules handled, in the platform, the integrations, the content or manually, and how is responsibility documented before launch? A concrete answer points to the affected settings and routines. If responsibility is left between technology, content and customer service, you need to sort it out before signing.
Reviewing an e-commerce agency becomes more useful when the answers are tested in practice. An anonymised example can show how the supplier documents a migration. A demo using your data shows whether the solution can handle the way you work.
Above all, judge whether the answer can be followed from requirement to test to responsible person. A confident presentation is easier to deliver than a verifiable handover. The handover is what you need to be able to demand, even if the project team changes.
Start with a 72-hour analysis of what you have today
A switch becomes a dated plan only once the current situation has been measured. In a 72-hour analysis, you set aside two hours, and within 72 hours you get an inventory of functions and integrations, a functional specification, a prototype and a complete cost picture with a timeline, free of charge.
The material should point to the boundaries: data, integrations and responsibility after go-live. Gather metrics, known errors, lists of connections and the contract terms that govern access and termination. Then obstacles can be split into what sits in the solution, what sits in your systems and what has to be solved commercially.
Expect to put in some time yourselves, though it is limited. Finance needs to be able to explain the reconciliation, product managers need to show where data falls short and customer service needs to describe the exceptions that eat up time. Not everyone has to be in the meeting, but someone on your side has to be able to gather the answers before the clock starts.
With that material in place, you can decide whether the solution can stay, be improved or needs rebuilding, and compare what each path demands of your team over time.
A new interface, a new maintenance partner and a new platform are three different deals. The analysis should show which effort is justified before you commit, and which part of the work can never be handed entirely to the supplier.

About Kenneth Lyngshede
Kenneth Lyngshede writes about business models, offers and strategy, and how companies can plan their digital development with predictable costs.

ERP and EDI that keep orders and invoices together
ERP EDI integration explained: which messages are included, how to validate data, and which metrics indicate whether the flow is working.
Peter Nilsson 
ERP systems as the hub for your website and portal
Business systems consolidate finance, orders, inventory, and product data into a single source. This is then connected to the web, portals, and EDI.
Peter Nilsson
PIM for wholesalers and who owns the product data
PIM for wholesalers starts with deciding who can change what. How to split ownership between ERP and PIM, choose stable keys and set limits on where AI can enrich product data.
Peter Nilsson