Vendor Onboarding vs Registration vs Prequalification

Direct answer: Registration records who a supplier is; onboarding determines whether it can be activated under the buyer's controls; prequalification evaluates suitability for a defined scope. Keep these decisions separate even when one portal collects their evidence.

Registration creates an identity record

Capture the legal entity, contact details and basic service information needed to route the application. Check whether the organisation already exists in the vendor master before creating another record. A new contact or trading name may belong to an existing entity rather than a new supplier.

Make the acknowledgement clear: receipt of an application is not approval to supply. Distinguish submitted information from independently checked information. The supplier should know which questions remain open and which team will make the next decision.

Onboarding controls activation

Determine the checks required for the proposed relationship, including the relevant identity, payment, contractual and specialist reviews. Assign each check to someone with the authority and competence to evaluate it. A completed questionnaire does not itself establish that the answers meet the buyer's requirements.

Define what activation permits. Creating a vendor identifier, allowing purchase orders and enabling payment may be separate actions in the buyer's systems. Record which approvals must precede each action so an early administrative step does not inadvertently authorise transactions.

Prequalification is tied to a scope

Assess whether the supplier has the capability, capacity and evidence for a particular category, project or service. A supplier approved for one location or activity should not automatically be treated as qualified for a substantially different assignment.

Specify the evaluation criteria and required evidence before assessment. Record any limits, conditions and validity period. If the supplier's offering changes, decide whether the existing qualification still applies rather than copying the earlier result into a new tender.

Connect the stages without collapsing them

Use one stable identity across the registration, onboarding and qualification records. Keep stage status and reasons visible to downstream teams. For example, a supplier may have a verified identity but still be awaiting a technical assessment; calling the entire record complete hides that distinction.

Agree how rejected, withdrawn and conditional cases are handled. A supplier returning with new evidence should not need a duplicate identity merely to restart review. Preserve the earlier decision and link the new assessment to it.

Test the handoffs

Walk through a new registration, an existing supplier applying for another category and a conditionally approved supplier whose permission expires. Check what procurement, finance and the supplier each see. Confirm that no one mistakes an acknowledgement, a vendor number or an uploaded document for an approval decision.

Clear terminology is useful because it changes behaviour: the right team receives the right question, and the resulting permission has an identifiable scope.

How Vendoreye supports this workflow

Vendoreye can coordinate structured intake, tenant-controlled categories, document requirements, evidence review, assessment, remediation, approval, lifecycle status and audit history. Tenant-scoped APIs can expose governed vendor information to ERP and procurement systems. Vendoreye does not replace the customer's responsibility for legal interpretation, policy, source verification or final decisions. Continue with the related implementation resource.

Sources and editorial basis

1. OECD due diligence guidance

These sources establish the official or recognised framework used in this article. Vendoreye's workflow recommendations are identified as implementation guidance rather than statements of universal law.