the crm holds what you know about a customer: who they are, what they bought, what they were told, and what they agreed to. the shop holds the orders. connect them well and marketing can speak to the right people about the right things. connect them badly and you email a customer about an order that was just refunded.
match customers before you sync them
the first problem is identity. a shop has registered accounts and guest checkouts. a crm has contacts, often from other sources. decide the matching key, usually a normalized email address, and what happens on a mismatch: merge, link or create a new record. without a rule, you collect duplicates, and every segment built on duplicated data is wrong.
b2b adds a second layer. a company has several buyers, so decide how shop accounts map to crm accounts and contacts, and who is allowed to place orders for whom.
what flows in each direction
from the shop to the crm: new customers, orders, order values, products bought, abandoned carts if you use them. from the crm to the shop: segments for promotions, customer groups, support history where it helps. keep both lists short. every field you sync is a field you must keep correct.
as with the erp, write down which system owns each field. a customer who changes their address in the shop should not have it overwritten by an old crm record.
consent is data, and it travels
under gdpr, marketing consent must be provable and withdrawable. store the consent status together with when and where it was given and what the customer was told. then sync it in both directions: an unsubscribe in the crm or the email tool must reach the shop, and a withdrawal in the shop must reach the crm. check the rules for your markets, and have your legal adviser confirm the wording.
transactional messages, such as order confirmations, follow different rules than marketing. keep them in separate flows so an unsubscribe does not stop a shipping notification.
segments and triggers
the visible payoff is segmentation: repeat buyers, lapsed customers, high-value orders, a product category. define each segment in terms of data the crm really has, and check its freshness. a "bought in the last 30 days" segment fed by a weekly sync is not what it claims.
triggers need guard rails. a refund, a cancellation or an open support ticket should pause promotional messages to that customer. this is a small rule, and it prevents most of the embarrassing emails.
pick the crm for the team that uses it
hubspot, salesforce and sap c4c differ in cost, flexibility and who can administer them. choose for the people who will use it daily, then check that its api covers your objects, volumes and rate limits. email platforms such as klaviyo often sit next to the crm, which makes the ownership table even more important.
example tools and docs
- hubspot developer documentation ↗ - contacts, companies, deals and webhooks
- salesforce developer documentation ↗ - apis and integration guides
- klaviyo developer documentation ↗ - email and sms marketing platform with commerce integrations
- gdpr full text on eur-lex ↗ - the regulation itself, including the consent articles
- gdpr.eu guide ↗ - plain-language explainers and checklists