Shopify HubSpot integration beyond contact sync

A Shopify HubSpot integration brings your customers, orders and products into HubSpot so marketing and sales can segment, email and report on real purchase data. HubSpot's own Shopify app covers the standard case: customers as contacts, plus order and product data. You need a custom sync when you sell B2B and want companies, deals and sales reps to line up with Shopify companies and draft orders, or when you need custom properties, calculated fields or data flowing back into Shopify.

What typically syncs

Off-the-shelf options

• HubSpot's own Shopify integration, installed from HubSpot or the Shopify App Store. It is the first thing to try.
• Middleware such as Zapier, Make or a heavier iPaaS, for adding flows the native app doesn't cover.
• Other Shopify marketing apps that push data to HubSpot as a side feature.

Where the standard integration stops

• B2B structure. Shopify B2B has companies, company locations and contacts with roles. Mapping that to HubSpot companies and associations is outside the scope of most standard integrations.
• Custom properties. You want lifetime value by brand, first product category bought, subscription status or the last B2B catalog used as HubSpot properties.
• Deals for B2B, not D2C. You want pipeline deals only for wholesale orders or quotes, created with the right owner and stage.
• Two-way updates. Sales reps change something in HubSpot that should reach Shopify, such as a customer tag, a metafield, or a draft order for the customer to pay.
• Consent. Marketing consent exists in both systems. A careless two-way sync can re-subscribe someone who unsubscribed. Decide which system owns consent and sync it one way.
• Volume and history. Backfilling years of orders, or keeping up during a sale, can exceed what a basic sync handles gracefully.

How a custom Shopify HubSpot integration works

1. Shopify → HubSpot: the app subscribes to customers/create, customers/update, orders/create, orders/updated and B2B company webhooks, queues each event, fetches full data through the GraphQL Admin API, and upserts into HubSpot using a unique property such as email or a Shopify ID property. Upserts make a retry safe.
2. Associations: contacts are associated with companies, and orders or deals with both, using HubSpot's associations API.
3. Calculated properties: the app computes values such as lifetime value, order count by category and last order date, and writes them to custom HubSpot properties, so marketing can segment without spreadsheets.
4. HubSpot → Shopify: a HubSpot workflow calls your app's endpoint (a verified webhook) when a property changes. The app writes a Shopify customer metafield or tag, or creates a draft order from a deal and sends the invoice.
5. Backfill uses Shopify bulk operations to export historical customers and orders in one job, then batches the writes to HubSpot within its rate limits.
6. Monitoring: failed upserts are listed with HubSpot's error message, and a periodic count check compares the number of Shopify customers with the number of synced HubSpot contacts.

An example of useful custom properties

Standard sync gives you contacts and orders. These calculated properties are what usually make HubSpot segmentation useful for a store:

Recalculate them from Shopify data on each order and refund, not by adding and subtracting inside HubSpot, so they can't drift.

Getting consent right

Marketing consent exists in Shopify (email and SMS marketing consent on the customer) and in HubSpot (subscription types). The safe pattern:

1. One owner. Usually Shopify owns the consent captured at checkout, and HubSpot owns consent captured through its forms and preference centre.
2. Sync opt-outs everywhere. An unsubscribe in either system is written to the other. An opt-in only flows from the owning system.
3. Keep the evidence. Store when and where consent was given, so you can answer a data request.
4. Don't backfill consent. Importing historic customers must never mark them as subscribed unless Shopify says they are.

Several stores, one HubSpot portal

With several Shopify stores feeding one HubSpot account, keep a store property on contacts and orders, and decide how to handle the same person buying from two stores: one contact with orders from both is usually right. Use a single integration app installed on every store, so the logic stays consistent.

Decision checklist

• D2C, B2B or both? Do you need companies and deals, or only contacts?
• Which custom properties would change how you segment or sell?
• Which system owns marketing consent?
• Does anything need to flow from HubSpot back to Shopify?
• How much history needs backfilling?
• Who owns the HubSpot data model, so the integration doesn't create property sprawl?