Ready for Integration?

Some preparations are necessary before you can start your TB.One integration. Check the following points and - if necessary - adjust your data so it meets the requirements.

1. Minimum Product Data Requirements

No matter which channel you are connecting, your product data must include the following information for successful integration:

•Product number: The product number is obligatory, has to be unique and must not contain space characters.

•Product activation: Products have to be activated for the respective channel.

•Brand: Products have to be assigned to a brand.

•Common/proper name: All products need a "common noun" and a "proper name", e.g. "common noun" = Sneaker, "proper name" = Air Max.

•Description: The description text for a product has to be a commercial continuous text.

•Search terms: The search terms of a product have to be significant keywords which define the product.

•Bullet points: As bullet points, product properties which consist of about 3 to 5 words and are not part of the description can be used. We recommend at least 3 bullet points per product.

2. Minimum Article Data Requirements

No matter which channel you are connecting, your article data must include the following information for successful integration:

•Article number: Every article has to have a unique article number.

•Article activation: Each article has to be activated.

•Prices: Prices have to be deposited on every article (they vary channel-specifically).

•Variants: You have to define variants, usually via size and colour.

•Stock: For the export to the channel, a positive stock has to be maintained on the article.

•EAN: Every article needs a 13-digit EAN.

•Manufacturer’s article number: If there is no manufacturer’s article number, the EAN or the article number can be used here.

3. Minimum Component and Media Requirements

No matter which channel you are connecting, your data must include the following additional information and media for successful integration:

•Mandatory components: Material and, if necessary, channel-specific mandatory components.

•Mandatory attributes: Season, gender, target group, and, if necessary, channel-specific mandatory attributes.

•Media:

oMin. 1 product image

oMin. 1 (recommended: 5) article images per variant.

oIn case of missing product media, the first article image is exported as a product image. Always comply with the specifications of the respective channel.

4. Shipping

Make the necessary arrangements to ensure a smooth shipping process:

Carrier

Make a contract with a shipping provider if you have not done so yet. Keep in mind which shipping providers are approved by the marketplaces you are connecting.

Label Printing

If you want to print shipping labels from TB.One, you have to provide information concerning the shipping number ranges you are using.

To create a shipping number range, your Solution Delivery Manager needs the following information (if you are shipping with DHL):

•User name (user name in the DHL backend)

•Password (DHL password in the DHL backend)

•DHL procedure number (2-digit; information provided by DHL)

•DHL participation number (2- digit; information provided by DHL)

•Telephone number

•Email address

•Contact person

To create a number range for return labels, your Solution Delivery Manager needs the following information (if you are shipping with DHL):

•User name (user name in the DHL backend)

•Password (DHL password in the DHL backend)

•Port ID (information provided by DHL)

•Delivery name (information provided by DHL)

5. Technical Onboarding Requirements - Brand Readiness Check

Master and Order Data

Tradebyte offers different solutions for the exchange of master and order data. You can create and maintain your data manually in TB.One. However, exchanging data via interfaces may be more convenient. Import the master data via CSV or use TB.One’s XML formats “TB.Cat” and “TB.Order” to exchange data with the software.

CSV Format

•Master data import via CSV

•Order data exchange via CSV

XML Format

•Master data import via TB.Cat

•Order data exchange via TB.Order

Required Interfaces

1.Master data interface

•Product and article data feed: Data exchange “full” once a day, ideally between 1:00 a.m. and 7:00 a.m.

•Price feed: Prices can be transferred in the product and article data feeds but you may transmit them in a separate file.

2.Transaction data interface

•Stock feed (data exchange every 15 minutes)

3.Order data interface

•Data exchange every 15 minutes

•Order notifications: DESADV/in, DESADV/out

•Order data retrieval (e.g. TB_Order.xml)

Data Exchange via SFTP

Tradebyte will forward your SFTP login data (login data include server / user / password).

•Folder "/ in“ (incoming directory): Store data you want to import in this directory (product data, media).
Attention: Content in this directory will be archived after 30 days.

•Folder "/ out" (outgoing directory): Find exported order files and PDF receipts here.
Attention: Content in this directory will be deleted after 14 days after creation.

•Folder "/ error" (error files): If errors occur during the import process, a file with error descriptions is placed in this directory.
Attention: Content in this directory will be archived after 30 days.

•Folder "/ archive" (archive): Imported data are prefixed with „done“ and automatically moved to this directory. Actively move successfully retrieved order export files to the archive directory.
Attention: Files are automatically deleted after approximately four weeks.

Data Exchange via REST-API

If you want to use the REST interface for the data exchange of stock and orders, please contact your Solution Delivery Manager.

They will provide you with the necessary details.