TB.One > Order Data and Order Processing > Order Processing via CSV > Message Data Fields (CSV)

Message Data Fields (CSV)

Via the interface, you can either mark entire orders as delivered (DESADV_ORD), or report the status (delivered, canceled, returned) of each item in detail (DESADV_POS).
Fields with green backgrounds are system fields. They are created and filled by TB.One automatically.

TIP:
The first row of the CSV file is ignored because it must always contain the column headings.

An example for a CSV message file can be found here.

1. MESSAGES AT ITEM LEVEL

File name: DESADV_POS_{timestamp}.csv

FIELD NAME	REQUIRED	DATA TYPE	DESCRIPTION
TB_ORDER_ID	Y	INT	Order ID; a unique order number assigned by TB.One
ORDER_PAID	N	INT	Order was paid; possible values: 0 = no 1 = yes 2 = payment loss If no value was provided, TB.One assumes "0"
POS_TB_ID	Y	INT	Unique number of the item (across all orders)
POS_ANR	Y	CHAR(50)	Article number
SHIP_QUANTITY	Y	INT	Delivery quantity
DIFF_QUANTITY	N	INT	Canceled quantity
TYPE	N	CHAR(20)	Message type; only if DIFF_QUANTITY > 0 diff_stock = cancellation (stock) diff_customer = cancellation (customer) If no value was provided, TB.One assumes "diff_stock"
RETURN_QUANTITY	N	INT	Return quantity
RETURN_CAUSE	N	CHAR(50)	Import key of the return cause
RETURN_STATE	N	CHAR(50)	Import key of the return state
PARCEL_TYPE	Y	CHAR(50)	Package type of the shipped article. Enter the import key of the package type stored in TB.One. For historical reasons, the values listed below are still accepted by TB.One. The software will try to match them to an import key: DHL_STD = DHL standard package DHL_LAN = DHL long package SPED = forwarding agent delivery SONSTIGER = other modes of transport
SHIP_CODE	N	CHAR(30)	Carrier's tracking number
IDCODE_RETURN_PROPOSAL	N	CHAR(30)	Proposed return code from a provided number range
COMMENT_INTERN	N	CHAR	Internal comment on the order. If provided in the CSV, preexisting comments will be overwritten.
DEDUCT_SHIPPING	N	FLOAT	Shipping cost discount (=amount to be credited)
ACK_QUANTITY	N	INT	Order confirmation
EST_SHIP_DATE	N	DATE(yyyy-mm-dd)	Along with the column "ACK_QUANTITY" you may transfer the estimated delivery date
COMMENT	N	CHAR	Comment regarding the message
MESSAGE_CHANNEL_DATA[key]	N	CHAR(50)	Can be used differently, depending on the channel. Ensure to provide the correct key. To indicate a warehouse location: Enter your ID for the corresponding warehouse location for each item (key= logistic_center_id).

TIP:
TB.One adds up reported quantities ("SHIP_QUANTITY", "DIFF_QUANTITY", "RETURN_QUANTITY"). Partial deliveries must, therefore, be reported in separate lines containing the respective quantity (instead of indicating the status of the overall position).
Example:
The ordered quantity ("POS_QUANTITY") is 10. The order is delivered in two packages, each containing 5 articles. In the CSV, this would be represented by two lines, each of which contains the value "5" for in the column "SHIP_QUANTITY".

If the field "PARCEL_TYPE" is not specified, TB.One will assume the default package type set in TB.One was used. If the field "SHIP_CODE" is not transmitted, the tracking number from the respective channel's order data will be assumed to be valid.

TIP:
For the optional field "DIFF_QUANTITY" the following behaviour can be activated in TB.One:
If less than the ordered quantity is shipped for a position, the software automatically generates a cancellation message for the missing amount.

Example:

The ordered quantity ("POS_QUANTITY") is 5. The quantity reported as shipped ("SHIP_QUANTITY") is 3. If the respective option is activated in TB.One, a quantity of 2 will be automatically reported to the channel as canceled.

If you merely want to set the payment status to "paid", the quantity fields can be left empty. If multiple messages are sent for one order, the current payment status must always be included.

2. MESSAGES AT ORDER LEVEL

If you cannot create dispatch advices that address the individual order positions specifically, you may report entire orders as "shipped". DESADV_ORD messages create dispatch advices for all open positions and quantities of an order.

File name: DESADV_ORD_{timestamp}.csv

FIELD NAME	REQUIRED	DATA TYPE	DESCRIPTION
TB_ORDER_ID	Y	INT	Order ID, a unique number from TB.One, relating to the order.
ORDER_PAID	Y	INT	Order was paid; possible values: 0 = no 1 = yes 2 = payment loss If no value was provided, TB.One assumes "0" .
TYPE	Y	CHAR(20)	Message type ship = order shipped diff_stock = cancellation (stock) diff_customer = cancellation (customer) If no value was provided, TB.One assumes "ship" .
PARCEL_TYPE	N	CHAR(50)	Package type. Enter the import key stored in TB.One. For historical reasons, the values listed below are still accepted by TB.One. The software will try to match them to an import key: DHL_STD = DHL standard package DHL_LAN = DHL long package SPED = forwarding agent delivery SONSTIGER = other modes of transport
SHIP_CODE	N	CHAR(30)	Carrier's tracking number.
IDCODE_RETURN_PROPOSAL	N	CHAR(30)	Proposed return code from a provided number range.
COMMENT_INTERN	N	CHAR	Internal comment on the order. If provided in the CSV, preexisting comments will be overwritten.
COMMENT	N	CHAR	Comment regarding the message.

For further information, see also:

•Order processing and messages via CSV - overview

•Files and naming conventions for orders and messages (CSV)

•Order data fields (CSV)