Enterprise DNA

Instead of Salesforce Loyalty Management

Stop renting Salesforce Loyalty Management. Own your loyalty programme.

We build your version around your earning rules, rewards and review process, bring across the agreed Salesforce records, reconcile the points and run it for you through Omni by Enterprise DNA.

Salesforce lists Starter at US$20,000 per organisation per month, billed annually: US$240,000 a year. Public USD list pricing, not a quote for your business.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The annual commitment

How much platform does your programme need?

Salesforce sells a broad loyalty platform. Compare that commitment with the member and reward work your team actually needs.

payments

A starting annual commitment

Starter lists at US$20,000 per organisation per month with annual billing. That is US$240,000 for a year before your separately agreed services.

trending_up

Growth is another edition

Growth lists at US$35,000 per organisation per month, billed annually. Its package includes member, reward, benefit and partner administration.

account_tree

Multiple programmes in Advanced

Advanced lists at US$45,000 per organisation per month, billed annually, with multiple-programme setup.

group

Partner features vary

The pricing comparison lists no partner management in Starter, simple partner management in Growth and advanced partner management in Advanced.

analytics

Analytics licences differ

The listed editions include one, three or five base analytics licences respectively. Check what your own management team needs.

schedule

An annual billing decision

Salesforce says Loyalty Management is billed annually. Compare your actual agreement and required connections before deciding to switch.

Your own operational base

Start with the member work that happens every week

Points

See what is available and what is expiring

Dated point lots keep the earning evidence and expiry together. Pending rewards reduce the available balance immediately.

  • check Each earning has a unique reference and evidence
  • check Earliest-expiring points are used first
  • check A cancelled request keeps the original expiry dates
  • check Review dormant members alongside their remaining points

Rewards

Give each request a clear review trail

Record the request, a separate reviewer and the evidence that the reward was fulfilled.

  • check Requests reserve points before approval
  • check A different reviewer records approval
  • check Overdue requests appear in the weekly attention list
  • check Draft reward authorisation sheets show the recorded decisions

Member care

Find missing evidence before the next review

Bring retention dates, permission evidence and open follow-ups into the same review.

  • check Flag missing retention reasons or review dates
  • check Flag promotion permissions with no supporting reference
  • check Draft member statements from current records
  • check Use your own policies for the reviews your business needs

Ownership

Bring the records across deliberately

Keep original source details and reconcile the points before operational cutover. We adapt your version to the programme you actually run.

  • check Import member exports with their original extra fields
  • check Preserve supported point-history exports for reconciliation
  • check Ask for reports combining points, reward status and your own review rules
  • check Add your fields and business rules without changing subscription edition

Make it yours

Design your own Salesforce Loyalty Management replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Loyalty Management. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Loyalty Management replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Loyalty Management data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Loyalty Program for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Loyalty Program for Claude Code

Connected to your own database

Which members have points expiring this month?

HR001

Name
Aroha Taylor
Program
Harbour Rewards
Reference
DEMO-001
Points
1200
Expires_on
2026-10-24

Ask it anything

Ten questions this version answers

These are questions the working demo answers today. Your version can use your own rules and records.

chat_bubble Which members have points expiring in the next 30 days?
chat_bubble Which inactive shoppers still hold spendable points?
chat_bubble Which reward requests are overdue?
chat_bubble What can each member spend after pending rewards are reserved?
chat_bubble Which members need a retention review?
chat_bubble Which promotion permissions lack supporting evidence?
chat_bubble Which tiers do rolling annual points suggest?
chat_bubble Who recorded or approved a reward change?
chat_bubble Which follow-ups remain open?
chat_bubble What belongs in the Monday loyalty review?

Switching

How to switch from Salesforce Loyalty Management

A move involves exporting member records and source history, mapping your fields and rules, reconciling points and rewards, then checking the new process alongside Salesforce before cutover.

  1. 1

    Export your records

    Export member records and, if available, LoyaltyMemberCurrency, LoyaltyLedger and TransactionJournal records. The member export is the starting point for the import. Keep the optional point and transaction exports as source history for reconciliation. Export what your account allows, usually CSV or Excel, and check with Salesforce Loyalty Management for the export path and available records.

  2. 2

    Load a test import

    Use the import preview first, before loading records into the new database. Provide the Salesforce programme information and review the preview results. When you are satisfied with the result, run the import without the preview. Member records come across, including extra source columns. Optional point and transaction exports are kept as source evidence, not added as spendable balances.

  3. 3

    Reconcile the results

    Check the import results for anything flagged, then compare the imported members and source history with Salesforce. Reconcile remaining point lots, expiry dates and outstanding reward commitments before using the new records operationally. A balance summary alone does not show which points were spent, reversed or expired. Confirm how each discrepancy will be handled before cutover.

  4. 4

    Run both side by side

    Keep Salesforce operating while you use the new database for a short, agreed period. Compare member records, remaining points, expiry dates, open reward requests and weekly reviews. Resolve differences before cutover. The base does not connect live to Salesforce, send member messages or deliver rewards, so account for any member experience or purchase connections separately.

  5. 5

    Switch off Salesforce

    Switch off Salesforce Loyalty Management only after you have reconciled the records and agreed the cutover. Confirm that your approved rules, member processes and any required connections are covered in the new setup. Loyalty Program covers loyalty back-office records and review paperwork, not the full Salesforce member experience or purchase connections. Stop using Salesforce for the functions you have moved.

construction

Where the real effort goes

The real work is usually mapping your fields and rules to the new records, then deciding which history to bring and reconciling points, expiries and outstanding rewards. The free base keeps imported point history as source evidence rather than spendable balances. Enterprise DNA handles the mapping and setup when you have them install and run your version.

Not ready for a call?

Get your Salesforce Loyalty Management switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Loyalty Management, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and operates your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional member records
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Preview your Salesforce export, then reconcile points before cutover
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your point rules, rewards and review policy
  • check Your Salesforce member records and reconciled point history
  • check A web front end and agreed connections where your business needs them
  • check A different technical foundation if that suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your member records alongside the rest of your business
  • check Agreed purchase and reward connections built into your version
  • check Ongoing changes, backups and operational support
Talk about your programme

Questions

Instead of Salesforce Loyalty Management, answered

Are you replacing everything Salesforce does? expand_more

We start with the loyalty back office: members, dated points, reward requests and review paperwork. Your member experience, purchase connections, partner rules and other requirements shape the custom version. We agree that scope before you switch.

Will our existing points carry across correctly? expand_more

Member records and supported source history come across through the import. A balance summary does not show which points were spent, reversed or expired. We reconcile remaining points, dates and outstanding rewards before putting your version into operation. The free version preserves source balances for review and does not treat them as new earnings.

Can we use our own reward and tier rules? expand_more

Yes. The free base uses dated, whole-number points and suggested tiers from annual earning totals. We build your version around your approved rules, including the fields, evidence and reports your operator needs.

Does it contact members or deliver rewards automatically? expand_more

The free base prepares drafts and records decisions. It sends nothing and does not deliver rewards. We scope any member screens and approved external connections as part of your version, with the review process you require.

What will Enterprise DNA charge? expand_more

One setup fee, then a retainer, agreed around the records, rules, connections and operating support you need. The free base has an MIT licence. Hosting and coding-assistant usage have separate costs. Bring your current agreement to the call so we can compare the full scope.

Make the loyalty system fit your programme

Book 30 minutes with Sam. Bring your Salesforce agreement, a sample member export and the reward rules your team uses. We will map the records, the points reconciliation and what your own version needs to do.

Loyalty Program for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Loyalty Management?

Get your version built