What it measures
% of delivery lines with complete order quantities
This KPI measures the outcome of the entire order fulfillment process after the delivery has been made; the financial consequence of any failure, such as a retailer deduction, is already locked in.
Business impact
- Triggers a 'chaos tax' of customer service overtime to manage complaints, manual order tracking by logistics planners, and emergency stock transfers between distribution centres.
- Directly causes shelf gaps at the retailer, resulting in lost sales that are rarely recovered. Each short-shipment erodes the working capital invested in getting the product to the dock.
Formula
(Complete delivery lines / Total delivery lines) x 100Grain
One row per outbound delivery line — customer × product × date
Inside the Implementation Pack
A preview of what's actually built for this KPI — extracted from the real Implementation Pack, not a mockup.
This is the primary ratio the pack's other measures build on — trend, rank, and period-comparison variants, all on Fact_Outbound_Delivery_Line. It guards against missing dates and values with NOT ISBLANK checks.
Fact_Outbound_Delivery_Line— 9 mandatory columns — customer key, qty delivered, ...Dim_Carrier— key + nameDim_Customer— key + nameDim_Plant— key + nameDim_Product— key + nameDim_Route— key + nameDim_Warehouse— key + nameDim_Date— Auto-generated calendar table — no customer data required
Full field-by-field data contract, in 4 SQL dialects (SQL Server, Snowflake, Databricks, BigQuery), ships in the pack.
| Target | 0.99 — performance considered compliant at or above this line |
| Warning | 0.96 — amber alert — triggers a review |
Both live in one Excel tab — change them, refresh the report, done. No DAX editing needed.
Everything you need to build In-Full Delivery Rate in Power BI — dimensional model, DAX measures, SQL views, and a food-industry demo dataset.