← Manufacturing collection
Manufacturing Procurement Business Central

The Person Who Fills In Your Supplier Scorecard Never Sees the Downtime

The lowest quote wins on the one line Purchasing can see. The plant keeps the rest: missed trucks, crushed pallets, a changed spec, a line waiting on cartons. Who fills in each line of the scorecard, and what Business Central can and cannot show.

Christopher Wakare
Updated
7 min read
Manufacturing

The lowest carton quote won the award in spring. By summer the plant manager kept a different list: trucks that missed the dock, pallets that arrived crushed, a board grade that changed without notice, and a packing line standing idle waiting on cartons. Purchasing's supplier scorecard for that vendor read green. Unit price sat under the next bid, and purchase price variance (PPV) against standard came in favorable every month.

A packaging practitioner on X described the same scene this month: "the lowest box quote is rarely the cheapest box," and "Price is one line on the scorecard. Your plant manager remembers the other ones." I asked whether it comes down to the plant manager seeing the idle time while Purchasing sees the unit price. The answer: "Yep. Lost or Downtime is killer in most operations." Both posts are anonymous, so I use them as color, not as data.

The definition

A supplier scorecard is the periodic rating a manufacturer gives each supplier on price, delivery, quality and service. Total cost of ownership in procurement widens the price line to everything the buyer pays after the purchase order: freight, receiving, rework, line stoppages. The scorecard holds a cost line only if someone who sees that cost enters it.

How this was sourced

Analysis, not a deployment write-up; no customer deployment is described here, and the opening scene is a composite built from the X post, not a client. The documented parts rest on an IndustryWeek podcast page (15 December 2025), a Manufacturers Alliance (MAPI) survey summary (35 leaders; the page shows no survey year), three undated ReliaMag pages (a maintenance trade publication, linked below), an ISM page (26 December 2025), TechTarget (17 August 2026) and three Microsoft Learn pages read in November 2026 (linked below). The MAPI survey is small and its members skew large, and I have no count of my own on how plants split the work. The two-supplier table uses inputs I chose and says so.

Supplier scorecard metrics that leave out the plant

IndustryWeek's "Behind the Curtain" podcast (15 December 2025, hosts Dr. Mohamed Saleh and John Dyer) puts the mechanism in direct materials. The page summary says "a win for the purchasing department on price per unit could harm on-time delivery or quality on the factory floor." Its example is a GE price-cut initiative that erased supplier-partnership gains while costs rose elsewhere. Saleh: "When you go after a price, I think sometimes you shortchange yourself, and you're penny wise and pound foolish." GE is far larger than a 100 to 3,000 person plant, so the mechanism is what transfers, in my reading, not the scale.

The Manufacturers Alliance (MAPI) "Measuring Supplier Quality" survey asked 35 manufacturing leaders in supply chain and quality (run 2 March to 27 April; the page shows no year, and carries a 2026 copyright) how they run scorecards. 70% of companies have more than one function managing their scorecard, and a majority split responsibility between Quality and Procurement. The summary does not mention Operations. The sample is small and MAPI's members skew large, so take it as direction. The supplier performance metrics that Quality and Procurement hold are price, delivery and quality at receiving. Line hours lost to a supplier belong to neither, which is my reading of the split, not the survey's.

The maintenance trade press describes the same conflict from the parts side. Ricky Smith, CMRP, a maintenance reliability trainer and author, writes in ReliaMag (undated) that "Procurement optimizes for purchase price and inventory carrying cost." Smith writes about maintenance parts. Cartons are a production input, so carrying his point over is my reading. On that reading neither goal is wrong. A buyer scored on price and carrying cost who awards the lowest quote is doing the job as measured.

An article from ReliaMag's editors (Reliable Media and Alison Field, undated) puts a clock on it. Cost gets measured "at the point of purchase rather than the point of failure," and the consequences of a bad part "don't show up on anyone's scorecard for weeks or months." The same publication says that when procurement repeatedly selects the cheapest parts, "reliability teams feel the friction long before invoices clear" (ReliaMag, undated). In your carton story the award date and the line-down date sit months apart, and the purchase order carries only the first.

