Store Credit vs Refund: A Decision Rule for Shopify Support Teams

Store credit vs refund comes down to two things: who caused the problem, and what the customer has done before. If the order arrived broken, wrong or missing, refund to the original payment method. If a repeat customer changed their mind, offer store credit with a bonus first, and refund if they say no. A gift card only fits when the person holding the item never paid for it.

The policy is the easy part. The hard part is that the rule usually lives in one senior person's head. So a VA or a seasonal hire makes it up under pressure, and either gives away cash or annoys the customer.

The rule below is written to be copied into a refund procedure. It includes the threshold, the Shopify permissions and the exceptions a new hire can't guess.

What is the decision rule for store credit vs refund?

Start from the return reason. Then check the order value, the customer's history and the fraud flag.

Two lines keep this honest. Never issue store credit for a problem the store caused. And never let a first-time buyer find out about a credit rule after they have already asked for cash.

This matches the site's refund policy enforcement SOP, which defaults to a refund and treats credit as an alternative with a small bonus.

How does each option work inside the Shopify admin?

Store credit is a balance on the customer's profile. They spend it as a payment method at checkout. When you refund, you can split the amount between the original payment method and store credit, and edit each part before you confirm.

To refund, you need to be the store owner or hold the matching Orders permission. Refund to original payment method and Refund to store credit are separate permissions. Give a VA only the one that matches the branch they are allowed to run. The post on the Shopify permissions your SOPs should name lists the exact names.

Two details catch teams out. Store credit doesn't work with legacy customer accounts, so the buyer has to sign in through customer accounts to spend it. And if a customer holds credit in several currencies, checkout shows only the balance in the checkout currency. An agent looking at the profile may see a balance the customer can't.

Which return reasons should never get store credit?

Anything the store got wrong. Damaged, defective, wrong item, missing item and non-delivery all go back to the original payment method, or to a replacement if the customer prefers one.

This is not only about fairness. Shopify's chargeback documentation lists Product unacceptable as a dispute reason: the customer got the item, but it was defective, damaged or not as described. Nothing in Shopify's help pages says store credit stops that dispute. A customer who wanted cash for a broken item can still go to their bank.

When you refund a product fault, use the refund screen with care. Restock items is selected by default, so clear it if the item can't be sold again. Refund shipping on purpose. You can refund up to the amount charged, but not on orders with an order-level free shipping discount.

What does a cash refund actually cost you?

More than the order value. On Shopify Payments, the original card processing fee is not returned when you refund. That is true whether or not the order was fulfilled. A refund doesn't add a new fee, but the first one is gone.

Third-party gateways work differently. If Shopify Payments is available in your country and you use another gateway anyway, Shopify's transaction fee is not refunded. If Shopify Payments isn't available in your country, the fee comes back in proportion to the refund. That credit only applies when you refund from the Shopify admin, not inside the gateway.

Two timing rules belong in the SOP. You can usually issue a refund up to 120 days after the order. And if your Shopify Payments balance goes past its negative balance limit, new refunds show as Refund pending. The customer is only notified once the refund has processed, so tell them that in the ticket.

Can a customer still file a chargeback after taking store credit?

Shopify's documentation doesn't say store credit closes a card dispute. On refunds it is clear. During an inquiry, a full refund means the cardholder can't start a chargeback, but a partial refund leaves a full chargeback possible. Once a chargeback is open, you can't refund the order at all, because the bank already holds the funds.

That is the best practical reason to keep cash refunds open on fault cases.

If a customer says they cancelled a chargeback, don't close the ticket on their word. Shopify says to get an official withdrawal letter from their bank and submit it as evidence. The chargeback dispute SOP covers the rest of that process. One exception: some stores are in a network dispute resolution program. There, disputes are settled automatically before they become chargebacks, and there is no evidence to submit.

What happens if you refund to store credit and the customer wants cash?

Shopify locks the original payment method on the refund screen. To refund the card as well, the agent needs the Over-refund orders previously refunded to store credit permission, and Shopify allows it only on Shopify Payments orders. The store credit already issued is not taken back. The refund processing SOP for Gorgias and Shopify shows where that branch sits in the handoff.

How should fraud signals change the call?

Fraud signals override the reason code. While they are live, the answer is neither credit nor cash until the order is verified. Nothing goes to a payment method that was never charged.

The signals that should trigger this hold, and the checks that follow, are in the order fraud prevention SOP. A refund decision follows the same logic as an order hold. Send it to whoever owns fraud. Don't let the agent decide alone.

What limits must your store credit policy respect?

Store credit has rules your policy page has to match. Otherwise support will promise things checkout can't do.

• Where it works: the online store, Point of Sale and the Shop app. Not on other sales channels, and credit on a customer profile can't be used in a B2B store.
• Not on draft or edited orders. To let a customer spend credit on an order you build in the admin, send them a checkout link and have them sign in.
• All or nothing. The customer can't apply part of their balance. Write that into any partial-credit offer.
• A cap. You can issue less than $15,000 USD in total to one customer account.
• Expiry is set each time. There is no store-wide default and no automation. If all return credit should expire on the same clock, the SOP has to say so, because someone sets it by hand.
• Expiry runs to the end of the day in your store's timezone, wherever the customer is. When a customer has several credits, the one that expires first is spent first. Check local law before you set any expiry.
• It is not free on newer stores. For stores created on or after May 12, 2025, orders paid partly with store credit are charged third-party transaction fees on the store credit amount.

How do you turn this into a decision branch a VA can follow?

Write it as a branch with numbered inputs, not a paragraph of philosophy. Four things turn a suggestion into a rule.

1. Name the inputs in order: reason code, then order value, then the number of orders on the account, then the fraud flag. An agent who checks them in that order lands on the same answer every time.
2. Put a dollar threshold on the agent's authority. Below it, the agent decides and acts. Above it, the ticket goes to a named person. A threshold is the one part of a refund policy a new hire can't argue with.
3. Write the exact clicks for each outcome: which refund method to select, and which permission the step needs.
4. Tag the order with the reason and the method used. Without tags you can't tell later whether credit is being spent or just piling up.

If you want customers to choose store credit, make it the better offer, not the only one. The Loop Returns exchange flow SOP sets bonus credit above the refund value for that reason. The returns SOP for DTC brands puts exchanges and credit first in the portal, with the refund one step further down.

Where does this decision rule fail?

In three places, and all three are predictable.

First, disclosure. A credit-first rule the customer only meets after asking for a refund feels like a bait and switch, especially on a first order. The rule works only if the policy is visible on product pages, at checkout and in the return confirmation.

Second, drift. The branch depends on things that change under it: staff permissions, the refund screen, your payment provider, your expiry choice. Open the refund screen on a real order in your own admin and check what your permissions actually let you select.

Third, review capacity. The threshold sends edge cases to a person. If that person is on holiday during Black Friday and nobody covers the queue, agents start guessing again, and the rule quietly stops existing.

Next step

Take one hour. Open your three most recent change-of-mind returns and your three most recent damaged-item returns. Write down what each agent actually did. Then write the branch that matches the calls you want, with one dollar threshold and one named owner above it.

Record the refund screen once while you make each call. ReccordSOP turns the recording into a numbered SOP, with a screenshot and the clicked button highlighted for every step. Record the same task again later and it compares the two, showing which steps changed instead of overwriting the old version. Send the finished SOP out as a checklist run, so you know which version a seasonal hire followed. It documents a process. It doesn't run the process, watch your store settings or make decisions for you.

The free plan covers 3 SOPs in total. Team is $19 per user per month, with a 3-user minimum. Start with your refund branch: record it on reccordsop.com.