From Online Coupon Claim to In-Store Purchase: Making Member Benefits Work at Checkout
A customer claims a coupon through the member mini-program and plans to shop in-store over the weekend. The mini-program shows that the coupon is available, but the checkout process still needs to verify the applicable stores, product scope, spending threshold, validity period, and stacking rules. Only when the POS system calculates the discount under the same campaign rules and creates a redemption record does the online benefit become part of an in-store transaction.
Brands need to manage eligibility, usage conditions, and coupon status separately. A successful claim means that the coupon has entered the customer’s member account. Whether it can be used in a specific order still depends on the products, store, and coupon status at checkout. After redemption, the coupon code, member, discount amount, and sales order should remain associated, allowing both the store and headquarters to trace the same business record.
PEKON connects CRM, WeChat mini-programs, and store POS to link member identities, online coupon claims, and in-store redemption, helping brands apply member campaigns to actual transactions.
Clear Coupon Information Creates Consistent Customer Expectations
Eligibility determines which members can receive a coupon, while usage conditions determine which purchases the coupon applies to. After claiming a coupon, members should be able to view the applicable stores, usage period, product scope, and spending threshold. This prevents customers from assuming that a claimed coupon can be applied to any order.
The campaign description should also clarify whether the threshold is based on the total order amount or the amount of eligible products, and whether the coupon can be combined with member discounts, gifts, or other promotions. When the customer-facing explanation, store rules, and system execution remain consistent, the coupon can be assessed against the same basis at checkout.
For example, a member claims a coupon offering RMB 30 off eligible skincare products when spending RMB 300 or more. The coupon is valid for seven days and can only be used at participating stores. The customer’s initial basket totals RMB 320, but only RMB 260 comes from eligible products, so the threshold has not been met. The customer then adds another eligible product priced at RMB 60. The total order value becomes RMB 380, while the eligible amount reaches RMB 320. After the RMB 30 discount, the amount payable is RMB 350. The store can explain the calculation through the product details, and the customer can decide whether to adjust the purchase.
When a brand changes the campaign scope, it should also clarify whether already-issued coupons continue to follow the original rules or whether the new rules apply from a specified time. If only the campaign page is updated while the actual coupon rules remain unchanged, stores may still calculate the discount according to the previous conditions. The effective date of each rule version and the treatment of existing coupons should be confirmed before the campaign is published.
Rule-Based Coupon Redemption Gives Store Staff a Clear Basis for Service
At checkout, the POS system first identifies the member holding the coupon and then retrieves the member’s currently available coupons. After the store staff selects a coupon, the system checks its validity, applicable stores, eligible products, spending threshold, and stacking rules before calculating the discount for the transaction. The status displayed in the mini-program only reflects the customer’s latest query. At checkout, the system must reassess the coupon using the master coupon record and the conditions of the current order.
If a coupon has expired, has already been redeemed, is being used at an ineligible store, or does not meet the spending threshold, the system should return the corresponding reason. Store staff can then explain the result based on the specific condition instead of treating every failed redemption as a system error. When the coupon is eligible, the system should associate the coupon status, discount amount, and sales order after payment succeeds to create a complete redemption record.
If payment fails or the entire order is cancelled, the coupon should not remain in a used status while the transaction remains incomplete. The system should restore the coupon to an available status according to the transaction result, or mark it as pending for further review. If the same coupon shows different statuses in the mini-program and POS, the store can use the member ID, coupon code, query time, and associated order to locate the discrepancy instead of applying a manual price adjustment and losing the original record.
The same coupon may appear in the mini-program, POS, or a sales-assistant tool. All touchpoints should read the latest valid status from the same source. The project should first determine whether the CRM, marketing platform, or another system stores the coupon master record. It should then define how repeated requests prevent duplicate redemption, how failed synchronization is retried, and how differences are reconciled according to the system architecture.
Redemption Records Help Headquarters Track Campaign Execution
After a coupon is used, the brand should be able to verify which member used which coupon, at which store and in which transaction, how much discount was granted, and when the coupon status changed. From the initial claim through after-sales processing, at least the following records should remain associated:
| Business Stage | Records to Associate |
|---|---|
| Online claim | Member identity, coupon code or coupon ID, claim time, campaign batch, and validity period |
| Checkout validation | Store, eligible products, threshold amount, stacking rules, and validation result |
| Transaction completion | Sales order number, discount amount, redemption time, and coupon status |
| Cancellation or return | Original sales order, refund details, coupon handling result, and operation records |
These records can be stored separately and linked through the member, coupon, and sales order. Stores can respond to customer inquiries, while headquarters can check whether campaign rules were actually applied to transactions.
When a return occurs after the transaction is completed, the original sales order should still be used for processing. Full-order cancellation, full returns, and partial returns may follow different coupon restoration policies, and the refund amount should be calculated according to the discount allocation in the original transaction. The brand should first define whether the coupon is returned, whether it keeps the original validity period, or whether a new coupon is issued. The system should then record the original redemption and subsequent adjustment instead of deleting the original usage record.
Claim records reflect member participation, while redemption and linked transaction records reflect actual usage. Rejection reasons indicate which condition prevented the customer from using the coupon. Headquarters can review claims and redemptions by campaign, store, and time period, then compare them with product sales and return records to assess campaign execution. The system provides operational facts, while campaign uplift still needs to be assessed against the pre-campaign baseline, eligible audience, and store coverage.
For more information about connecting member identities with store services, see Connecting the Member Center with Store Services.
PEKON Connects Members, Mini-Programs, and Store POS
PEKON CRM Member Center associates member identities, while the WeChat Mini-Program provides members with an entry point to view and claim coupons. Store POS retrieves available benefits, executes coupon redemption, and links the result to the transaction record. The three product areas support membership, coupon claims, and in-store purchases respectively, allowing the same coupon to enter the actual order through the member identity.
PEKON provides core capabilities for member identity management, coupon claims, and in-store coupon redemption. During implementation, the project should also define which system stores the coupon master record, where rules are configured, how redemption results are returned, and which information is available to headquarters and stores. Rule versions, coupon status after payment failure, coupon restoration after returns, third-party CRM interfaces, and exception reconciliation should be confirmed item by item as standard functionality, parameter configuration, interface integration, custom development, or not currently supported.