Commerce Graph · Research Note · Guide

COD Fraud Prevention for Online Sellers

COD fraud costs Indian online sellers far more than just returned parcels — here is how to detect it early, verify buyers systematically, and recover your margins.

AS OF 11 JUL 2026 · SOURCE: COMMERCE GRAPH — SHIPROCKET COMMERCE INTELLIGENCE
Key takeaways

Cash-on-delivery remains the dominant payment mode for a large share of Indian e-commerce transactions, particularly in tier-2 and tier-3 markets where digital payment trust is still maturing. That dominance, however, creates a structural vulnerability: because payment is deferred to the moment of delivery, sellers absorb the full operational cost of every order before receiving a single rupee, and fraudulent buyers exploit that gap with very low personal risk.

COD fraud takes several forms — from deliberate non-delivery acceptance and fake address orders to organised return abuse — and its financial damage compounds quickly. Every rejected parcel generates a reverse logistics charge, ties up inventory, and delays working-capital recovery. For small and mid-size Indian sellers operating on thin margins, even a modest fraud rate can erode profitability faster than any competitive price pressure. Understanding how to identify, intercept, and structurally prevent COD fraud is therefore not a compliance exercise; it is a core business capability.

What COD Fraud Is and How It Works in Indian E-Commerce

COD fraud is any behaviour where a buyer places a cash-on-delivery order without a genuine intention to accept and pay for the shipment. In the Indian context, it manifests in several distinct patterns that sellers must learn to distinguish.

The most common pattern is deliberate non-acceptance: the buyer is present but refuses delivery, often citing a fabricated defect or claiming they never placed the order. A second pattern is the ghost address order, where an incomplete or entirely fictitious address is provided, making delivery structurally impossible and triggering an automatic return. A third, more sophisticated variant is wardrobing or return abuse, where the buyer accepts the order, uses the product, and then initiates a return under a false pretext — though this is more prevalent on prepaid transactions.

What makes COD fraud particularly damaging is the asymmetric cost structure it creates. The seller pays for forward shipping, packaging, and the opportunity cost of reserved inventory regardless of outcome. When the parcel returns, a reverse logistics fee is layered on top. Multiply that across dozens of fraudulent orders per month and the cumulative drag on gross margin becomes material.

Fraud also clusters geographically and demographically: certain pin codes, first-time buyers with unverifiable contact details, and orders placed during high-discount sale events carry statistically higher risk. Recognising these patterns is the first step toward a systematic defence.

Key Risk Signals That Flag a COD Order as High-Risk

Effective COD fraud prevention begins at the order intake stage, not after dispatch. Sellers who build a checklist of pre-shipment risk signals can intercept the majority of fraudulent orders before a single courier movement occurs.

Phone number quality is one of the strongest individual signals. Numbers that are switched off, do not exist in telecom databases, or belong to virtual SIM services correlate strongly with fraudulent intent. A simple IVR confirmation call or SMS-with-OTP step at order placement eliminates a large proportion of ghost orders instantly.

Address completeness and verifiability is the second critical dimension. Orders missing a house or flat number, a recognisable locality name, or a serviceable pin code should trigger a hold, not immediate dispatch. Cross-referencing the delivery pin code against your logistics partner's serviceability map catches structurally undeliverable orders early.

Buyer history is the most powerful signal for repeat offenders. A buyer whose phone number or email is associated with previous RTO shipments on your platform — or on a shared industry blacklist — represents a known, quantifiable risk rather than a probabilistic one. Investing in a buyer risk score that aggregates order history, RTO rate, and payment mode preference pays dividends over time.

Finally, order profile anomalies — unusually high-value COD orders, multiple orders to the same address within a short window, or orders placed immediately after an account is created — are behavioural flags that warrant additional verification before acceptance.

Verification Workflows That Stop Fraud Before Dispatch

Knowing the risk signals is necessary but insufficient; sellers need operational workflows that act on those signals consistently at scale. Manual review does not scale beyond a certain order volume, so the goal is to build a tiered verification system where human attention is reserved for genuinely ambiguous cases.

The first tier is automated OTP or IVR confirmation. Any COD order above a defined value threshold, or from a first-time buyer, should trigger an automated call or SMS requiring the buyer to confirm the order. This single step eliminates orders placed accidentally or by minors, and deters low-effort fraudsters who rely on anonymity.

The second tier is address enrichment and pin-code validation. Integrate your order management system with a pin-code serviceability API so that incomplete or unserviceable addresses are flagged before the order enters the picking queue. Where addresses are ambiguous, a brief outbound call from your customer support team to confirm landmarks adds minimal cost but substantially reduces failed delivery attempts.

