ONIX 3.1 Metadata for Publishers: A Practical Guide to Book Product Information

ONIX 3.1 Metadata for Publishers: A Practical Guide to Book Product Information

A publisher can have a professionally edited manuscript, an approved cover, a print-ready PDF, and a validated EPUB—and still experience problems getting the book represented correctly across sales and distribution channels.

Why?

Because producing the book is only part of the publishing process.

Retailers, wholesalers, distributors, library suppliers, ecommerce platforms, and catalogue systems also need accurate information about the book.

That information includes details such as:

• ISBN
• title and subtitle
• author and contributor information
• publication date
• product format
• subject classification
• book description
• pricing
• availability
• related editions

This is where ONIX 3.1 metadata becomes important.

ONIX provides publishers with a structured method for communicating book-product information across the supply chain.

For publishers managing hundreds or thousands of titles, consistent metadata is not simply an administrative requirement. It becomes part of effective publishing operations.

What Is ONIX Metadata?

ONIX stands for ONline Information eXchange.

ONIX for Books is an international standard used to exchange structured information about book products.

It allows publishers to send product information in a machine-readable format rather than maintaining separate manual records for every retailer or distributor.

ONIX uses XML to structure information about a publication.

A product record can include bibliographic information, descriptive content, product identifiers, commercial details, availability information, and relationships with other editions or formats.

For example, an ONIX record may communicate:

ISBN → Title → Author → Product Format → Publication Date → Description → Subject → Price → Availability

The important point is that ONIX describes the book product.

It does not contain the complete book content itself.

What Is ONIX 3.1?

ONIX 3.1 is a version of the ONIX for Books standard designed for structured product-information exchange.

It provides publishers with a detailed framework for describing book products and communicating that information to organizations further down the supply chain.

A publishing team may use ONIX 3.1 to communicate information about:

• print books
• ebooks
• audiobooks
• different editions
• different territories
• related products
• availability
• contributor information
• descriptive and marketing information

Publishers should always check which ONIX version their distribution partners currently support.

The goal is not simply to use the newest available structure.

The goal is to deliver correct metadata in a format that downstream systems can reliably process.

Why ONIX Metadata Matters for Publishers

Metadata connects the finished publication with the systems that sell, distribute, catalogue, and discover it.

Without accurate metadata, problems can appear even when the publication itself is correct.

For example:

A retailer may display the wrong publication date.

A paperback may be confused with an ebook.

An author's name may appear differently across multiple platforms.

A product may be incorrectly shown as unavailable.

A book may appear under an unsuitable subject category.

Pricing may differ between the publisher's approved information and downstream catalogue records.

These errors can create additional work for publishing, sales, metadata, and distribution teams.

A structured ONIX workflow helps reduce this inconsistency.

What Information Can an ONIX Record Contain?

ONIX metadata covers several categories of book-product information.

Not every receiving system uses every field in exactly the same way.

Publishers should therefore understand both the ONIX standard and any additional requirements imposed by their distribution partners.

Why ISBN Accuracy Matters

ISBN information is one of the most important elements of book-product metadata.

Different product forms may require different identifiers.

Consider a publisher releasing the same title in:

• hardcover
• paperback
• EPUB
• audiobook

These products are related, but they should not automatically be treated as the same commercial product.

ONIX metadata should correctly identify the format associated with each product record.

Example

A publisher releases:

Digital Publishing Fundamentals

• Hardcover edition
• Paperback edition
• EPUB edition

The metadata for each product should communicate the appropriate identifier and product form.

If identifiers are mixed between formats, retailers and catalogue systems may associate the wrong information with a product.

For publishers, accurate identifiers are therefore a basic metadata-quality requirement.

How ONIX Handles Titles and Contributors

A book-product record should clearly identify the publication and its contributors.

That may include:

• main title
• subtitle
• authors
• editors
• translators
• illustrators
• other contributors

Contributor roles are important.

An editor should not automatically be described as an author.

