Eshop integration with Salesforce CRM: workflows, prerequisites and testing

Integrate the store with Salesforce CRM around a defined workflow and the installation's available interface. Salesforce integration turns a store purchase or enquiry into useful sales-team information. Mapping covers account, contact, lead where required, external customer ID and selected commercial events.

Salesforce integration turns a store purchase or enquiry into useful sales-team information. Mapping covers account, contact, lead where required, external customer ID and selected commercial events. Decide when to create a contact and when to update an existing company. Email alone is not always a sufficient matching key. We recommend a limited field set and a clear use purpose so that payment details or unnecessary information are not transmitted to CRM.

API access is included in Enterprise, Performance, Unlimited, and Developer editions, while Professional may require an add-on. The user also needs API Enabled permission. Salesforce recommends an isolated development and testing environment. CRM does not replace ERP inventory control. The integration focuses on accounts, contacts, leads, and commercial activities under an appropriate personal-data policy.

A services business receives a purchase from a professional already associated with a corporate account. A second purchase uses a slightly different company spelling. The connector uses the agreed matching rule and updates the existing relationship instead of creating another company. Sales sees the selected purchase event and order reference, not the entire technical checkout payload. A quotation enquiry from a new visitor follows a distinct lead workflow and is not presented as a completed sale.

An important failure scenario occurs when the same customer makes another purchase using a different spelling of the company name. Keep the external reference and confirmed destination ID before retrying. Separate access failure, business rejection and an unknown outcome. An operator must be able to inspect the relevant record and resolve its status without replaying completed steps. Agree which fields may appear in logs and who handles unresolved cases.

Test a second purchase without a duplicate contact, restricted permissions, and disallowed-field checks. For each case record the expected source data, destination record and customer-visible state. Include one denied-permission case and one interrupted response. Re-run a previously confirmed event and check that its business effect is unchanged. The acceptance record should identify the responsible team and the evidence required to close any discrepancy.

The initial discovery should confirm: API-enabled edition and API Enabled user; Restricted integration identity and sandbox; Account/contact matching and personal-data rules. Before launch, document the mapping for Checkout/contact → identity matching → Agreed fields → CRM account/contact → Purchase or enquiry → sales-team activity. Assign responsibility for access renewal, monitoring and correction. A change to product configuration or the agreed business rule should trigger targeted regression checks. Begin with this defined workflow; add another channel only after its ownership and acceptance cases are clear.