Pricing and quotation guide
Shopify theme customization cost
Theme customisation can cost almost nothing, when a change is a theme editor setting, or a substantial amount, when it means building and testing new sections across devices. The difference is rarely obvious from the request alone.
This page explains what decides the cost of a customisation and the longer-term costs that code changes bring with them.
Illustrative diagram
Theme customisation
- Editor changes
- Settings
- Templates
- New sections
- Build
- Device testing
- Core file edits
- Careful testing
- Higher update risk
- At each update
- Check log
- Re-apply if needed
Types of customisation and their effort
| Change | Usually done with | Relative effort |
|---|---|---|
| Colours, fonts, section order | Theme editor | Minimal |
| New product template for a product type | Theme editor | Small |
| Small style tweak the editor cannot reach | A few lines of CSS | Small |
| New custom section, such as a size guide | New section file and testing | Moderate |
| Changing how a core feature works, such as the cart | Code changes in core files | Larger, with update risk |
What drives customisation cost
- Editor or code
- Editor changes are quick; code needs writing, testing and documenting.
- Where the change lives
- New section files are contained; edits to core theme files take more care.
- Devices and browsers
- Changes are tested on phones, tablets and desktop, which takes time.
- App interactions
- Apps that alter the same pages can conflict and need checking.
- Theme quality
- Well-structured themes are faster to customise than heavily modified ones.
- Documentation
- Recording each change in your log adds a little time and saves much later.
Costs paid to third parties (separate from our fees)
- Paid theme licence, if changing theme
- App subscriptions for features you choose to add by app
Theme and app costs are paid to their developers and listed separately.
The long-term cost of code edits
Shopify's guidance on updating themes explains that theme editor customisations are copied to an updated theme, while code edits are only carried over if they do not conflict with the update. Code edits that do conflict must be copied into the new version by hand. Every code customisation therefore has a small recurring cost: checking or re-applying it whenever you update the theme.
That cost is manageable when changes are few, contained and logged. It grows quickly when they are scattered across core files with no record.
Per request or a block of changes
Per request
Suits you when
- Occasional changes
- Each change is independent
- You want to approve each cost
Watch out for
- Each request carries its own setup and testing
- Can cost more per change overall
Block of changes
Suits you when
- A list of related improvements
- A seasonal refresh
- Several templates affected
Watch out for
- Needs a clear, prioritised list
- One combined test and publish
Ways to keep costs down
Before asking
- Check whether the theme editor already offers the option
- Group related changes together
- Provide screenshots and examples
In the work
- Prefer new sections over core file edits
- Remove unused apps first
- Keep the customisation log current
Example: a list of six changes
Illustrative example — not a client case study
Situation: A store sends six requested changes for its product pages.
- Three can be done in the theme editor; we show the team how.
- Two need a single new section combining a size guide and delivery information.
- One needs a small CSS adjustment, added to a dedicated custom stylesheet.
What this shows: Only half the list needed paid code, and all code changes were logged. This example is illustrative.
App or custom code
Some features can be added either by installing an app or by writing a custom section. Apps cost a monthly subscription but are maintained by their developer; custom code has a one-off cost but becomes your responsibility to maintain through theme updates. For simple display features, custom sections are often cheaper over time. For complex features with ongoing data, such as reviews or subscriptions, an app is usually the better choice.
When an audit should come first
If a theme has been customised by several people over several years, the cheapest first step is often an audit rather than another change. An audit lists the code edits, leftover app code and unused sections, and estimates the effort to clean up or update the theme. Without it, each new request risks colliding with something nobody remembers adding.
Questions about Shopify theme customization cost
Why does a small change sometimes cost more than expected?
Testing across devices and checking app interactions take time, even for a few lines of code.
Can we avoid code altogether?
Often, if the theme is modern. Many changes are editor settings or alternative templates.
Do code changes cost more later?
They may need checking or re-applying when the theme updates, a small recurring cost.
Is it cheaper to buy an app?
For simple display features, custom sections can be cheaper over time. Complex features often suit apps.
Do you charge per hour or per change?
We usually quote per change or per block of changes, agreed in advance.
Is documentation extra?
Logging changes is part of the work, not an optional extra.
What does a theme audit cost?
It depends on how heavily the theme has been modified. We quote it as a fixed item after a first look.
Sources referenced
Platform features, guidance and rules change. We check the current versions before committing to an approach. This page is general information, not legal advice.
- Shopify Help Center: Updating themes (opens in a new tab) — reviewed 2026-10-22
Request a Custom Quote
Ask about Shopify theme customization cost
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.