A visual refresh, a theme rebuild and a catalogue restructure solve different problems. We work out which one you need before writing the design brief.
The store works, but the presentation is dated or inconsistent. We improve the visual system inside the current structure where that structure still holds.
The templates are difficult to change, slow or unable to support the buying journey. We replace or substantially rework the theme while keeping the store, catalogue and history.
Customers cannot find the right product, filters are unreliable or merchandising takes too much manual work. We fix collections, tags, navigation and product relationships. A new theme alone would only put the same problem on a nicer page.
We review the live store, the admin and the backlog. We look for the first constraint that affects buying or the team's ability to operate the site. The recommendation names that constraint and the smallest piece of work that removes it.
A trading store cannot be treated like a blank canvas. The scope identifies templates and app extensions that must keep working. Changes are reviewed on a non-live theme, key journeys are tested before release and the launch plan states how to revert if the release creates a serious fault.
From-price or scoped after discovery
Migration and build
From £5,000From $6,500
Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.
Starting price
Plus, B2B, multi-market
From £8,000From $10,500
Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.
Starting price · scoped after discovery
One bounded piece
£1,500$2,000
One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.
Fixed price
A visual refresh inside an existing theme is usually a bounded project. A theme rebuild with a catalogue restructure is a larger piece of work, and the difference between them is a diagnosis rather than a preference.
Often, and it is worth checking before committing to a rebuild. A well-built theme with a clean section architecture usually has more room in it than the team expects. Where it is genuinely obstructive we explain which parts and why, in terms of the changes it makes difficult.
It can, if URLs, internal linking, metadata or content are changed without a plan. We inventory the routes that earn traffic, hold them constant where possible, and redirect them one hop where they genuinely have to move. What we do not do is promise rankings will improve.
No, and on a trading store there is usually a good argument for not doing so. Templates can be rebuilt in sequence behind the scenes and published in stages, which keeps each change small enough to attribute if something moves.
By looking at the store, the admin and the backlog rather than at the brief. The output is a named constraint and the smallest piece of work that removes it, which is sometimes smaller than the brief assumed and occasionally larger.
If the real problem is structure rather than appearance, we will say so before you pay for the wrong project.
