Ask download sellers what their most common support message is and it is rarely about the product. It is some version of "I paid and never got my file" — sent by a buyer whose delivery email is sitting, unread, in a spam folder or a Promotions tab. The file was delivered. The sale completed. And yet, from the buyer's side of the screen, your store took money and sent nothing, and every hour they spend believing that is an hour closer to a refund request or a chargeback. Deliverability sounds like a marketing topic, the province of newsletter senders and cold outreach. For a download seller it is operations: the single email that carries your product has to arrive, be found, and be believed. This is the fix-list, in the order to work it.
First, prove where your delivery email actually lands
You cannot fix placement you have not measured, and your own inbox is the worst test account you own: you have emailed yourself, clicked your own links, and trained your provider to trust your mail. Test like a stranger instead. Keep a small set of seed addresses you control — one each at the big consumer providers your buyers actually use, typically Gmail, Outlook, Yahoo, and an Apple address — and run a real test purchase to each one after any change to your delivery setup, and on a schedule even when nothing changed.
For each seed, record four things: did it arrive at all, how long did it take, which folder or tab it landed in (inbox, Promotions, spam), and whether the download link worked from that mailbox without warnings. Write the results down with dates. Providers change filtering constantly, and a delivery flow that landed in the inbox in spring can drift into Promotions by autumn without you touching anything. The seed log turns "buyers say it is in spam" from a vibe into a before-and-after comparison — and it tells you whether a fix you make below actually moved anything.
Authenticate the domain your delivery comes from
The highest-leverage fix on this list is also the least visible: email authentication. Three DNS records decide whether receiving servers treat your mail as genuinely yours. SPF says which servers are allowed to send for your domain. DKIM adds a cryptographic signature your domain vouches for. DMARC tells receivers what to do when the first two do not line up, and gives you reports about who is sending as you. In plain terms: without them, your delivery email is a stranger claiming to be your store; with them, it is your store showing ID. Spam filters weigh that difference heavily, and some providers now treat missing authentication as a reason to filter or reject outright.
Two practical notes. First, if your delivery or store platform sends mail on your behalf, follow its specific instructions for connecting your domain — the records go in your domain's DNS, they are a one-time setup, and the platform's status page will usually confirm when they verify. Sending from your own authenticated domain, rather than the platform's shared one, also means your reputation is yours: a shared sending domain inherits the behaviour of everyone else on it. Second, if authentication is not offered or not possible in your setup, that is a genuine limitation worth knowing about your tool — weigh it when you choose where delivery lives, and lean harder on the second-path section below. Either way, never send delivery mail from a free consumer address with your store's name typed into the display field; that mismatch is exactly what filters are built to catch.
Be recognizable in the three seconds before the click
A delivery email that arrives but is not recognized has failed almost as completely as one in spam. Buyers scan a crowded inbox for something they expect, from a sender they remember, about a purchase they just made. Make all three obvious. The from-name should be the store name the buyer saw at checkout — not a person's first name alone, not a generic "Support" or "No-reply," and not a clever rebrand they have never seen. Keep it identical on every message you send; recognition compounds.
The subject line has one job: name the purchase. "Your [product name] download" beats "Your order is complete," which beats anything cute, urgent, or shouty. Avoid the classic filter-bait while you are at it — excessive capitals, strings of exclamation marks, and deceptive prefixes like fake "Re:" or "Fwd:" lines that pretend the message is part of an existing conversation. And set expectations before the email is even sent: on the confirmation page, tell the buyer the sender name and subject to look for, and that the message should arrive within a couple of minutes. A buyer who knows what to search for finds a Promotions-tab email in seconds; a buyer who does not know it exists files a ticket instead.
Build the email itself so filters and buyers both pass it
Content is the third factor, after authentication and recognition. A few habits cover most of it. Send a proper plain-text version alongside the formatted one; legitimate senders do, and its absence is a small but real negative signal. Keep the download as a link, not a large attachment — big attachments trip size limits and attachment scanning, and a link lets you control expiry, limits, and revocation afterwards anyway. Use the real destination address rather than a consumer URL shortener, whose shared reputation you do not control and which security filters treat with suspicion. Keep the design light: an email that is one large image with the link inside it hides your only important element from text scanning, from buyers with images off, and from anyone using a screen reader.
Then make the content itself boringly clear. The buyer's name or the product name near the top, one obvious download button or link, how long the link lasts and how many downloads it allows, and one line saying what to do if it expires. Everything else — cross-sells, social links, review requests — is weight on the one message that cannot afford to be ignored. If you want to market, do it in a later message that is allowed to land in Promotions without costing you a customer.
Never let the inbox be the only delivery path
Even a perfect deliverability setup loses some emails: a mistyped address at checkout, a corporate filter that quarantines first-time senders, a mailbox that is simply full. So the professional setup treats the email as the primary path, never the only one. The confirmation page immediately after payment should carry the download itself, or a clearly labelled button to it, for the buyer who is still standing there — the moment of highest intent and lowest confusion in the whole transaction. Where your setup offers an order or account page, make sure a buyer can get back to their file from it later, and say so in the email itself: "You can always re-download from your order page" turns a lost email from a crisis into a shrug.
Keep the receipt and the delivery as separate messages, too. A payment receipt from your payment provider and a delivery email from your store can fail independently; if one is filtered, the other still proves the purchase and tells the buyer what to look for. Finally, make re-delivery cheap for yourself: a one-click resend from the order record, not a manual hunt through dashboards. You will use it often enough that its cost, in minutes and in temper, is a real line item.
When a buyer says it never arrived, work a sequence — not a hunch
The "never arrived" message deserves a fixed routine, because the causes are few and each has a different fix. First, check your delivery record for that order: was the email sent, and when? A send that never happened is a different problem from one that was filtered. Second, confirm the address on the order against the one the buyer is writing from — a checkout typo (a transposed letter, an old work address) explains a large share of these tickets, and the fix is resending to the correct address after verifying the order is theirs. Third, give the buyer one precise search to run — the exact subject line and sender name — rather than a vague "check spam," and ask them to mark it "not spam" if they find it there; that signal helps their provider place your future mail, including their next purchase.
Fourth, resend once, promptly, and say that you have. If the resend also vanishes, suspect a strict filter on their side — common with corporate and school addresses — and offer the alternate path: the order page, or delivery to a personal address they provide. What not to do: argue that your system shows it sent. It may well have been; sending and arriving are different events, and the buyer is reporting their inbox, not your log. Log every one of these tickets with its cause. A month of causes is a diagnosis — mostly typos means a checkout problem, mostly one provider means a placement problem — and it tells you which section of this list to revisit next.
The fix-list, in order
- [ ] Built a seed set (Gmail, Outlook, Yahoo, Apple) and logged where a real test delivery lands, with dates — and re-test after any setup change
- [ ] SPF, DKIM, and DMARC set up and verified for the domain your delivery email is sent from; never sending delivery mail as a free consumer address
- [ ] From-name is the store name buyers saw at checkout, identical on every message; subject names the product ("Your [product] download")
- [ ] Confirmation page tells buyers the sender and subject to expect, and roughly when
- [ ] Email carries a plain-text version, a link (not a big attachment) to the real destination, one obvious download action, and its expiry/limit terms
- [ ] A second delivery path exists and is signposted: download on the confirmation page and/or an order page, with receipt and delivery as separate messages
- [ ] Resending a delivery is one click from the order record
- [ ] "Never arrived" tickets follow a sequence — verify send, check address typos, give the exact search, resend once, offer the alternate path — and causes are logged
Authenticate it, make it recognizable, and give it a second path home. Do those three, and the spam folder stops being where your product goes to disappear.
Closing note: I build FileFreight, a small flat-rate delivery tool for download sellers — secure expiring download links, per-buyer PDF stamping, licence keys with revocation, and refund auto-revoke, with buyers paying through your own Stripe account. Honest caveats: it is new and small; it does not handle taxes or merchant-of-record duties; there is no automatic importer yet (I migrate your catalogue free, by hand, for the first 20 sellers); it is not a Shopify app; and it is delivery-only, with no marketplace and no buyer library. Everything above is seller practice that works with any delivery setup. Pro is $19/mo at 0% per sale; the free tier takes 5% per sale.
Top comments (0)