Headless development

Headless commerce development for stores that have outgrown their theme

We measure your theme first, then build a storefront and content system in code you own, with Shopify or BigCommerce kept for products and checkout.

Get a stay-or-go recommendation
Trusted by the world's fastest-growing brands

Portfolio · selected work

The work, not the deck.

Every site below is live and owned by the client. Each window is a capture of the real page, not a drawn mockup.

Categories we work across
HospitalityFinancial servicesManufacturing and exportConsulting and researchRecruitmentD2C
urjalifes.inUrjalife's Pravaah resort website: rooms, activities and dining across a photographic homepage.
UrjalifeHospitality
adventswealth.comAdvents Wealth website: a financial planning homepage covering wealth building, tax and retirement.
Advents WealthFinancial services
syounaa.inSyounaa website: a wellness apparel storefront built around smart-textile product ranges.
SyounaaWellness apparel
infokool.comInfokool website: a precision cooling manufacturer, with an outdoor cabinet product grid and capability sections.
InfokoolManufacturing
howardjohnsonhinton.caHoward Johnson Hinton website: a mountain-lodge hero over a room-booking bar, followed by renovated room types.
Howard Johnson HintonHotel
sycamoreconsultant.comSycamore Consultancy website: a recruitment agency, with separate paths for employers and candidates.
Sycamore ConsultancyRecruitment
stutiexports.comStuti Exports website: a technical fibers and specialty yarns exporter, with core markets and capability sections.
Stuti ExportsTechnical textiles
duhomespg.inDuhomes website: student housing, with walking distances to nearby colleges and a room rate table.
DuhomesStudent housing
vaspro-global.comVasPro Global website: a technical advisory and project consulting firm, with expertise and mission sections.
VasPro GlobalConsulting
pretor.aePretor website: a marketing research and promotion consultancy, opening on research, strategy and growth planning.
PretorMarketing research

What the work is

Three parts, each changeable on its own

Headless commerce keeps a store’s three jobs apart: showing products, holding content and taking orders. Each runs as its own system, and APIs pass data between them.

Trail pack 40 LIn stockAdd to cartSize guideStorefrontNext.js, 5 templatesRenders 1,922 URLsCommerce platform1,820 products64 collectionsCart and checkoutContent system38 content pages

The storefront

A Next.js application, written for your design and your products. Pages render on the server or ahead of time, so phones and crawlers get finished HTML, as they do from a theme.

The content system

A headless CMS such as Sanity holds the guides, size charts, landing pages and campaign copy. Editors publish without a developer, and the same entries can feed the site, email and an app.

The commerce platform

Shopify, BigCommerce or your current platform keeps the catalog, inventory, cart and checkout. You keep the back office your team already knows, and the storefront reads from it through its API.

Two ways to build the storefront

A theme on your platform or a storefront of its own

Both are sound ways to run a store. We recommend the theme for a store that sells well on one, and the custom storefront when the limits below are costing you money.

ThemeA template that runs inside your platformHeadless storefrontCustom code that reads from your platform
Where the page is builtIn the platform’s theme system, from sections and app blocksIn your own application, with markup written for each template
Design freedomThe layouts the theme and its section settings allowAny layout your designer can draw, because the code is written for it
ContentPages and blog posts inside the platform’s own editorA separate CMS with structured entries that editors, email and apps can share
What it costs to runThe platform plan and the apps you install, with changes made in the theme editorHosting for the storefront and the CMS, plus developers for changes to the code
Best whenThe catalog is small, the theme meets the design and nobody on staff writes codeSpeed, design or several storefronts decide sales, and a developer is on call
Our recommendation rests on a measurement

If a theme passes Google’s thresholds on a phone and your team can make the changes it wants, stay on it. A headless build adds a codebase to maintain, which makes sense only when the theme is the constraint. The first deliverable below is the measurement that settles it.

What the sources say

Six facts to weigh before you go headless

Each comes from Google, Shopify or the Next.js docs, with the page and the date we read it.

  1. DefinitionShopify docs

    Shopify defines headless commerce as separating a storefront’s frontend from its backend.

    You build the frontend, and Shopify’s APIs supply products, the cart and checkout. Shopify’s Storefront API serves products, collections, search and the cart, then hands the customer to Shopify checkout. So the theme goes, and Shopify’s catalog, cart and checkout stay.

  2. Speed targetsCore Web Vitals

    Google rates a page as good when its largest content paints in 2.5 seconds or less, interaction responds in 200 milliseconds or less and layout shift stays at 0.1 or less.

    Each is judged at the 75th percentile of page loads, split by mobile and desktop. That means three in four real visits must meet the number, so a fast test on a developer’s laptop does not count. These are the targets our templates are built and measured against.

  3. Speed and salesGoogle, 2020

    A study of 37 brand sites found that a 0.1 second improvement across four mobile speed metrics went with an 8.4% gain in conversions on retail sites.

    Google commissioned the study, and 55 and Deloitte ran it over more than 30 million sessions in late 2019. The sites ran in Europe and the United States. It reports an association from the sampled brands, so treat 8.4% as evidence that speed matters, not as a forecast for your store.

  4. SearchGoogle Search Central

    Google can run JavaScript when it renders a page, and still advises server-side rendering or pre-rendering.

    Google’s guide says those approaches make a site faster for users and crawlers, and that not all bots can run JavaScript. A storefront that ships finished HTML is readable by crawlers that do not run JavaScript. The guide does not say rendering is required for Google.

  5. Fresh contentNext.js docs

    Next.js can serve a stored page instantly and rebuild it in the background, and a publish in the CMS can trigger that rebuild on demand.

    With time-based revalidation, the next visitor after the interval gets the stored page and a fresh version generates behind it. On-demand revalidation instead invalidates a path or a tag when your CMS or platform sends an event. That is how a price change reaches a stored page in seconds instead of at the next build.

  6. Shared cacheNext.js docs

    When Next.js runs on several servers at once, an on-demand refresh reaches only the server that receives it, unless the servers share a cache.

    The documentation says the default file-system cache belongs to each instance, and recommends a shared cache handler to coordinate. Hosting that manages this is one reason the written scope prices the hosting setup. On a theme, the platform handles it.

