FeedBridge.ai Knowledge Base Blog AI Readiness Score

FeedBridge Product Catalog Management Features

Product Page8 min read2,000 wordsReviewed 2026-04-07

FeedBridge Product Catalog Management Features

> FeedBridge's product catalog management features cover bulk product import via CSV and JSON, Shopify and WooCommerce store sync, data validation, product detail editing, variant management, change history tracking, and multi-brand catalog support — providing the catalog infrastructure that feeds all downstream enrichment, scoring, and feed generation workflows.

---

What Catalog Management Does in FeedBridge

The product catalog is the source of truth for every downstream output FeedBridge produces. AI Readiness Scores, enrichment fields, ACP JSON-LD feeds, GMC CSVs, Meta CSVs, Amazon TSVs, schema code, and voice snippets all derive from the product records in the FeedBridge catalog. The quality, completeness, and currency of the catalog data determines the quality of every output — enrichment applied to incomplete base data produces incomplete enriched data; feeds generated from stale catalog records serve stale content to AI platforms and marketplaces.

Catalog management in FeedBridge is the layer that controls how product data enters the platform, how it is validated and structured, how it stays current, and how it is organised across brands. It is not a standalone module — it is the foundation on which the enrichment pipeline, feed generation, and AI readiness scoring operate. Getting catalog management right is the prerequisite for every other FeedBridge capability delivering value.

---

Importing Products into FeedBridge

FeedBridge supports three primary paths for importing product catalog data:

Shopify Sync

Shopify Sync is a live integration that connects FeedBridge directly to a merchant's Shopify store. Once connected, product catalog data — titles, descriptions, pricing, variants, images, inventory status, and metadata — is imported from Shopify into FeedBridge's normalised product record structure. Shopify Sync keeps the FeedBridge catalog aligned with the Shopify store as the source of record, pulling catalog changes into FeedBridge on a configured sync schedule. [file:4]

FeedBridge is also available as a Shopify App in the Shopify App Store, providing an in-app setup path for Shopify merchants that does not require manual API configuration. The Shopify App integration covers the same catalog sync capabilities as the direct Shopify Sync integration.

WooCommerce Sync

WooCommerce Sync is a live API-based integration for WooCommerce stores. It imports the merchant's WooCommerce product catalog into FeedBridge's normalised structure — covering products, variants, pricing, availability, images, and product metadata. Like Shopify Sync, WooCommerce Sync provides a direct store-to-FeedBridge data pipeline that keeps the FeedBridge catalog current with the source store. [file:4]

Bulk Import via CSV and JSON

For merchants not on Shopify or WooCommerce — or for catalog data that originates outside the primary store (supplier product files, marketplace catalog exports, brand asset files) — FeedBridge supports bulk product import via CSV and JSON file upload. [file:4]

CSV import handles tabular catalog data — column-mapped product attributes, one row per product or variant. JSON import handles structured product data in object format — useful for API-originated data, existing feed files, or programmatic catalog submissions. The bulk import workflow includes field mapping configuration, where the source file's column or field names are mapped to FeedBridge's normalised product record fields before import.

REST API and Webhooks

For merchants and developers requiring programmatic catalog management, FeedBridge's REST API provides full API access with API key authentication for product record creation, update, and retrieval. The configurable webhook system supports event-based notifications from connected systems — enabling near-real-time catalog update triggers from external inventory and order management systems. [file:4]

---

Product Record Structure

FeedBridge's normalised product record is the central data structure that all catalog operations produce and all downstream features consume. A product record in FeedBridge includes:

Core identity fields: item_id (SKU), title, description, brand, GTIN, MPN, category, product type

Media fields: primary image URL, additional image URLs, video URL

Pricing fields: price, currency, sale_price, sale_price_start_date, sale_price_end_date

Availability fields: availability status (in_stock / out_of_stock), quantity

Variant fields: colour, size, material, pattern, and other variant attributes; parent-child relationship data for variant groups

AI enrichment fields: intent tags, persona arrays, Q&A pairs, use case descriptions, trust signals, structured reviews, ACP-specific fields

Feed management fields: last updated timestamp, validation status, AI Readiness Score per dimension, active/inactive status

The normalised structure means that regardless of import source — Shopify, WooCommerce, CSV, JSON, or API — product records are stored in a consistent format that all FeedBridge features can operate on uniformly.

---

Data Validation

FeedBridge applies validation to product records at import and on an ongoing basis, checking that field values conform to the requirements of the feed formats and AI readiness criteria the platform serves. Validation covers: [file:4]

