Structure of product data in the TB.CAT

The following nodes can be transferred within an exported product data catalogue. The examples of the nodes contain examples for monolingual and multilingual export. The transfer is not mixed! If the export contains several languages, all elements that can be translated are provided with translation.

Please regard the representation of the fields regarding mandatory fields/nodes! In screenshots, solid borders indicate mandatory values, broken lines indicate optional values. Within the chapters, the indication of mandatory/optional only refers to the appropriate node and not to the complete XSD. Example: At "TBCATALOG", the node "PRODUCTDATA” is shown with a dashed border. This means that this information is mandatory. Nevertheless, one level above, the complete node where "PRODUCTDATA” is part of, is indicated as optional by means of the dashed line. The result from this is: if the optional node is provided, the included "PRODUCTDATA" is mandatory. Another level above, the overall node with <SUPPLIER> and <PRODUCTDATA> is mandatory. As all sub-nodes are optional, this means that <TBCATALOG> provides at least one of the nodes <SUPPLIER> or <PRODUCTDATA>.

The information refers to the possibilities of TB.One and the standard TB.CAT. At the connection of channels, the here listed mandatory and optional fields may deviate, so that, for example, a node may be mandatory for a channel although it is not required within the TB.CAT. In addition, the field length specified in this document might differ for specific channels. This results in additional mandatory fields, i.e. the highest restriction applies. Channel-specific nodes must be added per channel.

Elements of product data