Marketplaces, commerce platforms, ERPs, carriers and payment networks
500+ Integrations, One Source of Truth
How Md. Farhan Khan designs commerce integrations as contracts about time, across 500+ marketplaces, commerce platforms, ERPs and carriers.
- Channels and integrations delivered
- 500+
- Integration methods
- API and EDI
- Transactions a day at peak
- 1M+
The problem
Every marketplace, commerce platform, ERP, carrier and payment network describes orders, stock and money in its own way, and updates them on its own clock. A brand selling on ten channels is running ten versions of the truth.
When those versions disagree, the cost is immediate: the same unit sold twice, a cancelled order, a price out of parity, a return nobody can match, a settlement that does not reconcile. At scale, these small mismatches become one of the largest operating losses in the business.
Most teams scope integration as field mapping. The failures that cost money are about time and ownership: whose version of an event wins, and when.
The approach
I design every connector as a contract, not a mapping, and run integration as a product with its own model, standards and roadmap.
State truth versus event truth. State is what a record says now. Events are what happened, and when. Exchange events, and the true state can always be rebuilt.
One owner per clock. Orders, stock, price and money each have exactly one source of truth.
Inventory as a ledger. The inventory model I designed records every stock movement as an event, across 24 stock states down to the bin, so availability is computed, never guessed.
Idempotent by design. Processing a message twice changes nothing, so retries after an outage are safe.
Entities kept apart. Multi-company and multi-country set-ups run as separate entities under one organisation, so stock never crosses a legal boundary.
Reconciliation from day one. Every order, return and settlement can be traced across every system it touched.
Migration without loss. Channels move one at a time inside a planned window, with stock flushed from the old system and fed to both until cutover, so no order is lost and no unit is sold twice.
Fix the class, not the ticket. Every recurring failure ends with a root cause and a rule.
The result
More than 500 channels and integrations delivered over APIs and EDI: marketplaces such as Amazon, Walmart, eBay, Flipkart, Myntra, Noon, Lazada and Shopee; commerce platforms such as Shopify, BigCommerce and Adobe Commerce; and the ERPs, carriers and payment networks behind them.
The same model carried a seller platform I delivered for one of India's leading beauty and fashion marketplaces: a seller portal with partner and aggregator integrations, so every seller and brand could join through the route that suited them.
At peak, the systems running these connectors carried more than one million transactions a day.
The principle: integration is a contract about time. Give every clock one owner, and 500 connections behave like one.