01
Catalogue & merchandising
Products, variants, bundles, collections and metadata modelled around your real range, with fast search and filtering built in.
- Variants & options
- Bundles
- Collections
- Search & filter
Own your checkout, kill the platform tax
Bespoke ecommerce, built around your business.
Bespoke ecommerce means a headless, hand-coded store, engineered on Node.js and Next.js, with a Stripe-native checkout you actually own. Instead of paying a platform tax and bending your business to fit Shopify or WooCommerce, we model your catalogue, pricing, tax and fulfilment rules around how you really sell, integrate Stripe for payments and subscriptions, build the operator tools your team needs, and hand you an auditable codebase with the customer data in your own database.
Commerce operations · system view
Revenue · today
£0 +12.4%
0.0%convert
Payment rails
Cards
Apple / Google Pay
Subscriptions
B2B · Net terms
Order stream
New order
#10472 · £184.00
Checkout pipeline · system view
A shopper browses, adds to cart and pays through Stripe. A signed, idempotent webhook confirms the order, fulfilment fires, and the data lands in a database you own. Every stage is yours, no platform tax in the middle.
01
Browse
Edge-cached
02
Cart
Server state
03
Stripe checkout
Cards + wallets
04
Webhook
Signed + idempotent
05
Fulfilment
Inventory synced
06
Owned data
Your database
Why you need this
The hidden cost of a hosted platform.
Pain 1
You pay a platform tax on every single order.
1 to 2% of GMV skimmed off the top, plus a stack of paid apps. At scale that is a full engineer's salary handed to a platform every year.
Pain 2
The platform fights how you actually sell.
B2B price lists, bundles, tax rules and fulfilment logic get patched with brittle $200/mo apps and manual ops work that never quite holds.
Pain 3
You do not own your checkout, data or speed.
A slow, locked-in checkout bleeds conversions to faster rivals, and you cannot fix it because you do not control the code.
Platform-tax calculator
What is the platform skimming from you?
Drag to your monthly sales. This is roughly what you hand to platform fees and the app stack each year, money you keep when you own a Stripe-native build.
£80,000
£5k£500k
Platform tax per year
£27,840
on £960,000 of annual sales
That is £139,200 over five years, often more than the cost of the custom build itself.
Estimate only, based on a blended platform + app overhead of ~2.9% of GMV. Your real figure depends on plan tier, apps and payment mix.
Built around your operation
We model how you really sell, then build the store around it.
The method
Five stages, from catalogue model to launch.
A repeatable build path: model the catalogue, integrate Stripe, build the operator tools, harden the webhooks, then migrate and launch on Core Web Vitals you can prove.
01
Model catalogue
Map products, variants, pricing, tax and fulfilment rules around how you actually sell, not a template.
CatalogueVariantsTax
02
Integrate Stripe
Stripe-native checkout, payment methods, subscriptions and the customer billing portal, wired for your flows.
Stripe CheckoutSubscriptions
03
Build operations
Operator dashboard for orders, inventory, refunds and fulfilment so your team runs the store, not a spreadsheet.
AdminInventoryFulfilment
04
Harden webhooks
Signed, idempotent webhooks with a dead-letter queue so no paid order is ever lost or double-processed.
IdempotencyDLQSignatures
05
Migrate & launch
Migrate catalogue, customers and SEO with redirects in place, then launch on Core Web Vitals you can prove.
Migration301sCWV
Commerce stack
You own every layer, top to bottom.
Layer 1 of 4
Storefront
Next.js RSC · edge-cached · Core Web Vitals
- Server components
- Edge caching
- SEO & schema
What's included
Every custom store ships with this.
- Headless Next.js storefront, hand-coded and fully auditable
- Stripe-native checkout with wallets, tax and subscriptions
- Product catalogue with variants, bundles and B2B price lists
- Operator dashboard for orders, inventory, refunds and fulfilment
- Signed, idempotent webhooks with a dead-letter queue
- Customer accounts and a self-serve Stripe billing portal
- Catalogue, customer and SEO migration with 301 redirects
- Core Web Vitals budget and conversion analytics wired in
What you receive
A store you run, not a platform you rent.
Commerce architecture diagram
A clear map of the whole stack: storefront, Stripe checkout, Postgres core and webhook operations.
Stripe checkout & portal
A fast, Stripe-native checkout and a self-serve customer billing portal for subscriptions and invoices.
Operator dashboard
The back-office your team runs the store from: orders, inventory, fulfilment and webhook event log.
Commerce capabilities
Six capabilities. One store you fully own.
From catalogue and Stripe payments to B2B pricing, subscriptions, operations and conversion performance, every capability is built into the codebase, not rented from an app marketplace.
Your team runs it
02
Stripe payments
Stripe-native checkout with cards, wallets, Stripe Tax and 3D Secure, so you take payments globally without a transaction tax on top.
- Stripe Checkout
- Wallets
- Stripe Tax
- 3D Secure
03
B2B & custom pricing
Customer-group price lists, quantity breaks, quotes, purchase orders and net terms for the way businesses actually buy from you.
- Price lists
- Quantity breaks
- Quotes
- Net terms
04
Subscriptions & billing
Recurring plans, trials, metered usage and a self-serve customer portal powered by Stripe Billing, with dunning handled for you.
- Recurring plans
- Trials
- Metered usage
- Dunning
05
Operations & fulfilment
An operator dashboard with order management, inventory truth, refunds, and idempotent webhooks feeding your fulfilment and ERP.
- Order management
- Inventory
- Refunds
- ERP webhooks
06
Performance & CRO
Edge-cached server components, a Core Web Vitals budget and conversion analytics so you can prove the checkout lift, not guess it.
- Core Web Vitals
- Edge caching
- A/B testing
- Funnel analytics
No lock-in. The stack we build your store on, all of it yours to own and extend.
- Next.js
- TypeScript
- Stripe
- Stripe Billing
- Postgres
- Supabase
- Upstash
- Vercel
- Stripe Tax
- PostHog
FAQ
Questions merchants ask before switching.
What is bespoke ecommerce?
It is a headless, hand-coded online store built on Next.js and Node.js with a Stripe-native checkout, instead of a hosted platform like Shopify or WooCommerce. You own the code, the data model and the checkout, and you model your catalogue, pricing and fulfilment around your business rather than fitting a template.
Why move off Shopify or WooCommerce?
Two reasons: cost and control. Hosted platforms charge a percentage of every order plus a growing stack of paid apps, and they constrain how you can model pricing, tax, B2B and fulfilment. A custom build removes the transaction tax, gives you rules that fit your business and lets you fix performance yourself.
Do you handle migration from my existing store?
Yes. We migrate your catalogue, customers and order history, set up 301 redirects to protect your SEO, and run the new store in parallel before cutover so there is no traffic or ranking loss at launch.
How are payments handled?
Through Stripe, natively. We implement Stripe Checkout or a custom checkout with the Payment Element, support cards and wallets like Apple Pay and Google Pay, wire up Stripe Tax, and verify everything with signed, idempotent webhooks so paid orders are never lost or double-counted.
Can you support B2B and wholesale pricing?
Yes. We build customer-group price lists, quantity breaks, quotes, purchase orders and net terms, alongside normal retail checkout, so the same store serves both B2C and B2B buyers.
Do you build subscriptions and recurring billing?
Yes. We use Stripe Billing for recurring plans, trials and metered usage, with a self-serve customer portal for upgrades, cancellations and invoices, and automated dunning to recover failed payments.
Will it be fast and good for SEO?
That is a core reason to go custom. We build on edge-cached server components with a Core Web Vitals budget, server-rendered product and category pages, structured data and clean URLs, so the store is fast for shoppers and legible to search and AI engines.
Will my team be able to run and extend it?
Yes. You get an operator dashboard for day-to-day work, a conventional codebase with named server actions, and a written runbook. Any senior engineer can read, operate and extend it, so you are never locked to us.
Ready to own your store?
Stop renting. Start building.
Bring your platform bill. We will show you what the same money builds when you own the store outright.
