Services / Headless Commerce and Product Data

Headless commerce, product data and integrations

For agencies and e-commerce brands whose product data has outgrown the store. We model products, connect PIM and ERP systems and build headless storefronts.

Discuss a project

Why this approach

Product data first

We start with products, variants, attributes and categories, and the system that owns each one. The platform choice follows from that model.

PIM and ERP connections

We connect your PIM and ERP to the store, so products, stock and orders stay in step. Each field has one owner, and each sync has a clear direction.

Shopify or MedusaJS

We build on the platform that fits your catalogue and the team that will run it. Shopify is hosted for you, and you host MedusaJS yourself.

Storefront and content

A Next.js storefront reads products from the commerce platform and editorial content from Sanity. Your team runs pages and campaigns. We handle changes to the storefront code.

Stack

Next.js: Storefronts with server rendering and caching
React: Product pages, filters and cart
TypeScript: One type system from product data to page
Node.js: PIM, ERP and payment integrations
Shopify: Hosted commerce platform
MedusaJS: Open-source commerce engine
Sanity: Editorial content next to product data
Azure: Cloud hosting and services

Process

01
Describe the catalogue
Tell us about your products, your current platform, the systems around it and your timing. We reply with questions or a time to talk.
02
Map the data
We map products, variants and attributes, and which system owns each one. You get the data model and the integration plan in writing.
03
Build and connect
We build the storefront and the integrations in your repository and your tools. Each week ends with a short demo of software that runs.
04
Launch and stay on
Documentation, access and a walkthrough are part of the plan. Most clients keep working with us on new features and upkeep.

Questions

What is product data modelling for e-commerce?

It decides how products, variants, attributes, categories and prices are structured, and which system owns each one. A clear model makes filters, feeds and integrations simpler to build. We agree it before the storefront work starts.

Can you connect our PIM to the store?

Yes. PIM integrations are part of our long-term partnership with IONA, shown on our work page. We agree which fields the PIM owns, when data syncs and what happens when a sync fails.

Do we need to replace our commerce platform?

Not always. A headless storefront can sit on top of your current platform, and some problems are only in the data or the integrations. We tell you what needs to change and what can stay.

Do you work with headless Shopify?

Yes. In a headless Shopify build, Shopify keeps products, checkout and orders, and a separate storefront reads from it. Samphire, one of our projects, runs on Next.js, Shopify, Sanity and Stripe.

How do you choose between Shopify and MedusaJS?

We look at the catalogue, the custom logic you need and the team that will run the platform. For a MedusaJS build, see MedusaJS development and our work for House of Massive. For advice before you commit, see web development consultancy.

Who hires you for headless commerce?

Agencies come first for us, when a client project needs commerce development. E-commerce brands hire us directly as well. We join as your development team, as a development lead inside a larger team, or as consultants.