Platform Governance
Part of Ecommerce platform governance
Reviewing unnecessary storefront customisations
Find theme and app customisations, judge the customer task they serve, and remove unneeded work through a controlled change.
Review a storefront customisation by asking what job it still performs, where it lives and what would happen if it were removed. A change may become unnecessary when a theme gains a suitable control, an app is retired or the business changes its offer. Its age alone does not answer the question.
Find the change before judging it
Start with the live theme and any available change record. List custom sections, app blocks and embeds, added CSS or scripts, and direct edits to theme files. Mark the page and customer task each affects. Ask what outcome was intended and whether that requirement remains.
On Shopify, the theme editor can change settings and arrange content without editing code. Apps can add blocks and embeds through that editor; direct theme code edits are another route. Shopify lets you work on a theme in draft before publishing it. Check how each specific change was made.
Question / Evidence to request
- Purpose
- The customer or staff task it supports now
- Location
- Theme setting, app component, custom CSS or code file
- Dependency
- App, product data, market setting or external script it needs
- Replacement
- A supported setting or simpler component serving the same task
- Removal result
- What should disappear and what must still work
Judge the customer result
A custom badge might repeat delivery information already on the product page. A selector might prevent an invalid choice. Both are examples to investigate, not findings about a real store.
Keep a customisation when removing it would make an important choice or instruction unclear. Simplify it when a maintained control can deliver the same result.
Review representative product and collection pages with real content, including an awkward product and a mobile view. Follow the affected task into basket or checkout where relevant. Before retiring a component that seems unused, check seasonal pages and market-specific layouts. A visual review alone cannot establish whether code supplies a hidden rule or data handoff.
Make removal a controlled change
Prepare a draft or staging version and record the intended difference. Shopify permits draft theme previews, but a preview cannot establish every live service path. WooCommerce advises a current backup and staging checks before software updates; for a custom theme change, confirm the appropriate backup and checking route with the people who maintain that installation.
Name the person who can restore the earlier presentation or repair a dependency. After release, inspect affected pages and tasks, including the order path if the change touched buying. Record what was removed, what replaced it and any remaining owner. If the purpose of old code cannot be established, investigate before approving its removal.
