Quick2Print Documentation
Quick2Print Documentation
ProductPricingSupportQuick2Print DocsGoverned AI and commerce contentBilling And WorkspaceConnect PrintfulConnect WooCommerceUpload DesignsMockup GenerationPrintful SyncProduction Release ChecklistProducts And CampaignsWorkspace Roles And Brand AccessImport TemplatesTroubleshooting SyncWooCommerce ConnectorFix a Blocked WooCommerce ConnectionWooCommerce PublishingAccounts, Brands And Connected Stores

WooCommerce Connector

Install and pair the official Quick2Print Connector for WooCommerce

The official Quick2Print Connector for WooCommerce runs approved WooCommerce work inside WordPress. It uses automatically selected signed wake transports and durable local polling while keeping Quick2Print authoritative for product intent, approval, scheduling and Printful processing.

Install and pair

  1. In Brand Settings → Store Connection, download the current private Quick2Print Connector release, then upload that ZIP in WordPress under Plugins → Add Plugin.
  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 connector, 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 a heartbeat is stale or connector work is due. Connector 0.3.1 immediately retries through WordPress's public /wp-admin/admin-ajax.php route if REST is rejected or unreachable. The wake contains no product data or secret. After authentication, the connector sends the matching wake heartbeat and executes at most one claimed job inside the bounded request. Product work is still retrieved over outbound signed HTTPS.

Action Scheduler remains the durable one-minute fallback and missing recurring actions are recreated without deleting pending or running work. Quick2Print marks a wake as confirmed only after receiving an authenticated heartbeat with the exact pending wake ID; an HTTP 200, routine poll, or redirected security page is not sufficient. Connection health is reported as instant, polling, offline, or unsupported with separate sanitized upstream and connector-authentication failures.

Quick2Print gateway traffic also carries a short-lived Ed25519 service signature with public keys, traffic purpose, outbound ranges, and abuse contact published under the stable gateway hostname. The per-Store HMAC remains required: service identity tells a host who sent the request, while the Store secret authorizes it.

Supported v1 work includes catalogue snapshots and mutations, simple and variable product upserts, copy and SEO updates, 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, last instant wake, scheduler, queue, versions, recent sanitized jobs and retry guidance. Brand Settings shows the last heartbeat, wake attempt, confirmed wake, wake error, and plugin poll/job error separately. When a hosting firewall, CDN or edge network blocks instant wake, both surfaces link to the step-by-step unblocking guide. Connector publication events confirm when WooCommerce changes a scheduled product to live, allowing Quick2Print to complete the release set safely. Disconnect revokes the installation and deletes the local connector secret; it never deletes WooCommerce products.

WooCommerce transport is fail-closed and connector-only. Disconnecting marks the Store as connector_required; it cannot silently switch to direct REST. Rollback uses the previous application image and the previous protected connector release, not customer consumer keys.

Troubleshooting Sync

Diagnose WooCommerce and Printful production workflow issues

Fix a Blocked WooCommerce Connection

Unblock Quick2Print in your hosting firewall, CDN, or security plugin

On this page

Install and pairHow jobs runPrintfulRecovery and rollback