How to Configure Member Marketing? Differences Between Points, Stored Value, Visit Cards, and Gift Cards

Select benefits based on store service models

High-frequency retailers may start with points and coupons; fixed-visit services suit per-visit redemption; gift cards fit gifting-based consumption. More features aren’t always better—first ensure staff can clearly explain offerings and customers understand available benefits before expanding entitlements.

Specify discount stacking rules

Tiered discounts, coupons, point deductions, and promotional prices may coexist. Clarify application order, mutual exclusions, inclusion of sale items, and benefit restoration after refunds. Test with an order meeting multiple conditions; retain calculation results and explanations.

Balances and visit counts require complete recording

Stored value top-ups, gift card issuance, multi-use card redemptions, and refunds require corresponding consumption records. For partial refunds, verify handling of cash, balance, points, and discounts. AllinWebPOS organizes members, card benefits, and reports so merchants can configure rules by service method, ensuring front-end operations and back-end reconciliation share consistent references.

Cross-store and Cross-platform Agreements Should Be Defined Separately

Sharing members between stores does not mean all benefits are cross-store usable. Third-party marketplaces may use separate identity and points systems; confirm identity merging, privacy authorization, and historical data migration plans. For prepaid consumption, verify validity periods and refund policies per local regulations.

Verify benefit rules using a partial refund example

Assume a member uses stored value and a coupon to purchase two items, then returns one. The store must explain: how the discount was allocated across items, which payment source the refund returns to, whether earned points are reclaimed, and whether the coupon becomes reusable. If payment also includes a gift card, these rules must extend to cover card balances and refund records.

These are business examples only and cannot be directly applied to all stores. Document agreed-upon outcomes, then verify against system configurations and specific deployment versions to ensure consistent customer explanations.

Session cards should not be checked solely by remaining sessions

Also verify applicable services, multi-user allowance, validity period, redemption stores, and cancellation methods. A single erroneous redemption should allow tracing related records, rechecking remaining uses after authorized processing. If service booking and redemption are separate, clarify when usage counts are consumed and whether cancellations restore them.

When using multi-use cards, configure entitlements by service type, usage count, validity period, and applicable stores. Combine purchase, usage, cancellation, and refund processes to establish clear rules understandable by both customers and staff.

Separate membership identity from benefit scope

Same phone number may map to different member profiles across systems or contain historical duplicates. Merging requires identity, balance, and benefit verification—not automatic overwrite by number. For cross-store benefit use, specify which store handles fulfillment and refunds.

For Third-Party Marketplaces, First Confirm Customer Identification, Authorization, and Data Migration Scope, Then Discuss Points or Balance Interoperability. Planning Identity Management and Benefit Rules Together Helps Customers Receive Consistent Service Across Channels.

Four types of benefits: purposes and verification focus

Deployment Checklist

• Each benefit has clearly defined usage scope
• Discount sequence and mutual exclusion rules are explainable
• Post-refund Balance, Visits, and Points Can Be Verified
• Separate Identity Verification for Cross-store and Cross-platform Access