April 2026
Shopify CRO Redesign
a mobile-focused os 2.0 rebuild of the kits uk buying path, with GA4 tracking on every key page
Ecommerce
Shopify
Role
AI product builder
Timeline
6 April to 14 May 2026
team
platform
Shopify OS 2.0, Prestige theme Redesign
The store fully redesigned:
Kits.style is an automotive styling retailer: body kits, badges, wheels, exhausts, lowering and fitting. i customised their Prestige theme for shopify os 2.0, and the work was mobile-focused and CRO optimisation plan.
What I changed on the buying path
The homepage gained a video hero and trust cards. Product pages got reworked stock, delivery, fitting, trust, and payment information, plus a sticky buy bar. Collections got category icons, quick filters and sorting. The cart drawer now suggests related products and carries fitting appointment context, and i repaired the booking app's buy controls after async rerenders kept replacing them.
design system
i built a token system for colour, type, spacing, radii and motion. black and charcoal surfaces, red for actions, gold for premium, green for trust. Exo 2 is the display type; Inter is the body. The tokens replaced duplicated colours and hard-coded values.
decisions that mattered
On mobile, I capped the gallery height so the title, price and buy button appear sooner. i made the product page button the single source of button styling, and consolidated the button rules behind it. the comparison slider was the worst bug: logical css properties and base-theme specificity kept fighting physical overrides, so the fix reset both in one block. i also abandoned one idea: the design-system css loaded asynchronously, but a blank-page bug pushed it back to blocking. the comments still estimate what async would have gained... those numbers were never measured, so they stay out of this story.
How I worked with ai
Claude assisted with some commits. i also defined agent roles for the workflow: architect, coder, reviewer, tester and security. One review pass resolved 96 recorded violations. The evidence covers defined roles and real commits, but it doesn't say which role wrote which line, so i won't guess.
measurement
custom tracking covers the key page types through the data layer, and ga4 collects those events. that's instrumentation, nothing more. the baseline i can defend: a local crawl on 12 april 2026 saw 150 pages, zero critical issues and 377 warnings, and a sitemap audit of 10 urls came back all 200. that's where i started from.
What's next
The 377 crawl warnings, mostly images and metadata, need to come down before I'd call the site clean. a seo app may be duplicating the theme's structured data, so that overlap needs resolving. and the blocking css decision is worth revisiting now the blank-page bug is understood.
No conversion numbers here. i don't have a before and after i can defend, and i'd rather publish nothing than a number someone has to trust. the real test of this project is whether the next person can pick up the theme, follow the tokens and fix a bug in minutes instead of days.