Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
The decision on the table is where your loyalty engine lives. Put it on Salesforce. Then every service agent, marketer and store employee works from one member record. Keep it elsewhere and you keep flexibility, but you pay for it with integrations that someone has to own for as long as the programme runs. That choice is hard to reverse once members have balances.
Loyalty Management runs the programme on your CRM records
Salesforce Loyalty Management is the product that holds the mechanics of a loyalty programme: who is a member, how many points they hold, which tier they sit in and which rewards they can claim. It stores each member against the same customer record that sales and service already use. Every accrual and every redemption lands in a transaction journal, a running ledger that shows exactly why a balance is what it is.
That shared record is the real argument for the product. A service agent handling a complaint can see that the customer is a top-tier member and offer points as a goodwill gesture, within rules you set. The wider case for Salesforce CRM as one customer record applies here in full, because loyalty becomes one more view of the same customer.
We configure and implement Sales Cloud and Service Cloud for retailers and B2B companies, loyalty programmes included. In those projects the loyalty data model is rarely the hard part. Agreeing which department owns the member record usually is.
What the platform handles out of the box
Loyalty Management covers the standard building blocks of a modern programme. You can run more than one point currency, for example qualifying points that decide the tier and reward points that customers spend. You can set tier rules, promotions with start and end dates, vouchers and partner rewards where other brands honour your points.
Where it stops is the programme design itself. The platform will run whatever earn and burn rules you give it. It will not tell you whether those rules make commercial sense, which is a separate discipline covered in our piece on designing the loyalty programme itself.
Connecting loyalty to commerce, marketing and the store
Integration effort depends on where customers earn and spend points. Service Cloud and Sales Cloud sit on the same platform, so they need configuration more than integration. B2C Commerce, part of Commerce Cloud (Agentforce Commerce), runs on its own platform. Showing a balance on the storefront or redeeming points at checkout needs an interface between the two.
The light case is a balance shown on the account page and points settled after the order ships. The heavy case is real-time redemption at checkout and at the till, across several countries, with returns reversing points correctly. The second case costs more and needs more testing. Customers notice when it fails.
