Customer Verification — OTP, Courier Zones & Call Confirm

Prove phone ownership and use success-rate zones before you ship COD in Bangladesh.

Customer verification for Bangladesh COD orders

Cash on delivery in Bangladesh lets anyone type a random 11-digit number and place an order—no payment, no commitment. Competitors, pranksters, and mistaken buyers create fake COD orders that cost packaging, forward delivery, and return penalties when the real owner refuses the parcel.

Customer verification combines courier success-rate zones (green, yellow, red), checkout OTP, conditional rules, call confirmation, and advance delivery fees so only serious buyers reach your packing bench. This guide shows how to layer those checks in WooEasyLife before you confirm and ship.

Bangla version: Customer verification. Free number lookup: BD Fraud Checker. Full COD system: English WooCommerce guide. Checkout hardening: Fake Order Protection.

Multi-layer customer verification for COD orders
Courier history → OTP/blacklist → call confirm → ship only verified orders

Why verification matters more than manual call confirm

Calling every COD order sounds safe until volume hits 60–100 per day. Staff miss calls, forget notes, and still ship numbers with terrible courier history because the call “felt okay.” Manual confirm alone cannot scale and does not stop prank orders placed with someone else’s phone number.

Automated verification uses data: courier delivery databases show whether a mobile actually receives parcels, OTP proves the buyer controls the number, and conditional rules apply friction only where risk is high. Result: fewer fake orders without slowing every loyal repeat customer.

Measure what fake COD already costs with Return Loss Calculator. Then compare against SMS/OTP spend—most shops save thousands of taka per month. Broader RTS strategy: COD return reduction.

Courier success zones: green, yellow, and red

WooEasyLife checks courier delivery history when a customer enters a mobile number. Green zone (roughly 80–100% success rate): the number regularly receives COD parcels. These orders can confirm and ship quickly—still spot-check very high AOV or suspicious notes.

Yellow zone (50–79%): mixed history. Require call confirmation or OTP before you mark confirmed. Ask product, COD amount, and address aloud; note who called and when so the next shift does not double-dial.

Red zone (under 50%): high return risk. Prompt advance delivery fee, hold the order, or block checkout entirely. Free lookup anytime on BD Fraud Checker before you pack.

OTP verification at checkout

OTP sends a one-time code via SMS or WhatsApp before Place Order completes. Only someone with the phone can finish checkout—prank orders using random or stolen numbers drop sharply.

Flow: customer enters mobile → system sends 4–6 digit code → customer enters code → order saves. Pair with Fake Order Protection for duplicate-number blocks, blacklists, and rate limits on repeat offenders.

Worked example: 50 fake orders × Tk 130 return penalty ≈ Tk 6,500 lost monthly. OTP on high-risk segments might cost Tk 300–400 in SMS—net save often exceeds Tk 6,000. Notification templates and delivery: Notifications automation.

Conditional OTP: verify smart, not every order

OTP on every order adds SMS cost and checkout friction for trusted repeat buyers. Conditional OTP applies verification only when rules fire—keeping conversion healthy while blocking fakes.

Common rules: require OTP when courier success is under 50% (red zone); when order value exceeds Tk 3,000–5,000; when the buyer is first-time on your store; or when the same IP/device places multiple COD attempts in an hour.

Trusted repeat customers with green history skip OTP and checkout faster. Adjust thresholds as you learn your audience. Deep checkout config: Fake Order Protection.

Call confirmation for yellow-zone orders

Yellow-zone buyers need human contact before packing. Call from the order card—WooEasyLife and Mobile app guide support one-tap dial and WhatsApp templates with order ID, product, COD amount, and area.

Script basics: confirm they placed the order, read back address and COD total, and ask when they can receive. If they hesitate or deny ordering, cancel before courier booking. Never auto-ship yellow numbers without a logged confirm.

Team discipline: one owner per order, timestamp notes, no duplicate calls that annoy customers. After verbal confirm, proceed to Courier Auto Entry only if history and notes still look clean.

Advance delivery fee for red-zone customers

Red-zone numbers have a pattern of refused or failed deliveries. Shipping COD anyway sends packaging and forward fees into a likely return. Advance delivery fee (partial or full shipping paid upfront) filters fake buyers who never intended to pay.

Show a clear popup or checkout notice: “This number has low delivery success—pay Tk X delivery charge now to confirm.” Serious buyers pay; prank orders abandon. Combine with OTP for maximum filter on repeat offenders.

Track how many red orders convert versus cancel—tune fee amount so you block fakes without killing legitimate edge cases. Full return math: COD return reduction and Return Loss Calculator.

Verification workflow before courier booking

Recommended sequence: order placed → courier history check (BD Fraud Checker) → apply zone rules (OTP, call, advance fee) → mark confirmed → auto courier entry. Skipping verification because courier API is connected multiplies return loss.

On mobile, review zone flags in Mobile app guide before you tap confirm. Push alerts for new COD and incomplete checkouts via Notifications automation so verification starts within minutes, not hours.

After verification, Steadfast/Pathao/RedX booking from Courier Auto Entry is safe automation—not a substitute for the checks above. Hub overview: English WooCommerce guide.

Next steps: turn verification on today

Checklist: enable BD Fraud Checker lookups → configure conditional OTP and blacklists on Fake Order Protection → set advance fee rules for red zone → train staff on yellow call confirm → connect courier auto entry only after confirm.

Measure baseline return loss on Return Loss Calculator, enable verification, remeasure after 30 days. Start a trial from Pricing. Bangla guide: Customer verification.

Why is OTP required for COD?

Anyone can type a random number. OTP proves ownership. Free history: BD Fraud Checker. Protection: Fake Order Protection.

What are green/yellow/red zones?

Courier success-rate bands—green ships fast, yellow needs call/OTP, red needs advance fee or hold. See COD return reduction.

Should every order use OTP?

Prefer conditional OTP for high-risk, high AOV, or first-time buyers to cut SMS cost and friction.

How do I confirm from mobile?

Use Mobile app guide for push + one-tap call, then approve.

Is this part of a topic cluster?

Yes under English WooCommerce guide. Bangla: Customer verification.

How do I start?

Test BD Fraud Checker → Pricing → enable Fake Order Protection and OTP rules.