A per-unit view can help finance and operations understand how disruption relates to the products they make. It puts an estimated annual exposure alongside volume and contribution margin. Used carefully, it is a planning lens for comparing dependencies and investment choices.
The method needs clear boundaries. A disruption does not occur evenly across every unit, and shared infrastructure affects several products at once. The calculation should preserve those features rather than hiding them inside an apparently precise unit cost.
Define the exposure before dividing it
Begin with a scenario affecting a production or distribution workflow. Estimate its frequency over a defined period and the loss if it occurs. Separate response costs, additional operating costs, stock losses and lost contribution. Identify which products depend on the affected workflow and how that dependence changes by season or production run.
A product requiring chilled storage and a shelf-stable product may have different consequences from an interruption. Those differences should come from the operation: handling limits, replacement options and the ability to defer orders. Product category alone cannot establish a reliable risk estimate.
Keep the arithmetic transparent
An expected-loss allocation is a management estimate. It does not automatically become a cost-of-goods-sold entry, provision or product-price adjustment. Finance needs to determine the accounting treatment separately. Keep the planning model labelled and traceable to its assumptions.
Choose an allocation that reflects the dependency
Shared services need a documented allocation method. Volume, production time or reliance on a particular facility may be useful bases, depending on the scenario. Test whether the method would distort the comparison between products. A low-volume product may require a critical capability that a simple volume allocation understates.
Preserve a view of the whole scenario alongside the allocation. Dividing exposure among product lines does not make a simultaneous interruption disappear. When estimating a portfolio, account for shared dependencies and avoid counting one warehouse outage as several independent events.
Compare the investment over its operating life
Include deployment, training, maintenance and the work needed to test the control. Estimate its effect on the specific loss scenario and explain the supporting evidence. Use a common time horizon and show how the comparison changes with volume, event frequency and impact. A change in the product mix can alter both the denominator and the exposure.
Keep cash needs and severe outcomes visible. The average allocated amount per unit may be small while a single incident creates a large immediate cost. Insurance also needs an event-level assessment of coverage, exclusions, deductibles and timing. A policy limit and an expected-loss estimate cannot be treated as interchangeable amounts.
Use observed disruption to improve the model
After an interruption, reconcile the estimate with response effort, stock decisions, customer orders and the time needed to regain throughput. Distinguish delayed sales from permanently lost sales. If customer retention is included, show the evidence and compare it with normal variation rather than assuming every change was caused by the incident.
Update the scenario when the evidence changes. Keep earlier assumptions available so that finance and operations can understand why the estimate moved. This turns the per-unit view into a continuing conversation about how the products are made and delivered.
The useful outcome is a shared understanding of the dependency, the proposed improvement and the uncertainty that matters to the choice. Unit economics can make that conversation concrete while the full operational scenario keeps it honest.