Guide
How to sync inventory across Amazon, Flipkart, Meesho and Shopify
Updated 3 min read
The short answer
To sync inventory across marketplaces, map every marketplace listing to one canonical SKU, hold stock in a single ledger, and push available quantity out to each channel whenever it changes. The hard parts are not technical: they are SKU mapping discipline, deciding how much buffer to hold, and handling the lag between a sale and the update reaching every channel.
- Step one is always SKU mapping — everything downstream depends on it
- One ledger in, many channels out. Never let a channel be authoritative
- Expect lag: design for it with buffers rather than pretending it is zero
- Reserve stock at order, deduct at dispatch — the two are not the same event
The model: one ledger in, many channels out
Every workable multi-channel setup has the same shape. One system holds the stock ledger. Each channel is a subscriber that gets told a number. No channel is ever allowed to be the source of truth, because the moment two are, you are reconciling forever.
The important detail is that available stock is not a stored number — it is derived. Physical stock, minus units reserved for orders not yet dispatched, minus any buffer you have chosen to hold back, equals what each channel is told. Store the movements, derive the number.
Setting it up, in order
- 1
Freeze one canonical SKU per product
Not per listing, per product variant that you physically hold. Decide the code once and never change it. A red t-shirt in size M is one SKU no matter how many marketplaces sell it under different names.
- 2
Map every listing to that SKU
Each marketplace has its own identifier — ASIN and seller SKU on Amazon, FSN and SKU ID on Flipkart, and so on. Build the mapping table deliberately, and treat an unmapped listing as an error that blocks sync rather than a warning to ignore.
- 3
Do a physical count and set opening balances
Start from reality on a day you are not shipping. Every hour spent here saves a week of distrusting the system later.
- 4
Decide your buffer policy per channel
A buffer is stock you deliberately do not advertise, to absorb the seconds between a sale and the update landing everywhere. Fast-moving SKUs need one; slow-moving SKUs mostly do not.
- 5
Turn on sync for one channel first
Watch it for several days across a weekend. Confirm that a sale on that channel produces the ledger entry you expect, then connect the rest.
- 6
Add a reconciliation habit
Cycle count a slice of your SKUs weekly rather than doing one painful annual count. Discrepancies found small are cheap to explain.
The failure modes to design around
- Sync lag
- There is always a gap between a sale and every channel knowing. Buffers exist for this. Anyone claiming zero lag is describing a demo, not a marketplace API under load.
- Duplicate SKUs
- The same product entered twice under slightly different codes splits your stock in half and breaks every report. Enforce uniqueness at creation, not at cleanup.
- Bundles and kits
- A combo pack is not a SKU with its own stock — it consumes component SKUs. If the system does not model that, bundles will quietly oversell their components.
- Returns limbo
- An RTO parcel is not sellable stock until it is physically received and inspected. Adding it back on the tracking event rather than the receipt event manufactures phantom stock.
- Marketplace-side edits
- Someone updates a quantity directly in a seller panel. Decide up front that the OMS overwrites it, and tell your team, or you will chase this for months.
Frequently asked questions
How do I keep stock in sync between Amazon and Flipkart?
Map both listings to one canonical SKU, hold the quantity in a single stock ledger, and let that system push available quantity to both channels whenever it changes. Never maintain the number separately in each seller panel — two sources of truth guarantee an oversell.
How fast should marketplace inventory sync be?
Near real time for fast-moving SKUs, which in practice means seconds to a couple of minutes depending on the marketplace's API limits. Because some lag always exists, hold a small buffer on your fastest sellers rather than assuming instant propagation.
What is a safety buffer and how much should I hold?
A buffer is stock you deliberately do not advertise, so a sale that lands during sync lag does not oversell. Hold it only on SKUs that sell fast enough for lag to matter; on slow movers it just hides sellable stock.