E-commerce development
Online stores with catalogue, checkout and payments.
- Catalogue and search
- Checkout and payments
- Stock and orders
- Analytics
What this is for
Selling directly to customers online, at any hour, with nobody in the room. A shop has to do the whole job unattended: show what is genuinely available, take money safely, and leave a record accurate enough to fulfil the order from. Most of the work sits in the parts a visitor never sees — stock that reflects the shelf, prices changed in one place, an order that arrives complete. The storefront is the visible half of it.
What it covers
- Catalogue and search
Products, variants and categories structured so a customer can narrow a large range down to the thing they came for. Search and filters are built against the catalogue as it will grow, not against a demonstration set.
- Checkout and payments
A checkout with as few steps as the order genuinely requires, taking payment through a provider so card details never reach your systems or ours.
- Stock and orders
Stock levels, orders and fulfilment status in one place, so what the site says is available is what is actually there.
- Analytics
Where orders come from and where people stop, measured, so a change to the shop can be judged afterwards rather than argued about.
What you end up with
- A shop that takes payment
Live, settling into your own account through a payment provider, and tested with real transactions before launch rather than after it.
- Catalogue, stock and orders in one place
One place to add a product, change a price or check an order, instead of three that have to be kept in agreement.
- Checkout tested on real phones
Checkout is where most orders are lost, and most of them are placed on a phone, so it is tested there specifically.
- Training for whoever runs it daily
The person adding products and handling orders is shown the shop as they will use it, not as it was built.
What we need from you
- Your product list and prices
In whatever form it already exists — a spreadsheet is fine. How the range is grouped matters more than how it is formatted.
- A payment provider, or a decision to make one
The provider affects fees, payout timing and what you are permitted to sell, so it is worth deciding before the build rather than during it.
- How you ship or deliver
Rates, regions, and whether anything is collected in person. Delivery rules are part of checkout rather than an addition to it.
Who works on it
Each part is done by the specialist for it, in the order the work reaches them.
- FirstDesignFlows and screens, agreed before any code is written.
- ThenFront-endInterfaces built to their measurements and checked on real devices.
- ThenBack-endThe logic, the data, and the contracts between them.
- ThenInfrastructurePipelines, hosting, monitoring and on-call.
- LastTestingTesting every release before it reaches a client.
How it runs
- DiscoveryFirst
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
- DesignBefore the build
You see the site before it is built, on desktop and phone, and approve it before the build starts.
- Designs to approve
- Mobile and desktop
- Final copy
- BuildThe build
The design is built to its measurements, on a link you can open at any point during the build.
- Live preview link
- Progress you can see
- Content loaded
- LaunchHandover
Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.
- Live on your domain
- Accounts in your name
- Support after launch
- SupportAfter launch
Updates, fixes and changes for as long as the site is live.
- Updates and fixes
- Monitoring
- A number to message
Questions people ask first
With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.
Also under Build
Get in touch
Every one of these reaches us directly, and is answered by a person.