In the following, the nodes that may be part of an order file are described in detail. As an XSD scheme like the standard TB.ORDER is built as a tree structure, fields that occur multiple times such as <TB_ID> and <CHANNEL_ID> are only valid within the node where they occus. Thus, the TB_ID within the node ITEM is the unique ID of the article in TB.One, the TB_ID within the node ORDER is the unique ID of the order in TB.One.

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 "ORDER", the node "SELL_TO" is shown with a dashed border. This means that this information is optional. At "Shipping and accounting address – SELL_TO and SHIP_TO", the fields for first name/last name, street/number and ZIP/city/country are mandatory fields indicated by means of the solid border. The result from this is: if the optional node "SELL_TO" is provided, the included address data is mandatory.

The information refers to the possibilities of TB.One and the standard TB.Order. During the connection to a channel, channel-specific deviations may occur, e.g. for the field lengths mentioned in this document.

Elements of order data

• Order – ORDER
• Order data – ORDER_DATA
• Shipping and accounting address – SELL_TO and SHIP_TO
• Order items – ITEM