A Leading Chemicals Manufacturer Transforms Procurement Decisions
About the company
A diversified chemicals manufacturer buying raw materials, packaging and engineering goods across several business units. Requisitions and sourcing run in Oracle, and supplier ratings are reviewed annually.
- Industry
- Chemicals
- Scale
- Raw materials, packaging and engineering goods across several business units
- Scope
- Supplier data, spend reporting, contract rates and award evidence
At a glance
Before Proconomy
- Vendor records were mixed
- Reporting started with cleanup
- Supplier evidence sat apart
- Contract rates had to be hunted
- Shipment data arrived incomplete
After Proconomy
- Supplier reporting means something
- Analysis stops being preparation
- Recent quality reaches the award
- Routine orders stop waiting
- Receiving stops chasing
Key products
- Spend intelligence
- Supplier management
- Contract lifecycle management
- Supplier portal
The challenge
Requisitions and sourcing happened in Oracle, but the information people needed to decide did not. Analysts cleaned vendor and spend data in separate files, and buyers looked up contract rates and supplier performance one at a time before an award, adding manual work to every decision.
Employee and non-commercial codes sat in the same vendor master as real suppliers, so every analysis started by excluding them.
Vendor records were mixed
Employee and non-commercial codes sat alongside real suppliers and blurred every analysis.
Reporting started with cleanup
Category views depended on corrected master files and fresh extracts each time.
Supplier evidence sat apart
Ratings and recent quality issues lived outside the quote review that needed them.
Contract rates had to be hunted
Buyers searched for annual rates before releasing routine purchase orders.
Shipment data arrived incomplete
Optional fields left receiving teams to fill the gaps afterwards.
What the manufacturer actually asked for
Five things, all of them about what a buyer can see at the moment of deciding.
- Vendor records classified so commercial reporting means something.
- Spend views by category and business unit without manual preparation.
- Delivery and quality evidence present during quote review.
- Active contract rates visible beside the approved request.
- Shipment and invoice detail complete before a supplier submits.
What we built
Vendor data rules, spend dashboards on the cleaned data, Supplier 360 inside quote review, contract rates at the point of release, and required supplier forms.
Vendor data rules
Records are classified and location fields reconciled so reporting draws on commercial suppliers only.
Spend dashboards on clean data
Cleaned spend is viewable by category and business unit without a preparation step.
Supplier 360 in quote review
Delivery and quality evidence is present while the quotes are being compared.
Contract-linked buying
Active rates and terms appear beside the approved request, at the point of release.
Required supplier portal forms
Shipment and invoice details must be complete before a supplier can submit.
The result
What changed once it was running.
Supplier reporting means something
Commercial reports exclude the records that were never suppliers in the first place.
Analysis stops being preparation
Teams make far fewer manual fixes before they can look at a category.
Recent quality reaches the award
Buyers weigh how a supplier has actually performed alongside what they have quoted.
Routine orders stop waiting
Buyers confirm valid terms without the search that preceded every release.
Receiving stops chasing
Complete supplier detail reduces the follow-up that landed at the stores.
See this running on your own numbers — fifteen minutes, no slides.
Request a workflow demonstrationThis will sound familiar. If any of these are you.
- Your vendor master contains records that were never suppliers.
- Every category analysis begins by correcting a master file.
- Supplier ratings are reviewed annually and not consulted at the award.
- Buyers search for the contract rate before releasing a routine order.
Where this connects
The questions we get asked.
No. Oracle keeps requisitions, sourcing and approvals. What was added is the data and evidence layer around the decision, which is where the manual work was.
It classifies records so reporting is correct, which is the part that was blocking analysis. Correcting the master in Oracle is a separate clean-up, and we will say so rather than let a tidy view imply tidy data.
As recent as what is recorded against the supplier. If quality issues are logged when they happen, they are present at the next review; if they are logged quarterly, that is what you see. The platform does not improve the input.
Then the form is wrong for that category, and it is configurable. Making a field mandatory that a supplier genuinely cannot answer moves the problem rather than solving it.
The same problem, at your scale
Every group that runs more than one operating company arrives at the same place: policy that exists on paper, applied differently in every plant, evidenced by whoever happens to remember. Bring us the workflow where that costs you the most, and we will run it against your rules.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.