A unit price exists on the quote the day you award. A stopped hour exists in a shift report, if someone writes it down, six weeks later. The IndustryWeek page adds a second route to the line: suppliers squeezed on price may recover lost revenue by using "cheaper materials" or "materials at the low end of the specifications." In my reading, that is one way a board grade changes without notice, and the change reaches the plant before it reaches any scorecard line. The hosts recommend "joint scorecards that show all costs."

Blaming the buyer for chasing price misses it. These sources describe a buyer optimizing the lines the scorecard carries, on a scorecard that carries the lines its filler can see. Telling that buyer to think about total cost adds a request. It adds no column and no owner.

Total cost of ownership in procurement starts at the receiving dock

The ISM page on supplier performance measurement KPIs (26 December 2025) says total cost of ownership "goes beyond unit price" to logistics, storage, handling and lifecycle cost, and that "A higher unit price can be optimal if TCO is lower." It calls the scorecard a "single source of truth in supplier performance management." Its data governance table gives QA access to inspection data and EHS and operations access to incident reports, and it asks you to assign roles for data validation and escalation. It names no owner for line hours lost or spec changes.

The receiving dock is where those lines first become visible. The late truck, the crushed pallet and the board grade that is not the one on the purchase order all show up there days or weeks before the line feels them. A line stopped waiting on cartons shows up in the shift report. If the dock log, the shift report and the scorecard sit in three places with three owners, the carton supplier's scorecard shows a green price line and a clean record, and the plant manager's list stays on the plant manager's desk.

A supplier scorecard example: two quotes, two views

Take two carton suppliers and 2,000,000 cartons a year at 500 per pallet, which is 4,000 pallets. Every figure below is an illustrative input I chose to show the structure, not a measurement and not client data. The last column shows who holds each number.

Scorecard line Lowest-quote supplier Steady supplier Who sees it today
Unit price $0.380 $0.400 Purchasing, Finance
Price variance against the $0.400 standard 5.0% favorable 0.0% Purchasing, Finance
Delivered by the requested date 88% 98% Receiving sees the late truck. Purchasing sees a percentage only if the dates are kept
Pallets rejected or reworked 4.0% (160 pallets) 0.5% (20 pallets) Receiving, Quality. A posted credit memo can show in Business Central; rework does not
Spec changes without notice 3 a year 0 Quality, the plant
Line hours lost waiting on cartons 18 2 The plant

Illustrative model, not client data. Volume, pallet size and every supplier figure are the author's inputs.

Price the gap on three separate lines. Cash: 2,000,000 cartons at $0.02 less is $40,000 a year lower spend with the lowest-quote supplier. That is Purchasing's line, and the only one its report carries. Capacity: 140 more pallets rejected or reworked at an assumed half hour each is 70 labor hours a year at receiving and on the line. Whether those hours are redeployed or paid as overtime decides if they turn into cash, so count them once, as hours. Upside: 16 more line hours lost at an assumed $4,000 contribution margin per constrained hour is $64,000 of margin not earned. If the line has slack and you recover the hours later, the loss is overtime, not margin.

Keep the three lines apart. A Plant Head or VP Operations at a manufacturer of 100 to 3,000 employees running packing lines takes three kinds of number upward here, and only the first has an owner on the scorecard today. A supplier decision gets scored by the person who sees one of its lines.

Supplier selection criteria the plant manager would add

More columns do nothing without a filler for each. James Alan Miller of TechTarget, writing on supplier segmentation (17 August 2026), says scorecards and KPIs alone do not build resilience unless someone is accountable for acting on them, and that "Ownership also must extend beyond procurement," with operations among the groups he names. For the carton supplier that means four lines, each with a named filler and a named source:

  1. Line hours lost to supplier shortfalls. The shift lead or planner, from the downtime log, by supplier and cause.
  2. Rejected or reworked receipts. Receiving or Quality, from the receiving log, by supplier.
  3. Spec or material changes, with and without notice. Quality or Engineering, on the day a change reaches the line.
  4. Delivery against the requested date. Purchasing, from the receipt dates in the ERP.

Review the scorecard monthly with the plant in the room. Purchasing keeps price and delivery. The plant keeps the other lines. The lowest quote will still win some awards, and with the plant's lines filled in it wins them with the cost visible.

From scorecard to supplier performance management in Business Central

