FeedBridge Feed Generation and Distribution Features

> FeedBridge generates and hosts five product feed format outputs — ACP JSON-LD, UCP Interactive Protocol, Google Merchant Center CSV, Meta Commerce Manager CSV, and Amazon Inventory File TSV — each served from a CDN-backed hosted URL unique per brand, with configurable refresh scheduling, continuous feed health monitoring, and multi-channel alert notifications.

---

What Feed Generation and Distribution Does

Feed generation and distribution is the output layer of the FeedBridge pipeline — the point at which enriched, validated, scored product catalog data is rendered into the channel-specific formats that AI shopping platforms, marketplaces, and search surfaces consume, and delivered to those channels via stable hosted URLs that each channel registers once and continues fetching on its own schedule.

The core operational model is: one product catalog, five simultaneous feed outputs, all served from hosted URLs that update automatically when the catalog changes. Merchants do not maintain separate product data sets for each channel — they maintain one catalog in FeedBridge, and the feed generation layer renders the appropriate format for each channel from that single source of record. This ensures consistency of product data across channels — the same title, price, availability, and enrichment content appears in every channel's feed, normalised to that channel's format specification. [file:4]

---

The Five Feed Format Outputs

ACP JSON-LD — Agentic Commerce Protocol Feed

The ACP JSON-LD feed is FeedBridge's AI-native feed format — the primary output for AI shopping platforms that support the Agentic Commerce Protocol. It is a JSON-LD structured feed file that encodes the full enriched product record in ACP-compliant format, including all AI enrichment fields that standard feed formats do not carry. [file:4]

The ACP JSON-LD feed includes all standard product identity and transactional fields (item_id, title, description, brand, GTIN, MPN, price, currency, availability, images, category), the full AI enrichment payload (intent tags array, persona arrays, Q&A pair objects, use case descriptions, trust signal objects), ACP-specific fields (structured reviews as a JSON array with reviewer name, rating, and review text; sale pricing with valid ISO 8601 start and end date fields), and complete parent-child variant data. The ACP JSON-LD feed is hosted at a CDN-backed URL unique per brand and registered with ACP-enabled AI platforms as the authoritative product data source for that brand. For a full explanation of ACP feed structure and field requirements, see ACP Feed JSON-LD Format Explained.

UCP Interactive Protocol — Universal Commerce Protocol

The UCP output is not a single downloaded feed file — it is a set of REST API endpoints that FeedBridge generates and maintains per brand, conforming to the Universal Commerce Protocol specification. UCP-compatible AI platforms query these endpoints directly rather than downloading a feed file. [file:4]

FeedBridge's UCP implementation includes the UCP Manifest (generated at `.well-known/ucp` per brand, declaring capabilities, supported endpoints, and authentication requirements), the Catalog Search endpoint (keyword and filter-based product search), the Catalog Lookup endpoint (item-level retrieval by `item_id` or barcodes — GTIN/MPN), and the Cart endpoint (add-to-cart and checkout session creation). The UCP Dashboard Hub provides a compliance scorecard and capability checklist showing endpoint status, validation results, and remaining compliance gaps. For a full explanation of UCP, see Universal Commerce Protocol (UCP) Explained.

Google Merchant Center CSV

The Google Merchant Center (GMC) CSV maps FeedBridge's normalised product record to Google's required and recommended product attributes for Google Shopping and Google AI Mode. FeedBridge's GMC output includes all Google-required fields (id, title, description, link, image_link, availability, price, brand, condition) and recommended fields (additional_image_link, gtin, mpn, product_type, google_product_category, sale_price, sale_price_effective_date, colour, size, material, age_group, gender). The AI-enhanced title and description from FeedBridge's enrichment pipeline populate the GMC `title` and `description` fields — improving the product content quality that Google's AI surfaces index and serve to buyers. For a full explanation of GMC feed requirements, see Google Merchant Center Feed Format. [file:4]

Meta Commerce Manager CSV

The Meta Commerce Manager CSV maps FeedBridge's product records to Meta's catalog data specification for Facebook Shops and Instagram Shopping. FeedBridge's Meta CSV output covers Meta's required fields (id, title, description, availability, condition, price, link, image_link, brand) and Meta-specific fields including `item_group_id` for variant grouping, `sale_price`, `sale_price_effective_date`, and additional image fields. Variant parent-child relationships are represented using Meta's `item_group_id` approach, ensuring variant product families display correctly within Facebook and Instagram shopping surfaces. For a full explanation of Meta feed requirements, see Meta Commerce Manager Feed Format. [file:4]

Amazon Inventory File TSV

