The short version
- One register, one row per certificate — not one per supplier.
- Track four fields beyond the expiry date: scope, facility, product match, renewal owner.
- Set reminders at 90, 60 and 30 days, and start the renewal chase at 90.
- Keep the evidence with the row so an audit is a lookup, not a project.
Why expiry slips
Certificates rarely lapse because nobody cared. They lapse because the date lived in a PDF inside a folder inside an email thread, and the person who knew about it changed role. A register fixes that with boring discipline.
The register fields that matter
- Supplier and facility — the site, not just the brand.
- Issuer and certificate number.
- Scope — the products and categories covered.
- Issue and expiry dates, plus renewal status.
- Product match — which of your SKUs rely on it.
- Owner — who chases renewal.
- Evidence link — the PDF itself.
Set the reminder rhythm
Three touches: 90 days (start the renewal conversation), 60 days (escalate if no reply), 30 days (decide: substitute supplier, hold stock, or accept a documented risk). The 90-day start is the one that saves you, because certification renewals involve site visits and paperwork that suppliers underestimate.
Match scope to SKUs
For each certificate, list the SKUs that depend on it. When a scope changes — new flavour, new line, new facility — you can see in one query which products are now uncovered. This is also the fastest answer to a retailer's due-diligence request.
Keep it audit-ready
An audit-ready file has: the current certificate, the previous one (for continuity), the spec sheet it covers, and a log line for every review. Store it where two people can reach it, and export it before you need it.
Checklist
- One register row per certificate, not per supplier
- Facility and scope recorded, not just the brand
- 90/60/30-day reminders with a named owner
- Every dependent SKU mapped to its certificate
- Previous certificates retained for continuity
- Export path tested before audit season
If you would rather hand this over
AMAN's accountant (Haseb) and researcher (Dalil) keep the register current: certificate expiry and scope tracked, dependent products flagged, renewal requests drafted for your approval. Nothing is sent to a supplier without your yes.
Questions people actually ask
How far ahead should I start a renewal?
Ninety days is a working default. Certification renewals often involve site visits and document collection that suppliers underestimate.
Do I need to keep expired certificates?
Keep them for continuity — auditors and retailers often ask what was in force on a given date. Mark them clearly as expired.
What if a supplier's certificate covers a facility I don't buy from?
Record the mismatch explicitly. It usually means the certificate does not cover your product, and that is exactly the gap an audit finds.