Return Fraud and Serial Returners: How to Tighten Your Policy Without Breaking Google's Return Policy Requirements

The Tension: Fraud Prevention vs. Return Policy Requirements

Return fraud — wardrobing, empty-box returns, serial returners who buy items with intent to use once and return — is a real and growing cost for online retailers. The instinct to fight back by tightening return policy terms is reasonable, but Google Merchant Center has specific, non-negotiable requirements for what a compliant return policy looks like, and several common anti-fraud tactics cross directly into policy violation territory. The result: retailers trying to protect their margins end up creating a second problem, a Merchant Center flag, on top of the fraud problem they were already fighting.

What Google Actually Requires in a Return Policy

At minimum, Google requires that your return policy be clearly stated, easy to find, and consistently applied — meaning the policy shown to a shopper on your site before purchase has to match what's actually honored after purchase. It doesn't require you to accept every return unconditionally; it requires that whatever terms you do set are clear, disclosed, and not effectively unusable in practice.

Restocking Fees: Where the Line Is

Restocking fees are allowed and a legitimate lever against low-effort return abuse, but they need to be clearly disclosed before purchase, not introduced at the return request stage. A restocking fee percentage that's reasonable (typically cited in the 10-20% range across most retail policies) and disclosed upfront is compliant; an undisclosed fee that appears only when a customer initiates a return is a policy violation and, separately, a strong driver of chargebacks and platform complaints.

How Much Can Legitimately Be Marked Final Sale

Marking specific categories final sale — clearance items, custom/personalized products, intimate apparel for hygiene reasons — is standard and compliant when disclosed clearly at the point of purchase. Marking your entire catalog final sale as a blanket anti-fraud measure is a different matter: it's the kind of policy that technically meets the "clearly disclosed" bar but fails the broader expectation that return terms be reasonable for the product categories being sold. If your account faces manual review over return policy, an unusually broad final-sale designation across ordinary, non-perishable, non-personalized goods is one of the first things reviewers look at.

Flagging Serial Returners Without Policy Violations

The compliant way to manage habitual serial returners is account-level, not policy-level: track return rates per customer account and apply case-by-case consequences (requiring store credit instead of refund, declining future orders, requiring manager approval) to specific accounts that trigger your fraud thresholds — while keeping the published return policy itself uniform and compliant for everyone else. This keeps your public-facing policy honest (it says what it does, for everyone) while still giving you a fraud-management lever that doesn't touch Merchant Center compliance at all, since Google evaluates your stated policy and its consistent application, not your internal account-level fraud rules.

Shortened Return Windows and Disclosure

Shortening your return window (30 days to 14 days, for example) to reduce fraud exposure from long-hold wardrobing is compliant as long as the shorter window is clearly disclosed before purchase and applied consistently. Where retailers get flagged is when the disclosed window doesn't match reality — a "30-day returns" claim in ad copy or on a category page that contradicts a shorter window buried in the actual returns policy page is a disclosure-consistency violation, separate from whether 14 or 30 days is itself acceptable.

Chargebacks vs. Returns: A Distinction Worth Tracking Separately

Retailers fighting return fraud sometimes conflate two distinct problems — customers who abuse a legitimate return process, and customers who bypass the return process entirely by filing a credit card chargeback. Tightening your public return policy does nothing to address chargeback fraud, since a chargeback dispute happens outside your return flow entirely, through the customer's card issuer. Treating a rising chargeback rate as a reason to restrict your public return policy for everyone is a mismatched response that creates compliance risk (an overly restrictive policy) without addressing the actual problem (payment-level fraud, which needs payment-processor-level tools like chargeback alerts, 3D Secure, and address verification, not return policy changes).

Track return-rate fraud and chargeback-rate fraud as separate metrics with separate response playbooks. This keeps your return policy tightening proportionate to actual return abuse, rather than over-correcting because of a problem your return policy was never the right tool to solve in the first place.

Refusing Returns Based on Item Condition

Rejecting a return because the item shows clear signs of use beyond what's reasonable for inspection (worn soles on shoes, removed tags with visible wear, a wardrobed item with deodorant marks) is a legitimate and compliant practice, but it needs to be disclosed as a condition of the return policy upfront, and applied through a documented, consistent inspection process rather than case-by-case discretion that can look arbitrary from the outside. Publish your condition standard explicitly — "items must be unworn, with tags attached, and free of odor or staining to qualify for a refund" — so both the customer and, if it's ever reviewed, Google can see the standard was clear before the fact, not invented after a specific return arrived.

Where this goes wrong: retailers who reject returns informally based on unstated internal criteria, leading customers to reasonably believe they followed the rules and were still denied. That gap between stated policy and actual practice is precisely what return-policy compliance reviews look for, separate from whether your underlying condition standard is reasonable.

Common Flags in This Category

Third-Party Return Fraud Detection Tools

A growing category of tools (Returnly, Loop, Narvar, AfterShip's fraud modules, among others) can score return requests for fraud risk without you needing to change your public-facing policy terms at all — flagging patterns like frequent returns from the same shipping address across different accounts, unusually high return rates on specific SKUs prone to wardrobing, or mismatched serial numbers on returned electronics. Layering one of these tools underneath a compliant, uniformly-applied public policy is generally a cleaner path to fraud reduction than tightening the policy itself, since it targets actual fraud signals rather than restricting legitimate customers along with fraudulent ones.

Pre-Submission Checklist

• Return policy is stated in one canonical location and linked consistently across product pages, ads, and marketing copy
• Restocking fees, if any, are disclosed before purchase, not introduced during the return request
• Final-sale designations are limited to genuinely appropriate categories, not applied catalog-wide as a fraud deterrent
• Serial-returner countermeasures are applied at the customer-account level with documented criteria, not baked into the public policy
• All stated return windows across site, ads, and policy pages match exactly

Frequently Asked Questions

Can I refuse future orders from a customer who returns too often?

Yes, this is an account-level business decision separate from your public return policy, and it's a common, compliant anti-fraud practice as long as you apply it based on documented, consistent criteria.

Is a restocking fee compliant with Google's return policy requirements?

Yes, as long as it's clearly disclosed to shoppers before they purchase, not revealed only when they attempt a return.

Can I mark my whole catalog final sale to stop return fraud?

You can, but it invites scrutiny if applied broadly to ordinary product categories that buyers reasonably expect to be returnable. Reserve final-sale status for categories where it's standard practice (personalized, perishable, hygiene items).