Service Codes & ITAD Matching: When “Certified Erasure” Means One Thing
The shared catalog of service codes, how Coverage uses them to route trade-in requests, and why “default-on” for compliance and security is the right starting point.
“Certified erasure” means one thing on one ITAD’s quote and another thing on the next ITAD’s quote, and that’s how trade-in customers end up comparing apples and pears. The platform fixes this by maintaining a shared service-code catalog — every ITAD speaks the same vocabulary, so the customer compares like with like.
The catalog
The platform seeds a canonical set of service codes spanning the operational lifecycle: data-erasure variants (NIST 800-88 Clear, Purge, Destroy), shredding (drives, full devices), refurbishment, recycling per material stream, transportation classes, secure pickup, and the compliance + security categories used by trade-in intake. Each code has a human-readable name, a short identifier, and a category. Tenants don’t edit the platform catalog — they activate the codes they offer and override per-tenant pricing on top.
Tenant Coverage
Each tenant configures Coverage at /settings/coverage: the regions they pick up in, the certifications they hold, the service codes they offer at what price level. When a trade-in customer publishes a pickup request — with the location, the device categories, and the service codes they need (e.g., NIST 800-88 Purge + R2v3 transport) — the matching engine finds tenants whose Coverage intersects the request. ITADs that don’t cover the request never see it; ITADs that do cover it bid against each other.
Why default-on for compliance + security
The compliance and security service codes (NIST 800-88, secure-chain-of-custody, regulated-waste-handling, ADISA-conformant) are seeded with default-on for every ITAD that holds the matching certifications. Otherwise tenants have to remember to activate them — and the trade-in customer who sets a compliance requirement gets fewer bids than they should. Default-on means a tenant who is certified shows up in the bid pool by default, with the option to opt out per code.
Versioning
Service codes are versioned at the catalog level. When the platform introduces a new code (a new compliance regime, a new disposal class), existing tenants get the new code in their Coverage UI to activate. Old codes don’t silently change semantics — if a code is replaced, the platform deprecates the old code and migrates active bids forward, with the operator able to review the migration.
Where the code shows up
On the trade-in intake form (the customer picks the codes they need), on the ITAD’s bid (the codes they’ll provide), on the awarded contract (the codes that became the agreement), and on the settlement (the codes that got billed). One vocabulary, all the way through.