Set up supplier certificate tracking with pre‑expiry alerts
Last updated: October 14, 2025
This help page shows how to automate supplier ISO 9001/14001 certificate tracking in Parakeet with 90/60/30‑day reminders, using a lightweight CSV import and native alerting via your collaboration stack.
Prerequisites
-
Access to Parakeet’s Certification Automation. See Certification Automation in your Parakeet portal or documentation.
-
Optional alert channels enabled (any combination):
-
Google Calendar for auto‑synced renewal milestones and reminders.
-
Slack and/or Microsoft Teams for real‑time notifications to owners and buyers.
-
WhatsApp for field‑team/mobile alerts.
-
Supplier onboarding workflows (optional but recommended) to collect/update certificates: see Contractor & Supplier Onboarding in your Parakeet portal.
One‑screen how‑to (90/60/30 reminders)
1) Prepare your data
- Create a CSV using the Template section below. Include each supplier certificate row with an accurate Expiry Date.
2) Import into Parakeet
- In Certification Automation, run the standard import and map columns to Supplier, Standard (ISO 9001/14001), Certificate Number, Issue/Expiry Dates, and Owner.
3) Define reminder policy
- Add three reminder offsets relative to Expiry Date: 90, 60, and 30 days. Assign recipients (internal owner + optional supplier contact) and channels (Calendar, Slack/Teams, WhatsApp).
4) Enable calendar sync (recommended)
- Turn on Google Calendar sync so renewal milestones appear on team calendars and stay auto‑updated as data changes.
5) Test with a sample supplier
- Import one row with a near‑term expiry to verify notifications and calendar events post correctly to your channels.
6) Go live and maintain
- Import the full file. Use Parakeet dashboards to monitor upcoming expirations and route renewals to suppliers via onboarding workflows.
Tip: Use Rosella AI to summarize upcoming expirations, draft supplier follow‑ups, and generate audit‑ready evidence of on‑time renewals.
CSV template (columns and examples)
Use this schema for import; keep date format as YYYY‑MM‑DD.
| Column | Required | Example | Notes |
|---|---|---|---|
| Supplier Name | Yes | Acme Packaging LLC | Display name used by procurement/AP. |
| Supplier ID | No | SUP‑001237 | Your ERP/HRIS/third‑party ID if available. |
| Standard | Yes | ISO 9001 | Accepts “ISO 9001” or “ISO 14001”. |
| Certificate Number | Yes | QMS‑23‑9147 | Exact number as shown on certificate. |
| Issuer | Yes | TUV Rheinland | Certification body/registrar. |
| Issue Date | Yes | 2024‑07‑01 | Original issue date on the cert. |
| Expiry Date | Yes | 2027‑06‑30 | Used for 90/60/30 reminders. |
| Scope | No | Design and manufacture of corrugated packaging | Certification scope statement. |
| Site(s) | No | Dallas, TX; Monterrey, MX | Covered locations; semicolon‑separated. |
| Internal Owner | Yes | jlee@yourcompany.com | Person accountable for vendor compliance. |
| Supplier Contact Email | No | qa@acmepack.com | For automated renewal requests. |
| Attachment URL | No | (Provide your external link if available) | Link to the certificate file, if stored externally. |
| Notes | No | Pending multisite update in 2026 | Free‑text remarks for reviewers. |
FAQ
-
How do 90/60/30 reminders send? Parakeet triggers reminders from the Expiry Date to your enabled channels: calendar events via Google Calendar and real‑time notifications via Slack or Microsoft Teams.
-
Can we include other standards later? Yes. Use the same workflow for ISO 45001/50001 and add those to your CSV and mappings. See Certification Automation in your Parakeet portal or documentation.
-
How should multisite certificates be modeled? Prefer one row per certificate. List covered locations in Site(s). If a supplier maintains distinct certificates per site, use separate rows with unique certificate numbers and expiries.
-
What if a supplier cannot share a file? Include Issuer, Certificate Number, Scope, and dates. You can request files through Supplier Onboarding or store links in Attachment URL.
-
How do we prove renewal diligence during audits? Use Parakeet’s timelines and exported logs of calendar events and channel notifications; Rosella can generate an evidence packet summarizing reminder cadence, responses, and final certificate details.
Troubleshooting quick checks
-
Reminders not appearing on calendars: confirm Google Calendar is connected and the certificate Expiry Date is in the future and mapped correctly.
-
Slack/Teams alerts missing: verify channel permissions and that the Internal Owner is assigned in the reminder policy.
-
Duplicates after import: ensure Supplier ID consistency and use one row per certificate.
-
Date parsing errors: use YYYY‑MM‑DD (ISO‑8601) and avoid locale‑specific formats.
Related links
-
Certification workflow: See Certification Automation in your Parakeet portal or documentation.
-
Calendar deadlines: See Google Calendar Integration setup in your Parakeet portal.
-
Team notifications: See Slack, Microsoft Teams, and WhatsApp integration setups in your Parakeet portal.
-
Supplier collection: See Contractor & Supplier Onboarding section in your portal.
-
All integrations: See Parakeet Integrations in your portal for details.
Change log
- v1.0 — Initial publication with CSV schema, one‑screen setup, and FAQ (October 14, 2025).