Upload and deliver ebooks
Ebook products deliver a paid file to the buyer after payment is approved. This path is different from link delivery, member access, or MemberKit integrations.
Use this guide when the product promise is a downloadable or accessible ebook file rather than ongoing membership access.
When ebook delivery fits
| Use ebook delivery when | Use another delivery method when |
|---|---|
| The buyer receives a book or guide file | Access is in an external members area. See external members callback URLs. |
| Delivery is complete after file access | The product is a recurring subscription |
| Support can verify one file per purchase | Access depends on a course platform such as MemberKit |
| Checkout copy can promise a digital file | Buyers need multiple labeled URLs. See link delivery. |
What ebook delivery affects
| Area | Impact |
|---|---|
| Product setup | File attachment and product type must match ebook delivery |
| Product approval | Approval details should describe the ebook accurately |
| Pricing | Usually one-time, but confirm the payment model before launch |
| Checkout | Copy must match file format and delivery promise |
| Sales | Support confirms approved sale before access troubleshooting |
| Refunds | Digital file delivery often needs a clear refund policy |
Setup workflow
- Confirm the correct business workspace.
[Screenshot: App header showing the active business name and workspace switcher.]
- Open Products and start a New product.
[Screenshot: Products list page with New product button visible.]
- On What will you sell?, select Ebook.
[Screenshot: Product type selector — Ebook tile selected; subtitle reads "PDF or ePub file."]
- Create the product or open an existing ebook product.
[Screenshot: Ebook product opened — product type Ebook confirmed in header or settings.]
- Confirm the product type matches ebook delivery.
[Screenshot: Product type field — Ebook selected and delivery set to file upload.]
- Complete product details and product approval details and sales page information.
[Screenshot: Ebook product details and approval fields — name, category, sales page URL, and offer description.]
- Upload the ebook file in the product ebook area.
[Screenshot: Ebook upload area — file attached with PDF or ePub filename visible.]
- Confirm the file is attached, saved, and is the final buyer version.
[Screenshot: Ebook file saved — filename and upload status confirmed on product.]
- Create the plan and offer for the ebook.
[Screenshot: One-time plan form connected to the ebook product.]
- Build and publish checkout with accurate delivery copy.
[Screenshot: Checkout builder preview for ebook — file format and access promise visible.]
- Run a test purchase through the first-sale workflow.
[Screenshot: Test checkout — ebook purchase payment submitted.]
- Confirm the buyer can access the ebook after approval.
[Screenshot: Post-purchase ebook download or access screen for the test buyer.]
- Document support steps for access and refund requests.
[Screenshot: Support playbook — ebook access troubleshooting and refund escalation steps.]
What to verify before launch
| Check | Why it matters |
|---|---|
| Uploaded file is the final version | Buyers should not receive draft or wrong editions |
| File format matches checkout promise | Reduces support tickets after purchase |
| Checkout is published | Unpublished drafts cause layout issues |
| Product is active and approved | Inactive products break live links |
| Refund policy is documented | Digital delivery disputes are common |
| Support knows where buyers find the file | See buyer access troubleshooting |
Replacing or updating an ebook file
| Situation | Recommended approach |
|---|---|
| Typo or formatting fix before launch | Replace file before traffic starts |
| New edition after launch | Review impact on existing buyers and support policy |
| Buyer cannot access current file | Investigate sale status before re-uploading |
| Product promise changed materially | Update checkout and consider offer versioning |
Best practices
- Upload the final file before sharing checkout links with paid traffic.
- Keep checkout copy specific about file type, access method, and refund terms.
- Test access on mobile and desktop after the first approved sale.
- Pair ebook setup with payment methods buyers will actually use.
- Train support to check Sales status before blaming delivery.
Common mistakes
- Attaching the wrong file version to a live product.
- Promising instant access when payment is still incomplete. See incomplete payments.
- Using ebook delivery for a product that should use member access.
- Changing the live file without telling support.
- Launching before product approval or checkout publish is complete.
FAQ
Can I replace the ebook file later?
Yes, but review impact on existing buyers and support before changing a live file. Document whether past buyers should receive the new version.
What if the buyer paid but cannot access the ebook?
Start with troubleshoot buyer access after purchase and confirm the sale is approved in Sales.
Should ebooks use one-time or subscription pricing?
Most ebooks are one-time. If access should renew, review one-time vs subscription pricing before launch.
Do I need webhooks for ebook delivery?
Not for basic file delivery inside AtomicPay. Use webhooks only if external systems also need the sale event.