Keep KDP book details and EPUB series metadata in two ledgers. Entering “volume 2” in a local EPUB does not prove that KDP will automatically group or display the product as volume 2. Similar labels belong to different systems and must be reconciled after each system has stored them.
Give each system its own record
The local ledger owns the series name, volume number, volume title, author, publication date, and edition used to build the EPUB. The KDP ledger owns the values entered or observed in KDP, the uploaded artifact, its status, and the date of verification. Add a shared publication card above both, but do not let either result silently overwrite it.
A card for volume two is transferred to each system independently. If a mismatch appears later, the two ledgers reveal whether the source EPUB or the retailer record needs correction.
Build the local side in Rune Studio
Enter series, author, publisher, and language on Series Information in the EPUB wizard. Choose volume 2 on Volume Selection. After selecting and ordering the chapters, use Metadata for edition, publication date, and cover. Compare the Review and Export summary with the publication card before generating the file.
In a three-chapter local inspection, the generated package contained the selected series name and volume number 2. Navigation and reading order were also present. A second build reproduced the structure, and the local package check was valid. That is evidence for the Rune Studio side of the ledger.
Begin the KDP side as unverified
The available run did not observe KDP's input form, acceptance response, or storefront series grouping. It cannot support claims of automatic synchronization or guaranteed series display. Use Amazon's current supported file guidance, enter the intended product details, and record what KDP actually returns.
If the result differs, decide whether the EPUB source is wrong or the retailer product record is wrong. Rebuilding a correct EPUB will not repair an unrelated KDP field, and editing a KDP title will not correct metadata inside the local artifact.
Watch for number collisions
Volume number and edition number can both be “2” while meaning different things. Product title and volume title may legitimately differ. A previous volume's publication date can survive in a copied project. A standalone value may be represented intentionally rather than left blank. Read the meaning written on the source card instead of inferring it from a file name.
EPUB metadata describes the publication package; it is not a retailer database. The distinction follows the package role in EPUB 3.3 and the separate operation of KDP.
Completion requires two observations: the local volume-two EPUB can be rebuilt, and KDP displays the submitted product as intended. Rune Studio is a candidate for the first task, not an interface for the second. Its current Mac feature scope keeps that boundary explicit.
