A digital product refund policy explains when buyers can request their money back, how you review the request, and what happens to their access afterward. For downloadable files, the last part matters: returning a payment does not retrieve a PDF already saved on someone’s device.
Write the policy around what your store can actually do. Separate refund eligibility from help with a missing email, and separate returning money from stopping future downloads. Then test those decisions before publishing the promise.
This guide is for sellers of files such as templates, e-books, and artwork. It is operational guidance, not legal advice or a ready-to-publish legal policy. Runner AI publishes it; the Runner example describes native digital delivery for eligible Runner-backed stores, not every connected platform.
What should a digital product refund policy include?
A useful policy lets a buyer understand the offer before paying and lets support handle a request without inventing rules afterward.
- Product scope. Name the downloads or bundles covered. Check that the files, formats, and license match the product page.
- Request process. Give buyers a contact route and the minimum order information to include. Confirm someone monitors that route.
- Eligibility. Explain how you handle duplicate purchases, unusable files, and change-of-mind requests. Check applicable law and platform requirements.
- Time limits. State any request window and when it starts. Support must be able to identify that date.
- Resolution. Describe the troubleshooting, replacement, or eligible refund options you can actually provide.
- Future access. Explain what buyers can download after a full or partial refund. Verify that your access controls can enforce the outcome.
Do not promise an immediate bank credit because your dashboard records a refund immediately. Payment processing and customer-visible timing are separate. Use the connected provider’s current guidance when explaining what happens next.
The broader guide to selling digital downloads covers choosing and testing a delivery system. This policy checklist starts where that launch work leaves off: what you promise when a purchase needs resolving.
Is a no-refund policy enough?
“Digital products cannot be returned” explains a practical limitation. It does not, by itself, establish which refund rules apply to your business.
Do not copy another seller’s final-sale wording and assume it settles your obligations. Your location, the buyer’s location, the type of content, and the circumstances of the sale can matter. Have qualified counsel review the rules for the markets you serve.
For a concrete jurisdiction-specific example, GOV.UK’s online-selling guidance describes requirements for digital downloads, including agreement to immediate delivery and acknowledgement of the effect on cancellation rights. That is UK guidance, not a worldwide rule or a checkbox that this article claims Runner supplies.
Keep a route for technical problems even if you restrict voluntary change-of-mind refunds. A buyer who cannot open the file needs a response that addresses the problem, not an automatic accusation that they are trying to keep it for free.
Match each request to the problem
Use these examples as a planning worksheet, not as mandatory refund outcomes.
- “The email never arrived.” Check the recipient address, email result, and whether access was created. Correct the address or resend access when appropriate.
- “The file will not open.” Check the delivered file, format, required software, and reported error. Define when to troubleshoot, supply a working file, or review refund eligibility.
- “I bought it twice.” Check both order records and which purchase should remain usable. Review the duplicate payment while preserving the intended purchase.
- “I only need a price adjustment.” Confirm the approved amount and whether the buyer keeps the product. A partial refund should not unintentionally end access.
- “One part of the bundle is wrong.” Identify the affected files and what the buyer retains. Do not promise file-level controls your platform cannot provide.
A download event is evidence about access, not proof that a file was useful or compatible. Nor is a sent email proof that the buyer saw it. Read the customer report alongside the available records.
Decide about money and future downloads separately
Consider a hypothetical $24 template purchase. You approve a $6 goodwill adjustment because one optional worksheet needed correction. If the customer keeps the template, cutting off all downloads would contradict the resolution.
Now consider a full refund where the agreed outcome ends future access. Record both decisions: the refunded payment amount and the access that should stop. Do not infer the second from the first.
For partial refunds, ask whether your platform can restrict the particular benefit involved. If it only offers an order-wide action, do not write a policy promising selective file revocation. Likewise, deleting a shared product file to resolve one buyer’s request can affect other buyers; use the controls intended for the individual purchase.
The order-level refund guide explains the financial scope of a refund. A digital-access decision answers a different question: what can this buyer request from the delivery system next?
What the Runner example shows
Runner’s native digital-delivery flow makes the access choice explicit. Its digital-products guide documents a choice to keep or revoke the buyer’s access when refunding an order with digital items. A refund recorded elsewhere leaves an access decision for staff rather than silently choosing an outcome.
The same guide includes a recorded purchase and refund demonstration. It shows a refund with access revoked. Use the guide for availability, prerequisites, and the current controls; this article does not replace those instructions.
Revoking access stops new downloads through that system. It cannot erase files already downloaded, and a recently issued file link can remain usable briefly. Your policy should not describe revocation as retrieving a file or preventing every copy.
If you are evaluating a store for this workflow, the digital-product storefront overview covers Runner’s offering. Confirm eligibility and test your actual delivery path before committing to a buyer-facing access promise.
Turn the decisions into a policy brief
Before asking someone to draft legal wording, fill in the operational facts. This is a brief for review, not a policy to paste into checkout.
We sell [files and formats] for use with [required software or devices]. Buyers receive them through [delivery method]. Refund requests go to [monitored contact route] with [minimum order information]. We review [request categories] under [approved eligibility rules and applicable requirements]. If a refund is approved, future access [stays available or ends, as specified for that resolution]. We explain payment timing using [provider guidance]. Technical delivery problems go through [support process].
Do not fill the gaps with defaults you have not approved. In particular, a seven-day window, “no exceptions,” and “lifetime access” are business and legal commitments, not harmless template text.
Check the policy against a test purchase
Use an authorized test environment and a controlled buyer inbox. Do not create a live charge merely to complete this checklist.
- Compare the product page, policy, and delivery email. They should name the same files, compatibility requirements, and support route.
- Confirm that the buyer receives usable access, not only a successful payment screen.
- Test a missing-email support request without requiring another purchase.
- Test an approved refund that keeps access, then verify the payment record and download availability separately.
- Test an approved refund that revokes access, then verify that new download requests are refused.
- Check how a refund made outside the store reaches the delivery record and who resolves any remaining access decision.
- Write a sample customer response that states the amount, payment status, and future access without promising a bank settlement date you cannot verify.
Common policy questions
Can I refund a digital product after it has been downloaded?
A completed download does not technically prevent a payment refund. Eligibility depends on the applicable rules and the purchase circumstances. Decide future access separately, recognizing that a downloaded copy cannot be recalled.
Does a refund automatically cancel download access?
Do not assume so. Payment and delivery systems can have separate controls. Verify the platform’s behavior, including refunds made directly through a payment provider, and record the intended access outcome.
Should a partial refund revoke everything?
Not automatically. A price adjustment may leave the buyer entitled to the entire product. A bundle complaint may involve only part of the purchase. Define the resolution first, then confirm that the platform can implement it without removing access the buyer should retain.
Where should buyers find the policy?
Make it easy to read before purchase and to find again when seeking help. Keep the product page, checkout references, delivery email, and support replies consistent. Changing a page after a complaint is not a substitute for knowing what the buyer was told when they paid.
Start with one product and one policy your support process can carry out. A useful refund policy leaves neither the buyer nor the next support person guessing about the money or the files.