When I published my memoir-workbook book, one line item on my launch checklist looked deceptively small: “deliver the PDF after payment.” I assumed I’d just email it to people myself. Then I thought about doing that at 2 a.m., on weekends, for buyers in different time zones, indefinitely — and I changed my mind fast.

This post walks through exactly what I set up, why I chose the path I did, and the alternatives I evaluated but didn’t use, so you can pick the right one for your own product instead of guessing.

Why “just email it manually” breaks down

The math is unforgiving. Every manual delivery is a moment where a paying customer is sitting there, refreshing their inbox, wondering if the purchase actually worked. Delay that even by a few hours and you get refund requests, chargebacks, and one-star reviews that have nothing to do with the quality of the PDF itself — they’re reviews of the waiting.

The flow I built

At a high level, every automated-delivery setup — mine included — reduces to the same four-step handoff:

Where products differ is which box does the work. Some all-in-one platforms collapse all four boxes into one product. Others make you wire boxes 2–4 together yourself. I ended up using the first kind, and I’ll explain why.

Option 1: An all-in-one digital storefront (what I actually used)

I distributed my book through Selar, a platform built specifically for selling digital products. The delivery mechanism was built in: I uploaded the finished PDF once, set the price, and every successful payment automatically unlocked a download link on the confirmation page and sent one by email — no extra automation layer required.

What I liked about this approach:

• Zero automation to maintain. No webhook, no third-party workflow tool sitting between payment and delivery that could silently fail.
• Built-in file hosting. The PDF lives on the platform’s storage; I never had to think about link expiry or bandwidth.
• Fraud and chargeback handling are the platform’s problem, not mine.

The tradeoff: less flexibility. If I wanted to trigger something else on purchase (add the buyer to a specific email sequence, notify me on Slack, log the sale to a spreadsheet), I’d need to bolt on automation anyway — which brings us to option 2.

Option 2: Stripe or PayPal + an automation tool

If you’re selling through your own site rather than a marketplace, the standard pattern is: payment processor fires a webhook → an automation tool catches it → the automation tool emails the file.

What the Zapier wiring looks like

Conceptually, the setup is three steps inside the automation tool:

1. Trigger: “New successful payment” in Stripe.
2. Optional filter: only continue if the product purchased matches this specific PDF (useful if you sell more than one thing).
3. Action: send an email (via Gmail, or the automation tool’s own mailer) with the PDF attached or linked, using the buyer’s email captured at checkout.

This route is more flexible than an all-in-one storefront, but every extra link in the chain is a place things can quietly break — an expired API connection, a renamed file that orphans the shared link, a filter condition that’s slightly too strict and silently drops real customers.

Option 3: Gumroad, Payhip, or Podia

These sit between the two options above — dedicated digital-product storefronts, similar in spirit to Selar, each with automatic file delivery built in and no separate automation required.

What I’d tell someone setting this up today

• Test the failure path, not just the happy path. Before launch, I ran a real test purchase and deliberately checked: does the download link work on a phone? Does the email land in spam? Is the PDF the final, proofed version and not a draft I forgot to swap out?
• Have a manual backup. Automation fails eventually. I kept the final PDF in a personal cloud folder so that if a buyer emailed saying delivery didn’t arrive, I could send it myself within minutes — no scrambling to find the file.
• Match the tool to your sales volume, not your ambition. An all-in-one storefront was the right call for a single book with no upsell chain. If I were running a multi-product catalog with segmented email sequences, I’d lean toward the Stripe + automation route for the extra control.
• Watch file size. My finished PDF ran to 163 pages with embedded diagrams. Some automation tools choke on large attachments — hosting the file and emailing a link is more reliable than emailing the PDF directly once you’re past a few megabytes.