Description
Bring your WooCommerce order details into HubSpot so your team can see the customer, order value and purchased products together.
SyncBridge sends WooCommerce orders to HubSpot as deals, customers as contacts, and purchased products as products and line items. Set up the connection inside WooCommerce, map your fields and order statuses, then use the sync log to investigate failed operations.
The free plugin synchronizes from WooCommerce to HubSpot. Optional Pro features are listed separately below. SyncBridge is an independent integration and is not affiliated with or endorsed by HubSpot or WooCommerce.
Included in the free version
- WooCommerce to HubSpot synchronization of orders, contacts and products.
- Contact lookup by normalized email before creating a contact.
- Map standard contact and deal fields, plus supported marketing-attribution values, to HubSpot properties.
- Choose a HubSpot deal pipeline and map WooCommerce order statuses to its stages.
- Sync logs, CSV log export and manual retry.
- Bounded retries for eligible temporary synchronization failures.
- WooCommerce HPOS compatibility.
- Local diagnostic checks for matching, conflict handling and loop protection.
- Overview with the recorded last successful order sync, pending/running order jobs and overdue-job warnings.
- Guided first sync: verify the connection, review mappings, inspect an order or explicitly create a synthetic test.
- Order-level results with confirmed CRM IDs and conservative retry controls.
- Local history preview and background import of up to 100 unique orders, with pause and resume.
- Portal-scoped CRM mappings and unique order keys for safe deal-create recovery.
Pro version
The separately distributed Pro version adds:
- Bring HubSpot deal-stage changes back to WooCommerce order statuses.
- Map custom order metadata and supported custom fields.
- Choose how conflicting updates are handled with data-priority settings.
- Synchronize company records for B2B workflows.
- Optionally send known customers’ abandoned carts to HubSpot and continue the same deal after checkout.
- Unlimited historical-order imports with date and order-status filters.
- Read-only comparison of mapped deal amounts, pipelines and stages; differences are reported without repair.
Pro implementations are not included in the WordPress.org package. Read about Pro at https://sync-bridge.tech/. The free plugin does not require a Pro license.
External services
HubSpot
After the administrator connects the store through OAuth, the plugin sends order, contact, product and optionally company data to api.hubapi.com to read/update the store’s HubSpot records. This is the core integration.
Terms: https://legal.hubspot.com/terms-of-service
Privacy: https://legal.hubspot.com/privacy-policy
SyncBridge connection service
connect.sync-bridge.tech handles OAuth connection and token renewal. It receives the temporary authorization code, refresh token and store return URL. The confidential HubSpot client secret stays on that server. CRM order/contact/product payloads go directly from the store to HubSpot.
Terms: https://sync-bridge.tech/terms
Privacy: https://sync-bridge.tech/privacy
Freemius
Freemius manages licensing, checkout and updates for optional Pro. Its opt-in is not required for free features. When opted in, it receives basic environment/account information such as site URL, WordPress/PHP versions and checkout email.
Terms: https://freemius.com/terms/
Privacy: https://freemius.com/privacy/
Installation
- Install through WordPress, or upload the plugin folder to wp-content/plugins/.
- Activate WooCommerce, then SyncBridge.
- Open WooCommerce > SyncBridge and connect HubSpot through OAuth.
- Configure field and deal-stage mappings for your pipeline.
- Create a test order. Open Logs to check the outcome, then verify the contact, deal amount, stage and line items in HubSpot.
- If a sync fails, inspect its log entry, correct the connection or mapping issue, and use Retry for an eligible order.
Requires WooCommerce 6.0 or later and access to the requested HubSpot CRM objects. Features using newer checkout hooks need a WooCommerce version providing those hooks. A working background scheduler is required. New storefront orders signal background processing automatically after the request. Scheduled retries and recurring tasks still require cron; local loopback HTTP requests must be allowed.
FAQ
What does safe deal creation require?
Order synchronization works without an additional HubSpot property. For stronger recovery after a lost response, you can manually create a deal property with internal name syncbridge_order_key, type text and unique values enabled. SyncBridge only checks its definition and never creates CRM properties or requests schema-write permissions. Overview and History show whether this optional protection is available and let you check again. Without it, an uncertain creation is held for manual review rather than creating a second deal. Existing linked deals continue to update.
What happens if I switch HubSpot portals?
Local contact, deal, product and company mappings are separated by the verified portal ID. Legacy mappings are copied only to their recorded original connection, while the original rows are retained. Reconnecting to another portal does not transfer its mappings or history jobs. If the original connection can no longer be established, old mappings remain unbound and require review. Keep a database backup before upgrading; replacing plugin files does not undo a schema migration.
Can I import all my historical orders?
Open History and select a creation-date range and order statuses in either edition. Preview separates orders to create, update, skip unchanged or review. It sends nothing to HubSpot. Processing starts only after confirmation, newest orders first, in background batches with pause and resume. Free sends up to 100 unique historical orders across runs; the syncbridge_history_free_limit filter can change this allowance. Only actual sending consumes a place. Skipped unchanged orders and attempts stopped before sending use no allowance. Retrying an admitted order uses the same place. Pro removes the allowance and adds customer, payment and amount filters and read-only comparison. Normal new-order synchronization is unaffected. The preview freezes the upper order ID; later orders require a new preview. Changed or deleted orders are checked again before sending.
Can history recognize deals from another integration?
This release cannot recognize deals created by other integrations such as MWB. Importing those orders may create duplicates. Stop the old integration and check a few orders before starting a larger import.
What happens when I move or copy my site?
SyncBridge remembers the store address. If it changes, CRM writes and background synchronization wait for your choice in Overview. For a move, continue with the same store ID and mappings. For a staging copy, create a new store ID and disconnect HubSpot until you deliberately reconnect. Original mappings stay isolated. Changing only HTTP to HTTPS or a trailing slash does not trigger this check.
Does it replace WooCommerce checkout or send marketing emails?
No. Customers continue using WooCommerce checkout. CRM synchronization does not send marketing or cart-recovery emails.
How are contacts matched?
Standard order synchronization uses saved record mappings and normalized email lookup. Review uncertain results before retrying; the plugin does not promise to resolve every duplicate already present in your CRM.
Why do updates take time?
Sync work runs in the background. Processing depends on your WordPress scheduler, store traffic and HubSpot API availability. Check Logs if an expected update does not appear.
Where can I get help?
Use the Support tab on this plugin’s WordPress.org page. Include the plugin, WordPress and WooCommerce versions, the action you tried and a redacted error message. Remove customer details, access tokens and credentials before posting publicly.
Does the free version synchronize changes back from HubSpot?
No. Reverse synchronization is implemented in the separately distributed Pro version.
Does CRM synchronization subscribe contacts to marketing?
No. Synchronizing a contact does not automatically subscribe that person to marketing or send email.
What does the Overview confirm?
Overview reads local scheduler and attempt evidence. OAuth connection checks its HubSpot portal; use Verify connection to repeat the check when needed. Confirmed contact/deal links appear only when the attempt belongs to the verified current portal. Local evidence is not a live CRM audit. Historical warnings may already be resolved.
Does the setup create orders automatically?
No. You can inspect an existing order. Creating a synthetic test requires an explicit confirmation and a test email. It creates a real pending order with one test item and a total of 1 in the store currency, then queues it for HubSpot. No payment is taken. Repeating the action reuses the setup order for the same user and connection.
What status data is stored?
The plugin records the latest attempt time, result, confirmed CRM IDs and the verified HubSpot portal ID in WooCommerce order metadata. Token refresh and reconnecting to the same verified portal do not reset this evidence. A new OAuth grant must confirm its portal before existing links can be shown. Evidence remains with the order; removing an order removes its evidence. The status center adds no telemetry.
What happens on an error?
Errors are logged. Eligible temporary failures have bounded retries. Permanent errors and uncertain creation outcomes require manual review. Open Inspect / retry from Logs. The new screen permits known temporary failures and corrected missing-email results, blocks unknown or historical outcomes, and checks for a queued job before dispatch. Normal automatic order-change synchronization keeps its existing behavior.
Screenshots





