Time to Act: The ONIX 3 Transition is Actually Here
Way back in the before times of 2019, the book industry faced a major turning point when Amazon announced that they would require publishers to transition from ONIX 2.1 to ONIX 3 for physical books' metadata. This sparked a flurry of activity and led to a wave of upgrades across the industry, but there was a notable exception: Kindle books were given a pass. Many publishers and aggregators breathed a sigh of relief and continued using their familiar ONIX 2.1 processes for eBook metadata.
That grace period is officially ending.
Amazon now accepts ONIX 3 for eBooks and has set a deadline of March 2026 for all ONIX-sending publishers to transition away from sending ONIX 2.1. Publishers who haven't made the transition to ONIX 3* yet need to act now.
But just as the book industry is greater than Amazon, so too is this transition to ONIX 3 greater than Amazon’s change in requirements. New accessibility legislation and the technical limitations that have been building up in ONIX 2.1 over the past ten years (since it was officially sunset by EDItEUR) have made ONIX 3 adoption inevitable. It’s not just advisable, but essential that publishers transition to ONIX 3 now.
Accessibility Metadata is Non-Negotiable
Here's what many publishers don't realize: the transition to ONIX 3 isn't just a technical upgrade—it's becoming a legal necessity. The European Accessibility Act (EAA) requires metadata about an eBook’s accessibility features to be provided and communicated throughout the supply chain for any eBook being sold in the EU.
Critically, metadata about accessibility features can only be conveyed via ONIX 3. ONIX 2.1 simply doesn't support the essential ONIX codelist (196) that includes accessibility metadata features like:
- Text-to-speech functionality
- High contrast display options
- Navigation aids for visual impairments
- Dyslexia-friendly formatting
- WCAG compliance
Without this metadata, your eBooks may not comply with EU accessibility regulations, potentially limiting your market reach and exposing you to legal risks.
Beyond Compliance: ONIX 3's Business Advantages
As Graham Bell explained in the Book Industry Study Group's 2020 webinar on the transition from ONIX 2.1, ONIX 3 wasn't developed in a vacuum. It addresses real business problems that accumulated over two decades, including:
- Enhanced Discoverability Through Richer Metadata
The demand for sophisticated marketing collateral has exploded since ONIX 2.1 was designed. ONIX 3 can handle multiple language descriptions, detailed promotional events, and comprehensive marketing materials that today's digital marketplace demands.
- Better Support of International Markets
The book business is global now in ways that weren't anticipated in 2003. ONIX 3 handles multiple languages in a single record, complex international sales rights, and the nuanced market information that global distribution requires. In ONIX 2.1, you could get away with listing just the countries where you wanted to sell. ONIX 3 requires comprehensive territorial information—not just where books are for sale, but where they're not. This precision is essential for global distribution.
- Comprehensive Digital Product Support
ONIX 2.1 was created when eBooks were an afterthought. ONIX 3 was built with full knowledge of how the digital market actually developed, supporting complex pricing models, subscription services, and the accessibility metadata now required by law.
The Technical Transition
One of the biggest misconceptions about the ONIX 2.1 to 3 transition is that it requires rebuilding everything from the ground up. That's simply not true.
If you're using a commercial title management solution, your first step should be contacting your vendor. The overwhelming majority already support ONIX 3 and can help you transition with minimal disruption, so talk to them today.
If you've built an in-house ONIX solution, you're not starting over. Much of your existing code will continue to work. As Bell emphasized in the 2020 webinar, there's about 60-70% commonality between ONIX 2.1 and ONIX 3. Your existing databases don't need major changes. ONIX is the message format, not the database structure. Think of it as creating a different report from the same underlying data. If this feels daunting, perhaps it’s time to look at a commercial title management provider to keep on top of updates so you don’t have to.
The March 2026 Deadline: The Bell is Tolling
With less than six months until Amazon's March 2026 deadline, your window of opportunity is rapidly closing. Get started now and escape the last-minute scramble in March.
Here’s where to focus today:
- Learn about ONIX 3. EDItEUR offers an abundance of information on ONIX 3, including training opportunities hosted by BISG. If you need to start at the ground floor, try the Metadata Education series on the BISG YouTube channel.
- Look at your current system and workflows. What needs to change? Is now the time to implement a total overhaul or will a tweak do? And if you opt for the ‘tweak’ now, make sure you plan for a more complete look at your metadata systems and processes later. And talk to your title management service provider if you use one.
- Talk to your Supply Chain partners. Communication is key. Set a transition timeline for any remaining recipients of your ONIX 2.1 feed. Most already support ONIX 3 and they are very aware of the looming Amazon deadline.
- Review your eBook accessibility. Take a look at your EPUB files as well as your EPUB conversion specifications. What accessibility features are included or need to be included for future compliance? How can you now communicate this within ONIX 3? EDItEUR has advice on this, of course.
The Bottom Line
The ONIX 3 transition for eBooks isn't optional anymore, it's a business necessity driven by legal requirements, technical evolution, and marketplace demands. Publishers who acted in 2020 for physical books already see the benefits. Those who waited now face a compressed timeline, but they can learn from early adopters and move forward strategically.
This transition may seem daunting, but as the 2020 experience showed, the technical challenges are manageable and the business benefits are real. Let’s truly sunset ONIX 2.1 and move forward with ONIX 3. Now’s the time!
*Note: I refer to “ONIX 3” throughout, in full knowledge that the current version is ONIX 3.1.2. This has been done for clarity and should not affect any information or advice I’ve offered.
CLAIRE HOLLOWAY is Manager of Publisher Relations for OCLC and the chairperson of the Book Industry Study Group’s Metadata Committee. Before making a mid-life decision to turn her focus to the library space, Claire had worked in editorial and production roles throughout the publishing industry. Claire loves books of all genres (except thrillers), metadata of all flavors, and sharing information about both to anyone who wants to learn.
BISG's Metadata Committee is responsible for suggesting changes to the ONIX standard and its code lists, so distributors and retailers can easily identify what a book is about and successfully market it. Building on BISG best practices, the committee makes recommendations to help metadata providers and recipients provide timely, high-quality metadata for all book formats. Click here to learn more.