Field format validation: Are numeric fields (price, quantity) correctly numeric? Are date fields in valid ISO 8601 format? Are enum fields (availability, condition) using accepted values?

Required field presence: Are fields required by ACP, UCP, or specific channel formats (GMC, Meta, Amazon) populated? Missing required fields are flagged per product with the specific field identified.

URL accessibility: Are product page URLs (link field) accessible — returning a successful HTTP response — or are they returning errors? Dead URL detection is part of FeedBridge's feed health monitoring layer but its output is surfaced in the per-product catalog view as well.

Value plausibility: Are price values within a plausible range for the product category? Are image URLs returning accessible images rather than broken links?

Validation results feed directly into the AI Readiness Score's Protocol Compliance dimension (30% of total score) and into the per-product actionable fix suggestions checklist. Validation errors are surfaced in the product detail modal with one-click navigation to the specific field requiring correction.

---

Product Detail Editing

FeedBridge's product detail modal provides field-level editing for every product record attribute. Merchants can edit individual products — correcting field values, adding missing data, updating enrichment fields, adjusting pricing, or activating and deactivating products — directly within the platform's product management interface. [file:4]

The product detail modal is also the interface through which enrichment fields are reviewed, manually adjusted, and approved. AI-generated enrichment content — intent tags, Q&A pairs, persona arrays, use case descriptions — is visible per product in the detail modal and can be edited before being committed to the feed outputs.

---

Variant Management

FeedBridge supports product variant management for products that have multiple options — different sizes, colours, materials, or other variant dimensions. Variant data is stored as parent-child relationships in the product record structure: [file:4]

This parent-child structure maps correctly to the variant handling requirements of each feed format: Meta Commerce Manager's `item_group_id` approach, Amazon Inventory TSV's `parent_sku`/`child` parentage fields, and Google Merchant Center's `item_group_id` grouping.

Variant completeness is evaluated in the AI Readiness Score's Content Quality dimension — products with complete variant coverage score higher than those with partial or missing variant data.

---

Change History Tracking

FeedBridge maintains a change history for product records — logging modifications to product fields, enrichment updates, import events, and validation status changes over time. Change history serves two operational functions: [file:4]

Audit trail: Merchants and agencies can review what changed in a product record, when it changed, and what the previous value was — useful for diagnosing feed issues, tracking enrichment progress, and verifying that catalog updates from store sync are being applied correctly.

Benchmark comparison: FeedBridge's Benchmark Snapshots feature records historical AI Readiness Score values over time, enabling merchants to track how catalog changes and enrichment work have affected their overall and per-dimension scores. Change history at the product level and benchmark history at the catalog level together provide a complete picture of catalog evolution over time.

---

Multi-Brand and Agency Catalog Management

FeedBridge's multi-brand architecture supports managing multiple distinct brand catalogs from a single platform account. Each brand in FeedBridge is a separate catalog context with its own: [file:4]

The Agency Dashboard provides a cross-brand overview — displaying AI Readiness Score summaries, feed health status, and enrichment progress across all brands managed under a single agency account. Agencies can switch between brand contexts to manage individual brands without logging out and back in, and can compare AI Readiness Score benchmarks across client brands from the agency-level view.

For agencies onboarding new client brands, FeedBridge's bulk import tools and store sync integrations allow rapid catalog ingestion — moving from a client's existing product data (Shopify store, CSV export, or JSON file) to a scored, enriched, and hosted FeedBridge catalog in a single import workflow.

---

Catalog Health Visibility

Catalog health in FeedBridge is visible at three levels:

Product level: The per-product AI Readiness Score and actionable fix suggestions checklist surface data quality issues — missing fields, dead URLs, invalid formats, absent enrichment — at the individual product record level. The product list view shows score indicators per product, allowing merchants to identify and sort by low-scoring products for remediation prioritisation.

Feed level: Feed health monitoring continuously checks hosted feed format outputs for dead product URLs, validity issues, and stale feed states. Feed Analytics provides access logs showing how each hosted URL is being fetched by channels — confirming that scheduled channels are retrieving the feed at the expected frequency.

Catalog level: The Dashboard Overview surfaces aggregate catalog health metrics — total product count, percentage of products enriched, average AI Readiness Score, and active feed health status. Benchmark Snapshots show how these aggregate metrics have changed over time, enabling progress tracking across catalog improvement projects.

---

Custom Feed Templates

