Trade-In & Exchange Program

When trade-in beats outright buyback

Trade-in makes sense when you are *replacing* hardware and want the residual value applied as credit against the new or refurbished purchase rather than taken as a separate SGD settlement. If you are simply retiring assets with no replacement, outright buyback is cleaner — cash hits the bank instead of credit hitting a procurement balance. Mixed fleets often split: current-generation gear trades in against the refresh, end-of-life gear goes to buyback or recycling, and a small tail goes to destruction. We will tell you the split per asset line at scoping.

What qualifies for trade-in credit

Working enterprise hardware with residual secondary-market demand — servers (Dell PowerEdge, HPE ProLiant, Cisco UCS, Lenovo ThinkSystem, Supermicro), enterprise storage (NetApp FAS/AFF, Dell EMC PowerStore/Unity, Pure, HPE), networking (Cisco Catalyst/Nexus, Arista, Juniper, Aruba, Fortinet, Palo Alto), and AI/GPU compute (NVIDIA H100/A100/L40, AMD Instinct, current-gen workstation GPUs). Laptops and desktops also trade in when the fleet is recent enough that secondary-market demand exists. Units are graded on working condition, configuration, generation, and completeness (caddies, rails, PSUs, OEM-original peripherals). Non-working or obsolete gear is routed to recycling, not credited.

How trade-in value is calculated

Credit is priced against the current secondary refurb market for the specific make, model, configuration and condition — the same basis as our buyback valuations, not the destruction-first scrap price most OEM trade-in programs apply. Enterprise hardware typically holds residual value for 18–36 months past end-of-warranty under Reuse-First refurb economics; AI accelerators hold value longer because supply is constrained. The valuation methodology is documented per asset so your finance team can reconcile to the GL and procurement can defend the credit to the OEM or distributor accepting it.

Data handling on traded-in units

Every storage-bearing device is sanitised to NIST SP 800-88 Rev. 1 (Purge for working drives; IEEE 2883-2022 firmware Sanitize for SSD/NVMe; DoD 5220.22-M overwrite where the original engagement specified it) before the unit re-enters the remarketing channel. A per-asset Certificate of Destruction is attached to the trade-in manifest. Nothing is resold before sanitisation evidence is recorded. For top-classified material (BFSI board-grade data, government restricted, healthcare PHI on retiring hosts) we route to physical destruction at 6mm / 2mm / 0.5mm particle size, with witness destruction available, and credit only the chassis/components that survive.

The exchange mechanics and timing

Pickup and asset reconciliation happen against the trade-in manifest the same week as the new-equipment delivery, so you do not carry double inventory or extra rack-U. Credit is confirmed on manifest reconciliation (the Maxicom standard timeline documented in your SOW) and applied to the replacement PO via the distributor or directly to the OEM that is fulfilling the new gear. Programme customers run trade-in on a rolling schedule with monthly true-up; one-off refreshes settle on a single SOW. Settlement is net-net in SGD — the credit nets against the new-equipment invoice so finance sees one transaction instead of two.

Edge cases — when NOT to trade in

If the replacement purchase is much smaller than the residual value of the retired fleet, take buyback as cash settlement instead — you should not strand value as unusable credit. If the retiring fleet is vendor-financed and bound for the leasing company at end-of-term, the lessor return takes priority and only the residual non-returnable units trade in. If the new procurement is going to a different OEM and that OEM does not accept third-party trade-in credit, we can still trade in — we then issue the credit as a Maxicom-side discount on a parallel order, or take the same units to buyback. We will say so at scoping if any of these apply.

What you receive

Per-unit valuation report (model, serial, condition, credit value). Sanitisation manifest with per-asset NIST/IEEE Certificate of Destruction. Trade-in settlement statement that nets against the replacement PO. Pickup chain-of-custody record. ESG footprint summary showing diversion-from-landfill and embodied-carbon-recovered estimate for the trade-in cohort — usable in CSRD / ISSB / BRSR / GRI sustainability reports.

Engagement profile and timeline

