Urgent.News

What's breaking now, across thousands of outlets.

Tech

What a courier success rate actually tells a cash-on-delivery seller

75%, 45%, and the two-parcel trap: turning one number into a shipping decision. In Bangladesh, most online orders are paid in cash on delivery. When a parcel comes back, the seller pays the delivery charge, the return charge and the time. So before confirming an order, many sellers look up the customer's phone number in a courier fraud checker and see a success rate: the share of that number's…

In Bangladesh, the majority of online purchases are settled with cash on delivery. When a shipment is returned, the seller must absorb the delivery and return fees, plus any additional time charges. Before finalizing an order, many merchants refer to the customer's phone number in a courier fraud checker to find the success rate: the percentage of that specific number's earlier shipments that were successfully delivered.

This data is valuable, but its interpretation can lead to different actions. The WooEasyLife checker categorizes results into four groups: 75% or higher (green): proceed as normal. Even for substantial orders, a single phone call to verify the customer's details is still advised. Between 45% and 75% (amber): mixed history. It's prudent to confirm the customer's name, address, and delivery time over the phone.

For high-value items, requesting the delivery charge beforehand might be beneficial. Below 45% (red): more than half of the customer's past parcels were returned. Rather than shipping without prior confirmation, it's wise to avoid placing orders outright. However, never disregard the customer without prior communication. A lack of history: this typically pertains to a new customer or a previously unknown phone number.

While not necessarily a cause for concern, routine checks should still be conducted. The two-parcel conundrum: percentages can be misleading when based on limited shipments. A 50% failure rate could stem from one return out of two parcels or ten returns out of twenty, both representing the same customer. Always consider the total number of parcels alongside the percentage.

Not all couriers are the same: a customer might have a clean delivery history with one carrier but a high failure rate with another. Relying solely on a single courier's statistics can lead to an incomplete picture. Remember, a ratio is merely a signal, not a definitive verdict. Shipments can be returned for various reasons, including incorrect addresses, disconnected phones, or delayed deliveries.

A low success rate is simply an indication that extra precautions are warranted before shipping. It does not inherently reveal anything about the individual's character.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I built a cross-API rate limit reference because I was tired of guessing

I kept hitting 429s on APIs I use daily. Every time, I'd search "Stripe rate limit" or "OpenAI rate limit" and land on a docs page that told me about one API, in one tier, with no error shape and no…

  • Developer created cross-API rate limit reference to avoid guessing limits.
  • Documented maximum requests per minute (RPM) and transactions per minute (TPM) for each API tier.
  • Included retry logic and JSON structure of 429 response with Retry-After header.

After the SOC Assessment: Common Findings and How to Fix Them

After the SOC Assessment: Common Findings and How to Fix Them _ Got your SOC assessment report back? Here are the findings that show up most often and a practical plan to remediate them._ The report…

  • Organize SOC assessment findings into high-risk/low-effort and high-risk/high-effort categories
  • Implement quick wins like updating contact info and confirming vital log sources
  • Establish basic metrics (detection time, response time) for current capabilities

More from Thursday 5 November →