A stock-out of a top-10 SKU costs more than a day of sales. On Amazon it damages the buy-box; on Shopify it loses a converting cart; on Allegro it costs search ranking that takes a week to recover. Vedron’s low-stock reports catch shortages 14 to 60 days before they become stock-outs, weighted by SKU velocity and supplier lead time, and the cycle count workflow keeps the stock figures honest so the alerts are trustworthy.
Reorder point math, not a flat threshold
A single “alert when stock drops below 10” threshold misses two things: it ignores how fast the SKU is selling, and it ignores how long the supplier takes to deliver.
Vedron calculates reorder point per SKU as:
Reorder point = (daily sales velocity × supplier lead time in days) + safety stock
A SKU selling 5 units a day with a 30-day supplier lead time and 10 units of safety stock has a reorder point of 160. A SKU selling 50 a day with a 60-day lead time and 50 units of safety stock has a reorder point of 3,050.
Both are correctly timed warnings; a flat threshold would warn too late on the first and too early on the second.
Velocity classification: ABC
Vedron classifies SKUs by revenue contribution:
- A SKUs (top 20 percent of revenue, typically 5 to 10 percent of SKUs): watched daily, reorder point reviewed monthly
- B SKUs (next 30 percent of revenue, typically 15 to 25 percent of SKUs): watched weekly
- C SKUs (the rest): watched monthly, reorder point reviewed quarterly
The low-stock report defaults to showing A and B SKUs that are approaching or below reorder point, so the daily inbox is 10 to 30 lines, not 500.
Lead-time learning
Supplier lead times drift. A supplier promising 30 days delivers in 45 for two months in a row, then back to 30. Vedron tracks actual lead time per supplier per SKU from PO date to goods-in date, and the reorder point uses a rolling average of the last 6 deliveries.
If the lead time for a supplier moves out, the reorder points on every SKU from that supplier move up automatically. The seller does not have to track it manually.
Cycle counts
Stock figures drift from the system number through pick errors, mis-sales, damage and theft. A 2 percent drift at the SKU level is normal; at 5 percent, the reorder alerts stop being trustworthy because the system thinks there is stock when there is not.
Vedron schedules cycle counts: a subset of SKUs is counted each day by the warehouse, so the full catalog is counted over 30, 60 or 90 days (chosen by the operator). The cycle count tool runs on a tablet with a scanner: scan the location, scan the SKU, enter the count, submit.
Discrepancies above a configurable threshold (typically 1 unit for A SKUs, 2 units for B/C) require a second count. Resolved discrepancies post to a stock adjustment account for review.
Multi-location handling
For a seller with multiple warehouses or shops, the reorder point is per location per SKU, not global. A regional shop that sells 2 of a SKU a week and the main warehouse that fulfills 100 a week need different reorder points on the same SKU.
Vedron also supports interbranch transfer suggestions: if one location is approaching stock-out while another has surplus, the system suggests a transfer before triggering a supplier reorder.
FAQ
How is the reorder point calculated?
Daily sales velocity multiplied by supplier lead time in days, plus a safety stock buffer per SKU. Velocity is the rolling average of the last 30 or 90 days (configurable). Lead time is the rolling average of the last 6 deliveries from that supplier for that SKU.
What is ABC classification and why does Vedron use it?
ABC classifies SKUs by revenue share: A is the top 20 percent, B the next 30 percent, C the rest. The low-stock report defaults to A and B SKUs so the daily alerts stay actionable; C SKUs are reviewed monthly.
How often should I run cycle counts?
A full-catalog cycle over 30, 60 or 90 days is typical. A SKUs are counted most frequently (monthly), C SKUs least (quarterly). Vedron schedules the subset per day so the warehouse spends 15 to 30 minutes per day on counts, not a full-stop stocktake once a year.
What happens when a cycle count shows a discrepancy?
Discrepancies above the threshold (typically 1 unit for A SKUs) require a second count. If the discrepancy holds, Vedron posts a stock adjustment and flags it for review. The adjustment account is the audit trail for how actual stock drifted from system stock.
Can I handle different lead times for the same SKU from different suppliers?
Yes. Each supplier-SKU pair has its own lead time and its own reorder point calculation. A SKU with a primary and a backup supplier has two lead times tracked separately.
