Salesforce Loyalty Management is the industry product purpose-built for customer loyalty, member-tier, and reward-points programmes. The product is sold on a transaction-based pricing model rather than a per-user named-licence ladder. The Admodum read on the transaction-tier inventory, the member and points-ledger data model, the cross-cloud surface against Marketing Cloud and Data Cloud, and the buyer-side rationalisation discipline.
Loyalty Management is the Salesforce industry cloud purpose-built for the loyalty, customer-retention, and reward-programme surfaces. The product layers a native loyalty data model on top of the Salesforce platform and holds purpose-built objects for the loyalty programme, the member, the tier band, the points balance, the voucher, the promotion, and the redemption rule. The product is positioned across retail, consumer goods, travel and hospitality, financial services, automotive, and telecommunications buyers operating customer-loyalty and reward programmes at scale.
The product sits inside the wider Salesforce licensing pillar and complements the underlying CRM-edition ladder. The product is rarely the standalone purchase: the buyer typically already runs Sales Cloud or Service Cloud, and Loyalty Management is the overlay subscription that adds the points-ledger and member-tier architecture.
The Loyalty Management data model holds native objects for the Loyalty Program (the programme itself), the Loyalty Program Member (the member record), the Loyalty Member Tier (the tier band), the Loyalty Program Process (the rules engine), the Voucher (the redemption instrument), the Promotion (the time-bound reward boost), and the Transaction Journal (the points-ledger row). The model holds the closing programme-design artefact and is the principal reason a buyer reaches for Loyalty Management rather than building a custom programme inside the platform.
The points-ledger object architecture is the principal differentiator. The transaction-journal row holds the points-earning event and the points-redemption event in a single audited model, with the rules engine evaluating the entitlement at the moment of capture. The model is purpose-built for the longitudinal member-points record and removes the customisation overhead that historically sat on Sales Cloud opportunity-object repurposing patterns inside the loyalty community.
Loyalty Management is sold on a transaction-based pricing model rather than a per-user named-licence ladder. The Salesforce contract carries a contracted transaction-volume band, commonly stated as a member-population ceiling combined with an annual transaction-volume ceiling. Incremental transactions above the band are billed against an overage rate or trigger a step-up commitment at the next renewal anchor.
The published list inside the publisher's reference material carries a per-transaction unit rate; the realised closing band is contract-by-contract and reflects the contracted transaction commitment, the cross-cloud subscription footprint, and the wider commercial position. The pricing-model read is the principal architectural difference from the per-user named-licence ladders that dominate Sales Cloud, Service Cloud, and Marketing Cloud, and the architectural difference cascades into the renewal-evidence pack.
The Loyalty Management surface overlaps materially with three sibling subscriptions. Marketing Cloud tiers hold the journey-send and member-communication surface; Data Cloud credits hold the unified-profile and segment-resolution surface; Service Cloud editions hold the member-service console and case-management surface. The overlap discipline reads what each subscription pays for and where the duplication risk sits.
The Loyalty Management member record holds the points-balance and tier-band record; the Data Cloud unified profile holds the cross-channel identity record; the Marketing Cloud subscriber record holds the messaging-send record. The architectural read aligns the three records onto a single member identity and reads the licensing footprint against the consolidated identity rather than against three separate counts. The discipline materially shifts the renewal economics on the cross-cloud cluster.
The Loyalty Management renewal cycle aligns with the wider Salesforce master subscription agreement. The renewal-cycle artefact reads the contracted transaction-volume band against the realised annual transaction inventory, the cross-cloud overlap position against Marketing Cloud and Data Cloud, the BATNA architecture on the loyalty surface, and the per-transaction list-step the publisher carries against the realised closing band drawn from the firm's Benchmarking library on the loyalty cluster.
The renewal-evidence pack carries five artefacts. The contracted transaction band against the realised member and annual-transaction inventory. The points-ledger volume against the redemption rate. The cross-cloud overlap surface against Marketing Cloud, Data Cloud, and Service Cloud. The competitive-loyalty BATNA position drawn from the wider loyalty-management market. The renewal posture against the publisher's transaction list-step. The pack is the closing position transmitted to the publisher inside the Renewal Programme cycle, countersigned by a second partner.
The commitment-design discipline reads four artefacts at the buyer-side commercial level: the contracted transaction band against the realised annual transaction inventory; the cross-cloud overlap position against Marketing Cloud, Data Cloud, and Service Cloud; the renewal-cycle posture against the publisher's per-transaction list-step; the BATNA architecture on file on the loyalty surface before the pricing letter response.
The senior-advisor read produces the renewal evidence pack, the closing-band benchmark, and the BATNA letter inside the Audit Defence framework when overage triggers a counter-position. The discipline aligns the renewal commitment to the realised member and transaction inventory rather than to the Salesforce account-team's full-programme forecast on the loyalty overlay. The wider active-user audit spoke reads the discipline that produces the deployment evidence underneath the transaction tier.
The sibling industry cloud for the fundraising and programme-management surface.
The journey-send tier that overlaps with the Loyalty Management member-communication surface.
The unified-profile credit consumption that overlaps with the Loyalty member record.
A senior Admodum Salesforce advisor will read your Loyalty Management contracted transaction band, your member and annual-transaction inventory, and your cross-cloud overlap position on a private call. Active renewal moments route to Renewal Programme.
Vendor Intelligence Monthly
One monthly briefing on Salesforce pricing moves, contract precedents and negotiation windows. Written by the advisors who run the engagements. No marketing list.
Subscribe to the briefing