A certain brand set 'spend 500 yuan to upgrade to Silver Card' at its Taobao flagship store, while its Douyin mini-store set 'spend 400 yuan to upgrade to Silver Card.' A member who had accumulated 480 points on Taobao switched to Douyin to place an order and saw 'spend 20 more yuan to upgrade'—but on the Douyin backend, that user's points balance was 0. The order ultimately went to a competitor. What points non-recognition causes is not a customer complaint; it is silent attrition: the user has no perception of being 'downgraded,' they simply lose the motivation to place an order.
When three systems operate in silos, the chain break typically falls at one of three layers: the identity layer (the two stores fail to recognize the same person), the rules layer (earning and redemption rates are not comparable), and the settlement layer (cross-store redemption costs have no owner). Identifying which layer the breakpoint sits in saves more time than blindly rolling out a unified membership system. Below, we troubleshoot layer by layer across three nodes.
Node One: Identity Identification Layer—Is the User Actually "the Same Person"
Each platform generates user_id independently; Taobao uid and Douyin uid have no natural mapping. A same-day verifiable test: look up the same phone number in the member back-ends of Store A and Store B respectively. If the points records on both sides are entirely independent and user profiles do not cross-reference, the identity layer is broken. The minimum fix: use an encrypted phone number hash as the bridge key and create a bridge table in the membership middle platform, with fields limited to phone_hash, a_store_uid, b_store_uid, and last_sync_time. The bridge table can be run as a T+1 batch job, provided both stores capture phone numbers at order time (via SMS verification or registration entry point).
Node Two: Points Rule Mapping Layer—Earning, Spending, and Expiry Each Calculated Separately
After identity unification, the second layer of breakage is that the rules are incomparable. Store A: 1 yuan = 1 point, 100 points redeem for 5 yuan, validity 12 months; Store B: 1 yuan = 1.5 points, 100 points redeem for 8 yuan, validity 6 months. Simply adding them will be distorted; a mapping table is needed to align the three sets of parameters:
| Parameter | Store A Rules | Store B Rules | After Unified Mapping |
|---|---|---|---|
| earning rate | 1 yuan = 1 point | 1 yuan = 1.5 points | Adopt Store B's 1.5 points; Store A spending is credited at 1.5 points |
| redemption | 100 points = 5 yuan | 100 points = 8 yuan | Unified 100 points = 6 yuan (weighted median) |
| expiry | 12 months | 6 months | Unified 12 months |
| Conflict resolution priority | Store-specific pricing > unified markup rate > platform default; items with a concession exceeding 12% require written sign-off from the store manager | ||
Node Three: Settlement Attribution and Cost Accounting Layer — Who Pays for Point Redemption
Cross-store point redemption means a real profit transfer: a user earns 500 points at Store A (cost ≈ 2.5 yuan) and redeems them for an 8-yuan voucher at Store B, where Store B absorbs a 5.5-yuan concession. Accounting formula: Monthly per-store redemption cost = Σ (face value of points redeemed at that store × concession rate × number of redemption transactions). Cross-store allocation is split as: the store where points are earned covers 60% of base cost, and the store where redemption occurs covers 40% of experience cost, booked under the “Membership Marketing Expense” line item on each store's P&L so that you can determine whether post-integration operations erode single-store gross margin. A more complete framework for identifying cost inflection points is available inHow Many Stores Can One System Manage Profitably: Cost Inflection Points and a Decision Checklist for Multi-Store Management.
When It's Worth Unifying and When to Keep Systems Siloed
Two quantitative criteria help you decide in 10 minutes: when store count ≥ 4 and cross-store customer overlap rate (after phone-number deduplication) > 30%, the marginal benefit of unification—rebuy lift plus a complete tiering structure—exceeds the monthly average O&M cost of a unified system, making it worthwhile. When store count ≤ 3 and overlap rate < 15%, the maintenance cost of three independent systems is lower than migration cost, so keeping them separate saves more. In the middle range (4–6 stores, overlap 15%–30%), start with identity-layer bridging only, and evaluate rule-layer and settlement-layer consolidation quarterly before merging. For tool selection, focus on isolation depth and batch operation capability—seeRunning Five or More Stores: How to Choose Your Management Tool—Isolation, Batch Operations & Sync Capability at a Glance; after unification, sub-accounts need to be re-assigned permissions at the field level to prevent customer service from accidentally modifying inventory fields—seeMulti-Store Sub-Account Permission Setup Guide.
FAQ
How to Handle Invoicing and Tax for Cross-Platform Points Redemption?
For tax purposes, the redemption activity is classified as a "member rights transfer" and is typically not invoiced separately. However, the redeeming store must book the transfer amount under the selling-expenses account for input VAT deduction. If points can be gifted or cashed out, local tax law must be consulted to determine whether a withholding obligation is triggered. Before unifying systems, have your finance team produce a chart-of-accounts mapping sheet to lock in the accounting treatment.
A store is about to close—how should its outstanding points be settled?
Handle it using "nearest-store redemption + time-limited conversion": 30 days before closure, open a window for points to migrate to surviving stores at a 90% conversion rate (10% is allocated as closure cost). Any unmigrated balance after the notice period ends is converted to cash or store credit at 1 point = 0.05 yuan. The total settlement amount is booked under closure P&L and must not be commingled with surviving stores.
What happens to expired points already accumulated by existing members after the rules are unified?
Adopt the "higher, not lower" principle: legacy points follow the remaining validity period under the original rules, while the new rules apply only to newly earned points. If the original validity period is shorter than the unified standard, it can be extended in one go to the unified standard, but this must be publicly announced on the member-facing side once to avoid secondary complaints.
If a single store runs a standalone points-doubling promotion, will it dilute the perceived value of the overall system?
Yes, but it is manageable. Set up a separate "Promotional Points" tag, displayed independently from regular points. Upon redemption, promotional points are consumed first but cannot be transferred or gifted. The promotional points ratio at any single store must not exceed 20% of that store's total points pool for the month; any excess is automatically downgraded to regular points to prevent the system's anchored value from being skewed by a single campaign.
