The Product List View is the primary operational workspace for managing enriched products at scale. It is designed to be fast, low-cognitive, and safe — allowing merchants to control delivery without needing to inspect every underlying tag.

This view appears when selecting Products from the left navigation.

Purpose of the Product List View

The Product List View allows merchants to:

• See the current enrichment and delivery status of all products
• Enable or disable delivery per product
• Navigate quickly to detailed product records (Gallery View)
• Identify products awaiting review
• Control visibility without editing content
• Manage large catalogs efficiently

This view is

Purpose of the Product Gallery

The Product Gallery is the primary confidence-building view in CatalogPilot.

This is where merchants can clearly see, at a glance, what CatalogPilot has changed, why it changed, and how that data will be interpreted by search engines and AI systems—without being required to edit or approve every individual field.

The Gallery is not a review queue and not a workflow gate.

It is a visual comparison and inspection space designed to reduce cognitive load while increasing trust.

How the Gallery Is Structured

Each product opens into a three-column comparison layout, with a clear distinction between

The Product tab provides structured, field-level access to core product content.

It is not the primary review interface — that role belongs to the Product Gallery described in Section 4.

Merchants typically arrive at the Product tab only after visually reviewing content in the gallery and deciding whether any targeted adjustments are needed.

5.1 Purpose of the Product Tab

The Product tab exists to:

• Allow precise edits to individual product fields
• Support manual overrides when needed
• Provide full transparency into enriched vs original values
• Preserve merchant control without forcing manual work

Most merchants will not need to use this tab

The Images / ADA tab displays accessibility-optimized metadata generated for each product image. This information is machine-read first and is primarily consumed by screen readers, search engines, and accessibility tools—not by shoppers directly.

What This Tab Represents

For each image, CatalogPilot generates three core accessibility fields:

• Image Title – a concise identifier for the image
• Alt Text – a descriptive sentence used by screen readers and accessibility software
• Caption – optional contextual description that may be used by assistive technologies and structured data

These fields are produced using image-to-content mapping, where CatalogPilot analyzes the image in the context of:

• The

The Variants tab appears only when a product includes one or more variants (such as size, color, or fit). Its role is to provide visibility into how CatalogPilot represents variants for discovery, not to encourage routine editing.

Why Variants Are Represented Separately

CatalogPilot intentionally generates independent variant records derived from the parent product.

This is not duplication for duplication’s sake. It is a deliberate structural decision that enables:

• Variant-specific structured data
• Attribute-level indexing (size, color, fit, SKU)
• Improved discovery for long-tail and filtered searches
• Accurate interpretation by AI systems and shopping engines

In practice:

• One parent product remains the canonical

The SEO tab displays and manages all search-engine–focused metadata generated by CatalogPilot for a product. This information is machine-read first, designed primarily for search engines, shopping engines, and AI crawlers rather than human visitors.

Most merchants will review this tab briefly and rarely need to edit it.

What the SEO Tab Controls

The SEO tab includes the following fields:

• Meta Title
• Meta Description
• Meta Keywords
• H1
• H2
• H3
• Source URL
• Canonical URL
• JSON-LD (Structured Data)

Together, these fields define how the product is interpreted, indexed, and ranked by search engines and AI systems.

Visual Indicators & Field States

Each field

Purpose of the Attributes Tab

The Attributes tab contains structured, machine-readable product attributes used primarily by search engines, shopping platforms, and automated discovery systems (such as Google Shopping, structured search, and AI-based crawlers).

Unlike the Product tab (which is human-facing) and the Gallery (which provides a comparative overview), the Attributes tab exists to ensure semantic accuracy, classification correctness, and eligibility for external indexing systems.

This tab is not designed for heavy manual editing and should be treated as a verification and exception-handling interface, not a content-creation workspace.

How Attributes Are Generated

Most attribute values are:

• Derived from your existing catalog

Purpose of the ESG Tab

The ESG tab contains optional, structured fields used to describe environmental impact, ethical considerations, and cultural or social context related to a product.

These fields are machine-readable signals, not marketing claims. They exist to support:

• Search and shopping systems that evaluate sustainability metadata
• AI-based discovery engines that factor ethical and environmental signals
• Future-facing compliance and classification frameworks

Completion of ESG fields is not required for CatalogPilot to function correctly.

How ESG Data Is Used

When populated, ESG data may be used by:

• Search engines and shopping feeds that surface sustainability attributes
• AI systems that assess

Purpose of the Social Tab

The Social tab contains structured metadata used when products are shared on external social platforms such as:

• Facebook
• LinkedIn
• TikTok
• X (Twitter)

These fields control how a product is presented when a link is shared, not how it ranks in search results.

Social metadata is machine-consumed by social platforms and preview engines. It is not intended for day-to-day human editing.

What Data Is Managed Here

The Social tab includes two primary metadata groups:

OpenGraph (OG)

Used by most modern social platforms:

• OpenGraph Title
• OpenGraph Description

These values determine the headline and summary shown in link

Purpose of the Legal / PCI Tab

The Legal / PCI tab attaches verified legal, compliance, and provenance information to each product record.

This information is machine-consumed first, but also provides a transparent compliance layer for regulators, marketplaces, and automated trust systems.

Unlike SEO or Social metadata, this tab establishes accountability and provenance, not marketing or discoverability.

What This Tab Provides

The Legal / PCI tab combines two distinct categories of information:

1. Product-Specific Compliance Fields

These fields may vary by product and are generated or populated when applicable:

• Compliance Notes (e.g., care instructions, material handling, safety notes)
• Warnings (e.g.,

Purpose of the AI Tab

The AI tab provides structured, machine-oriented signals designed to support future AI discovery, interpretation, and retrieval systems.

This tab is not intended to drive immediate SEO or human-facing content.

Its role is to anchor product meaning, context, and differentiation for advanced AI agents and large-language-model–driven systems.

Think of this tab as forward-looking semantic infrastructure.

What the AI Tab Contains

The AI tab includes the following fields:

LLM Summary

A concise, factual narrative describing the product as a complete entity.

• Generated to be stable, neutral, and non-promotional
• Designed for AI systems that require full-context understanding
• Locked

Below both Product and Category views, CatalogPilot provides two operational tabs:

• Activity
• Errors

These tabs exist to provide traceability, transparency, and confidence without increasing cognitive load during normal use.

They are designed to be informational, not something merchants need to actively manage day-to-day.

Activity Tab

The Activity tab records a chronological log of meaningful actions performed on a product or category within CatalogPilot.

This includes:

• Enrichment events
• Approval actions
• Manual edits
• AI-assisted generations
• System-initiated updates tied to enrichment workflows

Each entry includes:

• Activity Type (e.g. Enriched, Approved)
• Description of the action
• Created By (user or system)
• Timestamp
• Amount, when the