Lead Developer / Project Manager · PowerSell at Datamart Solutions · Jan 2020 – Nov 2020 · Team of 10
The problem
Sellers running storefronts across several marketplaces were doing everything more than once. Updating product presentation meant repeating the same edits platform by platform. Customer conversations arrived across Instagram, Facebook and Zalo, each in its own inbox, each easy to miss.
PowerSell was the suite meant to collapse all of that into one place. I owned two of its modules end to end — from building requirements with the product team, through the codebase, to managing the team that shipped them.
What I built
- PowerPaint — mass-decorate and update seller products across multiple e-commerce platforms in one operation, instead of one platform at a time.
- Social Commerce — a single surface for managing Instagram, Facebook and Zalo, with realtime messaging so conversations don’t go stale in a tab nobody opened.
- A crawler system for collecting marketplace and competitor data at volume.
- Microservices and queue infrastructure (RabbitMQ) to absorb the traffic and keep third-party rate limits from cascading into user-facing failures.
Stack
Laravel, microservices, e-commerce platform APIs, social platform APIs, crawler system, MongoDB, MySQL, RabbitMQ, realtime messaging, big data.
What this work teaches you
Multi-marketplace integration is mostly a lesson in other people’s APIs: inconsistent schemas, undocumented rate limits, silent failures, and sync conflicts when two systems both think they’re authoritative. None of it is conceptually hard and all of it will eat a quarter if you design for the happy path.
Datamart was later acquired.
If you’re syncing products, orders or messages across platforms and it keeps drifting out of agreement, let’s talk →