CatalogPilot Connector links a WooCommerce store to the CatalogPilot service. It provides authenticated REST API endpoints that CatalogPilot uses to synchronize products, variations, categories, and approved catalog content.
When storefront delivery is enabled, the plugin can apply approved CatalogPilot titles, descriptions, metadata, structured data, and image attributes to supported WooCommerce pages. The storefront runtime is included in the plugin package and loaded through the WordPress script API.
A CatalogPilot account and a configured CatalogPilot site are required. WooCommerce must be installed and active.
Features include:
This plugin connects to the CatalogPilot software-as-a-service platform at catalog-pilot.com. The connection is necessary to synchronize catalog records, receive approved content, verify the configured site, and report storefront delivery activity.
CatalogPilot provisions the site identifier and HTTPS service URL after the WordPress administrator authorizes the connection. Plain HTTP service URLs are accepted only when WordPress reports a local or development environment and the URL uses a recognized local-development host. When the administrator verifies the connection, the plugin sends the site identifier, storefront URL, and connector version to the configured CatalogPilot service.
When CatalogPilot makes an authenticated catalog synchronization request, the plugin returns WooCommerce product, variation, and category records to CatalogPilot. Depending on the record type, these records include WordPress/WooCommerce object identifiers; names, descriptions, slugs, status, and storefront URLs; SKU, price, stock status, variation attributes, and category relationships; image identifiers and URLs; language and translation relationships; and creation, modification, or deletion timestamps. These records are sent only in response to a request authenticated with a WordPress application password and matching CatalogPilot site identifier. Customer, order, payment, and WordPress password data are not included.
When storefront delivery is enabled, the plugin may send the current page URL, language, page type, WooCommerce product/category/variation identifiers, image URLs and image text attributes, applied field names, and delivery context identifiers to CatalogPilot. This data is used to return the correct approved catalog content, resolve newly encountered catalog images, and measure whether approved content was delivered. Requests occur directly from the visitor’s browser while visitors view supported storefront pages, so CatalogPilot may also receive standard browser request information such as the visitor’s IP address, user agent, and referring URL, subject to the browser and storefront referrer policy. The plugin does not send WooCommerce customer passwords or payment details.
Approved rich descriptions may contain HTTPS images, video sources, or iframe embeds hosted by third parties. Iframe URLs are rendered only when their host and path match the allow rules configured for the CatalogPilot site. When this approved media appears on a storefront page, the visitor’s browser connects directly to the media provider. The provider may receive standard browser request information such as the visitor’s IP address, user agent, and referring URL, subject to the browser and storefront referrer policy. Which providers are contacted depends on the store’s approved catalog content; each provider’s own terms and privacy policy apply.
CatalogPilot terms: Terms and Conditions
CatalogPilot privacy policy: Privacy Policy
For help connecting CatalogPilot, synchronizing a WooCommerce catalog, or delivering approved CatalogPilot content, email woo-support@catalog-pilot.com. Include the WordPress, WooCommerce, PHP, and CatalogPilot Connector versions when reporting a problem.
CatalogPilot support covers this connector and its CatalogPilot service integration. General WordPress, WooCommerce, hosting, theme, and unrelated third-party plugin support remains with those respective providers.