Contracts & Pricing Models: Six Ways to Get Paid

Contracts in ITAD are not standard. One client pays per device. Another pays per kilo, because they’re recycling. A third wants a revenue share on resold equipment. A fourth has a hybrid where lease-returns are per-unit but ad-hoc collections are per-kilo. The platform supports all of them as first-class pricing models, not as workarounds in a notes field.

Six pricing models

Per-unit: price × quantity. Simple. Used for buybacks, refurbished sales, structured procurement.

Per-kilo: price × weight. Used for recycling and bulk material flows where the unit count doesn’t reflect the value.

Fixed-purchase: lump sum for a defined lot. Used for "we’ll take everything in your storage room for €X."

Revenue-share: a percentage of resale revenue, with a configurable split. Used when the client retains residual ownership and wants upside on what the platform actually sells the equipment for.

Lease-return: per-unit base with chargeback rules. The contract carries a damage matrix (€ per defect code), a missing-device penalty (€ per missing serial against the manifest), and a residual-value floor. The settlement calculates itself when receiving completes.

Hybrid: a contract can combine models per service line. Lease returns at per-unit, ad-hoc collections at per-kilo, all under the same contract row.

Services and SLAs

A contract bundles services (each with its own pricing model and SLA). A service might be "lease return processing" with a 14-day SLA from delivery to certification, or "secure shredding" with a 48-hour SLA from arrival to certificate-issued. The SLA is monitored — if an asset crosses the deadline, it surfaces on the dashboard SLA widget before the client calls to ask.

Certifications scope

A contract can require specific certifications (R2v3, NAID AAA, ISO 14001) — and the platform won’t let the contract sign if the tenant doesn’t hold them as verified. Prevents the embarrassing day when a client audits and discovers the certs weren’t there.