Blog article

Does your online store need a redesign? What to check before rebuilding

Considering an ecommerce website redesign? Review product discovery, mobile checkout, payments and order handling before choosing focused repairs or a rebuild.

Conceptual shopping bag and product tag beside a magnifying lens highlighting a broken connection, introducing a review of an existing online store.
Original conceptual illustration of reviewing a buying journey, not a client store, payment screen or measured result.

The short answer

An online store may need focused repairs when a specific control, piece of information or payment connection is causing difficulty. Consider a wider redesign when several parts of product discovery, mobile shopping and order handling need coordinated changes. Review the buying journey and business context before committing to a rebuild.

Your online store gets visitors, but orders are disappointing. The design feels dated, and a rebuild starts to look like the obvious next step. Before committing, find out what is stopping a suitable customer from buying.

A store may need clearer product information, a repaired payment connection or a more usable mobile checkout. A wider redesign becomes worth discussing when several parts of the shopping experience need coordinated changes. Traffic quality, pricing, availability and delivery terms also deserve attention; changing the layout cannot resolve every reason a customer decides against an order.

An ecommerce website redesign should begin with an assessment of the existing store and a defined buying task. Here is what to review before asking a developer for a proposal.

Find where the buying journey breaks

Choose a product you actually sell and describe the customer who would reasonably buy it. Start from the page that customer is likely to reach, such as a product page linked from an advert. Do not assume everyone begins at the homepage.

Follow the task through:

  • Find the right item. Can the shopper use the menu, search or filters to reach a suitable product?
  • Decide whether it fits. Are the size, specification, price, availability and relevant delivery or return details clear?
  • Place the order. Can the shopper choose the right option, review the total and use a supported payment method?
  • Understand the outcome. Does the customer know what happened, and does the team have the record it needs to fulfil the order?

Record the exact point of difficulty, the device and the steps that reproduce it. “Customers cannot select a size on a phone” gives a developer something to investigate. “The website needs to be modern” leaves the underlying problem unclear.

Where you have reliable reports, compare stages and devices alongside actual order records. Check the reporting definitions, campaigns and time periods before drawing conclusions. An abandoned cart does not, by itself, identify a design fault or prove that the shopper intended to pay.

Test a purchase on a phone

Use an ordinary phone and a realistic connection. Try the menu, product options, image controls, cart and checkout. Notice whether a sticky banner covers a control, the keyboard hides useful feedback or an error makes the customer start again.

Check information as well as controls. A shopper may be able to press every button and still be unable to work out whether you deliver to their address. Put important conditions where the decision is made, rather than leaving the customer to discover them after entering their details.

Illustrative shopping journey

Find the broken connection.

  1. Product foundThe shopper selects an item.
  2. Total reviewedThe delivery choice and charges are clear.
  3. Payment unavailableNo usable payment method appears in this example.
  4. Paid outcome unconfirmedThe shopper cannot complete payment here.

Inspect the payment connection. The earlier steps work in this example. Check compatibility and configuration before changing unrelated pages.

Hypothetical journey, not a client checkout, test result or measured funnel. The gap represents an unavailable payment method. Actual stores can create pending orders before payment; verify the order and payment states separately.

The example illustrates a functional problem that could survive a visual refresh. WooCommerce's checkout documentation explains that incompatible payment extensions can leave a payment option unavailable in the Checkout block. A developer should check the actual extension and checkout configuration before recommending a replacement design.

For the broader mobile experience, use our mobile website review guide. The store review should also follow the customer into payment and the team's order-handling process.

When focused repairs may be enough

If the catalogue is easy to navigate, staff can maintain it and the problem is confined to one part of the journey, ask for a focused repair scope first. Examples include a product-option control that fails on mobile, missing delivery information or a checkout connection that stopped working after a change.

Ask the developer to explain the suspected cause, how it will be checked and what would count as a successful correction. Sometimes the work is configuration or content; sometimes it requires development. The assessment should distinguish those possibilities.

If slow loading is the main complaint, investigate it before treating a rebuild as the solution. Our website speed guide describes that starting point. Keep a usable part of the existing store when there is a sound reason to retain it.

When a wider ecommerce redesign makes sense

A coordinated redesign is more relevant when problems recur across the store. Categories may reflect an old product range, product templates may omit essential buying information, and the mobile journey may require customers to repeatedly backtrack. Correcting one button would leave those connected problems in place.

Also consider the team's work. If staff cannot maintain product options consistently or routine changes break layouts, the proposal should address editing and administration alongside the public pages. A visually polished homepage will not make an unreliable catalogue manageable.

Agree which journeys and templates need to change. Shopify's ecommerce UX guide covers discovery, product information, checkout and post-purchase communication. Use those areas as prompts for your own assessment, rather than assuming every store needs every feature.

The decision should name what the redesign will solve, what it will retain and which issues sit outside its scope. Low order numbers alone are not enough to choose a full rebuild.

Decide what can stay on the current platform

Redesigning a store and moving it to a different platform are separate decisions. Ask whether the current system can support the required catalogue, editing, payments and order process with a maintainable implementation.

If it can, a redesign may keep the platform and useful records while improving the templates and customer journey. If it cannot, ask which specific requirement creates the limitation and compare the cost of extending it with the work involved in moving.