Changelog
1.3.0
- Signal background processing after storefront orders without waiting for an admin visit.
- Ignore checkout drafts and retain follow-up changes while an earlier sync is running.
- Allow manual retry after a definitive rejected deal creation; retain protection for uncertain outcomes.
- Detect site moves from the stored home address without language/domain URL filters.
- Keep deal synchronization working without the optional unique order-key property; never write CRM schemas.
- Add shared date/status history filters, newest-first batches and unchanged-order skips.
- Pause CRM writes when a site copy or move is detected until the owner chooses how to continue.
- Recover contact email conflicts and reduce object-cache invalidations in request limiting.
- Scope CRM mappings to the verified HubSpot portal and preserve legacy mapping evidence during migration.
- Serialize order execution and attach unique store/order keys to deals. Recover uncertain creation by lookup before writing.
- Add preview-first history import: 100 unique orders in Free, unlimited in Pro, with progress, pause and resume.
- Add Pro date/status filters and read-only comparison of deal amounts, pipelines and stages.
- Share API request budgets across workers, honor Retry-After and prevent late refresh responses from replacing a new connection.
1.2.2
- Resolve the connected HubSpot portal automatically before background order synchronization after upgrading.
- Distinguish older attempts without portal evidence from attempts belonging to another portal.
- Use database compare-and-set leases to prevent simultaneous admin requests from acquiring the same lock.
1.2.1
- Unified button and input heights across the admin interface.
- Aligned setup actions, order search and log filters on desktop and mobile.
- Styled the routine-check filter as a matching checkbox control.
1.2.0
- Added a free Overview with scheduler evidence, last successful order sync and flagged log history.
- Bind status evidence to the verified HubSpot portal rather than token values; preserve it through token rotation and reconnection to the same portal.
- Expire abandoned dispatch/setup locks after 120 seconds and prevent an old request from releasing another request’s lock. Clean remaining locks on uninstall.
- Recognize historical successful orders from a saved deal mapping and their latest successful log without offering blind replay.
- Added a guided first sync and explicit, reusable synthetic test-order creation.
- Record order attempt times, confirmed CRM IDs and failure state using WooCommerce order metadata, including HPOS.
- Offer manual retries for known temporary or corrected missing-email failures; uncertain creation outcomes and legacy attempts require review.
- Replace blind log retry buttons with order inspection and server-side dispatch checks.
- Do not send an empty contact update when an email-only contact already exists.
- Index per-order log lookups and use WordPress site time for new log entries. Historical timestamps are retained as stored.
1.1.3
- Redesigned settings with a navy header, card layouts and gold action buttons.
- Improved keyboard focus, responsive tables and navigation labels.
- Clarified setup steps, connection errors and the limits of local diagnostic checks.
- Expanded Free/Pro descriptions, setup guidance, matching and historical-import FAQs.
- Updated the display name and directory tags; the plugin slug is unchanged.
1.1.2
- Consolidated settings under one WooCommerce menu with tabs for connection, fields, stages, logs and diagnostics.
1.1.1
- Pro: validate the cart pipeline and its two distinct stages before saving.
- Pro: keep cart settings on the current page after an AJAX save and explain expired sessions or connection failures.
1.1.0
- Clarified feature descriptions and external-service documentation.
- Report failed CRM operations instead of recording incomplete syncs as successful.
- Add bounded retries for eligible temporary sync failures.
- Read all pages of changed deals and associated line items.
- Improve token-refresh and transport-error handling.
- Remove stale line items when an order has no remaining products.
- Correct company mapping database keys.
1.0.7
- Updated Freemius SDK to the latest version.
1.0.6
- Fixed the missing public OAuth client ID on fresh installs.
1.0.5
- Restructured free/premium field mapping.
1.0.3
- Restructured free/premium settings screens.
1.0.2
- Restructured the free/premium split.
1.0.1
- Pro: two-way custom fields.
1.0.0
- Initial release.
