ONIX 3.0 and options
Every catalogue in ONIXEDIT Cloud is either ONIX 2.1 or ONIX 3.0; "3.0" covers the whole ONIX 3 family, and the 3.0 / 3.1 release only matters when a file is produced. This page explains how a Cloud account that started in ONIX 2.1 gets ONIX 3.0, and the two options an ONIX 3.0 catalogue can switch on: ONIX 3 Best Practices validation and the automatic transfer of deprecated ONIX 3.0 elements to ONIX 3.1.
Where to find it
- Manage ONIX 3 Options is a link in the header of the actions column of the title list of an ONIX 3.0 catalogue. It is shown to users of an ONIXEDIT Cloud subscription; the options are saved per catalogue.
- Need to work with ONIX 3.0? (tooltip Convert to or add a new ONIX 3.0 catalogue) is an entry of the Settings menu of the top bar. It is offered to the owner of a Cloud account that works in ONIX 2.1 and has not chosen an ONIX 3.0 option yet; it disappears once a choice is made.
- The ONIX 3.0 / 3.1 choice itself lives in the Actions dropdown (Export selected products to ONIX 3.0 REF, Export selected products to ONIX 3.1 REF and their SHORT variants) and in the ONIX 3 version field of each partner in Transmit to Partners.
Screen overview
The Manage ONIX 3 Options dialog has two cards, each with a description and a checkbox: ONIX 3 Best Practices with Enable ONIX 3 Best Practices, and Automatic Transfer of Deprecated ONIX 3.0 Elements to ONIX 3.1 with Enable Automatic Transfer of Deprecated ONIX 3.0 Elements. Save stores both for the current catalogue; Cancel closes without change.
How to get ONIX 3.0 on a Cloud account
When you register, ONIXEDIT recommends ONIX 3.0, the current version of the standard, but you may start in ONIX 2.1. To move later:
Open the Settings menu and choose Need to work with ONIX 3.0?.
Read the three options. The dialog warns: you can choose between these 3 possible options only once and you can't reverse your choice.
Option What it does Select option #1 - Export ONIX 3.0 files Keeps your ONIX 2.1 catalogue as the only one to maintain. Additional validations check that your titles meet ONIX 3.0 requirements, and the Actions dropdown gains the Export selected products to ONIX 3.0 REF / 3.1 REF / SHORT actions, produced by the automatic converter. Select option #2 - Convert my catalogue to ONIX 3.0 Converts the ONIX 2.1 catalogue and its content to ONIX 3.0. From then on you produce ONIX 3.0 files only; there is no way back to ONIX 2.1. Select option #3 - I want an additional ONIX 3.0 catalogue Keeps the ONIX 2.1 catalogue and adds a new, empty ONIX 3.0 catalogue. The titles allowed by your plan are shared between both, and a title needed in both formats is maintained twice. The new catalogue imports ONIX 2.1 and ONIX 3.0 files. Click the button of your option, or Do not choose now and return to the list to decide later.
With option 2 or 3, the catalogue selector of the top bar reloads with the converted or added catalogue. With option 1, the new export actions appear on the ONIX 2.1 list.
Your plan's title limit applies across catalogues; see My Subscription before choosing option 3 with a nearly full catalogue.
How to turn on Best Practices
- On the ONIX 3.0 list, click Manage ONIX 3 Options in the header of the actions column.
- Tick Enable ONIX 3 Best Practices and click Save.
From then on, validation checks the additional mandatory fields and rules of the official EDItEUR best practice guide on top of the ONIX 3.0 schema, in the entry form and in the error lists. Titles that were valid may become invalid: use Generate error list for selected products to see what to complete. Untick the option and save to return to schema-only validation.
How to transfer deprecated ONIX 3.0 elements
ONIX 3.1 deprecates a few ONIX 3.0 elements. With Enable Automatic Transfer of Deprecated ONIX 3.0 Elements ticked, an ONIX 3.0 file imported into the catalogue is mapped to the ONIX 3.1 counterparts, so that your data stays complete when you export to ONIX 3.1:
| Deprecated element | Where it goes |
|---|---|
TitleText | Moved to TitleWithoutPrefix when neither TitlePrefix nor TitleWithoutPrefix is present. |
SalesRestriction under PublishingDetail | Moved under the first SalesRights when no SalesRestriction exists there. |
PromotionContact | Moved to ProductContact/ProductContactName when no ProductContact is defined. |
Leave the option off if your partners still expect the ONIX 3.0 elements and you export in ONIX 3.0 only.
ONIX 3.0 or ONIX 3.1 at export time
The entry form is the same for both releases; fields that exist only in ONIX 3.1 or that are deprecated in one release carry a hint in the form. The release is chosen when the file is produced: pick the 3.0 or 3.1 action in the Actions dropdown (Exporting titles) and set ONIX 3 version on each partner (Transmit to Partners). An element that does not exist in the chosen release is left out of the file.
Tips
The ONIX 2.1 catalogue can already produce ONIX 3.0
Besides option 1, an ONIX 2.1 catalogue set up by ONIXEDIT for strict ONIX 3 validation shows the ONIX 3.0 and 3.1 export actions too. If you see them on a 2.1 list, the converter is active for you.
Options 2 and 3 are one-way
Conversion cannot be undone and an added catalogue shares your title allowance. Export a backup of your ONIX 2.1 catalogue (Exporting titles) before you convert.
Frequently asked questions
Can one catalogue hold ONIX 2.1 and ONIX 3.0 titles?
No. A catalogue is either ONIX 2.1 or ONIX 3.0. An ONIX 3.0 catalogue can import ONIX 2.1 and ONIX 3.0 files; an ONIX 2.1 catalogue imports ONIX 2.1 files only.
Where is the difference between ONIX 3.0 and ONIX 3.1?
Only at export and transmission time. An ONIX 3.0 catalogue exports to ONIX 3.0 or ONIX 3.1 from the Actions dropdown, and each partner has its own ONIX 3 version.
Can I change my mind after choosing an ONIX 3.0 option?
No. The three options of Need to work with ONIX 3.0? are offered once and the choice cannot be reversed. Read the three descriptions before clicking.
What does Best Practices add?
Additional mandatory fields and rules from the EDItEUR best practice guide, checked by validation on top of the ONIX 3.0 schema. Files that pass are accepted by the most demanding partners.