CRM

Shopify CRM integration: methods, data mapping and an 8-step setup

How to connect Shopify to a CRM: what to sync, app vs automation vs custom API, an 8-step setup, field mapping, a test checklist and common fixes.

19 Nov 202613 min readSalesformics editorial
Parcels linked by glowing threads to a cluster of tiles, illustrating Shopify data flowing into a CRM
In short

A Shopify CRM integration copies customers, orders and consent from your store into your CRM, so sales, marketing and support work from one record instead of three exports.

  • Use a native app if it syncs the objects you need. Use an automation platform for simple one-way flows. Build a custom API integration when the logic is specific to your business.
  • Decide the matching key, the order model and the consent rules before you install anything
  • Webhooks miss events, so schedule a nightly reconciliation

A Shopify CRM integration is a connection that moves customer, order and marketing-consent data from your Shopify store into a CRM and keeps the two in step. Once it works, a salesperson opening a contact sees what that person bought, when, how much they have spent and whether they can be emailed, without logging into the Shopify admin or asking for a spreadsheet.

There are three ways to build that connection: a ready-made app from the Shopify App Store, an automation platform such as Zapier or Make, or a custom integration written against Shopify's API. The right choice depends less on the CRM brand and more on what you need to sync, how often, and how much your data model differs from the defaults.

For most small stores an app is enough. If your store runs on Shopify Plus with B2B price lists, several storefronts or a headless front end, though, the integration usually becomes part of a larger build. At that point a partner offering Shopify website development services can design the store and the data flow together. This guide covers both paths. You will find what to sync, how to choose a method, an eight-step setup plan, a field-mapping cheat sheet and the problems that break most integrations in the first month.

What does a Shopify CRM integration actually sync?

A Shopify CRM integration syncs five kinds of data: customers, orders, products, abandoned checkouts and marketing consent. Everything else is optional. The table shows where each Shopify object usually lands in a CRM and what to watch for.

Shopify objectTypical CRM recordWatch out for
CustomerContactGuest checkouts without an account; one person with two emails
OrderDeal, custom order object or timeline eventRefunds, edits and partial fulfilment change the order after it is created
Line items and productsProducts on the deal or a purchase history fieldVariants (size, colour) need their own SKU, not just the product title
Abandoned checkoutLead activity or taskOnly useful if the shopper left an email; expires quickly
Email and SMS consentSubscription or consent fieldsMust sync both ways, or you will email people who unsubscribed
Customer tagsPicklist or multi-select fieldFree-text tags turn into dozens of near-duplicate values
Company and location (B2B)Company / accountSeveral buyers per company; payment terms live on the location

Notice that data doesn't flow only one way. Orders and customers start in Shopify, but consent changes, phone numbers corrected by a support rep, and tags set by sales can start in the CRM. Decide early which system owns each field. Our CRM integration guide covers this "system of record" question in more detail for any pair of tools.

Do you need a CRM if Shopify already stores customers?

You need a CRM when more than one person talks to customers, when you sell to businesses, or when a sale involves conversations before checkout. Shopify's customer list is built for orders and email campaigns. It isn't built for managing relationships.

Shopify gives you customer profiles, order history, segments and built-in email marketing. For a single founder selling a few hundred orders a month, that can be plenty. A CRM adds what Shopify lacks:

  • Pipelines. Wholesale enquiries, custom orders and high-value quotes move through stages before anyone pays.
  • Ownership and tasks. Each account has a named owner, a next step and a due date.
  • Conversation history. Calls, emails and meetings sit on the same timeline as purchases.
  • Data from other channels. Leads from trade shows, marketplaces, phone orders and your website forms live next to online buyers.
  • Reporting across the funnel. You can see which lead source turns into repeat customers, not just first orders.

A simple test: if your team keeps a side spreadsheet of "important customers" with notes Shopify can't hold, you already need a CRM. The integration's job is to make that spreadsheet unnecessary.

Three ways to connect Shopify to a CRM

