← Back to blog

Series Metadata in EPUB: How to Set It Up Correctly

October 22, 2026
Series Metadata in EPUB: How to Set It Up Correctly

In EPUB 3, series metadata lives in the package (OPF) file as a belongs-to-collection entry, refined by a collection-type of "series" and a group-position number. That is the part inside the file. The part most authors miss is that the big retailers ignore it for series linking: you also enter the series name and number in each store's dashboard, and the two must match exactly.

This guide shows the OPF markup, the dashboard rules for Amazon KDP, Kobo and Apple Books, the mistakes that stop books from linking, and a short checklist to run before every upload.

Alhora
Prepare Series Books with Confidence
Alhora formats manuscripts into eBooks and print editions, with real-time validation against publishing standards to help catch formatting issues.
Explore Alhora

Key takeaways

  • EPUB 3 stores series data in the OPF with belongs-to-collection, collection-type and group-position. There is no single "series" field.
  • Stores take series name and number from their own dashboards. Embedding alone is not enough, so enter the same values in both places.
  • Keep the series name clean: no "Book 1", no genre tags, and no series info in the title or subtitle.
  • One stray space or a mismatched name between volumes can stop the books from linking.
  • Validate the package with EPUBCheck before you upload, and keep one metadata record per series so every volume gets identical values.

Table of Contents

What series metadata does for a reader

Series metadata is what turns separate books into a series on a store page. When it is accepted, Apple Books says each book in the series links together, so customers can move to the next book, buy it, or pre-order it. Kobo's guidance makes the same point: metadata is how readers find your books, and series data is a large part of that.

For an author with a series, that matters commercially. A reader who finishes book one and sees a clear path to book two is the reader you want. Broken series data removes that path.

There are two layers to keep apart:

  1. Metadata inside the EPUB file. This travels with the file to e-readers, library apps and tools such as Calibre or KOReader.
  2. Metadata in the retailer dashboard. This drives the store's series page, "next book" prompts and search.

You need both, and they need to agree.

How EPUB 3 stores series information

EPUB 3 has no dedicated series field. The EPUB 3.0.1 specification defines belongs-to-collection as the property naming a collection that the publication belongs to, and group-position as the numeric position of the publication within that group. You build a series from three meta elements in the OPF metadata block:

  1. A belongs-to-collection element holding the series name, with a unique id.
  2. A collection-type element that refines that id and says "series".
  3. A group-position element that refines the same id and holds the number.

A minimal example for book 2 of a series:

<meta property="belongs-to-collection" id="series-1">The Harbor Chronicles</meta>
<meta refines="#series-1" property="collection-type">series</meta>
<meta refines="#series-1" property="group-position">2</meta>

The series name here is an invented example. Use your own, spelled the same way in every volume.

The Readium project, which documents how reading systems parse this data, describes the result as a belongsTo object holding a series with a name, a sort value and a position. The collection-type is expected to be "series" or "set". Choose "series" for ordered stories and "set" for boxed collections or bundles. Mixing them up can break auto-linking.

Why you will see calibre:series in older files

You may open an older EPUB and find Calibre-style tags instead. These are non-standard but still read by some software. A KOReader issue about EPUB 3 series handling shows how reading tools can handle the two approaches differently, and some basic readers ignore the EPUB 3 structure entirely. If you produce files for a mixed audience, write the EPUB 3 markup first. It is the one the specification defines.

Numbers: integers and decimals

group-position is numeric. Use "1", "2", "3". For a prequel novella that sits between main entries, retailers that allow decimals accept values like 2.5. Never write "Book 2" or "Two" in the numeric field. Apple's rule is explicit: you can only use numeric values, such as 3, and if you want the store to say "Volume", "Prequel" or "Novella", that goes in a separate display text field.

Retailer dashboards: what each store wants

The file is half the job. Here is how the three stores most indie authors use treat series data.

StoreWhere series data goesKey rule
Amazon KDPSeries fields on the book details pageSeries info stays out of the title and subtitle
Kobo Writing LifeSeries name and number fields when you set up the eBookSeries info belongs in the series fields only
Apple BooksSeries name, sequence number and display textNumeric sequence only; names must match exactly

Amazon KDP

KDP's Metadata Guidelines for Books list series information as its own section, separate from the title and subtitle. Treat the title field as the title only. If the series name is in the title, you are duplicating data the store builds series pages from.

Kobo Writing Life

Kobo's EPUB best practices tell authors to label series information correctly and not to put it in the title or subtitle. They also note that repeating series information in several places on a product page is often confusing. Their setup guide for a new eBook is the place to see exactly which fields to fill in. If you format for Kobo specifically, our Kobo EPUB formatting guide covers layout and accessibility testing before upload.

Apple Books

Apple asks for three things: series name, sequence number and display text. Its support page says the series name must match exactly for all books, and that consecutive numbers should be used if the order matters. You can submit series data with the first book, and the series appears on the store once two or more books from it are available.

Most series problems are not technical. They are small inconsistencies repeated across volumes.

Name drift

One book says "The Harbor Chronicles" and another says "Harbor Chronicles, The" or "The Harbour Chronicles". To a human these are the same series. To a catalog system they are different strings. A trailing space counts too. Kobo's guidance, as relayed in our research, treats consistency as the whole game: if the data differs even slightly, the books may not associate into one series page.

Volume information inside the name

The series field takes the name only. "The Harbor Chronicles, Book 2" in the name field is wrong, because the number has its own field. The same goes for the numeric field: "Book 1" in one volume and "1" in another is a mismatch, and text strings are not accepted.

