Skip to main content

Product families & attributes

Product families are the template for each type of product you sell. Get families right first — everything else (completeness, AI, exports) depends on them.

Why families matter​

Without familiesWith families
Every SKU is ad hocShared attribute set per product type
Completeness is vagueClear required fields per channel
AI guesses field namesAI reads governed attributes
Amazon and web share wrong fieldsChannel-scoped requirements

Footwear, electronics, and food supplements should be different families.

Set up attributes (global library)​

  1. Open Attributes (or Attribute groups, depending on your UI layout).
  2. Create groups that match how editors think — e.g. Marketing, Logistics, Compliance.
  3. Add attributes with the correct type (text, number, select, boolean, media, date).
  4. Mark whether values are per locale and/or per channel.
  5. For selects, define options (color names, materials) once — reuse everywhere.

Create a product family​

  1. Open Product families → Create.
  2. Set a clear code (e.g. footwear, consumer-electronics).
  3. Attach attributes from the library.
  4. Mark attributes required or optional for this family.
  5. If an attribute applies only on certain channels (e.g. Amazon-specific bullets), scope it to those channels.
  6. Choose which attribute drives display name and main image in lists and Brand Hub.

Variant structure (multi-variant families)​

When products have multiple SKUs:

  1. Under the family, define a variant structure (e.g. color-size).
  2. Pick axis attributes — typically Color (level 1) and Size (level 2).
  3. Editors create variants by combining axis values — descriptive attributes stay on the product.

Good practices​

  • Start with 10–20 core attributes per family, expand later.
  • Align mandatory fields with what your strictest channel requires.
  • Use consistent codes — APIs and MCP tools reference them.

Common mistakes​

  • One “General” family for the whole catalog.
  • Required attributes your ERP never sends — imports always fail completeness.
  • Forgetting channel scope — web is ready but Amazon is not.