Workflow guide
How to screen a supplier before onboarding
Resolve the company first, run restrictions second, and only export when the supplier is worth carrying into a real onboarding, sourcing, or vendor approval workflow.
Best for
Sourcing operators, onboarding teams, and consultants who need a repeatable supplier screening path.
Start with identity, not exports
The first question is whether you are looking at the right company. Resolve the entity first, then layer sanctions and restriction checks only after the name and jurisdiction are stable.
- Start with a company or supplier name query
- Confirm the closest legal entity before screening
- Avoid exporting before the identity check is settled
Run the restriction layer second
Once the entity looks plausible, move into watchlist and restriction-style screening. That keeps the workflow short and reduces false starts in onboarding.
- Use a single request path for entity plus risk checks
- Keep the same key as you move from test to recurring work
- Export only when the supplier deserves a saved dossier
Know when the workflow is a fit
This workflow is strongest when you need a repeatable public-data screening surface for sourcing, onboarding, or compliance support. It is weaker for bespoke investigations that require private internal evidence.
- Best for sourcing agents and vendor onboarding teams
- Useful for early-stage supplier triage
- Not a substitute for private diligence or legal advice
Validate the supplier fast, then decide if it belongs in recurring work.
The point is not to create more manual review. The point is to cut down the time between a supplier name and a usable screening decision surface.
Run a free company lookup
Test entity resolution before you decide whether this supplier needs deeper screening.
Compare company lookup options
See where a delivery-oriented API beats broad registry search for repeat work.
See plan limits and export access
Review when free evaluation should move into recurring screening and saved exports.