TB.One > Setup, Configuration & User Accounts > Getting Started > Connecting TB.One
At its core, connecting to TB.One requires the following steps:
1. CONCLUSION OF CONTRACT
Once you have contacted our Sales & Account Team and decided to use TB.One, you need to set up a basic contract with Tradebyte and book your sales channels. Depending on the channel or channels you are interested in, another contract with the channel(s) and, where applicable, a clarification of the commodity range in question may be required. For channels with special requirements, separate integration guides are available in the section "Channel documentation".
2. START OF THE INTEGRATION PHASE
The Tradebyte integration team will guide you through the preparatory phase. Tradebyte will set up your TB.One account and activate the booked channels. If the booked channels provide a test connection, Tradebyte will set up the test login and forward the credentials to you. Send the credentials you receive from the channel to Tradebyte by e-mail.
3. BASIC CONFIGURATION OF TB.ONE
Your Tradebyte Solution Delivery Manager will provide links to the basic documentation and the documentation(s) for your booked channels. During the configuration phase, engage yourself intensively in the "First set-up and configuration", especially the pages "Preliminary Considerations Regarding Master Data" and "Preliminary Considerations Regarding Order Processing" and their linked pages. Together with your Solution Delivery Manager, you will then configure the basic settings described in "Basic Master Data Configuration" and analyze what product data you can provide in which way.
During this step, you will also decide which interface you will use to transfer your product data to TB.One, and whether you generally work manually in TB.One's UI, or if you will use the interface function to work via a dedicated ERP system. This decision is not necessarily permanent and may be reevaluated at a later date. You can always switch to another way of data maintenance or use different methods for different types of data.
4. DATA CREATION/MAINTENANCE
In this step, you build up your product data. Try to make your data as universally applicable as possible while taking the channel requirements described in the respective channel documentation into account. If you create your master data manually, you need to create the basic values for attributes, components, brands, and other information first. The sequence and contents are described on the page "Manual Master Data Creation" and itIs linked pages.
If you want to import your product data catalog, you can choose to either use a CSV document or an XML file and deliver it via TB.One's SFTP access. The required settings in TB.One for exchanging data by import file are described here.
5. CHANNEL-SPECIFIC ADJUSTMENTS
After master data creation, configure the product data in TB.One per channel and assign them according to the channels' specifications:
•Assign primary channel categories for the channels' store navigation
•Map your component and attribute values to those defined by the channels
•Activate payment and shipping types for each channel
•Keep the channels' requirements regarding product and article images in mind
•If you plan on printing order documents (invoice, delivery note, etc.) via TB.One, configure them
TIP: |
Details for each channel's requirements can be found in the section "Channel documentation".
6. INITIAL DATA EXPORT
Once the preparation of data and the channel-specific adjustments are done, it is time for the initial data export. The type and destination of this export depend on the channel. If a test system is available, the initial export will target that system. Some channels check the data for content and quality before GoLive (e.g. Zalando and eBay). If you have booked one of those channels, we will send you a filled CSV file. You have to remove all third-party information that is irrelevant for the channel in question (e.g. other channels' prices). The file will then will be submitted to the channel for review.
This initial data export may create entries in the SolutionCenter. Improve your data until all entries are resolved and exports no longer create new entries. During the integration phase, you should not only work on errors but also on warnings and notes/hints. This will help you produce consistently "clean" data. In rare cases, channels may demand data adjustments, which you also need to implement.
7. TEST ORDERS
Some channels send a test order after checking your data (some even require actual shipment of the goods). You should also test your procedures regarding order processing. We will create some test orders for your system if needed. Note that some channels automatically cancel orders if they are not completed within a defined time frame (usually 6-10 days).
8. GO-LIVE
When the initial data export was completed successfully, and the error list in the SolutionCenter is cleared, your products will go live on the respective channel. Some channels will activate your data manually bit by bit. Others release everything automatically.
For channels with a test system, Tradebyte will switch the export to the live system. If this is the case, you may need to manually enter the credentials for your channel account in the system. At this point, the integration phase is complete, and your goods are available on the channel.
Once you have reached that stage, our Support Team will be happy to help you with any questions, suggestions, or problems.
9. RECEIVING AND PROCESSING ORDERS
When one of the channels receives an order for your products, it will transfer the order to TB.One. Depending on your settings made during the integration phase, the order may be exported directly to your ERP system or manually processed in TB.One. If you chose the export via REST, your system must return the message "order exported" to TB.One.
If you process orders manually, you have to do so via the order list or the scan desktop. If you can fulfill the order, send a delivery message (dispatch advice) to the channel via TB.One, in addition to shipping the physical goods. Should you not be able to fulfill the order, send a cancellation message. Depending on your configuration, print the necessary documents for the order (e.g. delivery note, order data sheet, pick list, product labels, invoice, shipping label or package list) either manually or automatically.
Some channels will notify you about received orders before the order is paid and released. TB.One shows these orders as so-called "pending orders" and automatically reserves stock to ensure that the orders can be fulfilled upon release.
A detailed description of manual order processing can be found here.
For further information, see also:
•Basic configuration of master data
•Manual master data maintenance
•Master data import via CSV
•Master data import via XML
•Order processing in TB.One (general)
•Manual order processing
•Order data exchange via CSV
•Order data exchange via XML