EDItEUR · ONIX 3.1 · 3.0
Validate your ONIX before a store reads it.
An ONIX file can pass schema validation and still reach the store wrong. We also check what the schema cannot see.
The check happens in your browser. The file is not uploaded to any server and is not stored. We only count, without identifying anyone, how many files are checked and of what kind. Never their name or their content.
How it works
Two layers, all on your computer.
- 01
EDItEUR's schema
Each product is checked against EDItEUR's official schema for its version, ONIX 3.0 or 3.1: the structure, the order of the elements, the required fields and every code against its list.
- 02
What the schema cannot see
A file can meet the schema and still say impossible things. We check for dates that do not exist, ISBNs with the wrong check digit or repeated, duplicate references, prices with no currency and complete records with no description.
- 03
In your browser
The file is read on your computer, product by product. Only EDItEUR's schemas are downloaded, from this site. The catalogue is not sent anywhere.
Scope
What it checks and what it does not.
It checks
- ONIX 3.0 and 3.1, with reference and short tags
- EDItEUR's official XSD schema with all its code lists
- Impossible dates, ISBNs with a typo or repeated, duplicate references and prices with no currency
- Complete records that do not bring the product description
- Files of up to 50 MB, product by product, with the line of every error
It does not check, and says so
- ONIX 2.1, which EDItEUR no longer maintains
- Each store's own requirements: we apply no store's profile
- The additional rules of the “strict” version of EDItEUR's schema
- Codes EDItEUR marks as deprecated: we do not flag them yet
- The consistency of files with short tags: for those, only the schema
Standard
Every check says which version it runs against.
EDItEUR's XSD schema for ONIX 3.0.8 and 3.1.3, with the code lists of issue 74, July 2026. The schemas and code lists are EDItEUR's, which publishes them free of charge for general use; we serve them unmodified, under its licence.
If you validate one file, this is enough. If you validate a catalogue, let's talk.
The same checks run inside Lantia's platform on every title, before every delivery to the stores. For an imprint that publishes every month, the next step is not validating files one by one: it is the check happening on its own.
Talk to the digital distribution team