Delivery

Delivery is what a buyer on Telegram actually gets the moment their order is marked paid. Open a product and go to its Delivery tab: a Digital Goods product has exactly one primary delivery method, chosen from three kinds — whichever you pick is what fires automatically after payment.

How delivery works

Three primary kinds: Message, Folder, or Inventory. Switching a product’s kind clears any configuration that assumed a different one — there is no merge between kinds.

Message delivery

Send one or more message blocks directly after payment. Each block can carry text, a single attached file (image, document, or other resource from your libraries), inline buttons, or a combination — sent in order. Limit forwarding and saving is a per-delivery toggle that tells Telegram to block buyers from forwarding or saving the messages (screenshots are still possible — Telegram has no way to prevent those).

Folder delivery

Buyers receive everything in a folder from one of your libraries, including future updates — delivery re-reads the folder rather than snapshotting it at purchase time, so anything you add later becomes available to buyers who already own the product. Requires at least one library with at least one folder before you can select it.

Redemption codes

Consume one unique item per purchase — a code or license key. Paste one item per line, or import a CSV (the first non-empty column of each row is used). Even if two buyers order at the same moment, each paid order claims its own line — nobody is ever handed a code someone else already received. A low-stock banner appears on the Delivery tab once inventory runs low.

Reusing resources

Every file you deliver, attach to a message, or send in a broadcast lives in Resources — team-scoped, reusable anywhere your team sends content.

A library is backed by a Telegram channel you own: create a channel, add your connected bot as an administrator, then point a library at it. Files land on Telegram’s side through your own channel — you own the channel and all content, and the library keeps working even if you stop using GramBase. Inside a library, folders organize files like a file explorer; one folder per library can be the current upload target, so new uploads land without picking a destination each time. Tags are team-level labels (Manage Tags) you apply to resources and folders for filtering, with a batch action to add, remove, or overwrite tags across a selection.

A resource isn’t tied to one product — the same file can back a delivery, sit in the message-block editor used for broadcasts, and serve as a product’s cover (a video cover’s thumbnail mirrors from Telegram automatically). Because a resource can be referenced from more than one place, deleting one a product depends on as its cover is refused with a list of the products still using it — you resolve those first, rather than GramBase silently breaking a product’s cover out from under you.

Delivery records and re-delivery

An order’s detail view has a collapsible delivery log listing every delivery attempt — status, a short message, and for a failure, the error text — newest first. Independent of the log, delivery resolves to one of three states: pending, sent, or error. A confirmed payment doesn’t by itself mean the buyer received anything.

When delivery is error, the order detail offers a retry — available only on a paid order whose delivery actually failed; a delivery that’s still pending or already sent can’t be retried, so you can’t accidentally re-send something that already went out. A retry is queued, not instant, and clicking it again while one is already in progress doesn’t start a second one. Retrying never creates a new payment event or charges the buyer again.