Define the request
Name the category, site, part family or service, business reason, criticality and decision deadline.
Ask only what the category and risk tier require, return incomplete responses, separate evidence review from authority and record exactly what the supplier is approved to provide.
Qualification is not a one-time Approved label. The live example distinguishes questionnaire completion, evidence readiness, audit need, review stage, conditions and approved-until date.
Start with Jodoo’s Free plan for up to five users. No credit card required.
The path should become stricter as supplier criticality, scope or regulatory exposure increases.
Name the category, site, part family or service, business reason, criticality and decision deadline.
Request the questionnaire, certificates, audit history, capability facts and declarations that apply to this scope.
Return missing, expired or inconsistent evidence with an accountable correction path.
Approve, conditionally approve, reject or defer with a recorded basis and approved-until date.
Translate the decision into a usable authorization for category, location and item family.
Qualification effort should match what can go wrong.
Confirm identity, commercial prerequisites, core policies and basic capability.
Add process capability, quality certification, control plans, audit or sample evidence.
Add regulatory scope, data handling, traceability, change notification and authorized specialist review.
Trigger a focused review after major defect, ownership change, certificate lapse, site move or sustained performance decline.
Procurement can coordinate without silently becoming quality, security or legal approval.
Quality, compliance, security, sustainability or operations record findings in the same case.
The final decision retains conditions, expiry, review owner and the evidence available at that time.
The pilot should prove that policy becomes usable reviewer work without creating a universal questionnaire.
Document the category, sites, part families or services, risk levels, mandatory evidence, specialist reviewers and the person authorized to approve each scope.
A routine supplier should move from request through review into a dated, scoped authorization with its evidence and decision owner still connected.
Use an expired or inconsistent certificate to prove the reviewer can return the case, the correction remains visible and approval cannot bypass the gap.
Add a limited scope, extra receiving control or short review date and confirm that downstream users can see the condition before using the supplier.
It organizes qualification requests, questionnaires, supporting evidence, specialist reviews, decisions, conditions, approved scope and requalification dates so teams can prove why a supplier is eligible.
Usually not. Approval is more useful when it applies to a defined category, part family or service, site, region and time period, with explicit conditions.
Use the scheduled review date plus event triggers such as certificate expiry, site or ownership change, serious defect, audit failure, new category, material process change or sustained performance decline.
Yes. A trained Jodoo administrator can add a category requirement, conditional evidence field or specialist review route in tens of minutes to a few hours, then test complete, returned and conditional cases before publishing the change.
No. Keep the ERP supplier identity where it is authoritative and store the reviewed qualification case, conditions, dates and approved scope as linked operational records.
Test a complete supplier, a returned evidence package and a conditional approval, then change the risk rules to match your real sourcing policy.