Integrate Third Party CRM with WooCommerce
what it takes to integrate third party CRM with WooCommerce
A mapped, two-way, queue-backed sync between your store and HubSpot, Zoho, Salesforce, Pipedrive or ActiveCampaign, plus the monitoring to prove it is working.
get a quoteField and object mapping
Customers to contacts, orders to deals, products to line items, and custom fields in both directions. We document the mapping so sales, marketing and support agree on what each field means.
Queue-backed, two-way sync
Every WooCommerce event is queued through Action Scheduler and pushed with retries and idempotency keys. CRM changes come back through webhooks so lifecycle stage and owner stay current in the store.
Monitoring and reconciliation
A sync log in wp-admin, alerts when the queue backs up, and a WP-CLI reconcile command that compares both systems and repairs drift without touching records that already match.
how a WooCommerce CRM integration is built properly
why the off-the-shelf connectors disappoint
Most stores start with the vendor plugin: HubSpot for WooCommerce, Zoho CRM for WooCommerce, or a Zapier or Make scenario. They work for a simple contact sync. They fall over when you need order line items as deal products, a lifecycle stage driven by purchase history, custom fields that exist only in your store, or a sync that survives an API outage without losing events. The vendor plugins also tend to run synchronously inside the checkout request, so a slow CRM API slows your checkout. When you integrate third party CRM with WooCommerce for a store doing real volume, the design has to assume the CRM will sometimes be unavailable and the store must never notice.
Signs that the current integration is costing you:
- Sales calling customers who already bought, because the deal stage never updated.
- Duplicate contacts created every time a guest checks out with a different capitalisation of the same email.
- Marketing automations firing on stale data because the sync runs on a nightly CSV export.
- Checkout taking two extra seconds while the CRM API is called inline.
- Nobody can say how many orders failed to sync last month.
the architecture we use
We build a dedicated plugin with three layers. An event layer listens to WooCommerce hooks: woocommerce_new_order, woocommerce_order_status_changed, woocommerce_created_customer, woocommerce_customer_save_address and, for subscriptions, woocommerce_subscription_status_updated. Each event writes a job to Action Scheduler rather than calling the CRM directly, so the checkout request finishes in milliseconds regardless of what the CRM is doing. A transport layer wraps the CRM API (HubSpot v3 CRM objects, Zoho CRM v6 REST, Salesforce REST with the OAuth 2.0 JWT bearer flow, Pipedrive v1) with token refresh, rate-limit handling and retries with exponential backoff. A mapping layer is plain PHP configuration that maps store fields to CRM properties and is versioned in Git, so a change to the mapping is a code review, not a mystery.
Inbound changes arrive through CRM webhooks to a custom REST route registered with register_rest_route(), validated with the vendor’s signature scheme, and applied through the WooCommerce CRUD classes to user meta, order meta and wp_wc_customer_lookup. We keep a swd_crm_sync_log table with the event, payload hash, CRM record ID and status, which is what the reconcile command and the admin screen read from.
subscriptions, deals and revenue
For subscription stores, the CRM needs the recurring picture: a deal per subscription with MRR, renewal date and status, and lifecycle changes when a renewal fails. We map shop_subscription objects to deals or custom objects and push renewal orders as revenue events rather than new deals, which keeps pipeline reporting honest. If the subscription logic itself needs work, see our custom WooCommerce subscription workflow service; the two builds are often scoped together.
data hygiene and deduplication
Before the first full sync we run a hygiene pass: normalise emails to lower case, match guest orders to registered customers by email, and decide the rules for which system wins when both have edited the same field. HubSpot deduplicates on email natively; Zoho and Salesforce need explicit duplicate rules, which we configure. The initial backfill runs in batches through WP-CLI (wp swd-crm backfill --since=2023-01-01 --batch=200) so it stays within API rate limits and can be resumed after an interruption.
keeping checkout fast
Because nothing calls the CRM inline, the integration adds no measurable time to checkout. We verify this with Query Monitor and a before-and-after Lighthouse run. If your checkout is already slow for other reasons, our WooCommerce checkout speed fix addresses that separately. After launch, the sync log and queue depth are added to the monitoring we run under website maintenance and support, so a stalled queue is caught before your sales team notices.
timeline and pricing
A one-way contact and order sync to a single CRM is typically two weeks. Two-way sync with custom objects, subscriptions and a historical backfill runs three to five weeks. You get a fixed scope and fixed price in writing before we start, and an answer on cost within 24 hours of a first conversation. The full design reasoning is in How to Integrate a Third Party CRM with WooCommerce (HubSpot, Zoho, Salesforce). To integrate third party CRM with WooCommerce on your store, tell us which CRM you use and what data must flow.