SCOR Model: The Supply Chain Operations Reference Framework

By Linh Ngo · Updated Oct 12, 2026

The SCOR model (Supply Chain Operations Reference) is a standard framework for describing, measuring, and improving supply chain processes. Classic versions organize the work into Plan, Source, Make, Deliver, Return, and Enable. The current SCOR Digital Standard from ASCM reworks that into seven processes: Orchestrate, Plan, Order, Source, Transform, Fulfill, and Return.

What is the SCOR model?

SCOR is a process reference model. That means it doesn't tell you how to run your supply chain. It gives you a common language and a set of building blocks so you can describe what you do, measure it the same way as everyone else, and spot where it's weak.

ASCM's own description is that SCOR was established in 1996 and has been updated regularly since. The model is now maintained by ASCM, which came out of the 2014 merger of the Supply Chain Council and APICS. If you read older books or consulting decks, they were written for the Supply Chain Council era, which is why you'll see two different process lists floating around.

The framework ties together four things in one structure: processes, performance metrics, practices, and the skills people need. ASCM calls these the four major sections of the model: Performance, Processes, Practices, and People.

One boundary matters before you start. SCOR describes processes, not functions or job titles. It also doesn't try to cover everything a company does. ASCM states that SCOR does not address sales and marketing (including demand generation), product development, or research and development. If you need a whole-enterprise view, you'll pair it with something broader, such as business process management.

Classic SCOR vs. the SCOR Digital Standard

This is the part most articles get wrong, because the model changed. Here is the short version.

Classic SCOR (through version 12) is built on six management processes:

• Plan: balance demand and supply and set the plan for the other processes.
• Source: procure goods and services.
• Make: produce or assemble the product.
• Deliver: take and fulfill customer orders, including transport and distribution.
• Return: handle returned product, both from suppliers and to suppliers.
• Enable: manage the rules, data, performance reporting, and other supports that keep the other processes running.

The SCOR Digital Standard (SCOR DS) is the current version, and ASCM describes it as organized around seven primary management processes: Orchestrate, Plan, Order, Source, Transform, Fulfill, and Return. ASCM's version 14 release notes list the main changes:

• The model is no longer linear, and Orchestrate was added to link supply chain strategy to Plan and the other processes.
• Deliver was separated into Order and Fulfill, to better represent omni-channel selling, transportation, and warehouse management.
• Make was expanded into Transform, and Return was updated to include services.
• Source was overhauled, and formal warehouse and transportation planning was added.
• Sustainability (circularity) practices, metrics, skills, and competencies were added to every process.

ASCM's crosswalk document maps the new processes back to version 12 for teams migrating, and it's the best place to start if your company has older SCOR documentation.

If you're starting fresh, use SCOR DS. If your team already has maps and metrics built on the six-process version, you don't have to throw them away. Most of the logic carries over, and the crosswalk shows where each piece lands.

The seven SCOR DS processes

Here is what each process covers, using ASCM's descriptions on the SCOR DS page.

ASCM's diagram shows these as a double infinity loop: supply and demand balance in a horizontal loop, while synchronizing and regenerating sit in a vertical one. The point is that the processes run at the same time and feed each other. That's a real shift from the old picture of a chain that moves left to right.

Performance attributes and metrics

SCOR doesn't leave "improvement" vague. Every metric belongs to a performance attribute, and ASCM's introduction lists eight attributes in three categories:

Each attribute has at least one Level 1 (strategic) metric. A few examples from the standard: Perfect Order Fulfillment (RL.1.1) for Reliability, Order Fulfillment Cycle Time (RS.1.1) for Responsiveness, Total Supply Chain Management Costs (CO.1.1), and Cash-to-Cash Cycle Time (AM.1.1) for Assets. The metric codes tell you the attribute and the level.

Metrics work as a diagnostic tree. In ASCM's words, Level 2 metrics explain gaps in Level 1 metrics, and Level 3 metrics explain Level 2. So if perfect order fulfillment drops, you drill down to find which sub-measure moved. If you're building out your own measures, the article on process KPIs covers how to pick them.

Key Facts