The third tier is selective COD acceptance based on risk score. Rather than accepting or rejecting orders in binary fashion, sellers can offer high-risk buyers a prepaid conversion incentive — a small discount or free shipping — that simultaneously reduces fraud exposure and improves cash flow. Buyers with genuine intent nearly always accept a reasonable prepaid offer; those with fraudulent intent typically abandon.

Documenting every verification interaction creates an audit trail that is useful both for internal learning and, where applicable, for filing complaints with platforms or authorities.

Building a Buyer Blacklist and Using Industry-Wide Tools

Individual blacklisting is the natural output of a mature verification workflow, but its value multiplies when sellers participate in shared fraud intelligence networks. The Indian e-commerce ecosystem has developed several mechanisms — at the logistics aggregator level, marketplace level, and through third-party data providers — that allow sellers to cross-reference buyers against a consortium of RTO and fraud histories.

A seller-maintained blacklist should capture the buyer's phone number, email address, and delivery address (including pin code), along with the nature of the fraud and its date. This structured record enables automated blocking at checkout rather than requiring manual review of every repeat order. Most modern order management systems and e-commerce platforms support custom blocklist rules that can trigger on phone number or email match.

Participating in logistics aggregator RTO databases is a complementary step. Shiprocket and similar platforms maintain aggregated delivery performance data across their seller networks. Sellers who share return data contribute to — and benefit from — a collective intelligence layer that individual blacklists cannot replicate.

It is important to apply blacklists with appropriate governance: a buyer incorrectly flagged loses access to legitimate purchases, creating customer service liability. Blacklist entries should be reviewed periodically and should require corroboration from more than one fraudulent event before permanent blocking is applied. A probationary state — where the buyer is required to prepay — is often a more proportionate and legally defensible response than outright blocking on a first incident.

Common Mistakes Sellers Make in COD Fraud Management

Even sellers who are aware of COD fraud risks often undermine their own defences through predictable operational mistakes. Understanding these failure modes is as important as knowing the best practices.

The most common mistake is acting only after the return arrives. Retroactive cancellation of fraudulent orders after the parcel has shipped recovers nothing — the forward logistics cost is already incurred and the inventory is in transit. Effective fraud prevention is entirely a pre-dispatch activity.

A second frequent error is applying verification universally but superficially. Sending an OTP to every buyer regardless of risk level increases friction for genuine customers, raising cart abandonment, while doing nothing to stop sophisticated fraudsters who simply intercept the OTP on a real number. Risk-tiered verification — lighter for established buyers, heavier for new or flagged accounts — balances security against conversion rate.

Sellers also routinely underestimate the cost of a single RTO. They calculate the reverse logistics fee but overlook the forward shipping cost already paid, the re-packaging labour, potential product damage, and the working-capital impact of funds not received. Building a true per-RTO cost model that captures all these components often reveals that even a low fraud rate is destroying a disproportionate share of net margin.

Finally, many sellers treat COD fraud as an external problem to be solved by their logistics partner or marketplace, rather than a first-party risk management responsibility. Platforms and couriers can assist, but the seller's own data — order patterns, customer history, address quality — is the most actionable intelligence available, and only the seller controls how it is used.

Building a Long-Term COD Risk Policy for Sustainable Growth

Tactical interventions reduce fraud in the short term, but sustainable protection requires a formalised COD risk policy that encodes rules, thresholds, and responsibilities into repeatable processes. Without this, fraud prevention reverts to ad-hoc decision-making whenever staff changes or order volumes spike.

A robust policy document should specify: which order attributes trigger automatic verification, what value threshold separates low-risk from high-risk COD orders, who has authority to override a hold or blacklist entry, how frequently blacklists are reviewed, and how fraud loss data feeds back into policy updates. This governance structure turns fraud prevention from an individual skill into an institutional capability.

The policy should also address the COD-to-prepaid conversion strategy explicitly. Defining which customer segments to target for prepaid nudges — new buyers, high-value orders, repeat RTO buyers — and what incentives are permissible ensures that the conversion effort is consistent and measurable rather than opportunistic.

As a seller's order volume grows, the economics of investing in machine-learning-based fraud scoring improve. At scale, automated models that ingest dozens of order attributes and return a real-time risk score outperform manual checklists. Many logistics platforms and fraud prevention SaaS providers offer APIs that integrate into existing checkout flows with relatively low engineering effort.

