Before You Begin:

Why CatalogPilot Changes the Role of Your Catalog

Choosing to use CatalogPilot is not a minor optimization decision.

It is a structural shift in how your product catalog exists, behaves, and creates value.

Traditionally, an eCommerce product catalog lives inside a platform.

Its data, structure, and reach are constrained by that platform’s rules, limitations, and roadmap. Even when optimized, the catalog remains largely siloed—serving the storefront first, and everything else second.

CatalogPilot changes that model.

For the first time, your product catalog exists externally as a structured, governed asset—independent of any single platform. Your storefront remains fully operational and unchanged, but the intelligence, enrichment, and discoverability of your catalog are no longer locked inside it.

This separation creates freedom.

It allows your catalog to:

• Be optimized once and delivered consistently
  
• Serve search engines, accessibility systems, and emerging AI platforms directly
  
• Support future marketing, syndication, and platform transitions without rework
  
• Grow in value without being rewritten or rebuilt for each new channel
  

CatalogPilot does not replace your platform.

It liberates your catalog from it.

What you are working with is not just improved product content—it is a catalog that can now:

• Be amplified beyond your storefront
  
• Be reused without duplication
  
• Be governed deliberately rather than edited reactively
  
• Evolve independently of platform constraints
  

This manual will show you how to operate that system confidently—where your attention matters, where it doesn’t, and how to let the system do the heavy lifting while you focus on growth.

Why This Matters

Most merchants never get to make this shift.

They optimize within the limits they’re given.

By choosing CatalogPilot, you’ve chosen to treat your product catalog as a long-term digital asset, not just a page generator.

Everything that follows in this manual is designed to help you manage that asset with clarity, efficiency, and control—without requiring you to micromanage it.

CatalogPilot is an external intelligence layer that sits alongside your eCommerce platform — not inside it.

Instead of overwriting or modifying your catalog data, CatalogPilot creates a secure, synchronized copy of your catalog outside your platform, enriches it, and then delivers approved improvements at page render time.

The Three Core States

Every piece of content in CatalogPilot moves through three clear states:

1. Enriched
   New structured content has been generated (SEO, accessibility, metadata, variants, images, categories).
   
   
2. Approved
   A human has confirmed the enrichment is acceptable. This is the trust boundary.
   
   
3. Delivered
   Approved content is actively being delivered to your storefront for visitors and crawlers.
   

At no point does CatalogPilot permanently overwrite your platform’s data.

What CatalogPilot Does

• Reads catalog data from your platform
  
• Enhances it for search engines, accessibility, and AI systems
  
• Lets you review and approve changes
  
• Injects approved content safely at render time
  
• Can be disabled instantly with no rollback required
  

What CatalogPilot Does Not Do

• It does not change your database
  
• It does not rewrite themes or templates
  
• It does not interfere with checkout, pricing, or inventory
  
• It does not create products or languages that don’t already exist
  

Think of CatalogPilot as air traffic control for your catalog — observing, optimizing, and guiding safely — never taking ownership. 

How the Manual Is Organized

Each section corresponds directly to a specific area of the CatalogPilot interface:

• Dashboard & Review workflow
  
• Product and Category management
  
• Enrichment tabs (Products, Images, Variants, SEO, Attributes, ESG, Social, Legal, AI)
  
• Storefront configuration
  
• Billing and usage transparency
  

Sections are intentionally self-contained, so you can jump to what you need without losing context.

How to Read It

• Skim first to understand what a screen or feature does
  
• Dive deeper only if you want to understand why it exists or how it behaves under edge cases
  
• Ignore sections that don’t apply to your current workflow
  

CatalogPilot is designed so that most merchants only need to interact with a small subset of features during normal use.

When to Use This Manual

• When onboarding or reconnecting a store
  
• When reviewing or approving enrichments
  
• When adjusting storefront or delivery settings
  
• When reconciling usage or billing details
  
• When explaining CatalogPilot to internal teams or agencies
  

What This Manual Is Not

• It is not marketing material
  
• It is not an SEO playbook
  
• It does not prescribe content strategy
  
• It does not require technical expertise
  

It exists to provide clarity, confidence, and transparency.

CatalogPilot is designed to get you real results early, while ensuring accuracy, safety, and human oversight during your first interaction with the system.

Your first enrichment is intentionally guided and verified, not instant — this is by design.

Step 1 — Connect Your Catalog

After signing up, you provide:

