GoHighLevel Shopify Integration: Setup & Ecommerce Automation (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 15 September 2026 · 9 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.
The GoHighLevel Shopify integration is the first thing I set up for any client running a store, because it's what turns Shopify order data into GHL contacts, tags and workflow triggers without a single Zap. I've connected this integration for Australian ecommerce clients on Basic, Grow and Plus Shopify plans, and the setup itself takes under fifteen minutes once you know which screen does what.
What trips people up isn't the connection — it's assuming the sync does more than it actually does. This guide walks through exactly what the native HighLevel Shopify integration syncs, what stays locked inside Shopify, when you actually need Zapier or Make instead, and the automations worth building once the data is flowing.
Quick Facts
| Connection method | OAuth app under Settings > Integrations > Shopify (legacy Custom App / API token method still works for existing connections) — HighLevel Support Portal, 2026 |
| One-time import options | Products, collections, contacts, orders and transactions — HighLevel Support Portal, 2026 |
| Ongoing sync options | Contact, order, transaction, product and collection sync, plus an Order Received trigger and a Payment Received trigger — HighLevel Support Portal, 2026 |
| Order-to-transaction mapping | Only one transaction record is created per Shopify order — HighLevel Support Portal, 2026 |
| Triggers being phased out | Shopify Abandoned Cart and Shopify Order Fulfilled triggers are marked as deprecating soon in favour of newer ecommerce store triggers — HighLevel Support Portal, 2026 |
| Entry-level Shopify plan cost | Shopify Basic runs USD $39/month billed monthly, or around USD $29/month billed annually — Shopify pricing breakdown, Demandsage, 2026 |
How the native HighLevel Shopify integration actually works
Inside any sub-account, go to Settings > Integrations > Shopify and click Connect. You'll be asked for your store's .myshopify.com URL, then handed off to Shopify's own authorisation screen.
This is the OAuth App method, and according to HighLevel's own support documentation it's now the recommended path — you no longer need to manually build a Shopify custom app and paste in an Admin API access token, which was the old way of doing it. If you connected Shopify to GHL before this OAuth flow existed, your store may still be running on that legacy Custom App method, and HighLevel's guidance is not to disconnect it unless you're ready to reconnect through the current flow.
Once you authorise the app in Shopify and click Install, you're dropped back into HighLevel and the store shows as connected. From there, two separate screens control what actually happens with your data, and conflating them is the single biggest source of confusion I see in client accounts.
Import Elements vs Sync Settings — they are not the same thing
During setup, HighLevel shows an Import Elements screen where you tick which historical records to pull in once: contacts, orders, transactions, products and collections. This is a one-off backfill of whatever already exists in your store.
Immediately after that comes a separate Sync Settings screen, where you choose what keeps updating going forward — contact sync, order sync, transaction sync, product sync, collection sync, and two workflow triggers (Order Received and Payment Received). Turning a sync option off later stops future updates, but it doesn't retroactively delete records HighLevel already pulled in.
What syncs into GoHighLevel — and what deliberately stays in Shopify
The integration is built for marketing and follow-up, not for running your store. Shopify remains the system of record for checkout, payment processing, inventory and fulfilment — none of that is meant to move.
- Shopify customers sync into GHL as contacts, with fields like name, email and phone mapped across
- Orders and transactions sync in, with order status recorded in GHL as either "Completed" or "Cancelled"
- Products and collections can be imported and kept in sync for use in HighLevel's own ecommerce store tools
- Order Received and Payment Received events fire as workflow triggers you can build automations on
- Tags can be applied to contacts through workflow logic once purchase or order data lands in GHL
A few gaps matter more than they look. Product taxes aren't mapped during import or sync, so tax-inclusive pricing logic stays in Shopify. Each order produces exactly one transaction record in the sub-account, even with multiple line-item payments, and unedited SEO fields come through as null rather than placeholder text.
Inventory tracking, shipping and fulfilment logistics, and full payment processing stay entirely on Shopify's side — the GoHighLevel Stripe integration and native invoicing tools are separate systems for taking payment directly through GHL, not a replacement for Shopify checkout.
Native app, Zapier, Make or webhooks — which one should move your data?
Most agencies default to whatever they used on the last project. That's the wrong way to pick. The right question is what event needs to move, how fast, and whether it needs transformation along the way.
| Method | Best for | Limitations |
|---|---|---|
| Native Shopify app | Contacts, orders, transactions, products, collections; Order Received and Payment Received triggers | Fixed field set, no custom mapping logic, taxes not mapped, one transaction per order |
| Zapier | Quick, no-code connections to apps GHL doesn't natively touch — Slack alerts, Google Sheets logging, ShipStation | Task-based pricing adds up fast at ecommerce order volume; added latency per step |
| Make | Multi-step logic, branching and data transformation between Shopify, GHL and other tools | Steeper learning curve than Zapier; still a middleware layer that can fail silently |
| Direct webhooks | Custom fields the native sync doesn't cover, near-real-time delivery, full control over payload | Requires someone comfortable with JSON payloads and testing; no visual interface |
If you're only after contacts, orders and basic tags, the native integration covers it and you can stop there. Once you need something the native sync doesn't touch — a custom Shopify metafield, a loyalty-points balance, a fulfilment status from a third-party app — that's when a Zapier connection into GoHighLevel or Make's more flexible scenario builder earns its keep. For anything closer to real-time, or where you're already comfortable working with raw payloads, GoHighLevel's webhook triggers skip the middleware layer entirely.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
Setting up the connection: what to actually click
Have your exact Shopify store URL ready before you start — HighLevel's own guidance stresses using the precise store name or .myshopify.com URL, not a guess.
- Open the sub-account and go to Settings > Integrations > Shopify, then click Connect
- Enter your store URL and click Next
- On the Import Elements screen, tick Contact, Order, Transaction, Product and Collection import if you want a full historical backfill
- On the Sync Settings screen, enable the ongoing sync toggles and the Order Received / Payment Received triggers you plan to automate against
- Click Save — this kicks off the OAuth redirect to Shopify
- Review the permissions on Shopify's Install App screen and click Install
For a full store migration, tick every available import and sync option so nothing historical is missed. If you're only automating new orders going forward, skip the historical import and turn on ongoing sync only.
The ecommerce automations worth building once you're connected
Connecting the integration is the easy part. The value shows up in the workflows you build on top of the Order Received and Payment Received triggers.
A few that consistently pay for themselves in client accounts:
- A post-purchase SMS and email sequence triggered off Order Received, thanking the customer and setting delivery expectations
- Automatic tagging by product or collection purchased, so future campaigns can be segmented by what someone actually bought — see our guide to building a tag structure that scales before you go wild with automation-created tags
- A win-back sequence for contacts who haven't ordered in 60 or 90 days, built on top of a database reactivation campaign for cold contacts
- Order-triggered internal notifications to a fulfilment or customer service pipeline so nothing sits unactioned
- Post-purchase upsell offers sent a few days after delivery, pointing back to a Shopify collection or a HighLevel order form
Keep abandoned-checkout in mind separately. HighLevel flags the older Shopify Abandoned Cart trigger as being phased out in favour of a newer ecommerce store abandoned-checkout trigger — build new automations on the current trigger, not an old snapshot referencing the deprecating one.
For the full reference, see HighLevel's official Shopify integration support article, and for moving an entire store's history, their Shopify-to-HighLevel migration guide.
Common mistakes to avoid
- Disconnecting a working legacy Custom App connection "to tidy up" without being ready to immediately reconnect through the OAuth flow
- Assuming tax data is mapped on synced products — it isn't, so tax logic needs to live in Shopify
- Building new abandoned-checkout automations on the old Shopify Abandoned Cart trigger instead of the current ecommerce store trigger
- Expecting multiple transaction records per order — HighLevel only creates one per order, which matters if your reporting logic assumes otherwise
- Skipping the Sync Settings screen and only completing the one-time Import Elements step, then wondering why new orders stop showing up
- Reaching for Zapier or Make for data the native integration already syncs, adding cost and another point of failure for no benefit
If you want help getting this connected properly and the automations built around it, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Does the GoHighLevel Shopify integration cost extra?
The integration itself is a built-in feature inside any GHL sub-account, so there's no separate app fee to connect it. You do still pay for your Shopify plan and your HighLevel plan separately, and heavier automation use may draw on your GHL workflow and messaging usage.
Can I run checkout directly through HighLevel instead of Shopify?
No — the Shopify integration is designed to bring customer, order and transaction data into HighLevel for marketing and follow-up, while checkout, payment processing, inventory and fulfilment stay in Shopify. If you want native checkout inside GHL for a separate offer, that's a different setup using HighLevel's own order forms rather than the Shopify connection.
What happens to my existing Shopify connection if I switch to the OAuth method?
HighLevel's guidance is that an existing Custom App connection can keep syncing as-is, and switching isn't automatic or required. If you do disconnect it, you'll need to reconnect using the current OAuth App flow rather than the old Admin API token method.
Why did only one transaction get created for an order with multiple payments?
That's expected behaviour, not a bug — HighLevel's Shopify integration creates a single transaction record per order regardless of how many payment events occurred on the Shopify side.
Should I use Zapier if the native integration already covers what I need?
No. Adding Zapier or Make on top of data the native integration already syncs just adds cost and another thing that can break. Reach for middleware only for the fields, apps or logic the native sync genuinely doesn't reach.
Do product taxes sync from Shopify into HighLevel?
No. HighLevel's own documentation confirms taxes are not mapped when products are imported or synced, so any tax-sensitive pricing display needs to stay on the Shopify side.
Is the Shopify Abandoned Cart trigger still worth using?
Not for new builds. HighLevel has flagged the Shopify Abandoned Cart and Shopify Order Fulfilled triggers as deprecating in favour of newer ecommerce store triggers, so new automations should be built on the current trigger set.
Does the integration work the same on every Shopify plan?
Mostly, but HighLevel notes that Shopify Basic-plan users may hit limitations on certain data types depending on Shopify's own API access at that tier, so it's worth testing your specific sync fields after connecting rather than assuming full parity with higher Shopify plans.
