Free — no card required

Vendor and Supply Chain Risk

Entity legitimacy, compliance disclosure, and product safety, checked in one workflow

The problem

Vetting a supplier or vendor properly means checking more than whether they're a real, active business. It means knowing whether they've met their own compliance obligations, and whether anything in their product line carries a live safety issue. Most procurement processes check the first and skip the other two, not from carelessness, but because each lives in a different register nobody's checking regularly.

How it works together

Entity verification confirms a supplier is a real, currently registered business. Modern Slavery Register lookup confirms whether they've actually filed a required statement, a missing one is itself a risk signal. Food recall screening, relevant for any supplier in the food or consumer goods chain, flags whether their products carry an active recall. Run together, this covers entity legitimacy, compliance disclosure, and product safety in one workflow.

Which plan you need

All three are Free. This is the one workflow on this list with no paid component to get started, batch screening across an active supplier list on the recall and modern slavery products requires Professional.

Further reading

Frequently asked questions

Does this apply to all suppliers, or just food and consumer goods ones?
Entity verification and Modern Slavery Register checks apply to any Australian supplier. Food recall screening is only relevant where the supplier's product line is food or beverage related.
How do I check an entire supplier list at once rather than one at a time?
Individual lookups are Free. Batch screening across an active list requires Professional on both the recall and Modern Slavery products.
What does a missing Modern Slavery statement actually mean?
It doesn't automatically mean noncompliance, some entities fall below the threshold or file late. It's a signal worth investigating, not a conclusion on its own.
Can this run as a recurring check rather than a one off at onboarding?
For recurring monitoring specifically, that's what CMaaS is built for, this workflow covers the point in time check, CMaaS extends it into something ongoing.
Get started free View API docs