Partner
Salesforce ecommerce integration that puts every web order in Salesforce CRM.
Salesforce ecommerce integration should mean your sales, service, and marketing teams see every web order, account, and consent choice in Salesforce, without exports or retyping. IWD connects Magento, Adobe Commerce, Shopify, and BigCommerce stores to Sales Cloud, Service Cloud, and Marketing Cloud, whether you need a Magento Salesforce integration for B2B accounts or a Shopify store that has outgrown its connector app.
You’ll know every name on your project.
- 175+ years of combined ecommerce experience.
- Senior developers & designers, dedicated PM & CXM.
- Over a decade together for most of us. Average tenure is nine years.
- 15 people. Lean mean machine.
Joe M.Founder & CEO
Max D.CTO
Marcos A.Senior Project Manager
Yaro P.Lead Full-Stack Developer
Bohdan B.Senior Frontend Developer
Signs your storefront and Salesforce CRM are out of sync.
Salesforce is where your teams decide who to call, what to send, and how to help. When the store does not feed it, people fill the gap with exports, spreadsheets, and guesswork. These are the symptoms we hear on almost every first call.
Sales reps cannot see what accounts buy online
Web orders stay in the storefront admin, so the rep who owns the account walks into a renewal call without knowing what the customer ordered last week or what they stopped buying.
Duplicate contacts pile up after every import
Customer exports are uploaded to Salesforce by hand, guest buyers turn into new contacts each time they check out, and nobody trusts the account list anymore.
Service agents work across three screens
A customer calls about an order, so the agent looks it up in the store admin, opens the case in Salesforce, and emails the warehouse, because order history never reached the CRM.
Marketing Cloud sends to the wrong people
Consent and preferences change on the website but not in Marketing Cloud, so unsubscribed customers still get campaigns and buyers who just ordered get the reminder email anyway.
A connector app that stopped covering the business
An app synced customers and orders when the store launched. Since then you added B2B accounts, custom fields, and a second storefront, and the sync quietly skips all three.
Sales Cloud, Service Cloud, and Marketing Cloud each need different store data.
Most companies run more than one Salesforce cloud, and each one asks something different of the storefront. We start every Salesforce ecommerce integration by confirming which clouds and edition you use and where your custom objects and fields live.
Sales Cloud
Sales Cloud is where accounts, contacts, and opportunities live. We map storefront customers and B2B companies to Salesforce accounts and contacts, write web orders and order lines to Orders or the object your team already reports on, and sync products and price books where reps quote from Salesforce.
Service Cloud
Agents need the customer's account, order history, and shipment status in front of them when a case opens. We bring order data into Salesforce and connect storefront contact and service forms to cases, including Salesforce web-to-case forms that turn a request on your site into a case.
Marketing Cloud
Marketing Cloud runs on subscriber status, consent, and purchase data. We sync customers, orders, and preference changes so journeys and segments work from current data, the way Penn State Extension's subscriber preference center feeds Marketing Cloud opt-ins.
This page covers connecting a storefront to Salesforce CRM. If your storefront itself runs on Salesforce B2C Commerce or B2B Commerce, see our Salesforce Commerce Cloud development services instead.
Magento, Adobe Commerce, Shopify, and BigCommerce Salesforce integration, platform by platform.
The same Salesforce org behaves differently behind each storefront. Here is where the work sits on each platform, and where to read more about the platform side.
Magento Salesforce integration
Magento Open Source gives you full control over how customers, orders, and products reach Salesforce, through custom modules and a queued sync that survives reindexes, upgrades, and peak traffic. For a Fortune 500 equipment manufacturer's Magento Commerce parts store, we built a Salesforce CRM integration covering customer brand, guest checkout, and account-name sync, plus a Salesforce web-to-case form for service requests.
Adobe Commerce Salesforce integration
We migrated Penn State Extension from Magento 1 to Adobe Commerce and built a bidirectional sync of customers, orders, and products into Salesforce Sales Cloud and Marketing Cloud. Penn State single sign-on and social login sit in front of it, Open edX course and webinar handling runs alongside, and the Salesforce connection makes the learner profile a single source of truth.
Shopify Salesforce integration
Both the Shopify App Store and Salesforce AppExchange list connector apps that sync Shopify customers and orders into Salesforce, and for one store with standard records an app is often enough. Custom work makes sense when Shopify Plus B2B companies have to land as Salesforce accounts, when several stores feed one org, or when the sync has to follow custom objects the app does not map.
BigCommerce Salesforce integration
BigCommerce stores often start with a pre-built connector or an integration platform. We step in when B2B Edition companies, customer groups, and price lists have to line up with Salesforce accounts, or when Multi-Storefront orders need to land on the right account and brand inside one Salesforce org.
Connecting an ERP to the same store? Our ERP integration services team designs the ERP and Salesforce connections together, so every customer and order record has exactly one owner.
Salesforce integration work from a team with the reviews to back it.
Adobe Solution Partner
Shopify Plus Partner
BigCommerce Elite Partner
Salesforce Partner
Klaviyo Partner
The store data your Salesforce org needs to see each customer.
Every project starts from the same list and then follows your org. Each record gets an owner, a direction, a timing, and a duplicate rule before anything is built.
Accounts and contacts
Storefront customers mapped to Salesforce person accounts, or to business accounts with contacts, using external IDs so every sync updates the right record instead of creating a duplicate.
B2B companies and buyers
Company accounts, buyers, roles, and ship-to addresses from Adobe Commerce B2B, Shopify Plus B2B, or BigCommerce B2B Edition mapped to Salesforce accounts and contacts, so reps see every buyer under the right company.
Orders and order lines
Web orders written to Salesforce with totals, products, status, and sales channel, so pipeline and revenue reports include what customers buy online, not only what reps close.
Products and price books
Products and price books synced where reps quote or build orders in Salesforce, so the catalog in the CRM matches the catalog on the store.
Cases and service requests
Contact, returns, and service forms that create Salesforce cases with the customer and order attached, including web-to-case forms for service requests.
Marketing consent and preferences
Newsletter sign-ups, opt-outs, and communication preferences synced with Marketing Cloud, so the store and your campaigns agree on who can be emailed and about what.
Selling to companies online? Our Shopify Plus B2B services and B2B ecommerce development teams design company accounts and buyer roles with your Salesforce account model in mind from the start.
Connector app or custom Salesforce integration? Let your data model decide.
Connector apps cover standard customers and orders well. Custom work earns its place when your Salesforce org has its own account model, custom objects, or flows that cross several clouds.
| Connector app | Custom Salesforce integration | |
|---|---|---|
| Best for | One store, standard customers and orders, and a Salesforce org with few custom objects | B2B accounts, several stores or brands, custom objects, and flows across Sales, Service, and Marketing Cloud |
| Data model | The app's own mapping of customers, orders, and products | Your account, contact, order, and case model, including person accounts and custom objects |
| Duplicates | Whatever matching the app supports | External IDs and matching rules agreed with your Salesforce admin |
| API usage | Set by the app's sync schedule | Batching, the Bulk API, and queues sized to your org's API limits |
| Who maintains it | The app vendor, plus your configuration | IWD under a support plan, or your own team with our documentation |
| From our work | We recommend one on the first call when your records fit it | The bidirectional Sales Cloud and Marketing Cloud sync behind Penn State Extension |
Many projects use both: a connector app for the standard records and custom code for the rules your Salesforce org depends on.
Stores where customer data has to line up across systems.
Penn State Extension's Sales Cloud and Marketing Cloud sync on Adobe Commerce, enterprise Magento parts commerce for a Fortune 500 equipment OEM, and ADTRAN's B2B Magento Commerce store with real-time EDI into the ERP.
Penn State
A multi-store Adobe Commerce build for Penn State Extension, serving learners across 67 counties.
Fortune 500 OEM
Enterprise Magento parts commerce for a Fortune 500 equipment OEM: predictive search, serialized catalog, warranties, checkout and B2B groups.
ADTRAN
A B2B Magento Commerce store with gated pricing, configurable software subscriptions, and real-time EDI into the ERP.
A Salesforce integration partner that stays after launch.
Same senior team from kickoff to launch and beyond. We do not outsource, we do not disappear after go-live, and we do not hand you off.
Across every phase. Discovery, build, launch, and growth, the same senior team stays with you.
Our job is to get you promoted.
You're going to love coming to work. Think of us as an extension of your team, here whenever you need us. Our mission is simple: your store wins, and so do you.
One team for the storefront and the Salesforce connection.
Most CRM integration problems sit between two vendors: the agency that built the store and the partner that runs Salesforce. IWD builds the storefront and the integration and works alongside your Salesforce admin or partner, so one team is accountable for a customer record getting from checkout to the right account.
Salesforce integrations we have built
Penn State Extension's bidirectional Sales Cloud and Marketing Cloud sync, documented in a public case study, and a Salesforce CRM integration with web-to-case for a Fortune 500 equipment manufacturer's Magento Commerce parts store.
B2B accounts mapped properly
Company accounts, buyers, and ship-to addresses are the hard part of a B2B CRM integration and the core of our B2B practice.
Identity, consent, and the CRM together
Single sign-on, social login, and marketing preferences designed alongside the Salesforce sync, as we built for Penn State Extension.
Honest scoping
If a connector app covers your records, we recommend it. Custom work is for the rules that need it.
A Salesforce integration mapped with your admin before anything is built.
Account models, duplicate rules, and automation differ in every Salesforce org. Agreeing on them first is what keeps the integration quiet after launch.
Assess
A 30-minute call on your storefront, your Salesforce clouds and edition, and what has to sync. If a connector app fits, we tell you and point you to it.
Map
We document which system owns accounts, contacts, orders, and consent, how duplicates are matched, and what happens on errors, with your Salesforce admin or partner.
Build and test
We build the storefront modules, middleware, or Salesforce-side flows, then test with real accounts, guest orders, B2B buyers, and service requests in a Salesforce sandbox.
Go live and support
We switch on live sync, watch API usage and error logs through the first weeks, and support the integration as your org, your store, and your campaigns change.
What teams ask before connecting their store to Salesforce CRM.
The questions we hear most on the first call. If yours isn't here, just ask.
What data syncs between our store and Salesforce?
Typically accounts and contacts, B2B companies and buyers, orders and order lines, products and price books, service cases, and marketing consent and preferences. We agree on the list, the direction, and the timing for each record during mapping, so Salesforce gets the data your sales, service, and marketing teams actually use.
Is this the same as Salesforce Commerce Cloud?
No. Salesforce Commerce Cloud is a storefront platform. Salesforce ecommerce integration, as we use the term here, connects a Magento, Adobe Commerce, Shopify, or BigCommerce store to Salesforce CRM: Sales Cloud, Service Cloud, and Marketing Cloud. If your storefront runs on Commerce Cloud, our Salesforce Commerce Cloud development team handles that work.
Should we use a connector app or a custom Salesforce integration?
Use a connector app when you run one store with standard customers and orders and your Salesforce org has few custom objects. Choose custom work when B2B accounts, several stores or brands, custom objects, service cases, or Marketing Cloud consent have to follow your own rules. Many projects combine both, and we will tell you on the first call if an app is enough.
Can you build a Salesforce Magento integration for B2B accounts?
Yes. Adobe Commerce B2B company accounts, or the customer groups and account structures on Magento Open Source, can map to Salesforce accounts and contacts with orders attached to the right account. For a Fortune 500 equipment manufacturer's Magento Commerce parts store, we built a Salesforce CRM integration covering customer brand, guest checkout, and account-name sync, plus a web-to-case form for service requests.
Can Marketing Cloud use our ecommerce data?
Yes. We sync customers, orders, and preference changes so Marketing Cloud segments and journeys run on current purchase and consent data. For Penn State Extension we built a bidirectional sync into Sales Cloud and Marketing Cloud, with a subscriber preference center that feeds Marketing Cloud opt-ins.
Can customers sign in once across the store and our other systems?
Yes. Single sign-on lets customers use one identity across the store and your other systems, with the Salesforce sync keeping the profile behind it current. Penn State Extension's Adobe Commerce platform uses Penn State single sign-on and social login, and the Salesforce connection makes the learner profile a single source of truth.
How do you keep the integration within Salesforce API limits?
Salesforce sets API request limits for each org based on its edition and licenses. We batch high-volume records, use the Bulk API for large loads, queue changes during peak traffic, and monitor usage so the integration never crowds out the other tools that call your org.
Do you support the integration after launch?
Yes. New fields, new Salesforce automation, new stores, and new campaigns all touch the integration. We provide ongoing monitoring and support alongside the rest of your store, and coordinate changes in the org with your Salesforce admin or partner.
Tell us which Salesforce clouds you run and what your team still copies by hand.
Send us your storefront platform, the Salesforce clouds you use, and the customer data your team moves between systems today. We will come back within one business day with an honest read on the right approach.