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
  

These features:

• Can only be enabled by CatalogPilot Support
  
• Require additional review and approval
  
• May require supplemental legal agreement
  

CatalogPilot defaults to manual approval to maintain enterprise-grade control and prevent unintended changes.

Enrich Variants (Global Variant Control)

Enrich Variants toggle controls whether variant-level enrichment is generated.

When enabled:

• Variants are treated as independent records
  
• Variant-specific schema and metadata are generated
  
• Variant images may be enriched
  
• Discoverability is amplified for each variant
  

When disabled:

• Variant pages inherit parent product content
  
• Variant pricing/SKU still come from the platform
  
• No variant-specific enrichment or estimates are created
  

This is the master override for all variant enrichment behavior.

Use Enriched Content on Site (Global Overrides)

This section lets merchants selectively disable delivery of enriched content for specific human-facing fields while keeping enrichment intact internally.

You may toggle delivery for:

• Title
  
• Alternate Title
  
• Short Description
  
• Long Description
  
• Meta Title
  
• H1 / H2 / H3
  
• Image Caption
  

When unchecked:

• CatalogPilot still enriches and stores content
  
• Original platform content is shown to visitors
  
• Structured metadata and machine-readable signals remain available unless disabled elsewhere
  

This allows merchants to:

• Preserve brand voice for human-visible copy
  
• Still benefit from structured data and indexing improvements
  

Language & Translation Settings (Reference)

A language selection area appears on this page listing supported languages.

Important notes:

• CatalogPilot does not create new languages
  
• Translations only apply to languages that already exist in your platform catalog
  
• Enabling a language assumes translated products already exist upstream
  
• Translation runs only after primary language enrichment is approved
  

Languages shown here act as opt-in delivery flags, not language creators.

Key Takeaway

Storefront Settings give merchants final authority over:

• What is delivered
  
• How it is delivered
  
• Whether variants are included
  
• Which enriched fields appear to humans
  

Enrichment can continue independently of delivery, ensuring safety, reversibility, and control.

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 clean, square or horizontal format.

Social Links

You may optionally add social profile URLs (e.g. brand social accounts).

• These links are included in structured data
  
• They support brand verification and entity trust
  
• They are not required
  

Leaving this blank does not affect enrichment quality.

Policy & Company Page Links

These fields link your existing policy and company pages into structured metadata:

• Privacy Policy
  
• Terms & Conditions
  
• About Us
  
• Return Policy
  

These links are used for:

• Compliance signaling
  
• Trust indicators for crawlers
  
• Merchant identity validation
  

Important note:

If your site uses a single page that contains multiple policies, it is acceptable to reuse the same URL in multiple fields as long as the page contains relevant content.

Address Information

Your business address is used to:

• Anchor your merchant entity
  
• Support trust and compliance signals
  
• Improve consistency across product and category schema
  

This information does not need to match a public storefront address exactly, but it should represent a real business location.

Twitter / Social Metadata

Optional fields for:

• Twitter Site
  
• Twitter Creator
  

These are used only for social preview enrichment and structured metadata.

If you do not actively use Twitter/X, these can be left blank without impact.

Saving & Updates

• Changes here are applied immediately to structured data
  
• No storefront downtime is required
  
• Updates affect future renders and crawls, not historical data
  

Key Takeaway

This section defines who you are, not what you sell.

CatalogPilot uses these settings to:

• Establish merchant identity
  
• Strengthen trust signals
  
• Support compliance and discoverability
  

You do not need to perfect every field — accurate, honest information is sufficient.

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 opened, the following fields can be managed:

• Name
  
• Email address
  
• Password
  
• Preferred time zone
  

The time zone setting ensures:

• Accurate timestamps for approvals, enrichment, and activity logs
  
• Clear alignment across teams working in different regions
  

Changes take effect immediately.

User Removal

Users can be deleted from this view.

• Removing a user revokes their access to CatalogPilot
  
• It does not affect catalog data, enrichment state, or storefront delivery
  
• All approved content remains intact
  

Access Philosophy

CatalogPilot treats user access as an operational control, not a content control.

• Any user can review, approve, or edit content
  
• Approval actions are logged in the Activity feed
  
• There is no hidden or destructive permission model
  

This keeps collaboration simple and transparent.

Key Takeaway

The Users panel is for identity and access only.

It does not change:

• Enrichment logic
  
• Delivery behavior
  
• Approval state
  

It simply ensures the right people can safely work inside the system.

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
  

Not all actions in CatalogPilot are billable.

Only enrichment-related operations generate charges.

All actions—billable or not—are logged for transparency.

Drill-Down Event Details

Each activity entry is clickable.

When selected, CatalogPilot displays:

• The exact fields involved
  
• Before/after values (where applicable)
  
• The internal context of the operation
  
• Any associated batch or object references
  

This creates a full forensic timeline of catalog changes.

Errors Tab

The Errors tab lists any system-detected issues encountered during processing, such as:

• Temporary API failures
  
• Retry exhaustion
  
• External platform delays
  
• Validation or delivery interruptions
  

CatalogPilot is designed to automatically retry recoverable errors.

If an error appears:

• Support may already be aware and investigating
  
• Merchants are encouraged to contact support if the issue persists or is unclear
  

Design Intent

This panel is not intended for daily merchant interaction.

It exists to:

• Provide confidence that the system is behaving correctly
  
• Allow support teams to diagnose issues quickly
  
• Offer merchants visibility without requiring intervention
  

Most merchants will rarely need to reference this section.

Key Takeaway

The Activity & Errors panel is the system ledger for CatalogPilot.

It records:

• What happened
  
• When it happened
  
• Who initiated it
  
• Whether it affected billing
  

Nothing is hidden, and nothing is silently changed.

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 see a list of available languages.

These represent:

• Languages already configured in the platform
  
• Languages detected during catalog synchronization
  

Selecting a language here:

• Enables enrichment for that language after approval
  
• Does not trigger enrichment immediately
  
• Does not create translated products or pages
  

Languages act as delivery permissions, not generation triggers.

Translation Execution Order

CatalogPilot enforces a strict sequence to prevent drift:

1. Primary language enrichment runs first
   
2. Merchant reviews and approves primary language content
   
3. Translation enrichment runs only after approval
   
4. Translated content inherits approved structure and intent
   

This ensures:

• Translations are anchored to validated source content
  
• Machine interpretation remains consistent
  
• Errors do not propagate across languages
  

Translation Scope & Limitations

Translations apply only to:

• Fields that exist in both languages
  
• Products that already exist in the platform catalog
  
• Supported enrichment fields (titles, descriptions, metadata, etc.)
  

CatalogPilot will not:

• Translate languages that don’t exist
  
• Generate partial language trees
  
• Infer or fabricate missing translations
  

If a product does not exist in a given language upstream, it will be skipped.

Pricing & Billing Behavior

When applicable:

• Translation enrichment is billed at up to 50% of the primary enrichment fee
  
• Translation charges only apply after approval
  
• No translation charges occur without explicit merchant action
  

Exact pricing is always shown before confirmation in batch estimates.

Recommended Best Practice

CatalogPilot recommends:

• Enriching and approving the primary language first
  
• Enabling translations incrementally
  
• Reviewing translated content at a glance rather than field-by-field
  

This maintains speed, consistency, and accuracy across large catalogs.

Key Takeaway

Language controls in CatalogPilot are protective by design.

They ensure that:

• Nothing is translated prematurely
  
• No language content drifts from approved intent
  
• Multilingual catalogs scale safely and predictably
  

CatalogPilot enhances what already exists — and only when you allow it.