How do I sync inventory across my website, Amazon and Flipkart?

Keep one stock figure for your website, Amazon and Flipkart by making one system the source of truth and pushing available stock to every channel.

Anadoris Digital · · 4 min read

Cardboard boxes
Photo: Jillien Minera / Unsplash (CC0)

Most overselling in Indian D2C brands has one cause: each channel thinks it owns the stock. The website shows one number, Seller Central shows another and the Flipkart panel shows a third, and someone updates them by hand in the evening. By the time they do, the numbers are already stale.

The fix is structural. Pick one place that holds the real count, and treat every channel as a window onto it rather than a separate store of truth.

Choose a single source of truth

The source of truth should be the system that knows about every stock movement: sales on every channel, returns, goods received from your manufacturer, transfers between warehouses and damages. For most brands that is an ERP or a dedicated order and inventory tool connected to the ERP.

Your website platform can be the source of truth only if almost all sales happen there and other channels are minor. Once marketplaces carry a meaningful share, the website becomes one channel among several and should stop being the master.

How the sync actually works

  • An order arrives on any channel and is pulled into the central system through the channel’s API or connector.
  • The central system reserves the units against that order.
  • Available stock is recalculated as on-hand minus reserved minus any safety buffer.
  • The new available figure is pushed back to every channel on a fixed schedule or on each change.
  • Returns, receipts and adjustments update the same record and trigger the same push.

The weak point is timing. If the push runs every few hours, two channels can sell the last unit in between. Ask how often each connector syncs, and whether it can push immediately when stock falls below a set level.

Handle fulfilment models separately

Stock that sits in a marketplace’s own warehouse, such as Amazon’s fulfilment programme, is not available to your website. Treat it as a separate location in the system. You track it for valuation and replenishment, but you do not share it with other channels.

The same applies to quick-commerce partners who hold your stock in their dark stores. Keep each of these as its own location so that your available-to-sell figure for self-shipped channels only counts what is actually in your own warehouse or 3PL.

Use buffers and channel allocation

A buffer is a small number of units held back from all channels to absorb sync delays. Set it per SKU: fast movers need a larger buffer than slow ones. Some brands also cap how much of a scarce SKU any one channel can show, so that a marketplace sale does not empty stock meant for the website.

Review buffers before each sale event. A buffer that is right on a normal day can be too small when orders arrive several times faster.

Checklist before you switch on sync

  • Every SKU has one internal code mapped to each channel’s listing ID, ASIN or FSN.
  • Bundles and combo packs are defined as kits so selling one reduces the component stock.
  • Opening stock is counted physically and entered on the same day sync starts.
  • Each warehouse, 3PL and marketplace-held stock is a separate location.
  • Buffers are set for the top-selling SKUs.
  • Someone receives an alert when a sync fails, rather than finding out from cancellations.

Common mistakes

Mapping errors cause most sync problems. A listing linked to the wrong SKU will quietly drain stock from the wrong product. Duplicate listings for the same product on one marketplace also split or double-count stock. Audit mappings monthly and whenever you add listings.

Another frequent mistake is manual edits on the channel side. If staff change stock directly on Amazon or Flipkart, the next push overwrites it, or worse, the central system never learns about the change. Make it a rule that stock is only changed in the source of truth.

Monitoring sync once it is live

A sync that works on day one can quietly fail on day forty, when a marketplace changes an API or a login token expires. Build a short daily check into someone’s routine. Compare the available figure for your top SKUs in the central system with what each channel shows. Any difference beyond the buffer means a sync has stopped or a mapping is wrong.

Keep a log of order cancellations caused by stock-outs on each channel. If cancellations rise, look at sync timing and buffers before blaming demand. Marketplaces track seller cancellations, so catching the cause early protects your account health as well as customer experience.

Where to start

  • Export SKU lists from every channel and build one mapping sheet.
  • Decide which system will be the source of truth and stop manual channel edits.
  • Set up one channel first, usually the website, and run it for a week.
  • Add marketplaces one at a time and compare counts daily during the first fortnight.
  • Set buffers and failure alerts before your next sale.

Anadoris Digital sets up this kind of single-stock-record integration for brands selling across their own site and marketplaces, if you would rather not build it in-house.

Related service: ERP Solutions · More on this topic: ERP Solutions articles

Common questions

How often should stock sync to marketplaces?

As often as the connector and the marketplace’s API allow without errors. Near real time is ideal for fast-moving SKUs. Where only scheduled syncs are possible, use a larger safety buffer to cover the gap between updates, especially during sale events.

Should Amazon FBA stock count in my website stock?

No. Stock held in a marketplace’s fulfilment centre can only be sold through that marketplace. Track it as a separate location for valuation and replenishment, but exclude it from the available quantity you show on your own website and other channels.

What happens to stock when an order is cancelled?

The reservation should be released and available stock increased automatically, then pushed to every channel. If the order was already packed, staff should confirm the unit is back on the shelf before it is released, so the system matches physical stock.

How do I handle combo packs in inventory sync?

Set each combo as a kit made of component SKUs. When a combo sells, the system reduces each component. Available combo stock is then calculated from the scarcest component, so you never sell a combo you cannot assemble.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project