Unified_Product_Catalog Table¶

The Unified_Product_Catalog table contains a row for every item in your product catalog, including descriptive attributes, such as name, brand, size, and color, grouping attributes, such as category, sub-category, class, and sub-class, and other attributes like MSRP, gender, and description.

Important

The Unified_Product_Catalog table represents the taxonomy for your products and brands. Attributes are added to the Unified_Product_Catalog table when pc/ semantic tags are applied to your data sources. All pc/ semantic tags are optional. Use the ones that best define the shape of your product catalog and best describe the individual items within it. The product ID is used as an input to AmpIQ predictive modeling.

Add table¶

The Unified_Product_Catalog table is a required table for the customer 360 database when transactions and itemized transaction data is available to your tenant and fields are tagged with pc/ semantic tags. The Unified_Product_Catalog table is built as a passthrough table from Stitch output.

To add the Unified_Product_Catalog table

From the Customer 360 tab, under All Databases, select the menu for the customer 360 database, and then click Edit.
From the Database Editor, click Add Table.
Name the table “Unified_Product_Catalog”.
Set the build mode to Passthrough.
From the Source Table drop-down, select the Unified_Product_Catalog table.
Click Next.
Add a table description. This enables a tooltip that is visible from other areas in Amperity.
Verify that semantic tags were applied correctly.

Tip

You can clear incorrectly tagged semantics individually or for the entire table. To clear semantic tags for the entire table, under Semantic Suggestions click Clear semantics.
From the Table Semantics drop-down, select Unified_Product_Catalog.
Click Save.

Define product catalog¶

A product catalog must be defined, and then joined to the Unified_Itemized_Transactions table.

A data source must be available with product catalog semantic tags applied.

Note

Amperity documentation refers to this data source as the Unified_Product_Catalog table, but it may have a different name in your tenant.
Apply the product-id semantic tag to product catalog data as required for AmpIQ predictive modeling; the product-category, product-description, and product-subcategory semantic tags are optional.

Important

Product affinity modeling requires the field that defines product categories – product-category in the Unified_Product_Catalog table – to contain between 20 and 2000 unique values.
A list of custom attributes may be defined. These must be available as columns in the Customer 360 database and must be added to the Unified_Itemized_Transactions table.
Tables that define product catalog semantic tags and custom attributes are managed as a data source (and associated feed) and should be maintained as part of your organization’s regular Amperity workflow.

Extend the Unified_Itemized_Transactions to include the taxonomy that defines your products and brands:

Add the column to which the product-id semantic tag was applied
Add other columns to which product catalog semantic tags were applied
Add any columns that define custom attributes, as necessary

The following example extends the Unified_Itemized_Transactions table using a table named Unified_Product_Catalog that has columns for each of the optional product catalog semantic tags:

SELECT
  uit.*
  ,upc.product_category AS `product_category`
  ,upc.product_description AS `product_description`
  ,upc.product_subcategory AS `product_subcategory`
FROM Unified_Itemized_Transactions uit
LEFT JOIN Unified_Product_Catalog upc ON uit.product_id = upc.product_id

Some brands require a single parameter to define a taxonomy and some require more than one. The following example shows a taxonomy that defines custom attributes for a class and subclass:

SELECT
  uit.*,
  ,product_class AS `product_class`
  ,product_subclass AS `product_subclass`
FROM Unified_Itemized_Transactions uit
LEFT JOIN Product_Metadata pm ON uit.product_id = pm.product_id
WHERE uit.is_return IS NULL AND uit.is_cancellation IS NULL
AND uit.item_revenue >= 0

Important

Every brand is unique. Discuss with your Amperity representative how to extend the Unified_Itemized_Transactions table to support the taxonomy that is required for your products and brands.

Column reference¶

The Unified_Product_Catalog table contains the following columns:

Column Name	Data type	Description
datasource	String	The name of the data source from which this customer record originated. Tip The combination of pk and datasource uniquely identifies a row in the Unified_Coalesced table, which correlates to a single row in a domain table.
pk	String	The combination of data source and primary key allows Amperity to uniquely identify every row in every data table across the entirety of customer data input to Amperity. Tip The combination of pk and datasource uniquely identifies a row in the Unified_Coalesced table, which correlates to a single row in a domain table.
product_brand	String	The brand name of a product or item.
product_brand_id	String	The ID for the brand name of a product or item.
product_category	String	This column is input to AmpIQ predictive modeling when joined to Unified_Itemized_Transactions. A category to which the product belongs.
product_category_id	String	The ID for the category to which a product belongs.
product_class	String	The name of the class (or grouping) to which a product or item belongs.
product_class_id	String	The ID for the name of the class (or grouping) to which a product or item belongs.
product_collection	String	The name of the collection to which a product or item belongs.
product_collection_id	String	The ID for the name of the collection to which a product or item belongs.
product_color	String	The color of a product or item.
product_color_id	String	The ID for the color of a product or item.
product_department	String	The department to which a product or item belongs.
product_department_id	String	The ID for the department to which a product or item belongs.
product_description	String	This column is input to AmpIQ predictive modeling when joined to Unified_Itemized_Transactions. A description of the product.
product_division	String	The division to which a product or item belongs.
product_division_id	String	The ID for the division to which a product or item belongs.
product_fabric	String	The fabric used for a product or item.
product_fabric_id	String	The ID for the fabric used for a product or item.
product_gender	String	A list of gender options for products. For example: F, M, unisex, NULL (for unknown).
product_group	String	The group to which a product or item belongs.
product_id	String	The unique identifier for a product. Values in this column depend on fields that are tagged with the pc/product-id semantic.
product_material	String	The material used for a product or item.
product_material_id	String	The ID for the material used for a product or item.
product_msrp	String	The manufacturer’s suggested retail price (MSRP) for a product or item. The manufacturer’s suggested retail price (MSRP) is the price before shipping costs, taxes, and/or discounts have been applied. MSRP is sometimes referred to as the base price.
product_name	String	The name of the product or item.
product_season	String	The season to which a product or item is associated.
product_season_id	String	The ID for the season to which a product or item is associated.
product_silhouette	String
product_size	String	The size of a product or item.
product_size_id	String	The ID for the size of a product or item.
product_sku	String	The stock keeping unit, or SKU, for the product or item. A stock keeping unit (SKU) is an identifier that captures all of the unique details of any individual product, including specific attributes that differentiate by color, size, material, and so on.
product_style	String	The style of a product or item.
product_subcategory	String	This column is input to AmpIQ predictive modeling when joined to Unified_Itemized_Transactions. A subcategory or secondary variant to which a product belongs.
product_subcategory_id	String	The ID for the subcategory or secondary variant to which a product belongs.
product_subclass	String	The subclass to which a product or item is assigned.
product_subclass_id	String	The ID for the subclass to which a product or item is assigned.
product_subdepartment	String	The sub-department to which a product or item is assigned.
product_subdepartment_id	String	The ID for the sub-department to which a product or item is assigned.
product_type	String	The type assigned to a product or item.
product_upc	String	The UPC code for the product or item. A Universal Product Code (UPC or UPC code) is a barcode that is widely used to track items in stores.