Supplier Scorecard

Builds each supplier's record from the ERP: deliveries on time or late over the last year, the open book today, and whose prices moved.

ReadsERPSupplier email

You get · Table on screen

Problem: Supplier calls run on impressions. The delivery record is scattered across a year of receipts nobody assembles, so the loudest recent problem stands in for the whole year.
Impact: Without the record there is no leverage in the conversation, and the suppliers who quietly deliver never get credit for it.
Solution: Builds each supplier's record from the ERP: deliveries on time or late over the last year, the open book today, and whose prices moved, with how fast they answer email beside it. One standings table, worst record first, so you walk into a supplier call knowing the record.

01 · What it looks like

The real screen, from a real run.

Nothing here is a mockup. These are captures of the working app against a live ERP, and the numbers in each caption are the numbers in the picture above it.

The Supplier Scorecard output: 8 of 20 suppliers flagged, 4 delivered late at least once, 7 raised a price, across 24 deliveries checked in the last year. — 8 of 20 suppliers flagged, from 24 posted deliveries over the last year. Worst record first: late on 2 of 6 deliveries, 12 days late on average, 2 parts up in price, no word on 9 open orders. That is the sentence you want before the call, and it is the one nobody has time to assemble by hand.

See the other tasks How Ask Mack works →

Which of these is your Monday morning?

Book an assessment and we will map the repeating work in your plant, then show you what the first build looks like against your own systems.

Book an Assessment Explore Project Foundry →