Finance & operations

A small cost per product can hide a large business loss

Spreading the cost of a possible shutdown across millions of products makes it look small. The business still needs enough cash to cope if it happens.

A backup system may look expensive until you compare its price with the orders a warehouse failure could cost you. Dividing an estimated loss by the number of products sold can help put that spending in context. It lets a business see how much of the money earned on each product might be at risk. But the small figure per product must not hide the large bill that could arrive after one interruption.

A warehouse failure can affect several product lines at once. The business may have to pay for repairs, extra shifts and replacement transport long before it recovers sales or receives an insurance payment. Keep that possible cash need beside the annual estimate when deciding what protection to buy.

Describe the interruption before putting a price on it

Start with a specific production or delivery failure. Estimate how often it might happen over a stated period and what it would cost if it did. Separate repairs, extra running costs and stock that must be discarded. For sales lost permanently, calculate the money those sales would have left after the costs of supplying them. Check that the same stock or other cost is not included twice. Identify which products would be affected and whether a busy season or a different production run would change the loss.

Explain why the consequences differ. Chilled goods may need to move before they become unsafe, while longer-lasting goods may be able to wait. But a warehouse IT failure does not necessarily stop refrigeration. Check what actually fails, whether stock or transport can be replaced and whether customers will accept a later delivery. The product category alone does not tell you the cost.

Show how the estimate is calculated

Label the figure as an estimate for making a management decision. It does not mean the business has incurred that cost on every unit sold. Finance should separately decide whether anything belongs in the accounts or whether prices should change. Use sales volume and loss estimates for the same products and period, and keep a record of the assumptions used to calculate both.

Share the estimated loss between products fairly

Dividing by units sold may make sense if every product uses the affected service in much the same way. Otherwise, time spent on the production line or dependence on a particular factory may give a better comparison. A product sold in small quantities can still be badly affected by the loss of equipment it alone needs. Explain why you chose a way of sharing the cost, then check whether another reasonable choice changes the spending decision.

Keep the total loss visible as well as each product’s share. If one warehouse failure affects several lines, it remains one interruption. Dividing the estimated loss between products must not turn it into several separate losses, or make the total disappear behind a collection of small figures.

Compare costs for as long as the protection will be used

Compare options over the same number of years, including setup, training, maintenance and practice costs. Explain what each option is expected to change. Would it make a failure less likely, get orders moving sooner or reduce one particular cost? Try less favourable assumptions and different sales volumes to see whether the choice still makes sense. Selling a different mix of products can change both the loss and the number of units used to calculate the per-unit figure.

In the example, 2.055 fils per unit sits beside a possible AED  2,055,000 incident. Show when the business might need to pay those costs, separately from the annual average. Check which losses insurance covers, which it excludes, how much the business must pay itself and when a payment could arrive. The maximum amount a policy will pay is not the same thing as the estimated average annual loss. Cyber risk evaluation connects that protection choice to the loss the business may have to fund.

Use an actual interruption to improve the next decision

After a failure, compare the estimate with what happened. Check repair work, extra staff time, discarded stock and customer orders. Record when the first orders left and when the warehouse could handle its normal workload again. Separate orders delivered late from sales lost for good, and check for costs counted twice. If the estimate includes customers leaving, look for evidence rather than blaming every later fall in sales on the incident.

Keep the original assumptions and explain which ones the evidence changes. A recovery record can tell you more about the cost of an interruption without telling you how often another will happen. Revise what the evidence supports, and leave the remaining uncertainties visible for the next spending decision.

Where this applies in our work: Cyber Risk Quantification.