How to sell digital products: delivery, refunds, piracy
Selling templates, courses and presets: delivery, licensing, refunds and chargebacks, and how much piracy is worth worrying about.
The short version
- The file is easy; everything hard about digital products moves into delivery, licensing, refunds and sharing.
- Delivery has to be instant, re-downloadable and correct the first time. Expiring links and manual sending are where refund requests come from.
- Publish formats, versions, what is included and a real preview. Most refunds are mismatched expectations, and preventing them is the highest-leverage fix available.
- Your files will be shared, and chasing individual downloaders buys back almost nothing. Sell updates, support and community — the parts that cannot be copied.
- AI drafts the sales page, delivery setup and pre-sale answers, but it will overstate compatibility and cannot decide your license tiers or make the product.
The first time a customer emails to say the download link expired before they could get to a laptop, you learn what selling digital products is actually about. Not the file. The twenty minutes after payment.
How to sell digital products, stated honestly: the product is easy to duplicate and costs nothing to deliver, so every hard problem moves somewhere else — into delivery reliability, license terms, refunds, and the fact that nothing stops a buyer from sharing it. Get those four right and the margin is the best in commerce. Get them wrong and you spend your week resending files.
What people actually buy, and what each one costs you after the sale
| Product | Where it sits on price | Where the effort goes | Support load |
|---|---|---|---|
| Templates (docs, spreadsheets, design files) | Low to mid | Making it genuinely editable; documentation | Medium: "how do I change the font" |
| Presets and brushes | Low | Version compatibility | High: "this doesn't work in my version" |
| Ebooks and guides | Low | Writing and layout | Low |
| Courses | Highest of these | Recording, editing, structure | High: access, progress, refunds |
| Audio and stock assets | Low, sold in volume | Volume and licensing clarity | Low, if the license is clear |
| Notion and Airtable systems | Mid | Duplication instructions | Medium: setup help |
Set your own numbers; the pattern worth taking is that the cheaper the product, the more buyers you need and the less support each one can absorb. A cheap preset pack with a 15-minute support conversation attached is a loss.
Pick the format by what you can document, not just what you can make. The product is the file plus the instructions, and the instructions are where most digital products quietly fail.
Delivery is the whole experience
Everything a customer feels about buying from you happens in the minute after payment. Three requirements:
Instant. The file arrives on the confirmation page and in an email, without you touching anything. A "we'll send it within 24 hours" line turns a purchase into an anxious wait and generates a support ticket.
Re-downloadable. Buyers lose files, change laptops, and read email on phones. A link that expires in an hour is a refund waiting to happen. Give a generous window or a permanent account-based download.
Correct the first time. Named, versioned files (brand-kit-v3.zip, not final_FINAL.zip), one README at the top of the archive explaining what is inside and what software it needs, and no mystery nesting.
mAutomate handles this side for digital product creators: payment clears, protected download links are issued automatically, and the buyer has the file before they have left the page.
One honest note on "protected": a protected link controls who gets the first download. It does not control what happens to the file afterwards. Nothing does. More on that below.
For courses, the equivalent decisions are drip versus everything-at-once, and whether access is lifetime. Lifetime access is a promise about your hosting bill, so if you make it, mean it.
Licensing, in plain language
Most buyers never read a license. The ones who do are about to use your work commercially, and they are the sale you want. Write it short and in plain words rather than borrowing boilerplate you have not read either.
A workable structure for most creators:
- Personal use. One person, their own projects, no resale.
- Commercial use. Use it in paid client work or in products you sell, still not resold as-is.
- Extended or team. More than one seat, or redistribution inside a product, priced accordingly.
Then state the three things that cause disputes. Can they resell or redistribute the file as it is? Almost always no. Can they use it for a client's project? Say yes or no explicitly. How many people or devices does one purchase cover?
Put the summary on the product page, above the detailed terms. A buyer who cannot tell whether they are allowed to use your template for a client will not ask. They will leave.
The purpose of a license on a $29 download is not to win a lawsuit. It is to make the honest majority confident they are doing the right thing.
Refunds and chargebacks
Digital goods create a real asymmetry: the buyer keeps the file after the refund. That makes some sellers write "all sales final," which is both a conversion problem and, in several jurisdictions, unenforceable against consumer rights.
A policy that holds up:
Be clear, not harsh. State what is refundable and when. "If it is not what you expected, reply within 14 days and we'll refund it" costs you a handful of refunds and buys the confidence that closes many more sales.
Prevent instead of litigating. Most refund requests are mismatched expectations. File formats, software versions, page counts, what is not included, a real preview — publish all of it and the request rate drops. This is the highest-leverage fix here.
Refund fast, and look for the pattern. A begrudged refund becomes a chargeback and a bad review; a fast one sometimes becomes a repeat buyer. If five people ask for the same reason, the product page is lying somewhere.
Chargebacks are a different animal: processor disputes that cost a fee on top of the refunded amount and count against you. Your defense is unglamorous records — what was bought, when, when it was downloaded, the terms shown at checkout, the support thread. Keep them. A clear store name on the card statement also prevents the most common dispute of all, a buyer who does not recognize the charge.
Piracy, and exactly how much to care
Your files will be shared. A popular template ends up in a group chat and eventually on a forum. This is certain, and the correct amount of energy to spend preventing it is close to zero.
The reasoning is unsentimental. Most people downloading a pirated copy were never going to pay. Chasing them costs hours and buys back almost nothing. Meanwhile every anti-piracy measure strong enough to matter — device locks, aggressive DRM, phone-home activation — punishes paying customers, who then write to you when it breaks.
What is actually worth doing:
- Sell updates, not just files. A buyer who gets new versions has a reason to be a buyer. A pirated copy is frozen the day it was copied.
- Attach the things that cannot be copied. Support, a community, feedback on their work, office hours. This is why courses survive piracy better than ebooks.
- Keep a light watermark or buyer reference in PDFs. Cheap, invisible to honest buyers, and makes casual redistribution traceable.
- Send takedowns only for the cases that cost you real money — someone reselling your work as theirs, or a site ranking for your product name. Not individual downloaders.
Treat it as a cost of the format, like breakage in shipping. Spend the hours on the next product instead.
Pricing anchors for things with no cost of goods
There is no base cost to mark up, which is freeing and paralyzing in equal measure. Four anchors that help:
What it replaces. A template that saves a freelancer six hours is priced against six hours of their rate, not against other templates.
Your tiers against each other. Three options — a single item, a bundle, and an extended license or a version with support — let the buyer choose a level rather than decide yes or no. The middle option usually sells, and the top one makes the middle look reasonable.
The shape of your audience. A thousand-person list selling a cheap product is a different business from a hundred-person list selling an expensive one. Both work. Picking one tells you what to build.
The support load at that price. If buyers at the bottom of your range need hand-holding, raise the price or remove the need for help. Those are the only two moves.
Free versions earn their keep when they create a reason to return — a sample chapter, one template from the set — and not when they are the whole product with a nag screen.
What the AI drafts, and where it gets it wrong
The sales page for a download has to overcome doubt fast, and that is drafting work: the what-is-included list, the format and compatibility details, the FAQ that answers objections before they become refund requests, the launch emails, the social posts. mAutomate's AI writes those from a brief about the product, sets up the secure instant delivery, and answers pre-sale questions about formats and licensing on your site so the 11pm question does not cost you the sale. Nothing goes out until you approve it.
What it gets wrong is predictable and worth watching for. It will overstate compatibility — claiming a preset works in versions you have not tested — which is how refunds begin. It will write confident benefit copy about a file it has never opened. It cannot decide your license tiers, because those are commercial choices about who your customers are. It will not tell you that your product is too thin to charge for; only buyers do that.
And it cannot make the thing. The template, the course, the judgment about what is genuinely worth $79 to the person reading — that is yours.
If you want the store side handled, every mAutomate plan starts with a 14-day free trial and no card required, from $29 a month on Launch. The digital product creators page covers the delivery and licensing setup specifically, and if part of what you sell is your time rather than your files, online store for coaches covers that half.
Questions people ask
How should a digital product be delivered after purchase?
Automatically, the moment payment clears, on the confirmation page and by email, with a link the buyer can use again later. Buyers lose files and change devices, so short expiry windows create refund requests. Name and version the files clearly and include a README explaining what is inside and what software it needs.
Should I offer refunds on digital downloads?
A clear, reasonable policy converts better than 'all sales final', which also conflicts with consumer rights in several places. State what is refundable and within how long, refund quickly when asked, and treat repeated requests for the same reason as a signal that the product page is overpromising somewhere.
How do I stop people pirating my digital products?
You cannot, and the effort is better spent elsewhere. Measures strong enough to work — device locks, aggressive DRM, activation checks — mostly punish paying customers. Sell ongoing updates, support and community instead, keep a light buyer reference in PDFs, and send takedowns only where someone is reselling your work or outranking you.
What license should I give buyers of a template or preset?
Something short and readable, in three tiers: personal use, commercial use for paid client work, and an extended or team license for multiple seats or redistribution. Then answer the three questions that cause disputes — can they resell the file, can they use it for a client, and how many people does one purchase cover.
- Digital products
- Pricing
- Refunds
Ready to start your store?
Let the AI build, market, and run it — you ship the product.
Get started free