Most merchants build their storefront for people.

Design, photography, layout, and descriptions are crafted for browsing. And that makes sense. Customers experience your store visually.

But search engines, compliance systems, accessibility crawlers, AI discovery engines, and marketplace indexers do not.

They interpret something else.

They do not evaluate “design.”

They do not measure “aesthetic quality.”

They do not reward visual polish.

They evaluate depth, hierarchy, relationships, and machine-readable clarity.

And in modern eCommerce, nearly 80% of discoverability happens within this invisible layer.

The Human View vs. The Machine View

To a shopper, a product page appears complete if it includes:

• A title
  
• A description
  
• Images
  
• Pricing
  
• Variants
  

To indexing systems, completeness is defined very differently.

Search and compliance systems evaluate:

• Heading hierarchy and semantic structure
  
• Canonical references
  
• Product-to-variant relationships
  
• Category reinforcement
  
• Accessibility attributes
  
• Structured product metadata
  
• Legal and compliance signals
  
• Data consistency across the entire catalog
  

Most of this exists behind the scenes.

When this foundation is incomplete, inconsistent, or shallow, search engines reduce confidence — even if the page appears fully developed to human visitors.

Depth Drives Discoverability

Modern indexing is no longer field-based. It is relationship-based.

Search engines and AI systems evaluate how:

• Products relate to categories
  
• Variants differentiate meaningfully
  
• Images reinforce accessibility compliance
  
• Metadata clarifies intent
  
• Structure remains consistent across the catalog
  

Without foundational depth:

• Smaller products become invisible
  
• Long-tail discoverability collapses
  
• Rich results diminish
  
• AI discovery engines misinterpret intent
  
• Compliance exposure increases
  

Catalog performance is not driven by design alone.

It is driven by systemic completeness.

The 80% You Don’t See

Native platforms provide surface-level product fields.

They were designed to:

• Display products
  
• Process transactions
  
• Manage inventory
  

They were not designed to build and maintain deep semantic architecture across every product, image, variant, and category.

Over time:

• Metadata drifts
  
• Accessibility attributes remain incomplete
  
• Variant clarity weakens
  
• Schema becomes outdated
  
• Compliance requirements evolve
  

This degradation is invisible to merchants — but measurable to indexing systems.

Equal Lift Across the Entire Catalog

CatalogPilot does not privilege high-volume products over smaller SKUs.

Every product receives the same depth of enrichment.

That means:

• Long-tail products gain visibility
  
• Lower-volume SKUs receive indexing clarity
  
• Variants become semantically distinguishable
  
• Categories reinforce intent
  
• Catalog-wide signals strengthen collectively
  

This is not selective optimization.

It is systemic elevation.

Dynamic, Not Static

Most storefronts operate statically.

Once created, structural data rarely evolves unless manually updated.

CatalogPilot operates dynamically.

As your catalog changes:

• Metadata is rebuilt
  
• Schema is refreshed
  
• Accessibility is reinforced
  
• Semantic signals are regenerated
  

This ensures:

• Indexing remains aligned with evolving standards
  
• Compliance does not decay
  
• Discoverability does not drift
  

Your catalog remains structurally current — not structurally stale.

Why This Matters Now

Modern search engines and AI systems evaluate far more than keywords.

They assess:

• Hierarchical clarity
  
• Semantic precision
  
• Accessibility readiness
  
• Compliance alignment
  
• Catalog-wide consistency
  

When foundational depth is weak, merchants often compensate by increasing paid traffic — driving up acquisition costs while underlying discoverability remains constrained.

Ignored products do not compete.

The invisible 80% determines whether your catalog is interpreted accurately — or filtered out.

The Systems That Actually Read Your Store

Modern storefronts are evaluated by dozens of indexing, compliance, and discovery systems. Below is a representative overview of how these systems interpret product data — and how CatalogPilot prepares your catalog to be understood correctly by them.

CatalogPilot does not control these systems. It prepares your catalog to be interpreted correctly by them.

This is the architectural layer most platforms never fully construct.