A translator should be identified according to the appropriate role.

For academic publishing, this can become more complex.

Edited volumes may have multiple editors.

Books may include contributors with different responsibilities.

Names may also appear in different forms across source systems.

A metadata workflow should therefore include checks for contributor consistency.

Questions publishers should verify

Is the contributor name spelled consistently?

Is the role correct?

Does the product metadata match the title page and approved publication?

Are contributor identifiers available where required?

Is the same person represented consistently across related titles?

Small inconsistencies can multiply across large catalogues.

What Is Subject Metadata?

Subject metadata helps communicate what a book is about.

Publishers may use structured subject schemes such as Thema, depending on their market and distribution requirements.

For example, a title about artificial intelligence in healthcare may belong to several relevant areas.

The metadata team needs to select subjects that accurately reflect the publication.

Subject information should not be chosen simply because a category has high visibility.

It should genuinely represent the book.

Why subject metadata matters

Subject information can support:

• retailer classification
• catalogue browsing
• distributor records
• library discovery
• product organization

The objective is accurate categorization rather than excessive classification.

How ONIX Supports Different Book Formats

One title may be available in several formats.

For example:

Book

↓

Hardcover

Paperback

EPUB

Audiobook

Each product can have different characteristics.

A paperback may have one price.

The EPUB may have another.

Publication dates can differ.

Territory availability may differ.

The publisher may also need to indicate how these formats relate to one another.

ONIX can support these product relationships.

This helps downstream systems understand that several products belong to the same intellectual work while still representing them as distinct commercial products.

Publishers managing digital editions can also review Gentize's EPUB Conversion Services guide for production-related considerations around digital-book outputs.

ONIX XML vs Publishing XML

This distinction is important.

Both may use XML, but their purposes are very different.

Publishing XML

Publishing XML represents the content inside the publication.

It may identify:

• chapters
• headings
• paragraphs
• tables
• figures
• references
• footnotes
• other structural content

ONIX XML

ONIX represents information about the publication as a product.

It may identify:

• ISBN
• title
• author
• format
• description
• publication date
• price
• availability

These two XML applications can work together in a publishing workflow, but they should not be confused.

Gentize's existing XML Conversion Services for Publishers article provides more detail about structured publication content.

What Is ONIX Metadata Validation?

ONIX validation checks whether a metadata record follows the expected technical structure and rules.

Validation may identify problems such as:

• missing mandatory information
• invalid values
• incorrect codes
• malformed XML
• structural errors

However, a technically valid ONIX file can still contain incorrect business information.

For example:

The XML can be valid while the publication date is wrong.

The contributor can be structurally valid but assigned the wrong role.

A valid product record can contain outdated pricing.

This means metadata QA needs more than technical validation.

A strong metadata QA workflow should include

Technical Validation

Does the record meet the required ONIX structure?

Bibliographic Review

Are the title, identifiers, contributors, and formats accurate?

Commercial Review

Are price, market, availability, and distribution details correct?

Receiver Requirements

Does the record meet the requirements of the retailer or distributor receiving it?

Together, these checks provide stronger metadata quality.

Common ONIX Metadata Problems

Publishers managing large catalogues should watch for recurring problems.

Incorrect Product Identifiers

The wrong ISBN may be associated with a format or edition.

Inconsistent Titles

Title or subtitle information may differ between the final publication and metadata feed.

Incorrect Contributor Roles

An editor may be listed as an author or vice versa.

Wrong Product Format

An ebook can be represented using information intended for a print edition.

Outdated Publication Dates

Publishing schedules can change without metadata being updated.

Weak Subject Classification

Products may have missing, broad, or unsuitable subject information.

Incorrect Availability

Products can appear available before publication or remain listed as unavailable after release.

Price Inconsistency

Commercial information can differ between approved internal records and downstream systems.

Each issue may appear small on an individual title.

Across thousands of records, however, the operational impact becomes much larger.

How Should Publishers Manage Metadata Updates?

