A medical equipment distributor in Kathmandu ran out of a fast-moving pulse oximeter model during the peak of demand season. The item was not on backorder. Nobody had noticed the stock dropping because the purchase manager checked inventory by physically walking the warehouse twice a week. The stockout lasted 11 days - the time it took to place an emergency order, arrange transport from the supplier, and clear the goods. That 11-day gap cost three customer relationships and roughly rū 4 lakh in lost sales.
The expensive part of a stockout is not the lost sale itself - it is the cost of the emergency response and the damaged supplier and customer relationships. Emergency procurement almost always costs more than planned replenishment. Expedited freight, premium pricing from suppliers who know you are desperate, and the goodwill lost with customers who had to go elsewhere all compound the direct revenue loss.
Inventory reorder alerts exist to make stockouts a deliberate choice, not an accident. When the system knows your average daily sales and your supplier's lead time, it can calculate exactly when to alert you to reorder - with enough time remaining to replenish through the normal supply channel, not an emergency one.
Calculate Your Average Daily Demand
The reorder calculation starts with understanding how fast an item actually moves. Average daily demand (ADD) is the total quantity sold over a period divided by the number of selling days. For a fast-moving item sold across every working day, use the last 60 to 90 days of sales data and divide by the number of working days in that period. For seasonal items, use the relevant season's data - Dashain season demand for consumer electronics is not representative of Magh demand. An ERP system calculates this from actual transaction history, which is far more reliable than asking the purchase manager to estimate from memory. For new items without history, use the supplier's demand guidance or industry benchmarks and refine after the first 30 days of actual sales.
Determine the Realistic Supplier Lead Time
Lead time is the number of days from placing an order to having usable stock in your warehouse. For local suppliers, this might be 2-5 days. For import goods via road from India, this is typically 7-14 days under normal conditions. For goods shipped from China via sea or air, lead times range from 21 to 45 days. The critical word is realistic: use the lead time you actually experience, not the lead time the supplier promises. If your China shipments average 32 days but the supplier quotes 25, use 32 in your calculation.
Nepal's supply chain has several sources of unpredictable delay. Birgunj and Bhairahawa border crossings can back up by 3-7 days during peak periods or when customs processing is slow. Monsoon season (Ashad to Bhadra) regularly adds 4-8 days to road transport times due to landslides and road closures on mountain routes. Political events can close borders or limit vehicle movement. A Nepali importer who uses the dry-season lead time as the baseline and fails to add a buffer for monsoon will face stockouts every year between Ashad and Bhadra. Build your lead time estimates from the 75th percentile of actual historical delivery times, not the average - this automatically incorporates occasional delays without being excessively conservative.
Calculate Safety Stock
Safety stock is the buffer quantity held to absorb unexpected demand spikes or supply delays. Without safety stock, any variation from the average - a larger-than-normal order from a key customer, a border delay, or a supplier production issue - immediately creates a shortfall. The standard safety stock formula: Safety Stock = (Maximum Daily Demand - Average Daily Demand) x Maximum Lead Time. For a business selling an average of 20 units per day with a peak of 35 units per day, and a maximum lead time of 18 days versus an average of 12 days: Safety Stock = (35 - 20) x 18 = 270 units. This buffer absorbs both the demand spike and the lead time extension simultaneously. For Nepal's import-dependent businesses, sizing safety stock to cover the monsoon delay period separately from the base calculation is a practical refinement that prevents the seasonal stockout that otherwise happens every year.
Safety stock is a working capital investment. Holding 270 extra units of a rū 500 item ties up rū 1,35,000 in inventory that is sitting idle most of the time. The decision to hold safety stock is a tradeoff between the cost of holding that inventory (typically 15-25% of inventory value per year in carrying costs) and the cost of a stockout. For high-margin, high-demand items or items critical to customer retention, safety stock almost always pays for itself. For low-margin, slow-moving items, the carrying cost may exceed the benefit. Review safety stock levels per item category, not as a blanket policy.
Set the Reorder Point in the System
The reorder point (ROP) is the stock level that triggers the reorder alert. The formula: ROP = (Average Daily Demand x Lead Time in Days) + Safety Stock. Using the earlier example: ROP = (20 x 12) + 270 = 240 + 270 = 510 units. When stock falls to 510 units, the system sends an alert to the purchase manager. At 20 units per day average consumption, the business has 510/20 = 25.5 days of stock remaining. The order will arrive in 12 days average. After arrival, there are still 13.5 days of stock left - that is the safety buffer. The ROP is entered as a field on the item master in the ERP. Once set, the system monitors the balance against this threshold automatically with every transaction.
Connect the Alert to a Purchase Requisition
An alert that requires a purchase manager to manually raise a purchase requisition still has a human delay gap. The most efficient setup connects the reorder alert directly to the purchase workflow - when the stock balance crosses the ROP threshold, the system either auto-creates a draft purchase requisition or places the item on a reorder worklist for the purchase manager's review. The purchase manager reviews the list, confirms quantities, and approves the requisitions in one session rather than monitoring each item independently. This changes procurement from reactive to scheduled - instead of responding to stockout emergencies, the purchase manager is working through a managed replenishment list at a predictable time each day or week.
A reorder point calculation is straightforward. The inputs are average demand, lead time, and acceptable safety stock. What makes it reliable in Nepal is using realistic lead times that include border delays and monsoon disruptions, not optimistic ones. Build from 75th-percentile actual delivery data and your ROP will hold through most supply chain variability.
Purchase manager visits warehouse twice a week. Stockout risk exists between visits for fast-moving items.
Alert fires the moment stock drops to the reorder point - no walkthrough delay, no missed items.
Purchase manager uses the supplier's promised lead time, not the realistic experienced lead time.
System calculates from past GRN data. Nepal border delays and seasonal factors built into the estimate.
Safety buffer exists as an informal feeling rather than a calculated quantity. Inconsistent across items.
Formula-driven buffer absorbs demand spikes and supply delays. Reviewed and updated when conditions change.
First signal of a stockout is a failed delivery or an embarrassed sales rep. Damage already done.
ROP designed to give enough lead time for normal procurement. Stockout becomes a deliberate choice, not an accident.
Urgent orders require premium freight, expedited supplier fees, and sometimes spot-market pricing.
Normal procurement with standard terms and freight. Emergency orders become rare rather than routine.
Frequently Asked Questions
Reorder points should be reviewed whenever the underlying conditions change. This includes: significant changes in sales velocity (new customer, lost customer, seasonal shift), changes in supplier lead time (new supplier, logistics route change), changes in supplier reliability, or significant changes in the cost of holding inventory. As a minimum, reviewing ROPs quarterly for fast-moving items and semi-annually for slower items keeps the system calibrated to actual business conditions. An ERP that tracks both average daily demand and actual lead time history makes this review straightforward - the inputs update automatically from transaction data.
The reorder alert fires when stock reaches the ROP, which is calculated to give sufficient lead time for a normal order cycle. If the purchase team cannot act immediately - approvals are delayed, the supplier is temporarily unavailable - the safety stock buffer exists precisely for this situation. The ROP is set above the safety stock level, so when the alert fires, there is still safety stock remaining as the final buffer. The critical requirement is that the purchase team acts within the window the ROP is designed to provide. If alerts are regularly ignored or delayed, the buffer is consumed and the system cannot protect against stockouts - the process discipline matters as much as the system configuration.
Yes, but with an additional dimension. For perishable goods, the reorder calculation must also consider the shelf life. If a product has a 30-day shelf life and your average daily demand is 10 units, ordering 300 units covers demand perfectly but may leave some stock expiring if demand dips. For perishables, the maximum order quantity is constrained by the shelf life as well as the storage capacity. An ERP that tracks expiry dates per batch can alert not just on low stock but on approaching-expiry stock that needs to be sold or returned before it reaches the write-off threshold. Both alerts - low stock and approaching expiry - are necessary for businesses managing perishable inventory in Nepal.
Intelligent Reorder Alerts Built on Real Transaction Data
MISAC's inventory module monitors stock balances against configurable reorder points set at the item level. Every sales invoice and GRN that changes a stock balance triggers an automatic check against the item's ROP. When the balance crosses the threshold, a reorder notification is sent to the designated purchase manager. The notification includes the current balance, the ROP, the configured lead time, and the suggested order quantity - all the information needed to raise a purchase requisition immediately.
MISAC's AI-assisted demand analysis calculates average daily demand from actual transaction history, updated continuously as new sales and return data arrives. For businesses with seasonal patterns - Dashain, Tihar, or monsoon-affected items - the system recognizes seasonal demand variation and can apply seasonal demand multipliers to ROP calculations for the relevant period. This means the reorder point for a festival item increases automatically in the pre-festival build-up period and returns to the base level after, without requiring the purchase manager to manually adjust every affected item.
The reorder alert connects directly to MISAC's purchase requisition workflow. The purchase manager reviews the reorder list, adjusts quantities if needed, and approves the requisitions - which then route through the configured approval chain and convert to purchase orders for suppliers. From alert to PO issuance, the entire process happens within the same platform. MISAC Intelligence Pvt. Ltd. builds this end-to-end procurement intelligence for trading companies, distributors, and manufacturers across Nepal who have experienced the real cost of running out of stock at the wrong moment.
Ready to See MISAC in Action?
See how MISAC's reorder alert system works for a trading company managing 200+ SKUs with variable import lead times across Nepal's supply chain.