Skip to content
codecollab.pl
§ Blog ecommerce website redesign

Redesigning a store without rebuilding it from scratch - when it pays off

Your store is not earning less because it is old - it is earning less because buying from it got harder

Krystian Kacik 10 min read
Contents

The most common reflex when a store looks dated is: “let’s build a new one”. I understand where it comes from - it is easier to picture a clean start than to dig around inside something that already exists. The trouble is that building from scratch is usually the most expensive, riskiest and slowest route to the same destination. And the destination is almost never “a new store”. The destination is more carts and fewer people bailing out halfway through checkout.

In most of the cases I see at clients, the foundation of the store is fine - the engine runs, the integrations work, orders come in. What hurts is the layer the customer sees and clicks: the layout, the readability, the path to checkout, the speed. That layer can be swapped out without touching the foundations. And that is exactly what a redesign is - transplanting the look and the shopping comfort onto an existing, healthy body.

Below I lay out when a redesign is entirely enough and when you genuinely have to rebuild. Because sometimes you do - and it is better to know that before you spend the money, not halfway through.

What “redesign” actually means compared to a rebuild

Let’s start with the distinction, because these two words get mixed up constantly and they are what decides the price.

A rebuild replaces everything: a fresh store installation, migrating products, integrations, payments, shipping, customer accounts and order history. All of it has to be built, tested and connected from zero. That is months of work and plenty of places where something can go wrong.

A redesign on an existing store is something narrower: I leave the engine, the product database, the integrations and all the logic in place, and replace what the customer sees and clicks - the page layout, the typography, the images, the path to checkout, the mobile version and the performance. Products, orders, customers and payment settings stay where they are. The store keeps running the whole time, and you lose nothing along the way.

What helps: before you decide on a budget, ask one question - is the problem what the customer sees, or how the store works underneath. If it is the former, a redesign is almost always enough.

Signs a redesign is enough (the foundation is fine)

This is the most common scenario. The store is a few years old, looks like it came from a previous era, but nothing serious is wrong inside. You recognise it by this:

  • The store runs on a current, supported platform (WooCommerce on an up-to-date WordPress, for example) and can be updated normally.
  • Orders, payments and shipping work without failures - customers buy, money comes in, integrations do not throw errors.
  • The product catalogue is tidy and the category structure makes sense - there is no need to rebuild the whole assortment.
  • The problems are “visual and clickable”: an ugly or cluttered layout, a poor mobile version, a confusing path to checkout, old photos, too many steps in the cart.
  • The store already has history in Google - people arrive from search and you do not want to lose that traffic.

If that sounds like your store, here is the good news: you do not need a rebuild. You need new skin and a better buying path on top of what you already have. That is a fraction of the cost and a fraction of the risk.

Signs you do need a rebuild after all

Sometimes patching costs more than a solid restart - and in that case I say so plainly rather than prolonging the life of something that will need replacing in a year anyway. A rebuild is worth considering when:

  • The store runs on an outdated, abandoned platform or theme whose author no longer supports it - updates break, and every change threatens to blow up the layout.
  • The foundation is glued together from dozens of plugins that get in each other’s way, and nobody knows what is holding what. Every fix moves three other things.
  • The architecture cannot keep up with the business - you want to add new product types, languages, wholesale, or logic the current store simply cannot carry.
  • The store is slow at its foundations, not on the surface - the problem sits in the construction itself and reworking the theme will not touch it (how to tell the difference I cover in more depth in the piece on a slow WooCommerce store).
  • The code is so patched together that every hour of work goes into defusing mines instead of real improvements.

The honest rule is this: if maintaining and patching the current store starts costing more than building it properly once, it is time for a rebuild. Up to that point, a redesign almost always wins on the numbers.

What a redesign actually changes in sales

This is the crux, because a redesign is not about “making it prettier”. Prettier is a side effect. The goal is that more of the people who already entered the store actually finish the purchase. The biggest gains come from cleaning up the path to checkout and the mobile version, because that is where carts leak.

Concretely, I work on the things that translate into carts:

  • The path to checkout - fewer steps, fewer fields, a clear “what next”. Every unnecessary screen and every surplus field is people dropping out right before they pay.
  • The mobile version - most store traffic today is phones. If tapping is awkward, the price is hard to read or checkout is hard to reach, you are losing sales on your biggest channel.
  • Readability of the offer - photos, descriptions, prices and the “add to cart” button where the eye looks for them. The customer should know in a second what they are buying and what it costs.
  • Speed - slow loading means abandoned carts. According to Google’s data, the probability of somebody leaving a page rises sharply with every extra second of load time. A redesign is a good moment to slim the store down while you are at it.
  • Trust - visible reviews, returns, shipping costs and secure payment. An old, neglected look undermines trust by itself, even if the store is completely honest.

