You open your WooCommerce dashboard expecting to see fresh orders flowing into Salesforce. Instead, nothing. Orders are stuck in WooCommerce. Customers aren’t appearing in your CRM. Products haven’t updated in days.

This is the moment when a WooCommerce-Salesforce integration goes from being a time-saver to a headache. And if you’re paying for a middleware tool like Zapier or a premium plugin, every minute of downtime feels like money wasted.

I’ve been there. As a developer who builds WooCommerce-Salesforce integrations (and runs stores using them), I’ve debugged every flavor of sync failure. From OAuth token expirations to field mapping mismatches, these issues are predictable and fixable.

Here are the 7 most common reasons your WooCommerce store isn’t syncing to Salesforce, and exactly how to fix each one.

1. OAuth Token Expired or Revoked

Salesforce uses OAuth 2.0 for authentication. Unlike basic API keys, OAuth tokens have a finite lifespan. Most Salesforce connected apps issue access tokens that expire after 2 hours to 24 hours. If your plugin doesn’t automatically refresh the token, the sync silently stops working.

How to diagnose: Check your plugin’s connection status page. If it shows “Disconnected” or “Token Expired,” that’s your culprit. In NexaForce, go to Settings → Salesforce Connection and look for the connection status indicator.

The fix: Re-authorize the connection. In NexaForce, click “Reconnect to Salesforce” and complete the OAuth flow again. If you’re using a custom integration, check that your refresh token logic is working. Some plugins require you to manually re-authenticate every 30 to 90 days depending on your Salesforce security settings.

To prevent this from happening again, ensure your plugin supports automatic token refresh. NexaForce handles this natively, but if you’re using a custom solution or a basic plugin, you may need to implement a cron job that refreshes the token before it expires.

2. Field Mapping Mismatch After WooCommerce or Salesforce Update

WooCommerce updates can change how order metadata is stored. Salesforce updates can rename or deprecate standard fields. When either happens, your field mappings break, and data stops flowing.

This is especially common after WooCommerce High-Performance Order Storage (HPOS) migration. HPOS changes how order data is queried, and some older plugins don’t account for this.

How to diagnose: Look at your plugin’s sync log. If you see errors like “Field XYZ not found on object” or “Invalid field,” you have a mapping issue. In NexaForce, check the Feed Builder for any red indicators next to mapped fields.

The fix: Review your field mappings. In NexaForce, open each feed (Orders, Customers, Products) and verify that every mapped field still exists in both WooCommerce and Salesforce. Remove any fields that no longer exist. Test with a single record before bulk syncing.

If you recently enabled HPOS, make sure your integration plugin is HPOS-compatible. NexaForce is fully tested with WooCommerce HPOS. If your current plugin isn’t, consider switching to one that is. You can check this in WooCommerce → Settings → Advanced → Features.

3. Webhook or API Rate Limiting

Salesforce enforces API request limits based on your edition. Developer orgs get 15,000 API calls per 24 hours. Enterprise editions get significantly more, but if you’re doing bulk syncs or have high order volume, you can hit these limits.

When you exceed the limit, Salesforce returns HTTP 429 (Too Many Requests) or 403 (Request Limit Exceeded). Your plugin may stop syncing temporarily or queue failed records.

How to diagnose: Check your Salesforce org’s API usage. Go to Setup → Company Settings → Company Information → API Requests, Last 24 Hours. If you’re above 80% of your limit, that’s likely your problem.

The fix: Reduce sync frequency. Instead of real-time sync on every order, batch sync every 15 minutes. NexaForce supports configurable sync intervals. If you’re using a middleware tool like Zapier, consider upgrading to a higher-tier plan with more tasks.

For stores doing over 500 orders per day, consider using NexaForce’s bulk sync feature which batches API calls more efficiently than per-order webhooks.

4. Incorrect Salesforce Object or Field Permissions

Your connected app or integration user needs specific permissions in Salesforce to create, read, update, and delete records. If permissions are too restrictive, the sync fails silently.

This often happens after a Salesforce security audit or when a new admin tightens permissions without realizing the integration depends on them.

How to diagnose: In NexaForce, enable debug logging and attempt a manual sync. Look for errors like “INSUFFICIENT_ACCESS_OR_READONLY” or “FIELD_INTEGRITY_EXCEPTION.” These indicate permission problems.

The fix: Ensure your integration user has at minimum these permissions:

• Read, Create, Edit on Lead, Contact, Account, Opportunity, Product2, PricebookEntry, Order, OrderItem
• API Enabled permission on the user profile
• Access to the connected app (if using OAuth)

