Most buyer email for a digital download store is not angry. It is confused, a little embarrassed, and written at the moment someone cannot find a file they paid for. The fastest way to answer it well is to have written the answer before the question arrives.
Below are six templates worth saving in your help desk, your notes app, or a text expander. Each one is short on purpose. Replace the bracketed placeholders, keep your own voice in the first and last lines, and delete anything that does not match how your store actually works. No dark patterns anywhere in these: no fake urgency, no guilt, no hiding the refund option, no pretending a policy says something it does not.
1. "I never got my download" — the recovery reply
Subject: Your [PRODUCT NAME] download
Hi [FIRST NAME] — thanks for reaching out, and sorry for the confusion. Your download was sent to [EMAIL USED AT CHECKOUT] a few minutes after your order on [ORDER DATE]. It sometimes lands in spam or promotions, so a quick search for "[PRODUCT NAME]" in that inbox usually finds it.
If it is not there, reply to this email and I will re-send it to the address you are writing from. No need to buy again — your purchase is on record here.
Why it works: it states the delivery happened without accusing the buyer of missing it, gives one concrete search step, and offers the re-send before they have to ask twice.
2. Download link expired / reissue reply
Subject: Fresh download link for [PRODUCT NAME]
Hi [FIRST NAME] — no problem at all, links expire after [TIME PERIOD] to keep files from being shared publicly. Here is a fresh link to [PRODUCT NAME]: [NEW LINK]
This one is good for [TIME PERIOD / NUMBER OF DOWNLOADS]. If you can, save the file itself somewhere you will find it again — the saved file never expires, only the link does.
Why it works: it explains why links expire in one plain sentence (sharing protection, not punishment), and it teaches the difference between the link and the file, which prevents the same ticket next month.
3. Refund policy wording + decline-with-care reply
Put the policy where buyers see it before checkout, in words like these:
Our refund policy: If [PRODUCT NAME] does not work as described, or you cannot get it running after we have tried to help, email us within [NUMBER] days of purchase for a full refund. Because this is a downloadable product you keep a copy of, we do not offer refunds for changed minds, accidental purchases after download, or buying the wrong item by mistake when the product page described it accurately. If your situation is unusual, email us anyway — we read every case.
And when you have to decline, decline like a person:
Subject: Re: Refund request for [PRODUCT NAME]
Hi [FIRST NAME] — I have read your email twice, and I understand this is not the answer you wanted. I cannot refund this one because [SPECIFIC, TRUE REASON — for example: the file was downloaded on (DATE) and the product page lists (REQUIREMENT) clearly]. That falls under the refund policy shown at checkout, which I have pasted below so you do not have to take my word for it.
What I can do: [GENUINE ALTERNATIVE — a different format, help getting it working, a credit toward (OTHER PRODUCT)]. If none of that helps, I understand, and thank you for trying [PRODUCT NAME].
Why it works: a specific true reason, the policy quoted rather than waved at, and a real alternative offered without caving on the boundary. Never invent a reason, and never decline by template alone — change the middle paragraph for every case.
4. License-key explanation for buyers
Software, fonts, plugins, and other key-gated products confuse buyers who have never seen a key before. Send this with the delivery email, not after they ask:
Subject: Your license key for [PRODUCT NAME]
Hi [FIRST NAME] — your license key is: [LICENSE KEY]
A license key is simply proof that your copy is yours. Paste it into [WHERE THE KEY GOES — for example: Settings → License inside the app] the first time you open [PRODUCT NAME]. You can use it on [NUMBER] devices at the same time. Moving to a new computer? Deactivate the old one first, or email us and we will reset it for you.
Keep this email — if you ever reinstall, you will need the key again.
Why it works: it answers the three questions every key buyer actually has — what is this, where does it go, and what happens when I change machines — before support hears from them.
5. Product-update announcement to past buyers
Subject: [PRODUCT NAME] updated — your new version is free
Hi [FIRST NAME] — you are getting this because you bought [PRODUCT NAME]. Version [NEW VERSION] is out today, and it is a free update for you.
What changed: [ONE OR TWO PLAIN-LANGUAGE CHANGES — what is fixed or added, and why it matters to the buyer]. What did not change: [ANYTHING BUYERS WORRY ABOUT — their files, settings, or key still work].
Get it here: [DOWNLOAD LINK]. Your existing license key and download account work as before. If anything looks wrong, reply to this email.
Why it works: past buyers are told clearly that the update is free, what actually changed, and that nothing they rely on broke. One email per meaningful update — batch the small fixes.
6. Pre-order delay note
Subject: [PRODUCT NAME] is running [TIME PERIOD] late — here is your choice
Hi [FIRST NAME] — you pre-ordered [PRODUCT NAME], due on [ORIGINAL DATE]. I am writing because it will now be ready on [NEW DATE]. The honest reason: [SPECIFIC, TRUE REASON, ONE SENTENCE].
You do not need to do anything if you are happy to wait. If you would rather not, reply to this email and I will refund your pre-order in full, no questions and no forms. When it ships, you will get the download email at this address, and pre-order buyers still receive [PRE-ORDER BONUS, IF ANY].
Why it works: it arrives before the missed date becomes a broken promise, it gives a real new date or says plainly that there is not one yet, and the refund option is one reply away — not buried, not conditional.
A note on where these come from
These templates are general seller practice; they work with any delivery setup that gives each buyer their own link and, where relevant, their own key. They were written alongside FileFreight, a small, new delivery-only tool — honest caveats: it is not a merchant of record and does not handle sales tax or VAT, there is no automatic importer yet (the first 20 sellers get a free white-glove migration instead), and it is not a Shopify app. If your current tool already handles delivery well, keep it and just take the templates — that is the part most sellers are actually missing.
Top comments (0)