See the top GoHighLevel agencies in the USA for 2026: 14 ranked
The GoHighLevel Shopify integration: what syncs, triggers and setup
Yes. GoHighLevel connects to Shopify natively, from Settings > Integrations > Shopify in each sub-account. Since HighLevel added an OAuth app, setup takes a store URL and one approval in Shopify, with no custom app or API token. It imports and keeps syncing contacts, orders, transactions, products and collections. Shopify activity can start workflows through the Abandoned Checkout and Order Fulfilled triggers. Taxes are not mapped to products, and workflows and store pages don't come across.
Updated
Shopify integration facts
| Fact | Detail | Source |
|---|---|---|
| Type | Built into the sub-account under Settings > Integrations > Shopify (no Zapier needed) | help.gohighlevel.com |
| Connection method | OAuth app: enter the store URL, approve the install in Shopify. The older custom app method is now legacy | ideas.gohighlevel.com |
| Data it brings in | Contacts, orders, transactions, products and collections, as a one-time import and as ongoing sync | help.gohighlevel.com |
| Contact fields added | Shopify Lifetime Value, Order Count, Last Order Date, First Order Date and Tax Exempt | help.gohighlevel.com |
| Orders | One transaction per Shopify order; statuses arrive as Completed or Cancelled | help.gohighlevel.com |
| Taxes | Not mapped to products when importing or syncing | help.gohighlevel.com |
| Shopify Basic plan | Can sync customers and orders through OAuth with no Shopify upgrade (setup guide). The migration FAQ still says Basic "may not be able to sync" them | help.gohighlevel.com |
| Workflow triggers | Abandoned Checkout and Order Fulfilled under Ecommerce Stores, with Order Source set to External > Shopify | help.gohighlevel.com |
| Setup guide updated | October 15, 2026 | help.gohighlevel.com |
What syncs between Shopify and GoHighLevel
Five kinds of Shopify data sync to HighLevel: contacts, orders, transactions, products and collections. During setup there are two separate screens. Import Elements pulls in historical records once. Sync Settings controls what keeps flowing after that. Changing sync settings later mainly affects future data, and turning a sync off does not delete what already arrived.
| Sync option | What it does |
|---|---|
| Contact Sync | Shopify customers become contacts; customer tags go into the normal tag field |
| Order Sync | Each order lands in the sub-account with one linked transaction |
| Order Received Trigger | Lets Shopify orders fire HighLevel's order trigger |
| Transaction Sync | Keeps payment records in step with Shopify |
| Payment Received Trigger | Lets Shopify payments fire HighLevel's payment trigger |
| Product Sync | Products appear under Payments > Products > Products |
| Collection Sync | Collections appear under Payments > Products > Product Collections |
Each synced contact gets five Shopify fields: Lifetime Value, Order Count, Last Order Date, First Order Date and Tax Exempt. All fields sync together; there is no per-field opt-out. Email and SMS consent fields are listed as "coming soon". Only completed, paid orders change these fields. A refund lowers Lifetime Value but does not lower Order Count, and draft orders are ignored. Lifetime Value covers purchases from the connected Shopify store only.
The migration guide says the contact import covers Shopify customers who have placed an order. Customers who never ordered may not come across.
Shopify triggers in GoHighLevel workflows
Shopify events start HighLevel workflows through two Ecommerce Stores triggers, Abandoned Checkout and Order Fulfilled, plus the order and payment triggers switched on during setup. Both Ecommerce Stores triggers also work for HighLevel's own stores, so you pick Order Source: External and Sub-Source: Shopify. Shopify is the only external store supported; HighLevel's Order Fulfilled article says WooCommerce is not supported yet.
| Trigger | Status | Notes |
|---|---|---|
| Abandoned Checkout | Current | Ecommerce Stores. Fires when a shopper enters an email but doesn't pay within the Duration (minutes) you set. Filters: cart value, country, products, order source. |
| Order Fulfilled | Current | Ecommerce Stores. Fires each time an item group is marked fulfilled. Filters include shipping carrier, tracking number, order tags and fulfilled products. |
| Order Received / Payment Received | Current | Switched on in the Shopify Sync Settings screen during setup. |
| Shopify Abandoned Cart | Deprecating soon | Existing workflows keep running; HighLevel recommends moving to Abandoned Checkout. |
| Shopify Order Fulfilled | Deprecating soon | Existing workflows keep running; HighLevel recommends moving to Order Fulfilled. |
HighLevel doesn't set a default abandonment window. Its help article (updated September 30, 2026) says fast-moving, low-priced stores often use 15 to 30 minutes and high-ticket stores several hours. The Shopping Cart element in the email builder fills in the shopper's cart items. Recovered orders show under Payments > Orders, and sends, opens, clicks and saved revenue sit in the workflow's Analytics tab.
For Order Fulfilled (updated October 27, 2026), each Shopify shipment is its own event and lists only that shipment's items. Adding or correcting a tracking number after shipping sends a follow-up event. Cancelled fulfilments and imported historical orders do not fire it.
How to connect Shopify to GoHighLevel
Connecting Shopify takes eight steps in the sub-account, with no developer setup:
- Open the sub-account and go to Settings > Integrations > Shopify.
- Click Connect.
- Type the store URL or store name exactly and click Next. The store name is the part after
/store/in the Shopify admin URL. - On Import Elements, tick the history to bring in: Contact, Order, Transaction, Product, Collection.
- Click Next. On Sync Settings, tick the ongoing syncs and triggers.
- Click Save. HighLevel sends you to Shopify.
- On Shopify's Install app screen, review the permissions and click Install.
- Shopify returns you to HighLevel with the store connected. Check products under Payments > Products.
HighLevel's changelog says the OAuth connection stores no long-lived API credentials, and access can be revoked from the Shopify admin at any time. Older connections built with a Shopify custom app keep working. HighLevel advises against disconnecting one unless you are ready to reconnect through OAuth. Basic-plan stores on the old method must reconnect through OAuth to get customer and order sync.
Limits and common problems
- No tax mapping. Taxes are not mapped to products on import or sync.
- SEO fields can arrive empty. Shopify products still on default SEO settings come in as null.
- Simple order statuses. Orders arrive only as Completed or Cancelled, each with one transaction.
- Contacts not syncing. HighLevel says Shopify may not be returning customer data because of its plan-based access rules. Its two articles disagree on whether Basic is enough (see the FAQ below).
- Email needed for cart recovery. A checkout without an email is never marked abandoned.
- Price and Available Quantity can't be used in If/Else conditions on the Abandoned Checkout trigger, only as custom values.
- Nothing else migrates. Workflows, store pages, checkout pages and payment settings are rebuilt by hand under Automation > Workflows and the store builder.
HighLevel's articles don't say whether one sub-account can connect more than one Shopify store, and they don't publish how quickly new orders appear after they are placed.
Native integration vs Zapier or Make
The native integration is the simpler choice for syncing customers, orders and products, because it adds the Shopify contact fields and the store-aware triggers and costs nothing extra. Zapier or Make make sense when a step falls outside what the native sync covers, such as writing Shopify data into a third app in the same run.
On Make, the HighLevel app has modules to create, update and search contacts, opportunities and tasks, add notes and enrol contacts in campaigns, and it can sit in the same scenario as Shopify. Make and Zapier bill by their own plans. Inside HighLevel, outbound calls through the Custom Webhook action are a premium workflow feature: 100 free lifetime runs per sub-account, then $0.01 a run without a Workflow Pro plan.
For more on Make, see the Make.com GoHighLevel integration. If the store also takes PayPal, the GoHighLevel PayPal integration covers where it works. Delivering digital files after an order is covered in digital product delivery. To have a store connection set up for you, compare GoHighLevel setup agencies.
Frequently asked questions
Does GoHighLevel integrate with Shopify?
Yes. HighLevel has a built-in Shopify integration in each sub-account under Settings > Integrations > Shopify. It imports and keeps syncing Shopify contacts, orders, transactions, products and collections, and Shopify events can start HighLevel workflows.
Do I need a Shopify custom app or API token to connect HighLevel?
No, not for new connections. HighLevel added an OAuth app: you enter the store URL, choose what to import and sync, then approve the install in Shopify. Stores already connected with the older custom app method keep working, but if that connection is removed it has to be rebuilt through OAuth.
Can GoHighLevel send abandoned cart messages for a Shopify store?
Yes. Use the Abandoned Checkout trigger under Ecommerce Stores, set Order Source to External and Sub-Source to Shopify, and set how many minutes count as abandoned. The shopper must have entered an email address, or the checkout is never marked abandoned and the workflow does not start.
Does Shopify sync to GoHighLevel on the Shopify Basic plan?
HighLevel's Shopify setup guide, updated October 15, 2026, says Basic stores can sync customer and order data through OAuth with no plan upgrade. Its migration FAQ, updated the same day, still says Basic stores may not be able to sync contacts, orders or transactions. If contacts stop coming in, HighLevel says Shopify's plan-based data rules are the usual cause.
Why does my Shopify order fulfilled workflow fire more than once?
HighLevel's Order Fulfilled trigger runs once per shipment, so a split order fires once for each part. HighLevel suggests a Tracking Number filter set to "Is Not Empty" to cut duplicates. Marking an order Delivered does not fire it again.
Does the Shopify integration bring over workflows or store pages?
No. HighLevel's migration guide says workflows, store pages, checkout pages, payment settings and team processes are not migrated and must be rebuilt. Only contacts, orders, transactions, products and collections come across.
Sources
All checked November 16, 2026.
- HighLevel help: How to Use the Shopify Integration with Your Account (last modified October 15, 2026)
- HighLevel help: How to migrate Shopify stores to HighLevel (last modified October 15, 2026)
- HighLevel changelog: Shopify integration just got simpler, no custom app setup required (undated)
- HighLevel help: Abandoned Checkout Trigger for E-commerce Stores (last modified September 30, 2026)
- HighLevel help: Workflow Trigger - Order Fulfilled (for ecommerce stores, including Shopify) (last modified October 27, 2026)
- HighLevel help: how to enable and rebill workflow premium features (last modified September 28, 2026)
- Make app documentation: GoHighLevel (created February 3, 2025; no update date)