“Who actually performs?”: answered from your own record.
Every confirmation, response time, dispute and delivery your programs generate becomes an explainable 1–5 scorecard. It's a data moat competitors can't copy, because they never captured the history, and it gets deeper with every program you run.
How the score is calculated
Instrument
The vendor lifecycle logs its own exhaust: confirmations, response times, changes, disputes, credit notes, deliveries. No forms, no surveys.
Derive
Five weighted dimensions roll into a composite on simple bands, Excellent to At risk, recomputed on a schedule, evidence attached to each.
Surface
The score meets you in the assignment flow, with the trend. A drop on a previously solid vendor is a signal-to-action, not a footnote.
Cheapest is a number; reliable is a record.
Enterprise procurement learned long ago that supplier selection isn't about the lowest quote, and that hard metrics must come from transaction data. No tool has given DMCs that discipline for ground vendors: the data lived in inboxes and memory. Yours now accumulates in the same system that runs the programs.
- Bands: Excellent, Strong, Fair, Watch, At risk
- Explicit confidence: insufficient, limited, established
- Every dimension opens to its evidence
- DMC-initiated changes never penalize the vendor
- Included on every plan: the history starts on day one
Reliability questions
Where do the scores come from?
From transaction data, never self-reporting: confirmation and re-confirmation rates, median response time to change requests, dispute and credit-note frequency, on-the-ground delivery signals, and repeat-assignment rate. Five dimensions, Reliability, Responsiveness, Stability, Delivery, Loyalty, weighted into a 1–5 composite with the evidence attached.
What if we've only run a few programs with a vendor?
The scorecard says “Building history” instead of faking a number. Confidence is explicit: insufficient, limited or established, and scores only render once the sample supports them. Honest cold start is a feature, not a gap.
Is it fair to the vendor?
Attribution is careful by design: changes you initiated don't count against the vendor, withdrawn disputes are netted out, and each dimension shows the evidence behind it. It measures how the relationship actually behaved, not who got blamed in the group chat.
Where does the score show up?
Where you choose vendors: on the vendor record and in the assignment flow, with the trend over time. A previously reliable vendor whose score drops is a signal to act on before the program, not after.
See it on your own programs.
A 30-minute walkthrough with the team, on data that looks like yours. Sales-led onboarding: we load your catalog, your vendors and your first programs with you.