• Datamaps provide a configurable way to control how the connector handles your stores product information. 
  • In simple terms, they control ‘what information goes where’ (part 1) when the connector communicates between REX and your eCommerce store, and ‘when’ that information is communicated (part 2). 
  • You can communicate with us to find a customisation to suit your specific needs.
  • You can not alter the data map yourself as changes require co-ordination with the integration process and timing.

Your datamap format will look like this (information included differs depending on your eCommerce platform):

*Store Table/TableName can be safely ignored


Part 1: Matching fields

The datamap determines which fields from a product’s information in REX is synced with your store, and where that information is placed (mapped) to in your eCommerce store. 

e.g., the below datamap means that the information in the “Description” field in Retail Express is equivalent to the “Title” field in your eCommerce site.


Part 2: Syncs

The connector offers three types of synchronisations:

  • New product sync (creation of a new product in your store from your REX data)
  • Product update sync (not available to some eCommerce platforms)
  • Stock and pricing sync 

The information included in these syncs is controlled by the datamap. A ‘Y’ in a row indicates that field is included in the corresponding sync.

e.g. For "Description"/"Title":

  • For a new product created with the datamap below, the information in the “Description” field in Retail Express would be entered into to the field “Title” in your eCommerce site. 
  • If a product update was performed on that product, the “Title” in your eCommerce store would be updated (i.e. overwritten) with whatever information was currently in the “Description” field. 
  • The “Title” field would be ignored in a stocksync. 
    • “Stock_Quantity” would be updated in a stock sync, but left alone in a product update.

Some information is always automatically included, without being listed in the datamap. For example, Supplier and Manufacturer SKUs are hard wired for products, and pricing is updated alongside stock syncs according to the normal REX hierarchy. (See https://translatorhq.freshdesk.com/en/support/solutions/articles/19000089029-how-do-i-set-sell-prices-for-my-ecommerce-store-  )