<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tibeau De Grauwe</title>
    <description>The latest articles on DEV Community by Tibeau De Grauwe (@stockflowsystems).</description>
    <link>https://dev.to/stockflowsystems</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4249598%2F98aa5856-6724-4340-bbb8-b328e8274d68.png</url>
      <title>DEV Community: Tibeau De Grauwe</title>
      <link>https://dev.to/stockflowsystems</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/stockflowsystems"/>
    <language>en</language>
    <item>
      <title>Syncing Shopify Inventory Across Multiple Sales Channels Without Overselling</title>
      <dc:creator>Tibeau De Grauwe</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:32:21 +0000</pubDate>
      <link>https://dev.to/stockflowsystems/syncing-shopify-inventory-across-multiple-sales-channels-without-overselling-31mh</link>
      <guid>https://dev.to/stockflowsystems/syncing-shopify-inventory-across-multiple-sales-channels-without-overselling-31mh</guid>
      <description>&lt;p&gt;&lt;em&gt;Why “available” is not the same as “on the shelf,” and a practical setup that keeps Shopify, marketplaces, and a till from selling the same unit twice.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Overselling is rarely a software mystery. It is usually a timing problem dressed up as a stock problem. A customer buys the last navy jumper on your Shopify store. At almost the same moment, another customer buys it on Amazon, or a staff member sells it at the market stall, or a wholesale invoice is still sitting in someone’s inbox. For a few minutes — sometimes a few hours — two systems both believe they own that unit.&lt;/p&gt;

&lt;p&gt;The refund, the apology email, and the cancelled pick are the visible cost. The quieter cost is that marketplaces score you down, regular customers stop trusting the product page, and you start hiding inventory behind “contact us for availability,” which is another way of saying the catalogue is no longer for sale.&lt;/p&gt;

&lt;p&gt;You can fix most of this without an enterprise order-management system. You need one place that is allowed to tell the truth, a clear definition of &lt;em&gt;available to sell&lt;/em&gt;, and a sync that is fast enough for your volume.&lt;/p&gt;

&lt;h2&gt;
  
  
  One shelf, several storefronts
&lt;/h2&gt;

&lt;p&gt;A typical small brand today might sell from:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a Shopify theme (webshop)&lt;/li&gt;
&lt;li&gt;Shopify POS or a retail till&lt;/li&gt;
&lt;li&gt;Amazon, Bol, Etsy, or another marketplace&lt;/li&gt;
&lt;li&gt;a wholesale or Instagram-DMs channel that never touches Shopify automatically&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Shopify can be the system of record for some of these, and a follower for others. That distinction matters. If Amazon is allowed to accept an order on a 20-minute delay, and Shopify POS is allowed to sell in real time, they will collide.&lt;/p&gt;

&lt;p&gt;Write down, for each channel:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Who is allowed to &lt;em&gt;promise&lt;/em&gt; a unit to a customer?&lt;/li&gt;
&lt;li&gt;How quickly does a sale reduce the shared stock figure?&lt;/li&gt;
&lt;li&gt;What happens to a unit that is reserved, in a draft order, in a fulfilled-but-not-shipped state, or in a return?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you cannot answer those three questions, you do not have a sync. You have a collection of numbers that occasionally agree.&lt;/p&gt;

&lt;h2&gt;
  
  
  Available to sell is a calculated number
&lt;/h2&gt;

&lt;p&gt;Physical stock is an input. Sellable stock is a decision. A useful starting formula is:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Available to sell = on hand − reserved / unfulfilled orders − damaged or held stock − safety buffer + inbound you are willing to pre-sell&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Most oversells come from treating “on hand” as “available.” Common traps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Unfulfilled Shopify orders&lt;/strong&gt; still occupy units. If your marketplace integration reads raw on-hand instead of available, it will sell stock that is already in a pick list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Draft orders and manual reserves&lt;/strong&gt; (a shop visit this afternoon, a B2B quote, a photo-sample) never reach the channel. Those units must be reserved somewhere, even if that somewhere is a dedicated “hold” location.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Returns&lt;/strong&gt; are not sellable the moment the parcel arrives. They need a quick inspect-and-putaway step. Until then, they should sit in a returns bin that is not shared with the webshop.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-location stock&lt;/strong&gt; is not a single pool. Five units in a store you cannot ship from today are not five units you should advertise on a 24-hour marketplace SLA.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Shopify locations help here, but only if each location has a job: “online fulfilment,” “shop floor,” “returns,” “wholesale hold.” Mixing them in one bin is how a POS sale tonight steals tomorrow’s web order.&lt;/p&gt;

&lt;p&gt;A practical walk-through of this split sits in StockFlow’s guide to &lt;a href="https://www.stockflowsystems.com/how-to-manage-multi-location-inventory" rel="noopener noreferrer"&gt;managing multi-location inventory&lt;/a&gt;. The same idea applies whether you have two spare rooms or two formal warehouses.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose a sync pattern that matches your volume
&lt;/h2&gt;

