Choose focused improvements when the foundations still work
If the visual direction is right, the theme is maintainable and the catalogue is organised, start with the friction you can identify. This might be a hard-to-use menu, unclear sizing, a product template missing important information or a campaign page that does not explain the offer.
A narrowly defined project can address a meaningful buying journey without disrupting the rest of the store. Define the desired behaviour before asking for a collection of cosmetic changes.
- Customers cannot find the right product category.
- Important information is difficult to find on mobile.
- A product option, cart interaction or app integration is broken.
- The team cannot update a recurring campaign without editing code.
Consider a redesign when the problems repeat across the store
A redesign becomes more useful when the brand direction has changed, every page follows a different visual system, or the current templates cannot support the way you sell. Repeated patches can become harder to maintain than a coordinated set of templates and sections.
A redesign is still not a reason to replace everything. Keep useful content, working integrations and recognisable brand elements where they support the new direction. Separate a visual redesign from a platform migration: they have different data and launch risks.
Use evidence before deciding the scope
Review the store on a phone, follow the product-to-cart journey and collect recurring customer questions. If analytics are available, inspect which pages and devices are involved in drop-offs. Session recordings can suggest issues to investigate, but a recording alone does not establish why someone left.
Check whether the issue is actually in the storefront. Delivery cost, stock availability, pricing or an offer that does not match the traffic can also affect purchases. A design project should not promise to fix every business problem.
Agree what success looks like for the first release
Use concrete acceptance criteria: customers can select a size from a collection card; the size guide opens on mobile; the campaign section is editable; the cart remains usable after adding a subscription. These are things you can verify.
If a conversion-rate experiment is appropriate, agree the tracking, traffic requirements and evaluation method separately. Technical completion, usability improvements and measured commercial lift are different outcomes.
- Describe the customer or team problem.
- Identify the affected pages, devices and integrations.
- Agree the implementation and what is excluded.
- Review the preview against the acceptance criteria.
- Measure the agreed outcome after launch where data is available.
Match the work to a real feature
Our AIPAI project includes measurement guidance in centimetres and inches. RQ The Label brings size selection and quick add into collection browsing. These are examples of specific shopping needs shaping the implementation, rather than decoration being the whole brief.
Start with the store, not a package name
Share your current store and the changes you have in mind. We can assess whether a focused project, a coordinated redesign or ongoing development support is the better fit. The scope and quote follow that assessment, including any content or app work needed.