Vendor base monitoring
Silence is not the same
as still trading.
The businesses your operation depends on go quiet long before anything tells you why. Send us the base, we match it against the datasets we publish, and every cycle after that returns what moved.
The cycle
One match is a check. A sequence is a picture.
A base does not go wrong all at once. It goes wrong a few records at a time, and the only way to see that is to look again.
You send the base
The suppliers, merchants or vendors you depend on, as a file. Business name and location is enough to match on. We tell you upfront if a column we need is missing.
We match it against the datasets we publish
Merchants, hospitality, hotels, quick service and licensed fleets, with more in build. Building the datasets out past that range is separate work with its own scope.
You get what we hold against each record
Trading status, category and location against every record we match, plus review rating where we hold one, and an owner or operator name where we can identify it.
Every cycle after that returns only what moved
The second match is where this starts earning. You read a short list of differences instead of rereading the base you already know.
What a cycle returns
What moved, and what didn’t
Every record in your base comes back under one of six classes. No change is most of the file, most cycles, and we say so rather than dressing it up.
Stopped trading
The record no longer shows as trading in the data we hold. It goes to whoever owns the relationship, on the cycle rather than on the day it bites.
Changed hands
The operator we hold is not the one we held last cycle. Usually the tell that the contract and the named contact you hold are pointing at someone who has gone.
Moved category
The category we hold is not the one we held last cycle. Usually the tell that what they do for you has changed as well.
Detail updated
Location, contact or rating moved. Small on its own, and collectively the reason a base drifts without anyone deciding it should.
No change
Most of the base, most cycles. We return it explicitly, because a short exception list is only worth reading if you know what it was measured against.
Not held
We don't hold a record for this one. It comes back as unmatched rather than as a status we guessed at, so the rest of the list stays worth trusting.
The fence
What this is not
- Point in time
- It reflects the datasets we publish at the point of the cycle. Not a live feed.
- Records only
- We hold documented records on UK businesses. We do not observe your operation and we hold nothing out of it.
- No score
- We return what we hold and what changed. Never a risk score, never a number standing in for the record.
- Your base only
- We recheck the records you send us. Nothing else comes back.
At scale
When the base gets big
Large bases run in a private tenant with custom scope and dedicated data ops. Cadence is scoped with your team.
FAQ
Frequently asked questions
How current is the picture?
Cadence is scoped with you against how fast your vendor base moves. Each match returns what we hold at that moment, and every cycle after the first returns the differences against your previous one. If you need a particular cadence we scope it with you, and we tell you plainly where the underlying source will not support it.
What comes back against each record?
An owner or operator name where we can identify it, on top of the trading status, category and location the cycle carries, plus review rating where we hold one.
Can I see it against my own base first?
Yes. Send a sample of the base and we match it against the datasets we publish, so you can see what we hold against your own records, and how much of them we hold, before committing to a cycle.
How does a cycle come back?
The first match returns as a CSV of your own base with what we hold against each record, or you read it in the platform. Every cycle after that returns the differences the same way, so what lands is a short list of what moved rather than the whole base again. Your records keep the identifiers you sent them with, so the file lines up against the base you already hold.
What is the lawful basis for the data you return?
Legitimate interests, documented under Article 6(1)(f) of the UK GDPR, with a Legitimate Interest Assessment available on request. We hold documented records on UK businesses and supply them controller to controller. What comes back describes the business and, where we hold it, the person operating it in that business capacity. Full policy detail sits on our compliance page.
Get started
Match the base you depend on
Send a sample and see what we hold against it.