You can connect Shopify to a CRM with a native app, an automation platform or a custom API integration. They differ in setup time, flexibility and who maintains them.

Native app from the Shopify App Store

Most popular CRMs and marketing platforms publish a Shopify app. You install it, approve the permissions, pick which objects to sync and run an initial import. Setup takes an afternoon. The trade-off is that you accept the vendor's data model. If the app turns every order into a deal and you wanted orders on a timeline, there may be no switch to change it.

Before installing, read the listing closely and check four things:

  • who built the app: the CRM vendor itself or a third party;
  • when it was last updated;
  • what recent reviews complain about;
  • exactly which objects it syncs, and in which direction.

Automation platform (Zapier, Make, n8n)

An integration platform listens for a Shopify event, such as a new order, and runs actions in the CRM, such as creating or updating a contact. It is the quickest route when no native app exists, or when you only need two or three one-way flows. It gets fragile as flows multiply. Each one is a separate recipe with its own error handling, and pricing usually scales with the number of tasks run.

Custom API integration

A developer writes a small service that subscribes to Shopify webhooks, calls Shopify's Admin API and writes to your CRM's API. You control the matching rules, the order model, the retry logic and the reconciliation schedule. It costs more upfront and needs someone to own it, but it is the only option that fits unusual processes: B2B accounts with several buyers, subscriptions, marketplaces feeding the same CRM, or a custom checkout.

Native appAutomation platformCustom API
Setup timeHoursHours to daysWeeks
FlexibilityLow: vendor's modelMedium: per-flow logicHigh: any logic
Two-way syncSometimesPossible, error-proneYes, by design
Historical importUsually built inManual or limitedScripted
Ongoing costApp subscriptionPer-task pricingHosting and maintenance time
Best forStandard stores, standard CRMsSimple one-way flows, no native appPlus, B2B, headless, multi-store
TipStart with the cheapest method that syncs every object in your table. Moving from an app to a custom build later is normal. Ripping out twenty fragile automation recipes isn't fun.

Which CRM works best with Shopify?

The best CRM for Shopify is the one whose integration syncs the objects your team uses, in the direction you need. Brand matters less than you think. Here is how the common choices tend to fit:

Type of toolExamplesTypical fit
All-in-one marketing and sales CRMHubSpot, Zoho CRMStores that also run B2B or high-touch sales next to ecommerce
Ecommerce marketing platformKlaviyo, BrevoEmail and SMS-led stores; strong on segments, light on pipelines
Sales pipeline CRMPipedrive, SalesformicsWholesale, custom orders and quote-based sales
Enterprise CRMSalesforce, Microsoft Dynamics 365Large catalogues, several brands, complex service teams
Helpdesk with customer profilesGorgias, ZendeskSupport-heavy stores that mainly need order context on tickets

Many stores run two tools: an ecommerce marketing platform for campaigns and a CRM for sales and accounts. That works, but only if one of them owns consent. Otherwise an unsubscribe in one tool never reaches the other.

How to set up a Shopify CRM integration in 8 steps

Setting up a Shopify CRM integration takes eight steps, from writing down goals to monitoring the live sync. Skipping the first three is the most common reason integrations get rebuilt.

1. Write down what each team needs to see

Ask sales, marketing and support for the three questions they want the CRM to answer. "Which wholesale accounts have not reordered in 60 days?" is a requirement. "Sync everything" isn't.

2. Choose the matching key

Email is the usual key for contacts. Also store the Shopify customer ID in a dedicated CRM field so updates always hit the right record, even after someone changes their email.

3. Decide how orders appear

Pick one model and stick to it:

  • Deals: good for B2B and quotes.
  • A custom order object: best for reporting on repeat purchases.
  • Timeline events with summary fields such as total spent and last order date: lightest for high-volume B2C.

4. Map the fields

List every Shopify field you need, the CRM field it goes to, the direction of sync and which system wins on conflict. Keep it in a shared sheet. It becomes the documentation.

5. Clean before you import

