Skip to main content

Data model

How catalog, media, and syndication objects relate in CataZenta — a conceptual map for architects and integrators.

Plain-language guide (start here for setup): Catalog fundamentals

Identity & access

EntityDescription
OrganizationYour company account.
TenantIsolated catalog workspace (brand, region, or business unit).
UserPerson with roles in one or more tenants.
Service accountAutomation identity with API access for integrations.

All catalog APIs are scoped to a tenant.

Catalog (PIM)

EntityDescription
Product familyTemplate: which attributes apply, what is required, optional per-channel rules.
Variant structureHow SKUs are built (e.g. color × size) for multi-variant products.
ProductCatalog item at model level; simple or multi-variant.
Variant (SKU)Sellable unit when the product has a variant matrix.
AttributeField definition (text, number, select, media, …).
Attribute valueActual data on a product or SKU, scoped by locale and/or channel when configured.
Category treeHierarchical taxonomy for navigation or channel classification.
Category assignmentLinks products to one or more categories.
ChannelPublish destination with a linked category tree and enabled locales.
CompletenessReadiness score per product or SKU for a channel–locale pair.

Digital assets (DAM)

EntityDescription
FolderOrganization of files in DAM.
AssetImage, video, or document with versions.
RenditionFormat or size prepared for a channel.
Product linkMedia associated with a product or SKU.

Syndication

EntityDescription
ConnectorSupported platform (Amazon, Shopify, …).
ConnectionYour linked account and settings.
Export profileRules and field mapping for outbound sync.
Attribute mappingHow a PIM field maps to a channel field (can vary by category).
Export jobBatch publish with per-SKU results.
Import jobBatch ingest from ERP or supplier feeds.
External listing referenceMaps your product to a live listing on a channel.

Workflows

EntityDescription
WorkflowStages products pass through before publish.
TaskApproval or action assigned to a user.

Typical flows

Enrich then publish

  1. Create a product family and attributes.
  2. Create a category tree and channel with locales.
  3. Create products, fill values, and link assets.
  4. Reach completeness for the target channel and language.
  5. Run an export job to the channel.

Integrate ERP

  1. Run an import job from your ERP or supplier feed.
  2. Map incoming fields to your attributes (often with AI assist).
  3. Editors review and approve in the PIM.
  4. Syndicate to channels.