EN
Marketplace

How to Sync Inventory Across Multiple Marketplaces? A Guide to Preventing Overselling

How do you sync inventory across multiple marketplaces? Causes of overselling, manual, XML and API methods, buffer stock calculation, available stock and 7 mistakes.

Contents 10 sections
  1. What is inventory sync?
  2. Why does overselling happen?
  3. What methods are used for inventory sync?
  4. How much does sync delay increase the risk of overselling?
  5. How are available stock and buffer stock calculated?
  6. Should stock be distributed to channels from a shared pool or by quota?
  7. In what order is stock updated when an order arrives?
  8. The 7 most common mistakes in inventory sync
  9. How do you sync inventory with NetKasam?
  10. Frequently Asked Questions About Inventory Sync

Imagine you sell the same product on two marketplaces and on your own e-commerce website. The last 3 units are left in the warehouse. In the morning, 2 orders come in from one marketplace, and before noon 2 from the other; because stock counts were not updated across channels, both showed "in stock." The result: 4 sales, 3 products, one cancellation and an unhappy buyer. The question how do you sync inventory across multiple marketplaces is the first big problem for every business that moves into multichannel selling, and the answer is not just picking a piece of software.

In this guide, we cover inventory sync from start to finish: why overselling happens, what the difference is between manual, XML and API sync methods, how available stock and buffer stock are calculated, whether stock should be distributed to channels from a shared pool or by quota, in what order stock is updated when an order arrives and what the 7 most common mistakes are. The sales and stock figures in the examples were chosen only to illustrate the method.

What is inventory sync?

In short: Inventory sync means keeping the stock count of the same product simultaneous and accurate across all sales channels, such as marketplaces, the e-commerce website and the physical store. When a sale happens on one channel, stock drops in the main source and the new number is sent to the other channels.

In single-channel selling, the stock problem is simple: as the product sells, that channel's stock drops. In multichannel e-commerce, however, the same physical product is sold in more than one storefront at the same time. Each storefront shows its own stock count, and these counts know nothing of one another. Sync is the bridge that connects these storefronts to a single warehouse.

At the heart of sync is the principle of a single source of truth: the stock count is kept and changed in only one place; marketplaces and the website are fed from this source. In a business that updates stock separately in one marketplace's panel, in another's and in Excel, there is no such thing as "the correct stock." We explained the general strategy of multichannel selling in our article multichannel selling in e-commerce.

Why does overselling happen?

In short: Overselling happens when the same product sells on another channel before a sale on one channel is reflected on the others. The most common causes are sync delay, manual stock updates, returns and cancellations returning to stock late and differences between warehouse counts and system stock.

The cost of overselling is not limited to the cancelled order. A buyer whose order is cancelled will most likely not buy from the same store again and may leave a negative review; marketplaces also count seller-caused cancellations in store performance and may apply sanctions under their own rules. So overselling is not just a lost sale; it is a cost charged to the store's future.

ReasonHow does it happen?Prevention
Sync delayStock is sent to channels once an hour or a few times a day; sales continue in the meantimeReal-time transfer via API, buffer stock equal to the delay
Manual updatesStock is changed by hand on each channel separately; one gets forgottenKeeping stock in a single source and sending it to channels automatically
Pending ordersProducts in orders not yet shipped still appear "in stock"Reserving stock the moment the order arrives
Returns and cancellationsA returned product is added to stock without inspection, or not added at allTaking it into stock after inspection, releasing reserved stock on cancellation
Count discrepancyThe system shows 5 units, the shelf has 3Regular counts, frequent checks on fast-moving products
Physical store saleA product sold in the store is not entered into the systemMaking store sales from the same inventory system as well

What methods are used for inventory sync?

In short: There are three methods: manual (through the panel or Excel), an XML feed and API integration. Manual updates may be enough for small catalogs; XML performs bulk transfers at set intervals; an API passes every stock change to all channels within minutes, often within seconds.

Manual (panel / Excel)XML feedAPI integration
How does it work?Stock is changed by hand on each channel or uploaded via ExcelThe channel reads the product and stock list from a file at set intervalsWhen stock changes, the new number is sent to the channel immediately
Update speedHours or daysDepends on how often the channel reads itClose to real time
WorkloadHigh, ongoingLow after setupLow after setup
Overselling riskHighMediumLow
Does it also receive orders?NoUsually not, only products and stockYes, order, status and invoice information is also transferred
Best suited forFew products, a single channel, low salesSupplier feeds, reseller networks, catalog sharingMultiple marketplaces and regular daily orders

XML is a common way of sharing a product and stock list as a file; it is ideal for pulling products from a supplier or giving a catalog to resellers. Working with marketplaces in both directions, that is, both sending stock and receiving orders, is done through marketplace APIs. We explained the XML-based sales model in our article XML reselling.