Merge duplicate customers, standardise tags and remove test orders in Shopify first. Importing dirty data only spreads it. The same rules apply as in any CRM data migration.

6. Connect in a test environment

Use a development store or a CRM sandbox if you have one. Place real test orders, including a refund, a partial fulfilment, a guest checkout and an order with a discount code.

7. Run the historical import, then switch on live sync

Import past customers and orders in batches, check the totals against Shopify reports, and only then turn on real-time updates.

8. Monitor and reconcile

Set an alert for failed syncs and schedule a nightly job that compares recent Shopify orders with the CRM. Shopify's own developer documentation is blunt about why. It says webhook delivery isn't always guaranteed and recommends periodic reconciliation jobs.

Example: one store that sells both retail and wholesale

Here is how the eight steps play out for a typical mixed store. It is an illustration, not a client case. Picture a small coffee roaster that sells bags to consumers on Shopify and supplies cafés on trade terms.

  • Questions from the team: sales wants to know which cafés are late reordering. Marketing wants consumer buyers who have not ordered in 90 days. Support wants order status on every ticket.
  • Order model: café orders become deals in a wholesale pipeline. Consumer orders stay as timeline events with roll-up fields, so the pipeline isn't buried under hundreds of small orders.
  • Matching: email plus Shopify customer ID. Cafés are companies, and each barista or owner who orders is a contact under that company.
  • Ownership: Shopify owns orders, products and addresses. The CRM owns account owner, café segment and payment notes. Consent syncs both ways, with the email platform as the single owner.
  • Method: the CRM's native app handles consumer customers and orders. A small custom service handles café accounts, because the app can't attach several buyers to one company.
  • First automation: a task for the account owner when a café goes 20% past its usual reorder gap.

The split method is common. Use the app where the defaults fit and custom code only for the part that doesn't. That keeps the build small and the maintenance honest.

How should you map Shopify data to CRM fields?

Map Shopify data to CRM fields by giving every field one owner, one format and one direction. These rules prevent most clean-up work later:

  • Keep IDs, not just names. Store the Shopify customer ID, order ID and product SKU. Names change; IDs don't.
  • Turn tags into picklists. Map the handful of tags that matter, such as "wholesale", "VIP" or "influencer", to fixed CRM values. Ignore the rest.
  • Store money with its currency. If you sell in more than one currency, a bare number on a contact is meaningless.
  • Use roll-up fields. Total spent, order count, first and last order date and average order value let you build segments without opening every order. Our guide to segment marketing shows what to do with them.
  • Treat consent as its own field set. Email consent, SMS consent, the date and the source. Never infer consent from "has placed an order".
  • Leave addresses in Shopify unless sales or delivery planning really needs them. Fewer copies of personal data means fewer places to keep accurate.

What changes for Shopify Plus, B2B and headless stores?

Shopify Plus, B2B and headless stores usually need a custom or heavily configured integration, because their data model goes beyond one customer placing one order.

  • B2B on Shopify introduces companies, company locations and buyers with permissions. A CRM account needs to hold several contacts, each tied to the right location, with payment terms and catalogues kept in sync.
  • Several storefronts (one per region or brand) mean the same person can exist in two stores. Decide whether the CRM shows one merged contact or one per store, and tag records with their source store.
  • Headless builds often add accounts, wishlists or quote requests outside Shopify's standard checkout. Those events need their own route into the CRM.
  • Higher volume means rate limits matter. Shopify meters its GraphQL Admin API by calculated query cost, by plan. A custom integration should queue requests and back off rather than fail.
  • Shopify Flow, the platform's built-in automation tool, can tag customers or send events to a webhook. It is a handy trigger layer, but it doesn't replace a sync.

If B2B buyers also log in to reorder and download invoices, the CRM and the store often share a front end. Our article on building a B2B customer portal covers that next step.

Which automations should you build first?

