Connecting Shopify and HubSpot Properly: What a Growing Retailer Needs to Know

If you are running a retail business with a team, the question is not whether to connect Shopify and HubSpot. It is which system owns which part of the customer record, and who fixes it when the two disagree.

Get that decided and the integration is an afternoon. Skip it and you get two systems each holding a slightly different version of every customer, which is worse than the spreadsheet you started with, because now two teams trust different numbers.

What the native integration syncs

Four things, and they are worth understanding separately because you make a decision about each one.

Customers

A purchase creates or updates a contact in HubSpot. Name, email, number of orders, total revenue and average order value come across and keep updating with each purchase. Over time that is a genuinely useful record, and it is also the point where you have to decide whether Shopify or HubSpot is the master for a customer's contact details.

Orders

Every order appears against the contact, with products, quantity, price and date. That is what makes segmentation possible: lapsed buyers, single product buyers, people who only ever buy on sale.

Products

Your Shopify catalogue syncs in, which means workflows can be triggered by a specific product, emails can reference accurate product data, and you can segment by category or range. This matters more the larger the catalogue gets.

Orders as deals

The integration can create a deal for each order and map Shopify's order states, pending, fulfilled, cancelled, onto your HubSpot pipeline stages. Useful for revenue reporting and forecasting inside HubSpot. Also the decision most likely to go wrong, because a thousand orders a month in your main sales pipeline makes that pipeline useless for anything else. Give e-commerce orders their own pipeline.

Connecting it

Use the official native integration from the HubSpot App Marketplace unless you have a specific reason not to. It is built and maintained by HubSpot, it keeps getting features, and it covers what most retailers need. The Shopify side of it is in the Shopify app store.

1. Install the Shopify app in HubSpot.
2. Log in to Shopify and approve the permissions.
3. Choose which deal pipeline orders flow into, and how the fields map.

Step three is the whole thing. The wizard will happily accept the defaults and you will live with them for years. Decide the pipeline and the field mapping before you click through, and write down what you chose. HubSpot's documentation on connecting the two via Data Sync covers the field level detail.

Then the initial sync pulls in historical customers, orders and products. A new store finishes in minutes. A store with eight years of trading and high volume takes hours. Use that time to write down which segments and workflows you want, rather than starting to build them against a half-synced database.

A purchase is not a subscription

This is the part most global integration advice skips, and it is a real risk rather than a technicality.

Under the Spam Act 2003, express consent means the person knew and accepted that they would receive marketing from you. Inferred consent is narrower than people assume: it applies where the person knowingly and directly gave you the address, and it is reasonable to believe they would expect marketing, which usually means a provable ongoing relationship with the marketing directly related to it. ACMA sets out its consent expectations for businesses using direct marketing in plain terms.

A completed Shopify order gives you an email address for the purposes of that order. On its own it is a thin basis for a weekly promotional campaign, and the burden of proving consent is on the sender, not the recipient.

So, three practical rules once the sync is running.

• Capture the marketing opt-in at checkout as its own field, unticked by default, and sync that field into HubSpot.
• Filter your marketing lists on that field, not on the existence of an order. Order data is for segmentation. Consent is for enrolment. Keeping those two separate is the whole discipline.
• Check the footer. Every commercial message needs an unsubscribe that does not require extra personal information, a login or an account, and has to identify the business that authorised it, by correct legal name, or name and ABN. ACMA's guidance on avoiding spam is worth ten minutes.

None of that stops you doing anything useful. It stops you doing the one thing that generates complaints.

What to build once the data is flowing

Four automations earn their keep before anything clever does.

• First purchase welcome. Who you are, how to use or care for what they bought, where to get help. This is the email people actually open.
• Abandoned cart. A reminder of what they left. An incentive only if your margin and your brand can carry it, because it trains people to abandon.
• Post purchase. Review request, complementary products, support details. Timed to when the thing has actually arrived, not to when it shipped.
• High value segments. Lists based on lifetime value or order frequency, used for early access and loyalty rather than for more discounting.

There is a fuller walkthrough of using purchase history for personalised email once the data is in place.

The dashboard worth having

Build one e-commerce dashboard rather than five, and put on it:

• Average order value
• Customer lifetime value
• Abandoned cart rate
• Revenue attributed to specific workflows and campaigns

Broken down by state or region, product category, and acquisition channel. Attribution reporting will connect the chain from Shopify order, to contact in HubSpot, to the campaign or asset that influenced the sale. Treat that chain as directional rather than exact, and say so when you present it.

Custom objects and metafields

As you grow, some things do not fit the contact or the deal: warranties, subscriptions, loyalty tiers. Shopify metafields and HubSpot custom objects or properties are how you handle those. Add them when a reporting question forces the issue, not in advance, because every custom object is a thing someone has to maintain.

When a custom integration is justified

For most Australian retailers the native app is enough. Look at something custom only if you have genuinely unusual data needs, you depend heavily on custom metafields and conditional logic, or you need to push data into another system in a specific shape. If that is you, the API and webhook practices behind a custom integration are worth reading first, and it is also worth checking whether Revenue Hub changes how you would structure it.

Keeping it honest

Three habits, checked quarterly.

• Confirm the property mappings still do what you think, particularly after either platform ships an update.
• Clear out the duplicates and obvious junk records.
• Keep naming consistent across the two systems. A product category called Outdoor in one and Outdoors in the other splits every report that touches it.

Where to start

Before you install anything, answer two questions on paper. Which system owns the customer's contact details, and which pipeline do orders belong in. Those two answers determine whether this integration is useful or a source of arguments.

Designing that split is a chunk of our RevOps and HubSpot work. If you already have the two connected and the numbers do not agree, send us what you are seeing, because that is usually a mapping decision made by a wizard rather than by a person.