Documents: Where the PDFs Actually Live
The documents store, polymorphic linking, storage quotas, and why evidence belongs on records instead of in folder names.
Every ITAD operation generates documents. Contracts, certificates, manifests, BOLs, photo reports, audit reports, evidence bundles. In too many operations those documents live in a shared drive folder called something like "Certificates 2025 FINAL (2)" and the question "where is the certificate for asset X" is answered by searching email. ReVend OS is the alternative.
The polymorphic link
A document in the platform is not free-floating. It is linked to an entity - a company, contact, asset, inbound order, outbound order, settlement, escrow or contract. One document table, many possible parent types. A contract certificate can attach once and surface on the company, the orders under that contract and the settlement derived from it. No duplicate uploads, no scavenger hunt.
Tags
Documents share the universal tagging system with companies and contacts. A "GDPR" tag on a document can sit next to GDPR-tagged contracts and contacts. One taxonomy beats five colored folder rituals.
Storage
Documents, photos, signatures and evidence files live in tenant-isolated Supabase Storage buckets with signed URLs and quota checks. Vercel Blob is used for avatars, not for operational evidence. Storage usage rolls up per tenant, and quota warnings or upload blocks use the same package/limit layer as the rest of billing-ready usage.
Discoverability
/general/documents is the cross-entity browser: filter by tag, linked entity type, date range or uploader. It is useful when "I uploaded that amendment last month" is the whole business question. Beats searching email by an order of magnitude, and email had a very low bar here.