Order orderdata

Node Mandatory Data type (Length) Description
ORDER Y Start of an order
Element: ORDER_DATE Y DATE Date of the customer order if provided by the channel. Otherwise, TB.One adds the date of the import.
Element: TB_ID N INT Unique, cross-channel order number from TB.One which allows to clearly identify the order at any time. Is assigned by TB.One during the transfer of the order from the channel to TB.One and is returned as status message of the REST call. Must be referenced as <TB_ORDER_ID> in messages concerning this order.
Element: CHANNEL_SIGN N String(12) Channel sign (generally 4-letter sign)
Element: CHANNEL_ID Y String(50) Unique order ID of the distribution channel
Element: CHANNEL_NO N String(50) Order number of the distribution channel (doesn’t need to be unique, e.g. order number of a web-shop)
Element: BILL_NO N String(50) Invoice number of the channel
Element: PAID N INT Paid flag that may be send by the channel 1 = paid (confirmed order); 2 = payment loss
Element: APPROVED Y INT Approval flag of the order as release indicator for the merchant to process the order. With TB.IO always 1
Element: CUSTOMER_COMMENT N String Customer comment to the order
Element: ITEM_COUNT Y INT Number of order items Is compared to the items included in the order. At deviances occur, the order is rejected due to security reasons.
Element: TOTAL_ITEM_AMOUNT Y FLOAT Gross total of the order items (without shipping or other costs), 2 decimal places Is compared to the values included in the order. At deviances occur, the order is rejected due to security reasons.
Element: DATE_CREATED N Unix Creation date (retrieval date) of the order in TB.One