CASE STUDY 01 / OMNICHANNEL ARCHITECTURE

THE MARKETPLACE
MACHINE.

Orchestrating product catalogues, real-time inventory, pricing, and fulfillment across 12 sales channels without turning warehouse operations into a fragile web of spreadsheets.

ROLEFractional CTO / Systems Architect
SCALE12 Channels · 21.6K SKUs · 1,000+ Orders/Day
STACKAPIs · Mirakl · Amazon MWS/SP-API · WooCommerce · Webhooks
IMPACTZero Inventory Drift · 4× Channel Expansion

The Business Problem

The business wanted to scale beyond its primary online storefront. The immediate commercial strategy was to launch across major marketplaces: Amazon, eBay, B&Q, Debenhams, Etsy, and Mirakl-powered retail networks.

However, adding each marketplace introduced an exponential operational burden:

12 CHANNELS, ONE REALITY

The core objective was to make adding a new marketplace a commercial decision rather than an operational crisis.

The Architectural Solution

Rather than relying on off-the-shelf plugins that poll every 15 minutes and collapse under high SKU volume, I architected a centralized, event-driven integration layer between the core commerce engine, the warehouse management system (WMS), and external marketplace APIs.

CATALOGUE / PIM
AUTHORITY
INTEGRATION ENGINE
RULES & TRANSFORMS
MARKETPLACE APIS
MIRAKL / AMAZON
WMS / FULFILMENT
DESPATCH

1. Decoupled Canonical Data Model

Products were assigned an immutable internal identifier. Each marketplace connector translated between this canonical internal representation and the target marketplace's specific schema. When a product attribute updated, only the translated delta was dispatched to downstream channels.

2. Idempotent Real-Time Inventory Broadcast

Whenever a sale occurred on any channel (or in the physical trade depot), an inventory event was fired immediately across all 12 channels. Crucially, the updates were designed to be idempotent: network timeouts and automatic retries could never cause double-decrements or stock corruption.

3. Unified Order Normalization

Orders from all 12 channels were ingested, normalized into a uniform data contract, and piped directly into the warehouse picking queue. Tracking numbers and dispatch confirmations were automatically routed back to the appropriate marketplace upon parcel scanning.

The Business Outcomes

← BACK TO PROJECTS NEXT CASE STUDY: LET THE MODELS AUDIT IT →