Skip to main content

This is a demonstration, not client work. No client has been engaged for this project and no results are claimed. It exists to show the scope and shape of a typical engagement.

E-commerce

Online store with fulfilment workflow

Demonstration scope: a store where stock stays consistent across the website, the warehouse and trade customers.

Overview

The project

A retailer was selling through a marketplace and a trade counter while beginning to build a direct channel. Stock was tracked in three places that disagreed, which produced overselling and cancelled orders.

This demonstration shows the shape of the work: one authoritative stock position, surfaced consistently everywhere it is sold, with orders flowing straight into the fulfilment process that already existed.

Objectives

What it needed to achieve

  • Hold stock in one place so channels cannot disagree
  • Send orders directly into the existing fulfilment process
  • Support the payment methods the actual customers use
  • Keep catalogue editing in-house
  • Report which products actually sell

Scope

What was, and was not, included

Scope boundaries matter more than scope size. This is where the work deliberately stopped.

Included

  • Catalogue structure with variants and per-variant stock
  • Product and category pages with search-ready metadata
  • Cart, checkout and payment provider integration
  • Order management with status, notes, refunds and cancellation
  • Stock synchronisation with the existing stock system via API
  • Tax, shipping and delivery rules configured to the business
  • Admin training session and written operating notes

Not included

  • Warehouse hardware and picking systems
  • Accountant software configuration
  • Ongoing catalogue entry and content production

Challenge

A retailer needed to sell direct while stock levels stayed accurate across a warehouse that also handled trade orders.

Solution

A catalogue and checkout connected to the existing stock system through an API integration, so inventory updates once and is reflected everywhere it is shown.

Implementation

How it was approached

Discovery established that stock consistency, not the storefront itself, was the real constraint — that shaped the architecture before any design work.

The existing stock system remained the single source of truth, with the store reading from it rather than duplicating inventory.

Order placement writes directly into the fulfilment process already in use, removing the manual re-keying step.

Failed and retried API calls were handled explicitly so a temporary provider outage does not produce duplicate or missing orders.

Technology

What it was built with

Screenshots are published only once imagery has been supplied and authorised. None are shown for this entry.

Building something similar?

Tell us what you have in mind and we will come back with questions, an approach and a written scope.