Audit a Series Name Across Covers, Title Pages, and Listings

Build an identity table for every volume and format, then compare the series wording and numbering across the cover, title page, metadata worksheet, and public listing. Record intentional differences separately from errors. Resolve the underlying identity decision before changing files so one correction does not introduce another inconsistency elsewhere in the series.

Define the authoritative wording

Start with the series name and volume relationships the author intends to use. Record the approved wording, capitalization, and punctuation. Keep book titles distinct from the series name so a descriptive phrase on one cover does not accidentally become a competing series identity. KDP metadata guidance says the series information on the cover should match the corresponding metadata field; a documented design preference does not override that requirement.

If earlier books already use different wording, do not choose a winner solely because one file is newer. Investigate how the difference arose and which published materials it affects. A revised design label may never have been intended as a rename. Write down the approved decision and its scope before editing files. The purpose of the audit is to establish a coherent identity, not merely make every visible string identical without understanding what it represents.

Create one row for each actual edition

List every relevant volume and format rather than one row per story. An ebook cover and a paperback cover can come from different production rounds, and an older print file may preserve wording that was corrected in the ebook. Record the file or page inspected and the date of the observation. A remembered description of the cover is not a reliable substitute for checking the actual asset.

Use columns for book title, series name, volume label, author name, format, and the locations where those values appear. Add a status for each discrepancy and explain intentional visual treatments, such as line breaks or type size. Do not treat an abbreviated or renamed series label as approved merely because a designer used it. Compare its wording with the metadata requirement and resolve any mismatch before the replacement package is accepted.

Check numbering and reading relationships

Compare volume labels with the intended reading order. A prequel, side story, collected edition, or revised edition may not fit a simple sequence. Record its relationship explicitly instead of forcing it into a number that suggests a different order. Review the current options and guidance in KDP before entering the relationship, since your internal planning shorthand may not match the way the platform presents series information.

Examine back matter and promotional references as well as the title page. A link inviting readers to "Book Two" may point to a title that was later renamed, or an optional novella may be described as required reading in one edition. Trace those references to the actual destination and intended relationship. Correcting the main metadata field does not automatically repair text already embedded in an ebook or printed in a paperback.

Plan corrections by dependency

Group discrepancies according to the work they require. A metadata worksheet correction, a replacement ebook cover, and a revised print wrap follow different production paths. Identify the owner and dependencies for each change. If a title or series decision affects several assets, approve the wording once and distribute the same record to everyone making the updates. This reduces the risk that each person interprets the correction differently.

Check the current KDP update path before assuming that every identity field can be changed in place. Preserve the existing identifiers and submission history while investigating the appropriate procedure for the actual situation. Do not solve a naming disagreement by creating duplicate records or inventing a new edition relationship without review. Keep the editorial decision and the platform procedure connected, but treat them as separate questions that both need a clear answer.

Verify the result on files and public surfaces

After preparing corrections, repeat the comparison against the replacement files before submission. Inspect every changed cover and title page rather than relying only on the source worksheet. When updated public information becomes available, compare it with the intended values and record what you observed. If a surface still differs, use the current platform status and support guidance to investigate rather than repeatedly making unrelated changes.

Save the completed identity table as the reference for the next volume. Include the date, approved wording, and known exceptions so a future collaborator does not recreate the same disagreement. A consistent series identity helps readers recognize the relationship between books, but the table itself is simply an operational record. Its value comes from keeping real files, metadata, and reading relationships aligned as the catalog grows.