Managing a Catalog at Scale

What this book is

The catalog tax

At book five, the backmatter is a few lines typed by hand and metadata lives in your head, and nothing is wrong because nothing is old enough to drift. Eighteen months later a reader clicks a link in Book 12's backmatter and lands on a 404 — the ASIN is correct, but the product was deactivated and relisted under a changed URL. Nobody touched Book 12 after publishing; the link has just been dead for four months. KDP doesn't notify you when a linked ASIN stops resolving. The book keeps selling, the dead link keeps appearing, and your only signal is a review that happens to mention it.

This book documents the operating system actually running underneath a fifty-plus-book catalog. series-metadata.md is the single source of truth for every data point on every book — ASIN, title, subtitle, publication date, status — nowhere else. build_all_docx.py maintains the build registry, mapping output formats and file paths so the build system knows the catalog without querying the filesystem. generate_backmatter.py reads from series-metadata.md and writes backmatter across the full catalog, pulling only confirmed ASINs, turning a 49-file propagation problem into one command. None of it works without the discipline underneath it — when an ASIN changes in KDP without a matching metadata update, the tooling faithfully propagates the wrong ASIN into every book it touches.

What you’ll learn

Eleven chapters, from the metadata spine to the correction pipeline

• the-metadata-spine — Why series-metadata.md has to be the single source of truth for every data point on every book, with nothing duplicated elsewhere.
• asin-discipline — ASIN and ISBN discipline: confirming before propagating, and why an unconfirmed ASIN is worse than a missing one.
• the-listing-template — A composable, versioned listing template that fixes template drift at the source instead of retroactively.
• the-builder-registry — How build_all_docx.py maps output formats and file paths so the build system knows the catalog without querying the filesystem.
• backmatter-as-infrastructure — Treating backmatter as infrastructure that propagates automatically, not prose that gets typed by hand per book.
• cover-discipline — Cover file naming, sizing, and compression conventions that keep the image pipeline consistent across dozens of titles.
• drift-detection — Catching stale metadata, mismatched templates, and dead links before a reader finds them first.
• before-you-submit — The pre-submission checklist that catches propagation errors before they reach KDP.
• scaling-the-discipline — What changes about the tooling and the discipline between book five and book fifty.
• the-correction-pipeline — Correcting an error that has already propagated across the catalog, in one pass instead of file by file.
• conclusion — The catalog tax compounds silently; the operating system in this book makes it detectable and correctable before a reader finds it.

From the book

A preview

Automation at scale amplifies whatever it reads; accurate data keeps the catalog clean, stale data turns the tooling into a reliable delivery mechanism for errors.

Who it’s for

Publishers whose catalog has outgrown working memory

This is for publishers whose catalog has outgrown working memory and who need the propagation and drift-detection problem solved once, in tooling, rather than resolved by hand every time a new title ships. It assumes the reader already publishes — KDP mechanics, docx build pipelines, and basic file-based metadata management aren't covered. What's here is the problem that appears after those basics are solved.

A longer excerpt is available to newsletter subscribers.

Buy Ebook on Amazon