Series info in the title or subtitle

It is tempting to write "Tide Wrack: A Harbor Chronicles Novel" as a title. KDP and Kobo both direct you to keep series information out of the title and subtitle fields. The store builds series display from the dedicated fields. Duplicating it can cause rejections or a messy product page.

Tags in the series field

The series field is not a keyword box. Adding "Bestseller" or a subgenre like "Small-town Romance" to the series name pollutes the catalog and can lead to a correction request or a rejection. Put genre and keywords where the store provides them for that purpose, and read the KDP guidance on keywords and categories alongside the series section.

Wrong collection type

A numbered, ordered story arc is a "series". A boxed set that bundles several books is closer to a "set". Labeling one as the other can break linking logic, so decide per product.

Trusting the file alone

You may embed perfect OPF markup and still see no series page, because the store reads its own fields. Treat the file as the record that travels with the book and the dashboard as the record that sells it.

A step-by-step workflow for a multi-book series

Use this order for every new volume.

  1. Fix the canonical series name. Decide exact capitalization, punctuation and spelling. Write it once in a master record and copy it from there. Do not retype it.
  2. Assign positions. Use whole numbers for main entries. Reserve decimals like 1.5 for prequel novellas or shorts that sit between entries, and only where the store allows decimals.
  3. Write the OPF block. Add belongs-to-collection, collection-type and group-position as shown above, with a unique id that the two refining elements point to.
  4. Clean the title fields. Title and subtitle carry no series name and no volume number.
  5. Validate the package. Run EPUBCheck. Recent EPUBCheck-compatible tooling validates collection rules, for instance that belongs-to-collection can only refine other belongs-to-collection properties. Our guide on fixing EPUBCheck errors walks through typical failures.
  6. Enter the same data in each dashboard. Series name, number, and display text where offered (Apple Books). Compare character by character.
  7. Check the live page. Once the store processes the book, confirm the series link and the order. Apple notes that a series shows up after two or more of its books are live, so do not panic over a single-book test.
  8. Repeat per volume. Copy values from the master record, never from the last book's dashboard page.

A quick audit table

Before upload, compare every volume of a series in one view:

CheckBook 1Book 2Book 3
Series name identicalyesyesyes
Position numeric only123
Series text absent from title/subtitleyesyesyes
Same collection typeseriesseriesseries
Dashboard matches fileyesyesyes

If any cell is "no", fix it before publishing, not after a store flags it.

Metadata beyond the series fields

Series data sits among other fields that retailers and libraries read: title, contributors, description, ISBN, language, categories and publisher. Errors in one field tend to appear in others, because they usually come from the same careless copy-paste. Our piece on book metadata best practices lays out a longer plan for getting all of it right across your catalog.

If you are also targeting libraries, schools or accessibility requirements, the package-level metadata for accessibility sits in the same OPF. See our EPUB accessibility checklist for that side of the file, and our notes on Google Play Books requirements if that store is on your list.

Our perspective: treat series data as one record, not eight forms

We built Alhora because formatting problems rarely come from one big mistake. They come from the same value typed slightly differently in eight places. Series metadata is the clearest example. A name that is right in the manuscript, right in the file and slightly different in one dashboard still breaks the reader's path to the next book.

Our view is that a series should have a single source of truth that every volume draws from. That is why Alhora handles batch series formatting, metadata and ISBN management, and real-time validation against publishing standards in the same studio as the typesetting. You see a problem while you are working on the book, not after a store rejection email.

Our perspective: treat series data as one record, not eight forms — overview diagram

We also keep a firm line on what software should do. Checks, validation and AI-assisted proofreading flag issues. They never write or change your creative content. Your series name, your numbering and your story stay yours.

One practical habit we recommend: write the series name and the position into your metadata before you finalize the interior. When the data exists early, every export, from EPUB to print PDF, starts from the same facts.

— James

Where Alhora fits

If you publish a series, you need exports for several stores from one project. Alhora is a book formatting studio for Mac, Windows, Linux and ChromeOS. It typesets ebooks and print editions, formats series in batches, manages metadata and ISBNs, and exports EPUB for KDP, Kobo, Apple Books, Google Play, Draft2Digital and IngramSpark. It is currently listed at £99 as a one-off purchase.

See how the EPUB side works for every store, or read about the studio on Mac or Windows.

FAQ

Do I need series metadata in the EPUB if I enter it in the store dashboard?

Yes, it is good practice to do both. The dashboard drives the store's series page, while the file carries the information to readers, libraries and apps that open the EPUB directly. Keep the values identical so nothing contradicts anything else.

What is the correct way to write series data in EPUB 3?

Add a belongs-to-collection meta element with the series name and an id. Then add two meta elements that refine that id: a collection-type set to "series" and a group-position with the number. This is the structure defined in the EPUB 3.0.1 specification.

Can I use "Book 1" in the series number field?

No. The number field takes numeric values only, and Apple Books states plainly that only numeric values are accepted. If you want the store to display a word like "Volume" or "Novella", use the display text option where it exists, not the number field.

Should the series name appear in my title or subtitle?

No. Both KDP and Kobo direct you to keep series information out of the title and subtitle and to use the series fields instead. Repeating it can trigger rejections and cluttered product pages.

Why isn't my series showing up on the store after publishing?

The usual causes are a name that differs between volumes, text in the number field, or a series that does not yet have two live books on Apple Books. Compare every volume's series name character by character, then check the numbering. If everything matches, contact the store's support with the exact values you entered.

Sources