Salesforce and Adobe Commerce (Magento) integration

Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.

Both waysSalesforce and Adobe Commerce (Magento)

What moves between them

  • Into SalesforceCustomer emails, billing contacts and IDs checked against Salesforce every hour, with mismatches recorded instead of silently overwritten.
  • Into SalesforceOrders and catalogue data for account reporting.
  • Out of SalesforceNew customers and companies created on the storefront when a deal closes, with the Salesforce ID stored on the commerce record.

How we build it

  • One ID, stored on both sidesThe storefront keeps the Salesforce account ID and Salesforce keeps the store’s customer ID, so matching never depends on names.
  • Read-only inbound accessThe hourly check uses read-only tokens and writes only the fields it owns, so it cannot set off other automation.
  • A switch on every writeA routing table decides per operation whether Salesforce writes to the store, and sandboxes default to off.
  • Drift records, not silent fixesIdentity mismatches become records an owner reviews, because an automatic fix can merge two customers into one.

What goes wrong, and the fix

Problems we have found and fixed in production.

  • Sandboxes create real customers in the live storeA sandbox copies the endpoint and credentials, so testing writes to production. Writes switched off by default in every sandbox.
  • Two customers share one IDA mislabelled record on either side. The hourly check flags the mismatch within the hour and an owner decides.
  • The same accounts are sent to the store again and againThe ID returned by the store never saved, so every update looks new. Fix the writeback, then backfill the missing IDs.

Questions

Can both systems be the source of truth?

Each field has one owner. Pricing and catalogue usually belong to commerce, and account ownership and contract terms to Salesforce. We write the field list down and the sync follows it.

Does this work with Magento Open Source?

Yes. The same REST API is used, and the design does not depend on the Adobe Commerce edition.

Other Salesforce integrations

  • Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
  • Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
  • Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
  • Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
  • Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
  • Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.

Talk to us about Salesforce and Adobe Commerce (Magento).

Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.

[email protected]