ONIX feeds
Standards-compliant ONIX 3 feeds, per channel.
Most authors will never see an ONIX feed. But if you're a small press, an imprint, or a publisher with established workflows, the quality of your ONIX is the quality of your distribution. Chiify generates per-channel ONIX 3.0 feeds and can ingest yours directly.
ONIX is the standard XML format the book industry uses to exchange product metadata between publishers, distributors, and retailers. EDItEUR publishes the spec; the current version is 3.0.
For individual authors, ONIX is invisible: you fill in your title, description, and BISAC categories in our UI, and we serialize that into the right XML format per channel. For publishers running their own catalog systems, ONIX is the interchange format — and the quality of your ONIX directly controls how well your books show up in retailers' search and recommendation engines.
What our ONIX feeds include
- Product identifiers — ISBN-13, GTIN-13, internal SKUs, optionally DOI
- Title elements — full title, subtitle, original-language title
- Contributors — authors, narrators, translators with proper ONIX role codes
- Subject classification — BISAC and Thema codes, audience codes, age range
- Publishing details — publisher, imprint, publication date, edition number
- Product form — EPUB, audiobook, paperback, hardcover with proper format codes
- Accessibility metadata — codes 94, 95, 96, 97 for EAA 2025 readiness
- Descriptions — short and long descriptions, table of contents, review quotes
- Pricing — list price per market, currency, tax info
- Sales rights — territory-by-territory rights and library lending rights
Per-channel customization
Different channels parse different subsets of ONIX. Our library aggregator uses one profile; IngramSpark uses another; Apple uses its own variant. We serialize correctly for each, rather than a one-size-fits-all feed that some channels misinterpret.
You can see exactly which channels we're generating ONIX for, and what each feed looks like, in your dashboard.
Bring your own ONIX (Enterprise)
If you already produce ONIX 3 feeds — typical for established small presses or imprints with 50+ titles — Enterprise accounts can ingest your feed directly. We validate against the EDItEUR spec, route per-title to the channels you specify, and deliver.
Enterprise also supports incremental feed updates (correction, price change, takedown) without re-shipping the whole catalog every time.
Frequently asked
Do I need ONIX as an individual author?
Probably not. We generate the ONIX feed for you automatically when we ship your book. This page is for small presses and imprints who want to understand what's happening under the hood.
Which ONIX version do you generate?
ONIX 3.0. We support both the library-aggregator reference profile and the IngramSpark profile, serialized correctly for each retailer.
Can I upload an existing ONIX feed instead of using your metadata UI?
Yes, for Enterprise accounts. If you maintain your own catalog system and produce ONIX 3 feeds, we can ingest your feed directly.
What ONIX fields do you populate?
The complete required set plus recommended optional fields: identifiers, titles, contributors, subjects, publisher, descriptions, accessibility metadata, language, pricing, and sales rights.
Can you exclude certain territories or retailers per title?
Yes. Per-title territory exclusions and per-channel routing rules are managed in your dashboard per book.
ONIX, done right.
Per-channel feeds, full standards compliance, BYOI feed ingestion for Enterprise. Talk to our team.