Store Credit, Partial Refund, or Keep-the-Item: A Decision Tree for Returns

Every return that ends in a full refund is a decision your business didn't actually make. It's what happens by default when nobody built a better option.

Most brands run one return policy for every item, every customer, and every reason. Full refund, every time. That's not a policy. It's the absence of one, and it's the single most expensive habit in ecommerce returns.

The default is costing you more than the return itself

A full refund gives back 100% of the sale, then adds the cost of return shipping, restocking labor, and a product that may not be resellable at full price, if it's resellable at all. On a $12 item, processing and shipping the return can cost more than the item is worth. On a $150 item that comes back lightly used, you're refunding full price for something you'll sell at a markdown, if you can sell it again.

None of this is a customer service problem. It's a decision architecture problem. You're offering one outcome when you actually have three, and the other two often serve the customer just as well while costing you far less.

The three outcomes, and what each one protects

Every return resolves into one of three outcomes, whether you've designed for it or not.

Keep-the-item. The customer keeps the product and you refund them anyway, no shipment back. This works when the item's value is lower than the cost to receive, inspect, and restock it. You lose the item's cost, but you save the logistics spend and you skip a step that annoys the customer as much as it costs you.

Partial refund. The customer sends the item back, or keeps it, and receives a reduced refund. This protects margin on items where full resale isn't realistic, a garment that's been worn, a box that's been opened and can't go back on a shelf as new, or a return outside the ideal condition or timing window.

Store credit. The customer gets the refund value back as credit toward a future purchase, sometimes with a bonus to make it more attractive than cash back. This keeps revenue inside the business instead of sending it out the door, and it works best on customers who are likely to shop with you again.

Each outcome trades something different. Keep-the-item trades product cost for logistics savings. Partial refund trades customer goodwill for margin protection. Store credit trades a small incentive for retained revenue and a future order. A one-size-fits-all refund policy uses none of these levers.

Build the tree around four variables

A decision tree doesn't need to be complicated to work. Four variables get you most of the way there.

Item value. This is your first fork. Set a threshold, informed by your average shipping and handling cost per return, under which sending the item back doesn't make financial sense. Items below that line are keep-the-item candidates by default.

Return reason. Sizing issue, changed mind, or "didn't like it" are different from defective or wrong item shipped. The first group is fair game for the full outcome menu. The second group usually still earns a full refund, because the business made the error, not the customer.

Item condition and resalability. Unopened and unworn goes back to inventory and can support a fuller refund. Opened, worn, or missing packaging drops resale value and points toward a partial refund.

Customer history. A first-time buyer returning something isn't the same as a repeat customer with a strong order history returning something. Loyal customers are the group most likely to accept store credit happily, especially with a modest bonus, because they were already planning to buy from you again.

Run a return through those four checks in order and you'll land on an outcome that fits, not one that was assigned by habit.

What the tree looks like in practice

Say a customer returns a $9 accessory because it didn't match what they expected. Item value is low, return reason is preference-based, condition is irrelevant at this price point. This is a clean keep-the-item case. You refund the customer immediately, they keep the item, and you never touch return shipping or restocking.

Now say a customer returns a $95 jacket, worn once, because the fit wasn't quite right. Item value is mid-range, the return reason is legitimate, but the item has been worn and can't be resold as new. A partial refund, say 80% of the purchase price, reflects the real resale value while still treating the customer fairly. They knew the item was worn when they wore it.

Now say a repeat customer with six prior orders returns a $60 item that simply didn't work out. Item value is moderate, condition is good, and this customer has a strong purchase history. Offer store credit with a small bonus, 110% of the refund value as credit instead of 100% back to their card. Many loyal customers will take that trade without hesitation, because they're already coming back.

None of these outcomes require a judgment call from a support agent. They fall out of rules you set once.

Where full refund still belongs

A rules-based menu doesn't mean full refunds disappear. They still belong wherever the business, not the customer, is responsible for the problem: defective products, wrong items shipped, or damage that occurred in transit. Pushing those situations toward store credit or a partial refund reads as punitive fast, and it should. The customer didn't create the problem, so they shouldn't absorb any part of the cost.

The rule of thumb is simple. When the return reason points at the customer's decision, preference, or fit, the outcome menu applies. When it points at the business's error, full refund stays the answer.

Make the menu feel like a choice, not a downgrade

The way you present these outcomes matters as much as the outcomes themselves. A partial refund that arrives as a surprise deduction feels like a penalty. The same partial refund, shown to the customer at the start of the return flow with a clear reason, feels like information they were given upfront.

Where you can, let the customer choose between two acceptable outcomes instead of assigning one. A customer offered "80% refund to your card" or "100% as store credit" is making a choice, not receiving a verdict. Most brands find customers pick store credit more often than expected, because it's framed as the better deal rather than the lesser evil.

Transparency is what keeps a rules-based system from feeling arbitrary. Publish the logic in plain terms on your returns page: items under a certain value are refunded without a return shipment, worn or opened items receive an adjusted refund, and loyal customers get bonus credit options. Customers respond well to rules they can see, even when the rule doesn't fully favor them.

Track revenue retained, not just return rate

Most returns dashboards stop at return rate and refund total. Add one more metric: revenue retained per return, meaning the dollar value you kept in the business through store credit, avoided shipping cost, or a partial refund, divided by total returns processed.

That number is the real measure of whether your outcome menu is working. A brand that shifts even 20% of its returns from full refund to store credit or keep-the-item will see that number move immediately, without changing a single thing about return volume or customer satisfaction scores.

The goal isn't to make returns harder. It's to stop treating every return as a single, expensive outcome when three cheaper ones were sitting there the whole time.

ShipAid's Smart Returns lets merchants build exactly this kind of rules-based outcome menu, routing each return to store credit, partial refund, keep-the-item, or full refund automatically based on item value, condition, and customer history. See how Smart Returns applies your rules at shipaid.com.