Prequalification and onboarding are often talked about as though they're the same thing, or as though one is a lighter version of the other. They're not. They solve different problems at different points in the supplier lifecycle, and using one where you need the other is why most procurement processes feel slower than they should.
Prequalification: should we even be talking to this supplier?
Prequalification answers a question about fit. Before you invest time in evaluating a supplier, negotiating terms, or starting onboarding, prequalification tells you whether they meet the basic criteria for the work.
That might be capability-based — do they have the equipment, certifications, and track record for CNC machining at automotive tolerances? It might be compliance-based — are they cleared under Section 889, do they carry the required insurance, have they passed a background check? Or it might be both.
The key characteristic of prequalification is that it happens before any commitment. You're not onboarding the supplier, you're not creating a vendor record, you're not asking them to fill in banking details. You're asking: of all the suppliers out there, which ones are worth a closer look?
Done well, prequalification produces a shortlist of three to five suppliers who can demonstrably do the job, with the evidence already in hand. Done badly, it produces a list of whoever responded to the RFI, with no way to distinguish between a qualified supplier and an optimistic one.
Onboarding: this supplier is approved — now make them payable
Onboarding answers a different question: we've decided to work with this supplier, so what do we need to collect, verify, and configure before the first purchase order can go out?
That means tax ID validation, banking details, insurance certificates, compliance documents, sanctions screening, and the creation of a vendor record in the ERP. It's administrative, it's necessary, and it's where most of the elapsed time in supplier management actually sits.
Onboarding is not a filter — it's a process. By the time a supplier reaches onboarding, the decision to work with them has already been made. The question is how quickly and accurately you can turn that decision into a working relationship.
Where the confusion causes problems
The most common mistake is using the onboarding process as a substitute for prequalification. A buyer needs a new supplier, skips the qualification step, and sends them straight into onboarding — full compliance packet, banking details, insurance, the lot. Three weeks later, halfway through the process, someone discovers the supplier doesn't have the right certifications for the work. The onboarding is abandoned, the time is wasted, and the search starts again.
The reverse mistake is less common but equally costly: running an extensive prequalification exercise and then requiring the same supplier to re-provide everything during onboarding. The supplier has already proven they're qualified — now you're asking them to fill in the same information in a different system, with different forms, reviewed by different people. That's not compliance; it's duplication.
The third problem is using neither. A surprising number of organisations, particularly those that have grown through acquisition, have suppliers in their ERP who were never formally qualified or onboarded. They were added by someone in a business unit who needed a vendor number, and they've been trading ever since. These suppliers aren't non-compliant on purpose; they're non-compliant because nobody's job was to check.
How they should work together
The right model is a funnel: prequalification narrows the field, selection chooses the supplier, and onboarding makes them operational. Information collected at the prequalification stage carries forward — a supplier who's already provided their certifications and capability evidence during prequalification shouldn't be asked for them again during onboarding.
In practice, this means the two processes need to share a data layer. A capability badge earned during prequalification should be visible to the onboarding team. A sanctions screening run during prequalification shouldn't need to be re-run three weeks later during onboarding — unless the result has expired, in which case the system should know that and re-run it automatically.
This is where most organisations hit a wall, because their prequalification and onboarding are different systems, different teams, and different processes. The supplier provides the same information twice, the buyer reviews it twice, and neither team knows what the other has already confirmed.
What to look for in a platform
If you're evaluating tools, the question that separates a real solution from a rebadged form-builder is: does the prequalification data carry through to onboarding?
Specifically:
- Can a supplier who scores well in prequalification start onboarding without re-providing their certifications, insurance, and compliance evidence?
- Does the system re-run time-sensitive checks (sanctions, insurance currency, financial standing) automatically, rather than relying on the buyer to remember?
- Can the buyer define different onboarding paths for different supplier types — a full compliance packet for a strategic vendor, a lightweight path for a one-off consultant — or does every supplier go through the same process regardless?
- Does the approved supplier record flow into the ERP automatically, or does someone have to re-key it?
If the answer to any of these is no, you have two systems wearing a trench coat rather than an integrated process.
The bottom line
Prequalification and onboarding are both necessary, but they do different jobs at different times. Using one where you need the other is a process problem, not a technology problem — but the right technology makes the right process easy to follow.
If you want to see what this looks like in practice, the sourcing agent will build a prequalification project from a plain-English description, and onboarding goes live in eight weeks. Both run on the same platform, sharing the same supplier data.