• Read-only API access to your platform
  
• Your public storefront URL
  
  

CatalogPilot begins collecting and normalizing your catalog data in the background.

Depending on catalog size and system load, this initial collection can take minutes to a few hours.

No changes are made to your storefront during this stage.

Step 2 — Initial Enrichment Preparation

Once your catalog data is available:

• A small initial set of products (currently up to 10) is queued for enrichment
  
• These first enrichments are handled within controlled system limits
  
• Processing may begin immediately or after a short queue delay, depending on current activity
  

In most cases, enrichment starts within minutes, but it can take longer during busy periods.

Step 3 — Review by CatalogPilot & Notification

When the initial enrichments complete:

• Results are reviewed as part of the onboarding process
  
• You’ll receive a notification when they are ready
  
• In some cases, a support agent may reach out to walk you through the results
  

This first cycle typically completes within the same day, and always within a reasonable onboarding window.

Step 4 — Review Your First Enriched Products

You’ll be directed to the Review page where you can:

• Toggle between Original and Enriched
  
• Visually confirm improvements
  
• Focus primarily on the Product tab
  
• Ignore deeper tabs unless something looks incorrect
  

This step is designed to take minutes, not hours.

Step 5 — Approve and Take Control

Once approved:

• You immediately gain control of the enrichment process
  
• You can run future batches yourself
  
• You’ll see clear estimates for cost and time before starting any batch
  
• Processing continues in the background with live progress indicators
  

From this point forward, you control when, how much, and what gets enriched.

What Changes After the First Cycle

The initial process is the most structured.

After that:

• Enrichment becomes self-serve
  
• Timing estimates are shown clearly before each batch
  
• Review effort continues to decrease
  
• No additional gatekeeping is required
  

CatalogPilot is designed to earn trust first, then move out of your way.

CatalogPilot is intentionally designed to do the heavy lifting automatically while keeping human approval and control at clear decision points.

Understanding this separation is key to using the system confidently.

What Happens Automatically

CatalogPilot automatically handles the following:

• Catalog synchronization
  Reads products, variants, images, categories, and related metadata from your platform using read-only access.
  
  
• Contextual analysis
  Observes public storefront structure to understand how content is presented to visitors and crawlers.
  
  
• Enrichment generation
  Produces structured metadata, accessibility text, variant mappings, category signals, and AI-ready attributes off-platform.
  
  
• Batch processing & scaling
  Queues, throttles, and processes enrichments safely in the background without affecting storefront performance.
  
  
• Delivery mechanics
  Injects approved content at page render time using a lightweight, reversible delivery mechanism.
  

None of these automated steps write directly to your platform or persist changes without approval.

What Requires Human Action

Human involvement is deliberate and limited to high-value checkpoints:

• Reviewing enriched products
  Merchants visually compare original vs. enriched content and confirm accuracy.
  
  
• Approving content for delivery
  Approval is the boundary where enriched content becomes active.
  
  
• Optional edits or overrides
  Merchants can:
  
• Edit specific fields
  
• Revert to original content
  
• Disable delivery for individual products or categories
  
• Delivery activation
  Installing or enabling the delivery trigger is a conscious, reversible decision.
  

Why This Balance Matters

CatalogPilot avoids two extremes:

• Fully manual systems that require constant micromanagement
  
• Fully automated systems that remove human oversight and create risk
  
  

Instead, it follows a “review once, trust thereafter” model:

• Most enrichments require only a quick visual confirmation
  
• Editing remains available at any time, even after approval
  
• Nothing is locked in permanently
  

What You Don’t Have to Do

You do not need to:

• Review every variant in detail
  
• Edit every image description
  
• Understand every metadata field
  
• Approve each enrichment individually
  

The system is designed to reduce cognitive effort, not increase it.

CatalogPilot Glossary & Key Concepts

Catalog

Your product catalog as it exists on your eCommerce platform (products, categories, variants, images, prices, availability).

CatalogPilot does not replace your catalog. It reads from it and builds an enriched copy externally.

Copy of Catalog (External Copy)

A secure, read-only copy of your catalog created via API connection.

This copy:

• Lives outside your platform
  
• Is used for enrichment, validation, and delivery
  
• Can be discarded instantly with no impact to your store
  

Enrichment

The process of generating structured, machine-readable content for products, categories, variants, and images.

Enrichment may include:

• Titles and descriptions
  
• SEO metadata (meta title, description, headings)
  
