Every online seller in Bangladesh who ships cash on delivery has met this customer: they order three items at midnight, confirm enthusiastically on Messenger, and then switch their phone off the day the parcel arrives. The courier attempts delivery twice, the parcel comes back, and the seller pays return charges for a sale that never existed.
This is why a courier fraud check — looking up a customer’s delivery history before you hand a parcel to the courier — has become as routine for careful merchants as confirming the address. In a market where COD still dominates online payments, fraud screening is not paranoia. It is basic cash flow protection.
This guide explains how COD fraud actually works in Bangladesh, how phone-number history checking functions, what fraud checker tools can and cannot tell you, and how to build screening into your daily order flow.
What courier fraud looks like from the merchant side
“Fraud” in the COD context rarely means sophisticated crime. Most of it falls into a few repeatable patterns:
- Prank and fake orders. Someone places an order with no intention of receiving it — sometimes as a joke, sometimes using another person’s number and address so a stranger gets a confused call from a delivery rider.
- Serial parcel refusers. A real customer who orders impulsively and refuses at the door, again and again, across many shops. One refusal is bad luck. A phone number with fifteen refusals across four couriers is a pattern.
- Sabotage orders. Sellers in competitive F-commerce niches report bursts of fake orders placed deliberately to drain their delivery budget. This is hard to prove in any individual case, but the operational damage is identical to any other fake order: you pay forward and return charges for nothing.
- Address games. Deliberately vague addresses (“beside the big mosque, ask anyone”) that guarantee a failed attempt, sometimes combined with demands to reroute the parcel somewhere else mid-delivery.
None of these require the fraudster to gain anything material. That is what makes COD fraud so common: the cost of placing a fake order is zero, and the entire loss lands on the merchant.
The real cost of a refused parcel
Sellers often mentally count only the return charge. The full damage is wider. As an illustrative example, consider a Dhaka-based clothing page shipping a 500 taka product outside Dhaka:
| Cost item | What happens |
|---|---|
| Forward delivery charge | Paid whether or not the customer accepts |
| Return charge | Many couriers bill a return fee on refused parcels |
| Packaging | Poly, tissue, invoice — rarely reusable |
| Product condition | Items come back creased, opened, or shop-soiled |
| Locked capital | The product sat in transit for 5–10 days instead of selling |
| Staff time | Confirmation calls, follow-up, re-listing |
The numbers vary by courier and product, but the structure is always the same: a refused COD parcel costs you two delivery legs plus degraded stock. For a seller running thin F-commerce margins, a modest return rate can quietly erase the profit from many successful orders. We cover the operational fixes in our guide to reducing parcel return rate.
How a courier fraud check works
The core idea is simple: your customer’s phone number has a history.
Every major courier in Bangladesh — Pathao, Steadfast, RedX, Paperfly, and others — records the outcome of each delivery against the receiver’s phone number. Delivered, returned, refused, unreachable. That history exists whether or not anyone looks at it.
A courier fraud check surfaces that history before you ship. There are three ways merchants do it today:
1. Checking inside a single courier’s merchant panel
Some couriers expose a customer success ratio directly in their merchant dashboard or API — how many parcels this number has received versus returned with that courier. It is accurate but only covers one courier’s slice of the customer’s behavior.
2. Using courier fraud checker tools
A category of third-party tools — FraudPeek, fraudchecker.link, and similar services — lets you enter a phone number and see an aggregated delivery record pulled from multiple couriers: total orders, delivered count, returned count, and often a success percentage per courier.
These tools are genuinely useful for a quick pre-ship screen. A number showing 2 delivered and 11 returned across three couriers is a shipment you should not send without advance payment. But treat the output as a signal, not a verdict:
- Data freshness varies. A tool is only as current as its last sync with each courier.
- New numbers show nothing. A fraudster with a fresh SIM looks identical to a first-time genuine buyer.
- Shared numbers mislead. A family member or an office receptionist may carry someone else’s refusal history.
- Coverage is partial. Orders through smaller couriers or a shop’s own riders may never appear.
3. Keeping your own blacklist
The cheapest fraud database is your own order history. Every seller should log refused deliveries with phone number, date, and courier, and check new orders against that list. It is small, but it is perfectly accurate for the fraudsters who target you specifically.
Red flags you can spot without any tool
Before any lookup, certain order patterns deserve a harder confirmation call:
- Multiple high-value items in a first-ever order from an unknown customer
- A delivery address that does not match the phone number’s area, with no explanation
- Refusal to receive a confirmation call, or a number that is off within an hour of ordering
- Urgent pressure to ship today combined with vague address details
- Several orders to the same address under different names or numbers
- Requests to change the receiving number after the parcel is already booked
None of these alone proves fraud. Two or three together justify asking for a small advance via bKash or Nagad before shipping — a request genuine customers increasingly accept, and fake ones almost never do. Our fake order prevention playbook covers this escalation ladder in detail.
Where your own data beats any external tool
External fraud checkers answer one question: has this number burned other sellers? Your own operation answers a better one: what is actually happening to your parcels, right now, by courier, area, and product?
That requires your order and delivery data to live in one place instead of scattered across courier panels and Excel sheets. When a courier runs modern courier management software, its merchants get a merchant panel where every booking, status change, and return is logged against the customer — so a repeat refuser is visible at booking time, not after the third failed delivery.
The same applies on the courier side. Delivery companies using Drix can see refusal patterns across their entire merchant base through reports and analytics: which receiving numbers keep bouncing parcels, which areas return the most COD shipments, which merchants are being targeted. That is intelligence no single seller can assemble alone, and it makes the whole network safer to ship on.
A practical pre-ship checklist
Pulling it together, a lightweight fraud screen for every COD order:
- Confirm the order by phone, not just Messenger — verify product, price, and full address.
- Run the number through a fraud checker tool and your own refusal log.
- For high-value or bulky orders, ask for a partial advance payment.
- Book with complete address details and the confirmed number only.
- Log every refusal with the reason the courier reported.
Five steps, roughly two minutes per order, and they remove the majority of predictable losses.
Fight fraud with better systems, not just suspicion
Fraud screening works best when it is built into the delivery workflow rather than bolted on. Drix is courier management software built for Bangladesh’s COD-heavy market: it gives courier companies full COD management — tracking every taka from the customer’s hand to the merchant’s settlement — and gives their merchants a panel where delivery history, returns, and customer patterns are visible before a parcel ever ships.
If you run a courier or delivery business and want fraud patterns, return rates, and COD reconciliation visible in one dashboard, book a free demo of Drix and see it on your own operation.