The Amazon Inventory File TSV is a tab-separated values flat file formatted to Amazon's Seller Central inventory file specification for the Amazon US marketplace. FeedBridge's Amazon TSV output maps product records to Amazon's required and recommended fields — including `item_sku`, `item_name`, `product_description`, `brand_name`, `manufacturer`, `part_number`, `standard_price`, `quantity`, `product_id` (GTIN/UPC), `product_id_type`, `condition_type`, `main_image_url`, and additional image fields. [file:4]

The Amazon TSV supports the parent-child variant structure using Amazon's `parentage` field system — `parent` records define the base product; `child` records define each variant with the `parent_sku` reference field linking them. This ensures that variant product families are correctly structured in Amazon Seller Central's catalog system.

Known gap: The Amazon Inventory File TSV is currently live for the Amazon US marketplace only. Amazon EU marketplace template support is a medium-priority roadmap item, not yet live as of April 2026. Merchants selling on Amazon EU marketplaces should note this limitation and contact FeedBridge for current status. For a full explanation of Amazon feed requirements, see Amazon Inventory File TSV Format.

---

Feed Format Summary

| Feed Format | Channel | Delivery Method | AI Enrichment Included | |---|---|---|---| | ACP JSON-LD | ChatGPT Shopping, ACP AI platforms | Hosted URL (JSON-LD file) | Yes — full enrichment payload | | UCP Interactive Protocol | Google AI Mode, UCP platforms | REST API endpoints | Yes — via Catalog Search/Lookup | | Google Merchant Center CSV | Google Shopping, Google AI Mode | Hosted URL (CSV file) | Partial — AI-enhanced title/description | | Meta Commerce Manager CSV | Facebook Shops, Instagram Shopping | Hosted URL (CSV file) | Partial — AI-enhanced title/description | | Amazon Inventory File TSV | Amazon Seller Central (US) | Hosted URL (TSV file) | Partial — AI-enhanced title/description |

---

Hosted URLs and CDN Delivery

Every feed format output in FeedBridge is served from a hosted URL that is unique per brand and per format. These hosted URLs are the distribution endpoints that each channel registers once — as the product data source for that brand — and continues fetching automatically at the channel's own crawl schedule or at the interval configured in FeedBridge's feed scheduling settings. [file:4]

Hosted feed URLs are backed by a CDN (Content Delivery Network), meaning the feed content is geographically distributed and served from edge locations close to the requesting channel's infrastructure. CDN delivery provides three operational benefits for feed distribution:

Reliability: CDN-backed URLs are highly available — individual server failures do not interrupt feed delivery, as requests are routed to available edge nodes automatically.

Performance: Feed files served from CDN edge locations load faster for channel crawlers regardless of where the requesting system is geographically located — reducing fetch latency and the risk of feed fetch timeouts that can cause channels to serve stale cached data.

Scalability: Large catalog feeds — containing thousands of products with full enrichment payloads — are served efficiently via CDN without performance degradation at scale.

Each brand's hosted feed URLs are stable — they do not change when feed content updates. A channel that has registered a FeedBridge-hosted feed URL will continue fetching the latest feed content at that same URL indefinitely, as FeedBridge updates the content at the URL with each feed refresh cycle.

---

Feed Scheduling

FeedBridge's feed scheduling feature allows merchants to configure the refresh interval at which each hosted feed format is regenerated from the current product catalog. Configurable auto-refresh intervals ensure that pricing changes, availability updates, new product additions, and enrichment improvements are reflected in the hosted feed outputs within the configured refresh window. [file:4]

Feed scheduling is the current recommended mechanism for keeping hosted feeds current with catalog changes — including availability and price changes. Merchants with high-velocity inventory should configure the most frequent available refresh interval to minimise the window between a catalog change and its reflection in the hosted feed outputs.

Known gap: Webhook-based real-time inventory sync — push-based price and availability updates that would update hosted feeds immediately when a change occurs, without waiting for the next scheduled refresh — is a high-priority roadmap item, not yet live as of April 2026. Until real-time sync is available, scheduled feed refresh at the most frequent available interval is the recommended approach for merchants where inventory accuracy is time-sensitive.

---

Feed Health Monitoring

FeedBridge monitors the health of all hosted feed format outputs continuously — checking feed validity, URL accessibility, and content currency on an ongoing basis. Feed health monitoring covers three dimensions: [file:4]

Dead URL detection: FeedBridge checks that the product page URLs (`link` field) and image URLs (`image_link`, `additional_image_link`) referenced in each feed are accessible — returning successful HTTP responses rather than 404s, redirects, or server errors. Dead URLs in a feed cause channel-side product rejection or suppression; detecting and flagging them in FeedBridge allows merchants to correct broken URLs before channels suppress the affected products.