• SCOR was established in 1996 and is now maintained by ASCM, which formed from the 2014 merger of the Supply Chain Council and APICS (ASCM).
• The current SCOR Digital Standard is organized around seven processes: Orchestrate, Plan, Order, Source, Transform, Fulfill, and Return (ASCM).
• The model has four sections: Performance, Processes, Practices, and People (ASCM).
• SCOR defines eight performance attributes in three categories: Resilience, Economic, and Sustainability (ASCM).
• ASCM focuses its process levels on Level 0 to Level 3, which are industry neutral. Organizations extend the model to Level 4 with their own practices (ASCM).
• SCOR DS is open access under a Creative Commons license, and registering for the required ASCM account is free (ASCM, introduction).

The process levels

SCOR is hierarchical, and knowing the levels keeps you from modeling too much or too little. In the DS version, according to ASCM's quick reference guide:

• Level 0: Orchestrate, the activities that connect the supply chain to suppliers, customers, and internal stakeholders.
• Level 1: the six core processes: Plan, Order, Source, Transform, Fulfill, Return.
• Level 2: the major process categories within each of those.
• Level 3: process elements, the individual activities that your business systems have to support.

The model focuses on Levels 0 to 3. Beyond that, you're on your own: Level 4 is where you describe your industry-specific, company-specific, and site-specific way of working. That's where tools such as business process mapping and value stream mapping pick up.

SCOR vs. other process frameworks

SCOR is often compared with other frameworks, but they answer different questions.

They combine well. A common pattern is to use SCOR to pick the processes worth fixing, value stream mapping to see waste inside them, lean methodology to remove it, and the theory of constraints to check you're attacking the real limit. Lean techniques such as just-in-time and pull systems live below SCOR's Level 3, in the practices you adopt.

How to apply SCOR step by step

The sequence below is a practical way to use the model. It isn't an official ASCM stage list.

1. Define scope and strategy. Pick the supply chain you're examining: a product family, a region, or a customer segment. Write down what the business wants from it, such as faster delivery or lower cost.
2. Choose your attributes. From the eight, pick the two or three that matter most to your strategy. Trying to improve all eight at once is how projects stall.
3. Map the processes at Level 1 and 2. Draw how Plan, Order, Source, Transform, Fulfill, and Return run today, plus who owns each. Add Orchestrate: who sets the rules, owns the data, and reviews performance?
4. Measure with Level 1 metrics. Pull current numbers for the attributes you chose. Where possible, compare against a benchmark. ASCM also runs a benchmark evaluation for its top corporate membership levels.
5. Diagnose with Level 2 and 3 metrics. Walk down the metric tree from the weak Level 1 number until you find the sub-process causing the gap.
6. Prioritize improvements. Rank gaps by effect on your chosen attributes and by effort. Pick a few.
7. Redesign at Level 3 and 4. Define the activities, systems, and practices needed. This is where you bring in Lean, Six Sigma, or whatever method suits.
8. Implement and track. Assign owners and dates. Re-measure on a regular cycle, and compare against the baseline. A process maturity check helps decide when a process is stable enough to stop fixing it.

SCOR assessment template

Copy this table to run the diagnosis.

SCOR examples by business function

These are illustrative scenarios, not case studies. They show how different functions use the same structure.

Do's and don'ts

Do:

• Start with the business strategy, then choose the attributes that support it.
• Use SCOR DS vocabulary for new work, and use the crosswalk to bridge older documentation.
• Work down the metric hierarchy before you decide on a fix.
• Keep processes separate from departments. The model describes activity, not org charts.
• Involve suppliers and customers where you can, since SCOR was built for multi-party supply chains.

Don't:

• Mix classic and DS terms in one document without saying which you mean.
• Treat it as a mandatory standard. SCOR isn't a certification.
• Expect it to cover sales, marketing, or product development.
• Chase all eight attributes at once.
• Stop at Level 3. The model expects you to extend it to your own Level 4.

Conclusion

SCOR gives supply chain work a shared map. The older six-process version is still common in training material, but the current standard reflects how supply chains actually behave now: looped, connected, and sustainability-minded. Pick the attributes that match your strategy, measure at Level 1, diagnose down the tree, and let your own practices fill in Level 4. Start with the current ASCM documentation so your terms match what the standard says today.

Related reading

• Business process management
• Value stream mapping
• Process KPIs
• Lean methodology
• Theory of constraints
• APQC Process Classification Framework