SELF-PUBLISHING INTELLIGENCE · SP08 · PUBLISH

Publish the Book as a Controlled Release System.

SP07 gives you production-ready files. SP08 decides where those files go, who controls each distribution feed, what identifiers and metadata define each edition, what the economics and rights settings are, and whether the live result actually matches the plan.

Self-publishing is not the same thing as uploading to Amazon. Amazon KDP can be one important branch. Retailer-direct publishing, aggregators, wholesale/POD distribution, owned direct sales, and hybrid combinations are different release architectures with different trade-offs.

1. Decide what the release needs to accomplish

Choose the publishing objective before choosing a service. A book built for maximum retailer reach may use a different architecture than a book built for simple Amazon-first release, bookstore/library availability, international access, direct customer relationships, premium bundles, or maximum operational control.

Record the priority markets, formats, required channels, excluded channels, tolerance for administration, appetite for exclusivity, and importance of owned-direct sales.

2. Choose the channel architecture

3. Name the distributor-of-record for every destination

“Wide” is not a destination map. For each format and destination, record which service is responsible for delivering that edition there. Then record which other services must exclude that destination.

4. Build the identifier strategy by format and edition

Record whether an identifier is required, what identifier is being used, where it came from, which publisher/imprint is attached to it, and whether it is portable beyond the service that supplied it.

Do not assume one ISBN covers every format. Do not assume a platform-provided ISBN or other identifier is portable. Country, format, edition, retailer, printer, and distributor requirements can differ, so confirm the current rule for the actual route being used.

5. Maintain one canonical metadata master

Create one approved source for the information that defines the release, then map it into each platform instead of rewriting from memory.

• Title, subtitle, series, edition, author, contributors, imprint/publisher, language, and publication date.
• Primary reader, book type, genre/subject, positioning, description, categories/subjects, search phrases, and audience fields.
• Formats, navigation/accessibility information, illustrations, reading-order information, and audio contributors where relevant.
• Territorial rights, public-domain status where relevant, AI-use disclosure inputs, contributor credits, permissions, and other required disclosures.

The cover, copyright/rights page, files, retailer metadata, series information, and contributor identity should agree. Platform descriptions should not invent promises or claims that the book does not support.

6. Translate SP02 positioning into categories and search fields

SP02 established the reader and market neighborhood. SP08 translates that decision into the categories, subjects, keywords, search phrases, age/grade fields, and other discovery metadata actually supported by each platform.

Do not distort the book to chase a category. The purpose of metadata is to improve findability while preserving an accurate reader promise.

7. Build pricing from economics, not folklore

Record pricing by format, channel, currency, manufacturing cost, wholesale discount where relevant, returns exposure, aggregator/platform fees, expected royalty or net, direct-fulfillment/payment costs, promotional options, and target margin.

There is no universal “best” book price. A sound price depends on positioning, format, cost, channel rules, territory, competitive context, and business objective. Platform price bands and royalty thresholds can change, so keep them in a living currentness layer rather than baking old numbers into the permanent curriculum.

8. Map rights and territories into actual channel settings

SP06 established the rights evidence and unresolved risk. SP08 converts that into operational publishing choices: territories controlled, territories excluded, third-party restrictions, public-domain territory differences, distributor settings, and any exclusivity program under consideration.

Do not select worldwide rights because it is convenient. Select only the rights the project can responsibly claim.

9. Treat exclusivity as a business decision

Exclusivity can affect where an edition may be sold or distributed. Record the program, format, territories, start/end conditions, conflicting channels that must be removed or excluded, migration requirements, and the official terms checked immediately before enrollment.

Do not let a retailer checkbox silently rewrite a deliberate wide or direct-sales strategy.

10. Treat direct sales as a real operating channel

An owned storefront can strengthen the reader relationship and support bundles or companion products, but “sell direct” is not just adding a buy button. Document digital delivery, print fulfillment, inventory/POD arrangements, taxes, shipping, support, refunds/returns, customer privacy/data, pricing, and the relationship between the direct edition and retailer editions.

Specialist: Give Your Work a Storefront →

11. Recheck every chosen platform before submission

Immediately before submission, verify the current official requirements for the service you are actually using. Check accepted files, covers, identifiers, metadata fields, category rules, price/royalty rules, territories, exclusivity, AI disclosures, accessibility fields, distribution destinations/exclusions, account/tax/banking requirements, locked fields, review rules, and post-publication change limits.

12. Preserve a submission record

For every platform/service submission, record the account, format, edition/version, exact file and cover, identifier, metadata version, price, territories, categories, search fields, accessibility information, AI/provenance disclosures, exclusivity, destinations, submission date, status, platform item ID, live URL, warnings, resolutions, and evidence.

This becomes the answer to a future question that otherwise causes chaos: What exactly did we upload, where, and under which settings?

13. Audit the live listing

Approval is not the end of SP08. Check the actual reader-facing result: title, author, edition, cover, format linking, price, description, sample, series/author links, availability, targeted wholesale/library reach, direct-store delivery, and duplicate/conflicting listings.

Record the live URLs and store IDs. Correct the evidence in front of you instead of assuming the upload screen became the storefront perfectly.

14. Control updates, migrations and new editions

Classify later changes: metadata correction, price change, file correction, production replacement, rights/territory change, channel change, new format, revised edition, new edition, distributor migration, delist/relist, or other.

Then identify affected platforms, identifiers, feeds, files, links, and whether the change reopens SP06 or SP07. A distributor migration requires explicit feed control; a substantive new edition can require much more than replacing one file.

SP08 readiness gate

• The chosen release architecture matches the project objective.
• Distributor-of-record is explicit for every important destination and format.
• Duplicate/overlapping feeds have been prevented or resolved.
• Identifier and imprint decisions are documented by format/edition.
• A canonical metadata master exists and matches the production package.
• Category/search-field choices trace back to SP02 positioning.
• Pricing economics and current platform constraints have been checked.
• Territories and exclusivity settings match the actual rights and strategy.
• Platform-current requirements and disclosures were checked before submission.
• Submission evidence is preserved.
• The live listing/channel result has been audited.
• Open issues are controlled rather than forgotten.

← Start Your Book

Jack Righteous · Create What You Love | Love What You Create.