Two scorecards land on a CPG supply team. One comes from a retailer and grades you: on-time delivery, fill rate, chargebacks, case accuracy. The other is the one you keep on your own co-packers, distributors and 3PLs, and it is usually a spreadsheet.
Vendor scorecard software is the category that automates the second one, and the reason evaluations go wrong is that the software is easy to compare on features and hard to compare on inputs. A scorecard is arithmetic. Whether it is worth anything depends on where the ordered quantity, the delivered quantity, the promise date and the receipt date come from, and whether all four agree on what a case is.
The definitions that decide the score
Before looking at any tool, settle these, because two teams using the same software and different answers here will produce different grades for the same supplier.
- Fill rate against what: the original order, the order after your own team amended it, or the quantity confirmed by the supplier. The same delivery passes or fails depending on which denominator you picked.
- On time against which date: the requested date, the confirmed date, or the appointment the warehouse gave the carrier. Appointment scheduling moves the goalposts and is often outside the supplier's control.
- Whose unit: cases, pallets or eaches, and what happens when a pack configuration changes mid-quarter.
- When a short shipment closes: a line delivered in two drops is one late delivery or one on-time and one late, and the choice changes a quarterly average.
- Which failures belong to the supplier: a stockout caused by your own late forecast is not a supplier miss, and a scorecard that cannot separate the two gets ignored the first time it accuses someone unfairly.
Every one of those is a business rule rather than a feature. Software that lets you configure them is better than software with a fixed opinion, and neither helps if the rule lives only in the head of the person who built the report.
The categories of vendor scorecard software
Four categories sell into this problem, and they are built for different jobs.
Procurement and supplier management suites
Built around the purchasing process: sourcing events, contracts, supplier onboarding, and scorecards as one module among many. They are the right home when procurement is the function driving this and the supplier base is large enough that onboarding and compliance are real work. Their scorecards read from purchase orders and receipts inside their own process, so a supplier relationship managed outside that process tends to be invisible to them.
ERP and warehouse reporting
Your ERP already holds the order, the receipt and the dates, and most, NetSuite included, ship a supplier performance report. Where all purchasing runs through one ERP, this is the cheapest correct answer, and it is underused because the report is ugly rather than wrong. It falls short when receipts happen in a 3PL system that syncs on a delay, or when half the volume moves through a co-packer arrangement the ERP records as a transfer.
BI dashboards on a warehouse
A modelled dataset in BigQuery or Snowflake with a dashboard on top gives you exactly the definitions you choose, which is the strongest version of this if someone owns the model. The assumption to test is that ownership: the dataset needs the joins between orders, receipts, pack configurations and supplier master data maintained by someone, and when that person changes role the definitions stop being maintained while the dashboard keeps refreshing.
Spreadsheets
Still the most common answer, and for a brand with eight suppliers and one warehouse it is a reasonable one. The failure is not the tool, it is the refresh: a monthly rebuild that takes a day gets skipped in a busy month, and a scorecard nobody has updated since the quarter before is a document rather than a control.
| Category | Strongest when | What it assumes |
|---|---|---|
| Procurement suite | Procurement owns the programme and the supplier base is large | Purchasing runs through its process |
| ERP reporting | One ERP holds every order and receipt | Receipts are timely and complete |
| BI on a warehouse | You want your own definitions and have someone to own them | The data model exists and is maintained |
| Spreadsheet | A handful of suppliers and one warehouse | Someone rebuilds it every month |
Where we fit
We are not a scorecard product, and a brand whose purchasing already runs cleanly through one ERP should use the report it already paid for. Permute is the layer underneath, for the case where the inputs are the problem rather than the presentation.
We connect the ERP, the 3PL feeds, the co-packer spreadsheets, the retailer portals and the rest of the systems we connect, resolve suppliers and products to one record each, and hold fill rate, on-time and chargeback attribution as explicit rules rather than formulas in a workbook: when the team agrees fill rate measures against the confirmed quantity, that definition is written once and every report mentioning fill rate uses it. A supply lead can then ask which suppliers missed confirmed quantity beyond the agreed tolerance last quarter and see the answer with the receipts behind it, which matters most in the meeting where a supplier disputes the number. The Governance layer is what makes the next step safe: you can share a supplier their own performance, scoped to their own rows, without exposing what their competitor charges you. Late feeds are visible as late rather than absorbed, so a quarterly grade does not change after it was sent.
Our limits are worth stating plainly. We read from the systems we connect and do not write back, so a corrective action or a debit memo is still raised in your ERP. We do not run the sourcing process, hold contracts, or manage supplier onboarding, and where those are the requirement a procurement suite is the right purchase, sitting on top of data we can supply.
Check whether your inputs support a scorecard
Connect your ERP and a 3PL feed, then rebuild last quarter's fill rate with the definition you meant.
How to run the evaluation
Take one supplier and one quarter into every demo (the supplier you argue with most, not the easy one). Ask the vendor to reproduce a number you already believe, using your definition of fill rate, from the systems that hold your receipts. Most of what you need to know arrives early in that exercise.
Then ask three questions that separate a scorecard from a report. Where does the confirmed quantity come from, and what happens when the supplier confirms by email? What does the tool do in the month a pack configuration changes? And when a supplier disputes a grade, what can you show them, at row level, without exporting to a spreadsheet first? A tool that answers those three well is worth more than one with twice the visualisations. Consumer brands running the same evaluation on the demand side will find our CPG analytics software breakdown covers the wider tooling question, and How to automate POS data analysis covers the retailer feeds these scorecards depend on. If the answer turns out to be that the inputs need work first, what it costs is the honest next question.
Bring one disputed supplier number
We will trace where it comes from across your systems and what it would take to defend it in the next review.
Questions supply teams ask about scorecards
Which metrics belong on a vendor scorecard?
Four carry most of the value: fill rate against confirmed quantity, on-time delivery against the confirmed date, case and label accuracy, and cost of failure in chargebacks or expedited freight. Quality and responsiveness measures are worth adding once the first four are trusted.
Adding a fifth metric before the first four are defined makes the scorecard longer without making it more persuasive.
How often should a scorecard be refreshed?
Monthly for internal review and quarterly for the supplier conversation, which matches how quickly a supplier can act on it. Weekly refreshes tend to produce noise that nobody has time to respond to.
The refresh cadence matters less than whether the number can be traced when it is questioned, since a disputed grade you cannot support undoes a quarter of goodwill.
Can we share a scorecard with the supplier itself?
Yes, and doing so is most of the value, since a grade nobody outside the building sees changes nothing. The constraint is access: a supplier should see their own performance and nothing about anyone else.
That is a permissions question rather than a reporting one, and it is worth checking how the data is handled before the first file goes out.
What about the scorecards retailers keep on us?
Those arrive in the retailer portal on their definitions, and you cannot change the arithmetic. What you can do is reconcile their view to your own shipment and receipt records, so a disputed chargeback has your evidence attached before the deadline to contest it passes.
Brands that do this well treat the retailer scorecard as a feed to be reconciled rather than a verdict to be filed.