EcomAtlas

Module

Product data

For
Lean founder-operator · also Head of ecommerce / growth, New-brand launcher

Published · v1.0.0

Locked

Lessons

4 lessons, in order.

0/4
  1. Lesson 1: Variant or separate product

    Model one purchase decision as variants and distinct purchase decisions as separate products, then verify Shopify's option, theme, app and channel constraints.

    Locked✓
  2. Lesson 2: Decide where each piece of product data lives before you need it

    Place recurring merchandising data in the Shopify field and resource level that matches how it must be governed, reused and consumed.

    Recommended first: Variant or separate product

    Locked✓
  3. Lesson 3: Make product data answer the questions shoppers use

    Define and populate a consistent attribute model before configuring filters, synonyms, or compatibility search.

    Locked✓
  4. Lesson 4: Keep the selected variant truthful when it cannot be bought

    Distinguish a sold-out variant from a nonexistent combination, unpublished variant, or inventory-location problem.

    Locked✓

Product data determines what Shopify can sell, what a theme can display, what search and filters can retrieve, and what operations can fulfill. The business outcome is a catalog whose structure represents the commercial truth once, with named owners for changes.

This module connects four decisions. Decide whether an offer is a variant or separate product. Put each fact in the correct Shopify object. Define the structured attributes needed by filters, search, and compatibility questions. Then specify what the storefront should do when a selected variant does not exist, is sold out, is unpublished, or cannot be fulfilled online.

Use this sequence:

  1. Define the commercial identity of the product and its variants.
  2. Place operational, merchandising, and shopper-facing facts in options, categories, metafields, tags, or another governed system.
  3. Standardize the attributes needed to answer priority shopper questions. Shopify category metafields can supply taxonomy-linked attributes and connect them to variant options.1
  4. Test how availability, publication, market, and location change the selected-variant experience.

Module diagnostic

Choose one high-priority product family. Can the team identify its product identity, variant-defining choices, canonical attributes, source of truth, compatibility relationships, publication scope, online-fulfilling inventory, and unavailable-state behavior? The first answer that differs between merchandising, operations, and the storefront is the data problem to fix.

Assignment

Create a catalog contract for that family. List every required field, its product or variant scope, approved format, owner, source, update event, storefront use, and exception. Populate it for the full family, then test one filter question, one search or compatibility question, and every supported unavailability state.

Evidence and further reading

  1. "Category metafields," Shopify Help Center, https://help.shopify.com/en/manual/custom-data/metafields/category-metafields. Supports category attributes and connections to variant options. Accessed August 23, 2026.

Was this helpful?