Feed validity tracking: FeedBridge validates that each hosted feed format output conforms to its channel specification — checking that required fields are present, that field formats are correct, and that the feed file itself is well-formed (valid JSON-LD, parseable CSV, correctly structured TSV). Feed validity failures at the format level can cause entire feeds to be rejected by channel systems rather than individual product suppression.

Stale feed detection: FeedBridge monitors whether hosted feed URLs are being fetched by registered channels at expected intervals, and flags feeds that have not been updated within the expected refresh window — alerting merchants when a feed may be stale due to a scheduling misconfiguration or sync failure.

Feed health status is visible in the FeedBridge platform dashboard at both the product level (per-product URL validity flags in the product list view) and the feed level (overall feed health status per format in the Feed Analytics view).

---

Feed Alert Notifications

When feed health monitoring detects an issue — a dead URL, a feed validity failure, a stale feed, or a feed fetch anomaly — FeedBridge triggers alert notifications to configured notification channels. [file:4]

FeedBridge supports four alert delivery methods:

| Alert Channel | Notification Type | |---|---| | Email | Feed health alerts sent to configured email addresses | | Slack | Alerts posted to a configured Slack channel via webhook | | Discord | Alerts posted to a configured Discord channel via webhook | | Webhook | HTTP POST alerts delivered to a configured endpoint URL |

Alert preferences are configurable per brand — merchants can choose which alert types trigger notifications and which delivery channels receive them, allowing feed health alerting to be integrated into existing operational monitoring workflows.

---

Feed Analytics

FeedBridge's Feed Analytics feature provides access log data for each hosted feed URL — recording fetch events with user agent, country of origin, HTTP response code, and response time. [file:4]

Feed Analytics serves two operational functions:

Channel confirmation: Merchants can verify that registered channels (Google, Meta, Amazon, AI platforms) are actively fetching their hosted feed URLs at the expected frequency — confirming that feed registration was successful and that the channel is receiving current product data.

Anomaly detection: Unusual fetch patterns — a channel that was fetching daily and has stopped, a new user agent fetching the feed unexpectedly, or a spike in fetch errors — are visible in the access log and can trigger investigation before the issue affects channel performance.

---

Custom Feed Templates

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

Custom templates are useful for three scenarios:

Non-standard field mappings: When a specific retailer or marketplace requires field names or value formats that differ from the standard channel specification — alternate attribute names, custom category taxonomies, or value normalisation rules — a Custom Feed Template applies the required transformation to the feed output without changing the base product record.

Catalog subsetting: When a channel should receive only a subset of the full catalog — specific categories, products above a price threshold, or in-stock products only — a Custom Feed Template defines the filter logic that limits which products appear in the channel's feed output.

Multi-region variants: When the same catalog needs to produce separate feed outputs for different geographic markets — with region-specific pricing, currency, or availability — Custom Feed Templates define the per-region transformation rules that generate distinct feed outputs from a single product catalog.

---

Implementation Checklist

For merchants setting up feed generation and distribution in FeedBridge:

[ ] Verify all five feed format outputs are generated — after catalog import and enrichment, confirm that ACP JSON-LD, UCP endpoints, GMC CSV, Meta CSV, and Amazon TSV outputs are all active and returning valid content at their hosted URLs
[ ] Register hosted URLs with each channel — submit each format's hosted URL to the relevant channel platform (Google Merchant Center, Meta Commerce Manager, Amazon Seller Central, ACP-enabled AI platforms) as the product data source for the brand
[ ] Configure feed scheduling — set the auto-refresh interval for each feed format to match the catalog's change frequency; use the most frequent interval available for high-velocity inventory
[ ] Configure feed health alert preferences — set up email, Slack, Discord, or webhook alerts for feed health events so that issues are detected and addressed promptly
[ ] Register UCP manifest — confirm the UCP manifest is accessible at `.well-known/ucp` and register it with UCP-compatible platforms (Google AI Mode)
[ ] Check Feed Analytics — after channel registration, verify in Feed Analytics that each channel is actively fetching the hosted URL at the expected frequency
[ ] Set up Custom Feed Templates — for any channels with non-standard field requirements or catalog filtering needs, configure Custom Feed Templates before submitting the hosted URL
[ ] Note Amazon EU limitation — for merchants selling on Amazon EU marketplaces, note that the Amazon TSV is currently US-only; monitor FeedBridge's roadmap for EU template availability

---

Why It Matters for Merchants

Feed generation and distribution is the mechanism by which enriched, AI-ready product data reaches the channels where buyers actually shop. A perfectly enriched product record in FeedBridge that is not delivered to channels produces no commerce outcome — the feed layer is what converts catalog investment into channel presence.