Finally, sellers should treat their RTO rate as a primary business metric, reviewed weekly alongside conversion rate and gross margin. A rising RTO rate is an early warning indicator of fraud exposure increasing; catching it early allows policy adjustments before losses compound into a structural problem.

Methodology

Figures reflect orders on the Shiprocket network over the trailing 30 days unless a period is stated. Order-volume figures are indexed to the leading city within each tier (= 100), not absolute counts. AOV, RTO and prepaid share are tier averages. Any current, incomplete month is excluded from trend charts. Data via the Commerce Graph over Shiprocket’s Sense APIs.

Frequently asked questions

What is COD fraud and how does it affect Indian e-commerce sellers?

COD fraud occurs when a buyer places a cash-on-delivery order with no genuine intention to accept and pay for it at delivery. For Indian sellers, the impact is direct and financial: they bear forward shipping costs, packaging, and inventory holding costs for every fraudulent order, then pay reverse logistics fees when the parcel returns. Because payment is collected at the door, the seller has no financial protection before the delivery attempt occurs, making pre-dispatch fraud detection the only effective defence.

How can I verify a COD order before dispatching it?

The most effective pre-dispatch verification steps are: sending an OTP or making an automated IVR call to confirm the buyer's phone number and order intent; validating the delivery address against a pin-code serviceability database; and cross-checking the buyer's contact details against your internal RTO history or a shared industry blacklist. Applying these checks in a risk-tiered manner — heavier scrutiny for new buyers and high-value orders — minimises friction for genuine customers while intercepting the majority of fraudulent placements.

What are the most common signs that a COD order might be fake?

Key red flags include: a phone number that is switched off, non-existent, or unresponsive to confirmation calls; an incomplete or unverifiable delivery address lacking a house number or recognisable locality; a buyer account created very recently with no order history; unusually high-value orders placed on COD from an unverified buyer; and multiple orders placed to the same address in a short window. Any combination of two or more of these signals warrants a verification hold before the parcel enters the dispatch queue.

Can I blacklist a buyer who repeatedly refuses COD deliveries?

Yes, sellers can and should maintain a blacklist of buyers associated with repeated non-acceptance or fraudulent orders, captured by phone number, email, and delivery address. Most e-commerce platforms and order management systems support custom block rules that prevent blacklisted contacts from placing future COD orders. A proportionate first response is to require prepayment rather than outright blocking, which preserves access for buyers who may have legitimately changed their minds while eliminating their ability to generate fraudulent COD shipments.

How do I convert high-risk COD buyers to prepaid without losing the sale?

Offer a targeted prepaid conversion incentive at the checkout or order confirmation stage — such as a modest discount, free shipping, or an extended return window — that makes the prepaid option genuinely attractive. Buyers with real purchase intent respond well to financial incentives and typically convert without friction. Fraudulent buyers, who have no intention of accepting the parcel, almost always abandon rather than commit payment upfront. This makes the conversion offer a dual-purpose tool: it improves cash flow for genuine orders and automatically filters out a significant share of fraudulent ones.

What is an RTO and how much does it actually cost a seller?

RTO stands for return-to-origin, meaning a shipment that could not be delivered and is sent back to the seller. The true cost of an RTO is higher than most sellers account for: it includes the forward shipping fee already paid, the reverse logistics charge, re-packaging labour and materials, potential product damage during transit, and the working-capital impact of delayed revenue recovery. Sellers who calculate only the reverse logistics fee routinely underestimate how badly a high RTO rate damages net margin, which is why tracking RTO as a primary metric — not an afterthought — is essential.

Should I stop offering COD altogether to prevent fraud?

Removing COD entirely is rarely the right answer for Indian sellers, particularly those serving tier-2 and tier-3 markets where COD drives a large share of genuine purchase intent. A more calibrated approach is to offer COD selectively: restrict it for first-time buyers above a certain order value, require verification for high-risk pin codes, and reserve outright COD blocking for confirmed fraudulent accounts. Eliminating COD broadly sacrifices legitimate revenue to avoid a problem that targeted verification and risk scoring can address more precisely.

How does sharing RTO data with logistics partners help prevent COD fraud?

Logistics aggregators like Shiprocket maintain delivery performance databases that aggregate RTO and non-acceptance data across their entire seller network, creating a collective intelligence layer no individual seller can replicate alone. When a fraudulent buyer's phone number or address appears in your return data and you share it with your logistics partner, that information can flag the same buyer attempting orders through other sellers on the same network. Participating in this ecosystem both contributes to and draws from a shared defence, making repeat offenders progressively harder to exploit across multiple merchants.