Breaking the mold: a Dual-Channel Self-Publishing Experience
When you're self-publishing your first book, the advice you get falls into two camps: “Go exclusive with KDP Select for the promotional tools” or “Go wide for…
When you’re self-publishing your first book, the advice you get falls into two camps: “Go exclusive with KDP Select for the promotional tools” or “Go wide for maximum reach.” Like most binary choices in publishing, both are wrong — or at least incomplete.
I’m launching Traffic Engineer on November 7th through what I call dual-channel direct distribution: IngramSpark for print and expanded ebook reach, plus KDP for Amazon’s ebook ecosystem. Not KDP Select. Not exclusive. Direct.
Here’s the systems-thinking breakdown of why this matters.
The Problem with KDP Select
KDP Select gives you access to Kindle Unlimited, Countdown Deals, and Free Book Promotions. In exchange, Amazon requires 90-day exclusivity — your ebook can’t be sold anywhere else.
The pitch is simple: “Amazon is 70% of the market anyway. Why not take the promotional tools?”
Here’s why that’s a trap:
- You’re optimizing for Amazon’s distribution algorithm, not your audience’s reading preferences.
- Kindle Unlimited pays authors based on pages read, not books sold. You get roughly $0.004 per page. For a 300-page memoir, that’s about $1.20 per read-through. Compare that to a $9.99 ebook sold direct, where you keep 70% ($6.99).
The math only works if KU visibility drives dramatically higher read volume. For authors building a long-term brand, it’s a dependency trap.
Why I Chose IngramSpark for Print
IngramSpark isn’t sexy. It’s infrastructure. Here’s what it gives me:
- Global print-on-demand distribution to 40,000+ retailers and libraries. Libraries are discovery engines for memoir.
- Returnability. Bookstores won’t stock a book they can’t return. IngramSpark offers returnability; Amazon’s KDP doesn’t.
- Professional credibility. IngramSpark is what traditional publishers use.
The cost? $49 to upload, plus $25 per revision. I’m paying for reach, not convenience.
Why I’m Using StreetLib for Amazon Ebooks (Not KDP Select)
I’m not uploading my ebook to KDP at all. StreetLib distributes to Amazon Kindle as part of their standard package — along with Apple Books, Kobo, Barnes & Noble, and Google Play.
This means I can reach Amazon’s 70% ebook market share without locking myself into their ecosystem.
What I get through StreetLib:
- Distribution to Amazon Kindle + all other major ebook retailers.
- Single upload, multiple platforms.
- One royalty dashboard.
- No exclusivity requirements.
What I give up:
- Kindle Unlimited revenue.
- Countdown Deals and Free Book Promotions.
- Direct control over Amazon listing metadata.
I’d rather own the relationship across all platforms. A reader who buys my book at full price is signaling intent. They’re more likely to join my email list and follow the PureTome journey.
The Dual-Channel Architecture
Print Distribution:
- IngramSpark → Bookstores, libraries, international retailers, Amazon (backup).
- Amazon KDP Print → Amazon buyers who prefer Prime shipping (primary).
Ebook Distribution:
- StreetLib → Amazon Kindle, Apple Books, Kobo, B&N, Google Play, international platforms.
Why both KDP Print AND IngramSpark for print? Amazon buyers expect Prime shipping. IngramSpark’s Amazon integration works, but fulfillment is slower. By uploading to both, I give Amazon buyers instant gratification while maintaining wide distribution everywhere else.
The Critical Sequencing Issue: Upload to KDP Print First
Here’s the trap: If IngramSpark hits Amazon’s catalog first, Amazon treats your book as “already available” through a third party. When you then try to upload to KDP Print, Amazon may block your upload or require a manual override that takes days.
The Correct Upload Sequence:
- Step 1: Upload Print to KDP First. Establish KDP’s primacy for print in Amazon’s system.
- Step 2: Upload Print to IngramSpark. Use the SAME ISBN. Enable Amazon distribution.
- Step 3: Upload Ebook to StreetLib. Use a DIFFERENT ISBN.
The Bottom Line
KDP Select optimizes for Amazon’s algorithm. Wide distribution optimizes for audience ownership.
I’m not anti-Amazon. I’m pro-optionality. Traffic Engineer is the story of what happens when you put all your dependency in one system and it fails. I’m not making that mistake with my publishing strategy.
Get new essays by email
Memoir craft, AI architecture, and system design. No spam, unsubscribe anytime.