Skip to content
Services

Six ways we ship ecommerce code.

We are builders, not marketers. Every engagement below is scoped by a developer, built in your theme or codebase, and handed back as code you own. No page-builder apps, no process layers, no retainer you cannot cancel.

Liquid Shopify 2.0 WordPress GA4 GTM REST / GraphQL
Landing pages

Campaign and product pages hand-coded as native Shopify sections or standalone HTML. Your team edits copy, images and order in the theme editor. Ships in days, loads in under two seconds on mobile.

Section-based 0 builder apps
Shopify development

New builds, redesigns and custom features on Shopify and Shopify Plus. Liquid, Online Store 2.0 sections, metaobjects, B2B catalogues and checkout extensions. We work in a duplicated theme and hand over a documented diff.

Liquid Plus / B2B
WordPress development

Custom themes and blocks for content sites that sit next to a store. Editors get the fields they need and nothing else. Plugin count stays low because the layout is in the theme, not in a builder.

Custom themes ACF blocks
UX and conversion

We read the session recordings and the funnel, write one hypothesis per test, then build the variant in code. PDP, cart and checkout first, because that is where the money leaks. You get the result and the winning code, not a slide deck.

A/B tests Core Web Vitals
Tracking and analytics

GA4 and GTM set up server-side where consent allows, with the full ecommerce event set from view_item to purchase. Every event is verified against real orders, so the numbers in your dashboard match the numbers in Shopify.

GA4 / GTM Consent mode
Integrations

ERP, PIM, 3PL, subscriptions and CRM wired to Shopify through the Admin and Storefront APIs. Jobs retry, failures alert, and the mapping is documented so the next developer does not have to reverse-engineer it.

Admin API Webhooks
How we work

Scoped in days, shipped in weeks.

You talk to the developer who does the work. Four steps, no account manager in between.

01
Audit and scope

We look at the theme, the analytics and the blockers, then send a fixed scope with a price and a date. One business day, no discovery workshop.

02
Build in a branch

Work happens in a duplicated theme or a git branch. Your live store is never the staging environment.

03
Review and measure

You get a preview link, a QA checklist and before/after numbers measured on mid-tier Android over 4G.

04
Ship and hand over

We deploy, watch the first days of data, and hand over documented code. Support after launch is optional, never locked in.

Start a project

Send the store URL, the platform and what is in the way. Reply within one business day, from the developer who would do the work.