We recently built an e-commerce marketplace middleware for a leading retail chain for consumer electronics & durables. The middleware enables them to sell their products on multiple e-commerce sites seamlessly.
Through this blog post series, I am planning to share how we developed it in Clojure by building a minimal version of it.
For managing the products inventory, updating the pricing of the product and honouring the customer orders in their 134 stores, they are using a proprietary Order Management System (OMS). To perform similar activities in the e-commerce marketplace sites, they were manually doing it from the seller portal provided by the marketplace. This back-office work is repetitive and exhausting.
They decided to improve this process by performing all the activities using their OMS. They wanted a middleware which will listen to the changes in the OMS and fulfil the order management activities across different marketplaces without any manual intervention.
10,000 Foot View
The system that we built would look like this.
The retailer’s back office team perform their operations with their OMS. The OMS exposes these activities to the outside system using IBM MQ.
In response to messages from the OMS, the middleware executes the respective operations (listing a product, unlisting a product, updating price of a product, etc.,) in the marketplace site.
The middleware also runs some cron jobs which periodically pulls the new orders and order cancellations from the marketplaces and communicate it back to the OMS via IBM MQ.
The middleware has a database (Postgres) to persists its operational data and exposes this data to the back office team via a dashboard powered by Metabase.
How we developed it
As mentioned earlier, we are going to build a minimal version of this project called
Wheel using which I will be sharing how we implemented it.
I will also be updating the below list with the new blog post links.