
A stagnating shop loses sales without anyone noticing
A confusing catalogue, a checkout that no longer converts or performance that has slipped: these symptoms do not fix themselves, and putting off the redesign simply extends the time the shop runs below its targets. This service covers the functional and visual redesign of a shop that is already trading: catalogue, checkout, payments, shipping, useful data and preparation of the switchover. A move to another platform can be included when the initial analysis justifies it.
Indicative scope
Same platform, fewer than 50 products.
Migration to another platform, up to around 100 products.
Complex catalogue, business rules or connections: on quote.
The starting price is shown at the top of this page; the other tiers are stated in your quote. The standard lead time is 4 to 6 weeks. A complex migration can take 6 to 10 weeks or more, depending on the data, the connectors and the testing. When an e-commerce audit already exists, its findings feed into the quote, with no automatic refund.
Who is it for?
Trading shops whose catalogue, checkout or performance no longer meet their goals.
Businesses that have already had an audit and are ready for a redesign or migration.
Shops whose data (catalogue, customers, orders) must be carried over without interrupting sales.
A redesign that takes real operations into account
An online shop is more than the pages customers see. It also depends on pricing rules, stock, payment methods, carriers, emails, apps and the habits of the team that processes orders. Preparing the redesign therefore starts with a technical and operational inventory, not just a mock-up.
The priority journeys are defined from your actual business: finding a product, checking availability, ordering, paying, receiving the expected information, and letting your team process the sale. Special cases that affect the budget, such as complex variants, trade pricing, subscriptions or connections to a business system, are identified before the build.
When a migration is planned, the quality of the source data and the capabilities of the target platform are checked before promising a complete transfer. Anything that cannot be transferred automatically is flagged and priced. This approach limits surprises at switchover and lets us plan the necessary checks, without guaranteeing that there will be no interruption or anomaly at all.
The work runs remotely; an on-site visit remains possible, on quote.
What is included
Definition of journeys, catalogue and operational constraints.
Responsive theme, navigation, product pages and checkout.
Configuration of payments, taxes, shipping and notifications set out in the quote.
Transfer or migration of the data defined in the scope.
SEO redirects, analytics and performance checks.
Testing of critical scenarios, backup, switchover plan and post-launch checks.
How the project runs
Inventory of the shop, data, apps and flows.
Approval of the scope, target platform and migration plan.
Build, data transfer and functional testing.
Acceptance testing, a switchover rehearsal if needed, launch and checks.
Deliverables
The redesigned (or migrated) shop live, with catalogue and checkout approved.
SEO redirects applied and performance checks carried out.
Documentation of access, configuration and the switchover plan handed over.
What is not included
Platform, theme and app subscriptions, full entry or rewriting of the catalogue, custom connectors, transfer of a large history and complex business development are priced separately.
Frequently asked questions
Are open orders and customer accounts carried over? It depends on the platform and the data available. The objects, periods and migration rules are listed precisely in the quote and approved during acceptance testing.
How do you limit the interruption to sales? The switchover is prepared with a backup, a data freeze if needed, tests of payments and shipping, and checks immediately after launch.