After two decades of shipping online stores, the pattern is clear: rebuilds rarely fail on technology. They fail on decisions nobody wrote down.
Every few years, a business decides its online store is holding it back. The answer, almost always, is a rebuild. And almost always, the rebuild takes twice as long as planned.
The problem is rarely the platform
Teams spend weeks comparing platforms. That comparison matters far less than the questions nobody asks:
- Who owns the product catalogue after launch?
- Which reports does the finance team actually open every week?
- What happens to the URLs that bring in organic traffic today?
A rebuild is a business decision dressed up as a technology project.
Write the decisions down
Before a single screen is designed, write a one-page brief that lists what must not break. Traffic, integrations, the checkout flow your repeat customers already know.
- List every page that earns revenue.
- Map every redirect before you migrate.
- Agree on one person who can say "no".
What good looks like
A good rebuild is boring. Launch day is quiet, traffic holds, and the team wonders why they were nervous. That calm is the result of decisions made months earlier.
Have a project like this in mind?
Let's talk
About the author
Tony John
Engineer, e-commerce consultant and digital marketer with twenty-four years in IT. He writes about making technology less complicated for business, drawing on real projects in online stores, marketing and software. His articles are short, practical and written for people who run a business rather than a server room.
More about Tony