Can Shopify Integrate With Salesforce? Routes and Costs

Does Salesforce Have an Official Shopify Connector?

Yes, and it comes from Salesforce. Its developer documentation describes a Shopify connector for Data 360 with one stated job: “Use the Shopify connector to ingest data into Data 360.” It is the one Shopify connector we found in Salesforce's Data 360 documentation as of October 8, 2026; MuleSoft's Anypoint Connector for Shopify, covered below, is a separate route that exposes operations of Shopify's REST Admin API.

In Salesforce's table of Data 360 connectors, the Shopify Connector is listed as Data In, structured, with batch and zero copy as its methods. Its status is the next thing to know, and the connector's own page states it:

Beta comes with Salesforce's Beta Services Terms, and the same page says “a customer may opt to try a Beta Service in its sole discretion.” As of October 2026, running store data through it is your call, not a default.

Which Route Fits Your Salesforce Setup

The deciding question is where the Shopify data has to land: Data 360, the CRM your sales team uses, Marketing Cloud, or a flow of your own. Each row below is a route that a Salesforce, Shopify, MuleSoft or Zapier page documents, with what that page says about direction.

Sync Apps for Salesforce CRM and Marketing Cloud

For Salesforce CRM and Marketing Cloud, the route runs through apps from other developers. Shopify's guide to CRM integrations says so directly:

The guide's example is Salesforce Sync, which “sends Shopify customer and order data to Salesforce”; the guide says it starts at $19 per month and includes a seven-day free trial. Three such apps were on the App Store on October 8, 2026:

Worked example — a store with 1,000 orders a month. On the listings as of October 8, 2026, that volume sits on Salesforce Sync's $39 plan and inside Shophop's $50 base plan. The two do different jobs, so compare them on where your data has to land first: Salesforce Sync writes to Salesforce CRM, while Shophop also covers Marketing Cloud.

Above those volumes, each of those two listings adds its own charge per extra order or per extra 1,000 orders, so read your bill off the listing for your volume. Before you install any sync app, check on its listing which Salesforce records it creates and run it on a few test orders.

MuleSoft's Shopify Connector

If your company already runs MuleSoft's Anypoint Platform, there is a ready connector. MuleSoft's connector documentation says “Anypoint Connector for Shopify (Shopify Connector) gives you access to the Shopify platform,” and that “This connector exposes operations provided by the Shopify REST Admin API.”

That REST base is the thing to weigh. Shopify's own reference is direct: “The REST Admin API is a legacy API as of October 1, 2024.” What that status means for an integration you are about to build is covered in our REST to GraphQL migration guide.

On MuleSoft's side, the connector release notes say “The connector is now compatible with Shopify REST Admin API v2026-01,” and list release 1.1.14, dated September 4, 2026, as the newest.

Zapier or a Custom Build

If the routes above don't fit the flow you have in mind, two options remain:

• Zapier. Zapier has a Salesforce and Shopify integration page headed “Connect Salesforce and Shopify to power AI-driven automation.” Whether an automation layer of that kind or Shopify's own Flow fits better is the subject of our Shopify Flow vs Zapier vs n8n comparison.
• Your own app. When you need a flow of your own, such as data going back into Shopify, a developer builds it on Shopify's Admin API; start with our guide to Shopify webhooks.

How to Connect Shopify to Data 360

Two gates sit in this sequence, and they are different. Steps 1 and 2 decide whether you can set the connector up at all: Salesforce's connection guide asks for the System Admin profile or the Data Cloud Architect permission set, and its data stream guide for the Data Cloud Architect permission set, so hand this list to whoever holds them in your org. Step 5 decides what it carries, one new object per stream in batch.

Salesforce documents steps 3 and 4 on separate pages, the external credential and the Shopify connection, and gives the second one a single purpose: “Set up the Shopify connection to start the flow of data into Data 360.”

What the Data 360 Connector Brings In

What arrives, and in what shape, is set when you create a data stream. Salesforce's data stream guide describes the result: “The data stream creates a data lake object (DLO) in Data 360 that you can map to the Customer 360 Data Model to use across Data 360.”

• Two connection methods. “This connector supports both batch ingest and zero copy connection methods,” and both are beta as of October 2026.
• One object at a time in batch. In batch mode, “You can select one new object on the Available Objects tab,” so a store that needs customers, orders and products plans a stream for each.
• Two schemas. Salesforce documents a GraphQL schema named GRAPHQL-2024-07 and a REST schema named REST-2024-07.
• Objects you'll recognise. Among the GraphQL schema's objects are Customers, Companies, CompanyContacts, DraftOrders, Orders and Products; Salesforce describes Customers as “Retrieves a list of customers.”

On direction, the connector table gives one answer: Data In. The REST schema describes its Customers object as “Create, update, delete, and query customers,” but that line describes the schema's object, not the direction this connector moves data.

What Does a Shopify–Salesforce Integration Cost?

The sync apps are priced separately in the sync-apps table: Salesforce Sync and Shophop by orders, Webkul: Sync Marketing Cloud by plan tier. Salesforce prices Data 360 by use, and its pricing page draws the line at ingestion:

If you already pay for Salesforce, the start is lower still: “Salesforce customers can provision Data 360 for free with a limited amount of storage and consumption credits.” The list prices behind use sit on the same page, and the Sales Cloud seat, for a store with no Salesforce yet, sits on Salesforce's Sales Cloud pricing page.

Which meters your use triggers is set by your own Salesforce contract, not by this table, so ask your Salesforce account team for the figures that apply, and whether your org's edition includes Data 360, before you plan volumes.

What to Check Before You Rely on the Connector

Three points in Salesforce's documentation change how much weight the connector can carry. Each row pairs one with the move it calls for.

The Shopify API Version Under the Connector

Salesforce's object pages name both Shopify schemas after a date: GRAPHQL-2024-07 and REST-2024-07. On Shopify's side, versions age on a fixed policy: “Each stable version is supported for a minimum of 12 months, with at least nine months of overlap between consecutive versions.”

What happens when an app calls a version that has aged out is documented too:

A schema label is not proof of the version the connector actually calls, so treat it as a check rather than a worry: after Test Connection, and again periodically, compare the fields in your data lake object with what you expect from Shopify.

When You Don't Need Salesforce

Salesforce earns its place when a team already sells, serves or markets in it and needs the store's buyers and orders there. If that team does not exist yet, look at what your store already does before adding a second system: our answer on which CRM features Shopify has natively goes through them one by one.

• Choosing a CRM, not connecting one. If the decision is still open, our Shopify to HubSpot guide covers that vendor's connector, what syncs and what it costs.
• Zoho CRM instead. The Zoho CRM route and its gates work differently.
• Starting Salesforce from zero. The Sales Cloud entry seat is in the cost table, at list price, billed monthly or annually.

The Bottom Line

The integration question splits on one fact you already know: which Salesforce cloud your team works in. The connector, the sync apps and the custom routes each answer a different version of it.

Frequently Asked Questions