TB.One > Import & Export > Master Data Import via TB.Cat/XML > Master Data Import via XML - Files and Naming Conventions

Master Data Import via XML - Files and Naming Conventions

The Tradebyte standard for transferring product data is called TB.Cat. XML files must be checked for their schema validity before transmitting them to TB.One, regardless of the interface you use.

The current XML schemata can be found at the following locations:

TB.Cat v. 1.2:

https://api.core.tradebyte.com/schema/all_in_one/tb-cat_1_2_import.xsd

TB.Cat v. 1.3:

https://api.core.tradebyte.com/schema/all_in_one/tb-cat_1_3_import.xsd

TB.Cat v. 1.4:

https://api.core.tradebyte.com/schema/all_in_one/tb-cat_1_4_import.xsd

 

Import files for product data must be designated as follows:

TBCAT_{timestamp}.xml

TBCAT_

Identification as a product catalog

{timestamp}

Timestamp
You may choose the configuration of the timestamp. However, the following structure is recommended:
YearMonthDay_HourMinuteSecond (e.g. "20200812_124501").

.xml

File extension

 

ATTENTION:
Files containing the word "test" in their name are not imported. They are exclusively used for the purpose of testing the connection.

In order to avoid an overlap of upload and import processes, you need to upload the files with the extension ".tmp" and rename them once they have been successfully uploaded.

PRICE INFORMATION ONLY

To only update the price information, it is not necessary to provide a complete TB.Cat. Instead, you can transmit a TB.Cat file that only contains the article numbers and price information.

The naming convention for price files is the same as for the regular TB.Cat:

TBCAT_{timestamp}.xml

TBCAT_

Identification as a product catalog

{timestamp}

Timestamp
You may choose the configuration of the timestamp. However, the following structure is recommended:
YearMonthDay_HourMinuteSecond (e.g. "20200812_124501").

.xml

File extension

 

ATTENTION:
The way you need to structure these price data XMLs differs depending on the version of your TB.Cat (see table below).

 

TB.CAT VERSION

PRICE INFORMATION

1.2/1.3

Whether TB.One treats your prices as channel-specific or price-list-specific depends on the attribute "channel" in the node <A_PRICE>. If you provide a channel sign for this attribute, the prices are channel-specific. If you provide a price list key, they are price-list-specific.

TIP:
Wheter the data are channel- or price-list-specific is determined by the attribute "channel" in the node <A_PRICE>:

<?xml version="1.0" encoding="UTF-8"?>

<TBCATALOG>

<ARTICLEDATA>

<ARTICLE>

<A_NR>FBUSB-4R/A_NR>

<A_PRICEDATA>

<A_PRICE channel="listone" currency="EUR">

<A_VK>8.99</A_VK>

<A_VK_OLD>15.99</A_VK_OLD>

<A_UVP>18.99</A_UVP>

<A_MWST>2</A_MWST>

</A_PRICE>

</A_PRICEDATA>

</ARTICLE>

</ARTICLEDATA>

</TBCATALOG>

For a description of the nodes, see <A_PRICEDATA> for TB.Cat 1.2.

1.4

TIP:
Price data only, without price list:

<?xml version="1.0" encoding="UTF-8"?>

<TBCATALOG>

<ARTICLEDATA>

<ARTICLE>

<A_NR>FBUSB-4R/A_NR>

<A_PRICEDATA>

<A_PRICE channel="zade" currency="EUR">

<A_VK>8.99</A_VK>

<A_VK_OLD>15.99</A_VK_OLD>

<A_UVP>18.99</A_UVP>

<A_MWST>2</A_MWST>

</A_PRICE>

</A_PRICEDATA>

</ARTICLE>

</ARTICLEDATA>

</TBCATALOG>

TIP:
Price data only, with price list:

<?xml version="1.0" encoding="UTF-8"?>

<TBCATALOG>

<ARTICLEDATA>

<ARTICLE>

<A_NR>FBUSB-4R/A_NR>

<A_PRICEDATA>

<A_PRICELIST key="cutbtradi1">

<A_VK>9.99</A_VK>

<A_VK_OLD>12.99</A_VK_OLD>

<A_UVP>14.99</A_UVP>

<A_MWST>2</A_MWST>

</A_PRICELIST>

</A_PRICEDATA>

</ARTICLE>

</ARTICLEDATA>

</TBCATALOG>

For a description of the nodes, see <A_PRICEDATA> for TB.Cat 1.4.

 

STOCK INFORMATION ONLY

If you only want to update the stock information, it is not necessary to provide a complete TB.Cat. It is sufficient to transfer only the relevant information. The current XML schema can be found at:

https://api.core.tradebyte.com/schema/all_in_one/tb-stock_all_in_one.xsd

Naming convention for stock files:

TBCAT_stock_{timestamp}.xml

TBCAT_stock

Identification as a stock catalog

{timestamp}

Timestamp
You may choose the configuration of the timestamp. However, the following structure is recommended:
YearMonthDay_HourMinuteSecond (e.g. "20200812_124501").

.xml

File extension

 

Example XML: One central warehouse (referencing by A_NR)

<?xml version="1.0" encoding="UTF-8"?>

<TBSTOCK>

 <ARTICLE>

         <A_NR>3810blM</A_NR>

         <A_STOCK>15</A_STOCK>

 </ARTICLE>

</TBSTOCK>

 

Example XML: One central warehouse (referencing by A_EAN)

<?xml version="1.0" encoding="UTF-8"?>

<TBSTOCK>

 <ARTICLE>

         <A_EAN>4003423414351</A_EAN>

         <A_STOCK>15</A_STOCK>

 </ARTICLE>

</TBSTOCK>

 

Example XML: Several warehouses (see "storage facilities")

<?xml version="1.0" encoding="UTF-8"?>

<TBSTOCK>

 <ARTICLE>

         <A_NR>3810blM</A_NR>                                        

         <A_STOCK identifier="key" key="Zentrallager">10</A_STOCK>

         <A_STOCK identifier="key" key="Außenlager 1">5</A_STOCK>

 </ARTICLE>

</TBSTOCK>

 

 

 

<!-- alternative: <A_EAN>4003423414351</A_EAN> -->

For further information, see also:

•Master data import via XML - overview

•Examples: XML for TB.Cat 1.2 or TB.Cat 1.4