This table should include all products, product variants and unique identifier information. We use this as a source of truth for all skus in your store.

Time Period: Current

Why do we need this? We use this information to aid in training our pricing models, implementing margin constraints and correctly calculating P&L metrics.

Schema

Unique Constraint: sku_primary.
NameRequired?TypeDescriptionExample
Identifiers
sku_primaryrequiredstringMust be unique. This is the sku identifier at the most granular at which you would want to manage pricing."sku_variant_12"
barcodeoptionalstring12345678905
barcode_typeoptionalstringE.g asin/ upc/ gtin"gtin"
Price
list_pricerequiredfloat14.99
member_priceoptionalfloat12.99
subscriber_priceoptionalfloat12.99
discounted_priceoptionalfloat14.49
Costs
costrequiredfloat7.10
cogsoptionalfloat11.20
total_costoptionalfloat
Details
namerequiredstring"Blue T-Shirt"
descriptionoptionalstring"The best blue t-shirt."
imageoptionalstringURL link to image for product"exampleimagelink.com"
sku_brandoptionalstringBrand of product being sold."Gap"
categoriesrequiredstring[]Sku category["Men", "Shirts"]
sub_categoriesoptionalstring[]Sku subcategories["T-shirt", "Casual"]
attributesoptionaljsonSku attributes{"Size": "Medium", "Color": "Blue", "Material": "Cotton"}
tagsoptionalstring[]Tags for this sku, which will be applied as imported product tags in the dashboard.["Basics", "Snacks"]
store_idoptionalstringId for the store where the purchase was made - brick and mortar store id, ecomm region, etc."loc_1"
is_activerequiredbooleanNote that we do not suggest price changes or track price changes for inactive SKUs.true
miscoptionaljsonAny fields that we should know about, but aren’t in our schema?