Redesign vs platform replacement: Start with a shopper task: find product, choose variant, check out; Test theme, content, app or code before considering platform replacement; Use Lighthouse scores (60+ avg) to validate fixes in development store
Image: Commerce Platform Guide

Replatforming

Part of Ecommerce themes and storefront performance

Separating visual redesign from platform replacement

A dated-looking storefront does not automatically need a new commerce platform.

A dated-looking storefront is not, by itself, evidence that its commerce platform is the problem. Trace a failed shopper task to the theme, content, app or code first; consider replacement only when a tested requirement remains beyond the platform’s capabilities or reasonable operating limits.

Diagnose the problem at the smallest useful level

Start with a concrete task: finding a product, choosing a variant, understanding delivery, checking out or updating content. Record exactly where the task breaks, then ask whether the cause is theme layout, product data, an app, custom code or a platform capability. A shopper-facing symptom alone does not identify the cause.

Shopify’s “Performance best practices for Shopify themes” names Liquid, images, JavaScript, CSS and fonts, and resource hints and CDN as areas to check within a theme. The guide identifies render-blocking stylesheets and scripts as common reasons First Contentful Paint is late, and images without dimensions, late font swaps and app-injected content as common causes of Cumulative Layout Shift.

Use the performance measures to locate the fault: First Contentful Paint tracks the first text or image, Largest Contentful Paint usually tracks the main hero or product image, Cumulative Layout Shift tracks unexpected movement, and Interaction to Next Paint tracks visible response after a tap or click. Main-thread JavaScript can slow Interaction to Next Paint; these are examples of implementation problems to investigate before proposing a replacement.

Shopify requires themes submitted to its Theme Store to average at least 60 on Lighthouse across the home, product and collection pages, and says merchants can run similar tests in a development store. Test a revised theme or page template with the same catalogue and integrations; if it fixes the task, the issue was not a platform capability gap.

Visual Redesign vs Platform Replacement: Key Considerations

  • Focus areaTheme, content, app, or code
  • Primary indicators to testFirst Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift, Interaction to Next Paint
  • Common causes of poor performanceRender-blocking scripts/styles, images without dimensions, late font swaps, app-injected content
  • Platform replacement triggerRequired capability cannot be met after testing theme/content/app changes

Steps to Diagnose a Shopper Task Failure

  • Identify the specific shopper taske.g., finding a product, checking out, updating content
  • Record where the task breaksAt theme layout, product data, app, custom code, or platform capability
  • Test performance metricsCheck First Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift
  • Validate fixes in a development storeUse same catalogue and integrations to test revised theme
  • Decide based on outcomeChoose redesign if task is fixed; consider replacement only if capability gap remains

Price the full decision

For an Australian planning anchor, a professional redesign for an established business is quoted at AUD $12,000–$60,000+ in 2026, with many medium-sized businesses investing AUD $18,000–$35,000. Those figures describe website redesigns, not a like-for-like platform replacement quote; scope and complexity affect the cost.

Compare written proposals against the same required outcome. Include design and templates, content and data transfer, integration work, staff training, testing, search and checkout continuity, maintenance and future changes; account for recurring platform and app costs over the same period.

Keep the visual brief separate from the platform requirements. For each required selling model, integration path, level of control and operating cost, write down what the current platform must do and test that requirement in a working proof using the relevant workflow.

Choose a redesign when a theme, content, app or code change fixes the shopper task and the required capabilities pass the test. Choose replacement when a required capability or integration path still cannot be met reasonably after that check; a new platform can otherwise carry weak product content and navigation into a more expensive system.

When to Choose Visual Redesign Over Platform Replacement

  1. Isolate the issue to theme, content, app or code?Use performance audits and user task testing
  2. Test fixes using a proof-of-concept in a dev storeEnsure improvements meet required outcomes
  3. Confirm capability gap persists after fixesIf yes, consider platform replacement
  4. Avoid replacing platform with weak contentDo not carry over poor UX into a more expensive system

More from Replatforming