Contentserv Marketplace / Tradebyte-Connector
Paid Service
Categories: Connector
AppKey: tradebyte
Compatibility: CS16.0 and later
Developed by S.HE Business GmbH

Learn more about S.HE Business GmbH
Contact Person
Sandra Herdering


The Tradebyte ecosystem provides answers to the challenges of the digital transformation in commerce and enables the seamless interconnection of manufacturers, traders and retailers in the digital supply chain. Consistent and standardised exchange formats and transmission paths – supported end-to-end by Tradebyte – enable a fully-automatic and always synchronous data flow. Highly-scalable SaaS solutions building on the modern ecosystem, provide the necessary functions out-of-the-box. The Tradebyte ecosystem overcomes barriers and saves resources with a short time-to-market.



  • Product and article data are transferred fully automatically from Contentserv's PIM system to Tradebyte|TB.One.
  • Product data are mapped only once in Contentserv for each channel.
  • This is stored in the defined Tradebyte directory as PANDA.csv, and a fully automated upload to TB.One can take place.
  • TB.One therefore serves as a hub for exporting product and image data to the respective channels – complex mapping for each article is not necessary. New data fields and new channels must be defined only once. Everything is intermeshed to achieve effective, profitable channel connections.
  •  Our unique set-up process allows us to integrate your data without errors.



Tradebyte product values (attention: in Contentserv values are called attributes)

  • Tradebyte product values are defined.
  • Each Tradebyte value is assigned a Contentserv attribute.
  • Specific Tradebyte value options (e.g. multilingualism, multiple selection or keywords) are taken into account.


CS-Attributes - Value Mapping

  • The Contentserv attributes are mapped to the TB.One values via the connector. The mapping is shown graphically.
  • Data is automatically sent to TB.One


Export CSV

  • The export CSV includes products and articles (SKU)
  • SKUs are exported from specific favourites lists
  • Data is semi-automatically mapped against TB.ONE attributes
  • Prices and other channel-specific data are taken into account and exported for each channel
  • A studio plugin built into Contentserv tracks the export process and maps one or more record tables
  • A studio plugin built into Contentserv tracks the export process and maps one or more record tables
  • A form of log file is written for the DELTA, which enables a comparison with the previously exported data, so that TB.ONE does not export existing data again
  • The exporter initially populates a record table
  • Predefined data from Contentserv is exported and stored in the table
  • Additional scripts import the data from the table into TB.ONE
  • Data is exported via a built-in search filter in Contentserv known as a “favourites list”
  • For each sales channel and collection, one favourite is configured in Contentserv using the complex search function
  • All search criteria are stored in the favourite and it behaves dynamically. An unlimited number of criteria can be taken into account (e.g. workflow status, product class, USPs, etc.)