Ecommerce Website Developer

01Service

Custom and bespoke ecommerce development

For retailers whose catalogue, checkout or integrations have outgrown what a template platform will do without a fight. Built in React and Next.js, with the commerce engine chosen to suit the business rather than the other way round.

  • Next.js and React
  • Engine chosen per project
  • You own the code

02Judgement

When bespoke is the right answer

Bespoke is not better. It is a trade: more control and more ownership, in exchange for more cost and more maintenance. These are the cases where that trade usually pays.

  1. Your catalogue does not fit the template model

    Made to order items, configurable products, bundles priced differently from their parts, trade pricing per customer, or stock held across several locations. Template platforms can be bent to these, and the bending is usually where the cost goes.

  2. The checkout needs to behave differently

    Split delivery, part payment, quote to order, purchase order approval, or delivery rules that depend on the product rather than the basket total. If a platform forces you to explain your own rules to your customers as exceptions, that is a sign.

  3. An integration is the actual product

    When the shop is a front end to an ERP, a stock system or a manufacturing process, the integration is the hard part and the storefront is the easy part. Building the storefront bespoke lets the integration define the model rather than fighting it.

  4. Performance is a commercial constraint

    Large catalogues, heavy imagery, or customers on mobile connections where every added second costs orders. A bespoke front end lets you control exactly what is sent and when.

03Counter case

When it is not

We would rather tell you this at the enquiry stage than halfway through a build.

  • A straightforward catalogue that a well configured Shopify or WooCommerce build handles properly. Bespoke would cost more and do less.
  • A business that needs to change everything itself, frequently, without a developer. A template platform with a mature admin is usually kinder.
  • An idea that has not been validated yet. Prove people will buy before paying to have the shop built from scratch.
  • A tight deadline with no appetite for ongoing maintenance. Bespoke means you own the code, and owning code means maintaining it.

04Technology

What it is built with

The stack is chosen per project. This is what we actually work in, and when each one earns its place.

Next.js and React
The default for a bespoke storefront. Server rendering means product pages arrive as HTML rather than waiting for JavaScript, which matters for both customers on slow connections and for crawlers. React handles the parts that genuinely need interactivity, such as variant selection and basket state.
Headless commerce
A commerce engine handles catalogue, pricing, tax and orders, and a separate front end renders the shop. It suits retailers who need unusual merchandising or several channels from one catalogue. It is more moving parts, so it is the right answer less often than it is proposed.
TypeScript throughout
Catalogue and order data has a lot of shapes, and most ecommerce bugs are a field that was not what the code assumed. Static types catch a useful share of those before anybody sees them.
Node.js services
For the integration layer: stock synchronisation, order routing, fulfilment callbacks and anything that has to keep working when a third-party system is slow or unavailable.
WordPress and WooCommerce
Still the right answer for a smaller catalogue where the client wants to edit everything themselves. A bespoke front end can sit on top of WooCommerce where the admin suits the business but the storefront does not.
PostgreSQL and Redis
Relational storage for anything that must stay consistent, such as stock and orders, with caching in front of the read paths that get hit hardest.

05Process

How a bespoke build runs

  1. Model the catalogue first

    Before any interface work, agree how products, variants, bundles, pricing and stock actually behave, including the awkward cases. Nearly every expensive late change traces back to a catalogue model that was decided by assumption.

  2. Prove the integrations early

    Connect to the stock, order or ERP system in the first phase rather than the last, with defined behaviour for the case where it does not answer. Integrations discovered late are where bespoke projects overrun.

  3. Build the storefront in reviewable slices

    Category, product, basket and checkout, each on a staging environment you can use, with accessibility and performance checked per template rather than audited at the end.

  4. Hand over something maintainable

    Documented architecture, environment configuration, a tested restore procedure and a runbook. You own the code: you should be able to give it to someone else and have them understand it.

06Reading

Related material

Abstract measured panel in the brand colours

Article · 2 min read

Monitoring that reaches a person

An alert nobody receives is a log entry with extra steps. Deciding who gets woken is part of the system design.

Not sure whether you need bespoke?

Describe the catalogue and the rules that do not fit. If a template platform would serve you better, we will say so.