Shopify HubSpot integration
Shopify HubSpot integration that keeps contacts, deals and orders aligned
Who this is for, and who it is not for
This fits a Shopify or Shopify Plus merchant with at least one of these conditions: marketing sends to people who already bought, an unsubscribe in one system does not reach the other, B2B buyers are tracked as HubSpot deals but order on Shopify, or a team re-exports Shopify customers into HubSpot by hand.
It does not fit a store that uses HubSpot only for forms and has no deals or lifecycle stages to keep in step. A native sync, or none, is the right answer there. It also does not fit a team that wants every Shopify event as a HubSpot property, because properties nobody reports on only slow the portal.
Five record types break between Shopify and HubSpot
HubSpot is usually the system of record for contact status and marketing consent, and Shopify for the order. These are the places that split goes wrong.
Orders
A Shopify order has to reach HubSpot as a deal, an ecommerce object or a line item on the contact, depending on how sales and marketing use it. The break is the order after sync: a refund, an edit or a cancelled line must update the same HubSpot record rather than add a second one.
Customers
A Shopify customer becomes a HubSpot contact only if email is present, and a guest checkout may carry none. Marketing consent is the sharper edge: a Shopify opt-in has to arrive as a HubSpot marketing status, and an unsubscribe in HubSpot has to flow back, or both systems keep writing to people who opted out.
Inventory
HubSpot has a product library but does not own stock. If sales quote from it, quantity should be read from the system that owns it, not typed. Writing quantity from HubSpot to Shopify is the pattern to avoid.
Pricing
A HubSpot product price and a Shopify price are two sources for one number. For B2B, decide whether a negotiated price lives on the HubSpot deal and is pushed to a Shopify catalogue, or is set in Shopify and read by HubSpot.
Returns
A refund changes the value of the deal and the lifecycle stage of the contact. If HubSpot never hears about it, a customer who returned everything still counts as a customer in reports and in segments.
Native sync, iPaaS or custom build for HubSpot: which one fits
Table: three ways to connect Shopify to HubSpot. Vendor statements come from the vendor pages named in each row (Vendor pages read October 2026). HubSpot's own Shopify integration scope and the Shopify App Store listing: not measured. The fit rule is our delivery judgement.
Native sync
HubSpot's own Shopify integration, or a Shopify App Store connector. Object coverage, sync direction and pricing: not measured.
iPaaS
Celigo's HubSpot page says its HubSpot integration apps and prebuilt connectors help teams manage the sales pipeline, and its Shopify page lists connectors and templates. Celigo pricing: not measured.
Custom build
A build designed against your HubSpot objects: consent flowing both ways, B2B deal and order matching, and a reconciliation job that finds contacts one side never received.
What we check first in a Shopify HubSpot integration
Five checks come first, and they decide which row of the table applies.
Consent in both directions
Where a marketing opt-in is captured, where an unsubscribe is stored, and whether either change reaches the other system.
The match key and duplicates
How a Shopify customer is matched to a HubSpot contact, and how many duplicate contacts already exist before anything syncs.
The deal and order model
Whether an order is a deal, an ecommerce object or a line item, confirmed against the reports sales and marketing already run.
Properties that earn their place
Each field we sync has a report or a workflow that reads it. A property nobody reads is not synced.
Who reads the errors
A named person sees a rejected contact or order, the reason and the affected customer.
What we run after a Shopify HubSpot integration goes live
Go-live starts the work, because an integration is a running system. We run these checks and name who acts on each.
- A daily comparison of Shopify customer and order counts with HubSpot records.
- A consent check that unsubscribes in either system reached the other.
- An exception view for rejected contacts and orders, with the reason and the owner.
- A review whenever a HubSpot property, workflow or lifecycle stage changes.
- A short written note each month: what failed, what it touched and what we changed.
What we can show, and what we cannot
We have no published client result for this integration yet, so this page carries none. It lists what we check and what we run instead. The published example of our method is Container One, a Shopify Plus merchant whose migration is still in progress, run one endpoint at a time with the old system as the reference. Read the Container One case study.
Other systems and the wider integration scope
The integrations hub sets out how we choose between a native app, an iPaaS and a custom build for any system. Guides to the others we connect most often:
Common questions
Does Shopify integrate with HubSpot?
Yes. Shopify connects to HubSpot through a native sync, connectors, iPaaS platforms and custom builds. Use the native sync when customers and orders map to standard HubSpot contacts and deals, and build custom when consent or B2B rules differ.
Should Shopify orders sync to HubSpot as deals?
Only for B2B or high-consideration orders that a salesperson works. Everyday DTC orders suit an ecommerce object or a line item on the contact, so the deal pipeline does not fill with completed purchases nobody follows up.
How should marketing consent sync between Shopify and HubSpot?
In both directions, with one system named as the source of truth for each market. An opt-in captured at Shopify checkout should set the HubSpot marketing status, and an unsubscribe in HubSpot should update the Shopify customer.
Can HubSpot show Shopify order history on the contact?
Yes. Orders can be shown on the contact as ecommerce records or line items. Decide which one before the sync, because switching later means rebuilding the reports and workflows that read it.
What happens to a refund in HubSpot?
It should change the deal value or ecommerce record and the contact's lifecycle stage. Otherwise a customer who returned everything still counts as a customer in segments and reports, and keeps receiving campaigns written for buyers.
Migration & Replatforming
Contacts that disagree across Shopify and HubSpot cost more than the fix
Latest guides
Shopify & Ecommerce
Shopify SEO checklist: 13 checks and who owns each
A Shopify-specific SEO checklist: 13 checks from collection canonicals and variant URLs to app scripts, structured data and AI Overview readiness, each with how to check it, what good looks like and who owns it.
Shopify & Ecommerce
Shopify vs Wix: which one fits the store you run?
Wix caps a product at 1,000 variants and six options; Shopify allows 2,048 variants and three options. Wix suits service businesses and small catalogues. Shopify suits stores where inventory, wholesale or an ERP runs the business.
Shopify & Ecommerce
Shopify Plus pricing: what $2,300 a month really costs
Shopify Plus lists at $2,300 a month on a three year term, but the licence is the only line Shopify prices for you. Here is the total cost by stage, Advanced and Plus side by side, and the cases where Advanced is the better answer.
Shopify & Ecommerce
Shopify Plus examples: 10 stores and what to copy
Ten Shopify Plus stores, each confirmed as Plus on Shopify's own customer pages, read as teardown notes. For each one: what to study, why it matters, and whether you need Plus to copy it.
AI & Search
Generative engine optimization for Shopify: 5 page changes
GEO and AEO in plain words for a Shopify brand: what an AI answer needs from your product and collection pages, what we change, how you measure it, and what nobody can promise.
AI & Search
Vector database vs graph database for AI: how to choose
Compare vector and graph databases for RAG and AI applications. Choose based on retrieval questions, relationship checks, data ownership and evaluation.