A typical Maxicom engagement runs through six stages, each documented and signed off before the next begins. Stage 1 — Scoping (1-3 business days): asset list reconciled to physical reality, regulator stack confirmed, witness destruction requirement determined, settlement currency and PO terms agreed. Stage 2 — SOW and pricing (1-2 days): written SGD quote per asset with line-item detail; SOW includes service levels, certificate retention, exception handling, indemnity terms, NDA. Stage 3 — Pickup scheduling (1-5 days): chain-of-custody manifest pre-prepared, vehicle GPS-tracked from pickup, tamper-evident sealed containers on top-classified loads. Stage 4 — Sanitisation and refurbishment (5-14 days): NIST SP 800-88 Rev. 1 Purge or IEEE 2883-2022 firmware Sanitize per media; Reuse-First triage applied per device; per-asset Certificate of Destruction generated; refurb-eligible units routed through trader-channel network. Stage 5 — Settlement (5-7 days): SGD settlement against PO, line-item per asset, net of agreed deductions; ESG metrics report attached. Stage 6 — Quarterly review (programme engagements): Reuse-First reuse rate, compliance attestations, sustainability metrics, exception reporting. Total cycle from signed SOW to settled PO: 14-30 business days for single-event engagements; 30-90 days for multi-site programmes; rolling cadence for multi-year contracts.

Audit defensibility — what regulators actually inspect

Across the four markets we operate in, regulator inspections of ITAD documentation focus on four criteria. First, per-asset granularity: does the certificate name specific drives by serial number, or is it a bulk-job certificate naming only "all drives in batch X"? Bulk certificates are the most common finding and we do not issue them. Second, standard citation: is the sanitisation method named with a specific reference to NIST SP 800-88 Rev. 1 (Clear / Purge / Destroy with technique), IEEE 2883-2022 (Block Erase or Crypto Erase), DoD 5220.22-M where contractually specified? Vague references like "secure wipe" or "industry-standard erasure" fail audit. Third, verification evidence: is there documented evidence the sanitisation actually completed — controller status response, read-back verification, photographic evidence of physical destruction? Vendors that skip verification produce certificates that fail on this field. Fourth, chain-of-custody continuity: does the certificate trace back to the pickup manifest without unsigned gaps in transit, intake, or destruction-stage hand-off? Maxicom certificates pass all four criteria by design across BFSI inspections (RBI in India, OSFI Guideline B-13 in Canada, MAS TRM in Singapore, Central Bank of UAE / DIFC / ADGM in the UAE), government inspections, and healthcare audits since 2015.

Settlement mechanics — currency, PO, payment terms

Settlement is in your reporting currency (SGD) against your purchase order. Payment terms are 7 business days from manifest reconciliation as the Maxicom standard; programme engagements run on milestone-based settlement against the rolling pickup schedule with monthly true-up. Line-item invoicing per asset is standard — your finance team sees exactly what each unit was worth and how the total was computed, with deductions for destruction, logistics, or rework called out explicitly. We do not bundle. We do not surprise-charge. Cross-border settlement (where the engagement spans multiple Maxicom operating regions) is consolidated to your reporting-currency entity through internal Maxicom inter-company arrangements; the customer-facing transaction is single-currency. Where the customer requires invoicing through a specific Maxicom legal entity (Maxicom UAE, Maxicom India, Maxicom Singapore, Maxicom Canada, Maxicom Hong Kong), the SOW is structured accordingly and the GST / VAT / HST / withholding-tax treatment is handled per local tax law.

Where this service fits in your refresh cycle

Most enterprise IT refresh cycles produce predictable retiring volumes — laptop fleets at 3-year cycles, server estates at 5-year cycles, networking at 5-7 year cycles, GPU clusters at 12-18 months under AI workload pressure. Maxicom services attach to those refresh cycles as the disposition workstream: at the back of the refresh, retiring assets flow through Reuse-First triage; at the front of the next cycle, refurbished assets are available through our Refurbished IT Sales pipeline if the customer wants to mix new and refurb procurement. The integration model varies by engagement: single-event services (refresh, decommissioning, M&A divestiture) run as 14-60-day SOWs; programme services (Programme ITAD, Global ITAM) run as multi-year master service agreements with quarterly review cadence. Most BFSI and government engagements move from single-event to programme within 12-18 months as the customer realises the disposition workstream is more efficient under a programme contract than under repeated single-event RFPs.

