dotCREA
TREN

Shopify theme customisation: get everything out of your current theme

We bring the theme you already use closer to your brand, add the sections it lacks, and fix the points that hold conversion back — without replacing it.

What does this service cover?

What most stores need is not a new theme but the right use of the one they have. Off-the-shelf themes ship with a wide set of options, and most of those are never switched on during setup.

In a customisation project we first separate out what can be solved with a setting; code only comes in where it is genuinely required. That way theme updates keep working.

Settings first, code second

Our order never changes: if the same result can be reached with a setting, we do not write code. Where we do write code, we follow the theme's own structure.

Anything solvable through theme settings is applied first
New requirements are written as theme sections, so your team can manage them from the admin
One-off code buried directly in template files is avoided
Every change is applied on a duplicate theme first, then published

The payoff for that discipline: when a theme update arrives, the work we did does not disappear.

Frequently requested customisations

A size chart, instalment information and delivery time block on the product page
Filter and sort layout on the collection page
A cart drawer and free-shipping threshold indicator
Reusable sections for campaign and landing pages
Improved menu and search behaviour on mobile
Accessibility fixes: contrast, focus states, screen reader labels

How we work

01
Audit
The current theme, installed apps and any custom code changes are reviewed; what can be solved through settings is separated out.
02
Priority list
Work is ordered by conversion impact and cost, with the reasoning for each item written down.
03
Implementation
Changes are built on a duplicate theme and submitted for your approval with a preview.
04
Launch and measurement
It goes live, and the effect on speed and conversion is tracked before and after.

Frequently asked

Not when it is done properly. That is why we write changes as theme sections and settings and avoid one-off code buried in template files. Where that is unavoidable, we document exactly what changed and where.