Themes, checkout, Functions. Apps. Built properly.

Custom themes and rebuilds, written to be edited. Sections and blocks that merchandisers can use without a developer on call, and a codebase the next person can read.

Most projects start from Dawn or an existing theme and end with a store the team can run themselves: new landing pages from the editor, product templates driven by metafields, and a deployment path that pushes one theme to every region.

Checkout.liquid is gone. Everything that used to live there is rebuilt as extensions: upsells, gift messages, delivery notices, order rules and post-purchase, styled to match the storefront.

Extensions run inside Shopify's checkout, so they work with Shop Pay, accelerated checkouts and the new customer accounts without hacks. The usual brief is a list of what the old checkout did, then a plan for what becomes an extension, what becomes a Function and what is no longer needed.

Server-side rules that run inside checkout. Hide a shipping rate for a postcode, reorder payment methods, bundle products in the cart, or block an order that breaks a rule.

Each Function ships with a small admin page so the store team can turn it on, adjust its settings and see what it is doing. Rules live in metafields or the app's own settings, not hard-coded, so a change is a form edit rather than a redeploy.

Embedded admin apps for the thing no app-store app quite does. Product personalisation, scheduled sales, size guides, tagging rules, internal dashboards.

Apps are built on Shopify's Remix template with Prisma and the Admin GraphQL API, hosted on Render or Fly, and monitored after launch. They are private to the store, so there is no app-review cycle and no monthly fee to a third party.

For brands that have outgrown a theme. A React storefront on Hydrogen, deployed to Oxygen, with the cart, accounts and markets wired to Shopify.

Headless is the right call when the storefront needs things a theme cannot do well: editorial content from a CMS, complex product configurators, or a design system shared with other properties. It is the wrong call for most stores, and the first conversation is usually about whether it is needed at all.

Automation for the jobs a team does by hand every week. Product data cleanup, tagging, reporting and internal tools built on the Admin API, plus training so staff can run them.

The AI part is practical: draft product descriptions from a spec sheet, classify support tickets, or summarise weekly sales into a note the team actually reads. Every workflow has a human check before anything touches the live store.

Wholesale on the same store as retail. Company accounts, price lists and payment terms configured in Shopify B2B, with the theme and checkout adjusted for trade buyers.

Most B2B projects replace a spreadsheet-and-email ordering process or a separate wholesale site. The store keeps one catalogue and one theme, with company-specific pricing, minimums and net terms handled by Shopify.

Plus features put to work. Flow automations, Launchpad for campaigns and a deployment process that pushes one theme to every regional storefront.

For multi-store brands the deployment side matters most: one theme repo, per-region settings, and a release process that means a change goes live everywhere at once rather than being copied by hand.

Moving a store to Shopify without losing what already works. Products, customers, orders and URLs carried across, redirects in place, and a theme ready before the switch.

The cutover is planned around trading: data is migrated and checked in a staging store, redirects are tested against the old sitemap, and the switch happens in a quiet window with a rollback plan.

Designs that are built to be built. Figma files that map to sections and blocks, so what the merchant sees in the editor matches the mockup.

Design and build by the same person means fewer handoff gaps. The Figma file uses the same names, spacing and type scale as the theme, and every screen is designed with the editor in mind.

Faster pages and fewer drop-offs. Audits that turn into a fix list, then the fixes themselves: scripts, images, layout shift and the checkout path.

The audit looks at real user data, not just a lab score. The output is a short list ranked by effort and impact, and most of the wins come from removing things rather than adding them.

Keeping a live store healthy. A fixed block of hours each month covers the small changes, app updates and the quarterly platform shifts Shopify ships.

Retainers suit stores that have a steady flow of small requests and no in-house developer. Work is logged, hours roll into a monthly summary, and larger projects are quoted separately.