The shared-pool problem
When Amazon, Shopify, eBay and WooCommerce all spike, they often drink from one warehouse. Channel-native stock figures lie if each channel thinks it owns 100% of the same carton. Overselling is what happens when allocations are missing and buffers are theatre.
Set a single stock source of truth
Map every channel location to one warehouse model. Keep FBA separate. Publish available stock (on-hand minus allocations and holds), not raw on-hand. OmniRestock’s multi-warehouse model is built around one stock source per warehouse for that reason.
Buffers that actually work
- Channel safety buffer: reserve a fixed % or units of own-warehouse stock for web versus marketplaces.
- Time buffer: stop selling when projected cover on a channel falls under N hours at peak rate, not when on-hand hits zero.
- Inbound buffer: do not sell into POs that are not yet received.
Example: 3PL has 1,000 units. Reserve 200 for Shopify, 100 for eBay, remainder shareable. When shareable hits the time buffer, marketplaces go low-stock while Shopify keeps a promise.
TikTok Shop and other fast channels
TikTok Shop on OmniRestock is coming soon (pending partner approval); until then many sellers use CSV or other connectors. Whatever the pipe, count that velocity in the same warehouse pool. Viral spikes without a buffer are classic oversell events.
Operational controls for peak weekend
- Freeze large wholesale draws without allocation.
- Increase sync frequency where APIs allow.
- Pre-authorise FBM fallbacks for Amazon when FBA dies.
- Staff CS for cancellation offers before chargebacks.
Worked example
Warehouse 800 units. Shopify + Amazon FBM + eBay share it. Peak rates 40+35+25 = 100/day. Without buffers you advertise 800 everywhere and oversell by day two if any channel lags on sync. With a 150-unit web reserve and a 4-hour time buffer on marketplaces, you degrade availability intentionally instead of randomly.
Common mistakes
- Each channel app managing stock independently.
- Selling into open POs.
- No weekend sync monitoring.
- Ignoring FBA vs own-warehouse split.
- Adding TikTok firehose without raising buffers.
A 10-day operating cadence
Peak weeks reward boring rhythm. Use a daily 20-minute stand-up with the same agenda: stockouts in the next 72 hours, inbounds that slipped, ad spend on thin cover, and warehouse labour. Write decisions in a shared note so night shifts and agencies see the same truth.
Assign a single owner for Amazon inbound appointments, a single owner for 3PL labour, and a single owner for ads budgets. Split ownership without a RACI chart is how two people both assume the other paused the campaign.
On Mondays, refresh forward daily rates from the last seven sellable days plus the planned promo calendar. On Wednesdays, re-check restock limits and stranded inventory. On Fridays, snapshot cover for the top 50 SKUs and archive it — you will want that file when January asks what happened.
Cash, fees and contribution profit
Black Friday is not only a units problem. Ad auctions clear higher, refund rates rise, and Amazon festive peak fulfilment fees (where they apply) sit on top of ordinary FBA fees during the published peak window. Re-run contribution profit with peak CPC and peak fees before you approve air freight.
A simple gate: emergency inbound is allowed only when expected contribution after peak fees and freight still clears your floor margin. If it does not, throttle demand instead of buying expensive volume that arrives as the spike ends.
Keep a watch list of aged FBA risk for leftovers. Units that miss the sale and sit into Q1 can attract storage pressure. Plan removals or outlet pricing in December rather than discovering the bill in February.
People, carriers and cut-off times
Inventory plans fail when nobody booked Saturday labour. Confirm 3PL cut-offs for Friday and Cyber Monday in writing. Ask which carriers still pick up late afternoon. Print a packing rules sheet for FBA cartons so you do not burn a day on labelling errors.
Customer service needs macros before the weekend: delay, partial shipment, substitute, and “back on X date”. Silence in the inbox is not calm customers — it is chargebacks later.
After the weekend
On Tuesday, reconcile what sold versus the forecast by SKU. Raise or cut January POs from that file, not from vibes. Mark which backups (FBM, transfers) you would reuse next year and which were chaos. That note becomes next October’s checklist.
How OmniRestock helps
OmniRestock keeps FBA and own warehouses as separate stock sources, forecasts per SKU, and shows stockout and order-by dates so peak decisions stay coherent. Draft POs respect MOQ and case pack; stock write and supplier emails stay off until you enable them. Alerts can go to email, Slack or Teams. If you need a prioritised list before connecting everything, start with the free stockout report.
Buffers that survive flash spikes
Overselling at peak is usually a publishing problem, not a warehouse problem. Each channel API reports “available” from a stale number while orders are still in flight. Introduce a safety buffer per channel (for example 5–10% of weekly peak forecast, or a fixed unit floor on heroes) and sync availability from a single service — OmniRestock or your WMS — rather than letting Amazon MCF, Shopify and eBay each decrement independently.
Time-based cut-offs matter: stop promising next-day on your site two hours before pick cut-off, and pause ads when cover drops below the buffer even if the channel still shows a green status. For TikTok Shop marked coming soon, reserve stock in the plan now so launch day does not steal Amazon cover.
Incident checklist for the big weekend
Staff a stock desk with authority to pause SKUs. Pre-write the pause rule: if free cover < buffer OR inbound ETA slips past Cyber Monday, unpublish non-Amazon channels first, then reduce Amazon ad spend, then switch to FBM if FBA is empty. Log every pause so you can rebuild the forecast after the weekend with stockout-day correction.
See allocated stock, available stock and the excess inventory checker for the opposite problem after peak.
Worked example: one carton, three channels
You hold 300 units of a hero SKU. Amazon forecast needs 180 through Cyber Monday, Shopify needs 90, and you want a 30-unit operational buffer. Publish at most 180 to Amazon and 90 to Shopify (or 150/90 with a 30-unit central buffer held back from both). If Amazon velocity runs hot on Friday morning, you reduce Shopify availability first rather than letting both channels race to zero.
When an order is unpaid or pending, decide whether it reserves stock. Pending Amazon orders that routinely cancel should not lock the same hard allocation as paid Shopify orders. Document the rule before peak; changing reservation logic mid-weekend creates double-sells that support cannot unwind politely.
After peak, reverse the problem: excess cover from timid buffers. Use sell-through and the excess checker to mark units for January promotions instead of letting them age into dead stock. Read the overstock guide once the spike is over.
Pre-mortem before the weekend
On the Thursday before Black Friday, walk the failure modes out loud: WMS sync delay, Amazon pending orders, 3PL cut-off missed, viral SKU at 3× forecast. For each, name the owner and the pause switch. Teams that skip the pre-mortem spend Saturday inventing process under fire.