Service Codes & ITAD Matching: When “Certified Erasure” Means One Thing
The tenant service catalog, the Coverage page that decides which pickup requests reach your inbox, and the one rule that does the matching.
“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 narrows that gap with a service catalog every tenant starts from, a Coverage page where each ITAD declares what it offers and where, and a matching rule that only shows a customer’s request to the ITADs that can actually fulfill it.
The catalog
Under /settings/services every tenant has a service catalog seeded with system services across logistics, processing, destruction, remarketing, compliance and financial work. System services cannot be deleted — core flows expect them to exist — but your team can activate or deactivate them and reorder them within a category. On top of that, your team adds custom services: a four-character code, a name, a description, a pricing unit (per unit, per kilogram, per hour or fixed) and a default rate. Deactivating a service that something depends on shows dependency warnings first, because a line in Settings can be quietly holding up contracts, bids, settlements or invoices.
Coverage
Under /sourcing/coverage your organization declares what it can take on: a master switch for accepting pickups, the countries you cover as ISO codes, the certifications you hold, the services you offer — drawn from your active catalog, so an empty catalog means an empty list — a minimum lead time in hours, and a default shortage fee per missing item. The page opens with a plain-language summary that updates as you edit: whether you are live or paused, which countries you receive requests from, and the rule below. Lead time and shortage fee become bid defaults; they save typing, they do not replace reading the request.
The matching rule
A customer’s pickup request appears in your inbox only if the pickup country is one you cover, you hold every certification the request asks for, and you offer every service it asks for. All three, or nothing. Switching accepting pickups off hides new matching requests; bids you already placed and work you already won stay where they are. After you save Coverage, the inbox re-checks it. There is no “default-on” — an ITAD shows up for a compliance requirement because it declared the certification, not because the platform assumed it.
Where the services show up
On the customer’s request, as the services they need. On your bid, as the services you will provide. On the contract, as included services with their rates. And downstream in settlements and invoices, which is why the catalog warns before you deactivate one. One vocabulary from intake to invoice — and the only thing the customer has to compare is the number.