‹ Blog
Estimated read time
In this article
Section heading
November 18, 2026

How do wrong-item return scams work, and how can fraud teams detect them?

Rachel Rosensweig
Product Marketing Lead, Fraud

This scenario is based on patterns fraud teams have described to us. Details have been changed, and it does not describe a specific company or a Radar customer result.

A wrong-item return scam convinces a customer to send a correct, legitimate shipment to a fraudster’s address. Precise location signals show fraud teams where shipment lookups come from and where a newly added device actually is, working alongside the identity, device, and payment checks they already run. For a team that has to stop device losses before the next shipment goes out, those two signals are the earliest places to look. Read more about fraud prevention with Radar.

What is a wrong-item return scam, and how does it unfold?

A wrong-item return scam is a social engineering attack that turns a real order into stolen inventory. A merchant ships the right device to the right customer, and the fraudster talks the customer into sending it on.

A call that sounds like the company

Fraudsters start with stolen account details and phone numbers. They call customers from a number that appears to belong to the company, which makes the call feel legitimate.

An offer that gets the customer to order

On the call, they mention a real promotion that the merchant is running, such as a free device with a new line or other offer of free inventory along with the purchase of a good or service, and walk the customer through placing the order live.

A tracking number that tells them when to call

They ask the customer for the tracking number, provided through the merchant’s website (not UPS or FedEx or another external provider). With it, they can watch the shipment on the company’s own tracking page and know when it arrives.

An unboxing call and return label

Right after delivery, they call again and ask the customer to open the box. They then convince the customer that the wrong item was shipped and give return instructions. The return address belongs to the fraudsters, who collect the devices and resell them.

The scam works because every step looks like normal customer service, so each order, shipment, and return looks legitimate on its own.

Why do existing fraud signals miss wrong-item return scams?

Each existing signal covers one step, and none connects the lookups, the orders, and the returns. In this scenario, the first clue came from tracking page traffic, not from a customer report.

Customers did not know to report it

Customers believed they were fixing a shipping mistake, so the company received few reports.

Unusual tracking page traffic was the first clue

The team saw a highly unusual volume of lookups for domestic shipments, coming from IP addresses in the same foreign region. That traffic was the fraudsters checking on their victims’ packages.

Signal What it could have shown Why it missed
Customer reports That customers were being contacted Rare, because victims believed the process was real
Tracking page traffic Repeat lookups from one foreign region Revealed the pattern only after it had grown
Device location history A new device far from the account's usual place Reviewed only during the investigation
Promotion orders A run of orders tied to one scam Looked normal one at a time

‍

How can precise location help catch wrong-item return scams earlier?

Precise location shows who is looking at a shipment and where a new device actually is, so teams can act before more devices ship. IP location shows where a connection appears to come from. Precise location, from device GPS, Wi-Fi, and sensor data, shows where the device is. 

Flagging tracking lookups from the wrong place

Compare where each tracking lookup comes from with where the package is going. A shipment headed to a home is normally checked from that area, by the customer or someone in their household. A lookup from an IP address thousands of miles from the delivery address is unusual, and a consistent pattern of them is a signal worth acting on.

Here is an illustrative example. A device ships to a customer in the Midwest. Over the next few days, the tracking page for that shipment is opened repeatedly from IP addresses in the same region on another continent, including just before delivery. The customer isn’t traveling, and no one in the household is there. Those lookups fit someone watching the package to know when it arrives.

IP location shows where a connection appears to come from, which is enough to see a mismatch like this one. Teams can:

  • Compare the IP location of each lookup with the delivery address, and flag lookups that are far from it
  • Look for repeated lookups of the same shipment from the same distant place
  • Check for VPN and proxy use, since a masked connection on a domestic shipment adds to the signal
  • Ask for a stronger check before showing tracking details when a lookup looks risky
  • Investigate why a distant region is watching domestic packages

One lookup from far away has plenty of innocent explanations, such as a traveling customer or a relative abroad. The pattern is what matters: the same shipment checked repeatedly, from the same distant place, that never matches where the package is going.

Comparing a new device’s location with the account’s history

If the item being shipped is a device such as a cell phone, location history lets a team spot an account whose long-standing device stays in one place while a newly added device only appears far away. That mismatch is a reason to review the order before the next device ships.

What precise location will not catch on its own

Precise location will not catch, on its own, the phone calls, spoofed caller ID, and the return address sit outside location signals. Location helps most with lookups and device activity on a company’s own channels, so call controls and return rules still matter.

Precise location adds a physical view that identity checks, IP geolocation, and device fingerprints cannot confirm on their own.

What should a fraud team check first?

Check tracking page traffic first, because it was the earliest signal in this scenario, then add new-device location checks. The list below runs from the earliest signal to the later controls.

  1. Review tracking page traffic for repeat lookups from one region or from masked connections.
  2. Add rate limits or a sign-in requirement before showing tracking details.
  3. Flag new devices added to accounts whose location history does not match.
  4. Require return labels that the company generates, and review any return that uses a different address.
  5. Watch for promotion orders that are followed quickly by an exchange or return request.
  6. Test any new signal on your own traffic, alongside your current tools, and measure added detection, false positives, and customer friction.

Add location signals to the identity, device, and payment checks you already run, then measure what they catch that those checks miss.

Test Radar against your own tracking and device data

Test Radar's location signals against your own tracking page traffic and new-device activity - chat with our team to learn more.