If you’re using a dedicated integration user (recommended), log in as that user in Salesforce and verify they can manually create a test Lead. If they can’t, adjust the profile permissions.

5. Duplicate Rules Blocking Record Creation

Salesforce duplicate rules and matching rules can prevent new records from being created if they match existing records. This is great for data quality but terrible for sync if your rules are too strict.

How to diagnose: Check your sync error log. If you see “DUPLICATES_DETECTED” or “DUPLICATE_VALUE” errors, duplicate rules are blocking the sync. In NexaForce, these errors appear in the Sync Log with the specific record details.

The fix: Review your Salesforce duplicate rules. Go to Setup → Duplicate Rules. Consider creating an exception for your integration user or adjusting the matching criteria. For example, if your rule matches on email address, but your WooCommerce customers sometimes have different email formats, the sync may fail.

Alternatively, configure your integration to update existing records instead of creating duplicates. NexaForce supports account matching, so it can update an existing Salesforce contact when a WooCommerce customer with the same email re-orders.

6. WooCommerce HPOS Compatibility Issues

WooCommerce High-Performance Order Storage (HPOS) was introduced in WooCommerce 8.0 and became the default in 9.0. It changes how order data is stored and queried. If your Salesforce integration plugin was built before HPOS, it may be querying the old postmeta tables, which are no longer populated by default.

How to diagnose: Check if you’re using HPOS: WooCommerce → Settings → Advanced → Features. If “High-Performance Order Storage” is enabled, your integration must support it. In NexaForce, go to the System Status page and look for “HPOS Compatible: Yes”.

The fix: If your current plugin doesn’t support HPOS, you have two options. First, disable HPOS in WooCommerce (not recommended long-term, as HPOS significantly improves performance). Second, switch to an HPOS-compatible integration plugin like NexaForce, which was built from the ground up with HPOS support.

If you’re developing a custom integration, use wc_get_orders() and the orders table directly instead of get_post_meta() calls on order IDs.

7. SSL Certificate or Server Firewall Blocking API Calls

Salesforce requires TLS 1.2 or higher for all API connections. If your server is using an outdated SSL/TLS configuration, the connection will fail. Similarly, some shared hosting environments block outbound API calls to certain IP ranges.

How to diagnose: Test the connection manually. In NexaForce, use the Connection Test button. If it fails with an SSL-related error, your server’s TLS configuration is the problem. You can also check your server’s PHP error log for cURL errors like “SSL connection timeout” or “certificate verify failed.”

The fix: Contact your hosting provider and ask them to enable TLS 1.2 support and allow outbound connections to Salesforce API endpoints (*.salesforce.com and *.force.com). If you manage your own server, ensure OpenSSL is up to date and PHP is compiled with cURL support.

For a quick test, create a simple PHP script that calls the Salesforce REST API using wp_remote_get(). If it fails, your server environment is blocking the connection.

Preventing Future Sync Failures

Once your sync is working again, take these steps to prevent future issues:

• Monitor API usage weekly. Set up a Salesforce report that tracks API calls by integration user. Get alerted when you hit 70% of your daily limit.
• Test after every update. After updating WooCommerce, Salesforce, or your integration plugin, manually sync a test order before relying on the integration.
• Keep a sync log. Enable detailed logging in your integration plugin. NexaForce stores 30 days of sync history. Review it weekly for any warning-level errors that haven’t escalated yet.
• Use a staging environment. Test major updates (WooCommerce major versions, Salesforce releases) on a staging site before applying them to production.

When to Consider a More Reliable Integration

If you’re experiencing sync failures weekly despite following these fixes, your integration tool may be the weak link. Many WooCommerce-Salesforce plugins were built years ago and haven’t kept up with WooCommerce’s rapid evolution.

NexaForce was built specifically for modern WooCommerce stores. It supports HPOS natively, handles OAuth token refresh automatically, and includes a visual feed builder that makes field mapping straightforward. At $159/year, it replaces middleware tools that cost $20-$100 per month, and it keeps your data on your own server.

Whether you use NexaForce or another tool, the key is choosing an integration that’s actively maintained and tested against the latest WooCommerce and Salesforce versions.

Get Your WooCommerce-Salesforce Sync Working Again

Start with the OAuth token check—it’s the most common cause. Then work through the list: field mappings, API limits, permissions, duplicate rules, HPOS compatibility, and server configuration. One of these seven fixes will almost certainly resolve your issue.

If you’re tired of fighting with sync failures and want an integration that just works, try NexaForce. The free version handles basic sync, and Pro unlocks conditional filtering, bulk sync, and priority support. Your data should work for you, not against you.