Connect WooCommerce
Pair a WooCommerce Store with the Quick2Print Connector
Quick2Print publishes products through the official WooCommerce Connector. Pairing lets the Store claim and execute approved jobs locally without exposing WordPress passwords or relying on inbound WooCommerce REST access.
Required Access
Install the private connector ZIP and open WooCommerce → Quick2Print → Connect to Quick2Print. The signed-in user chooses an authorised Account, Brand and Store. The saved Store URL must exactly match the normalized HTTPS WordPress URL.
Quick2Print lets Team Members view connector status. Account Owners and authorised Administrators can pair, rotate or disconnect an installation.
Connected-Store Scope
Quick2Print pairs one WordPress/WooCommerce installation to one Store in v1. The installation reports its Account, Brand and Store identity on the local Quick2Print admin page.
After Connecting
After pairing, Quick2Print automatically runs the same end-to-end wake used by Test connector. A successful matching heartbeat marks the connector instant; one-minute Action Scheduler polling remains active if both signed inbound routes are temporarily blocked. Most Stores need no hosting changes. If a firewall, CDN or edge network rejects both instant routes, Quick2Print shows the exact allowlist details and links to the hosting and firewall guide.
If the test needs attention, follow the message shown beside the connection. The most common fixes are:
- confirm public HTTPS, outbound HTTPS, WordPress, WooCommerce, PHP OpenSSL and Action Scheduler meet the requirements shown by the plugin;
- confirm the Store URL and WordPress home URL normalize to the same public HTTPS address;
- inspect the sanitized recent-job error and use its recovery action;
- reconnect if the installation was revoked or its encrypted local secret can no longer be read.
A connected Store allows Quick2Print to create hidden or review drafts, publish live when enabled, and schedule future publication. WooCommerce transport is connector-only and never falls back to customer REST credentials.