Marketplace
Tradebyte TB.One
For merchants selling across many marketplaces: TB.One is the link between merchant and marketplaces. The catalogue is built from the Commerce Bundle — the same mapping as for the shops; in the workflow the difference is another target building block.
For the order side the integration brings four data models of its own: order, order line, order message and article stock. Documents are checked against the published schema before sending; an error names the record and the field instead of “document invalid”.
An order is closed only once it has actually been stored.
- Tradebyte TB.OneMarketplace
- ConFlowIOintegration platformRun active
- Xentral
- JTL-Wawi
- Pimcore
- 12ready-made building blocks
- 21data models in the Commerce Bundle, one mapping for every target
Building blocks
Twelve building blocks for TB.One
Eight for the merchant side, four for accounts connected as a channel themselves. A merchant-only account is not authorised for the channel-side blocks.
- Hand over catalogueWrite
Hands over the catalogue from the Commerce Bundle, in full or only the changes.
- Hand over stockWrite
Hands over stock in batches.
- Read ordersRead
Reads open orders from TB.One.
- Close orderWrite
A building block of its own, placed after the step that stores the order. If storing fails, no order is lost.
- Report order statusWrite
Reports shipment, cancellation, return and deductions per item.
- Read order messagesRead
Reads messages about orders, such as cancellations and returns.
- Fetch order documentRead
Fetches a document for the order as a PDF.
- Free request
For anything without a ready-made building block: a request to the API, using the stored credentials.
- Read catalogueRead
Channel side: reads the catalogue in full or as changes since the last run, in the shape the hand-over expects.
- Read stockRead
Channel side: reads stock in full or as changes since the last run.
- Hand in orderWrite
Channel side: hands an order in to TB.One.
- Confirm message as processedWrite
Channel side: confirms a status message as processed.
In practice
Two workflows with TB.One
Collect marketplace orders
Closed only once the order has actually been stored.
- Triggera schedule
- Readopen orders from TB.One
- Hand overas a sales order to Xentral
- Closethe order at TB.One
TB.One keeps handing an order out until it is confirmed. If storing fails, nothing is closed — and no order is lost.
Catalogue to the marketplaces
The same range as in the shop, through TB.One to many marketplaces.
- Readarticles from Xentral or Pimcore
- Maponto the Commerce Bundle
- Change detectionpass on only what changed
- Hand overcatalogue to TB.One
A record that does not fit is named with its field before TB.One rejects the whole document.
Good to know
What to know about TB.One
- PrerequisitesWhat your TB.One account needs.
- A merchant account in TB.One for the eight merchant-side blocks
- For the four channel-side blocks, an account connected to TB.One as a channel
- Not coveredLimits of TB.One's API, not of ConFlowIO.
- A merchant-only account is not authorised for the four channel-side blocks
- TB.One rejects a whole document if it does not fit the published schema — so ConFlowIO checks first and names the record and the field
- TB.One keeps handing an order out until it is closed — so closing is a building block of its own, placed after storing
- DurabilityApplies to this integration as to every workflow in ConFlowIO.
- Failed steps retry themselves
- Large reads are processed page by page, each page a step of its own
- A failed run is continued rather than started over
- Live logs per step, with credentials removed
Works well with
What works with TB.One
Frequent partners
Catalogue and orders run through the Commerce Bundle.
Contact
See Tradebyte TB.One on your own data
We are glad to show ConFlowIO on your own data. Bring a real slice of your orders.
The difference shows at real volumes — not at five sample records.
Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.
Rather write directly?info@conflowio.com