
Article · 2 min read
A backup you have not restored is a hypothesis
The only evidence that a backup works is having used it. Ask when yours was last actually restored.
01Service
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.
02Judgement
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.
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.
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.
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.
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
We would rather tell you this at the enquiry stage than halfway through a build.
04Technology
The stack is chosen per project. This is what we actually work in, and when each one earns its place.
05Process
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.
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.
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.
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

Article · 2 min read
The only evidence that a backup works is having used it. Ask when yours was last actually restored.

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

Article · 2 min read
A checkout that cannot be completed by keyboard excludes customers who were ready to pay. The same fixes reduce abandonment for everyone.
Describe the catalogue and the rules that do not fit. If a template platform would serve you better, we will say so.