Build it with Medusa.
Control it with Souk.
Make your store easier to buy from and adapt to your business. We redesign the site and move it to Medusa, with a plan for your data, tools and daily orders.
Discuss your redesignMoving products is only part of the job. The prices, connections and daily routines around them are what keep your business running.
We list the prices, discounts, shipping options and account features your customers use, including rules that only exist in the current code. Your team helps us identify exceptions, such as negotiated prices or employee purchase limits.
We map the tools that handle stock, payments, accounting and customer emails, and check what each connection needs. Stock updates, payment events and failed orders all need an agreed owner and behaviour.
We record your page URLs, search settings and analytics so they can be checked on the new site. Redirects, search metadata and tracking events belong in the migration scope, not on a list for later.
We redesign product pages, navigation and checkout around how your customers shop. Where your current platform allows it, we can launch the new design first and move the store’s data and operations later. Your team reviews the design and buying journeys before they reach customers. If separating the two stages adds unnecessary work, we plan a single launch instead.
We transfer the agreed data, connect your tools and test complete orders. Before launch, we review the results with you and agree on the final data update, any pause in operations and the recovery plan. Your existing store keeps selling while we prepare the replacement; recent orders and stock changes are accounted for in the final transfer.
The steps depend on your current platform and integrations. A staged launch is not possible for every store; we check that before recommending it.
We inventory pages, components, buying rules and connections. You can see what stays, what changes and what is removed before we build.
Each agreed buying journey has checks: the right price, payment, stock update and order reaching the right tools. We run those tests and compare transferred data with the original.
You review the results and approve the switch. The plan covers monitoring, support and what to do if something fails. The code, setup and test results are documented for handover.
Medusa is open-source software for products, orders and payments. It lets us adapt your store’s buying rules and connect your tools. You own the custom code we build. We’ll check whether that flexibility justifies the work and running costs for your business.
Share your store with our team. We first discuss what you want to improve and agree on the scope of a diagnostic. The resulting migration plan gives you:
Pages, components, data and connected tools, including the parts your team relies on every day.
Buying journeys, pricing rules and integrations, with the checks needed to preserve them or validate a change.
What to rebuild, transfer and test; the launch sequence, dependencies and points where your team approves the work.
Scope, assumptions and next steps. That can mean improving your current platform if a move is not justified yet.
We check what can transfer and how each field maps to the new store. Passwords, saved payment details and app data may not be portable.