Scoring vendors without the black box

A vendor score is only as honest as its clock. Scored against first promises, May’s three main vendors separate clearly, and the twelve blocked invoices behind one of them stop hiding inside a weighted average.

RuleScore vendors from the landed documents: deliveries against first promise, blocks against invoices, and publish the arithmetic so purchasing argues inputs, not weightings.

Nevermeasure on-time against the last confirmed date. Every reschedule the vendor requests resets the clock, and chronic lateness grades itself out of the metric.

A vendor score is only as honest as its clock. The first promise is the one the vendor cannot renegotiate afterwards.

◆ May scores, computeddeliveries, punctuality, blocks.

Vendor	Receipts	On first promise	On-time %	Blocked invoices
Vendor A	52	48	92.3	3
Vendor B	38	31	81.6	12
Vendor C, intercompany	29	27	93.1	2
Smaller vendors	23			1

Receipt counts are the vendor cut’s own rows, and the block column partitions the eighteen blocked invoices by who caused them. Vendor B’s twelve blocks against 38 deliveries is the finding the summary score would have smoothed away. Sample values are illustrative, never client data.

◆ The metric that forgives latenessthe reschedule loophole.

In common configurations, delivery punctuality is measured against the latest confirmed date, and practitioners report vendors managing the metric by reconfirming: ask to slip, get a new date, arrive on time. Scoring against the first promise closes the loophole and changes several rankings overnight.

◆ The black box retiredweights argued once, in the open.

The delivered evaluation blends criteria through configured weightings most buyers cannot see, so every review meeting relitigates the formula. Published arithmetic over landed documents moves the argument to the inputs, where it belongs.

Use case

Problem

Vendor scores come from a weighted black box, reschedules erase lateness, and the vendor causing a third of invoice blocks still scores well.

What we build

Scores computed in the open from landed receipts and blocks, on-time against first promise, every number traceable to its documents.

What you get

Vendor reviews with teeth: punctuality that cannot be renegotiated, quality joined from the invoice side, and rankings purchasing actually believes.

Would your vendor rankings survive a first-promise clock?

We rebuild the score from the documents and find out.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
MM: Materials Management, the purchasing and inventory module.
ME65: The delivered vendor evaluation with its configured weightings.
first promise: The original confirmed delivery date, before reschedules.
reconfirmation: A vendor-requested new date; resets naive on-time clocks.
blocked invoice: An invoice the three-way match refused; see the blocks page.