How much does sync delay increase the risk of overselling?

In short: Exposed order risk = Hourly sales × Delay (hours). For a product that sells 48 units a day, if stock is updated once an hour, 2 orders can be taken with outdated stock information; if it is updated four times a day, 12 orders.

During the delay, each channel keeps selling with the stock count from the last update. When stock is plentiful, this is not a problem; but when stock runs low, orders that come in during the delay may be for products that no longer exist. The chart below shows the number of orders that "could be taken with outdated stock" by delay, for a product selling a total of 48 units a day (2 units an hour) across all channels:

ScenarioOrders that can be taken with outdated stock information as the delay grows
  1. Update every 15 minutes0.5 orders
  2. Hourly update2 orders
  3. Manual update four times a day (6 hours)12 orders
  4. Update once a day (24 hours)48 orders

Example: a product that sells 48 units a day. Calculation: hourly sales (2) × delay (hours).

This calculation also tells you how much buffer stock you need. If stock is updated every hour, never showing the last 2 units to marketplaces largely eliminates the overselling risk caused by the delay. With real-time sync, this buffer drops to one unit, or even zero.

How are available stock and buffer stock calculated?

In short: Available stock = Physical stock − Stock reserved for pending orders − Items awaiting inspection − Buffer stock. Buffer stock = Hourly sales × Sync delay (hours) + Safety margin. Marketplaces are sent available stock, not physical stock.

FormulaFour calculations for finding the stock to send to channels
  1. Exposed order risk = Hourly sales × Delay (hours)
  2. Buffer stock = Hourly sales × Delay + Safety margin
  3. Reserved stock = Quantity of products in orders not yet shipped
  4. Available stock = Physical stock − Reserved stock − Items awaiting inspection − Buffer stock

The safety margin is added for count discrepancies, sudden sales spikes during campaigns and the possibility of damaged products.

Example: there are 100 units of a product in the warehouse. 12 units belong to orders not yet shipped, and 3 units have come back as returns and are awaiting inspection. The product sells 2 units an hour, stock is updated once an hour and you want to keep a safety margin of 3 units. Buffer stock is 2 × 1 + 3 = 5 units.

Stock calculationFrom 100 units of physical stock, 80 units are sent to marketplaces
  1. Physical stock in the warehouse100 units
  2. Reserved for pending orders−12 units
  3. Returned, awaiting inspection−3 units
  4. Buffer stock (2 × 1 hour + 3 safety margin)−5 units
  5. Available stock sent to channels80 units

Prepared with sample values.

Buffer stock is not a permanent loss: as the product runs low, it shows as "sold out" on the channels, but the buffered items stay in the warehouse and can be used in the physical store, for a phone order or until the next stock receipt if needed. Because sales speed up during campaigns, the buffer should also be increased temporarily.

Key numbersFour numbers from the sample product's stock calculation
  • 48units: the product's daily sales across all channels
  • 12orders: orders that can be taken with outdated stock when updating by hand four times a day
  • 5units: recommended buffer stock with hourly updates
  • 80units: available stock sent to channels from 100 units of physical stock

Prepared with sample values.

Recommended readingHow Do You Manage Products with Variants on a Marketplace? A Guide to Size, Color, SKU, Barcode and Variant Matching

Should stock be distributed to channels from a shared pool or by quota?

In short: For most businesses, a shared pool is the most efficient approach: all channels see the same available stock, and the product goes to whichever channel sells first. A channel quota means a fixed amount reserved for one channel; it is used to protect a priority channel when stock is limited.

Shared poolChannel quota
How does it work?80 units of available stock appear as 80 on every channelOf the 80 units, for example, 40 are reserved for one marketplace, 25 for another and 15 for the website
AdvantageStock does not run dry on the best-selling channel or sit idle on any channelThe product does not sell out on the priority channel, and campaigns can be planned per channel
DisadvantageRequires fast syncWhile a product sells out on one channel, the quota may sit idle on another
Best suited forNear-real-time sync, a large catalogLimited-stock products, channel campaigns, slow sync

The two methods can also be used together: most of the catalog sells from the shared pool, while a quota is reserved for a specific channel for a small number of campaign products. Whichever method you choose, the stock count is still kept in a single source; the quota only determines how much is sent from that source to the channel.

In what order is stock updated when an order arrives?

In short: The order is created on a channel, the integration pulls it into the main system, the product is reserved from stock and the new available stock is sent to the other channels; once the order is invoiced and shipped, stock drops for good, and if it is cancelled or returned, the reserved stock is released.

Order flowHow one order updates stock in multichannel selling
  1. 01
    The order is placedThe buyer purchases the product on a marketplace.
  2. 02
    The order is importedThe integration pulls the order into the main inventory system.
  3. 03
    Stock is reservedThe quantity is deducted from available stock and held as reserved until shipping.
  4. 04
    Channels are updatedThe new available stock is sent to the other marketplaces and the website.
  5. 05
    Invoice and shippingThe order is invoiced, the shipping label is printed and stock drops for good.
  6. 06
    Cancellation and returnOn cancellation, the reserved stock is released; on return, the product is inspected and taken into stock.

