Redesign or rebuild your online store? Start with what is actually wrong.
Separate design problems from operational limits before replacing your store. A decision table, a useful brief and a safe way to test the changes.
Alphabite · Ecommerce design and development team ·
A store you dislike does not automatically need a new platform. First separate how it looks, how customers use it and what your team cannot do. Those are different problems with different costs.
Describe the failed task, not just the look.
“Make it more modern” leaves too much room for interpretation. “Customers cannot tell which size is selected on mobile” gives the team something they can reproduce and fix. Collect five examples like this before asking for a proposal.
Include your own working day. If staff retype orders into a courier portal, changing the homepage will not remove that task. Keep design requests and operational requests in separate lists.
What kind of work does the problem need?
Use this as a starting point for an assessment, not a verdict on your platform. A theme limitation and a platform limitation are not the same thing.
| What you observe | First thing to investigate |
|---|---|
| Products are hard to compare or understand | Product information, images, variants and page layout. |
| Checkout is difficult on a phone | Reproduce the flow and inspect errors before redesigning it. |
| Staff copy information between systems | An integration or a change to the order workflow. |
| A required business rule cannot be implemented reliably | Technical assessment of extension versus rebuild. |
Ask for a working example before approving the whole redesign.
Choose one demanding product, one collection and one mobile purchase journey. Include a long title, unavailable variant and delivery restriction. A beautiful desktop mockup with ideal content cannot demonstrate these cases.
For The Clashers, books, 19 and ClashVit needed distinct product presentation within the same store. The useful question was how to give each range the right context, not how many decorative sections to add.
Keep what already works.
If a rebuild is justified, list the URLs, product records, customer accounts and connected systems that need to survive the change. Plan redirects and a test order before switching traffic. A new design should not quietly discard search visibility or a working fulfilment process.