Business

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

Required

string

Stable identifier shared by all variants of one product.

variant_id

Required

string

Stable identifier for one sellable variant.

parent_product_id

Optional

string

Optional parent identifier used by grouped catalogs.

sku

Required

string

Merchant stock keeping unit for the variant.

title

Required

string

Customer-facing product title.

description

Optional

text

Product description without layout markup.

brand

Optional

string

Brand or manufacturer name.

category

Required

string

Primary normalized product category.

subcategory

Optional

string

More specific normalized category.

variant_attributes

Optional

object

Structured size, color, material, or other variant values.

price

Required

number

Regular selling price.

sale_price

Optional

number

Current promotional price when applicable.

currency

Required

string

Three-letter currency code.

inventory_count

Optional

integer

Available units when exact inventory is tracked.

availability

Required

string

Normalized stock status.

image_url

Optional

url

Primary product image URL.

product_url

Required

url

Canonical product or variant page URL.

gtin

Optional

string

GTIN, UPC, EAN, or ISBN when assigned.

source_url

Optional

url

Source used to verify the record.

updated_at

Required

datetime

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