Digital products
Traide supports digital goods as first-class catalog citizens on the same multivendor rails as physical goods. Digital lines flow through per-seller suborders, commissions, payouts, and the double-entry financial engine exactly like physical lines — there is no separate "digital checkout" or side-channel. What changes is fulfillment: for the file-based goods this page covers, a paid line produces a secure, expiring download link, an email to the buyer, and a durable entitlement recording what the customer owns.
This page covers modelling, upload, delivery, and reading delivery state for file-based digital goods. The companion pages: Entitlements & refunds covers the ownership ledger, the customer library, refund-driven revocation, and webhooks; License keys, codes & gift cards covers the per-unit credential kinds — pools, reveal, the verification API, and the refund flip. The operator-facing walkthrough lives in the user guide: Digital products.
How digital products are modelled
Every product template, product, and variant carries a fulfillment kind:
enum FulfillmentKind {
SHIPMENT
DIGITAL_FILE
SERVICE
LICENSE_KEY
CODE
GIFT_CARD
TICKET
}
SHIPMENT— physical goods (the default).DIGITAL_FILE— delivered as a downloadable file. This kind drives everything on this page.SERVICE— non-shippable service lines. No delivery automation runs for this kind today.LICENSE_KEY/CODE/GIFT_CARD— per-unit secret credentials: every unit sold is a distinct key with its own lifecycle and entitlement, delivered by reveal rather than download. Covered in License keys, codes & gift cards; marketplaces enable them explicitly viaenabledFulfillmentKinds.TICKET— event tickets. Like the key kinds, a marketplace enables it viaenabledFulfillmentKinds.
The kind waterfalls: setting it on a product template provides the default for products created under it, and a product's kind provides the default for its variants. Because the kind lives at the variant level, one product can sell a digital and a physical variant side by side (an ebook and a paperback under the same product).
The legacy booleans isDigital and isShippingRequired are still populated for compatibility, derived from the kind. When branching on product behavior, read fulfillmentKind, not the booleans — the kind is the typed source of truth, and on order lines it is snapshotted at purchase time while the booleans on catalog objects can change afterwards.
Which kinds a marketplace accepts is controlled by MarketplaceConfiguration.enabledFulfillmentKinds. If a kind is not enabled for the marketplace, catalog writes using it are rejected.