Check the account permissions, extension support and provider requirements for the actual store. A different theme does not automatically support every existing integration. Moving platforms also needs a plan for products, customers, orders, account access and any information that cannot transfer directly. Do not agree a migration solely because another technology is newer.

Compare the full scope and continuing costs

Request a proposal around the same requirements, so a small repair and a wider redesign can be compared fairly. Ask what is included in product templates, mobile behaviour, content preparation, payment and shipping connections, testing and staff handover.

Separate the development fee from continuing charges. Depending on the solution, those may include hosting or a platform subscription, extensions, support and payment-provider fees. Establish who owns the accounts, who pays renewals and what happens when a licence or service changes. A reduction in one subscription does not establish a lower total operating cost.

Ask who will handle product data and check that variants, images, stock information and delivery rules remain usable. Record exclusions such as product photography, copywriting, historical-data cleanup or third-party account approvals. Include any agreed maintenance and post-launch checks in the comparison.

Our redesign brief guide covers the wider proposal. For a store, add representative products, the payment and delivery requirements, and an example of how the team handles an order today.

Inventory important product and category addresses before changing them. If URLs need to move, agree a relevant mapping and check the redirects. Google's site-move guidance describes URL mapping, testing and monitoring; it does not guarantee unchanged rankings. Link changes should be part of the project plan.

Agree how new orders, stock changes and staff edits will be handled during the transition. A review copy can become out of date while the live store continues trading. The plan needs an owner for the final data check, a release window and a recovery route if an important buying task fails.

For a wider URL transition, use our redesign and SEO guide. Keep migration work visible in the quote rather than assuming it is included in a page-design fee.

Accept the work through complete shopping tasks

Ask for a demonstration using suitable test accounts and the chosen payment provider's supported test setup. Agree the arrangements before anyone changes a trading store. Shopify warns that customers cannot place live orders while payment providers are in test mode.

Include tasks that reflect what you sell:

  1. Find a product, select a valid option and verify the displayed price and availability.
  2. Enter a supported delivery destination and check the total, including the charges that apply.
  3. Complete a test payment and inspect the corresponding order and payment state used by staff.
  4. Try a failed or abandoned payment and check the message, retry route and recorded state.
  5. Check the agreed customer confirmation and the team's fulfilment record or notification.
  6. Repeat the important tasks on a phone and with a keyboard, including correcting an input error.

An order record and a successful payment are separate observations to verify. WooCommerce's order-status guide distinguishes a received order awaiting payment from later states. WooPayments documents test orders and test-mode payment handling; other gateways need their own supported procedures. Label test records and agree their handling so they are not confused with real fulfilment work.

For returns, cancellations or subscriptions, include the relevant tasks in the scope rather than assuming a successful first purchase covers them. Our staging review guide explains how to record what was reviewed and what still needs a production check.

Give the developer a useful starting brief

Send the store address, the problem you want to solve and a product or shopping task that demonstrates it. Include the platform, important connections, selling regions and who maintains the catalogue. Describe any recent changes and the timing constraints for the work.

Use anonymised examples where order information is needed. Share account access through an agreed private process; the initial enquiry does not need customer records or payment details.

Ask the developer for findings and options before settling on a full rebuild. WebBuild's ecommerce and WooCommerce development service covers catalogue and checkout journeys, scoped payment and shipping connections, and order administration. Discuss your existing store with the buying task you want to improve so the work can be scoped around that requirement.

A WebBuild project offer

Could your website be doing more for your business?

Share your website and request a complimentary initial assessment of its design, usability, performance and enquiry experience.

10%OFF

Quoted WebBuild service fees

Up to US$300 per project, or the equivalent confirmed in your quote.

Complimentary Initial Website Assessment

Terms & conditions apply

Tell us about your project

Start with your details. We’ll discuss the right next step.

Which describes your project?

Security check

Preparing the security check…

This form uses Cloudflare Turnstile to prevent spam. If the check does not load, email your request or call +91 968 502 1028.

We use your details to respond; this does not subscribe you to marketing. Privacy Policy · Terms & conditions apply.

Preparing the security check…

Questions covered in this guide

Do low sales mean our online store needs a redesign?

No. Review traffic quality, product fit, prices, availability and delivery terms alongside the shopping journey. A specific functional problem may need a repair, while connected problems across the store can justify a wider redesign.

Can we keep the existing ecommerce platform?

Often that is an option, but the required catalogue, editing, payments and order process need assessment. Compare extending the current platform with moving only after identifying the actual limitations and migration work.

What should an ecommerce redesign quote include?

Agree the templates and journeys, product-data responsibilities, payment and shipping connections, testing, transition, account access and handover. Separate development fees from subscriptions, licences, payment-provider charges and ongoing support.

Will a redesign increase our sales?

A redesign can address identified shopping problems, but sales also depend on demand, traffic, pricing, stock and fulfilment. Agree the problem, acceptance checks and measurement definitions; no sales increase can be promised from a change in appearance.

What should we send a developer first?

Send the store URL, platform, a reproducible shopping problem, selling regions and relevant connections. Describe who maintains products and handles orders. Use anonymised examples and share account access through an agreed private process.

Sources and project context

Turn the question into a clear next step.

Tell us about your current setup, the people using it and what needs to improve.

Keep exploring

Related reading

Chat with us