From web development to digital marketing, we build for growth. Head to Mavlers Agency.

Mavlers Logo
Book a call
All blogs

HubSpot

HubSpot and Shopify Integration: Native App, Data Hub, or Middleware? What Breaks and What it Costs

Most HubSpot Shopify sync issues are not connector failures. They are data decisions nobody owns. Compare native, Data Hub, and middleware.

By Chintan Doshi

7 minutes

November 12, 2026

HubSpot and Shopify Integration: Native App, Data Hub, or Middleware? What Breaks and What it Costs

What the native app does now, and why the old mental model misleads

HubSpot launched its Shopify integration in May 2018, free for shared users, with an ecommerce pipeline where Shopify orders landed as deals. Then the model changed. HubSpot introduced dedicated Orders and Carts objects to replace storing ecommerce transactions in Deals, and released public APIs for both in 2024.

Today’s Data Sync app syncs contacts and products both ways, while orders, carts and discount codes (beta) flow one way, from Shopify. Records update within about 10 minutes of a change. The app is built by HubSpot, available on all plans, adds ecommerce reports, and lets you segment on order and cart data. For a lot of stores, it’s the right default and the only connector they will ever need.

The trouble is that many teams still carry the 2018 picture in their heads. The data moved objects. The dashboards and workflows didn’t. Any report still built on Deals can quietly miss web orders.

Identity and history: duplicates, missing orders, and the backfill trap

Duplicate contacts

The sync matches contacts by email address, so customers stored in Shopify without one, and people who use one address at checkout and another on your forms, won’t match. The “Only sync contacts with an email address” setting reduces duplicates but also narrows what reaches HubSpot. You’re trading completeness for cleanliness, and someone should make that trade on purpose. For cleanup, see our guide on how to identify, merge, and prevent duplicate contacts in HubSpot.

Why aren’t my Shopify orders syncing to HubSpot?

Run three checks before you blame the connector.

  1. Are you looking in the right place? Orders live in the Orders object now, not in Deals.
  2. Did the customer have an email? If not, the order still syncs, just without a contact attached.
  3. Is a sync filter excluding it? Setup filters decide which records come across at all.

Orders also can’t be edited in HubSpot, because they sync one way. Corrections happen in Shopify.

The backfill trap

When you turn on order or cart sync, every record that meets your filter criteria syncs at once, and anything you already imported into either app may come across again as a duplicate. Contact deletions don’t carry over in either direction. The fix is a decision, not a setting: clean up or archive legacy imports (old CSV uploads, data from a previous connector) before you switch sync on, and decide whether years of order history belong in HubSpot at all.

Product data

Products match on product name, with capitalization, special characters, and punctuation stripped first, and Shopify metafields aren’t supported. Variants used to be a hard stop, but HubSpot now documents a separate product variant sync that brings each variant across as its own product record, one way from Shopify. Match on SKU if products already exist in HubSpot, and since HubSpot’s documentation on variants has changed recently, confirm the option in your own portal first.

Consent

This is where the two platforms think differently. Shopify tracks email marketing state as subscribed, pending, unsubscribed, or not subscribed. HubSpot splits the question in two: whether someone can be marketed to, and what they’ve agreed to receive. Only marketing contacts can receive marketing emails, and every new one counts toward your billable contact tier. Synced contacts arrive as contacts you can’t email unless you switch the app on in the Marketing Contacts integration settings, and that only applies to contacts created afterward.

Get it wrong one way and you email people who never opted in. Get it wrong the other way and you pay for contacts you shouldn’t mail or silently lose real subscribers. Consent rules should be written by whoever owns compliance, not inferred from a connector default. Our guide to enterprise email marketing in HubSpot covers the sending side.

Carts

Abandoned cart flows have real revenue behind them: Baymard’s 2026 benchmark puts documented cart abandonment at 70.22% across 50 studies (here’s what a strong abandoned cart email looks like). But the connector keeps changing. HubSpot removed several fields from cart sync on April 1, 2025, including buyer accepts marketing, and variant and discount code sync have arrived since. Somebody has to be reading the release notes for both platforms.

