At 07:40 on Black Friday, the merchandising lead opens the 3PL screen and counts 47 units of the hero SKU still on the shelf.
Shopify shows 61 available, because yesterday's marketplace orders sit unapplied and Continue selling is still on from an October restock campaign, while paid traffic is already live against that product page.
Those fourteen extra units become breakfast cancellations once the pick face is empty.
A Shopify oversell during a flash sale is a cancelled order for a unit the warehouse no longer has. You stop it with three lines on each promoted SKU: an available-to-sell number, one hide-or-backorder rule, and a channel-sync check, all written before ads send buyers into checkout.
Picture a caf茅 chalkboard that says how many slices of cake are left. It only stays true when one person holds the chalk, and every till reads the board before it sells a slice. I call this the chalkboard rule: one writer for the stock number during the sale, and every channel reads from it.
Introduction
This article teaches you to write that available-to-sell number, oversell rule, and sync check so flash-sale checkout cannot sell units the warehouse has already lost. The dated walk of checkout, inventory, fulfilment, and support gates before peak season belongs in A Shopify Black Friday Readiness Checklist for Brands That Already Scale.
Merchant and developer threads keep returning to the same pattern: a storefront that looks in stock, a connector that is a few minutes behind, and a cancellation email before breakfast. Shared physical stock across separate products, Flow jobs that decrement siblings, and inventory apps that retry stale writes all widen the same gap. This post stays on the SKU sheet for the hours ads are live.
Why does checkout keep selling the last box?
Flash-sale oversells rarely look like an outage. Checkout completes, the confirmation email sends, and the 3PL rejects the order an hour later because the pick face is empty.
The tickets repeat across merchant and developer threads. Shopify available still shows units while the warehouse count is already zero, or two channels sell the last unit in the same minute. Continue selling accepts the order after available hits zero, a bundle or duplicate listing sells a component another product still claims, or an inventory app retries a failed write and applies the decrement twice.
The same questions show up as three product pages linked to one physical plate, or sold-out gaps that look like a replenishment failure. The public page makes a poor inventory report, and peak traffic only makes it expensive.
Apps and theme scripts that were quiet in September also start fighting when checkout volume jumps. If a widget, a marketplace connector, and a 3PL feed can all change available stock, the first hour of the sale becomes a race for the chalk.
What do on-hand, available, committed and reserved mean?
Shopify inventory is accurate for one item at one location, in the states Shopify owns. On-hand is what is physically at that location, and available is what that location can still sell inside Shopify. Committed is already on an order, while reserved is held, often by a draft order or a process Shopify does not yet treat as committed.
Ads, checkout and the warehouse run on different clocks.
Paid traffic keeps sending people to a product page until someone stops the ad set. Checkout starts from the available number Shopify had when the buyer opened the cart, and the warehouse ships from the units a picker can actually touch. When those numbers drift apart, the store sells a unit that is already gone.
Continue selling when out of stock widens the gap on purpose, because Shopify will take the order after available hits zero. That setting is a backorder policy, and it is only safe when the product page already prints a dispatch date the warehouse has signed.
Who else is holding the chalk?
A second writer makes the same mess without that setting. Marketplace connectors, POS, 3PL feeds and inventory-sync apps all adjust available.
Shopify's 2026 inventory mutations expect compare-and-swap quantities and idempotent retries, so a timeout does not apply the same change twice. Older connectors that still POST a new count from a cached read will overwrite the flash-sale decrement with yesterday afternoon's number.
Shared components add a third failure. Three storefront products that draw from one physical stack need one inventory item, a native bundle, or a dedicated component SKU, because a Flow that decrements the siblings after each sale will miss cancellations, returns and draft-order holds, then sell the last unit three times.
Chalkboard rule diagnostic
How do I check one SKU before the ads start?
Work on the SKU that will take the most paid traffic, and leave the store-wide export for January.
Open Shopify, the 3PL and every marketplace on the same variant. Write four numbers on one row: on-hand at the fulfilment location, Shopify available, committed plus reserved, and what the other channels still claim they can sell. If those disagree by more than the buffer you are willing to eat, the SKU is not ready for a flash sale.
Then answer four questions on the same row:
- Is Continue selling on for this variant?
- Which apps or feeds are allowed to write inventory after the freeze?
- Does another product, bundle, or kit consume the same physical unit?
- What happens in the first sixty seconds after available hits the buffer: hide, dated backorder, or stop spend?
If you cannot name the writer, treat every extra inventory app as a suspect. Admin tasks that still bounce between five systems in ordinary weeks are the same ownership gap, and that year-round version lives in How to Fix Shopify Operational Friction When Simple Tasks Still Take Too Long.
Place one live test order on a phone for the exact offer you will advertise, then refund it. Confirm the line deducts the fulfilment location you will actually pick from, the 3PL sees the order, and Shopify available moves by the same quantity. A checkout that looks healthy while the warehouse never sees the SKU is a different failure, covered in How to Fix Shopify Checkout Abandonment When Your Funnel Looks Healthy.
What number goes on the board?
Fix the SKU sheet before you touch the ad account. For each promoted variant:
Available-to-sell = on-hand at the pick location minus committed, minus reserved, minus marketplace holds, minus buffer
The buffer is units you will not advertise, such as damage, wholesale leakage, or the days you stocked out last year and never counted as lost demand. If you were out of stock, last year's units sold are a floor, so add those missing days back or you will reprint the stock-out on an earlier date.
Put that number into Shopify as the available quantity at the location you will pick from. Leave no second location sellable if it cannot ship the flash-sale promise, and keep incoming purchase orders in incoming until the units are on the shelf.
What happens when the board hits the buffer?
Pick one rule per SKU and print it on the same row.
| Rule | When to use it | What buyers see | What you do in the same hour |
|---|---|---|---|
| Hide | Finite flash inventory with no dated restock | Variant gone, or page redirected | Cut the ad set and remove the SKU from sale collections |
| Dated backorder | You can name a dispatch week the warehouse has signed | Buy button stays, dispatch date on PDP and checkout | Keep Continue selling on only for that SKU, and staff the delay emails |
| Stop spend | The page must stay up for organic or email, but paid traffic must die | Page may remain, add-to-cart optional | Pause campaigns first, then hide if remaining units keep leaking |
Hide suits finite flash inventory with no dated restock. The variant disappears or the page redirects, and in the same hour you cut the ad set and pull the SKU from sale collections.
Dated backorder suits a SKU with a dispatch week the warehouse has signed. The buy button stays with that date on the product page and at checkout, Continue selling stays on for that SKU alone, and someone is staffed to send the delay emails.
Stop spend suits a page that must stay up for organic or email while paid traffic ends. Pause campaigns first, then hide the variant if remaining units keep leaking.
Mixed rules across Shopify, Amazon and wholesale are how the last unit sells twice. If Amazon still has 12 while Shopify has 0, Amazon is on a different rule unless you wrote that allocation into available-to-sell that morning.
How often should I read the board?
Run the sync check the morning the offer goes live, then again every two hours while ads spend. Read Shopify available at the pick location, 3PL on-hand with the open pick backlog, and each marketplace's remaining quantity. Confirm Continue selling is still off unless the SKU sits on the dated-backorder rule.
When remaining units hit the buffer, carry out the rule in the same hour, and hide the product and cut spend together. A hidden product with a live ad is still an oversell you paid for.
Who gets the chalk during the sale?
Give one system permission to write Shopify available. The 3PL or ERP can hold the chalk if it already owns on-hand, and Shopify can hold it if every other channel only reads.
If a connector still adjusts inventory from a cached count, switch that write off for the weekend or replace it with a compare-and-swap update that refuses to apply when the quantity has already changed. Shopify now documents that pattern for inventory mutations, and peak weekend is a poor time to discover your app still overwrites.
Kits and duplicate listings need a structural change in how the catalogue maps to stock. Use one product with variants, Shopify Bundles against a component SKU, or a dedicated inventory item that every listing reads, because a Flow that subtracts siblings after the order is a second writer with no compare-and-swap and no return path.
Draft orders and invoice checkouts deserve their own line on the sheet. A wholesale invoice that uses real variant IDs so shipping rates calculate can decrement the same flash-sale SKU again, so park those drafts or use inventory behaviour that leaves available stock alone until Cyber Monday is over.
When is it more than a sheet?
Get help when the numbers disagree and you still cannot name a single writer. That usually means a 3PL feed, a marketplace connector and an inventory app all update the same variant, or three product pages share one physical stack with no component SKU. It also shows up when POS, Collective, or a second Shopify store sells the units the flash sale is advertising.
Plus leaves that map exactly as it is. It helps when you already use checkout extensibility and want launch support, which belongs in a plan decision made away from the November inventory sheet. If that decision is still open, use Choosing the Right Shopify Plan before you book a connector rebuild against the freeze.
Finance should hear the volume conversation before the weekend too, because a reserve or delayed payout during the days you are cancelling oversold orders stacks a cash problem on a stock problem. The reserve mechanics sit in Shopify Payments Reserves: Does Upgrading to Plus Change Anything?.
The sale can stay aggressive, as long as one hand holds the chalk.
Conclusion
You can now write a per-SKU available-to-sell number, a hide-or-backorder oversell rule, and a channel-sync check so flash-sale checkout stops at the units the warehouse still has. The sale can stay aggressive if the inventory row stays honest.
If Shopify, the 3PL and your marketplaces still write the same SKU without a source of truth, we scope that through integrations and system optimisation, starting from the SKUs you plan to advertise. If the gap is a custom inventory writer or a bundle that native tools cannot model, that is custom app development. For a discovery conversation that starts from the SKUs you plan to advertise, book a stack assessment.
