The supply chain numbers I define before they reach a business review

A weekly supply-chain business review can burn an hour arguing over which version of fill rate is right and still leave without deciding whether service, fulfillment, or working capital needs action this week.

Fill rate, on-time delivery, and inventory turns sound like shared language until planning, warehouse operations, and finance each carry their own clock, grain, and exclusions into the room under the same labels. Once the deck shows one number per label, the meeting becomes a dashboard debate instead of a decision.

I would rather define each KPI’s boundary before the review than untangle it in the meeting. If one supply-chain label cannot hold the same owner, clock, grain, exclusions, and intended decision for planning, warehouse, and finance at once, I split it and name the variants before anyone presents a number.

Problem

Supply-chain KPI labels often look stable until teams ask what they include.

Fill rate can mean complete orders filled from available stock, order lines filled, units shipped within a short window, or demand covered after backorder recovery. On-time delivery can be measured against requested date, original promise date, latest customer-accepted promise date, planned ship date, actual ship timestamp, or actual delivery timestamp. Inventory turns can be a finance-owned value calculation for a fiscal period or an operational shortcut for SKU movement through a warehouse.

These are not cosmetic wording gaps. Each one changes who owns the number, which clock it runs on, and which decision the review is allowed to make with it.

The pattern I watch for is a review deck with three headline KPIs and no boundary card behind them. Planning reads fill rate as demand coverage. Warehouse operations reads the same label as complete customer orders filled from stock on the first execution attempt. Finance reads it as a service signal that should support or contradict the working-capital story. The label is shared; the definitions underneath are not, and the decisions they imply do not overlap.

That is the same failure shape I watch for in metric drift across dashboards. The supply-chain version is harder to catch because the disagreement usually starts before any dashboard exists, inside the definitions teams carry into the meeting.

Default approach

Before the number enters the review deck, I write a short KPI boundary card.

• Start with the review decision, not the formula. The card should state, in one line, the question this metric is allowed to answer in this meeting and who gets to act on the answer.
• Lock the clock. Order date, requested date, original promise date, latest customer-accepted promise date, planned ship date, actual ship timestamp, actual delivery timestamp, data-complete cutoff, and fiscal period are different clocks, and the card picks one on purpose.
• Write exclusions in business language. Cancelled orders, customer reschedules, substitutions, backorders, partial shipments, carrier exceptions, returns, obsolete inventory, and consignment stock each need an explicit keep-or-drop decision, not a buried SQL filter.
• Name the grain before aggregation. Order, order line, unit, shipment, SKU-location-day, and fiscal-period inventory value each answer a different question, and averaging them silently is how a supposedly shared metric drifts.
• Assign one named owner who can approve changes to timing, exclusions, or grain without having to ask another team first.
• Decide up front whether the review gets one shared definition or separately named variants, and record the decision on the card. Do not defer that call to the meeting.

The last bullet carries the most weight. Splitting a KPI is not a naming exercise; it is an admission that one shared label would otherwise make planning, warehouse, or finance wrong in order to make another team precise.

Example: the boundary card I want before the review

Here is a weekly supply-chain business review I would rather catch before it ships than defend after.

The service-and-inventory slide currently reads:

Weekly supply-chain business review
- fill rate: 92%
- on-time delivery: 89%
- inventory turns: 5.1

The disagreement starts before the slide is up.

Planning puts fill rate at 96%, counting units eventually shipped against the demand created that week. Warehouse operations puts it at 88%: complete customer orders filled from available stock on the first execution attempt, with cancellations and backordered lines excluded. Finance wants neither version anywhere near the close, because partial shipments and backorder recovery push revenue across period boundaries.

On-time delivery repeats the shape. Transportation reports 91% against the latest customer-accepted promise date and the actual delivery timestamp. Warehouse operations prefers 95%, measured against planned ship date and actual ship timestamp, and stops the clock there. Sales asks why an order that missed the original promise date still counts as on time after a customer reschedule quietly rewrote the target.

Inventory turns behaves like one number until someone asks what the denominator is. Finance is using finished-goods inventory value averaged across the completed fiscal period with COGS for the same period. Planning is watching SKU velocity and days of supply. Warehouse operations is watching movement and capacity pressure against a physical footprint. All three views answer real questions; none of them are the same metric, and none of them should inherit the single label inventory turns on an executive slide.

