What separates a partnership from an ordinary supply relationship?

Not warmth, and not the length of the relationship. What separates them is that information moves before it has to. In an ordinary arrangement the buyer learns about a problem when a delivery arrives wrong; in a working partnership the supplier says in advance that a shipment will be late, that a lot sits near a limit, or that a raw material source is changing. That behaviour is worth more than any commercial concession, and it only develops where early disclosure is rewarded rather than punished.

How many metrics should a supplier scorecard have?

Few enough that each one is looked at. Four or five is usually sufficient and more than eight is reliably ignored. Choose measures that reflect something the supplier can actually influence, that you can compute from records you already keep, and that point at different failure modes rather than three versions of the same one. A scorecard that takes an afternoon to assemble each month will quietly stop being assembled, which is worse than having chosen fewer measures.

How often should a formal review happen?

Frequently enough to be about trends rather than incidents, which for most material relationships means quarterly or twice a year, with the interval set by volume and by how much the relationship is changing. The critical part is not the interval but that the meeting has a fixed agenda, a written output and named actions with owners and dates. A review that is only ever an update becomes optional, and optional meetings are the first thing cancelled in a busy period.

What should a complaint contain to be actionable?

Enough for the supplier to find the material and reproduce your observation: the lot identification, the delivery date and quantity, the specific observation with the method and result, the retained sample reference, the immediate effect on your process, and whether affected stock is contained or released. A complaint that states only that the material was unsuitable cannot be investigated, and the investigation that follows will be a negotiation about what happened rather than an analysis of it.

When should an issue be escalated, and to whom?

Escalate on time elapsed rather than on frustration. Agree in advance what response each stage of an issue should receive and by when, and agree that missing the deadline moves it up a level automatically, on both sides simultaneously. Escalation to a named counterpart at the same level, rather than to whoever is senior, keeps the process procedural instead of personal, and means that someone with authority sees the issue before positions have hardened.

Supplier partnership in practice: metrics and reviews

Company news · Eapearl Chemical · 15 December 2025

Partnership is the most-used and least-defined word in industrial purchasing. It becomes a real thing at the point where somebody writes down what is measured, when it is reviewed and what happens when it goes wrong.

A word that means nothing until it is measured

Ask two people in the same company what the partnership with a given supplier consists of and the answers usually diverge. One describes a long relationship and good personal contact. The other describes a recurring documentation problem that nobody has raised formally. Both are accurate, and the gap between them is where these relationships quietly deteriorate.

The purpose of measurement here is not to generate pressure. It is to give both parties the same picture, so that a conversation about performance starts from a shared set of facts rather than from competing recollections. A supplier who is told that the documentation was wrong a specific number of times last quarter can act on that. A supplier told that there have been problems with paperwork can only become defensive.

Choosing few measures that point at different things

Measure	What it exposes	Usual counting dispute
Lots released within specification	Process control at the supplier	Whether a lot accepted under concession counts as conforming
Deliveries complete and on the agreed date	Planning and logistics reliability	Which date counts when the buyer requested a change
Documentation correct with first delivery	Administrative control, often the earliest warning	Whether a same-day correction still counts as an error
Time to acknowledge a complaint	Whether the issue route functions at all	When the clock starts, and whether it runs over holidays
Time to a written investigation report	Whether the supplier investigates or merely responds	Whether an interim reply stops the clock
Advance notice of a problem	The behaviour that distinguishes a partner	Hard to count; often better tracked as named examples

The counting disputes in the third column are not pedantry. Every one of them will arise, and agreeing the rule before the first measurement is the difference between a scorecard that informs a discussion and one that starts an argument about arithmetic.

The measure that resists counting

The most valuable supplier behaviour is the hardest to put a number on: telling you about a problem before you discover it. A supplier who reports that a lot sits close to a limit, that a shipment will miss its date, or that a raw material source is being changed, is giving you time to act. A supplier who lets you find out has transferred the cost of their problem to you.

Counting these is awkward because early warnings look like bad news, and any system that scores them naively will reward concealment. The practical approach is to record named examples in the review record rather than to score them, and to make it explicit in the meeting that early disclosure is treated as good performance. Then take care that your own organisation behaves accordingly, because one hostile reaction to a voluntary disclosure will end the practice permanently.

The review meeting

A review that consists of each side reporting that things are broadly fine is a waste of two diaries. Give it a fixed agenda and a written output, and hold it on a schedule rather than when someone remembers.

The figures since the last review, circulated in advance so the meeting discusses causes rather than discovering numbers.
Open actions from the previous review, each closed or explicitly carried with a reason.
Every complaint raised in the period, with its current status and the corrective action taken.
Changes on either side: process, site, personnel, raw materials, regulatory position, packaging.
Forecast and capacity for the coming period, including anything the supplier needs from you to plan.
One item from each side that the other could do better. Requiring both directions keeps the meeting honest.

The written output does not need to be long, but it must name actions, owners and dates. An action with three owners has none, and an action without a date will be discussed again in the same form at the next meeting.

Complaints: a route that actually works

The purpose of a complaint procedure is to convert an observation into a correction that lasts. Most fail at one of two points: the complaint does not contain enough for anyone to investigate, or the response addresses the individual delivery without touching the cause.

A usable complaint identifies the lot and the delivery, states the observation with the method and result, references a retained sample, describes the effect on your process, and says whether affected stock is contained. A usable response comes in stages: acknowledgement that the complaint has been received and understood, containment describing what has been done about material already shipped, investigation setting out the cause with evidence, corrective action saying what has changed so the cause cannot recur, and verification confirming after some period that it has not.

The verification step is the one most often skipped, and it is the only one that distinguishes a corrective action from a promise. Agree who checks, against what, and when.

Escalation without personalising it

Escalation works when it is automatic and symmetric. Agree the response time expected at each stage, and agree that exceeding it moves the issue to the next level regardless of how anyone feels about it. Agree also that the route is level to level, so that a technical stalemate goes to the technical managers on both sides and a commercial one to the commercial managers, rather than everything travelling to whoever is most senior.

Two properties make this work. It is not a complaint about a person, because nobody chose to escalate; the clock did. And it is reciprocal, so the supplier can escalate your unanswered questions by the same route, which they will need to do at least as often as you will.

What the supplier should get in return

Relationships described as partnerships are frequently one-directional in practice: the buyer measures, the supplier is measured. The obligations that make the arrangement real run the other way as well. Forecasts that are shared honestly, including when they are uncertain. Payment on the agreed terms, which is more persuasive than any scorecard. Notice of your own changes, since a reformulation or a new market alters what the supplier must provide. Feedback on material that performed well, not only on material that failed. And a named, reachable contact who does not change without introduction.

When partnership is the wrong model

Not every material deserves this. A commodity bought occasionally on price, with several interchangeable sources and no qualification burden, does not justify a scorecard or a quarterly meeting, and imposing one consumes attention that a critical material needs. Reserve the apparatus for sources where switching is slow, where the material is embedded in a registered or qualified product, or where a supply interruption stops your plant.

The judgement is about consequence, not about volume. A small-quantity specialty embedded in a qualified formulation can be far more critical than a bulk commodity such as ethanol or butyl acetate, precisely because it cannot be replaced quickly. To discuss supply arrangements, documentation or a technical review against a named application, use our contact page.