AI agent · Manufacturing · Chase what is missing
Supplier certificate tracking
Your approved supplier list is only as good as the certificates behind it. The agent reads every certificate and compliance declaration on file, checks that it covers the right site and scope, requests renewals before they lapse, and tells supplier quality where the gaps are.
Typical volumes for this process, not a client figure.
Certificates sit in shared folders; expiries surface at audit or when a customer asks.
Every certificate read and dated; renewals requested before expiry, gaps sent to quality.
Where the time goes today
A supplier stays on the approved list because of documents: a quality management system certificate from a certification body, approvals for special processes such as heat treatment, plating or welding, and declarations on restricted substances and material origin that your own customers require you to collect. A mid-sized manufacturer holds thousands of these across hundreds of suppliers, each with its own validity dates and scope.
They usually live in shared folders or as attachments in the supplier record. Someone in supplier quality checks them at onboarding, and again when an auditor or a customer asks for evidence. Between those moments, certificates expire, certification scopes change, and a supplier moves production to a new site that the certificate does not cover.
Two checks take real reading. The first is scope and site: a certificate may be valid but cover the supplier's head office, not the plant that makes your parts, or a scope that excludes the process you buy. The second is declarations that do not expire but go stale: when the restricted substance list your requirement refers to is updated, every declaration made against the previous list needs renewing, and nobody tracks that.
How the agent works
- Inventory what existsThe agent reads every certificate and declaration on file and records type, holder, site address, scope, number, issuing body and dates, each linked to the page it came from.
- Map to requirementsIt works out which documents each supplier must hold from the commodities and parts it supplies and the requirements your customers flow down to you.
- Watch dates and listsIt tracks expiry dates and watches for updates to the substance lists and specifications your declarations refer to, marking affected declarations for renewal.
- Request and check renewalsAhead of each expiry, it sends the supplier a specific request. When the renewal arrives, it checks holder, site, scope and dates against the requirement and returns anything that falls short with the reason.
- Update and escalateIt updates the certificate status in your supplier record and escalates to the supplier quality engineer when a certificate lapses, a scope narrows, or a supplier stops responding.
What stays with a person
The supplier quality engineer keeps approval decisions. Whether a lapsed certificate suspends a supplier, whether new orders are blocked, whether a scope wording covers the part you buy, and whether to accept a temporary waiver are judgements with commercial and quality consequences. The agent sets a status; whether that status blocks purchasing is a rule you configure in your ERP, not a decision the agent takes.
Customer notifications also stay with people. If a supplier's certificate is withdrawn and the parts go into a customer's product, your customer contract may require you to tell them; that message is written and sent by your quality team.
What it reads, what it produces
| It reads | It produces |
|---|---|
| Certificates and declarations in folders, the supplier portal and the supplier record | A register of every certificate and declaration with scope, site and dates |
| The approved supplier list and the commodities each supplier provides | Renewal requests sent ahead of expiry |
| Customer requirements that flow down to your suppliers | Rejection notices stating what a renewal fails to cover |
| The current versions of the substance lists and specifications you require | A list of declarations made stale by a list or specification update |
| Certification bodies' public directories, where their terms permit automated lookups | An escalation queue for the supplier quality engineer |
Controls that come with it
- The requirement map is owned by supplier quality and versioned
- A certificate is marked valid only when holder, site, scope and dates all pass
- Purchasing blocks are applied by your ERP rules, never by the agent directly
- Each check stored with the document page and the values read
- A quarterly sample of valid certificates rechecked by a person
- Waivers recorded with who granted them, why and until when
How you know it works
- Suppliers with an expired or missing certificate on any given day
- Days between expiry and a valid renewal on file
- Audit findings related to supplier certificates
- Declarations older than the current list version
- Supplier quality hours spent collecting documents
Is your process ready?
- Written rules: the requirement per commodity is often implicit. Write down which certificate each supplier type needs and what scope wording is acceptable.
- Systems: the supplier record in your ERP or quality system must accept status updates by interface, and its licence must permit automated use.
- Cheap check: each result can be compared with the certificate page in seconds, and customer audits test the register independently.
- Volume: hundreds of suppliers with several documents each repays the build; a short list of critical suppliers can be tracked by hand.
- One description: purchasing and supplier quality must agree what happens when a certificate lapses, before the agent starts reporting lapses.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Certificates naming the group or head office instead of the manufacturing site you buy from.
- Scope wording that sounds broad but excludes the process you actually buy, such as design or a special process.
- Suppliers who answer renewal requests with the old certificate again, which must be caught by date, not by file name.
- Certification body directories with terms that forbid automated lookups; check before building on them.
Questions we get
How is this different from tracking subcontractor documents on a construction site?
Here the focus is the approved supplier list over years rather than a project over months. The difficult checks are scope and site, which require reading the certificate carefully, and declarations that go stale when a referenced list changes. The consequence of a gap is usually a quality or customer compliance issue rather than site access.
Can the agent confirm a certificate has not been withdrawn?
Where the certification body publishes a directory and its terms permit automated lookups, yes: the agent checks the certificate number and status on a schedule. Where no directory exists or lookups are not permitted, the agent relies on the document and the supplier's response, and your quality team decides whether direct confirmation is needed for critical suppliers.
Will it block purchase orders to a supplier with a lapsed certificate?
Not by itself. The agent updates the status on the supplier record. Your ERP applies whatever rule you have set for that status: a warning, a block on new orders, or nothing. Supplier quality decides the rule per commodity, because blocking a sole-source supplier is a different decision from blocking one of five.
What do we need to start?
Your current supplier list with commodities, the folders or records where certificates live, and a written requirement per commodity. The first run is an inventory, and it usually shows how many certificates are already expired or missing. That list is useful on its own, before any chasing starts.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.