AutoSyncPress CRMBridge Sync for Zoho CRM

CRMBridge connects WordPress and WooCommerce to Zoho CRM. Customers become contacts, orders become deals with the right stage and amount, and enquiries become leads — automatically, in the background, and fully logged.

AutoSyncPress and CRMBridge are not affiliated with Zoho Corporation. Zoho and Zoho CRM are trademarks of Zoho Corporation.

WooCommerce is optional. If you run a store, CRMBridge syncs orders and customers. If you don’t, it still captures registrations, enquiries and blog commenters as leads. Most sites that want people in a CRM are not stores, so the plugin does not pretend otherwise.

It does not create duplicate contacts

Duplicates happen when an integration searches Zoho for the customer’s email and creates a contact if it doesn’t find one. Two background jobs can both finish that search before either finishes writing — so both create, and the same person ends up in your CRM twice.

CRMBridge never does this. It uses Zoho’s own upsert with duplicate checking, so the match happens inside Zoho, under Zoho’s lock. One contact comes out, every time — even if the competing writer is a Zoho form, another site, or a person typing.

It tells you what your Zoho API allowance is costing

Zoho CRM does not bill API usage in requests. It bills in credits, against a hard daily ceiling — 5,000 a day on Zoho’s own Free edition of CRM. When you hit it, every call fails for the rest of the day, and from the outside that looks exactly like “the plugin stopped working” with nothing to explain it.

CRMBridge shows you this. The Health screen displays credits used against your ceiling. Background syncing slows down at 80% and pauses at 95%, resuming automatically at midnight UTC — and syncing one order by hand always works, even then.

It is also cheaper by design: matching a customer with an upsert costs a twentieth of what searching and then creating does.

It tells you what will break before you turn it on

Deal stage is a picklist, and Zoho rejects any value that is not in your Deals layout. The moment your team renames a stage — and most teams do — every order fails with a validation error that names the field and not the reason.

The Pre-flight screen checks your configured stages against your real Zoho sales process and names any that do not exist, alongside what your org actually has. It also flags orders with no billing email, and custom fields that are not on your layout.

Everything else

• Deals with the right amount. Order total goes to Amount, which is what every pipeline and forecast report reads. The line-by-line breakdown is attached as a searchable note, which keeps the deal record readable in list views.
• Contacts, Accounts, Deals and Leads. Optional B2B grouping under a company account.
• Custom field mapping. Send your PO number, referral code or delivery date to any custom field you have added to Deals.
• One-click re-sync, from the order screen and the orders list, with the last few sync events shown in place.
• A real log — every sync with its outcome, how long it took, and what Zoho answered.
• Test mode. Log exactly what would be sent, and send nothing, until you are happy.
• Sandbox and developer environments. Point at a Zoho sandbox instead of your live CRM and prove the setup before a real record is touched. Health shows which environment you are on.
• Every Zoho region: India, US, Europe, Australia, Japan, Canada and Saudi Arabia.
• HPOS and block checkout compatible.

What it sends where

• Customer or registered user → Contact, matched on email
• Billing company → Account (optional)
• Order → Deal, staged from the order status
• Order items, coupons and totals → Note on the deal
• Registration, enquiry or comment → Lead

External services

This plugin connects to the Zoho CRM API to create and read your CRM records. That connection is the entire purpose of the plugin, and it is made only to the Zoho organisation you authorise.

• Service: Zoho CRM API v8 — the regional endpoint you select (for example https://www.zohoapis.in/crm/v8) and the matching Zoho accounts domain for authentication.
• When it is used: when you authorise the connection, and thereafter whenever an order, customer, registration or enquiry is synced, and when the Pre-flight and Health screens read your organisation’s settings.
• What is sent: the customer, order and enquiry data required to create the corresponding Zoho CRM records — name, email address, billing address and phone, company name, order line items, totals and currency — together with your OAuth access token.
• Terms of service: https://www.zoho.com/terms.html
• Privacy policy: https://www.zoho.com/privacy.html

That is the only external service. The plugin sends nothing to the author, at any point, under any setting. There is no telemetry, no analytics, no usage tracking and no phone-home.