Skip to main content

​
Overview

Catalogs are containers for products. They provide a structured workflow for managing product content that mirrors git-based version control.

​
Catalog lifecycle

​
States

  • Draft — editable, not visible to external consumers
  • Published — locked for direct edits, visible via the public products API

​
Operations

Marks the catalog as live. Published products become available through the public /api/catalog/products endpoint. A published catalog cannot be directly edited — fork it first.
Reverts the catalog to draft state and removes its products from the public feed.
Creates a copy of the catalog. Use forks to iterate on content (add products, edit descriptions, run AI enhancements) without affecting the live version.
Applies changes from a fork back into the parent catalog. Conflict resolution is handled at the product level.

​
Catalog stats

Each catalog tracks aggregate statistics:
  • Total product count
  • Products with optimization score above threshold
  • Feed-ready products (all required fields populated)
  • Last published timestamp

​
Best practices

Use the fork → edit → merge workflow for seasonal updates. This lets your team iterate on “Spring 2026” content while “Winter 2025” stays live.