Shopify Salesforce integration
Shopify Salesforce integration that settles who owns the customer record
Who this is for, and who it is not for
This fits a Shopify or Shopify Plus merchant with at least one of these conditions: sales reps cannot see what a customer ordered on Shopify, B2B buyers exist as Shopify company accounts and as Salesforce accounts under different names, support cases open without order history, or Salesforce price books and Shopify price lists disagree.
It does not fit a store with no sales or service team working in Salesforce. There the connector question never arises. It also does not fit a team that wants every Shopify event copied into Salesforce, because a Salesforce org full of events nobody reads has no owner for its data volume or its storage.
Five record types break between Shopify and Salesforce
Salesforce is usually the system of record for the relationship and Shopify for the transaction. These are the places that split goes wrong.
Orders
A Shopify order has to land on a Salesforce object a rep can use, whether that is an Order with line items or an Opportunity. The break is edits after sync: an address change, a partial shipment or a cancelled line needs to update the same Salesforce record, not create a second one.
Customers and accounts
Salesforce splits a person into a Lead, a Contact and an Account, while Shopify holds a customer or a B2B company. Guest checkouts and repeat buyers with two emails create duplicates. Decide the match key and which system wins when the two disagree.
Inventory
Salesforce rarely owns stock. Reps still ask whether an item is available, so the integration shows quantity read-only from the system that owns it. Writing quantity from Salesforce back to Shopify is the pattern to avoid.
Pricing
A Salesforce price book and a Shopify price list are two sources for the same price. Pick one owner per customer segment. For B2B this means deciding whether the negotiated price lives in Salesforce and is pushed to a Shopify catalogue, or the reverse.
Returns and cases
A return starts as a Salesforce case and finishes as a Shopify refund, or the other way round. The integration has to carry the order reference both ways, so the service team sees the refund and finance sees the case.
Prebuilt connector, iPaaS or custom build for Salesforce: which one fits
Table: three ways to connect Shopify to Salesforce. Vendor statements come from the vendor pages named in each row (Vendor pages read October 2026). Salesforce and Shopify App Store listings: not measured. The fit rule is our delivery judgement.
Native connector
A connector installed from the Shopify App Store or the Salesforce AppExchange. Listing scope, object coverage and pricing: not measured.
iPaaS
Celigo's Shopify and Salesforce page says it offers prebuilt connectors and automated workflows for Shopify Salesforce integration at enterprise scale. Celigo pricing: not measured.
Custom build
A build designed against your Salesforce objects: account matching, price book sync, order updates after export, and a reconciliation job that finds records one side never received.
What we check first in a Shopify Salesforce integration
Five checks come first, and they decide which row of the table applies.
The match key
How a Shopify customer is matched to a Salesforce Contact and Account, and what happens to a guest checkout with no match.
Which objects reps use
We ask reps which Salesforce screen they look at when a customer calls, and map orders to that object rather than to the tidiest one.
The price source
Whether a price comes from a Salesforce price book, a Shopify price list or a quote, and who is allowed to change it.
Duplicates already in the org
A count of existing duplicate contacts and accounts, because an integration syncs duplicates as faithfully as it syncs clean records.
Who reads the errors
A named person sees a rejected record, the reason and the affected order. Salesforce validation rules reject records the connector never heard about.
What we run after a Shopify Salesforce integration goes live
Go-live starts the work, because an integration is a running system. We run these checks and name who acts on each.
- A daily comparison of Shopify order counts with Salesforce records, with differences listed.
- A duplicate check on new contacts and accounts, so matching drift shows early.
- An exception view for rejected records, with the validation rule that rejected them.
- A review whenever a Salesforce field, validation rule or price book changes.
- A short written note each month: what failed, what it touched and what we changed.
What we can show, and what we cannot
We have no published client result for this integration yet, so this page carries none. It lists what we check and what we run instead. What carries over from published work is naming the system of record first: on Container One, 40 depots were seeded into one pricing hub before the legacy system was retired endpoint by endpoint. Read the Container One case study.
Other systems and the wider integration scope
The integrations hub sets out how we choose between a native app, an iPaaS and a custom build for any system. Guides to the others we connect most often:
Common questions
Does Shopify integrate with Salesforce?
Yes. Shopify connects to Salesforce through connectors, iPaaS platforms and custom builds. Use a prebuilt connector when orders and contacts map to standard Salesforce objects, and build custom when B2B accounts, price books or returns need your own rules.
Should Shopify orders sync to Salesforce as Orders or Opportunities?
Sync them to the object your reps already use when a customer calls. Orders suit completed transactions with line items, and Opportunities suit B2B deals that are still being negotiated. Pick per sales motion, not per tool default.
Which system should own the customer record?
Salesforce should own the relationship and Shopify the transaction and the checkout identity. Write down which system wins when name, email or address differ, and make the other system read-only for that field.
Can Salesforce show Shopify inventory?
Yes, as a read-only view from the system that owns stock. Reps can see availability without writing quantity. Letting Salesforce write quantity back to Shopify creates two owners for one number.
What breaks when Shopify B2B accounts meet Salesforce accounts?
Names and hierarchies rarely match. A Shopify company with several locations may be one Salesforce account or several. Agree the mapping per customer, keep the Shopify company ID on the Salesforce record, and match on that ID rather than on the name.
Migration & Replatforming
Sales reps who cannot see what a customer bought cost more than the fix
Latest guides
Shopify & Ecommerce
Shopify SEO checklist: 13 checks and who owns each
A Shopify-specific SEO checklist: 13 checks from collection canonicals and variant URLs to app scripts, structured data and AI Overview readiness, each with how to check it, what good looks like and who owns it.
Shopify & Ecommerce
Shopify vs Wix: which one fits the store you run?
Wix caps a product at 1,000 variants and six options; Shopify allows 2,048 variants and three options. Wix suits service businesses and small catalogues. Shopify suits stores where inventory, wholesale or an ERP runs the business.
Shopify & Ecommerce
Shopify Plus pricing: what $2,300 a month really costs
Shopify Plus lists at $2,300 a month on a three year term, but the licence is the only line Shopify prices for you. Here is the total cost by stage, Advanced and Plus side by side, and the cases where Advanced is the better answer.
Shopify & Ecommerce
Shopify Plus examples: 10 stores and what to copy
Ten Shopify Plus stores, each confirmed as Plus on Shopify's own customer pages, read as teardown notes. For each one: what to study, why it matters, and whether you need Plus to copy it.
AI & Search
Generative engine optimization for Shopify: 5 page changes
GEO and AEO in plain words for a Shopify brand: what an AI answer needs from your product and collection pages, what we change, how you measure it, and what nobody can promise.
AI & Search
Vector database vs graph database for AI: how to choose
Compare vector and graph databases for RAG and AI applications. Choose based on retrieval questions, relationship checks, data ownership and evaluation.