E-commerce · Multi-marketplace
A platform that lets vendors publish one catalogue across twelve Amazon marketplaces and keeps price, stock and orders in sync, rebuilt from cron scripts into an event-driven service while migrating APIs under it.
Vendors keep selling across twelve marketplaces from one catalogue instead of managing each one by hand, and the platform absorbed an Amazon API migration as an internal change instead of a seller-facing outage.
// the problem
Vendors selling the same catalogue across a dozen Amazon marketplaces needed price, stock and orders to stay in sync everywhere, on a platform that had grown as a set of procedural cron scripts nobody could safely extend.
// engineering
The platform was rebuilt around a command bus and a long-running worker consuming domain events, with domain, application and infrastructure layers separated so a sync rule lives in one place instead of one script per marketplace.
Amazon's retirement of MWS in favour of SP-API happened while the platform was live. The two APIs were bridged behind the same internal interface, so sellers kept publishing and syncing while the underlying integration changed under them.
Products are matched to existing listings by barcode, categorised against each marketplace's own taxonomy, and translated automatically, so one catalogue entry becomes a correct listing in the UK, Germany, France, Italy, Spain, the Netherlands, Sweden, Turkey, the UAE and India, among others.
Catalogue and stock updates go out as bulk feeds, and each record's outcome is reported back individually, so a rejected item in one marketplace doesn't block the rest of the batch or hide which listing failed.
// result
Vendors publish and manage one catalogue across twelve Amazon marketplaces through four portals — vendor, agent, administration and signup — with order import, low-stock alerts and commission tracking for the agents who bring vendors onto the platform. The event-driven rebuild and the MWS-to-SP-API migration ran at the same time, without interrupting sellers already live.
The platform started as cron scripts calling Amazon’s API directly; it now runs as an event-driven service with a command bus, and it bridged the move from MWS to SP-API without sellers noticing.
Event-driven backend · Command bus · Relational database · Background worker · Domain-driven architecture
Tell us what you're building. You'll leave with an honest opinion, even if it's "you don't need us."
Reference calls with past clients are available under NDA during evaluation.