Native, Data Hub, or middleware: choose by the decisions you need to control

Every route answers the same two questions differently: who controls the mapping, and who maintains it. The native app runs on HubSpot’s default mappings. Custom field mapping needs at least Data Hub Starter (Data Hub is the new name for Operations Hub). Data Hub Professional adds programmable automation (custom code in JavaScript or Python), data quality automation, and up to 10 webhook triggers, and its AI data tooling is covered in our HubSpot Data Agent guide. Middleware or a custom build gives you full control of the logic, whether that’s keeping orders in Deals or bringing metafields across. The price is a second system you have to own.

RouteWhat it addsBest fitCost structureWho maintains it
Native Data SyncDefault mappingsData fits the defaults; reporting on OrdersIncluded with HubSpotHubSpot maintains the connector; you own settings, filters, consent rules
Data Hub StarterCustom field mappingsSpecific Shopify fields in specific propertiesPer seatYou own the mappings
Data Hub ProfessionalProgrammable automation, webhooksAn ops person who can maintain logic in HubSpotMonthly fee, one Core Seat includedYou own the code and workflows
MiddlewareLogic outside HubSpot; some offer orders as dealsNeeds beyond the defaults, configured rather than codedUsage or subscriptionYou own a second system and depend on its vendor
Custom buildWhatever both APIs allowMetafields, B2B pipelines in Deals, shared consent rulesEngineering timeYour engineers, permanently

HubSpot’s pricing page lists Data Hub Starter at $20 per seat per month (a limited new customer offer starts at $7) and Data Hub Professional from $720 a month billed annually, with one Core Seat included and additional Core Seats from $45 a month. Middleware is priced differently: Zapier, for example, charges per successful action step, so cost scales with volume and workflow length. Don’t line these up as “cheapest route.” They’re different cost structures.

The license is often the smallest part of the bill. Total cost is the license, plus setup, plus monitoring time, plus the cost of a silent failure nobody catches for a month. Middleware and custom builds move maintenance onto your team, while the native app hands roadmap control to HubSpot. No route “fixes” HubSpot. Each one extends it.

The owner and monitoring checklist

Before you switch sync on, write down an answer for each of the five decisions:

  1. Identity: the key you match on, and how customers without an email are handled.
  2. Order history: whether it comes in, and how legacy imports get cleaned first.
  3. Product data: which attributes marketing needs, and whether variants sync on SKU.
  4. Consent: the marketing contact rule for the Shopify app, signed off by whoever owns compliance.
  5. Backfill: the filters for each object, and which reports and workflows move from Deals to Orders.

Then name one owner. A person, not a team, owns the sync, its field mappings, and the release notes for both platforms. In our view, that’s a few hours a month inside existing headcount, not a new hire. Each month, they check sync errors in Connected Apps, orders with no contact, contacts created without an email, the change in marketing contacts after large sync events, and workflows that are failing or enrolling nobody. Multiple stores, large catalogs, and B2B selling on Shopify Plus raise the load.

If you’d like a second opinion, our HubSpot team works on these integrations as a HubSpot Solutions Partner, and we’d start with the five decisions before any data moves. For Shopify brands, the payoff shows up in ecommerce email that reaches the right customers.

The integration is only as opinionated as you are

A connector has no opinion about who your customer is, what counts as consent, or whether last decade’s orders matter. It applies whatever rules it’s given, including the ones nobody chose. Those unchosen rules are where the duplicates, missing orders, and surprise contact bills come from.

So before you compare connectors, list the five decisions and write a name next to each one.

Chintan Doshi
LinkedIn

Subject Matter Expert (SME)

Chintan is the Head of Email & CRM at Mavlers. He loves email marketing and has been in the industry for 7+ years. His track record of email marketing success covers building email programs from scratch and using data-driven strategies to turn around underperforming accounts.

Ahmad Jamal
LinkedIn

Content Writer

Writes on email marketing, CRM, and marketing automation, with a focus on lifecycle strategy and customer journeys. Brings a blend of writing expertise and technical understanding to craft engaging, strategy-driven martech content.

You may also like

Tell us about your requirement

We'll get back to you within a few hours!

Select a service