The hosted URL model with CDN delivery and automatic refresh solves a significant operational problem for multi-channel merchants: maintaining accurate, consistent, and up-to-date product data across five or more channels simultaneously without managing five separate data pipelines. FeedBridge's feed generation layer consolidates that complexity into a single catalog management workflow, with channel-appropriate format rendering, health monitoring, and scheduling handled automatically. The result is that a price change, a new image, or a new Q&A pair added to a product record in FeedBridge propagates to all five channel feeds within the next scheduled refresh cycle — without any manual channel-by-channel update work.

---

FeedBridge Relevance

All five feed format outputs (ACP JSON-LD, UCP Interactive Protocol, Google Merchant Center CSV, Meta Commerce Manager CSV, Amazon Inventory File TSV for US), CDN-backed hosted URLs per brand, configurable feed scheduling, feed health monitoring (dead URL detection, validity tracking, stale feed detection), Feed Analytics (access logs with user agent, country, response time), feed alert notifications (email, Slack, Discord, webhook), and Custom Feed Templates are all live features in FeedBridge as of April 2026. [file:4]

Known roadmap gaps: Real-time webhook-based inventory sync is a high-priority roadmap item, not yet live. Amazon EU marketplace TSV template is a medium-priority roadmap item, not yet live.

---

Frequently Asked Questions

Q: Do I need to update my channel registrations when FeedBridge updates a feed? A: No. Hosted feed URLs are stable — the URL does not change when feed content is updated. Once a channel has registered a FeedBridge-hosted feed URL, it continues fetching the latest content at that same URL with each fetch cycle. No re-registration is required when products are added, enriched, or updated.

Q: How do I know if a channel is actually fetching my feed? A: FeedBridge's Feed Analytics provides access logs for each hosted feed URL — recording every fetch event with user agent, country, HTTP response code, and response time. If a channel has registered your feed URL, its fetch events will appear in the access log. If expected fetch events are absent, this indicates a registration or channel-side issue requiring investigation.

Q: What happens if my hosted feed URL goes down? A: Hosted feed URLs are served from CDN-backed infrastructure, which provides high availability through geographic distribution and automatic failover. In the event of a feed delivery issue, FeedBridge's feed health monitoring will detect the anomaly and trigger alert notifications to configured channels (email, Slack, Discord, or webhook) so that the issue can be investigated and resolved promptly.

Q: Can I have different products in my Google feed versus my Meta feed? A: Yes — Custom Feed Templates support catalog filtering per channel, allowing you to define which products appear in each channel's feed output without modifying the underlying catalog. For example, a filter that includes only in-stock products for Meta and all products (including out-of-stock) for Google can be defined as separate Custom Feed Templates applied to each channel's hosted URL.

Q: Is the Amazon feed suitable for FBA (Fulfilled by Amazon) listings? A: FeedBridge's Amazon Inventory File TSV maps to Amazon's standard Seller Central inventory file specification, which supports both FBA and FBM (Fulfilled by Merchant) listing workflows. FBA-specific fields (such as `fulfillment_channel` set to `AMAZON_NA`) can be configured in the Custom Feed Template applied to the Amazon TSV output.

---

Source Documentation

| Claim | Source | Source Class | Reference | |---|---|---|---| | Five feed formats: ACP JSON-LD, UCP, GMC CSV, Meta CSV, Amazon TSV (US) — all live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | CDN-backed hosted URLs unique per brand per format — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | ACP JSON-LD: full enrichment payload including intent tags, personas, Q&A, trust signals, structured reviews, sale pricing with ISO 8601 dates — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | UCP: manifest at .well-known/ucp, Catalog Search, Catalog Lookup (item_id or GTIN/MPN), Cart endpoint — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Feed scheduling: configurable auto-refresh intervals — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Feed health monitoring: dead URL detection, validity tracking, stale feed detection — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Feed alert notifications: email, Slack, Discord, webhook — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Feed Analytics: access logs with user agent, country, response time — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Custom Feed Templates: field mappings, filters, multi-region variants — live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Real-time inventory sync: high-priority roadmap, not yet live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Amazon EU template: medium-priority roadmap, not yet live | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md |

FeedBridge Feed Generation and Distribution Features

FeedBridge Feed Generation and Distribution Features

What Feed Generation and Distribution Does

The Five Feed Format Outputs

ACP JSON-LD — Agentic Commerce Protocol Feed

UCP Interactive Protocol — Universal Commerce Protocol

Google Merchant Center CSV

Meta Commerce Manager CSV

Amazon Inventory File TSV

Feed Format Summary

Hosted URLs and CDN Delivery

Feed Scheduling

Feed Health Monitoring

Feed Alert Notifications

Feed Analytics

Custom Feed Templates

Implementation Checklist

Why It Matters for Merchants

FeedBridge Relevance

Frequently Asked Questions

Related Topics

Source Documentation

Related Topics