Managing a product catalog, variants, media and assortments
Turn authorized catalog inputs into products, variants, offers, approved media and assortments.
On this page
Maintain a catalog your business can rely on—not just a collection of scraped pages. The planned outcome is a versioned catalog of products or services, variants, offers, approved media and reusable assortments.
Start from owned scope
Provide your account/workspace context, catalog identity, authorized source references and any reviewed business-authored facts. Imported observations must retain their source and capture time; customer corrections should preserve history instead of erasing contradictory evidence.
Products, families, variants and offers are different identities. A service offering must not be forced into a physical-product shape merely because the acquisition pipeline supports products first.
Keep durable outputs
A useful result contains normalized catalog records, relationships, provenance, unresolved conflicts and the exact revision used by downstream Stores or exports. Record price/currency and offer context rather than inventing missing values.
For example, a bedding family can have size/color variants and several seller offers. One qualifying page does not prove every variant or image was acquired.
Import and media boundaries
A saved Catalog quote never expires. Start, Stop and server-derived Continue preserve the frozen scope. Page processing, product persistence, projection delivery, media hosting, rights approval and publication have separate completion states.
Availability and next decision
Business APIs are planned. First-class service authoring and some manual catalog/offer workflows need explicit completion. Review rights and unknowns before promoting research into catalog truth; export or refresh must be a separate authorized action.