Unifying customer identity across channels
The foundation is knowing who the customer is. Match records from the store, e-commerce, loyalty, and service systems using email, phone, and account identifiers, and decide the rules for merging them. Respect consent preferences from the start: record what each person agreed to and apply it across channels. Data quality work is less exciting than campaigns but determines whether any personalization works.
A unified profile also reduces cost, since duplicates inflate mailing lists and distort metrics such as repeat purchase rate.
Data 360 for unified profiles →Service that knows the order history
Service agents need purchase history, order status, and past issues in front of them. Connect the commerce platform so an agent can see what was bought, delivered, and returned, and can act on it within policy. Define service levels by channel and issue type, and use knowledge articles to answer common questions consistently. Reporting on contact reasons shows which products or processes cause the most friction.
- Order and return data visible in the case.
- Policy-driven refund and replacement actions.
- Contact-reason reporting fed back to merchandising and operations.
Loyalty, campaigns and personalization
Loyalty programs reward repeat purchases, but they only work when points, tiers, and offers are consistent across channels. Decide where the program runs and how redemptions are recorded. For campaigns, segment by behavior, value, and preference rather than blasting a list, and measure results against a holdout group where possible. Frequency limits protect customers from over-contact, which is a common cause of unsubscribes.
Wholesale and partner accounts
Many consumer brands also sell to retailers and distributors. Wholesale accounts need a different approach from consumers: account teams, pre-season orders, trade promotions, and sell-through reporting. Keep wholesale accounts distinct from consumer profiles but connected where useful, and give account managers visibility into orders and performance from the ERP. Separate the two motions so each is measured on the right metrics.
Salesforce for wholesale distributors →Stores, clienteling and field teams
Store associates and field representatives can use mobile tools to see customer preferences, record visits, and follow up. Clienteling for high-value customers, such as remembering sizes and past purchases, builds loyalty in a way mass marketing cannot. Field merchandising teams can log store conditions and compliance with displays. Keep mobile screens simple, since staff have little time during shifts.
Field service and mobile tools →Measuring what matters
Agree a small set of measures: customer lifetime value, repeat purchase rate, contact rate per order, resolution time, and campaign contribution. Build dashboards from the unified data and review them in regular business meetings. Avoid vanity metrics that cannot be tied to decisions, and be honest about attribution limits when customers touch several channels before buying.
Decisions to settle before configuration starts
- Identity rules. Decide how records are matched and merged across channels.
- Consent model. Define how preferences are stored and respected, with legal review.
- System boundaries. Confirm commerce and inventory systems remain systems of record.
- Wholesale separation. Decide how consumer and wholesale accounts are modeled.
A realistic first 90 days
- Days 1 to 30. Audit customer data sources, define identity and consent rules, and choose the first use case.
- Days 31 to 60. Connect the commerce platform, build the unified profile, and configure service views.
- Days 61 to 90. Launch segmented campaigns with measurement, train service and store teams, and review results.
Pitfalls in retail projects
- Skipping data quality. Personalization on duplicate records embarrasses the brand.
- Over-contacting customers. Set frequency limits and honor preferences.
- Too many use cases at once. Start with one that proves value.
- Ignoring store staff. Tools that slow associates will not be used.
