Enterprise procurement rarely suffers from a shortage of technology.
Most large organizations already have an ERP. Many have invested in an S2P platform, supplier portals, catalogs, analytics tools, or all of the above.
The harder problem is what happens around and between those systems.
A requisition may begin in SAP while supplier communication and commercial comparisons still happen over email. Coupa may already host the catalog, but inconsistent product data makes it difficult to search or trust. Supplier, catalog, inventory, and ERP information may exist in separate systems that teams manually reconcile. And years of procurement data may be available without being structured well enough to analyze.
That is the common thread across the six enterprise transformations below.
None starts with the assumption that the core ERP or procurement stack has to be replaced. Instead, each addresses a specific constraint around the existing environment: data quality, workflow governance, catalog control, supplier management, operational integration, or spend intelligence.
The result is six very different examples of what procurement transformation can look like when the objective is to make the existing ecosystem work better.
The six control points procurement leaders should examine
- Data foundation: Can you trust the supplier, item, catalog, and spend data your processes depend on?
- Requisition-to-PO governance: Are sourcing, comparison, approvals, and supplier interactions controlled between PR and PO?
- Supplier and buying controls: Does procurement validate what becomes available to buyers?
- Adoption after go-live: Does the new process remain used six months, two years, or five years later?
- Operational integration: Do catalogs, inventory, suppliers, and ERP systems work from connected information?
- Procurement intelligence: Can the data you already own expose savings, consolidation, and performance opportunities?
They are not necessarily six sequential stages. An organization can have several of these gaps at once.
But there is one dependency that consistently matters:
If the underlying procurement data cannot be trusted, every workflow, catalog, dashboard, and AI initiative built on top of it inherits the problem.
1. A global beverage company standardized 8,496 SKUs without replacing Coupa
Procurement catalog problems are often blamed on the buying interface.
But sometimes the interface is working exactly as intended. The information feeding it is not.
What this looked like for a global beverage company
The challenge
A leading beverage company already had more than 200 product catalogs in Coupa. The procurement platform was in place, but catalog data varied significantly across markets.
Product descriptions were inconsistent. Images and tags were incomplete. Taxonomy varied by geography. Manufacturer information was missing or unreliable.
The result was a catalog environment that was harder to search, maintain, and trust than it should have been.
The solution
Instead of replacing Coupa, the work focused on the underlying procurement data.
ewiz procure standardized and enriched 8,496 SKUs across 274 catalogs, enhanced product descriptions, tags, and images, and supported multilingual catalog enrichment in English and Spanish. The cleaned catalog data was then uploaded back into the company’s existing Coupa environment.
The outcome
- 100% indirect spend visibility across key suppliers
- 65%+ of SKUs mapped accurately to manufacturer data
- 22% of previously uncategorized spend identified
- More than 70% of SKUs simplified with clearer descriptions
The important lesson is not that the company needed another catalog.
It needed better information inside the catalog it already had.
That distinction matters because poor catalog data does not stay contained inside catalog management. It affects search, guided buying, supplier comparison, category reporting, analytics, and eventually AI.
Sometimes the highest-value procurement technology project is making the existing technology more trustworthy.
Read the full beverage catalog case study
Why this matters beyond catalogs
- Poor procurement data does not stay contained inside master data.
- It flows straight into every system built on top of it; catalogs, spend reports, supplier scorecards, and AI recommendations all inherit the same inconsistencies.
- An inconsistent supplier master weakens spend consolidation.
- Poor item descriptions reduce catalog searchability.
- Weak taxonomy affects category reporting. Duplicate SKUs fragment demand.
- AI cannot reliably classify, compare, or recommend when the underlying context is inconsistent.
That is why procurement transformation increasingly has to start by asking a less glamorous question:
What state is the data in before we ask another system to use it?
2. A chemical manufacturer cut PR-to-PO cycle time by 87% while keeping SAP S/4HANA
Having a digital requisition and a digital purchase order does not necessarily mean the process between them is digital.
What this looked like for a global chemical manufacturer
The challenge
At a chemical manufacturing enterprise, SAP managed the beginning and end of the transaction: the purchase requisition and the purchase order.
But once a PR was raised, much of the workflow moved outside SAP.
- Supplier inquiries were emailed.
- Quotations arrived in inboxes.
- Comparisons were built manually in Word or Excel.
- Approvals moved through email.
- Supplier onboarding depended on manual document collection and compliance checks.
The problem was not SAP itself. It was the unmanaged workflow around it.
The solution
ewiz procure was deployed as a modular procurement layer connected to the existing SAP S/4HANA environment.
Requisitions synchronized from SAP. RFx events were populated from PR data. Supplier technical and commercial responses were captured centrally. Comparison sheets were automated. Approvals moved through configurable workflows with a full audit trail. The PO then returned to SAP.
Supplier onboarding was digitized alongside the sourcing workflow, including GST and PAN verification, certificate management, expiry tracking, and compliance alerts.
The outcome
PR-to-PO processing fell from 141 minutes to 19 minutes per requisition—an 87% reduction. Supplier onboarding dropped from 79 hours to 3.6 hours per supplier (approx. 95% reduction in onboarding time)
The procurement team achieved:
- 2X team capacity without additional headcount
- 100% audit-ready trails
- Zero missed compliance notifications or expiry alerts
The value was not simply faster PO creation.
It was closing the governance gap between requisition and purchase order while allowing SAP to remain the system of record.
Read the full PR-to-PO case study
3. A Fortune 500 FMCG enterprise brought ~60% of global tail spend under a governed procurement catalog
Catalog digitization does not end when a storefront goes live.
The harder question is whether people continue using it—and whether the data, suppliers, controls, and support model remain current after launch.
What this looked like for a global FMCG enterprise
The challenge
A global consumer-goods enterprise had already attempted to digitize indirect procurement.
The initiative struggled with usability, limited demand aggregation, inconsistent catalogs, fragmented indirect-spend visibility, a large supplier base, weak product and supplier data standards, and quality-control gaps.
Users began returning to familiar off-system purchasing methods.
The problem underneath the adoption issue was not simply interface design. The catalog data and operating model were not strong enough to sustain governed buying.
The solution
The procurement catalog was rebuilt around a cleaner data foundation and an operating model designed for ongoing use.
More than 15,000 fragmented SKUs were consolidated into 3,000+ active, standardized products. The catalog worked alongside Coupa for purchase-order processing, Intertek for product-quality controls, multiple supplier systems, and marketplace infrastructure.
Supplier enablement and catalog maintenance continued after deployment rather than being treated as implementation tasks. More than 5,000 suppliers were onboarded, and 1,000 enterprise users were trained.
The outcome
Over seven years, the program managed $900M+ of indirect spend across 50+ countries and accounted for approximately 60% of the client’s global long-tail procurement spend.
The environment supported 5,000+ suppliers, 3,000+ active catalog products, 400+ purchase orders per month, and approximately 10,000 support conversations annually.
That scale highlights an often-overlooked part of procurement transformation:
Go-live is a technology milestone. Adoption is an operating model.
Catalogs need maintaining. Supplier information changes. Users need support. New countries and suppliers need onboarding. Governance has to continue.
The software may go live once. The procurement environment changes every day.
Read the full FMCG procurement catalog case study
4. A food & beverage manufacturer brought €100M in cabinet spend under procurement control
High-value equipment procurement creates a different challenge from everyday catalog purchasing.
Finding the product is only one part of the process. Procurement also needs confidence that specifications, pricing, commercial terms, and supplier information have been validated before the buyer can place an order.
What this looked like for a global food and beverages manufacturer
The challenge
For one food & beverage manufacturer, cabinet and refrigeration-equipment procurement covered 1,500+ SKUs, 40+ suppliers, more than €100M in spend, and 150,000+ orders.
Supplier specifications, commercial details, pricing, and customizations were being coordinated through a mixture of emails, offline files, procurement systems, and regional teams.
Procurement lacked a consistent approval gate before products reached buyers. Regional requirements, country-specific logistics, and tender-linked pricing added further complexity.
The solution
A role-based workflow separated supplier submission, procurement validation, and buyer ordering.
Suppliers submitted specifications, commercial information, pricing, and customizations through a structured intake process.
Procurement then validated specifications, checked pricing accuracy, confirmed alignment with awarded eTender terms or contracts, and reviewed commercial readiness.
Only after approval did the product become available to buyers.
eTendering was incorporated into the same operating model to structure supplier participation, commercial evaluation, and tender-linked pricing.
The outcome
- 100% of cabinets routed through procurement approval before buyer access
- 1,500+ equipment SKUs unified into a single source of truth
- ~40–50% reduction in manual supplier onboarding effort across 30+ suppliers
- €100M in equipment spend brought under improved pricing accuracy and compliance
- 150,000+ orders with end-to-end procurement visibility
The environment also provided end-to-end procurement visibility across 150,000+ cabinet orders.
This case demonstrates a different form of procurement control from the FMCG catalog example.
For technically complex and commercially significant products, the critical control point sits between supplier submission and buyer access.
A catalog alone does not create that control.
An approval gate does.
Read the full cabinet procurement case study
5. A merchandise leader standardized 28,000+ SKUs across 120+ portals and connected catalog, inventory, and ERP
A procurement catalog becomes much more valuable when it reflects what is actually happening operationally.
Product information, inventory, supplier data, warehouses, orders, and ERP records cannot remain separate versions of the truth indefinitely.
What this looked like for a global merchandise business
The challenge
A global branded-merchandise leader was operating across a large network of products, suppliers, clients, and markets.
Catalog, supplier, inventory, and warehouse information was distributed across ERP systems, supplier feeds, and individual portals. Teams relied on manual reconciliation to keep catalogs current, understand inventory, and process orders.
Buyers lacked consistent real-time inventory visibility, while warehouse mapping, quantity allocation, ordering, and reordering required manual intervention.
The solution
With ewiz procure, more than 28,000 SKUs were standardized across the catalog ecosystem.
Curated catalogs were connected directly with warehouse inventory. Supplier specifications, availability, and pricing were synchronized into the buying environment. ERP and FTP workflows supported live stock updates, while warehouse mapping, quantity allocation, stock triggers, and order processing became connected workflows.
Punchout integrations with Coupa, Ariba, Procurify, and Workday allowed the environment to work alongside the procurement technology already in place.
The outcome
The resulting ecosystem supports
- 120+ sourcing portals,
- 28,000+ standardized SKUs,
- 1.5 million+ transactions annually
It operates across 15+ countries, 15+ languages, and 10+ currencies, with real-time inventory visibility across buying portals and reduced reliance on manual reconciliation between catalog, ERP, supplier, and warehouse systems.
At this scale, catalog management is no longer simply a content-management problem.
It becomes part of the operating infrastructure connecting:
Demand → Catalog → Inventory → Supplier → Order → Fulfillment
Read the full merchandise catalog case study
6. A Fortune 100 enterprise turned €200M+ of fragmented indirect spend into analyzable procurement intelligence
This is the sixth case study that was not clearly identified in the previous draft.
Not every procurement opportunity requires a new sourcing event.
Sometimes the opportunity is already contained in historical spend data—but hidden by inconsistent supplier records, free-text descriptions, missing fields, multiple languages, and incompatible source systems.
What this looked like for a fortune 100 enterprise
The challenge
A Fortune 100 enterprise had three years of POSM procurement data covering 200,000+ procurement records and more than €200M in spend.
The information was spread across more than four source systems and multiple formats, currencies, and markets.
Records contained 7+ languages, corrupted encoding, large volumes of free text, 1,441 fragmented vendor codes, and 33,140 records with blank PO dates.
The business had the data. It did not yet have a dependable basis for analyzing it.
The solution
A three-stage data-cleansing process standardized the information, classified the spend, and consolidated fragmented supplier records.
The implemented pipeline brought together 100K+ line items and produced 90,909 clean, classified, and deduplicated transactions across seven markets.
Transactions were structured into four categories and 144 subcategories. Nine attributes were extracted from free-text information, while fragmented supplier codes were mapped into master entities.
The outcome
The resulting dataset achieved
- 99% classification accuracy
- Reduced manual analyst effort by 90%
- Cut time to insight from more than six weeks to five days
More importantly, clean data changed what procurement could see.
The analysis identified a €40M vendor-consolidation opportunity, including supplier spend fragmented across multiple codes and countries. It also separated €30M+ of one-off campaign spend that had been obscuring underlying patterns.
Those numbers should not be confused with realized savings.
They represent something procurement needs before a savings initiative can be credibly pursued: a defensible view of the opportunity.
A savings strategy is only as reliable as the spend baseline underneath it.
Read the full indirect spend data cleansing case study
What these six procurement transformations have in common
The six cases address very different problems: catalog data quality, PR-to-PO workflow, long-tail procurement, equipment governance, operational integration, and spend intelligence.
But several patterns repeat.
The existing enterprise stack did not automatically need replacing. Coupa remained part of the beverage and FMCG environments. SAP remained the system of record for the chemical manufacturer. The merchandise deployment connected with existing ERP and procurement systems. The data-cleansing program worked with records already distributed across multiple source systems.
The interventions instead focused on the gaps around those systems.
- Data had to become reliable enough to use.
- Workflows had to capture decisions rather than leave them in email.
- Suppliers, pricing, and products needed governance before reaching buyers.
- Catalogs had to remain connected to inventory and operational information.
- And procurement data had to become consistent enough to support analysis.
That leads to a useful way of thinking about procurement transformation:
Fix what procurement knows. Govern what procurement does. Learn from what procurement produces. Keep it working after go-live.
What do these cases mean for procurement AI?
Procurement leaders are increasingly being asked where AI should be deployed.
- Supplier evaluation?
- Sourcing?
- Contract review?
- Spend classification?
- Predictive analytics?
- Intelligent intake?
All of those are legitimate use cases.
But they share one dependency.
The AI must understand the data it is being asked to reason across.
If a supplier appears under several names, product descriptions differ by country, categories are inconsistent, units of measure vary, or historical records are incomplete, automation simply encounters the same ambiguity procurement analysts already face.
The procurement data challenge can become particularly difficult in global environments:
- Multiple languages
- Inconsistent supplier names
- Free-text item descriptions
- Incomplete taxonomy
- Duplicate SKUs
- Different category structures
- Fragmented ERP and S2P systems
The ewiz procure procurement-data methodology, for example, explicitly addresses multilingual normalization, structured-field extraction, taxonomy mapping, supplier deduplication, content enrichment, and ongoing data governance before downstream analytics depend on the information.
The strategic implication extends beyond any one solution:
AI maturity cannot sustainably outrun procurement data maturity.
That changes the question procurement leaders should ask.
Instead of only asking:
“Where can we deploy AI?”
It may be more useful to ask:
“Which procurement decisions now have data trustworthy enough for AI to support?
What this procurement transformations had in common
The companies and use cases are different, but the operating pattern is remarkably consistent.
- First, the existing enterprise stack was not automatically replaced. SAP remained central to the chemical manufacturer’s environment. Coupa remained part of the beverage and FMCG ecosystems. Other enterprise platforms, supplier systems, inventory sources, and ERPs continued to perform their core roles.
- Second, data quality was treated as an operational dependency rather than a cleanup exercise. SKUs, suppliers, catalogs, taxonomy, and transaction data had to become reliable before workflows and analytics could deliver their intended value.
- Third, clean data was activated. It powered sourcing, supplier onboarding, catalog buying, approvals, inventory workflows, and compliance controls.
- Fourth, governed activity created better intelligence. Once the underlying records became structured and comparable, procurement could identify consolidation opportunities, measure adoption, monitor suppliers, and build more credible savings baselines.
- Finally, the operating model continued after launch. Supplier enablement, catalog maintenance, data governance, user support, reporting, and adoption were treated as recurring disciplines rather than implementation tasks.
That sequence captures the procurement model ewiz procure has been built around:
Data Foundation → Procurement Activation → Procurement Intelligence — sustained through expert-led Managed Services.
Or, more simply:
Most procurement technology assumes the data is clean. Fixing it first changes what everything downstream can deliver.
Six questions procurement leaders can ask today
A transformation program is not required to identify where control is breaking.
Start with six practical questions.
1. Can finance and procurement agree on supplier spend without manually reconciling systems?
If the CFO asked tomorrow for total spend with the company’s 20 largest suppliers, would the ERP, S2P platform, local systems, and supplier master produce the same answer?
2. Can you reconstruct how a supplier was selected?
For a recent sourcing decision, can the team show who was invited, what was submitted, how the comparison was made, who approved it, and why the supplier was selected?
3. How much addressable spend actually flows through approved buying channels?
And is that percentage increasing or declining?
4. What does it take to keep the procurement environment operating?
How much buyer time is still spent chasing supplier information, fixing catalogs, answering user questions, reconciling data, or resolving exceptions?
5. Do procurement and operational systems describe the same reality?
Can users trust that product information, supplier details, pricing, inventory, and ERP records are consistent?
6. Which procurement decisions are genuinely AI-ready?
Which decisions could AI support today without someone first having to clean, reconcile, or reinterpret the underlying data?
The objective is not to create another maturity score.
It is to identify where unreliable data, fragmented execution, or weak governance is constraining the next measurable outcome.
What should procurement leaders take from these case studies?
Procurement transformation is often framed as a platform decision.
These six cases suggest a broader view.
The company may already have SAP.
It may already have Coupa.
It may already have catalogs, supplier systems, warehouses, analytics, and years of historical spend data.
The bigger question is whether those investments are connected by data and processes that procurement can trust.
- Can the organization rely on the information underneath the systems?
- Can it govern the activity moving between them?
- Can it sustain adoption after launch?
- Can it turn historical procurement activity into better decisions?
That is why replacing the core technology stack is not always the starting point.
Sometimes the bigger opportunity is making the stack already in place work as one procurement operating model.
About ewiz procure
ewiz procure works with enterprise procurement teams across procurement data, sourcing, catalogs, supplier management, analytics, and ongoing procurement operations. The case studies above are drawn from ewiz procure enterprise deployments.
Want to discuss for your domain?
