Choose the service target before interpreting stockouts

Define the decision before reading the percentage

MIT distinguishes stockout-free cycles from demand units supplied immediately.

Ask the business owner what consequence makes a shortage important. A small missing item could prevent completion of an entire installation, while another operation might tolerate occasional partial fulfillment with a clearly explained alternative. Neither context can be understood from an attractive dashboard label alone. Describe the consequence in concrete terms before discussing a target.

Identify the product scope, location and review period. Keep materially different customer promises separate during the discussion. A common target across unrelated products may be convenient administratively but still require justification. Record whether the decision concerns operational continuity, the volume customers receive or another approved objective. Do not silently turn a reporting convention into the organization’s risk preference.

Calculate both views of one history

Fictional history: two of ten cycles had shortages. Eight divided by ten gives 80% shortage-free cycles. Of 1,000 requested units, 990 were supplied immediately; 990 divided by 1,000 gives 99% unit fill. These historical fractions do not establish future probabilities.

Put the two results beside the same underlying record. Then ask what happened during the affected occasions: was a customer unable to finish a job, did an agreed later shipment resolve the issue, or was the request abandoned? Obtain evidence rather than assuming that a small numerical shortfall was harmless. Customer consequences belong alongside the numerical result, not inside an invented adjustment to it.

Keep the original request and fulfillment records intact. If the team discovers an incomplete request log, mark that limitation and determine which conclusions remain supportable. Do not replace unobserved demand with a confident guess simply to complete the table. This exercise depends on the stipulated history; real operational records may need separate investigation before the same calculation is useful.

Choose the objective that matches the commitment

Have the commercial and operations owners describe which failure they would prioritize and why. Consider whether a service promise already commits the organization to a particular outcome. A marketing preference for a larger percentage cannot override that commitment. Equally, a planning target should not become a public guarantee merely because it appears in an internal document.

Compare the cost of improving the relevant outcome with other possible responses. An approved substitute, a more realistic delivery statement or a different assortment might address the customer problem differently from holding more stock. Treat these as proposals requiring their own evidence and authority. The arithmetic does not establish which intervention is effective or authorize a purchase.

If the owners choose to monitor more than one measure, state the role of each. Avoid creating a composite score that hides a serious failure behind a strong result elsewhere. Specify who investigates a disagreement and which customer consequence should guide that investigation.

Make the target usable in a planning handoff

Write the approved objective, its operational scope and the evidence required to evaluate it. Include an example of a failure that should trigger attention and one that should be routed elsewhere. This makes the target actionable without pretending that every exception can be handled by a single threshold.

Ask the planner to explain what additional information is needed before translating the objective into an inventory policy. The record should distinguish an agreed service ambition from a tested replenishment design. Preserve assumptions about customer behavior and unresolved data quality instead of allowing a spreadsheet to conceal them.

Review the objective when the product’s role or customer promise changes. A component that becomes essential to a larger installation may deserve a different discussion even if its sales volume stays constant. Keep the reason for any change so a later analyst can distinguish a policy decision from an apparent improvement caused by altered reporting.

Make the reasoning concrete.

A fictional parts supplier presents the two results above. Sales wants to publish the larger number, while operations is concerned that a missing component can interrupt a customer’s assembly work.

The supplier records the objective and keeps the historical calculation internal until any public wording has its own approval.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Consequence

   What customer task fails when the product is missing?

2. Scope

   Which products and promises belong in this decision?

3. Evidence

   What limitations affect the supplied history?

4. Priority

   Which outcome do the responsible owners want to improve?

5. Handoff

   What must the planner establish before proposing a policy?

Watch for the wrong conclusion.

• Choosing the largest number because it looks reassuring.
• Treating an internal ambition as an external guarantee.
• Changing the reporting scope without preserving the reason.

Sources & scope

Original operational reasoning and explicitly fictional numerical fixtures. Source-derived definitions and mathematical applications remain attributed. Qualified owners decide real policy and purchasing. No account changes, purchase, stock movement or deployment occurs.

• MIT: Inventory Management, Probabilistic Demand →Primary technical documentation · Supports: Supports the two service definitions.