Using KDP and IngramSpark Together: ISBNs and Distribution

What each platform will do in your plan

Start with a one-sentence plan: “We will manage our Amazon print edition directly through KDP and make the same edition available through IngramSpark’s wholesale network.” Then name the person responsible for maintaining each account. That decision is more useful than uploading everywhere and resolving conflicts afterward.

IngramSpark’s official FAQs permit this combination when you own the ISBN and advise leaving KDP Expanded Distribution unselected. Wholesale availability gives buyers an ordering route; it does not establish that a shop will carry the book.

A second platform also means another proof, another set of production requirements and another record to maintain. If you cannot name the additional channel you need, first finish a reliable release through the channel you already understand.

Can you use the same ISBN on KDP and IngramSpark?

For the same print edition, an ISBN assigned to your publishing entity can support this setup. A platform-supplied identifier has different restrictions. KDP’s ISBN guidance says its free ISBN is usable only on KDP; it also requires the registered title, author and imprint details to match.

IngramSpark describes the restriction on its supplied ISBN in its FAQs. ISBN allocation differs by country; use the relevant national agency rather than assuming a US process applies everywhere.

An identifier should express the publishing decision. Adding another ISBN simply to bypass an error can create listings that readers cannot easily distinguish. Record what each identifier represents before asking a production supplier to use it.

Leave KDP Expanded Distribution off for this shared setup

KDP Expanded Distribution is a specific program, separate from offering your paperback on Amazon. KDP’s eligibility rules say the paperback’s ISBN must not already have been submitted for distribution through another service. This supports treating the wholesale route as a deliberate choice.

If your book is already enrolled, stop before creating a competing wholesale setup. Record the ISBN and current program status, then use the platforms’ support processes to clarify removal or any transfer needed. Keep confirmation with your release notes. Do not assume an unchecked box instantly updates every downstream catalogue.

Keep one approved book record and separate production files

Create a master record containing the title, subtitle, contributors, imprint, language, edition, binding, trim size and ISBN. Add the approved description and the date of your last change. Copy from this record when setting up either platform.

Keep the print product consistent, but check each platform’s file requirements. Identical-looking upload screens do not establish identical cover dimensions. IngramSpark’s print file instructions require a complete interior PDF and a separate complete cover PDF, and recommend its cover template generator.

For example, your file register might say “Paperback interior: revision 08; KDP cover: revision 05; IngramSpark cover: revision 05.” The cover files can use their respective templates while representing the same approved book. Avoid filenames such as “final-final-new,” which hide which version someone actually reviewed.

Use the print and EPUB formatting checklist to separate production checks. After a correction, verify the newly exported file and update both records if the change applies to both.

A fictional paperback decision, worked through

Consider an invented project, The Neighborhood Repair Journal, by fictional author Robin Ellis. Robin wants a paperback for Amazon readers and a wholesale ordering route for independent shops. This example demonstrates a decision process; it is not a Greenfield client or a sales result.

1. Define one edition. Robin records the paperback’s title, author, binding and intended imprint before starting either upload.
2. Confirm the identifier. The paperback uses an ISBN assigned to Robin’s imprint. A later hardcover will have a different identifier.
3. Assign the channels. The release notes name direct KDP publication and IngramSpark wholesale distribution, with KDP Expanded Distribution left off.
4. Approve both proofs. Robin checks page order, text near the binding, cover alignment and barcode placement in copies produced through both routes.
5. Inspect the listings. Robin saves each retailer URL and checks the displayed edition, description and ordering information before announcing availability.

The decision record helps Robin report a mismatch precisely: which ISBN, which listing and what is wrong. It cannot guarantee a bookseller order or dictate Amazon’s supply decisions.

KDP Select is a separate ebook decision

Do not confuse Expanded Distribution with KDP Select. Select is the optional Kindle ebook program. KDP’s current enrollment guidance sets ebook exclusivity conditions during enrollment while allowing print distribution elsewhere.

Using IngramSpark for your paperback therefore does not automatically prevent Select enrollment. Sending the ebook through additional retail channels is a different decision. Read the current terms, including permitted exceptions, before distributing that ebook elsewhere or placing a downloadable copy on your website. Keep the enrollment dates in the ebook’s own record.

Check the release before announcing it

• Both accounts use the approved title, author, imprint and correct edition identifier.
• Files and physical proofs have an identifiable revision and recorded approval.
• The distribution choices match the written plan.
• You understand the selected wholesale terms and the consequences of returns.
• Reader links reach the intended format, and someone owns future corrections.

Once the setup is dependable, use the separate guide to approaching bookstores. If you need help coordinating editions, files and account responsibilities, explore publishing support and request a distribution scope for your book.

Questions about using both platforms