Refactoring a theme without a redesign budget
A theme refactor is the project nobody will fund, because it produces no screenshot. Done in the right order it is also the one that makes every later change cheaper.
AUTHOR
Director at Lucent Commerce. 22 posts, newest first.
A theme refactor is the project nobody will fund, because it produces no screenshot. Done in the right order it is also the one that makes every later change cheaper.
Peak does not bring new questions, it brings the same five at ten times the volume. Every one of them can be answered in October, on the page where it gets asked.
Every ticket is a customer paying you in their own time to report a defect. Most stores treat that as a cost to reduce rather than the cheapest research they will ever get.
A readiness checklist is what you do in October. A runbook is what someone opens at 2am with a phone in one hand and no time to think.
A freeze that stops everything gets broken by the first urgent request and then means nothing. Freeze the things that cannot be undone from the admin, and leave the rest open.
A review that produces forty comments produced nothing. Automate the nitpicks, then spend human attention on blast radius, Liquid cost and who owns the setting.
Changing the architecture and keeping the design is a legitimate project, and a harder sell than a redesign. It is also the one that pays back.
Nothing you build in the last week will beat anything you rehearse in it. The work is proving the discounts, the rollback and the rota, and saying no to everything else.
Most ecommerce roadmaps are a list of things somebody wanted. This is how to build one that survives contact with a trading year.
Sections, blocks and settings each solve a different problem. Using the wrong one is how a theme becomes unmaintainable.
NEXT STEP
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritized list of fixes.