By NHI Mgmt Group Editorial TeamBased on Riskified: “What return behavior looks like around the world” (July 6, 2026)

TL;DR: Major regional differences in return frequency, social-media influence, and what shoppers consider acceptable make one-size-fits-all return policy and fraud controls unreliable, according to Riskified’s 2026 survey of 2,091 consumers across seven markets. The data shows fraud and ecommerce teams need market-specific thresholds, sharper communications, and models that reflect local behaviour rather than global averages.


At a glance

What this is: This survey shows that return abuse patterns differ materially by market, with regional variation in frequency, social influence, and what consumers consider acceptable.

Why it matters: Fraud, ecommerce, and IAM practitioners responsible for customer-risk decisions need controls that adapt to regional behaviour, or they will over-flag honest users and under-flag coordinated abuse.

By the numbers:

  • The report surveyed 2,091 consumers across seven markets and interviewed ten senior retail leaders.
  • In China, 70% of consumers return items frequently or very frequently, compared with about 30% in the US.
  • In China, 93% of consumers have encountered return-related content on social platforms, while 60% of US consumers have never seen it.
  • Over 60% of consumers globally say they would adjust their return behavior if they knew the real costs of returns.

Context

Return abuse is not a single global pattern. The same return policy can look calibrated in one market and blunt in another because customer behavior, social influence, and tolerance for gray-area returns vary by geography.

For fraud and ecommerce teams, that means the unit of analysis is not the average consumer. It is the local market baseline, the communication style that shapes customer response, and the control threshold that distinguishes normal returns from coordinated abuse.

Riskified’s survey makes that segmentation problem explicit: controls that ignore market context create both false positives and blind spots.


Key questions

Q: How should teams calibrate return-fraud controls across different markets?

A: Use regional baselines rather than a single global threshold. Return frequency, social influence, and consumer tolerance vary widely, so review rules should be tuned to local behaviour and not just enterprise averages. A control that works in Tokyo may be noisy in Shanghai, while a rule that fits the US may miss elevated abuse elsewhere.

Q: Why do return-abuse patterns create false positives when controls are too rigid?

A: Rigid controls ignore the fact that some markets naturally return more, accept different behaviors, and respond differently to policy. When the baseline is wrong, ordinary customers look suspicious. That pushes unnecessary reviews, creates friction, and hides the distinction between normal variance and coordinated abuse.

Q: What signs suggest return abuse is becoming coordinated rather than individual?

A: Look for repeated claim language, shared tactics, sudden clusters of similar returns, and high exposure to return-related advice on social platforms. Those signals indicate that behaviour may be spreading through playbooks, which means the issue is no longer just customer choice but coordinated manipulation.

Q: How should merchants detect and reduce return policy abuse without making legitimate shoppers feel punished?

A: Merchants should treat return abuse as a risk segmentation problem, not just a refund problem. Strong controls combine policy design, customer behavior signals, and order history review so genuine shoppers are not blocked unnecessarily. The goal is to spot patterns such as repeated coupon misuse, non-receipt claims, and wardrobing early enough to limit losses while preserving a smooth experience for low-risk customers.


Technical breakdown

Why regional return behavior breaks global policy

Return controls usually assume that a single set of thresholds can govern all customers. In practice, return frequency is shaped by local norms, market maturity, and the social acceptability of behaviors such as wardrobing, bracketing, or item-not-received claims. When those baselines differ sharply, the same rule set can be too loose in one region and too strict in another. That creates a governance problem as much as a fraud problem because the policy signal no longer matches the actual customer population being controlled. The operating model has to separate honest variance from abuse patterns, or the organisation will optimise for the wrong risk.

Practical implication: Calibrate return thresholds by market segment, not by global average.

How social media amplifies coordinated return abuse

The report suggests that some markets are not just seeing individual abuse, but behavior shaped by shared tactics and advice circulating on social platforms. That matters because once return manipulation becomes socially normalised, the problem moves from isolated fraud to distributed behavioural coordination. Traditional anomaly rules built around rare outliers become less effective when the activity is widely known and repeatedly copied. In those environments, pattern detection needs to look at clustering, repetition, and tactic reuse rather than just absolute return rate. The key technical issue is that fraud models must distinguish local cultural norms from deliberately amplified abuse playbooks.

Practical implication: Tune fraud models to detect coordinated behaviour patterns, not just high-volume returns.

Why customer communication is part of the control surface

The article shows that more than policy strictness alone, customer understanding affects behavior. If over 60% of consumers would change their return behavior after learning the real cost of returns, then policy communication is part of the fraud-control stack. This is not only a messaging issue. It changes how much pressure lands on review queues, how many borderline cases escalate, and how likely customers are to perceive enforcement as arbitrary. Clear explanation can reduce misuse while preserving legitimate returns, especially in markets where restrictive policy is culturally acceptable but poorly understood. That makes transparency an operational control, not just a brand consideration.

Practical implication: Build clear return-policy communications into the control design, not just the customer journey.


Threat narrative