What helps: before the redesign, pick one or two numbers you want to improve - the share of people completing a purchase, say, or the load time of a product page. Otherwise “the new look” becomes a matter of taste rather than of results.

Why keeping your URLs and SEO is critical here

This is the part that is easiest to break in a rebuild - and the strongest argument for redesigning on the existing store.

If your store has been running for a while, it has earned a position in Google. Specific product and category URLs are indexed, they have history, and they pull in traffic you no longer pay for. That is one of the most valuable invisible assets a store has.

In a redesign on the existing foundation those URLs stay untouched. I replace the look, but /category/winter-boots is still at the same address. To Google it is the same page, only better - no reset, no loss of position.

In a rebuild the URLs change very easily - a different platform, a different structure, different endings in the links. If nobody prepares proper redirects from the old addresses to the new ones, Google loses half the store overnight, and traffic and sales go with it. I have seen stores vanish from search for weeks after “the new, prettier version”, because nobody took care of the redirects.

What helps: if you do have to change URLs, the iron rule is a one-to-one redirect map from old addresses to new ones, prepared before launch, not after the fact. That is the difference between a smooth switch and a loss of traffic.

A fraction of the cost and a fraction of the risk

Finally, let’s do the plain arithmetic, because this is usually the argument that tips it.

A redesign on a healthy foundation is cheaper for a simple reason: I am not rebuilding payments, integrations, product exports, customer accounts and all the logic that already works. You pay for the look and the shopping comfort, not for recreating things you already have. That really is a fraction of the cost of a full build.

It is also cheaper in the hidden cost - the risk. Every place I do not touch is a place that cannot break. During a redesign the store runs the whole time, orders keep coming in, and I make the changes calmly on a copy before any customer sees them. A rebuild is moving the entire business house - and like every move, it carries the risk that something gets lost or broken on the way.

Then there is time. A redesign is usually weeks, not months. The sooner the store sells better, the sooner the investment pays for itself - and you are not waiting half a year to see the effect.

That is why my default recommendation is simple: first we check whether a redesign is enough. I propose a rebuild only when the foundation genuinely calls for it - and then I say so plainly, with a specific reason, not “because it will look nicer this way”.

How to settle this for your own store

Do not guess and do not spend blind. The order is simple: measure first, decide second.

Send me a link to the store. I will check whether the foundation is healthy, where carts are leaking and whether in your case a redesign is enough or a rebuild is genuinely needed. You get a concrete answer with a reason - not “it depends”. If a redesign is enough, I will say so and price it. If it is not, you will hear that too, before you spend a zloty.

Frequently asked questions

Will a redesign hurt my Google rankings? In a redesign on the existing foundation, product and category URLs stay untouched, so to Google it is the same page, only better. The risk only appears when the URL structure changes - and then the remedy is a one-to-one redirect map prepared before launch, not after the fact. As a side effect, a redesign usually helps in search, because it improves speed and the mobile version.

How long does a redesign without a full rebuild take? Usually weeks, not months - because I am not recreating payments, integrations, products or customer accounts, only replacing the layer the customer sees. I give a specific deadline after looking at the store, because the number of templates and how heavily the theme was hand-modified make the difference.

How much does a store redesign cost? I bill projects at a fixed price agreed up front, usually in the 5,000-10,000 PLN net range (Polish market rates), depending on scope. A redesign is cheaper than a rebuild for a simple reason: you pay for the look and the shopping comfort, not for recreating logic you already have. You get the scope and the amount in writing before the start.

Will the store be offline during the redesign? No. I prepare the changes on a copy of the store, and they go to production only once they are finished and checked - the store keeps taking orders the whole time. The switchover itself is a short operation that I schedule outside peak hours.


Running a store where something does not work the way it should? I build and rebuild WooCommerce stores - from a single fix to reworking the whole sales flow. Tell me what you are dealing with and I will send back a scope and a price.

§ Quote in 24h

Your store is slowing down or looks dated, and you do not know where to start?

Describe the scope in two sentences or send a link to your store. I tell you what to fix first, and you get a fixed bid in writing within 24 hours - no "from X" pricing.

Send your scope - quote in 24h