Shopify Salesforce integration for sales, service and B2B teams

A Shopify Salesforce integration connects your store to Salesforce's CRM, usually Sales Cloud for B2B and account teams, and Service Cloud for support. Shopify customers, companies, orders and products become Salesforce records that reps and agents can work with. Connector apps and middleware cover standard mappings. A custom integration fits when your Salesforce org is heavily customized, when you sell B2B with account hierarchies and custom pricing, or when Salesforce needs to drive actions in Shopify.

Typical data flows

• Customers → Contacts or Person Accounts, deduplicated by email.
• B2B companies and locations → Accounts, often as a parent–child hierarchy, with contacts attached.
• Orders → Orders with line items, or a custom object if your org already has an order model from an ERP.
• Products and prices → Products and Price Book Entries, when reps need to quote or report by product.
• Refunds and cancellations, so revenue reporting in Salesforce stays accurate.
• Salesforce → Shopify: account terms, rep assignment, credit status, and quotes that should become draft orders.
• Service Cloud: order and fulfillment status visible on the Case, so agents don't switch to the Shopify admin.

Off-the-shelf options

• Connector apps listed on the Shopify App Store or Salesforce AppExchange.
• Integration platforms: MuleSoft (owned by Salesforce) and other iPaaS tools such as Workato, Celigo or Boomi, with Shopify and Salesforce connectors.
• Light automation tools for simple one-way flows.

Where they break

• Customized orgs. Validation rules, required custom fields, record types and triggers in your org reject records a generic connector creates.
• Person Accounts vs Contacts. Connectors often assume one model.
• B2B hierarchies. Shopify companies with several locations and buyers, mapped to parent and child accounts with the right contact roles.
• Duplicates. Without a reliable external ID, retries and edits create duplicate records.
• API limits. Salesforce enforces daily API request limits per org. A chatty sync during a sale can use them up and affect other integrations.
• Two-way conflicts. Both systems edit the same field, and the last write wins silently.

How a custom Shopify Salesforce integration works

1. External ID fields. Create external ID fields on Salesforce objects, such as Shopify_Customer_Id__c and Shopify_Order_Id__c, and use Salesforce's upsert by external ID. A retried event updates the same record instead of creating a new one.
2. Events from Shopify: webhooks for customers, companies, orders and refunds are verified and queued. Full records are fetched through the GraphQL Admin API.
3. Batching: writes go through Salesforce's composite or bulk APIs to stay within limits during peaks, and history backfills use Shopify bulk operations on the read side.
4. Salesforce → Shopify: a platform event, Change Data Capture or a flow calls the integration when a relevant field changes. The app updates Shopify, for example a company's payment terms, a customer metafield or a new draft order for a quote.
5. Field ownership: each field has one owning system, written down. The integration never writes a field from the non-owning side.
6. Reconciliation and errors: failed records show Salesforce's validation error, and daily counts and totals are compared between the systems.

An example field mapping

A simplified mapping for a B2B-heavy org using Accounts and Contacts. Your org's custom fields and record types will change the details.

Several stores or markets

If you run more than one Shopify store, add a store field to every synced record, and make the external ID unique per store, for example by prefixing it with the store's domain. Otherwise two stores' order #1001 collide. The same applies to multi-currency: store both the shop currency amount and the presentment currency amount, and label which one reports should use.

Testing with a sandbox

Build and test against a Salesforce sandbox and a Shopify development store, never against production. A good test set includes:

• a new D2C customer, a returning customer with a changed email, and a B2B buyer at two locations;
• an order with a discount, a partial refund and a cancellation;
• an order edited after creation;
• the same webhook delivered twice, which must result in exactly one Salesforce record;
• a validation rule failure, which must appear in the error list, not disappear.

Then run a backfill of a few months of real history in the sandbox and compare totals with Shopify's reports before going live.

Decision checklist

• Sales Cloud, Service Cloud, or both? Person Accounts or Contacts?
• Which objects and custom fields must be filled, and which validation rules apply?
• Do you sell B2B with account hierarchies and custom pricing?
• What should Salesforce be able to change in Shopify?
• What is your Salesforce API limit headroom today?
• Which system owns each field?