← All work

Case study · № 007 · 2024 to present

BUILDMYRIG · one store, every channel

A full operations system for a large UK gaming retailer and its international exports: one catalogue synced across eBay, Amazon, and the website, every order captured in one place, and the whole back office alongside it. Work in progress.

RoleFull-stack, team: frontend, backend, integrations
Timeline2024 to present
StackNext.js · Node · eBay & Amazon APIs
StatusIn development
In progress Technical plate 007: system schematic of the BuildMyRig store operations platform

The problem

A retailer selling across its own website, eBay, and Amazon, plus international exports, has one catalogue living in three places that do not agree. Stock sells on eBay but still shows available on Amazon. Orders arrive in three separate dashboards. Dispatch, returns, and the back office each run on their own tools.

The brief was a single system that runs the whole store: one catalogue, every channel, one back office.

The build

  • Inventory and listings synced across eBay, Amazon, and the website, including product variations, so one catalogue drives every channel instead of three copies drifting apart.
  • Orders captured from all channels into one queue, then dispatched through FedEx, DPD, and Parcelforce with parcel tracking.
  • The full after-sale surface: returns, refunds, replacements, and product upgrades and downgrades, handled in the same system.
  • The back office alongside it: payroll, HR, attendance, physical and geolocation tracking, and document management. A whole office, not just a storefront.

Decisions that mattered

One catalogue, many channels. Multi-channel stock only stays honest if a single source of truth pushes to eBay, Amazon, and the site, instead of reconciling three of them after the fact.

Capture every order in one queue. Staff should never log into three seller dashboards. Pulling every channel's orders into one place is what makes dispatch and returns manageable.

Variations are first-class. Same product, many variants is where naive inventory systems break. Handling variations properly across every channel was a core requirement, not an edge case.

Outcome

In active development as the operating system for a large UK gaming retailer and its export business, spanning storefront, marketplaces, dispatch, after-sales, and the back office. It is the largest single system I have worked on, and the closest to the multi-integration, real-consequence work I do now.

Previous case← IAMP Next caseTenneco →