Learn · Technology and vendors

Integration basics

Integration connects your Loyalty Register to the tools you already use, such as a point of sale, ecommerce platform, or email system. When configured well, member actions in those tools create or redeem points automatically, keeping balances current without manual spreadsheets. Start with one high value connection, then add others once the first runs correctly.

How it works

Integration connects Loyalty Register to the systems that already record member activity. A point of sale, ecommerce platform, or booking tool sends each completed transaction to Loyalty Register through an application programming interface or a scheduled file import. Loyalty Register matches the member identifier, applies the earning rule, and updates the point balance in real time or near real time. For redemptions, the same flow works in reverse: the till or website asks Loyalty Register whether the member has enough points, then Loyalty Register deducts the points after the sale completes. A two way sync can also push a current balance to a till display or an email tool, but the core loop is always the same: capture an event, identify the member, apply the rule, and store the new balance. Start with one connection and one clear rule so you can verify every number before adding more.

Worked example

This worked example is illustrative arithmetic for a cafe integrating its till with Loyalty Register. In April a member spends 240 dollars and earns 5 points per dollar, so the member receives 1,200 points. In May the member redeems 1,000 points. The programme sets 200 points equal to 1 dollar of discount, so the redemption value is 5 dollars. The member's remaining balance after redemption is 200 points. The integration updates these balances automatically after each till sale and each redemption.

What to do

  1. Identify one system that holds member purchases or redemptions, such as your point of sale or online checkout.
  2. Check whether Loyalty Register has a prebuilt connector for that system. Use it before writing custom code.
  3. Map the data fields: member identifier, transaction amount, timestamp, and channel must match exactly on both sides.
  4. Configure earning and redemption rules in Loyalty Register and test with three real transactions from a test member.
  5. Switch on the integration for live traffic for one week and compare daily point totals with your till or ecommerce reports.
  6. Then add the next integration, such as email or SMS, using the same mapping and test routine.

Common mistakes

  • Connecting every system at once makes failures hard to trace, because any one broken integration hides the source of balance errors.
  • Using a member's email address as the only identifier fails when email changes, so balances split across two records.
  • Testing only a successful transaction misses failed events, such as a refund or a voided sale, which then leave incorrect balances.
  • Leaving manual imports in place after integration means staff may double count points when both processes run on the same day.

Related