Where CatalogPilot Operates

CatalogPilot functions inside this invisible layer.

It:

• Reconstructs foundational depth
  
• Enhances machine-readable metadata
  
• Strengthens accessibility compliance
  
• Reinforces indexing clarity
  
• Operates non-destructively
  
• Delivers dynamically at render time
  

It does not change how your store looks.

It changes how it is understood.

Final Thought

If your storefront looks complete but underperforms, the issue may not be design.

It may be foundational.

And foundational depth is rarely visible — but it is always measured.

CatalogPilot was built specifically for that invisible 80%.

The Outgoing section controls how CatalogPilot delivers approved enriched content to your live storefront.

This page is intentionally separated from enrichment and review to reinforce an important principle:

CatalogPilot enrichment and CatalogPilot delivery are independent.

You can enrich, review, and approve content without delivering anything to your storefront until you explicitly choose to do so.

What Outgoing Delivery Does

When enabled, CatalogPilot:

• Injects approved enriched metadata at page render time
  
• Delivers content only when pages are viewed by visitors or crawlers
  
• Does not overwrite platform data
  
• Does not modify your database, templates, or checkout
  
• Can be disabled instantly without cleanup or rollback
  

Delivery operates entirely at the render layer.

Global Delivery Status & FailSafe Switch

At the top of the page you’ll see:

• Running status indicator
  
• FailSafe toggle
  

The FailSafe Switch is a global on/off control for CatalogPilot delivery.

When FailSafe is:

• On → enriched content is delivered
  
• Off → your storefront immediately returns to native platform behavior
  
  

No content is removed, reverted, or rewritten when disabling delivery.

This is a hard safety cutoff, not a soft pause.

Installation Options

CatalogPilot supports three installation paths. All achieve the same result.

Option 1 — Manual Install (Recommended)

Best for merchants or teams comfortable placing code directly.

• Paste the provided script into your site’s <head>
  
• Works on any supported platform theme
  
• Fastest and most direct delivery path
  

Support can install this for you with temporary access if preferred.

Option 2 — Google Tag Manager

Recommended if your site already uses GTM.

• Add a Custom HTML tag with the CatalogPilot script
  
• Set trigger to All Pages
  
• Publish
  

This method introduces a minimal additional load step but remains fully supported.

Option 3 — Send to Your Developer

For agencies or internal developers.

• Download the .txt file
  
• Share with your developer
  
• No additional context required — this is a standard header script
  

CatalogPilot Delivery Script

The delivery script shown on this page is unique to your account and environment.

It contains:

• Your site identifier
  
• Delivery endpoint reference
  

This script only reads configuration and injects approved metadata.

It does not transmit orders, customers, or private data.

Installation Verification

Use Verify Installation to confirm that delivery is active on your storefront.

This check:

• Confirms the script is detected
  
• Verifies delivery readiness
  
• Does not crawl or alter your site

Safety Guarantees

CatalogPilot delivery:

• Never overwrites platform data
  
• Never modifies stored content
  
• Can be disabled instantly via FailSafe
  
• Delivers metadata only at render time
  

Your platform remains the system of record at all times.

Support Access

If you need help installing or verifying delivery, you can:

• Book a 10-minute screenshare
  
• Allow temporary access for support installation
  
• Contact support directly
  

Most installations take only a few minutes.

Key Takeaway

Outgoing Delivery is explicit, reversible, and controlled.

You decide:

• When enriched content is delivered
  
• How it is installed
  
• When it can be disabled
  

CatalogPilot never assumes delivery — it waits for your approval.

The Dashboard is the operational control center of CatalogPilot. It provides merchants with a real-time, high-level view of catalog status, enrichment progress, review requirements, delivery activity, and subscription limits — without requiring technical knowledge.

Everything on the Dashboard is designed around three principles:

1. Transparency – You can always see what is happening and why.
   
2. Control – Nothing is delivered without approval unless explicitly authorized.
   
3. Safety – All actions are reversible and non-destructive.
   

1. Merchant Identity & Session Status

