A Rillor forward contract is, mechanically, a delivery obligation between a buyer, an OEM, and Rillor as the platform. The buyer commits to take physical delivery of a specific SKU at a specific facility in a specific delivery month, at a fixed price. The OEM commits to ship. Rillor sits in the middle: it KYC's both sides, captures the end-customer-of-record for the OEM's NVIDIA business unit, holds the deposit in an independent escrow agent's account, and orchestrates the handoff.
Standardization is the load-bearing decision. Every contract on Rillor uses the same six fields: SKU, quantity, delivery month, deposit percentage, settlement currency, channel-of-record. No bespoke language per buyer. This is what makes the contracts comparable, and ultimately, transferable.
Settlement is physical. At the delivery date, the OEM ships the hardware to the receiving address on the contract. Rillor confirms receipt with the buyer and releases the balance of payment from escrow. If the buyer defaults pre-delivery, Rillor can re-list the contract to its verified buyer book; the deposit covers the OEM's storage and cancellation cost per the contract terms. If the OEM fails to ship, the deposit is returned to the buyer in full and Rillor sources from a secondary supplier if possible.
This piece walks every clause and every contingency. If you're a partner conversation reading this, that's intentional. Pre-launch, the standard contract is short. We want it to stay that way.