# Digital delivery

URL: /systems/commerce-and-fulfillment/digital-delivery · Id: `page:systems/commerce-and-fulfillment/digital-delivery`

> How a paid Order delivers files at once, keeps each download open from the receipt, and checks a buyer's right to run what they bought.

A [Digital product](/products/templates/digital-product) sells files once, such as an ebook, a template pack or a plugin. Each paid [Order](/business/nouns/order) grants an [Entitlement](/business/nouns/entitlement) to its [Files](/business/nouns/file), so delivery happens the moment payment clears.

## What the buyer gets
The [Offer](/business/nouns/offer) names what it delivers: one Entitlement to `File.get` on each File it sells. When `Order.paid` fires, the buyer gets an email with the download, and the receipt opens it again whenever they come back.

No second record holds the right to download. The Entitlement is the right, and [Billing](/systems/billing) keeps it with the Order that granted it. A support agent answers "where is my download" from the same record.

## Checking the right to run
A plugin or a desktop app checks that its buyer may run it. [`Entitlement.check`](/business/nouns/entitlement/check) answers whether a [Customer](/business/nouns/customer) may call a [Verb](/business/nouns/verb) now. An app that calls the [Startup](/business/nouns/startup)'s API checks the same Entitlement.

An app that runs offline needs a key it can verify without calling. A license key on the Entitlement is the shape proposed, with three asks:

| You say | Status |
| --- | --- |
| `Give each buyer a license key` | `planned` |
| `Revoke this buyer's key` | `planned` |
| `Is this key valid` | `planned` |

## Next
- [Digital product](/products/templates/digital-product): the template, its default Offer and its [Systems](/business/nouns/system).
- [Billing](/systems/billing): Orders, Entitlements and refunds.