At the top left of the Dashboard, you will see:

• Store Name – The merchant storefront currently connected to CatalogPilot.
  
• Account User – The logged-in user.
  
• Last Login Timestamp – Displays the most recent login time (UTC).
  
• Storefront Link Icon – Opens the live storefront in a new tab.
  

This area confirms which catalog you are working on and prevents accidental actions on the wrong store.

2. Connection & Automation Status Indicators

Next to the store identity are four status indicators:

• API Connected
  Confirms CatalogPilot is successfully connected to your eCommerce platform for catalog synchronization.
  
  
• Catalog Sync
  Indicates that product data is being read and kept in sync with your platform.
  
  
• Auto-Enrich (Support-controlled)
  Disabled by default. When enabled by CatalogPilot Support under agreement, approved products are automatically queued for enrichment.
  
  
• Auto-Approve (Support-controlled)
  Disabled by default. When enabled under agreement, enriched items are automatically approved without manual review.
  
  

By default, CatalogPilot requires explicit human approval for all enriched content. Auto-features are intentionally restricted to maintain enterprise-level control and data integrity.

3. Catalog Status Ring & Counts

The circular chart provides an immediate snapshot of catalog state:

• Approved – Items fully reviewed and approved.
  
• Awaiting Review – Items enriched but not yet approved.
  
• Ready to Enrich – Items eligible for enrichment.
  

The numeric counters beside the ring provide exact counts for each state.

This ring reflects catalog readiness, not delivery status.

4. Enrichment Mode Selection

The Choose Enrichment Mode panel controls how items are selected for enrichment:

Auto

Automatically selects the oldest eligible items (by initial import order).

This is the safest and fastest way to progress through large catalogs.

Products

Allows manual selection of individual products via a searchable pop-up.

Categories

Allows selection of one or more categories and applies enrichment to products within them, up to the selected batch limit.

5. Batch Size Control

The slider allows you to select how many products to include in the next batch:

• The maximum value is capped by administrator-defined limits to ensure system stability and review quality.
  
• Batch limits can be increased by CatalogPilot Support upon request.
  

This ensures enrichment happens in manageable, reviewable increments.

6. Batch Estimation & Pricing

Estimate Batch

Generates a cost estimate for the currently selected items.

Estimate All Items Ready to Enrich

Provides a full estimate for everything currently eligible for enrichment across the catalog.

Pricing is shown transparently by item type (products, variants, categories, images), and translation pricing is clearly noted when applicable.

7. Review Indicator Badge

On the right side of the Dashboard is the Review Badge:

• Blue Badge – Indicates the number of products waiting for review. Clicking it takes you directly to the Review screen.
  
• Green Badge – Indicates zero items require review.
  

This ensures review tasks are never missed.

8. Subscription Tier Display

Below the review badge is your current subscription tier:

• Displays Tier level
  
• Shows the maximum catalog size allowed under that tier
  

CatalogPilot requires your tier to match your active catalog size for enrichment to be available across the full catalog.

9. Active Batch Panel

When a batch is running, a progress panel appears showing:

• Current status (Queued / Enriching / Finalizing)
  
• Progress bar
  
• ETA (when available)
  
• Item-level counts for:
  
• Products
  
• Variants
  
• Categories
  
• Images
  

The panel also indicates which item is currently being enriched.

You may safely leave this page — enrichment continues automatically in the background and you will be notified when it completes.

10. Final Product Catalog Panel

This panel reflects the approved state of your catalog:

• Categories
  
• Products
  
• Images
  
• Variants
  
• Total generated tag count
  

The tag count is intentionally high because:

• Each product generates 30–50 structured tags
  
• Each image, variant, and category contributes additional records
  
• Inherited and relational metadata is counted independently
  

This represents the full structured footprint of your catalog.

11. Storefront Discoverability Panel (Outgoing)

This panel shows what has been delivered to your storefront during the current delivery cycle:

• Categories
  
• Products
  
• Variants
  
• Images
  
• Total delivered tags
  

These numbers:

