WooCommerce Connector

The official Quick2Print Connector for WooCommerce runs approved WooCommerce work inside WordPress. It avoids hosting firewalls blocking inbound REST-key traffic while keeping Quick2Print authoritative for product intent, approval, scheduling and Printful processing.

Install and pair

1. Install the private quick2print-connector-0.1.0.zip release in WordPress.
2. Activate it, then open WooCommerce → Quick2Print.
3. Select Connect to Quick2Print and sign in to the beta application.
4. Choose the Account, Brand and Store whose saved HTTPS URL exactly matches this WordPress installation.
5. Return to WordPress and run Test connection, then Sync now.

The browser exchange uses a short-lived, single-use code with PKCE and state validation. WordPress stores the resulting installation secret encrypted with WordPress salts and AES-256-GCM. No WooCommerce consumer key is sent to the connector.

How jobs run

Quick2Print signs a small request to /wp-json/quick2print/v1/wake when possible. The wake contains no product data or secrets; it only asks Action Scheduler to run. The plugin then claims the full job over an outbound signed HTTPS request. A one-minute outbound polling schedule is the guaranteed fallback when inbound wake requests are blocked.

Supported v1 work includes catalogue snapshots, simple and variable product upserts, selected variation synchronization, categories, tags, brands, attributes, pricing, stock, tax, dimensions, images, related products, visibility and publish state, and reconciliation snapshots.

Printful

Keep the official Printful Integration for WooCommerce plugin active and connected to the matching Printful Store. Quick2Print detects its non-secret status but does not copy or replace Printful code. After WooCommerce product completion, the existing Quick2Print Printful discovery, variant and mockup workflow continues.

Recovery and rollback

The Quick2Print admin page shows heartbeat, scheduler, queue, versions, recent sanitized jobs and retry guidance. Disconnect revokes the installation and deletes the local connector secret; it never deletes WooCommerce products.

During beta, encrypted direct REST credentials are retained but unused while Store transport is connector. An operator can switch the Store back to direct transport for rollback.