How to Create a Valid ONIX Product from Scratch with ONIXEDIT Cloud

 

 

Creating your first ONIX product can seem complicated at first.

The ONIX standard contains many possible fields, codes, and sections, but you don’t need to complete everything to create a valid product record.

With ONIXEDIT Cloud, the required fields are clearly identified, validation is built into the interface, and you can create, enrich, export, and transmit ONIX metadata directly from your browser.

Watch: Create Your First Valid ONIX Product

In this tutorial, we create a complete ONIX product from scratch in ONIXEDIT Cloud and export it as a valid ONIX file.

Start with the mandatory ONIX fields

When you create a new product in ONIXEDIT Cloud, mandatory fields and sections are highlighted.

This gives you an immediate visual guide showing what still needs to be completed before the product can be considered valid.

The error summary also provides a complete list of validation issues and lets you navigate directly to the corresponding fields.

This makes it easier to work with ONIX without having to memorize every requirement of the standard. The ONIXEDIT Cloud user manual describes each of these sections in detail.

Use default values to save time

Some metadata values are often the same across many products.

For example, a catalogue may frequently use the same country of publication or other recurring information.

ONIXEDIT Cloud allows default values to be defined at the catalogue level so they are automatically populated when a new product is created.

This can reduce repetitive data entry and help maintain consistency across your catalogue.

Enter the core product information

A basic ONIX product usually starts with identifiers and title information.

In the tutorial, we enter:

  • Record reference

  • ISBN-13

  • EAN

  • Title

  • Publication date

  • Number of pages

ONIXEDIT Cloud also provides contextual field help directly in the interface, making it possible to view the meaning and expected use of individual ONIX fields while you work.

The more metadata you provide, the richer and more useful your ONIX record becomes.

Add supply and commercial information

A valid ONIX product also needs the appropriate supply information.

In the example, we define:

  • Supplier

  • Supplier role

  • Product availability

  • Price

  • Currency

  • Market or country information

Once the required information is present, ONIXEDIT Cloud validates the complete product before export.

Validate your ONIX metadata automatically

Validation is built into the workflow.

If a required field is missing or a value does not respect ONIX requirements, ONIXEDIT Cloud identifies the issue.

For example, date values must follow the expected format. If an invalid date is entered, the interface immediately reports the problem.

This helps users create compliant ONIX records without manually checking the XML structure.

Export your product as ONIX 3 or ONIX 3.1

Once the product is valid, it can be exported directly from ONIXEDIT Cloud.

The tutorial demonstrates exports in:

  • ONIX 3

  • ONIX 3.1

  • Reference names, also known as long tags

  • Short tags

Long tags are easier for humans to read, while short tags are more compact and are commonly used for system-to-system exchanges. The underlying metadata remains the same; only the XML representation changes.

Enrich your ONIX product with a cover image

A valid ONIX record can be further enriched with supporting media.

In the video, a high-resolution front cover is added directly to the product.

ONIXEDIT Cloud automatically creates a thumbnail version for efficient catalogue browsing while retaining the original image as part of the product’s media resources.

Additional metadata and media can be added over time to make the product record more complete.

Send ONIX metadata to your business partners

Creating the ONIX file is only one part of the workflow.

ONIXEDIT Cloud can also be configured with partner FTP accounts so that selected products, or an entire catalogue, can be transmitted directly to business partners.

This can simplify recurring metadata distribution to distributors, aggregators, retailers, resellers, and other recipients. See the ONIXEDIT Cloud feature list for the full picture.

Who is this tutorial for?

This workflow is useful for:

Publishers and content providers

Create and maintain ONIX metadata for your titles without working directly with XML.

Distributors and aggregators

Create or enrich ONIX records when source metadata needs to be completed, corrected, or standardized.

Resellers and retailers

Understand the structure and validation of ONIX product metadata received from suppliers.

Metadata professionals

Learn the core elements required to build a valid ONIX product and see how ONIX validation works in practice.

You don’t need to be an ONIX expert to get started

The ONIX standard is extensive, but creating your first valid product doesn’t have to be complicated.

ONIXEDIT Cloud guides you through mandatory fields, validates your metadata, provides contextual help, and lets you export a standards-compliant ONIX file once the essential information is complete.

From there, you can progressively enrich the record with additional bibliographic, commercial, marketing, and media information.

Key takeaways

  • Only the mandatory fields matter at first: ONIXEDIT Cloud highlights them and the error summary jumps straight to what is missing.

  • Catalogue-level default values fill in recurring information, such as the country of publication, automatically.

  • Identifiers, title and supply: record reference, ISBN-13, EAN, title, date, pages, supplier, availability, price, currency and market are enough for a first valid record.

  • Built-in validation: missing fields and invalid values, such as a malformed date, are reported before export.

  • Export and transmit: ONIX 3 or ONIX 3.1, in long or short tags, with a cover image, straight to your partners’ FTP accounts.

Frequently asked questions

What information is required to create a valid ONIX product?

The exact requirements depend on the product and ONIX context, but ONIXEDIT Cloud identifies mandatory fields and sections directly in the interface and reports any missing or invalid information.

Does ONIXEDIT Cloud validate ONIX metadata?

Yes. Validation is integrated into the editing workflow and identifies missing required fields or invalid values before the product is exported.

Can I export ONIX 3.1?

Yes. ONIXEDIT Cloud can export ONIX 3 and ONIX 3.1, including reference-name and short-tag XML representations.

Can I add cover images to an ONIX product?

Yes. Cover images and other supporting resources can be associated with products and managed alongside the ONIX metadata.

Can ONIXEDIT send files directly to our partners?

Yes. Partner transmission profiles can be configured so ONIX metadata can be sent to selected recipients.

Create your first ONIX product with ONIXEDIT Cloud

Whether you’re new to ONIX or simply want an easier way to manage book metadata, ONIXEDIT Cloud provides a guided environment for creating, validating, enriching, and distributing ONIX products.

Learn more about ONIXEDIT Cloud

Ready to try it? Start a free trial.