• Update approximately every 15 minutes
  
• Reflect delivery activity, not catalog totals
  
• Confirm that approved content is actively reaching the storefront
  

A timestamp shows the last successful delivery.

12. Safety & Philosophy

Every element of the Dashboard is designed to ensure:

• No platform data is overwritten
  
• No content is delivered without approval
  
• All actions are observable
  
• Delivery can be disabled instantly
  

CatalogPilot operates as an intelligence and delivery layer — not a replacement for your platform.

Purpose of the Review Page

The Review page is the primary quality-control checkpoint in CatalogPilot.

Its role is to give merchants fast, low-cognitive confirmation that enriched product data is accurate, improved, and safe to approve — without requiring deep technical review or repetitive editing.

This page is intentionally designed to:

• Minimize cognitive load
  
• Encourage visual comparison rather than line-by-line validation
  
• Reinforce trust in the enrichment system
  
• Make bulk approval the normal and safe action
  

CatalogPilot assumes that merchants want control, not busywork.

Review Status Overview (Top Counters)

At the top of the Review page, merchants see a summary of items awaiting review:

• Products Awaiting Review
  
• Images Awaiting Review
  
• Variants Awaiting Review
  
• Categories Awaiting Review
  

These counters represent items that have completed enrichment and are pending merchant approval.

Important:

Not every enriched object appears here.

Many records (such as inherited variant data or category-level metadata) are derived from already-approved sources and do not require redundant review.

Review Queue Tabs

The Review Queue is divided into four tabs:

• Products (primary focus)
  
• Variants
  
• Images
  
• Categories
  

Product Tab (Primary Review Focus)

The Products tab is the only tab most merchants need to meaningfully review.

This tab displays enriched versions of product-level content that merchants are already familiar with from their eCommerce platform, including:

• Product Title
  
• Description
  
• Meta Title & Meta Description
  
• Structured headings (H1, H2, H3)
  

These fields represent the largest and most visible change compared to the original catalog and are where merchants will most easily recognize value.

Original vs Enriched Comparison

CatalogPilot provides two levels of comparison controls:

1. Global toggle buttons (Original / Enriched)
   
2. Per-section toggles (for Products, Variants, Images, Categories)
   

These toggles allow merchants to quickly switch between:

• Original — the data as it existed in the platform
  
• Enriched — the AI-generated, optimized version
  

The intent is visual validation, not forensic inspection.

Merchants are encouraged to:

• Scroll through the Product list
  
• Toggle Original ↔ Enriched
  
• Confirm that the enriched content is clearly more complete, descriptive, and structured
  

This comparison can typically be completed in seconds per product.

Edit vs Approve

Each product row includes two actions:

• Approve (Primary action)
  
• Edit (Secondary, intentionally de-emphasized)
  

Edit Button (Use Sparingly)

The Edit option exists for edge cases only.

Using Edit:

• Increases cognitive load
  
• Interrupts batch-level review flow
  
• Is unnecessary for the vast majority of products
  

CatalogPilot strongly encourages merchants to approve unless something is clearly incorrect.

The system is designed to avoid drift, hallucination, or destructive changes.

Editing is always available.

Even after approval, merchants can edit any enriched field at any time from the product view. Approval simply enables delivery and visibility — it does not lock content. This allows merchants to move quickly into the main product view, review everything at a glance, and make targeted edits only if needed.

Variants Tab (Verification Only)

The Variants tab is intended for confirmation, not review.

What merchants should look for:

• Variants match the parent product
  
• Attributes such as size, color, or style are correctly represented
  

What merchants do not need to do:

• Edit variant descriptions
  
• Manually review repeated content
  
• Validate every variant independently

Why This Works

CatalogPilot builds independent structured records for each variant while inheriting approved product data.

This allows:

• Each variant to be indexed independently
  
• Improved long-tail discoverability
  
• Amplified schema coverage without duplication risk
  

Images Tab (ADA & Descriptive Validation)

The Images tab shows enriched image metadata, including:

• Image titles
  
