Appearance

The buyer who refunded 8 orders to one address. Flag them first. ​

Posted 2026-05-17

A multi-channel reseller pulled a return audit this week and found one buyer name attached to eight orders of the same SKU, all delivered to the same address, all refunded. Six weeks. $1,200 out the door. The only reason it got caught was that the operator finally sat down on a Friday and read the returns log line by line. The buyer had been hitting the account for a month and a half without a single alert, because the data lived in eight different reports and nobody was looking at it together.

Three more threads ran the same week. One eBay seller got the "send a picture of damage" partial-refund routine from a buyer who had already pulled the move twice. Another eBay seller had an account place a multi-item order and immediately request a cancel after fulfillment started. A third found buyers blocked on one account coming back the next month under a slightly different name. The patterns are not hidden. The tools just do not show them.

The trap is the toolchain, not the buyer ​

Returns fraud detection is a pattern-recognition problem and the patterns are simple. Same buyer name. Same shipping address. Same SKU. Same refund reason. Same window. What makes the patterns invisible is that the data lives across Amazon Seller Central, eBay Selling Manager, Walmart Seller Center, Shopify Admin, and BackMarket's portal. Each system shows that channel's returns and only that channel's returns. Each system has its own refund-reason taxonomy. Each system has its own timing. And once you are also shipping from a separate tool, the connection between "order shipped from one screen" and "refund processed in another" is one more layer of cross-reference you do not have time to do.

The result is that the fraud is recoverable only after the fact. By the time the buyer has hit you eight times, you have eight return records sitting in eight different exports. You would have caught it on order three if you had been looking at one screen.

What the actual losses look like ​

Take the r/FBA case at face value. Eight orders. $1,200 refunded. One ASIN. Average unit price about $150. The headline number is the refund. The real loss is bigger.

Amazon's return shipping deduction on a customer-funded return runs $6 to $11 per unit depending on weight, plus a returns processing fee of roughly $1.80 on FBA. That is another $60 to $100 on top of the refunds. Then there is the fact that units that did ship back came in unsellable condition, because the buyer's whole intent was to keep the unit and get the money. Reimbursement on FBA-lost units is a process you have to run yourself, and partial-refund claims are not eligible. Add another $400 to $800 of unrecoverable inventory cost to the $1,200, and the actual hit on that one buyer was closer to $1,700 to $2,100.

The eBay version of the playbook is different but the math is parallel. The "send a picture of damage" partial-refund move asks for $20 to $40 off a $150 sale with no return required. The buyer keeps the unit. eBay's resolution center often pushes the seller to accept because contesting takes 30 minutes of evidence upload and the buyer can leave negative feedback on the way out. The same buyer pulls the move four times across four accounts and four sellers and nobody connects the dots, because the only place dots get connected is your own ledger if you happen to be keeping one.

Walmart is similar. The buyer claims a delivery issue, Walmart pays out the refund from seller funds, the unit stays with the buyer. Shopify is the only channel where you have a real chargeback fight with the issuing bank, and that fight is decided by tracking strength, signature confirmation, and shipping records, not by your relationship with Shopify.

The pattern across all four channels is identical. Low effort for the buyer. High friction for the seller. Automatic payout from your funds. Sellers absorb it because the cost of detection is currently higher than the cost of the loss.

The view that makes the pattern visible ​

Three columns on one screen make returns abuse detectable in under five minutes a week.

Column one: returns by buyer name across all channels. If buyer "C. Lopez" shows up twice this week from two different marketplaces and once last week from a third, that is the alert. The lookup is by buyer name and shipping address combined, because the same buyer behind multiple marketplace identities is the most common scaling move. Address-only matching surfaces the multi-account version of the same buyer.

Column two: returns by SKU. A given SKU should have a baseline return rate, typically 2 to 6 percent depending on category. If one SKU is at 18 percent this month, either the listing has a defect problem to fix or it has become a fraud target. The two are easy to tell apart by looking at return reasons. A defect shows up as "item not as described" or "doesn't work." A fraud target shows up as "didn't arrive" with delivery confirmation already showing delivered, or "arrived damaged" with no return shipped, or "partial refund requested" with no return at all.

Column three: refund-without-return ratio by buyer. Buyers who request and receive refunds without ever returning the unit are the cleanest signal. A normal customer returning a defective unit is happy to ship it back. A buyer collecting refunds is not. Run the ratio over a 30-day window and the top of the list is the watch list.

Once those three views exist on one screen, the workflow takes five minutes a week. Look at column one and scan for repeats. Look at column two and find any SKU above its baseline. Look at column three and identify the high-ratio buyers. Anyone who shows up in two of the three columns is a confirmed pattern. Block on each channel they hit. Amazon has the buyer-block list in Seller Central. eBay has the blocked-bidder list. Walmart has the buyer-feedback tool. Shopify uses customer tags plus fulfillment freeze.

The second-order workflow is preventive. A serial-tracked SKU that has been a fraud target before should require a signature for delivery on the next order. A high-value SKU with high refund-without-return rates should move to a stricter return policy on the platforms that allow it. A buyer flagged once and seen again across the network can be auto-cancelled at order intake, not after fulfillment.

None of this requires anything more sophisticated than the data you already generate. The only thing that has to change is where you can see it.

We built this because we lost to it ​

Rilk's returns inbox pulls returns from Amazon, Walmart, eBay, Shopify, and BackMarket into one screen, with buyer name and shipping address on every row. The return rate by SKU dashboard lives in Reporting, with the by-channel and by-reason cuts already built. Return rate by SKU rolls 30 and 90 days, so the spikes that mean fraud surface as outliers within hours, not weeks. The per-unit cost basis follows the unit through the return, so when a unit comes back and gets re-graded down, the new cost is on the unit's record, not in your head.

The view that makes patterns easy to find is the unified one. The buyer who hits you on Amazon and again on eBay shows up two rows apart. The shipping address that has received four orders under four "names" sorts together. Spotting the cluster takes a glance once the data is side by side. It is impossible when the data is in four separate exports.

Rilk does not auto-block buyers and we do not plan to. Auto-blocking is the wrong instinct. Half of repeat returns are real customers with real defects on a SKU that needs work, not fraud. The job of the software is to surface the pattern. The decision still belongs to the operator. The five-minute Friday review is the workflow, and it pays for itself the first month it catches a $1,200 ring.

  • Returns. Unified inbox, inspection workflow, and outcome routing across every channel.
  • Reporting. Return rate by SKU, by channel, by reason, on settlement-reconciled data.
  • Multi-channel sync. Inventory stays in lockstep when units come back.
  • Refurbisher use case. Returns are the input, not the exception.
  • Rilk vs ShipStation. What one tool replaces when you stop stitching.

Built for resellers and refurbishers.

© 2026 Rilk