Ecommerce Website Developer

01Service

Ecommerce website development

Building and maintaining online shops for retailers in the United Kingdom. The work covers the catalogue and checkout, the systems the shop depends on, and the technical conditions that decide whether product pages are fast and findable.

  • Catalogue and checkout
  • Connected systems
  • Fast, findable product pages

What is delivered

  • Catalogue model
  • Checkout behaviour
  • Front end build
  • Integrations
  • Technical SEO
  • Operational handover

This is likely to fit if

  • You already sell online and the shop is slow, fragile or difficult to change.
  • You are replatforming and need the migration not to lose search visibility.
  • You have outgrown a template build and need bespoke catalogue or checkout behaviour.
  • You need someone accountable for the shop after launch, not only during the build.

This is not the right fit for

  • A one page brochure site with no products. The work here is specific to trading systems.
  • Marketplace-only selling with no website of your own.
  • Paid media buying, brand design or copywriting as a standalone service.

02Deliverables

What is delivered

Catalogue model
Product, variant, category and attribute structure that matches how you actually sell, including the awkward cases such as bundles, made to order items and restricted delivery.
Checkout behaviour
Payment provider integration, tax and delivery rules, validation and error handling. The aim is that a customer who wants to buy is never blocked by a technical fault.
Front end build
Templates for home, category, product, basket and checkout, built to work by keyboard, at 320 pixels wide, and at 400 per cent zoom.
Integrations
Stock, order management, fulfilment and transactional email, with explicit handling for the case where the other system is unavailable.
Technical SEO
Canonical rules for variants and facets, crawl controls, pagination, structured data that matches visible content, and a redirect map for anything changing address.
Operational handover
Documented architecture, environment variables, backup and restore procedure, and a runbook for the failures that are likely rather than the ones that are interesting.

03Stages

How the work is staged

  1. Discovery and scope

    Review the current shop, the systems around it and the records that exist. Produce a written scope with the catalogue model, integration list, URL disposition and the things explicitly excluded.

  2. Build and review

    Incremental delivery on a staging environment with authentication, so nothing in progress is publicly reachable or indexable. Accessibility and performance are checked per template as they are built.

  3. Migration rehearsal

    Freeze the URL map, test every redirect, verify canonical and sitemap output, and rehearse the restore. A migration that has not been rehearsed is not a plan.

  4. Cutover and support

    Deploy, verify DNS, certificates and redirects from raw requests, then monitor errors, uptime and crawl coverage through the period when problems actually surface.

04Due diligence

Questions worth asking

These apply to any developer you speak to, including this one.

What happens to my existing URLs?
Every URL that changes address needs a redirect to the closest genuine equivalent, agreed in writing before launch. Pages with no equivalent should return a proper not found or gone response, never a redirect to the homepage. Ask to see the map.
Who owns the hosting and the domain?
You should. If a developer holds your domain, DNS or hosting account in their own name, you cannot leave and you cannot recover the site if they disappear. Accounts should be in the business name with the developer given access.
What happens if the shop goes down at the weekend?
There should be a named person, a monitoring alert that reaches them and a documented restore procedure that has been tested. Ask when the restore was last actually performed rather than whether backups exist.
How is performance measured?
Field data from real visitors over a rolling window, not a single laboratory score from a fast desktop connection. A laboratory test is useful for catching regressions, but it is not evidence of what your customers experience.

05Reading

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.

Describe the problem, not the brief.

What you sell, the platform you are on and what is failing. That is enough to tell you whether this is worth taking further.