Metadata changes throughout the publication lifecycle.

A book's original metadata may be created months before publication.

During production, information may change.

For example:

The subtitle is revised.

Publication is delayed.

A contributor name is corrected.

A new format is introduced.

Pricing changes.

Territory availability is updated.

Metadata processes should therefore support controlled updates.

A practical workflow is:

Create → Validate → Review → Distribute → Update → Revalidate

Publishers should also define who owns each type of information.

Editorial may control title information.

Production may confirm formats.

Marketing may provide descriptions.

Sales or distribution teams may manage pricing and availability.

Clear ownership reduces conflicting updates.

ONIX 3.0 vs ONIX 3.1

Publishers moving between ONIX versions should first understand the requirements of the organizations receiving their metadata.

A publisher should not move to a new metadata workflow without checking compatibility.

Important questions include:

• Which ONIX version does each receiver support?
• Are current publishing systems compatible?
• Which new data capabilities are actually needed?
• How will legacy records be handled?
• Will all downstream partners accept the new output?

The correct decision depends on the publisher's technology and supply-chain environment.

A metadata standard is most useful when both sender and receiver can process it correctly.

How ONIX Fits Into the Book Publishing Workflow

Metadata should not be treated as an isolated activity performed only after production.

It should stay aligned with the publication throughout the publishing process.

A typical workflow may include:

Manuscript

↓

Editing

↓

Typesetting

↓

Proofreading

↓

Indexing

↓

EPUB / Print Production

↓

Metadata Verification

↓

Distribution

For example, the final book title in the metadata should match the approved title on the publication.

Contributor information should match the final credits.

Product format should match the delivered edition.

Publication date should reflect the approved release schedule.

Metadata accuracy therefore depends on coordination between production and publishing operations.

Why Metadata Quality Becomes Critical for Large Catalogues

A publisher with ten titles may be able to review metadata manually.

A publisher with thousands of titles faces a different problem.

Small inconsistencies become difficult to identify.

Legacy metadata can accumulate.

Some titles may lack subject codes.

Others may contain outdated descriptions.

Different formats may not be properly related.

Contributor information may be inconsistent.

At scale, publishers need a structured review process.

A useful metadata audit can identify patterns such as:

• missing identifiers
• incomplete contributor information
• inconsistent titles
• missing classifications
• outdated dates
• format mismatches
• incomplete product relationships

Instead of correcting individual errors one by one, teams can identify common issues and improve the underlying workflow.

How Gentize Innovations Supports Publishing Production

Gentize Innovations supports book publishing and digital-production workflows including:

• typesetting
• EPUB production
• indexing
• editing support
• structured-content preparation
• metadata-related publishing support

Metadata preparation works best when it remains aligned with the actual publication and downstream requirements.

For publishers managing multiple formats or large catalogues, Gentize can discuss metadata requirements alongside production activities such as EPUB conversion, typesetting, and digital publishing.

Where a project requires specific ONIX feeds, receiver-specific requirements, or ongoing metadata management, the scope should be defined clearly before production begins.

Better Metadata Supports Better Publishing Operations

ONIX 3.1 provides publishers with a structured method for communicating book-product information.

But good metadata depends on more than producing technically valid XML.

The information itself must be correct.

The right ISBN must be associated with the right product.

Contributor roles must be accurate.

Formats must be identified correctly.

Publication dates, descriptions, pricing, subjects, and availability should remain consistent.

For publishers, metadata should therefore be treated as part of the publishing-production workflow—not simply as a final administrative task.

When product information is accurate and structured, publishers are better positioned to distribute consistent information throughout the book supply chain.

Planning a Publishing or Metadata Preparation Project?

If your publishing catalogue contains inconsistent product information, multiple formats, or growing metadata-production requirements, start with a representative set of titles.

Gentize Innovations can discuss how metadata preparation can fit alongside EPUB production, typesetting, indexing, and other publishing workflows.

CTA: Discuss Your Publishing Production Requirements with Gentize Innovations