What the work includes

What the headless build hands over

The written scope names the templates and platforms; each card ends with the file or account you keep.

Storefront assessmentGo headless0 s2.5 s4 sHome11 app scripts3.4 sCollection13 app scripts3.9 sProduct14 app scripts3.6 sCart9 app scripts2.8 sField data, phone, 75th percentile

Storefront assessment

We measure your main templates on a phone against Google’s thresholds and count the apps loading scripts. Then we say stay on the theme or go headless, with the numbers. You receive: the assessment and a written recommendation.

Phone field dataApp scriptsTheme limits
Build plan38 developer daysTemplateDays010203038Home5Collection9Product page12Cart handoff4Content pages8Approval on staging, one template at a time

Storefront in Next.js

We build the home, collection, product and cart templates as a Next.js application that sends finished pages. Product data comes from your platform’s API. You receive: the application in a repository you own, and a staging site to review.

Next.jsTypeScriptServer rendering
ContentUnpublished changesGear guidesSize chartsLanding pagesBannersTrail pack sizingShown onTrail pack, 40 L+ 1Also used inSiteEmailPublishing refreshes 2 pagesPublish

Content in a headless CMS

Guides, size charts, landing pages and banners move into a CMS with fields shaped for them, so editors publish without code. A publish refreshes the affected pages. You receive: the CMS project in your account and an editor guide.

SanityStructured entriesEditor roles
What syncs and whenPlatformWhenStorefrontPrice or stockWebhookPage refreshedNew productWebhookPage builtCartLiveCart updatesCheckoutHandoffCheckout button1,820 products and 64 collections

Platform connection

We connect the storefront to your commerce platform for products, inventory, cart and the handoff to checkout. Webhooks refresh prices and stock on the stored pages. You receive: the integration code and a map of what syncs and when.

Storefront APICartWebhooks
URL map1,922 mapped1,904of 1,922 URLs keep their path1,904 keep their path18 redirected/pages/fit-guide/guides/fit301/blogs/gear/stoves/guides/stoves301+ 16 more in redirects.csv

Search, URLs and structured data

We keep existing paths wherever we can, redirect the rest with a map, and add product, price and availability markup to the new pages. Sitemaps are rebuilt. You receive: the URL map and a before-and-after crawl comparison.

URL mapProduct schemaSitemaps
Accounts4 in your nameHostingRepositoryCMSError monitorMembersSample Outdoor Supply Co.Owner since day oneOwnerWWebzeniaRemovable by the ownerMemberrunbook.mddeploy · roll back · renew

Hosting, monitoring and handover

Hosting, the repository, the CMS and the error monitor are set up in accounts in your name from day one. We write down how to deploy, roll back and renew. You receive: the logins, the runbook and a walkthrough with your team.

Your accountsError alertsRunbook

How it runs

Assess, design the split, build, cut over

You approve each template on staging before it goes live.

storefront-assessment.csv

Storefront assessment

Sample · Sample Outdoor Supply Co., Denver, CO
TemplateMobile LCP, 75th percentileScripts from apps
Home3.4 s11
Collection3.9 s13
Product3.6 s14
Cart2.8 s9
None of the four shopping templates reaches Google’s 2.5-second threshold, and the apps behind those scripts run reviews, filters and subscriptions the store keeps. Recommendation: go headless on Shopify, keep Shopify for products and checkout, and move content to Sanity.

Our stack

The tools behind the storefront and the content

What we build with, host on and monitor with. Pick one for the detail.

Next.js
Why Next.js

Next.js is a React framework that renders pages on a server or ahead of time and sends finished HTML.

How we use it

It runs the storefront: collection and product templates, the cart and the refresh of stored pages when prices or content change.

SpeedSEO-readyRendering
Next.jsSSR
WordPressPHP
DIY builderClient

Questions

Headless commerce development, answered

Start here

Find out if a headless storefront fits your store

Tell us where your products live and what is slowing you down. We’ll send back a written recommendation and the measurements it rests on.