Contracts: Where the Money Gets Decided
Service contracts, pricing models, SLAs, and why "we'll figure it out later" is the most expensive sentence in ITAD.
A contract in ReVend OS defines the rules of engagement between you and a client. What services you provide, how you price them, what the SLAs are, and how the money flows when everything is done. It's the document that settles arguments before they start — assuming someone read it.
Why contracts matter more than you think
In ITAD, every client is different. One pays per device. Another pays per kilo. A third insists on a revenue share model that took four meetings to negotiate and still confuses everyone in accounting. Without a contract in the system, every settlement becomes a debate.
ReVend OS contracts attach to companies and flow through to inbound orders, settlements, and invoices. Change the pricing on a contract, and every future settlement reflects it. No spreadsheet. No "I thought we agreed on €4.50 per unit." The contract said €4.50. The system calculated €4.50. Discussion over.
Pricing models
ReVend OS supports six pricing models out of the box (see contracts-pricing-models for the operational deep-dive):
Per-unit: A fixed price per device, regardless of what it is. Simple. Common for data destruction contracts where the client doesn't care about residual value.
Per-kilo: Priced by weight. Common for recycling contracts and commodity-grade equipment that nobody is going to test individually.
Fixed-purchase: A lump sum for a defined lot. Common for "we'll take everything in your storage room for €X" deals where the buyer commits to a number and the lot is settled in one move.
Revenue-share: The client gets a percentage of the resale value, with a configurable split. The ITAD keeps the rest. This is where the grading really matters — the difference between Grade A and Grade B is the difference between a happy client and an awkward phone call.
Lease-return: Per-unit base with chargeback rules from the contract's damage matrix and missing-device penalties. The settlement calculates itself when receiving completes.
Hybrid: A contract can combine the models per service line — lease returns at per-unit, ad-hoc collections at per-kilo, all under the same contract row.
SLAs
Each contract can define SLA targets: processing time, reporting cadence, pickup windows. The system tracks actual performance against these targets. When you're three days from an SLA breach, the dashboard tells you. When you've already breached it, the dashboard tells you that too — with slightly more urgency.