Download CV
← all 25 systems

platform · 2025 · client unnamed

Bookstore E-commerce over an Existing ERP

A storefront, admin dashboard and API sitting in front of the client existing ERP, which stays the source of truth.

3

Tiers shipped

API, admin dashboard, storefront

ERP

Source of truth

deliberately not replaced

The problem

A bookstore chain already ran products, stock and pricing in an established ERP. They needed a modern storefront and dashboard, but replacing the ERP was never on the table and duplicating its data would create two versions of the truth.

The approach

Built the platform explicitly in front of the ERP rather than beside it. The ERP remains authoritative for catalogue, stock and price; the platform owns the customer experience, carts, orders and content. Three tiers shipped: the API, an admin dashboard, and a storefront.

Architecture

The ERP is upstream and authoritative. The platform reads catalogue and stock from it and pushes orders back, with the customer-facing layer owning everything the ERP has no opinion about.

One decision

Each with what it cost

A decision without a stated tradeoff is a preference.

01

Sit in front of the ERP rather than migrate off it

Why

The client staff already operate it daily. Migrating a working ERP to gain a storefront is a large project with no upside for the people doing the work.

What it costs

The platform inherits the ERP data model in places where a greenfield schema would be cleaner.

Outcome

The client keeps running their business in the ERP their staff already know, and customers get a storefront that reflects it.