The time between step 2 and step 4 is the sync delay, and buffer stock is set according to this time.

The most critical point of this flow is step 3. Stock should be reserved the moment the order arrives, not when it ships; otherwise, products waiting to be packed keep selling on other channels. In the return process, inspecting the product before taking it into stock is just as important; for return documents, see our article how to issue a return invoice.

Recommended readingHow to Do Marketplace Accounting? A Guide to Sales Invoices, Commission Invoices, Withholding Tax and Payout Reconciliation

The 7 most common mistakes in inventory sync

In short: The most common mistakes are changing stock by hand in channel panels, sending physical stock to channels, deducting stock when the order ships rather than when it arrives and not reflecting returns and cancellations in stock.

  1. Changing stock by hand in the marketplace panel. Stock that is not changed in the main source is overwritten at the next sync, or differences arise between channels. Stock is changed only in the main source.
  2. Sending physical stock to channels. Stock sent without deducting pending orders and returns awaiting inspection leads to selling products you do not have.
  3. Deducting stock at shipping. In the hours between the order and shipping, the same product sells again on another channel.
  4. Not using buffer stock. With delayed sync, the last units sell on more than one channel at the same time.
  5. Forgetting cancellations and returns. If the reserved stock of a cancelled order is not released, the product is taken off sale; if a return is not taken into stock, a sellable product is forgotten in the warehouse.
  6. Using the same barcode on different products. Orders are matched to the wrong product, and the stock of two products is corrupted at once. For products with variants, each variant should have its own barcode.
  7. Reflecting supplier stock directly. The stock in the supplier's XML is not in your warehouse; stock reflected without accounting for delivery time and the supplier's other sales produces overselling.

How do you sync inventory with NetKasam?

In short: NetKasam keeps your stock in a single source; with marketplace and e-commerce integrations, stock drops in NetKasam when orders arrive, and the current stock information is transferred automatically to connected channels.

NetKasam inventory management keeps your products by variant and warehouse; the detailed stock movements report shows the source of every change. The stock of products you create with marketplace integration and e-commerce integration is transferred to your e-commerce website and to the sites you provide XML to; the stock of orders placed on your website is deducted in NetKasam. This way, stock information is processed automatically and incorrect stock counts are prevented.

The Connect plan includes order and stock sync, real-time sync and one XML product feed; on the order management screen, you invoice orders from all channels in bulk and print shipping labels. If you have more than one warehouse, you track stock by warehouse and make transfers with branch and warehouse management. Bookkeeping and the e-Invoice system are always free; plan details are on the pricing page.

Frequently Asked Questions About Inventory Sync

What is inventory sync?

It means keeping a product's stock count the same and up to date across all sales channels, such as marketplaces, the e-commerce website and the store. When a sale happens on one channel, stock drops in the main source and the new number is sent to the other channels.

What is overselling?

It is selling a product that is out of stock because stock information reached the channels late. The result is order cancellation, an unhappy buyer and, depending on the marketplace's rules, a drop in store performance.

How do you track inventory across multiple marketplaces?

Inventory is kept in a single main system, and marketplaces connect to this system via API. Orders are imported into the main system, stock drops there and the current available stock is sent to all marketplaces automatically.

How much buffer stock should you keep?

It is set at hourly sales multiplied by the sync delay, plus a small safety margin. For a product that sells 2 units an hour and is updated every hour, 2 units plus a safety margin is enough.

What is the difference between XML and API?

XML means reading the product and stock list from a file at set intervals and is usually one-way. An API sends the new number as soon as stock changes and also transfers order, status and invoice information in both directions.

Should stock drop when the order arrives or when it ships?

It should be reserved the moment the order arrives. Stock that waits until shipping keeps selling on other channels and leads to overselling.

When is a returned product added back to stock?

It is added after the product reaches the warehouse and is checked to be in sellable condition. Returns awaiting inspection are not included in available stock.

How is inventory synced if I also have a physical store?

Store sales should also be made from the same inventory system. If a product sold in the store is not entered into the system, it keeps appearing in stock on the marketplaces, and overselling occurs.

Inventory sync is the invisible but most expensive detail of multichannel selling. Today, count how many different places you change your stock in; if the answer is more than one, the first step is to move stock to a single source. Then calculate buffer stock for your ten best-selling products and start sending marketplaces available stock instead of physical stock.

Bookkeeping Is Now Completely Free

Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.

Start FreeMarketplace Integration

Read similar articles

19 free tools

Commission, shipping, VAT and profit calculations in your browser, no sign-up needed.

All tools