To manage inventory sync across Amazon, Flipkart and Myntra, keep one master SKU list as your source of truth, map every marketplace listing to it, allocate stock with a safety buffer, update quantities after every sale, cancellation and return, and audit stock against orders and settlements weekly to catch drift early.
Why inventory sync breaks across three marketplaces
Inventory sync means keeping the sellable quantity of each SKU accurate on every channel, so a sale on one marketplace reduces what the others show. When it fails, you see orders you cannot ship, seller-initiated cancellations, poorer ratings and stock idling on a channel where it does not sell.
Three marketplaces make this harder for specific reasons:
- Each uses its own listing IDs and SKU formats, so one shirt in one size can have three identifiers.
- Fulfilment models differ. Some stock sits in your warehouse, some in a marketplace-run facility, and how much quantity you control depends on the model.
- Returns come back at different speeds and in different conditions, so units re-enter sellable stock late or never.
Check your seller agreement and each seller panel for how stock-outs and seller cancellations are treated. These terms change, so confirm the latest version rather than relying on memory.
Step 1: Build one master SKU map
Start with a master SKU list that your team owns. No marketplace should be the source of truth. Every channel listing maps back to it.
- Create a master SKU code at the size and colour level, such as one code per kurta, colour and size.
- Map each channel identifier (Amazon SKU or ASIN, Flipkart listing and SKU, Myntra style and size codes) to that master code in one sheet or system.
- Lock the naming rules so new listings cannot go live without a mapping.
- Record the fulfilment model per listing, so you know which units are in your warehouse and which are not.
Most sync errors come from a bad mapping, not a bad tool. A size M mapped to a size L will oversell one and starve the other for weeks before anyone notices.
Step 2: Decide allocation and safety buffers
You have two basic options. A shared pool shows the full sellable quantity on every channel and reduces it everywhere after each sale. It maximises sales but needs fast updates. A fixed allocation assigns units to each channel. It is safer when updates are slow, but stock can get stuck on a slower channel.
Many brands use a hybrid. Fast-moving SKUs get fixed allocations with a periodic rebalance, while slow movers use a shared pool.
- Set a safety buffer per SKU, a few units held back from the sellable count to absorb delays, damaged units and QC rejections.
- Use a higher buffer during sale events, when order volume outpaces sync cycles.
- Review allocation weekly using sell-through by channel, not gut feel.
Do not copy a buffer figure from a blog post, including this one. Set it from your own sync delay, cancellation history and the penalties in your agreements.
Step 3: Update stock on every inventory event
Sync is not only about new orders. Quantity should change on every event that moves a unit in or out of sellable stock:
- New order, and order cancelled before dispatch
- Dispatch or handover to the courier
- Customer return, RTO (return to origin) and the QC outcome
- Inward stock, transfers and damaged or lost units
Check what each marketplace supports. Some allow API or bulk-file updates, while others rely on manual panel uploads. Where updates are manual, fix a schedule, say at the start of the day, mid-day and end of day, and treat high-velocity SKUs more often. Log the time of each update so you can later explain a mismatch.
Returns need special attention. A unit is not sellable until it is received and passes QC. Add it back only then, and tag its channel of origin so you can match it to the return claim.
Step 4: Run a weekly stock and settlement audit
Even good sync drifts. A weekly audit catches drift before it becomes a month of write-offs. Compare these views for each master SKU:
| Check | Compare | What a gap suggests |
|---|---|---|
| Orders vs dispatches | Orders received against units shipped | Cancellations or stock-outs |
| Dispatches vs settlements | Shipped units against settled order lines | Missing or delayed payouts |
| Returns vs restocked | Returns received against units added back | Lost, unreceived or unrecorded returns |
| Book vs physical | System stock against a cycle count | Mapping or update errors |
This is where operations meets fee audits. A unit that leaves stock but never shows in a settlement, or a return you never received back, is money to chase. Verify commissions and fees against the rate card and agreement for each marketplace, and raise recovery cases within the window stated in your terms.
Doing this by spreadsheet across three channels is slow. MarketplaceMetrics by Fundle reconciles marketplace sales and settlements, checks fees against agreed terms and tracks returns and recovery cases, so stock gaps and money gaps can be reviewed together. Myntra Excel reports are reviewed today, and other marketplaces are in scope discussion.
Common mistakes to avoid
- Treating one marketplace panel as the master stock record.
- Changing a SKU code on one channel without updating the map.
- Restocking returns on receipt without checking QC.
- Ignoring sync delays during sale events.
- Auditing stock but not settlements, so unpaid or short-paid units go unnoticed.
Fix the map first, then the rules, then the audit. Tools help only when these three are in place.
Worked example
Illustrative example only. Figures are not real data or marketplace rates.
A brand holds 200 units of one SKU in its own warehouse. It sets a safety buffer of 10 units, leaving 190 sellable, and allocates 90 to Amazon, 60 to Flipkart and 40 to Myntra.
- Midweek, a batch of 6 units fails QC, but the stock sheet is not updated for a day.
- The shared system still shows 190 sellable, and 4 orders arrive that cannot be fulfilled. At an assumed selling price of ₹1,200, that is ₹4,800 of sales at risk.
- Any cancellation penalty or rating impact depends on each marketplace's terms. It is not included here, so check your agreement.
The buffer absorbed some of the error, but not all. Updating stock on the QC event and reviewing the weekly audit would have exposed the 6-unit gap within days.
Questions and answers
Can I use one tool to sync inventory across all three marketplaces?
Possibly, but it depends on what each marketplace supports through APIs, bulk files or panel uploads. Confirm integration options in each seller panel and with the tool vendor. Whatever you choose, keep your own master SKU map as the source of truth.
How often should inventory sync run?
Run it as often as your sales velocity requires. Fast-moving SKUs and sale events need frequent updates, while slow movers can tolerate longer gaps. Measure your cancellation rate and sync delay, then tighten the schedule where stock-outs actually occur.
Should I allocate fixed stock to each marketplace or share one pool?
A shared pool maximises sales but needs fast updates. Fixed allocation is safer when updates are slow but can strand stock. Many brands use fixed allocation for fast sellers with periodic rebalancing, and a shared pool for slower SKUs.
How does inventory sync connect to fee audits?
Stock movements should match orders, returns and settlements. Units shipped but not settled, or returns not received back, signal recoverable money. Auditing them alongside commissions and fees against your agreed terms helps you raise claims within the allowed window.