# Minimum catalog product fields At a minimum, your product feed should contain: * A unique **`ID`** for each product. * **Basic information** such as `title`, `URL`, image, `price`, and `currency`. * **`Stock` or `availability`** to control whether products can be shown. * **Category mapping** (`categoriesIDs` or hierarchy). * **Date of creation** `createdAt` ISO date (to enable rules like "new arrivals"). * `imageUrl` * Optional: * `brand`, `gtin`, `mpn`, `attributes` (e.g., `color`, `size`, `material`, `gender`, `age_group`) When connecting CMS as a catalog source in Recommendations & Merchandising (R\&M), you should be aware of certain standard product attributes that are either mandatory or strongly recommended. ### Shopify specifics | Field(s) | Required or Recommended? | Reason | | ------------------------------------------------------------- | ------------------------ | -------------------------------------------------------------------------------- | | `id`, `handle`, `title` | **Required** | Core identifiers and product name, mandatory for referencing & display | | At least one `variant` with: • `price` • `inventory_quantity` | **Required** | Ensures availability & pricing logic for rules and merchandising | | `created_at` | **Required** | Enables “new arrivals” and date-based strategies | | `images` | **Required** | Ensures visual display in recommendations and merchandising | | `body_html` (description) | **Recommended** | Provides product context, improves UI and SEO | | `product_type` / `vendor` | **Recommended** | Useful for filtering, boosting, and organizing catalog rules | | Standard product category (taxonomy) | **Recommended** | Supports category-based rules, navigation, external sync (e.g., Google Shopping) | | Metafields | **Recommended** | Extend schema with custom attributes (e.g., eco\_score, release date) | For richer strategies, add `product_type`, `vendor`, category taxonomy, and relevant metafields. ### Prestashop — Minimum Product Schema for R\&M | Field(s) | Required or Recommended? | Reason | | ------------------------------------------------ | ------------------------ | ----------------------------------------- | | `id`, `name`, image | **Required** | Core identification and display | | Variant with `price` and `quantity` | **Required** | Required for availability & pricing logic | | `created_at` / `date_add` | **Required** | Enables “new arrivals” strategies | | `type_product` | **Recommended** | To differentiate product behaviors | | `description` / `description_short` | **Recommended** | For UI/SEO and richer content | | Categories (`categories`, `id_category_default`) | **Recommended** | For category-based rules & filtering | | Features / `id_manufacturer` | **Recommended** | For advanced merchandising logic | | Variants/attributes (color, size, etc.) | **Recommended** | For nuanced rule targeting & filtering | ### Magento (Adobe Commerce) — Minimum Product Schema for R\&M | Field(s) | Required or Recommended? | Reason | | -------------------------------------------------------------------------- | ------------------------ | ---------------------------------------------------------------------- | | `id` (entity\_id), `sku`, `name` | **Required** | Core identifiers and product name, mandatory for referencing & display | | At least one `price` (regular or final) + `stock_item.qty` / `is_in_stock` | **Required** | Ensures availability & pricing logic for rules and merchandising | | `created_at` | **Required** | Enables “new arrivals” and date-based strategies | | `media_gallery_entries` (at least one image) | **Required** | Ensures visual display in recommendations and merchandising | | `description` / `short_description` | **Recommended** | Provides product context, improves UI and SEO | | `type_id` (simple, configurable, virtual, bundle, downloadable) | **Recommended** | Helps distinguish product behavior for rules and merchandising | | `attribute_set_id` and custom attributes | **Recommended** | Used for filtering, boosting, and custom business logic | | `category_ids` | **Recommended** | Supports category-based rules, navigation, and merchandising | | `manufacturer` or brand attribute | **Recommended** | Useful for filters, boosting, and brand-specific strategies | | EAV attributes (color, size, material, etc.) | **Recommended** | Allow granular targeting in rules and dynamic filtering | ### Salesforce Commerce Cloud (SFCC) — Minimum Product Schema for R\&M | Field(s) | Required or Recommended? | Reason | | --------------------------------------------------------------------------------------- | ------------------------ | --------------------------------------------------------------------------------------- | | `id` (product\_id), `name` | **Required** | Core identifiers and product name, mandatory for referencing & display | | At least one `price` (list\_price, sale\_price) + `inventory` (ATS = Available To Sell) | **Required** | Ensures availability & pricing logic for rules and merchandising | | `online_flag` / `online_from` / `online_to` | **Required** | Controls product online visibility and supports “new arrivals” or date-based strategies | | At least one `image` (via `image_groups`) | **Required** | Ensures product has visual content for recommendations and merchandising | | `short_description` / `long_description` | **Recommended** | Provides context and enhances UI/SEO | | `brand` (custom attribute or classification) | **Recommended** | Useful for filtering, boosting, or brand-focused strategies | | `primary_category_id` and `classification_category_ids` | **Recommended** | Supports category-based rules and merchandising | | `custom_attributes` (e.g., color, size, material) | **Recommended** | Allow advanced filtering, boosting, and dynamic rules | | `creation_date` (if available in feed) | **Recommended** | Useful for “new arrivals” strategies | ### Magento — Minimum Product Schema for R\&M Coming soon * --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.abtasty.com/recommendations-and-merchandising/reference/catalog-cms-connection/minimum-catalog-product-fields.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.