DEV Community

jinguo ren
jinguo ren

Posted on

You Sold the Last One Twice: Fix Overselling Before Black Friday Does It for You

The sale you cannot fulfil is worse than the sale you never made

On October 7, a shop owner asked the Shopify Community a question that every dropshipper has quietly worried about: the supplier's stock figure syncs to the store, but the supplier can sell the last unit somewhere else before the next update runs. What do you do about that gap?

There is no honest answer that removes the gap entirely. Unless the supplier reserves stock for you, your store is always selling against a number that was true a few minutes ago. During a normal week that costs you an awkward email now and then. During Black Friday week it costs you a weekend of cancellations. One seller in a September r/shopify thread described a top product selling 50 units in 10 minutes across several channels, with a sync delay leaving them 30 units oversold on one channel alone — and an estimated $15,000 in lost sales once the cancellations were done. Another seller quoted in a 2026 order-management roundup put last month's oversell damage at roughly $3,000 in cancelled orders, plus the customers who will not come back.

Overselling is not a stock problem. It is a timing problem, and timing problems get worse exactly when sales get better.

Why your stock number is a message, not a fact

Every channel keeps its own copy of your inventory. When something sells, a message has to travel to the other copies and lower them. Those messages queue, fail, and retry. Shopify's own developer documentation warns that webhook delivery is not always guaranteed and tells apps to run reconciliation jobs for exactly this reason. Sellers in the same threads report supposedly real-time sync apps running 8 to 15 seconds behind under load — and Black Friday load is not normal load. Shopify reported merchant sales peaking at $5.1 million per minute at 12:01 p.m. EST on Black Friday 2025. That is the minute your sync is under the most pressure, and the minute a stale number does the most damage.

Three specific holes open the gap wider. First, listing the supplier's full quantity: if the supplier shows 12 and you list 12, the last few units are contested by every other store that supplier feeds. Second, silent sync failure: a sync scheduled every 15 minutes that fails unnoticed leaves you selling against hours-old stock while your dashboard still looks calm. Third, the leftover setting: more than one seller has left "continue selling when out of stock" switched on after a preorder ended, so the store kept selling at zero long after the count correctly hit nothing.

Marketplaces price this mistake for you. Amazon counts seller cancellations over a 7-day window with a target under 2.5%, warning that going above it can cost selling privileges; eBay treats an out-of-stock cancellation as a transaction defect. Your own store has something worse: a customer who paid, waited, and got a cancellation email instead of a parcel.

Shrink the window, in this order

Step 1: Never list the supplier's full count. Hold a safety buffer. The consensus in that October thread was blunt: most small shops keep a small safety buffer — 2 to 5 units depending on how fast the item moves — rather than listing the supplier's exact count. Build the buffer into the import and sync logic so a sync does not overwrite it. For a fast mover heading into Black Friday, be more conservative: holding back around 10% on your best sellers is cheap insurance compared with a cancellation wave. The units you hide are not lost sales. They are the units that absorb the lag.

Step 2: Recheck stock at order time, before fulfilment. A listing-time count is a promise made hours ago. Before an order goes to the supplier, check the supplier's current stock for that variant. If it is gone, you find out in minutes — while you can still offer a substitute, a wait, or a fast refund — instead of days later when the supplier finally replies. This single recheck turns most oversells from a customer-service incident into a routine choice.

Step 3: Alarm stale data, not just zero data. Zero stock stops sales. Stale stock does not, and stale is the dangerous state. If your last successful sync is older than your sync interval by a wide margin — say, no successful update in an hour on a 15-minute schedule — treat the affected products as suspect: pause the fastest movers or drop their listed quantity to the buffer floor until a fresh sync lands. Selling against a number you know is old is a decision, not an accident.

Step 4: Audit the two settings that defeat every sync. Inventory tracking must be on for every variant, and "continue selling when out of stock" must be off unless you are deliberately running a preorder. Check per variant, not per product — the burning setting usually hides on one variant promoted months ago.

Step 5: Consider authorize-now, capture-on-fulfilment for high-risk items. Shopify's delayed payment capture lets you authorize the card at checkout and capture only when the order is fulfilled. If the supplier sold the last unit elsewhere, you cancel and the authorization is released — the customer was never charged, which is a completely different conversation from a refund. Check the limitation first: fulfilment apps that require a "Paid" status before sending the order to the supplier conflict with this setting, so test it on one product before you rely on it.

This is the layer where sync tooling earns its keep. GetDropFlow, the Magento 2 plugin I build, syncs AliExpress prices and stock into a merchant's own store on their own server — and the lesson from building it is that the sync itself is only half the job. The buffer, the order-time recheck, and the stale-data alarm are what make the synced number safe to sell against.

A concrete example: 12 mugs, 7 phantom sales

Take the composite case from a November analysis of Black Friday overselling: a seller lists 12 units of a mug across her store and marketplaces. At noon every channel truthfully shows stock. By 12:06 she has sold 7 units she does not have, because each channel sold against its own copy of "12" while the updates were still travelling.

Now run the same spike with the steps above. She lists 9, holding 3 as buffer. The first sales consume the buffer's protection while syncs catch up, and the order-time recheck catches the moment the supplier's real count hits zero — before the last two orders are sent for fulfilment. Those two customers get a same-hour message offering a substitute or an immediate release of their authorization. Instead of 7 cancellations, a defect mark, and a weekend on the phone, she has 2 handled exceptions and a store that told the truth. She "lost" the margin on 3 hidden units for one weekend. She kept the account health and the customers.

The takeaway

You cannot make a supplier's stock number real-time, and you do not need to. You need the gap between the supplier's truth and your store's number to cost you nothing when — not if — it opens. Hold a buffer, recheck at order time, alarm stale syncs, and audit the settings that sell past zero. Do it this week: Black Friday is November 27, and the busiest minute of the year is exactly when a stale number stops being a rounding error.

How many units of your best seller are you actually willing to hide as a buffer? Tell me your number in the comments — most sellers I ask have never picked one.

— Jinguo, maker of GetDropFlow (https://getdropflow.com)

Top comments (1)

Collapse
 
hiredov profile image
Dov at HireDov •

The framing of stock as a message rather than a fact is useful, and the buffer-per-velocity rule is practical. One angle that seems to get less attention is the supplier side: a buffer protects you from sync lag, but it doesn't tell you when a supplier is reliably slow to update or short on stock. Do you track supplier reliability separately, for example how often a listed count turned out wrong, and use that to set the buffer per supplier instead of per product? That could make the 2 to 5 unit range less of a guess.

(AI-assisted reply from HireDov.)