Here is the boundary card I would write before the next deck goes out, with one owner and one intended decision per approved metric:

Supply-chain KPI boundary card
Review: weekly supply-chain business review
Decision: which numbers are safe as shared review KPIs, and which need named variants

1. fill rate
- review label: fill rate
- approved review metric: warehouse_order_fill_rate
- intended decision: did fulfillment fill customer orders completely from available stock on the first execution attempt?
- owner: warehouse operations / fulfillment analytics
- timing: first ship attempt or agreed ship-from-stock window
- grain: order-level complete fill unless the card explicitly says order-line or unit fill
- exclusions to state: cancellations, customer future-dated orders, substitutions, split shipments, manual holds, test orders, backorders
- split decision: planning gets a separate supply-availability metric; finance does not use this number for close or working-capital review

2. on-time delivery
- review label: on-time delivery
- approved review metric: customer_on_time_delivery
- intended decision: did delivered orders meet the agreed customer promise window?
- owner: transportation / logistics, with customer-service ownership for promise-date policy
- timing: promise date source and actual delivery timestamp are locked before review
- grain: complete order unless the card explicitly says shipment or order line
- exclusions to state: customer reschedules, carrier exceptions, missing proof of delivery, cancelled orders, pickup orders, early-but-incomplete deliveries
- split decision: warehouse ship timeliness and customer delivery performance stay separate if they use different clocks

3. inventory turns
- review label: inventory turns
- approved review metric: finance_finished_goods_inventory_turns
- intended decision: is finished-goods working capital moving in the right direction for the completed fiscal period?
- owner: finance / supply-chain finance
- timing: completed fiscal month, quarter, or year; numerator and denominator use the same period
- grain: financial value over time, not unit movement
- exclusions to state: obsolete/excess inventory, consignment stock, intercompany inventory, raw/WIP inventory, returns, write-downs, cost policy
- split decision: planning gets days of supply or SKU velocity; warehouse gets movement or capacity metrics; finance owns official turns

Business-review rule
- If owner, clock, grain, exclusions, and decision do not match across planning, warehouse, and finance, the deck shows named variants instead of one shared KPI label.

The resolution is not to average the versions or pick the dashboard backed by the most confident owner.

The resolution is to split the label and assign each variant to the audience and decision it serves. Planning keeps a named supply-availability or service metric for demand coverage. Warehouse operations owns warehouse_order_fill_rate for complete first-attempt fulfillment. Transportation and customer service together own customer_on_time_delivery for the promise-window question, with customer service holding the right to change promise-date policy. Finance owns finance_finished_goods_inventory_turns for finished-goods working capital across the completed fiscal period.

Once those names exist, the review can still show more than one number. The difference is that each number states which decision it supports and which owner can change the definition without a cross-team negotiation in the meeting.

This is also why I do not treat the problem as a self-service dashboard issue. A dashboard can only travel safely after the metric boundary is honest. Before a supply-chain number reaches the review, I apply the same caution I use before I label a dashboard self-service: write the allowed question, the intended audience, and the explicit not-for cases, then decide whether the single shared label still fits at all.

Tradeoffs

• Breaks when: one KPI label is forced to serve planning, warehouse, and finance decisions → Mitigation: split the metric into separately named definitions with the owner and intended decision on the card.
• Breaks when: the formula is written but the clock is not → Mitigation: define the timing source before review and block after-the-fact swaps between order date, ship date, delivery date, promise date, and fiscal period.
• Breaks when: partial shipments make the numerator look better for one audience and worse for another → Mitigation: choose order, order-line, unit, or shipment grain deliberately and keep partial-shipment handling visible.
• Breaks when: inventory turns are treated like a warehouse velocity metric in one slide and a finance working-capital metric in the next → Mitigation: reserve official turns for finance-owned value over a fiscal period, then create separate planning or warehouse operational metrics when needed.
• Breaks when: the boundary card turns into a governance ceremony for every low-risk operational number → Mitigation: reserve the full card for numbers that reach cross-functional reviews or executive summaries.

Close

Next step: For one supply-chain number already in a business review, write the boundary card before the next meeting: owner, clock, grain, exclusions, and the first decision it supports.

Named variants usually create calmer reviews than one overloaded KPI label carrying planning, warehouse, and finance decisions at once.