Ecommerce Product Dataset Template
A normalized product catalog schema that separates product identity from sellable variants while keeping pricing, inventory, imagery, and source records ready for import and review.
For: Ecommerce teams, catalog managers, and marketplace sellers
Schema Fields
product_id
Requiredstring
Stable identifier shared by all variants of one product.
variant_id
Requiredstring
Stable identifier for one sellable variant.
parent_product_id
Optionalstring
Optional parent identifier used by grouped catalogs.
sku
Requiredstring
Merchant stock keeping unit for the variant.
title
Requiredstring
Customer-facing product title.
description
Optionaltext
Product description without layout markup.
brand
Optionalstring
Brand or manufacturer name.
category
Requiredstring
Primary normalized product category.
subcategory
Optionalstring
More specific normalized category.
variant_attributes
Optionalobject
Structured size, color, material, or other variant values.
price
Requirednumber
Regular selling price.
sale_price
Optionalnumber
Current promotional price when applicable.
currency
Requiredstring
Three-letter currency code.
inventory_count
Optionalinteger
Available units when exact inventory is tracked.
availability
Requiredstring
Normalized stock status.
image_url
Optionalurl
Primary product image URL.
product_url
Requiredurl
Canonical product or variant page URL.
gtin
Optionalstring
GTIN, UPC, EAN, or ISBN when assigned.
source_url
Optionalurl
Source used to verify the record.
updated_at
Requireddatetime
Last verified update time for the record.
Use Cases
- Catalog migration
- Marketplace listing preparation
- Product feed cleanup
- Pricing audits
- Inventory documentation
- Catalog enrichment
Separate Products From Sellable Variants
A product groups the shared title, brand, description, and category. A variant identifies the exact size, color, material, pack, or configuration someone can buy. Keeping both identifiers prevents a catalog from duplicating shared facts or losing inventory detail.
Catalog Checks Before Import
- Confirm that every variant ID and SKU is unique
- Use one currency code and one availability vocabulary
- Keep prices numeric and store the currency separately
- Validate product and image URLs
- Check that sale prices do not exceed regular prices
- Require an update time for records that change
What the Template Does Not Decide for You
Each storefront and marketplace has its own required taxonomy, image rules, variant limits, and feed names. Map this neutral schema to the destination platform after the catalog is clean rather than using one platform's field names as the permanent source structure.
- Exports
- CSV, JSON, XLSX
- License
- Standard personal and commercial license