Price

Because Metabooks is a price database for retail sellers and hence for consumers, only some of the values possible in ONIX are of use.
Metabooks price information must always include the type of price, an amount, the applicable VAT as well as the area of validity. Additional optional elements are also available.

• Type of price
• Price Qualifier
• Notes on price
• Quantity
• Temporary prices
• Amount
• Value-Added Tax
• Currency
• Country and Region
• Period of validity
• Unpriced Items
• Examples

The type of price defines what kind of price the Price Composite contains. It determines whether the price described is a subscription price, retail price, special price, etc. whether it is subject to fixed pricing and whether it is a gross or net price.

Products may, in accordance with ONIX specifications, have a fixed set of price types (Code list 58) You can send any of these price types to Metabooks, although only Metabooks relevant prices will be shown, while all price types may be exported. The Yellow Supplement and price reference feed use Metabooks-relevant prices exclusively, however.

Metabooks relevant price types are always gross prices (incl. VAT), which is why the Metabooks nomenclature does not include any information on whether the price given includes VAT.

Retail prices are to be assigned the following price types in Metabooks.

Special prices are generally identified in Metabooks by the price type 12. A specific type of special price may be defined by additionally entering price qualifiers, or by adding an indication of quantity. Metabooks-relevant price types include the following.

A retail price including VAT is to be specified as follows:

<x462>02</x462>

<PriceType>02</PriceType>

Selected price types may be further specified by the use of a price qualifier (PriceQualifier or j261). Values for this field may be found on code list 59. In Metabooks, price qualifiers serve to declare individual special prices

A special price available only when procuring the entirety of a work is to be declared as follows.

<j261>03</j261>

<PriceQualifier>03</PriceQualifier>

Notes on prices should only be added if the desired pricing information cannot be provided using the available price elements and codes.

Particularly for special prices, a complementary note explaining in greater detail the conditions qualifying the customer for the special price may be helpful.

A supplementary note for a member price could look as follows.

<j262>just a note</j262>

<PriceTypeDescription>just a note</PriceTypeDescription>

By defining a certain quantity (MinimumOrderQuantity or j263) within a special price, you clarify that this price is valid only if this quantity is ordered. Defining a quantity typifies a special price as a volume price, and is permitted only in the special prices section.

A volume price for ordering 50 units is to be entered as follows

<j263>50</j263>

<MinimumOrderQuantity>50</MinimumOrderQuantity>

Pre-announcements often do not yet have a definite price. Because Metabooks always requires listing a price, you can mark a price as temporary This tells the customer that the stated amount is an approximation, rather than a set price.

Whether a price is temporary or fixed is entered into PriceStatus or j266 . No entry as well as the value “00” are interpreted by Metabooks as fixed prices.

Temporary prices are to be entered as follows.

<j266>01</j266>

<PriceStatus>01</PriceStatus>

Each price must have a set amount. For ONIX 3.0, this amount is entered into PriceAmount or j151.

For a product to be sold for a price of 9.99, the amount is to be entered as follows.

<j151>9.99</j151>

<PriceAmount>9.99</PriceAmount>

Metabooks allows VAT only for the following countries: Germany, Austria, Switzerland and Brazil. For other countries, entering VAT into Metabooks is not possible. This is because Metabooks relays VAT rates to the bookselling trade, and guarantees the accuracy of the relayed data. The selected countries encompass the primary markets of Metabooks as well as of Metabooks. As soon as the VAT rates in one of these countries changes, all prices listed in Metabooks will be corrected to the new rate.

VAT data contains coded date on the type of VAT (reduced or full) in addition to the relevant VAT rate as a percentage. In ONIX 3.0, VAT data is to be entered in the tax composite, which is part of the price composite. The type of VAT is found in TaxRateCode or x471 and the relevant rate in TaxRatePercent or x472. In both formats, VAT is defined by codes from Code list 62.

In ONIX 3.0, the tax composite also contains the element TaxType or x470 . Please enter the value “01” from code list 171 to indicate that you are providing VAT data.

