In October 2023, during a weekly management review, one number stopped everything: 20.5 percent of bestsellers were out of stock simultaneously. Not slow movers, not tail SKUs. Bestsellers. The products that drive the majority of revenue, carry the highest BSR, and are most sensitive to lost sales.
That number triggered a war-room meeting.
Why 20.5% is different from 5%
An out-of-stock event on a single SKU is a supply chain problem. You missed a reorder point, the container was late, something broke in the plan. You fix it and move on.
A 20.5 percent simultaneous OOS rate on bestsellers is a systemic failure. It means the inventory planning process itself is broken, not one SKU's replenishment schedule.
The distinction matters because the response is completely different. A single OOS event gets resolved at the SKU level. A systemic rate that high requires an audit of the entire planning infrastructure: the reorder triggers, the lead time assumptions, the safety stock calculations, the PO creation workflow, and the visibility into in-transit inventory.
There is no clean threshold that universally separates "normal operational blip" from "systemic failure." But across well-run Amazon businesses, a simultaneous OOS rate above 5 percent on bestsellers usually means something is wrong with the process, not just the timing. At 20 percent, the process is definitely broken.
The downstream effects that don't show up immediately
When a bestseller goes out of stock, the damage doesn't resolve when the product comes back in stock. Three things happen in sequence, and each one compounds the next.
BSR deterioration. Amazon's BSR algorithm weights recent sales heavily. A product that was selling 50 units per day and drops to zero for two weeks comes back with a severely degraded rank. Recovering that rank requires time and often increased PPC spend to stimulate velocity.
PPC efficiency drops. Sponsored ads on a product with declining BSR get lower impression share and higher cost per click. You're paying more to reach fewer people for a product that's already lost momentum.
Conversion rate erosion. Customers who found your product OOS during the stockout period often bought a competitor and didn't come back. The listing's conversion history during the OOS period, even if not fully visible in your reporting, affects the organic ranking signals Amazon weights.
The actual cost of that 20.5 percent OOS event extended well beyond the two to three weeks those products were unavailable. The recovery period was longer than the stockout.
What Flieber was built to prevent
The structural fix that followed the October 2023 event was Flieber onboarding. The process took multiple sessions to configure properly: bundle setup, SKU-to-ASIN mapping, Skubana integration, multi-channel fulfillment workflow, and the forecasting model configuration itself. The platform's value is not that it predicts demand perfectly. It's that it creates a systematic early warning structure so that the reorder point on a bestseller is calculated, visible, and actionable before the product goes out of stock.
Before Flieber, the early warning process was manual: someone was watching stock levels periodically and raising the alarm when things looked low. That's a person-dependent system, and person-dependent systems fail when the person is busy, sick, or distracted by something else.
After Flieber, the system flags the reorder point. The signal doesn't require anyone to be watching.
What the right OOS target actually looks like
Different types of Amazon businesses should have different targets, and the targets should be calculated explicitly rather than assumed.
For high-SKU-count businesses with a long tail of products, a small number of tail SKUs being OOS at any given time is inevitable and not worth optimizing against. The focus should be on a zero-tolerance policy for bestsellers defined as your top 20 percent of SKUs by revenue. If any product in that top tier is OOS, it's a priority issue.
For low-SKU-count businesses (under 20 SKUs), every OOS event is meaningful. A brand with 10 SKUs that has two products out of stock is running at 20 percent OOS across the entire catalog. There is no tail to absorb the variance.
For seasonal businesses, the pre-season inventory build is the highest-stakes planning window. An OOS event in October or November, during the demand peak, causes disproportionate BSR and revenue damage compared to an OOS event in February.
Set the target explicitly: bestsellers at zero simultaneous OOS. Define which SKUs count as bestsellers by a revenue threshold, something like the top 80 percent of trailing 90-day revenue. Review that list quarterly, because the roster changes.
The week before matters more than the week of
The 20.5 percent rate was a symptom of what happened weeks earlier. The reorder points weren't triggered in time, the POs weren't created in time, and the containers weren't ordered in time. By the time the OOS rate hit 20.5 percent, the window to fix it had already closed.
The relevant question is never "why are these out of stock right now?" It's "what was the inventory level eight weeks ago, and why didn't the process flag a problem then?"
That's the audit. Run it backward from the stockout, not forward from the dashboard.