• ADA / accessibility image text
  
• Schema-ready structured fields
  
• AI and semantic classification fields
  

Enrichment never overwrites platform data.

Approval

A required confirmation step where merchants review and accept enriched content before it is delivered to the storefront.

Approval:

• Prevents drift and hallucination
  
• Ensures enterprise-grade control
  
• Can be done per-item or in bulk (“Approve All”)
  

Approved content can still be edited later.

Original vs Approved

• Original: Content sourced from your platform and storefront
  
• Approved: Content generated by CatalogPilot and confirmed by you
  

The system always preserves both views for comparison.

Batch

A group of items selected for enrichment together.

Batches can be created by:

• Auto (oldest un-enriched items)
  
• Manual product selection
  
• Category-based selection
  

Nothing runs until a batch is confirmed.

Estimate

A cost preview shown before enrichment begins.

Estimates:

• Show item counts and pricing
  
• Reflect only what is currently eligible
  
• Do not trigger billing until confirmed
  

Review Queue

A temporary holding area for newly enriched items awaiting approval.

Designed for:

• Visual comparison
  
• Fast confirmation
  
• Minimal cognitive load
  

Most merchants approve here without editing.

Product Gallery

The primary comparison view showing:

• Human-facing content
  
• Machine-facing content
  
• Accessibility and structured metadata
  

This is the most important review surface in CatalogPilot.

Product Tabs

Secondary editing panels beneath the gallery.

Used for:

• Targeted edits
  
• Field-level overrides
  
• Advanced review (optional)
  

The gallery comes first; tabs support it.

Variants

Individual product variations (size, color, etc.) treated as independent structured records.

CatalogPilot creates separate variant records so:

• Each variant can be indexed independently
  
• Variant-specific schema can be delivered
  
• Discoverability is amplified without duplicate URLs
  

Variant content is largely inherited from the parent product.

Images / ADA

Image-level enrichment including:

• Image titles
  
• Alt text
  
• Captions
  
• Accessibility descriptions
  

These fields are primarily machine-read and should rarely be edited unless incorrect.

Attributes

Standardized product characteristics used by search engines and shopping platforms.

Includes Google-required fields such as:

• Availability
  
• Condition
  
• Product type
  
• Category taxonomy
  

Yellow fields are optional unless known with certainty.

Schema

Structured data (JSON-LD) delivered at render time to describe products, categories, and variants to search engines and AI systems.

Schema:

• Is injected dynamically
  
• Does not modify theme files
  
• Can be disabled instantly

Storefront Delivery

The process of delivering approved structured content to your live storefront when pages are viewed.

Delivery:

• Happens at render time
  
• Is non-destructive
  
• Reflects only approved content
  

FailSafe Switch

A global control that instantly disables all CatalogPilot delivery.

When turned off:

• Your store reverts to native behavior
  
• No cleanup or rollback is required
  
• All enriched data remains safely stored externally
  

Incoming (Catalog Sync)

The secure, read-only connection that pulls catalog data from your platform into CatalogPilot.

CatalogPilot:

• Reads data only
  
• Does not write back
  
• Respects platform authority

Outgoing (Delivery)

The controlled delivery of enriched content back to your storefront via a lightweight script.

Outgoing delivery:

• Is optional
  
• Can be paused or disabled
  
• Does not affect checkout or transactions
  

Tags

Individual structured data elements generated during enrichment.

A single product may generate dozens of tags across:

• Product fields
  
• Images
  
• Variants
  
• Categories
  
• AI and semantic layers
  

High tag counts indicate depth—not duplication.

Activity Log

A detailed timeline of actions within CatalogPilot.

Logs include:

• Enrichment events
  
• Approvals
  
• Edits
  
• Batch status changes
  
• Billable actions (where applicable)
  

Usage

A real-time record of billable enrichment activity.

Usage is:

• Itemized
  
• Time-stamped
  
• Assigned to invoices automatically
  

Invoice

A weekly summary of enrichment usage.

Invoices:

• Combine all usage into a single line item
  
• Reference detailed activity for auditability
  
• Are separate from subscription billing
  

Subscription

Your base plan that defines:

• Catalog size limits
  
• Access level
  
• Feature availability
  

Subscriptions are billed separately from enrichment usage.

Translation

Optional enrichment of approved content into existing platform languages.

Translations:

• Run only after primary approval
  
• Apply only to languages already present in your catalog
  
• Are discounted relative to primary enrichment