Reuse-First reuse rate — the disposition KPI that matters

The single most informative disposition KPI is the Reuse-First reuse rate: the percentage of retired tonnage that was refurbished and redeployed (vs destroyed). Across Maxicom engagements, our blended reuse rate for the reported per engagement was 67% — meaning about two-thirds of every retired tonne came back into productive service somewhere in our five-country network rather than being destroyed and recycled. The remaining 33% split between regulator-mandated destruction (top-classified data, encryption key stores, drives that failed Purge verification) at about 22%, and asset classes where refurb is uneconomic (legacy USB flash, optical media, certain consumer-grade peripherals) at about 11%. We report your engagement-specific reuse rate quarterly so you can benchmark against the blended; programme engagements typically improve their reuse rate from year 1 to year 2 as the engagement learns which asset classes hold value. The reuse rate also drives the embodied-carbon-recovered metric flowing to your sustainability committee — every percentage point of reuse rate corresponds to approximately engagement-specific tonnage of CO₂e avoided per 1,000-asset engagement.

Cross-jurisdiction execution — when your engagement spans multiple Maxicom regions

A meaningful portion of our engagements span multiple operating regions — UAE-headquartered enterprises with Indian back-office, Canadian banks with Indian or Singaporean operations, multinational hyperscale tenants with cross-border AI clusters. The cross-jurisdiction model: single SOW with the contracting Maxicom legal entity (typically the entity in your reporting-currency jurisdiction), country leads in each operating region executing locally, programme manager coordinating across, consolidated reporting in your reporting currency, regulatory attestations issued per jurisdiction so each regulator sees a compliant engagement record in their format. Asset routing decisions happen at scoping: where the customer requires sovereign data residency, sanitisation completes in-jurisdiction before any cross-border movement; where cross-border resale is permitted, post-sanitisation refurb routing optimises against the trader-channel network. This is the single most-cited reason BFSI and hyperscale customers consolidate from regional vendor panels to Maxicom — operational simplification at the contract level without losing local-execution depth.

Insurance, indemnity and liability — what the SOW actually covers

Standard Maxicom SOW indemnity covers: gross negligence in sanitisation execution (e.g. drive routed to refurb without completed Purge verification — never seen in 25 years of operations, but contractually covered if it occurred); chain-of-custody breach attributable to Maxicom operators (transit incidents, intake mismatches); errors in the per-asset certificate where the error caused regulator finding. We carry professional indemnity insurance sized to enterprise engagements; cover sheet and policy reference available on NDA at SOW signing. Standard exclusions: customer-side mis-classification at retirement (Maxicom executes against the data classification on the manifest; if the customer mis-classifies, that is the customer's exposure); regulator changes after engagement signing where the SOW does not include a change-management clause; force majeure events. Where the customer requires expanded indemnity (typical for BFSI top-classified engagements), the SOW addendum specifies the extended cover and the cost premium.

Termination, exit and data-portability — what happens if the engagement ends

Standard Maxicom MSAs include: 60-day termination-for-convenience with no penalty, 30-day cure period for material breach, 30-day exit transition with full handover of engagement records to the customer or to a successor vendor in the customer's nominated format. Data-portability: every engagement record (manifest, certificate, settlement invoice, ESG metrics) is exportable in CSV / JSON / PDF / on encrypted physical media. Compliance vault retention continues post-termination for the regulator-required period; certificates remain retrievable on request even after the commercial relationship ends. We do not hold data hostage; we do not gate exit; we do not impose unreasonable transition fees. Where the customer is moving to a new ITAD vendor, we cooperate with the successor on chain-of-custody handover. The exit clause is the single most underrated piece of an MSA — we draft it for clean exit because clean exit is the right answer for both sides.