For Germany Austria and Switzerland, there are default settings in Metabooks which VAT rates apply, depending on product form. These default settings are not mandatory, but considered a recommendation.

If no VAT for one of these countries is listed for a product, Metabooks will automatically use the default values, in accordance with the product form. There is also a warning if a VAT rate differs from the default.

A product to which the reduced VAT rate of 7% applies is to be entered as follows.

<tax>
 <x470>01</x470>
 <x471>R</x471>
 <x472>7</x472>
</tax>

<Tax>
 <TaxType>01</TaxType>
 <TaxRateCode>R</TaxRateCode>
 <TaxRatePercent>7</TaxRatePercent>
</Tax>

Each price listing must include currency information for the price in the defined country. VLB does check whether the currency fits the country and points out any inconsistencies, however, it may be explicitly desired to trade a product for a different currency than that of the target country.

Currency is defined in CurrencyCode or. j152 using values from code list 96.

For each price, information regarding geographic validity is required. This may be provided by defining a region or country.

ONIX 3.0 requires country or region information to be listed in the territory composite. Countries may be listed in CountriesIncluded or x449 or x449 using valued from code list 91 , while regions may be listed in RegionsIncluded or x450 using values from code list 49 .

Metabooks allows only positive reports for areas of validity. Using CountriesExcluded or. x451 and RegionsExcluded or x452 in ONIX 3.0 is impermissible and will lead to the title being refused.

A price declaration intended for the bookselling trade in Switzerland must be declared as follows.

<territory>
 <x449>CH</x449>
</territory>

<Territory>
 <CountriesIncluded>CH</CountriesIncluded>
</Territory>

If a price declaration is identical for multiple countries, you can list all respective countries in a price composite. In ONIX 3.0 merely the codes for CountriesIncluded or x449.

If all Euro countries except Germany and Austria are to use the same price, the country information is to be provided as follows.

<territory>
 <x449>BE CY EE ES FI FR GR IE IT LT LU LV MT NL PT SI SK</x449>
</territory>

<Territory>
 <CountriesIncluded>BE CY EE ES FI FR GR IE IT LT LU LV MT NL PT SI SK</CountriesIncluded>
</Territory>

Generally, Metabooks supports regional listings. We explicitly recommend adding country information to all price listings, because these are reliably evaluated and processed by the bookselling trade. Regional codes which often limit the price listed to one part of a country are not necessarily correctly interpreted by the bookselling trade.

One regional code established in practice is ROW (Rest Of World). Using this code tells booksellers that unless there is a price listing for the sellers’ specific place of business, he may offer it to customers at the “ROW price” in the currency listed.

The regional code ROW is to be entered as follows.

<territory>
 <x450>ROW</x450>
</territory>

<Territory>
 <RegionsIncluded>ROW</RegionsIncluded>
</Territory>

Each price may be listed with a specific period of validity. To do so, a starting date and an end date are to be provided. Using this technique, you may define subsequent price listings for your product. Each subsequent price automatically activates at the listed start date.

Start and end dates are to be provided accurate to the day in Metabooks. For each validity date, a PriceDate composite is to be created in ONIX 3.0 Using values from code list 173 and the PriceDateRole or x476, this defines whether it is a start date, end date or a combined listing.

The actual dates are to be listed in Date or b306 . For any date, supplementary information regarding the date format should be added using the date format attribute with values from code list 55.

Separately defined start and end dates are to be given a value of 00 (YYYYMMDD); combined entries a value of 06 (YYYYMMDDYYYYMMDD).

The temporary validity of a price listing from January 1st, 2018 to December 31st, 2018 is to be entered as follows.

<pricedate>
 <x476>14</x476>
 <b306 dateformat="00">20180101</b306>
</pricedate>
<pricedate>
 <x476>15</x476>
 <b306 dateformat="00">20181231</b306>
</pricedate>

<pricedate>
 <x476>24</x476>
 <b306 dateformat="06">2018010120181231</b306>
</pricedate>

<PriceDate>
 <PriceDateRole>14</PriceDateRole>
 <Date dateformat="00">20180101</Date>
