Skip to content
GrowmoonGrowmoon
WhatsApp LinkedIn

Loyalty programme worksheet: compare custom, integration and SaaS

Use one purchase, one refund and one redemption to compare a packaged loyalty platform, an engine integration and a custom build. The same examples make it easier to see which rules each option supports and what your team will need to operate.

Illustration: a glowing loyalty card above a balance scale with stacks of reward coins on each side

The examples are illustrative. Confirm the scope and permissions for your project.

An existing service may cover the required programme. A custom member interface may also use a third-party loyalty engine. Separate the interface, points authority and connected commerce systems in each proposal so the buyer can see where a requirement is satisfied.

Set the rules for earning and spending points

Decide what earns points, what is excluded and how to round the result. Consider tax, discounts, shipping and tips separately where they affect eligibility. Identify the event that earns the points and the system that supplies the purchase ID.

Vendor behavior can vary by configuration and account. For example, Square's Loyalty API documentation describes country-dependent default tax treatment, permissions and limits on editing programme settings through the API. Check the selected system's current behavior rather than assuming that a custom app can change every engine rule. Square Loyalty API

Use one row per rule:

Turn the programme into explicit rules
RuleDecision to write downPerson who approves it
EarnEligible amount, timing and roundingProgramme owner
RefundFull/partial reversal and prior redemptionProgramme owner with finance counterpart
ExpiryClock, timezone and treatment of old balancesProgramme owner
RedemptionReservation, confirmation and failure behaviorProgramme and commerce owners
AdjustmentWho may change points and what is recordedOperations owner

Keep the app's display rule and the authoritative points rule aligned. Decide how the member sees a delayed or disputed balance.

Test a purchase, refund and redemption

The following invented rule earns one point per eligible currency unit and reverses points for a partial refund. It assumes an opening balance of zero, whole-unit amounts and no previous redemption. It is a worksheet to discuss, not a tested implementation or a recommended financial policy.

Walk through a fictional ledger before commissioning screens
StepFictional inputExpected balance under this example
Eligible purchase P-00180 units80 points
Repeat of P-001Same purchase reference80 points
Partial refund F-001 linked to P-00120 eligible units60 points
Failed redemption attempt D-001Confirmation fails60 points under the agreed example rule

Now change one condition. What happens if points were already spent before the refund? What if the same purchase arrives through both POS and online channels? Record the chosen policy, the authoritative reference and the expected member message. A proposal should identify any case it leaves unsupported.

Expiry deserves its own example with fixed timestamps. Decide whether the clock follows each earning event or member activity, and identify the relevant timezone. Ask how a rule change affects existing balances and what record explains that change to support staff.

Compare the same rules across delivery options

For SaaS, check whether configuration and exports satisfy the required rules. For engine integration, identify the APIs, permissions and events available to the proposed application. For a custom engine, ask who accepts the ledger behavior and maintains it after changes to connected systems.

Compare setup and ongoing cost units separately. Include each participating location, integration, message channel and support responsibility where applicable. Obtain current provider terms for the actual account; avoid treating a headline plan as a complete project quote.

For buyers operating in the United States, United Kingdom and Australia, use a market row for the applicable account configuration, currency, customer communications and support hours. Validate these against the concrete programme instead of cloning assumptions across countries.

Check which records your team can inspect

Acceptance evidence should identify the rule version and show the expected and actual result for the selected cases. Ask for member-balance history, linked corrections and attributable administrator actions. Set a process for resolving a disagreement between the member app and the commerce system.

Bring the rule table, fictional ledger and POS/system inventory to a loyalty app development scope discussion. Use them to decide whether configuration, integration or a custom build has a justified role in the first release.