E-commerce
July 1, 2026
"My store loyalty card shows 120 points, my online account 80." "I lost my physical card, how do I recover my balance?" "The card number doesn't work at checkout." Three tickets where a poorly synchronized loyalty card weakens omnichannel trust.
The physical/digital loyalty card support covers inconsistent balance, account linking, loss/theft replacement, wallet pass, and POS sync delay. Distinct from the general loyalty program (#375 bot): here, physical/digital card identifier and store-online synchronization.
This guide #587 covers policy LCARD-SUP, flow LC-1 to LC-8, and matrix LCARD-MAP. First loyalty card support content. Future support pair LCARD bot (#588).
Summary
Why do loyalty cards generate receipts?
A loyalty card exists in three forms: physical in-store plastic, digital online account, and mobile wallet pass. The customer expects a single, unified balance. When POS and online balances diverge, the card is lost, or the number is rejected at checkout, the ticket becomes urgent.
Five Typical Friction Points
Inconsistent Balance: In-store vs. online account balance
Unlinked Card: Physical plastic card without an associated Shopify account
Loss or Theft: Card replacement without losing accumulated points
Invalid Number: Expired card or typo during checkout
Delayed Sync: Store purchase points not reflecting online
Antavo points out that 42% of omnichannel programs report physical-digital card sync issues as the primary cause of loyalty churn (Antavo, 2026 Loyalty Report). Without LCARD-MAP, agents often merge accounts manually or promise balances without verifying the POS system.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
LCARD #587 vs points #374, loyalty bot #375, MEMSALE #583 and bot #588
Five contents, five distinct loyalty layers.
Quick matrix
#587 LCARD: digital physical card balance link sync
#374 Points: PTS-REC investigation missing points incident
#375 Loyalty Bot: common redemption balance program rules
Loyalty Questions: pre-launch go-live FAQ
#588 LCARDbot: bot loss number balance sync
#374 = post-purchase points incident. #587 = card identifier and online store omnichannel sync.
Which lcard_* typologies should be classified?
Eight loyalty card ticket scenarios.
Eight lcard typologies
lcard_balance_mismatch: POS balance differs from online account
lcard_not_linked: plastic card without digital account
lcard_lost_stolen: loss theft blocking replacement
lcard_number_invalid: card number rejects lookup checkout
lcard_duplicate_account: two accounts same customer merger
lcard_wallet_pass: Apple Google wallet pass does not work
lcard_replacement: request for new physical card
lcard_sync_delay: store purchase missing points sync delay
Tags: lcard, loyalty_card, omnichannel_sync. LCARD-MAP-GROUNDED: sync balance replacement from map only.
How to structure the LCARD-MAP matrix?
The LCARD-MAP matrix documents the card program for agents and future bot #588.
LCARD-MAP Columns
program_id: Smile Yotpo POS program identifier
card_types: physical digital wallet pass
lookup_methods: email card_number phone barcode
sync_rules: POS online delay hours batch
merge_account_policy: duplicate accounts merge procedure
replacement_policy: loss theft replacement fees delay
wallet_pass_provider: Apple Google PassKit config
escalation_ops: ops contact POS sync balance dispute
Sync Smile Yotpo, POS export, Shopify customer metafield card_number and helpdesk macros. Audit: sync_rules communicated to agents and customer FAQ.
LCARD-SUP policy in six rules
Six loyalty card support rules.
LCARD-MAP-GROUNDED: sync replacement merge from map only
BALANCE-VERIFY-BOTH: lookup POS and online before adjust
NO-MERGE-WITHOUT-VERIFY: account merging according to merge_account_policy map
SYNC-DELAY-CITE: cite sync_rules map before blaming client
LOST-BLOCK-FIRST: block lost card before replacement issue
POINTS-ESCALATE: missing points post-verify → #374 PTS-REC
LCARD flow LC-1 to LC-8
Eight-step loyalty card agent flow.
LC-1 Intake: lcard_* intent + email card_number order_ref
LC-2 Card lookup: LCARD-MAP program lookup methods
LC-3 Balance verify: POS API online Smile Yotpo both
LC-4 Classify: mismatch link lost invalid duplicate wallet
LC-5 Sync check: sync_rules delay batch status
LC-6 Respond: macro LCARD grounded map
LC-7 Execute: merge link block replace escalate ops
LC-8 Close: tag lcard_resolved program_id
SLA: lcard_sync_delay explained with sync_rules map in a single interaction if within normal delay.
Essential LCARD macros
Four macro agents.
LCARD-BAL-01
"Card [card_number] [email]: online balance [points_online] / POS [points_pos map]. [If discrepancy: cause [sync_delay / duplicate account / transaction pending].] [If within sync_rules timeframe: points visible within [sync_hours] h.] [If dispute: escalated to ops [escalation_ops].]"
LCARD-LINK-01
"Card [card_number] linked to account [email]: [linked / not linked]. [If not: procedure [merge_account_policy map] link [account_url].] [If duplicate: merge according to ops map.]"
LCARD-LOST-01
"Card [card_number] reported [lost / stolen]. Blocked. Replacement: [replacement_policy map fees timeline]. Balance [points] kept on account [email]. New card: [delivery_timeline]."
LCARD-WALLET-01
"Wallet pass [Apple / Google]: [active / expired / not issued status]. [If failed: regenerate via [wallet_url map].] Displayed balance sync [sync_rules]. Physical card [card_number] linked [yes / no]."
Edge cases: point incident, gift card, BOPIS and MEMSALE
Five cases outside the standard macro card.
Confirmed missing points: PTS-REC #374 investigation adjust
Gift card balance: gift card distinct programme points
Store purchase BOPIS: Click Collect #177 channel attribution
Tier member sale: MEMSALE #583 distinct card tier status
General programme rules: loyalty bot #375 redemption
Gift card balance euros ≠ loyalty card points. Reroute if customer is confused.
Essential lcard KPIs
Five LCARD monitoring metrics.
lcard_ticket_rate: lcard_* tickets / active card members
lcard_sync_success_rate: sync delay resolved without escalate
lcard_link_success_rate: linked cards / lcard_not_linked tickets
lcard_balance_dispute_rate: balance disputes / total lcard tickets
lcard_replacement_sla: lost card replacement delay
Target: lcard_sync_success_rate greater than 90% with sync_rules map communicated to FAQ and agents.
LCARD anti-patterns
Five common mistakes.
Account merge without verification: NO-MERGE-WITHOUT-VERIFY map
Promised balance without POS check: BALANCE-VERIFY-BOTH APIs
Blaming client sync: SYNC-DELAY-CITE sync_rules first
Replacement without blocking: LOST-BLOCK-FIRST loss theft
Gift card confusion: reroute gift card distinct points
LCARD with Qstomy
Qstomy on Shopify: detect lcard intent, LCARD-MAP RAG sync cite, Smile Yotpo balance lookup, handoff #588 bot tier 1 balance number.
Pipeline: #588 bot balance link wallet → #587 merge block replace escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
LCARD Checklist (8 steps)
LCARD-MAP v1: sync merge replacement wallet lookup
Policy LCARD-SUP: 6 BALANCE-VERIFY-BOTH rules
8 lcard_* typologies: helpdesk tags
4 LCARD-* macros: BAL LINK LOST WALLET
Sync POS test: sandbox transaction batch verify delay
Procedure merge ops: duplicate account documented
Agent training 30 min: LCARD vs PTS-REC vs gift card
Dashboard KPI: lcard_* section 9
FAQ
Difference points #374?
#374 = missing points incident post-purchase. #587 = card identifier omnichannel sync.
Store balance different from online?
LCARD-BAL-01 BALANCE-VERIFY sync_rules map.
Lost card?
LCARD-LOST-01 blocking then replacement_policy map.
Is Bot #588 enough?
Tier 1 balance number sync. Merge block replace → agents #587.
Going further
This week: publish LCARD-MAP sync_rules, test LCARD-BAL-01 mismatch scenario, measure lcard_sync_delay_rate.
Enzo
July 1, 2026