</PriceDate>
<PriceDate>
 <PriceDateRole>15</PriceDateRole>
 <Date dateformat="00">20181231</Date>
</PriceDate>

<PriceDate>
 <PriceDateRole>24</PriceDateRole>
 <Date dateformat="06">2018010120181231</Date>
</PriceDate>

Unpriced Items are an exception. This information must be explicitly provided in the product in place of the price listing. In ONIX 3.0, you may do this using UnpricedItemType or j192 while selecting the reason (code list 57).

Products that are free of charge must have the following entry instead of the price.

<j192>01</j192>

<UnpricedItemType>01</UnpricedItemType>

Price listing without separately listed VAT

<price>
 <x462>04</x462>
 <j266>02</j266>
 <j151>22.99</j151>
 <tax>
 <x470>01</x470>
 <x471>R</x471>
 <x472>7</x472>
 </tax>
 <j152>EUR</j152>
 <territory>
 <x449>DE</x449>
 </territory>
 <pricedate>
 <x476>14</x476>
 <b306 dateformat="00">20180101</b306>
 </pricedate>
 <pricedate>
 <x476>15</x476>
 <b306 dateformat="00">20181231</b306>
 </pricedate>
</price>

<Price>
 <PriceTypeCode>04</PriceTypeCode>
 <PriceStatus>02</PriceStatus>
 <PriceAmount>22.99</PriceAmount>
 <Tax>
 <TaxType>01</TaxType>
 <TaxRateCode>R</TaxRateCode>
 <TaxRatePercent>7</TaxRatePercent>
 </Tax>
 <CurrencyCode>EUR</CurrencyCode>
 <Territory>
 <CountriesIncluded>DE</CountriesIncluded>
 </Territory>
 <PriceDate>
 <PriceDateRole>14</PriceDateRole>
 <Date dateformat="00">20180101</Date>
 </PriceDate>
 <PriceDate>
 <PriceDateRole>15</PriceDateRole>
 <Date dateformat="00">20181231</Date>
 </PriceDate>
</Price>

Price listing without separately listed VAT

<price>
 <x462>04</x462>
 <j266>02</j266>
 <j151>22.99</j151>
 <tax>
 <x470>01</x470>
 <x471>R</x471>
 <x472>7</x472>
 <x473>17.19</x473>
 <x474>1.20</x474>
 </tax>
 <tax>
 <x470>01</x470>
 <x471>S</x471>
 <x472>19</x472>
 <x473>3.87</x473>
 <x474>0.73</x474>
 </tax>
 <j152>EUR</j152>
 <territory>
 <x449>DE</x449>
 </territory>
 <pricedate>
 <x476>14</x476>
 <b306 dateformat="00">20180101</b306>
 </pricedate>
 <pricedate>
 <x476>15</x476>
 <b306 dateformat="00">20181231</b306>
 </pricedate>
</price>

<Price>
 <PriceTypeCode>04</PriceTypeCode>
 <PriceStatus>02</PriceStatus>
 <PriceAmount>22.99</PriceAmount>
 <Tax>
 <TaxType>01</TaxType>
 <TaxRateCode>R</TaxRateCode>
 <TaxRatePercent>7</TaxRatePercent>
 <TaxableAmount>17.19</TaxableAmount>
 <TaxAmount>1.20</TaxAmount>
 </Tax>
 <Tax>
 <TaxType>01</TaxType>
 <TaxRateCode>S</TaxRateCode>
 <TaxRatePercent>19</TaxRatePercent>
 <TaxableAmount>3.87</TaxableAmount>
 <TaxAmount>0.73</TaxAmount>
 </Tax>
 <CurrencyCode>EUR</CurrencyCode>
 <Territory>
 <CountriesIncluded>DE</CountriesIncluded>
 </Territory>
 <PriceDate>
 <PriceDateRole>14</PriceDateRole>
 <Date dateformat="00">20180101</Date>
 </PriceDate>
 <PriceDate>
 <PriceDateRole>15</PriceDateRole>
 <Date dateformat="00">20181231</Date>
 </PriceDate>
</Price>