The Trade-In Module: How A Pickup Request Becomes A Pickup

The trade-in module is the customer-facing surface where corporate IT teams publish a pickup request, certified ITADs bid on it, the customer awards one, and the awarded work becomes real operations. It runs in its own app shell with its own auth, its own RLS, and its own UI - separate from the operator app where work is done, but wired into it through Coverage matching, the bid pipeline, and the notifications layer.

Customer-facing portal

A customer signs up through the trade-in flow. The portal has its own shell: dashboard, requests, pickups, invoices, certificates, notifications and settings. Each surface is scoped to the customer's account. The customer sees their own request and proof, not somebody else's clear-out from a different building.

Publishing a request

A multi-step wizard captures contact and company, device-level item detail, logistics, preferred timing, compliance and security requirements, then review. Submit, and the request lands in the matching pipeline.

The bid round

The matching engine finds ITAD tenants whose coverage matches the region, certifications and service requirements. Each eligible ITAD sees the request in the Sourcing inbox with the compliance and security requirements inline. They submit a structured bid: amount, services, SLA, validity and notes. Pre-award identity stays masked so the bid round is about the work, not brand karaoke.

The award

The customer compares bids by price, certifications, trust score and SLA. Awarding a bid reveals the winning ITAD's identity, clones the customer into that ITAD tenant's CRM where needed, and creates the operational handoff into Core: collection plus inbound order, ready for planning and receiving.

Pickup, processing and proof

The awarded ITAD coordinates the pickup, receives the goods, tests, grades, erases where needed, and publishes certificates back to the customer portal as they become available. Pickup invoicing and operational finance belong to the ITAD's Core records. ReVend tracks the handoff and proof; the ITAD team still does the physical work. Software remains bad at carrying pallets.

Smart relaxation

If a request gets zero bids - too narrow a region, too strict a service set, too aggressive a timing window - the portal can suggest safe relaxations. A customer who sees silence and gets no help leaves. A customer who sees "drop this one requirement and four ITADs can bid" has somewhere to go.