What it measures
% of outbound order lines meeting all service requirements
Business impact
- Increased 'chaos tax' from service recovery actions: premium freight to meet closing delivery windows, customer service overtime to manage complaints, and unplanned warehouse labor to re-work rejected loads.
Formula
(Order lines meeting all criteria / Total order lines) x 100Grain
One row per outbound delivery line — customer x product x requested delivery 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— 11 mandatory columns — qty delivered, carrier key, ...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.98 — performance considered compliant at or above this line |
| Warning | 0.94 — 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 Outbound Service Level in Power BI — dimensional model, DAX measures, SQL views, and a food-industry demo dataset.