The Certifications Catalog: Why R2v3 and B Corp Live in the Same List
How the certifications catalog works, why it covers the niche ones too, and what verified status actually does.
ITAD is one of the few industries where the difference between two companies is mostly which audit they passed last. R2v3, NAID AAA, ISO 14001, e-Stewards, B Corp, ADISA, RIOS, WEEELABEX — the procurement officer at a major bank cares about which of these you hold, because their compliance team will ask, and they don’t want to be the team that picked an ITAD partner who couldn’t produce the certificate when it mattered.
The certifications catalog ships with the major standards built in, each with a category, the issuing body, the scope, the typical renewal period in months and a website. It covers the ones every ITAD has heard of. It also covers the niche ones — because if your warehouse holds a regional certification that isn’t on the global list, it still matters when it matters.
What’s in a certification record
For each certification a company holds: the standard (linked to the catalog row), the certificate number, the issue date, the expiry date, the scope, and the certificate document itself stored as evidence. The catalog row says what the standard is; the company record says that this company holds it, until when, and where the proof is.
Verified status
A certification record can be marked verified by platform staff who have actually looked at the certificate document and confirmed it matches the catalog standard; the review queue lives under /admin/certifications/pending. Verified certifications carry weight in the trust score (up to 10 bonus points, weighted by the catalog category). Unverified certifications appear on the company profile but don’t contribute to the score — because anyone can claim a certification, and the difference between “claimed” and “verified” is the whole point of having a catalog.
When a verification is granted or a verified certificate expires, a database trigger recomputes the trust score. So a seller who lets R2v3 lapse drops in the rankings the same week the cert expires, not the next time someone manually pokes the score.
The catalog and the pickup request
The trade-in request wizard asks the customer which certifications the bidding ITAD must hold, from a short fixed list: R2v3, e-Stewards, NAID AAA, ISO 14001, ISO 27001 and WEEELABEX. Those codes mirror the certification tags an ITAD sets on its Sourcing coverage, and a request only reaches inboxes where every required tag is present. The catalog is the long list for profiles and tenders; the wizard list is the short list that gates matching. Six codes are enough to route a pickup. A hundred would only produce longer forms and the same six answers.
The niche ones
Catalog rows are tenant-owned, so an organization can add its own entries for standards nobody else has heard of — a national e-waste scheme, ISO 27001 with a specific Annex A scope — alongside the system rows. They appear on the profile and in tender responses. Because procurement teams ask about them, and “we have it but it’s not in the platform” is a worse answer than “yes, here it is.”