To be able to identify products, and match products across different channels together, SiteLucent searches a product detail page (PDP) to find the GTIN Code OR the combination: Brand + MPN.
When is mapping needed?
In most cases this product mapping process goes well. In some cases it does not, because crucial information on an eCommerce product page is missing or is displayed incorrectly. A mapping file is needed when one of the following situations occur (which makes automatic identification impossible):
- No GTIN or brand / MPN present on the PDP (nor in the underlying source code);
- Misspelled or partial MPN codes. For instance, with additional characters in between, or missing parts of the official code;
- Invalid GTIN code(s). We always check the validity of GTIN codes we find. Codes that fail the 'valid GTIN code test' get rejected, to avoid polluting our system with incorrect identifiers.
- Incorrect brand name. An MPN code is only unique in combination with the brand name. If the brand name is misspelled, or different from the official brand name, our system will 'think' it's a different product and record is as such.
Create a Mapping file
In a mapping file we link the Retailer’s Shop Product ID to the GTIN (and/or MPN-brand-combination). The Shop Product ID is a unique code that retailers use to correctly pick and ship an order.
Retrieve the retailers' Shop ID via one of these 2 options:
- Retailer's Portal: In case of Amazon: export ASINS from Vendor- or Seller Central.
- A SiteLucent CSV-export:
- Log in to your SiteLucent account.
- Enter a dashboard that contains a data table widget.
- Apply your filters: Choose the retailer that gives issues identifying products (we recommend doing one retailer at a time).
- Export the widget data into a CSV file from data table widget.
- You can find a column with the Shop Product ID in your exported file.
Next to the Shop Product ID you keep/add the columns:
- Retailer name
- GTIN (EAN, UPC)
- Brand name
- MPN (Manufacturer Product Number)
You can also use this template.
When ready, send the mapping file to your Customer Success Manager or to firstname.lastname@example.org