Awarding points for purchases without duplicate credits

The same order can trigger several events: creation, payment, fulfilment and a connector retry. A loyalty program should award purchase points once for the qualifying order, then record later changes as separate ledger entries.

Key Metrics for Loyalty Point Accuracy

Define the award key

Use a stable order ID and program member ID, and record the earning-rule version applied. Decide whether points appear as pending at order creation or only after payment. Under LoyaltyLion's purchase rule, points stay pending for its configured approval period after an order is paid. That is a product-specific workflow, not a universal loyalty standard.

Test duplicate webhooks or imports, split payments, guest-to-member matching and a manual correction. Before issuing a missing-points credit, inspect the existing ledger for a pending award. A delayed approval is not a missing award. Keep any manual credit with a reason and operator so it can be distinguished from the automated event.

Reconcile with orders

Compare a sample of completed eligible orders with awards, and awards with source orders. Flag one-to-many matches for review. If an order is cancelled or refunded, post the appropriate reversal rather than deleting the original award. This leaves support with a traceable explanation for the customer's balance and helps prevent a second credit during a retry.