← All documentation

Catalog basics

Products, categories, attributes, and languages.

A concise reference for the structures that keep product information consistent across your Tabgrid catalog.

How should I structure a product catalog?

Give each product a stable identifier, group products into meaningful categories, define reusable attributes and choose the fields relevant to each product type. Confirm the language context before editing localized content.

Product records

A product record brings an identifiable item together with its titles, descriptions, images, categories, and structured attributes. Agree on stable external product identifiers before bringing in source data; imports and updates depend on matching records consistently.

Each product also carries system fields such as its creation date, last-updated timestamp, and the workspace it belongs to. These fields are useful for auditing changes and for filtering products that need review after a bulk import or edit.

Categories and product organization

Use categories to describe how the assortment is grouped. Build a hierarchy that matches how your team browses and maintains products, then assign products to the right category. Keep the product's classification separate from the attribute values that describe its details.

Keep category names short and consistent so filters and navigation built on top of them stay predictable. Check your workspace rules before using multiple category assignments.

Attribute definitions, groups, and families

An attribute definition describes a reusable product field and its data type. Attribute groups organize related fields for editors. Attribute families select the fields relevant to a product type, helping different products capture the details they actually need.

A useful setup starts with clear field names, deliberate data types, and consistent definitions for units and allowed values. Review imports against the attribute structure before processing a large catalog.

Common attribute types

These are examples of field types to consider when designing a catalog; confirm supported types in your workspace before mapping an import.

  • Text

    Short free-text values such as a product title or model name.

  • Rich text

    Longer formatted content such as a product description.

  • Number

    Numeric values, optionally with a defined unit, such as weight or wattage.

  • Select / multi-select

    A value chosen from a predefined list, such as color or size, with one or multiple selections allowed.

  • Boolean

    A true/false flag, such as whether a product is eligible for a specific channel.

  • Media

    Images or other files attached to a product, such as the primary product photo or a spec sheet.

Languages and localization

Product content can be managed in language-specific contexts where languages are configured. Review the selected language before editing a description or requesting an assisted translation so that changes are written to the intended localized content.

AI-assisted translations and bulk edits depend on the workspace's enabled features and AI settings. Treat generated content as a draft: inspect the preview and verify names, units, claims, and terminology before confirming.