Skip to Content
DestinationsProduct FeedsOverview

Product Feed Pilots

Understand the current availability and operating model for Vendo product catalog feeds.

Last reviewed September 15, 2026

Limited pilot: Product feed delivery is not a generally available, self-service destination. Contact your Vendo team before you plan a catalog launch around it.

Product feed destinations map the unified product catalog of Vendo to the fields that an advertising or commerce catalog expects. The intended result is one destination item for each purchasable variant.

Availability

TargetCurrent state
Meta CatalogPilot implementation. Requires Vendo-assisted validation against your catalog.
TikTok CatalogPilot implementation. Requires Vendo-assisted validation against your catalog.
Google Merchant CenterComing soon in the app. Not available for production setup.
Amazon MarketplaceNot available. The delivery client is not implemented.

Do not treat a connected advertising account as proof that product feed delivery is enabled. Conversion, audience, reporting, and catalog capabilities are separate modes.

How a Pilot Works

Vendo reads the unified product catalog of the workspace and applies a field mapping for the destination. Then Vendo tries to publish the full catalog. Each scheduled run publishes the current catalog again. It does not send only the changes.

The mapping can copy a canonical product field or supply a fixed value. Vendo skips records that have no usable mapped fields. When the destination returns enough item-level detail, Vendo captures platform errors for investigation.

Pilot Requirements

Before Vendo enables a pilot, agree on:

  • The source that owns product, variant, price, availability, and image data
  • The destination catalog and credentials to use
  • The stable identifier for each variant
  • Required destination fields and any fixed defaults
  • A non-production validation catalog or another safe test scope
  • Launch ownership, rollback, and error-review procedures

Validate Before Launch

  1. Compare a sample of Vendo products with the source catalog.
  2. Review the complete field mapping with the catalog owner.
  3. Publish to the agreed test scope.
  4. Inspect accepted, rejected, and skipped items in both Vendo and the destination.
  5. Verify variant grouping, prices, currency, links, images, availability, and identifiers.
  6. Approve the production catalog only after the destination results match the source of truth.

Support

If your agreement includes a product feed pilot, contact your Vendo representative. Give the workspace, destination, catalog identifier, and intended launch date. Otherwise, use this page as a capability preview, not as setup instructions.

  • Meta Ads: Reporting, conversions, and audience capabilities
  • TikTok Ads: Reporting, conversions, and audience capabilities
  • Shopify: A common source for the unified product catalog
Need help?

When you contact support, give your workspace, the source or destination name, the job ID and the first error message.

support@vendodata.com
Last updated on