Blog · Board and management reporting · Supply chain
SCOR metrics organize supply chain performance into an agreed measurement framework. Learn how to map business exports, calculate perfect orders and check the resulting scorecard.
SCOR metrics help supply chain teams connect business results to a consistent performance framework. The useful output is a scorecard whose measures have agreed definitions, traceable source rows and owners who can investigate a gap. Mapping a familiar KPI name to SCOR is only the start; its population and calculation must match too.
ASCM's SCOR performance introduction organizes performance into three categories and eight attributes. It also describes a hierarchy in which level-2 and level-3 metrics help diagnose higher-level results.
| Category | Performance attributes | Business question to resolve |
|---|---|---|
| Resilience | Reliability, Responsiveness, Agility | Can the chain meet commitments and respond to disruption? |
| Economic | Cost, Profit, Assets | What resources and financial results accompany that service? |
| Sustainability | Environmental, Social | What environmental and social outcomes are being measured? |
An attribute is a direction, not a number. Reliability, for example, needs a specific measure and calculation before it can appear as an actual result. Avoid treating an unqualified label such as "service" as though it has an agreed denominator.
The framework also connects measurement to operating processes. ASCM's SCOR Digital Standard overview describes processes including Order, Source, Transform and Fulfill. That helps locate the owner of a gap without assuming that every poor customer result began in the warehouse.
Select your strategic questions before selecting measures. The guide to aligning supply chain metrics with strategy covers that choice; this page concentrates on mapping and proving the measurements.
Use a row per selected metric. Record the official reference, your business scope, the grain of the export, exclusions, unit, calculation and owner. Keep a dated copy of the definition used for each reporting period.
These mappings illustrate where common files can contribute. They do not mean every export already contains the evidence needed for the full measure.
| Business file | Candidate SCOR mapping | Evidence to check before calculating |
|---|---|---|
| Customer order register with delivery evidence | RL.1.1 Perfect Customer Order Fulfillment | Product and quantity, delivery commitment, documents and condition across every order line |
| Purchase orders and supplier receipt records | RL.1.2 Perfect Supplier Order Fulfillment | Agreed supplier commitments and complete supporting receipt evidence |
| Inventory valuation and consumption records | AM.2.2 Inventory Days of Supply | The required valuation basis, averaging method, consumption basis and period |
Inventory days is an Assets diagnostic; it is not the complete cash-to-cash measure. Similarly, a supplier receipt date alone cannot prove a perfect supplier order. Document partial coverage as a local diagnostic until the full definition can be supported.
For other operating measures and their source exports, use the supply chain KPI guide. Keep its general KPI list separate from the question of whether a particular SCOR definition has been met.
Take an illustrative Illinois distributor reviewing completed customer orders in a closed reporting period. Each order below contains a single order line, and the customer, place and agreed delivery timing are combined into the delivery commitment test. All required evidence is available.
ASCM's detailed RL.1.1 definition requires every component to pass, and every line in an order to be perfect, for that order to count as perfect. Its detailed page currently labels the metric "Perfect Customer Order Fulfillment."
Perfect order fulfillment = Perfect orders / Eligible orders × 100
Use a value of 1 for a component that passes and 0 for one that fails. The last column is 1 only when all component columns are 1.
| Order | Product and quantity | Delivery commitment | Documentation | Condition | Perfect order |
|---|---|---|---|---|---|
| IL-101 | 1 | 1 | 1 | 1 | 1 |
| IL-102 | 1 | 0 | 1 | 1 | 0 |
| IL-103 | 1 | 1 | 0 | 1 | 0 |
| IL-104 | 1 | 1 | 1 | 1 | 1 |
| IL-105 | 0 | 1 | 1 | 1 | 0 |
| IL-106 | 1 | 1 | 1 | 0 | 0 |
| Passed | 5 | 5 | 5 | 5 | 2 |
Perfect order fulfillment is 2 / 6 × 100 = 33.3%, rounded to one decimal. Each individual component passes on 5 / 6 × 100 = 83.3% of orders. Those component percentages cannot be averaged to obtain the perfect order rate: different orders fail different tests.
If the component flags occupy columns B through E, the row formula is:
=IF(COUNT(B2:E2)<>4,"Missing evidence",IF(MIN(B2:E2)=1,1,0))
Validate the input flags so only 0, 1 or a blank is allowed. A blank remains an evidence exception; it must not silently become a pass. Reconcile and resolve those exceptions before publishing the full-population result.
For orders containing multiple lines, perform the tests at line level and then require every eligible line to pass. Count the order identifier once in the denominator. Otherwise, a large order gains extra weight simply because it has more lines.
The population check is 2 perfect orders + 4 imperfect orders = 6 eligible orders. Tie those order identifiers to the closed-period order population after documenting approved exclusions. Investigate duplicates before combining delivery and documentation files.
The diagnostic check is also visible: each component has a single failure, and those failures belong to separate orders. That explains how fairly strong component results coexist with a much lower combined result.
Suppose the evidence owner establishes that IL-103's documents were accurate, complete and on time, correcting a reporting error. Its documentation flag changes to 1. Perfect orders become 3, so the corrected rate is 3 / 6 × 100 = 50.0%, an increase of 16.7 percentage points after rounding. Preserve the correction reason and period. Fixing documents late would not justify rewriting a failure of the original timing requirement.
The operating discussion now has a clear shape. Customer service owns the commitment exception, the documentation owner investigates the reporting error, inventory operations investigates the quantity exception and quality investigates the condition failure.
Bring your order register, receipt or inventory export and agreed metric definitions to Covirage. Covirage maps the columns; its tools compute and check the supported figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, set up your business and bring a sample of your own data.
See Covirage for supply chain teams for the supporting operating context.
Attributes group measures around a strategic characteristic such as reliability or responsiveness. The attribute provides direction; a defined metric provides the measurable result. Use the current ASCM framework and record which definitions your scorecard follows so comparisons use the same basis.
Level-1 metrics describe strategic supply chain outcomes. Level-2 metrics help diagnose the performance behind those outcomes, while level-3 measures provide further detail. The relationship supports investigation; a lower-level measure should not simply be relabeled as the strategic metric.
On-time delivery tests the agreed delivery commitment. Perfect order fulfillment also considers whether products and quantities, documentation and condition meet the relevant requirements. An order can arrive on time and still fail the perfect order test because another component failed.
A spreadsheet can hold the definitions, source records and calculations for selected measures. Its usefulness depends on consistent order identifiers, appropriate evidence and agreed exclusions. Keep missing evidence visible and reconcile the measured population before using the result to assess performance.