Attacker objective: Exploit return policy gaps to secure refunds, keep goods after use, or generate repeatable margin loss at scale.

  1. Entry begins with consumer-facing return channels that are easy to abuse when policy thresholds do not match local behaviour.
  2. Escalation occurs when social-platform tactics or AI-assisted claim writing make abusive requests more persuasive and harder to distinguish from legitimate cases.
  3. Impact is margin erosion, higher review load, and more friction for honest customers when controls are either too strict or too permissive for the market.
  4. The attacker objective is to maximise refunds, avoid detection, or convert product use into low-friction financial gain.

NHI Mgmt Group analysis

Market-specific return governance is now the baseline, not the exception: return abuse cannot be managed correctly with a single global threshold when customer norms differ this sharply by country. The article shows that frequency, acceptability, and social amplification all vary by market, which means policy design and fraud scoring have to be localised. The practitioner conclusion is straightforward: global policy should set principles, while market-level controls set the actual decisioning boundary.

Return abuse is becoming a behavioural intelligence problem: when social platforms circulate return tactics, the issue is no longer only individual fraud but the diffusion of playbooks. That changes how teams should think about signal quality, because aggregated behaviour can reflect coordination rather than anomaly. The implication is that fraud operations need market-specific behavioural baselines before they can trust any model output.

Return policy is also an access-control problem over financial loss: every return decision is a governed entitlement to reverse a transaction, not just a customer-service action. If that entitlement is too broadly granted, abuse scales; if it is too narrowly constrained, legitimate customers are punished. The practical conclusion is that return governance needs the same calibration discipline that access governance uses: identity, context, and eligibility must align.

Communication is part of the control, not a postscript: the report’s finding that consumers would change behaviour if they understood return costs shows that policy transparency can reduce misuse. That does not replace fraud detection, but it can lower pressure on enforcement and improve customer acceptance of legitimate controls. Teams should treat policy explanation as a measurable input to abuse reduction, not as soft guidance.

What this signals

Market segmentation is now a fraud-control requirement: return policy that ignores regional baseline behavior will either over-enforce or under-enforce. Teams need decisioning that reflects local consumer norms, because the same return pattern can be routine in one market and abusive in another.

Coordination changes the threat model: when consumers share return tactics through social platforms, abuse stops looking like isolated misuse and starts behaving like distributed operational playbooks. Fraud teams should treat clustered claim patterns as a signal of behavioural diffusion, not just volume growth.


For practitioners

  • Calibrate return thresholds by market Set review and restriction thresholds using regional baselines for return frequency, acceptable behavior, and local abuse patterns rather than a single global average.
  • Segment fraud models by behavioural context Train and tune models separately for markets with different social-media exposure, claim styles, and tolerance for gray-area return behavior.
  • Add coordination signals to abuse detection Look for repeated language, tactic reuse, and clustered claim patterns that suggest coordinated return abuse rather than isolated customer behavior.
  • Rewrite policy communication for each market Explain why return limits exist in language that matches local expectations, because transparency can change behavior and reduce friction.

Key takeaways

  • Return abuse is not evenly distributed, so global policy settings can create the wrong outcome in both strict and permissive markets.
  • The survey shows that consumer behaviour, social influence, and perceived acceptability all change by region, which weakens any single fraud threshold.
  • Fraud and ecommerce teams need local baselines, clearer policy communication, and models that can separate ordinary variation from coordinated abuse.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP API Security Top 10 addresses the attack and risk surface, while NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsReturn approvals function as governed entitlements that must match context and eligibility.
Recommendation — Align return eligibility rules with context-aware authorization logic rather than one-size-fits-all thresholds.
CIS Controls v8CIS-5 — Account ManagementReturn abuse management depends on controlling repeated customer entitlement misuse and review access.
Recommendation — Use account and entitlement governance to restrict repeated abuse paths without blocking normal customers.
OWASP API Security Top 10API6 — Unrestricted Access to Sensitive Business FlowsReturns are a sensitive business flow that can be overused when controls are too loose.
Recommendation — Apply tighter controls to return workflows so the business flow cannot be exploited at scale.

Key terms

  • Return Abuse: Return abuse is the misuse of a legitimate returns process to extract value without following the merchant's intended rules. Common forms include wardrobing, product switching and repeated opportunistic returns. It is operationally difficult because it often looks like ordinary customer behaviour until patterns are analysed across time.
  • Behavior Baseline: A record of normal activity for a non-human identity, including typical consumers, resources, and actions over time. Baselines help security teams detect when an identity is being used in an unusual way and provide the context needed to enforce least privilege safely in dynamic environments.
  • Gray-area return behavior: Gray-area return behavior sits between clearly legitimate commerce and obvious fraud. Examples include bracketing or returning items after short-term use, and the governance challenge is that acceptability varies by market, making enforcement decisions less uniform.
  • Coordinated abuse: Coordinated abuse is repeated misuse that is amplified by shared tactics, common scripts, or social influence rather than isolated customer choice. In return programs, it often produces patterned claims, clustered timing, and higher detection difficulty than one-off misuse.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
NHIMG Editorial Note
Published by the NHIMG editorial team on July 10, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org