Title: CatalogPilot Connector Author: advisionecommerce Published: October 9, 2026 Last modified: October 10, 2026 --- Search plugins ![](https://ps.w.org/catalogpilot-connector/assets/banner-772x250.png?rev=3737105) ![](https://ps.w.org/catalogpilot-connector/assets/icon-256x256.png?rev=3737105) # CatalogPilot Connector By [advisionecommerce](https://profiles.wordpress.org/advisionecommerce/) [Download](https://downloads.wordpress.org/plugin/catalogpilot-connector.0.1.69.zip) * [Details](https://wordpress.org/plugins/catalogpilot-connector/#description) * [Reviews](https://wordpress.org/plugins/catalogpilot-connector/#reviews) * [Installation](https://wordpress.org/plugins/catalogpilot-connector/#installation) * [Development](https://wordpress.org/plugins/catalogpilot-connector/#developers) [Support](https://wordpress.org/support/plugin/catalogpilot-connector/) ## Description #### Turn Your WooCommerce Catalog Into a Competitive Advantage CatalogPilot transforms ordinary WooCommerce product catalogs into intelligent, structured information designed for AI discovery, modern search and greater online visibility. Retailers using CatalogPilot are already reporting improvements in product discovery and sales. **Experience it on your own products before spending anything.** **30 days free. No credit card. No commitment.** **We’ll enrich up to 50% of your qualifying catalog at no cost.** Like what you see? Subscribe and we’ll enrich the remaining qualifying catalog at no additional enrichment charge. CatalogPilot then automatically maintains your catalog at 100% enrichment as products change or are added, with ongoing enrichment billed at transparent pay-as-you-go rates. **Your original WooCommerce catalog remains untouched.** 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: * Authenticated, paginated catalog synchronization. * Product, variation, category, and image overlay storage in WordPress. * Storefront presentation of approved CatalogPilot content. * Multilingual product and category identity support. * Connection verification from the WordPress administration area. ### External services This plugin connects to the CatalogPilot software-as-a-service platform at [catalog-pilot.com](https://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](https://support.advision-ecommerce.com/i260-terms-conditions) CatalogPilot privacy policy: [Privacy Policy](https://support.advision-ecommerce.com/i259-privacy-policy) ### Support For help connecting CatalogPilot, synchronizing a WooCommerce catalog, or delivering approved CatalogPilot content, email [woo-support@catalog-pilot.com](https://wordpress.org/plugins/catalogpilot-connector/woo-support@catalog-pilot.com?output_format=md). 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. ## Installation 1. Install and activate WooCommerce. 2. If replacing another CatalogPilot distribution, deactivate and delete that package first. Do not install multiple distributions together. Existing connection settings and synchronized catalog tables are retained; private-updater credentials are not retained by the public distribution. 3. Install and activate CatalogPilot Connector. 4. Open **WooCommerce > CatalogPilot** in WordPress administration. 5. Follow the setup link to connect the store to a CatalogPilot account. 6. Create a dedicated WordPress application password for the CatalogPilot synchronization user when prompted. 7. Complete connection verification in CatalogPilot, then use **Verify Connection with CatalogPilot Account** in WordPress. ## FAQ ### Does this plugin require a CatalogPilot account? Yes. The plugin is a connector for the hosted CatalogPilot service and requires a configured CatalogPilot site. ### Does it require WooCommerce? Yes. WooCommerce must be installed and active. ### Where are diagnostic logs stored? Diagnostics are disabled by default. A store manager can enable privacy-safe CatalogPilot diagnostics under **WooCommerce > CatalogPilot**. Messages are written through WooCommerce logging with source `catalogpilot`, omit credentials, customer data, catalog content, URLs, site identifiers, IP addresses, and object identifiers, and follow the store’s WooCommerce log-retention settings. ### Can I install multiple CatalogPilot distributions together? No. The private package and the public `catalogpilot-connector` package are alternative distributions of the same connector and must not be installed together. Deactivate and delete the installed distribution before uploading the replacement. Connection settings and synchronized catalog tables are retained. The public distribution clears private-updater credentials, so after switching back to the private distribution, run CatalogPilot Verify Install to provision private updates again. ### What happens to connector data when I delete the plugin? Deactivation and plugin deletion do not contact external services or automatically remove settings and synchronized catalog tables. This prevents data loss during updates or distribution replacement. To remove the connection permanently, disconnect the site through your CatalogPilot account, then select **Permanently remove local CatalogPilot data** under **WooCommerce > CatalogPilot**. This removes only CatalogPilot- owned data and does not alter your WooCommerce catalog. ### How do I disconnect safely? First deactivate sync, then use **Disconnect** in your CatalogPilot account. That server-side action fences queued work, clears the WordPress connector identity, and revokes the dedicated WordPress application password. The separate **Disconnect this WordPress site** action under **WooCommerce > CatalogPilot** clears only the local WordPress connector state and does not revoke credentials retained by your CatalogPilot account. If WordPress is unreachable, CatalogPilot records a revocation failure, blocks normal connector/updater use, and keeps the credential only so an administrator can retry. Deactivating or deleting the WordPress plugin alone never performs a remote disconnect. ### What WordPress permissions does synchronization require? Use a dedicated WordPress user with an application password. The user must have the `manage_woocommerce` or `manage_options` capability. ### Does the plugin load JavaScript from a third-party server? The plugin code and storefront runtime are packaged with the plugin and enqueued locally; no plugin JavaScript is downloaded from CatalogPilot. Approved rich descriptions can contain third-party media or allow-listed iframe embeds. An embedded page may execute its provider’s JavaScript inside that iframe, as described in the External services section. The unminified sources corresponding to the packaged storefront runtime are included in `assets/src/`. ### How are the packaged JavaScript files built? The files in `assets/js/` are minified from the corresponding files in `assets/src/` with the GPL-compatible esbuild 0.25.9 build tool. With Node.js installed, run these commands from the plugin directory to reproduce them: ``` npx --yes esbuild@0.25.9 --loader=js --minify --charset=utf8 --legal-comments=none --target=es2018 < assets/src/storefront-runtime-core.js > assets/js/storefront-runtime-core.js npx --yes esbuild@0.25.9 --loader=js --minify --charset=utf8 --legal-comments=none --target=es2018 < assets/src/woo-embed-runtime.js > assets/js/woo-embed-runtime.js ``` ## Reviews There are no reviews for this plugin. ## Contributors & Developers “CatalogPilot Connector” is open source software. The following people have contributed to this plugin. Contributors * [ advisionecommerce ](https://profiles.wordpress.org/advisionecommerce/) [Translate “CatalogPilot Connector” into your language.](https://translate.wordpress.org/projects/wp-plugins/catalogpilot-connector) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/catalogpilot-connector/), check out the [SVN repository](https://plugins.svn.wordpress.org/catalogpilot-connector/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/catalogpilot-connector/) by [RSS](https://plugins.trac.wordpress.org/log/catalogpilot-connector/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.1.69 * Handle empty storefront microdata fields without interrupting structured-data processing. #### 0.1.68 * Mark category JSON-LD with CatalogPilot `sdPublisher` provenance, including schema owned by an SEO provider, so delivery monitoring can identify CP-managed output. #### 0.1.67 * Escape approved storefront titles and category labels in rendered HTML while preserving Woo Product Filter block context data. #### 0.1.66 * Match WordPress scaled and thumbnail image URLs to their original image identity while retaining compatibility with existing catalog image rows. #### 0.1.65 * Set the author URI to AdVision eCommerce, distinct from the CatalogPilot plugin URI. * Update the tested WooCommerce version to 11.1.1 after local compatibility checks. #### 0.1.64 * Keep H1-only and Title-only storefront configurations from falling back to a disabled sibling heading field when the selected field has no approved value. #### 0.1.63 * Fetch the local storefront payload for H1-only classic WooCommerce first loads so the enriched H1 value is available after compact bootstrap. #### 0.1.62 * Honor an H1-only storefront configuration on classic WooCommerce product headings while preserving Title precedence when both fields are enabled. #### 0.1.61 * Harden synchronized runtime configuration to accept data-only JSON and escape inline values. * Disable storefront payload diagnostics in production packages. * Separate WordPress.org update handling from the private updater and clear private updater state in the public build. * Require encrypted CatalogPilot service connections outside recognized local-development hosts. * Initialize each site’s catalog table schema on first run and when the connector version changes, retry failed migrations, and report unavailable storage without accepting catalog publishes. * Retry connector-version and updater-health settings after partial upgrade failures without rerunning completed schema work. * Keep partially written catalog chunks retryable when a catalog row or completed- batch marker cannot be saved. * Return a retryable error when connector or embed settings cannot be verified after saving. * Reject oversized local runtime-media requests before catalog resolution or image candidate filtering. * Confirm compatibility through WordPress 7.1 while retaining the WordPress 6.5 minimum. * Declare WooCommerce 9.2 through 11.0 compatibility in every distribution header. * Move CatalogPilot administration under WooCommerce and use the WooCommerce management capability. * Replace direct PHP error logging with optional privacy-safe WooCommerce diagnostics. * Lower the connector runtime floor to PHP 7.4. * Declare compatibility with WooCommerce High-Performance Order Storage; the connector does not read or write order storage or overwrite native WooCommerce catalog fields. * Add authenticated disconnect, application-password revocation fencing, and an explicit typed-confirmation local data purge. #### 0.1.60 * Initial WordPress.org release candidate. * Package the storefront runtime locally and enqueue it with WordPress APIs. * Add separate private and WordPress.org distribution builds. ## Meta * Version **0.1.69** * Last updated **3 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1.3** * PHP version ** 7.4 or higher ** * Tags * [catalog](https://wordpress.org/plugins/tags/catalog/)[multilingual](https://wordpress.org/plugins/tags/multilingual/) [product data](https://wordpress.org/plugins/tags/product-data/)[seo](https://wordpress.org/plugins/tags/seo/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/catalogpilot-connector/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/catalogpilot-connector/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/catalogpilot-connector/reviews/) ## Contributors * [ advisionecommerce ](https://profiles.wordpress.org/advisionecommerce/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/catalogpilot-connector/)