Product Mapping Overview

Product Mapping holds the relationship between the:

  • Online Marketplace SKU
  • Tradebox product SKU
  • Sage Product Code (where applicable)

This is an essential process (where products are being held) because Stock Keeping Units (SKUs) can often differ between platforms and systems. The Product Mapping table keeps track of how each SKU is connected so stock levels can be adjusted and passed correctly. Ideally, all SKUs would be identical across all platforms and systems, however, this is often not the case.

Product Mappings are held on an individual sales channel basis because the products you have set up could have different relationships for different platforms.

The Product Mapping Import Template article provides an overview of the import file as well as an example template CSV file.

A step by step guide on how to import the product mappings can be found in the Importing Product Mappings article.


Using Tradebox Stock Control

Tradebox's default behaviour is to automatically create a mapping where the online SKU and the Tradebox SKU are identical. If Tradebox downloads an online order with a SKU that is not in the Tradebox product list, the order will be assigned a Query status and the user will be prompted to either create a new product in Tradebox or map the downloaded SKU to an existing (non matching) Tradebox product.


Using Sage Stock Control

If Sage integration is set up, you should first of all import your products from Sage. This will automatically create a mapping between the Sage stock code and the products in Tradebox. If you download orders before doing this, the orders will all be placed into Query until the products are imported and mapped.

After the products have been imported, orders may remain in query if the product doesn't exist in Sage, or the SKU is not identical (matches are character-specific but not case-sensitive for alphabetic characters). The orders will generate a Product Mapping Issue prompting the user to create the product in Sage or map the SKU to an existing (non matching) Sage product.

Often the user may wish to create these Product Mapping relationships in advance of downloading any orders. Full details of how to do this can be found in the Importing Product Mappings article. 


Product Mapping Tables

The Product Mapping tables can be viewed via Products > Mapping > select your Sales Channel and Mapping Type from the drop down menus. The following views can be displayed:

  • All Mappings
  • Tradebox SKUs with NO mapped online marketplace SKU
  • Marketplace SKUs with NO mapped Tradebox SKU
  • Marketplace SKUs with NO mapped Sage Product

Once the filters have been applied the following screen is displayed:


This table holds the relationship between the 3 potential SKUs. The following features are also enabled/available via Product Mapping.


Many to One Relationships

The Product Mapping Table enables many to one relationships, where the different online SKUs are mapped to the same Tradebox SKU or Accounts SKU:

  • ABC1 = ABC123
  • ABC2 = ABC123
  • ABC3 = ABC123


Posting Multipliers

The Multiplier column allows the user to establish a factor by which the stock level in the downloaded online marketplace product SKU can be multiplied. Multipliers are used in cases where a user sells online in one quantity and runs the rest of their stock control in another quantity.
In our above example, the marketplace SKU BOARD_002 has a multiplier of 5; it represents a 5-pack of whiteboards on the marketplace, but in our warehouse we track them as individual unit. This might be because we buy from the supplier in crates of 100 and repackage them, or it might be because we also sell a 10-pack under a different online SKU and use the same Accounts/Tradebox product to keep accurate stock availability of both listings.

Where the stock levels are adjusted (Tradebox or Accounts) is dependent upon the Inventory Choice made when setting up the software.

When working with quantity multipliers, Tradebox still needs to be able to calculate a unit price to a whole pence. To use quantity multipliers, the quantity stated MUST be divisible by the gross product unit price, to the penny after the multiplication. 

  • Units 30 - Price £1.20 = unit price in Accounts/TB of 4 pence
  • Units 30 - Price £1 = unit price in Accounts/TB of 3.33333333 pence

If your prices aren't divisible to a whole-pence unit price, quantity multipliers are not a valid option. Instead you should look to use BOMs (Bill of Materials) where an end product is made from subcomponents. This does require one product record for each end product, so if we sell our whiteboards in 2-packs, 5-packs and 10-packs, we'd need four product records (three end products and the single where we actually track the inventory).

PO (Purchase Order) (Sage Only)

The PO function is only applicable where Tradebox is integrated with Sage 50 Accounts Professional. The feature allows the user to configure Tradebox to create a Purchase Order in Sage 50 Professional when it processes an order with the specified SKU in it.  In the Product Mapping Import Template CSV file this field is called "DirectToCustomer"

Typically, this feature is used in a drop ship environment, where the user doesn't hold the item in stock and wishes to send a PO to the supplier for dispatch directly to the buyer. For this to happen successfully, each Product Record in Sage needs to a default Supplier Record and a Cost Price.  When this feature is utilised, Tradebox will:

  • Create an individual PO in Sage for each unique product, against the Supplier account as held on the Sage Product Record.
  • Create the PO at the Cost Price held on the Sage Product Record.
  • Create the PO with the buyer's shipping address as provided by your online marketplace.

To use dropship, it must be enabled in each relevant Sales ChannelAccounts > Postings > tick the Create Purchase Orders (Dropshippers) box. You can then opt products in as dropship items by ticking the PO box against each desired SKU in Products > Mapping for each channel.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk