Hub for Intelligent Purchasing

Every spend analysis starts with a caveat about the uncategorised bucket. Purchase orders arrive with descriptions written by whoever raised them, the product hierarchy was last curated two reorganisations ago, and a material sits under three category codes depending on which plant bought it. So category-level spend is directionally true and operationally useless: a negotiation team cannot tell a supplier what they actually buy, and a cost programme cannot tell whether a category moved or the coding did.

• A large share of purchase orders sits uncategorised, and every analysis is qualified because of it.
• The product hierarchy drifts out of date faster than it can be manually curated.
• The same material is coded differently across sites, so vendor exposure is understated.
• Category change scenarios cannot be evaluated because the baseline is not trusted.

Hub gives procurement a granular and current picture of what the organisation actually buys. Historical purchases are harmonised against a real-time canonical product hierarchy, so category spend reflects the materials underneath it rather than the codes attached to it. Category analysis then shows how spend is evolving against those underlying materials and against current vendor exposure, which is the view a negotiation or consolidation decision needs. What-if scenarios can be run on that base — concentrating on a subset of vendors, for instance — with the risks of the alternative surfaced alongside the opportunity. The uncategorised bucket is attacked directly: generated recommendations propose a match to an existing category or a justified addition to the hierarchy, which a category manager accepts or rejects.

Categorisation is the whole problem, and it is a language problem. A purchase order line is a short, abbreviated, human-written string; deciding which category it belongs to means understanding what the thing is, not matching a token. That is why rule sets stall at partial coverage and why the uncategorised bucket never empties. A model closes it, but the hierarchy is a governed asset — so recommendations are proposals, and a category manager remains the authority on what the taxonomy says.

HARMONISATION

Historical purchases against a real-time canonical hierarchy

ANALYSIS

Category evolution by underlying material and vendor exposure

SCENARIOS

What-if evaluation, with risks surfaced alongside opportunity

CATEGORISATION

Recommendations for uncategorised POs, accepted or rejected by a manager

AUTONOMY

Proposes taxonomy changes; the hierarchy stays governed

1. 01Historical purchasing harmonised against a canonical product hierarchy that stays current.
2. 02Spend category evolution analysed against underlying materials rather than coded labels.
3. 03Current vendor exposure visible per category, so consolidation decisions have a baseline.
4. 04What-if scenarios evaluated for change opportunities and for the risk they introduce.
5. 05Uncategorised purchase orders matched to existing categories by generated recommendation.
6. 06New hierarchy additions proposed with justification, for category-manager approval.

Material level

Category resolution, against coded labelsdesign intent

Governed

Hierarchy changes, proposed not applieddesign intent

• DUE DILIGENCE RESPONSEHub Response for RFPs & DDQs→
• RELATIONSHIP BANKINGHub for Real-time Customer Intelligence in Banking→
• DEAL SOURCINGHub for Investment Screening & Due Diligence→