Describe the specific change first
Write down what customers should see or do on a particular page. “Make the store look premium” is difficult to test. “Show materials and included items above the purchase button” is a concrete requirement.
Collect examples and identify page types: home, product, collection, search or cart. State whether the change applies to all products or a group. This helps decide between a global setting, a template and product-specific data.
Prepare a theme copy and test scope
Duplicate the theme before making changes and name the copy clearly. Preview it before publication. Record the original state and document changed files or settings.
A theme copy is not a full store copy. Product data and other global settings are shared. Changing real products for a test can affect the live store. Use safe examples and agree a suitable test environment for larger changes.
What the theme editor can change
The editor exposes the settings, sections and blocks provided by your theme. These may include colours, fonts, header, images and product content. Available features depend on the theme and its version.
Start with existing capabilities. A section that already meets your needs does not need rebuilding. Check long text, multiple images and variant products: a layout that only works with a short example is not ready for general use.
| Change | First approach to check |
|---|---|
| Colours, type and logo | Global theme settings |
| Content order | Arrange sections and blocks |
| A different page for some products | Create and assign a separate template |
| Product-specific information | Connect metafields to suitable content elements |
| Reviews or size guidance | Existing feature or compatible app block |
| Special interaction | Define a theme-code or app requirement |
Use templates and metafields deliberately
Several products may use one product template. Changing its structure affects those assigned products. To give a group a different layout, create a separate template and check assignments.
Metafields store extra data such as materials, care guidance or size information. Suitable theme settings can connect dynamic sources to these fields. Agree data types and maintenance responsibilities before populating a catalogue. Handle missing values sensibly.
When Liquid, CSS or JavaScript is needed
Liquid connects theme templates to Shopify data. CSS controls appearance and JavaScript can add interactions. Code is useful for a defined requirement beyond available settings, such as a custom section or variant presentation.
Keep changes limited and documented. Check keyboard access, loading behaviour and failures alongside appearance. Changing a displayed price in a theme does not change checkout price calculation. Business logic must be implemented at the appropriate system point.
Add apps and understand their boundaries
Compatible apps provide blocks in supported sections. App embeds are activated separately and can provide overlays or invisible functionality. After changing themes, verify that required integrations are active and positioned correctly.
A background-processing app differs from a theme block. ERP and accounting synchronisation need an integration. Standard theme app blocks also do not customise checkout pages; see Shopify checkout customisation.
Test the complete theme change
Test actual page types beyond the homepage. Use mobile and desktop, long product names, several variants and an empty cart. Check pages without optional content too.
Agree acceptance criteria for larger changes. Customers should be able to choose the correct variant, the purchase button should remain accessible, and a size-guide interaction should work by keyboard.
- Check home, product, collection, search and cart pages.
- Cover long text, absent images and sold-out variants.
- Verify keyboard access to menus, forms and interactions.
- Check app blocks and embeds in the new theme.
- Place a test order with discount and shipping.
- Approve the preview and document a previous version for fallback.
Plan cost and theme updates
Effort depends on page types, interaction requirements, data quality and test coverage. Adding one section differs from rebuilding a theme. Describe these differences when requesting customisation.
Reconcile theme updates with your custom changes. Check what carried over, conflicts and app behaviour. Purchased themes, custom code and ongoing support have separate licensing and costs. See commissioning a Shopify store for project planning.
