How is the supply chain data maturity score calculated?

Each of the eight questions scores 0 to 12 points, and the sum is converted to a score out of 100. The score maps to a tier: Emerging (0–25), Developing (26–50), Maturing (51–75), or Leading (76–100).

Is this assessment an audit or certification?

No. It is an indicative estimate built only from your eight responses, meant to start an internal conversation about data readiness, not to certify your practices.

Are my answers uploaded anywhere?

No. The assessment runs entirely in your browser and nothing is uploaded.

Which area should we improve first?

Start with the lowest-scoring area that blocks the most work. Product and inventory data usually come first, because orders, shipments, and planning depend on them.

Supply chain data maturity assessment

Supply chain data maturity describes how consistently product, inventory, vendor, order, and shipment data is governed, shared, and trusted across systems and sites.

Answer eight questions on product, inventory, vendor, order and shipment data for a maturity score out of 100 and a breakdown. Runs in your browser.

Browser-sideNo accountCopy, download, or print

Last reviewed 30 Oct 2026

Your inputs are saved as a draft in this browser only. Nothing is uploaded.

Jump to result

Interactive workspace

Inputs

Organization or plant group

Plants or operating sites

Product master governance

Inventory visibility

Vendor master consistency

Order traceability

Shipment data sharing

ERP integration architecture

Data quality management

New application readiness

Result

Maturity score38 / 100

Maturity tierDeveloping (26–50)

Raw score36 / 96

OrganisationNorth manufacturing network

Sites assessed6

Foundational master data exists but reconciliation and manual exports still slow decisions. A governed canonical layer would reduce integration debt.

Indicative maturity estimate from the eight responses provided; not an audit or certification.

Dimension scores

Dimension	Score	Of 12
Product master governance	4	12
Inventory visibility	4	12
Vendor master consistency	8	12
Order traceability	4	12
Shipment data sharing	4	12
ERP integration architecture	4	12
Data quality management	4	12
New application readiness	4	12

Supply chain data maturity
Maturity score: 38 / 100
Maturity tier: Developing (26–50)
Raw score: 36 / 96
Organisation: North manufacturing network
Sites assessed: 6

Foundational master data exists but reconciliation and manual exports still slow decisions. A governed canonical layer would reduce integration debt.
Indicative maturity estimate from the eight responses provided; not an audit or certification.

Supply chain data maturity
Maturity score: 38 / 100
Maturity tier: Developing (26–50)
Raw score: 36 / 96
Organisation: North manufacturing network
Sites assessed: 6

Foundational master data exists but reconciliation and manual exports still slow decisions. A governed canonical layer would reduce integration debt.
Indicative maturity estimate from the eight responses provided; not an audit or certification.

How to use it

Enter your organization or plant group and the number of operating sites.
Answer the eight questions, from product master governance to new application readiness, picking the option closest to how you work today.
Review the maturity score, tier, and per-dimension breakdown.
Copy, download, or print the result to share with your team.

Questions

How is the supply chain data maturity score calculated?: Each of the eight questions scores 0 to 12 points, and the sum is converted to a score out of 100. The score maps to a tier: Emerging (0–25), Developing (26–50), Maturing (51–75), or Leading (76–100).
Is this assessment an audit or certification?: No. It is an indicative estimate built only from your eight responses, meant to start an internal conversation about data readiness, not to certify your practices.
Are my answers uploaded anywhere?: No. The assessment runs entirely in your browser and nothing is uploaded.
Which area should we improve first?: Start with the lowest-scoring area that blocks the most work. Product and inventory data usually come first, because orders, shipments, and planning depend on them.