Business Central's purchasing overview (Microsoft Learn, updated June 2026) points to the Power BI Purchasing app to "analyze and monitor your procurement KPIs." That app includes a Vendor Quality Analysis report (Business Central 2025 release wave 2 and later) that, per Microsoft Learn, "analyzes vendor performance, showcasing vendor quality, returns, reliance and purchase discount trends." Its measures include Return Rate (Amount), purchase discount percentage, Spend Reliance % and Item Reliance %, built from value entries and purchase invoice and credit lines. It lists no delivery-timeliness measure. It counts a rejected pallet only once a purchase credit memo is posted against the vendor for it. Reworked pallets, spec changes and line hours never reach it.

Delivery timeliness depends on purchase line dates. The date calculation page (Microsoft Learn, updated October 2025) says that with a requested receipt date, Business Central subtracts lead time to set the order date, and adds inbound warehouse handling time and safety lead time to set the Expected Receipt Date. Without a requested date, it adds lead time to the order date first. The page also says "By default, many of the date fields this article mentions are hidden on purchase order lines." An on-time percentage built on those dates inherits your lead-time setup. Check which date your figure compares against and who keeps it.

In decision infrastructure terms, each scorecard line needs a named owner and a source. For the delivery line, the supplier on-time trend and overdue supplier deliveries signals in OpsGrid (in beta) check your Business Central online purchasing data on a schedule, rank the worst on-time performers and send a card to a named owner in Teams. The supplier delay alerts page has the detail. For these signals OpsGrid writes nothing to Business Central.

That covers one line of the four. OpsGrid works with Business Central online only and reads Business Central only, so line hours lost, rejected pallets and spec changes sit outside what it sees if your shift log, receiving log and quality system live elsewhere. Those lines need their own owner and their own log. Vendor quality holds and OTIF breach risk are on the OpsGrid roadmap and do not run today. OTIF itself has a separate gap between signal and action, covered in After-hours approvals are your OTIF problem.

Pull the last supplier you changed on price and write down the award date. Then total the line hours lost, rejected pallets and unannounced spec changes since, from the plant's own logs. If the person who scored that supplier cannot say where those numbers live, the scorecard carried one line of the cost.

Frequently asked questions

What is a supplier scorecard?

A supplier scorecard is the periodic rating a manufacturer gives each supplier, usually on price, delivery, quality and service, so awards and reviews follow a record instead of memory. It rates only what someone enters. Price and delivery come from purchasing and ERP data. Line stoppages, rejected pallets and spec changes appear only if the plant, receiving or quality enters them.

What metrics should a supplier scorecard include?

Four groups: price and price variance against standard; delivery against the date you requested; quality at receiving, meaning rejected or reworked receipts; and plant impact, meaning line hours lost to supplier shortfalls and spec changes with or without notice. Give each metric one named person who fills it from one named source by a set day each month. Price and delivery usually have an owner already. The plant-impact lines are the ones that need one.

What is total cost of ownership in procurement?

Total cost of ownership is the full cost of a purchase after the purchase order: freight, receiving, handling, rework, line stoppages and lifecycle cost, on top of the unit price. ISM's supplier performance page (26 December 2025) says it goes beyond unit price and that a higher unit price can be optimal if TCO is lower. Several of those lines are recorded by the plant and receiving, not by Purchasing, so someone has to carry them onto the supplier's record.

How do you create a supplier scorecard?

Start with the lines, not a template: price and price variance, delivery against the requested date, quality at receiving, and plant impact (line hours lost to supplier shortfalls, spec changes). Give each line one named owner and one source: the ERP for price and delivery, the receiving log for rejects, the downtime log for line hours. Set a fill date each month and review with the plant in the room. Include the plant-impact lines from the first version, because no one fills them in by default.

Which supplier misses reach your line before they reach Purchasing's report?

OpsGrid checks supplier on-time delivery in Business Central online on a schedule and sends a ranked card to a named owner in Teams. Talk through which supplier lines your plant tracks today.

Talk it through →

The Execution Edge

Monthly. For operations leaders building faster on AI. Real case studies, system blueprints, and tools, no fluff.

Your subscription could not be saved. Please try again.
Your subscription has been successful.