Content Solutions DocumentationPublished Date: September 27, 2017 Downloaded: April 3, 2026, 9:46 am |
 |
Content Solutions Documentation |
UPC/EAN
September 27, 2017
Description
The UPC (Universal Product Code) and EAN (European Article Number) are specific types of barcodes used in the United States, Canada, the United Kingdom, Australia, and in other countries for
identifying the products.
The UPC / EAN codes can be used for mapping the products to the corresponding DataSource SKUID. A SKU may have different UPC / EAN codes
however a code cannot be linked to different SKUs.
Database Structure
The UPC / EAN codes are delivered in the metamap tables.
Metamap (cds_metamap)
The metamap links UPC / EAN codes (as well as distributor part numbers, and Customer part numbers) to DataSource
SKUIDs.
|
Field Name |
Type/Lenght |
Nullable |
Field Description |
|
ProdID |
varchar(40) |
not null |
Unique product key |
|
DistiSKU |
varchar(40) |
not null |
UPC / EAN code (or Distributor part number or Customer part number) |
|
DistiID |
varchar(10) |
not null |
ID of UPC / EAN account (or a distributor or Customer account identifier) which name is |
|
Delivery: Full |
|||
Distivoc (cds_distivoc)
This table is related to the table metamap and contains UPC/EAN accounts, the distributors, customer accounts
and manufacturer names.
|
Field Name |
Type/Lenght |
Nullable |
Field Description |
|
ID |
varchar(10) |
not null |
Unique key for UPC / EAN account, the distributor, customer account or manufacturer |
|
Name |
varchar(50) |
not null |
UPC/EAN accounts, distributors, customer accounts or manufacturer names. |
|
Delivery: Full |
|||
A sample query to extract the UPC / EAN codes can be found here.