Store Credit Is Not Loyalty: The 2026 Ecommerce Retention Playbook

John Brown

3 days ago

5 min read

There is a difference between giving a customer a reason to return and giving them money they are already owed. Too many ecommerce teams put store credit, loyalty points, gift cards, and goodwill adjustments into one retention bucket. The dashboard may show redemption and repeat orders, but the customer experiences are fundamentally different.

Heading into the holiday return season, I would treat store credit as a financial promise first and a CRM opportunity second. The order matters. A customer who accepted a $40 return credit does not need a campaign congratulating them for earning a reward. They need to know where the $40 is, how to use it, and whether it expires.

Three balances, three different customer expectations

Store credit typically represents a monetary balance issued to a customer, including for refunds or goodwill. Loyalty points are program-specific units earned under published rules. Gift cards can carry their own legal requirements and accounting treatment. Calling all three “rewards” is convenient for marketers and confusing for customers.

Shopify’s current store-credit documentation explains that eligible customers can apply store credit when signed into customer accounts or using Shop Pay. It also explains that expiration is configured per issuance, not through a universal store-wide default. That means a CRM message cannot safely assume that every customer has the same expiration policy.

The first audit question is not “How much store credit revenue did we drive?” It is “Can a customer see and redeem the exact balance we told them they had?” Start with that before building a campaign.

The operational problem hiding inside a retention metric

Consider two customers who each place a $90 order. Customer A uses $20 in promotional loyalty value earned through prior purchases. Customer B uses $20 of store credit issued after a delayed refund. Both orders can look like $90 in gross merchandise value, and both can be attributed to an email. But the economics and the customer experience are not equivalent.

Customer A may have been influenced by a reward. Customer B may simply have recovered money already owed. I would report the two separately, with credit redemption treated as a payment or settlement mechanism where applicable, not automatically as incremental CRM-generated demand. Finance should define the revenue and liability treatment for the specific program.

This is the same measurement discipline I argued for in my earlier piece on attributed versus incremental revenue. A platform attribution report is useful for campaign diagnostics, but it does not prove the campaign caused the order.

Build a store-credit service journey before a promotion

The first message should confirm issuance with the exact amount, currency, source of credit, expiration date if one exists, and clear instructions for accessing it. For Shopify stores, test the sign-in experience and Shop Pay redemption path on mobile before publishing the flow. A working link to a generic homepage is not the same as a working redemption journey.

A second message can be sent if the credit remains unused after a reasonable interval. It should solve friction rather than manufacture urgency: “You still have $40 in store credit. Sign in to your account to use it at checkout.” If a legitimate expiry exists, include the exact date and relevant timezone rather than a vague countdown.

A third message is optional. If the customer has already contacted support about a refund, has an unresolved order issue, or has unsubscribed from marketing, do not route them into a generic promotional sequence. Coordinate service notifications and marketing permissions with legal and CX rather than assuming one consent rule covers every message.

Expiration is a trust decision, not just a campaign trigger

Shopify states that store credit with an expiration date expires at the end of that day in the store’s timezone, and that when multiple credits expire on different dates the earliest-expiring credit is used first. Shopify also advises merchants to check local laws before setting expirations. Those are operational details with direct implications for copy, support macros, and CRM data.

If you choose to send reminders, use the actual credit-lot expiration data, not the most recent credit issuance date. A customer may have $10 expiring next week and another $30 that does not expire. “Your $40 expires Friday” would be inaccurate. That is a small data-model mistake with a very visible customer consequence.

There is also a fraud consideration. In April 2026, the FTC warned consumers about phishing texts impersonating rewards programs and claiming points were about to expire. For legitimate reminders, keep sender identity consistent, avoid suspicious shortened links, and provide a familiar route through the customer account. Urgency should never make the message look like the scam customers have been told to avoid.

The five-field data contract I would require

Before activating a store-credit lifecycle, I would require a customer identifier, available monetary balance with currency, individual credit-lot expiration timestamps, issuance reason, and the latest redemption or debit event. Add marketing eligibility and unresolved-service status as suppression inputs. Ownership should sit with the team maintaining the financial ledger, not with a marketer manually updating a profile property.

For a practical QA case, issue a test customer two credits with different expiration dates, redeem part of the first, then verify the remaining balance in Shopify, the CRM event payload, the email preview, and checkout. Repeat for an expired credit, a fully redeemed credit, and a customer who is not signed in. Do not launch if the systems disagree.

Measure customer outcomes, not just redeemed balances

My scorecard would separate credit issued, credit outstanding, credit redeemed, expired credit, support contacts per credit recipient, redemption failures, and repeat purchase after credit issuance. Segment by issuance reason, because a goodwill gesture after a bad experience should not be evaluated against the same baseline as a promotional loyalty incentive.

For a promotional credit experiment, randomly hold out eligible customers from the marketing reminder where appropriate, while preserving legally or operationally required notices. Compare incremental orders and contribution margin after the cost of the incentive. For refund-related credit, focus first on successful redemption, complaint reduction, and the customer’s subsequent experience rather than pretending the original refund is new value created by CRM.

What I would do this week

I would start by asking Finance and CX to agree on the definitions of store credit, gift cards, and loyalty rewards. Then I would pull ten recent credit issuances, follow each one from ledger to CRM to checkout, and document any mismatch in amount, expiry, or customer identity. Only after that would I brief creative.

If the goal is loyalty, build something customers actually value and can understand. If the goal is resolving a refund, resolve it clearly. Mixing the two may produce a prettier retention dashboard, but it makes for a worse customer experience.