Build the automations that turn store events into sales actions first. Marketing flows are usually already covered by your email platform.

  1. High-value first order: create a task for an owner to call or send a personal thank-you when an order passes a set amount.
  2. Wholesale or trade sign-up: create a deal in the B2B pipeline and assign it by region.
  3. Reorder reminder: flag accounts that have gone longer than their usual gap between orders.
  4. Abandoned high-value cart: for B2B or expensive items, a task for a human follow-up works better than a third automated email.
  5. Refund or complaint: notify the account owner so the next sales call doesn't open with an upsell.
  6. VIP threshold: when lifetime spend crosses a level, update the segment and tell the owner.

Testing checklist before go-live

Test the integration with real edge cases, not just one clean order. Tick every item before switching it on for the whole store:

  • New customer with an account creates exactly one contact
  • Guest checkout with an existing email updates that contact rather than creating a duplicate
  • Order with a discount code shows the paid amount, not the list price
  • Full and partial refunds update totals and roll-up fields
  • Edited order (item added or removed) updates the CRM record
  • Unsubscribe in Shopify reaches the CRM, and the reverse
  • Customer changes email in Shopify and the CRM record still matches by ID
  • Test and draft orders are filtered out
  • A sync failure produces an alert someone actually receives
  • Imported historical totals match Shopify's own reports for the same period

Common Shopify CRM integration problems and fixes

Most integration problems come from duplicates, missed events and unclear ownership of fields. The table lists what typically goes wrong and what to do.

ProblemUsual causeFix
Duplicate contactsGuest checkouts, typos, matching on nameMatch on email plus Shopify customer ID; merge on a schedule
Orders missing in the CRMMissed webhook, app downtimeNightly reconciliation of the last few days of orders
Totals don't match ShopifyRefunds and edits not synced, currency mixedSync order updates, not only order creation; store currency
People emailed after unsubscribingConsent synced one way onlyPick one consent owner and sync changes both ways
Sync slows down at peakAPI limits during sales eventsQueue and retry with back-off; avoid full re-syncs on busy days
Fields overwrittenBoth systems edit the same fieldSet a winner per field in the mapping sheet

How much does a Shopify CRM integration cost?

The cost of a Shopify CRM integration depends mostly on the method. Licence fees vary by vendor, so think in terms of effort and running costs:

  • Native app: often included in the CRM plan or sold as an add-on. Budget a day or two of internal time for mapping, clean-up and testing.
  • Automation platform: a monthly subscription that grows with task volume, plus the time to build and maintain each flow.
  • Custom integration: several weeks of developer time for a typical B2B or Plus setup, plus hosting, monitoring and someone who owns fixes after Shopify or CRM API updates.

The hidden cost is bad data. A cheap integration that creates duplicates or misses refunds costs more in wrong reports and awkward sales calls than a properly scoped one.

Shopify CRM integration FAQ

Does Shopify have a built-in CRM?

Shopify has customer profiles, order history, segments and built-in email marketing, which covers basic customer management. It has no sales pipelines, account ownership, tasks or call logging, so teams that sell to businesses or work deals by hand usually connect a separate CRM.

Can I connect Shopify to a CRM without coding?

Yes. Most CRMs publish an app in the Shopify App Store, and automation platforms such as Zapier or Make can link Shopify to almost any CRM. Code is only needed when your data model or sync rules go beyond what those tools offer.

Should Shopify orders become deals in the CRM?

Only when orders follow a sales conversation, such as wholesale, quotes or custom work. For high-volume consumer orders, roll-up fields on the contact or timeline events are lighter and keep the pipeline clean.

How long does a Shopify CRM integration take?

A native app can be live in a day, including mapping and testing. A few automation recipes take a few days. A custom integration for a Shopify Plus or B2B store usually takes several weeks, including historical import and reconciliation.

Do I need two-way sync between Shopify and my CRM?

For marketing consent and contact details, yes, or unsubscribes and corrections get lost. Orders and products normally flow one way, from Shopify to the CRM, because Shopify stays the system of record for them.

Try it on your own pipeline14-day trial, no card needed.
Start free