The Storefront Settings section controls how approved CatalogPilot content is applied to your live storefront and how global delivery behavior is configured.

This page acts as the final control layer between enrichment and live delivery.

Site Identification

Site Name

Displays the name of the storefront connected to CatalogPilot. This is for reference only and does not affect delivery behavior.

Site URL

The live storefront URL where CatalogPilot delivers enriched content at render time.

This must match the storefront domain used by your platform.

Auto-Enrichment Controls (Support-Only)

Two advanced automation options appear here but are disabled by default:

• Auto-Enrich
• Auto-Approve Enriched

CatalogPilot supports translation-aware enrichment while preserving strict control over how and when translated content is generated and delivered.

This section explains how language handling works and what merchants should (and should not) expect from translation features.

Core Principle: CatalogPilot Does Not Create Languages

CatalogPilot does not create new languages in your catalog.

Translations are only applied when:

• The language already exists in your eCommerce platform
• Products are already present in that language upstream
• The merchant explicitly enables translation delivery

CatalogPilot enhances existing multilingual catalogs — it does not invent or auto-expand them.

Language Selection Controls

Within Storefront Settings, merchants may

This section controls how your brand, policies, and business identity are represented in structured data (JSON-LD) and social previews across your storefront. These settings do not change how your site looks to customers, but they are critical for trust, compliance, and search engine understanding.

Schema Logo

The Schema Logo is used in your site’s structured data to establish brand provenance.

• This logo is embedded into JSON-LD as your official brand mark
• It helps search engines and AI systems associate products with your business entity
• The logo does not affect storefront visuals

Best practice:

Use your primary brand logo in a

This section allows merchants to manage who can access CatalogPilot, what identity they use, and how they interact with the system.

CatalogPilot is designed to support multiple users per storefront, with shared visibility into catalog status and enrichment activity.

Users List View

The Users panel displays a list of all users who currently have access to the storefront.

Each row shows:

• Name — the user’s display name
• Email Address — used for login and notifications

Standard table controls are available:

• Search
• Pagination
• Per-page selection

Clicking a user row opens that user’s detail view.

User Detail View

When a user is

The Activity & Errors panel provides a complete, chronological audit of everything that happens inside CatalogPilot for a storefront.

This section is designed for transparency, traceability, and operational confidence.

Activity Tab

The Activity tab displays a detailed timeline of actions performed across the system, including but not limited to:

• Enrichment actions (products, images, categories, variants)
• Approval actions
• Batch state transitions (Queued → Enriching → Finalizing → Completed)
• Manual edits
• System-generated events

Each row includes:

• Activity type (e.g., Enriched, Approved, Status Changed)
• Description of the action
• User who initiated the action
• Timestamp (created or updated)
• Amount, when the action is billable