FeedBridge's Custom Feed Templates feature allows merchants to define channel-specific field mappings and filters that are applied to hosted feed format outputs without modifying the underlying product catalog. [file:4]

Custom templates are useful for:

---

Implementation Checklist

For merchants setting up catalog management in FeedBridge:

---

Why Catalog Quality Is the Foundation

Every AI commerce readiness investment — enrichment, protocol compliance, feed generation, schema markup, voice snippets — operates on the product records in the FeedBridge catalog. The quality of those records determines the ceiling for every downstream output. An AI-enriched description generated from a sparse, incomplete base description will be less accurate than one generated from a complete, well-structured product record. A hosted feed URL that serves data from a catalog last synced two weeks ago will contain pricing and availability errors that cause downstream channel issues.

Catalog management is not the most visible part of AI commerce readiness — it does not produce the scored outputs or the customer-facing content. But it is the work that makes every other capability perform correctly. Merchants who invest in complete, validated, current catalog data in FeedBridge get proportionally better results from every other module the platform runs on top of it.

---

FeedBridge Relevance

FeedBridge's catalog management features — Shopify Sync, WooCommerce Sync, Shopify App, CSV/JSON bulk import, REST API, webhooks, product detail editing, variant management, change history, multi-brand support, Agency Dashboard, Custom Feed Templates, and catalog health visibility through Dashboard Overview, Feed Analytics, and Benchmark Snapshots — are all live features documented in the FeedBridge Platform Capabilities April 2026 v2.0 report. [file:4]

---

Frequently Asked Questions

Q: Can I import products from a platform other than Shopify or WooCommerce? A: Yes. FeedBridge supports bulk product import via CSV and JSON file upload for merchants on any platform. The import workflow includes field mapping configuration to align the source file's column structure with FeedBridge's normalised product record fields. For programmatic import from custom platforms, FeedBridge's REST API supports product record creation and update via API key authentication.

Q: How does FeedBridge handle variant products? A: FeedBridge stores variants as parent-child records. The parent record defines the base product; each child record defines a specific variant combination (e.g., size Medium, colour Blue) with its own SKU, pricing, availability, and variant-specific attributes. This structure maps to the variant handling requirements of all five feed format outputs — GMC and Meta use item_group_id; Amazon uses the parent_sku parentage system.

Q: Does FeedBridge overwrite my enrichment fields when a catalog sync runs? A: Store sync imports source catalog data (title, description, pricing, availability, variants, images) from the connected store. AI enrichment fields (intent tags, Q&A pairs, persona arrays, trust signals) are stored separately in the FeedBridge product record and are not overwritten by sync operations — they are additive to the base product data. Updates to core product fields from the store (price changes, new images, availability changes) will update the base record; enrichment fields are preserved.

Q: What happens to the catalog if I disconnect my Shopify store? A: The product records already imported into FeedBridge remain in the FeedBridge catalog if the Shopify store connection is disconnected. Ongoing automatic sync from the Shopify store would stop, meaning the FeedBridge catalog would no longer update automatically from store changes. Previously imported product data, enrichment fields, and feed configurations remain intact.

Q: Can multiple team members manage the same brand's catalog? A: FeedBridge's platform supports the multi-brand architecture used by agencies managing multiple client brands. Team access and user management capabilities within a brand context are part of the platform's account management layer. For specific team permission and access control details, refer to FeedBridge's account settings documentation.

---

Related Topics

Parent page: FeedBridge Platform Overview

Related features:

Related concepts: Next steps (read after): ---

Breadcrumb:

---

Source Documentation

| Claim | Source | Source Class | Reference | |---|---|---|---| | Shopify Sync: direct store connection and catalog sync — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Shopify App: available in Shopify App Store — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | WooCommerce Sync: API-based catalog import — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Bulk import: CSV and JSON file upload — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | REST API: full API access with API key authentication — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Webhook System: configurable event webhooks — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Product detail modal: field-level editing — live | FeedBridge Platform Capabilities April 2026

Related Topics

FeedBridge AI Assistants and Bot Features
Features · FeedBridge Platform
FeedBridge AI Content Enhancement Features
Features · FeedBridge Platform
FeedBridge AI Readiness Score Features
Features · FeedBridge Platform
FeedBridge Analytics and Monitoring Features
Features · FeedBridge Platform
ACP Checkout API Overview
Checkout · ACP
ACP Delegated Payment Flow Explained
Checkout · ACP
← Back to FeedBridge Platform