&lt;p&gt;There is no single correct architecture. There is a correct one for your order volume and your risk tolerance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pattern A — Shopify as the hub.&lt;/strong&gt; All channels read and write Shopify inventory. Marketplaces connect through Shopify’s own channels or a well-supported connector. This works well if most orders already flow through Shopify and you can live with the connector’s lag (often a few minutes, sometimes longer during a sale). Keep POS on the same inventory location as the till, not on the online location, unless you genuinely fulfil store and web from one shelf.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pattern B — an inventory layer in the middle.&lt;/strong&gt; Shopify, the till, and the marketplaces are channels. A dedicated inventory tool holds on-hand, reservations, and buffers, and pushes &lt;em&gt;available to sell&lt;/em&gt; out to each channel. This is the better pattern once you have more than one fulfilment location, or once a marketplace integration has already burnt you during a promotion. It is also the right pattern when you need a buffer that Shopify’s native fields do not express cleanly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pattern C — manual with discipline.&lt;/strong&gt; If you sell 20 orders a week across two channels, a shared spreadsheet updated twice a day can still work. It stops working the first time you run ads on a Friday and pack orders on a Monday. Do not scale paid traffic on Pattern C.&lt;/p&gt;

&lt;p&gt;Whatever you choose, measure lag with a stopwatch once. Place a test order, then refresh the other channel. If the second channel still shows the unit 15 minutes later, that is your oversell window. Close it with a buffer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use buffers on purpose, not as a vague “cushion”
&lt;/h2&gt;

&lt;p&gt;A channel buffer is a number of units you refuse to advertise on that channel. It is not the same as safety stock for purchasing, although the two are cousins.&lt;/p&gt;

&lt;p&gt;Example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;On hand in the online warehouse: 18&lt;/li&gt;
&lt;li&gt;Reserved in open Shopify orders: 3&lt;/li&gt;
&lt;li&gt;You will not pre-sell inbound stock&lt;/li&gt;
&lt;li&gt;Amazon buffer: 2 (to cover sync lag and a messy return)&lt;/li&gt;
&lt;li&gt;Webshop buffer: 0 (Shopify is your fastest, most accurate channel)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Available to Amazon = 18 − 3 − 2 = 13&lt;br&gt;&lt;br&gt;
Available to the webshop = 18 − 3 = 15&lt;/p&gt;

&lt;p&gt;You will occasionally look “out of stock” on Amazon while the webshop can still sell. That is a feature. You are choosing a slightly lower advertised quantity over a dirty cancellation rate.&lt;/p&gt;

&lt;p&gt;Raise buffers when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a sale or influencer post is about to hit&lt;/li&gt;
&lt;li&gt;a connector has been unreliable&lt;/li&gt;
&lt;li&gt;you are moving warehouse, doing a stock count, or expecting a delayed inbound&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Lower them again afterwards, or you will strand sellable stock.&lt;/p&gt;

&lt;h2&gt;
  
  
  A setup checklist you can finish in a week
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Clean the catalogue.&lt;/strong&gt; One SKU, one barcode, one inventory item. Duplicate products across channels are a classic source of “we still have it on Etsy.”&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Name your locations honestly.&lt;/strong&gt; Online, store, returns, quarantine. Do not fulfil web orders from a location that is not staffed to pick.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Decide the system of record&lt;/strong&gt; and write it down in one sentence the whole team can repeat.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Connect each channel once&lt;/strong&gt;, then run a test sale and a test refund on every path. Watch the number move. If it does not move, the integration is theatre.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set buffers&lt;/strong&gt; on the slower or less trusted channels.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stop selling from side channels that cannot reserve stock&lt;/strong&gt; — WhatsApp, email quotes, market stalls — unless those sales are booked into the same system within minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reconcile daily for two weeks&lt;/strong&gt;, then weekly. Compare on-hand, available, and what each storefront is advertising. The first week will be uncomfortable. That is the point.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If Shopify is your main storefront, start from a connector or inventory tool that is built for &lt;a href="https://www.stockflowsystems.com/integrations/shopify" rel="noopener noreferrer"&gt;Shopify inventory&lt;/a&gt; rather than a nightly CSV drop. A once-a-day file is a photograph. Overselling happens between photographs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to watch after you go live
&lt;/h2&gt;

&lt;p&gt;Track three numbers for a month:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cancellation rate due to no stock&lt;/strong&gt;, by channel&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Time-to-sync&lt;/strong&gt; after a sale (in minutes)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Variance&lt;/strong&gt; between physical counts and system on-hand, especially on the SKUs you advertise in more than one place&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If cancellations fall but variance stays high, you have improved the storefront and not the warehouse. If variance is tight but cancellations remain, the lag or the buffer is wrong. Fix the actual cause. Do not add another app on top of a messy location structure.&lt;/p&gt;

&lt;p&gt;Overselling is a design problem. Once available-to-sell is defined, and every channel is either fast or buffered, the last jumper can only be sold once.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Tibeau De Grauwe is the founder of StockFlow, a Belgian cloud inventory platform for small businesses and webshops. He writes about practical stock control, from reorder points to barcode scanning, at &lt;a href="https://www.stockflowsystems.com" rel="noopener noreferrer"&gt;stockflowsystems.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>shopify</category>
      <category>ecommerce</category>
      <category>inventory</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