• Alt text (ADA / WCAG)
  
• Descriptive captions
  

Merchants should:

• Glance to confirm descriptions are accurate
  
• Ensure imagery is clearly described
  
• Avoid over-editing unless something is factually wrong
  

The image enrichment system is designed to be:

• Highly consistent
  
• Stylistically aligned
  
• Safe for accessibility and search engines
  

Categories Tab (Search & Discovery Optimization)

The Categories tab reflects metadata generated for category-level discovery.

Most merchants do not have native access to category SEO fields in their platform.

Category enrichment is:

• Primarily for search engines and crawlers
  
• Not intended for frequent human editing
  
• Safe to approve as a group
  

This is one of the key ways CatalogPilot improves site-wide discoverability beyond product pages.

Approve All (Primary Action)

At the top of the Review Queue is the Approve All button.

This is the expected and encouraged action.

When clicked:

• All currently reviewed items are approved instantly
  
• Approved content becomes eligible for delivery
  
• Merchants can immediately navigate to live product pages to see results
  

Approval does not wait for background jobs to complete; it acts on finalized records only.

Partial Visibility Is Intentional

Not all enriched records appear in the Review Queue.

This is by design.

CatalogPilot avoids:

• Redundant review
  
• Re-approval of inherited data
  
• Cognitive overload
  

Only records that introduce new or materially changed information are surfaced for review.

Summary: How Merchants Should Use Review

1. Open the Review page
   
2. Focus on the Products tab
   
3. Toggle Original ↔ Enriched
   
4. Scroll and visually confirm improvements
   
5. Click Approve All (recommended for most cases)
   
6. Move on — detailed edits can be made later from the full product gallery view if needed
   

For most merchants, this entire process takes minutes, not hours.

The Incoming section represents the live connection between your eCommerce platform and CatalogPilot.

This is the primary data pipeline that allows CatalogPilot to observe your catalog so enrichment can occur safely and externally.

This form is completed during onboarding and remains accessible for reference and updates.

What This Connection Does

CatalogPilot’s connector:

• Securely reads your platform’s catalog data
  (products, images, descriptions, categories)
  
• Maintains ongoing synchronization
  
• Does not write, modify, or push data back to your platform
  
• Does not interfere with pricing, inventory, checkout, or orders
  

CatalogPilot always operates outside your platform’s database.

This is reinforced by the inline tooltip shown in the interface.

Connection Status & Health

At the top of the panel, merchants can see:

• Last Synced timestamp
  
• Sync Status indicator (green = healthy)
  
• Running toggle
  

This confirms the connector is active and communicating correctly.

If syncing is paused or interrupted, CatalogPilot will surface that state clearly and safely.

Connection Details Explained

Store Name

The human-readable name of your store as it appears in CatalogPilot.

API Key / API Secret

Credentials used to authenticate read-only access.

Secrets are masked by default and stored securely.

Storefront URL

The canonical URL of your storefront.

Used for validation, crawling context, and delivery alignment.

Cluster

Identifies the regional infrastructure handling your catalog

(e.g., us1). This is managed automatically and rarely needs adjustment.

Language Code

Primary language used for enrichment.

CatalogPilot only enriches languages that already exist in your platform.

Currency Code

Used for normalization and reference only.

CatalogPilot does not calculate or modify pricing.

Legal & Compliance References

To ensure transparency and compliance, merchants must provide:

• Privacy Policy URL
  
• Terms & Conditions URL
  

These links are used later to attach provenance and compliance signals to enriched product and category records.

They do not replace your platform’s policies — they reinforce them.

Saving Changes

Changes to this form:

• Are validated before saving
  
• Do not retroactively alter past enrichments
  
• Apply safely to future sync and enrichment cycles
  

In most cases, merchants will rarely need to edit this section after onboarding.

Design Philosophy

This panel is intentionally simple and conservative.

It exists to answer three questions:

1. Is my catalog connected?
   
2. Is it syncing safely?
   
3. Can I trust that nothing destructive is happening?
   

If the status is green, the answer to all three is yes.