COD without the returns bill.
Every COD attempt is scored 0–100 in milliseconds — network history, address quality, velocity and location — then your rules decide: allow, take an advance, or block.
- Risk score 0–100 on every COD attempt
- Allow / partial-COD / block per band
- Pincode, state, product, collection gates
- Same-day COD velocity cap
- NDR queue + decision simulator
- ✓ 6 delivered on network, 0 RTO
- ✓ Complete address, residential IP
- ✓ Normal checkout velocity
- ✗ 2 RTOs on network, 0 delivered
- ✗ 3rd COD attempt today
- ✓ Address looks complete
A risk engine with real memory
The score is built from what the network already knows: past RTOs, delivered orders, paid orders, failed payments — plus live signals from this attempt.
Network reputation
A serial returner is flagged on your store even if they've never bought from you.
Address & device signals
Gibberish addresses, datacenter IPs, IP-vs-state mismatch, checkout velocity, OTP hammering.
Email-aware identity
Phone-switchers are caught by email history; per-customer allow/block overrides beat everything.
Your rules, graduated
Risk bands map to actions — and hard gates run regardless of score.
Per-band actions
Low → allow. Medium → your choice. High → partial-COD advance or full block.
Caps
Order-value min/max, cart item-count limits, and a same-day COD cap per phone.
Geography & product gates
Pincode (exact or prefix), state, product and collection blocks — each with its own action.
Operate it, don't guess it
The RTO suite shows where returns actually come from and lets you test every change before shoppers feel it.
RTO breakdowns
Return rates by pincode, state, product and courier — next to the rule that fixes each.
NDR rescue queue
Undelivered orders surface with call/WhatsApp actions while they can still be saved.
Decision simulator
Enter a phone, pincode and cart — see the exact verdict and every signal behind it.
Close the loop before dispatch
The riskiest moment for a COD order is the gap between placing and shipping. IndiSell uses it.
COD confirmation
Confirm every COD order on WhatsApp, SMS or email before it ships — with in-chat Confirm / Cancel buttons.
Cancellations teach the engine
A shopper who cancels at confirmation never costs you a shipment — and their next attempt scores accordingly.
Outcomes close the loop
Delivered and RTO results flow back automatically, so reputation reflects reality, not first impressions.
Three steps. About a day.
Turn on scoring
Every COD attempt gets a 0–100 score from day one — network history included.
Set bands & gates
Choose actions per risk band; add pincode, state, product and value gates.
Test, then trust
Run the simulator on real inputs before shoppers feel a change — then watch RTO fall.
Common questions
Will it block my good customers?
Repeat buyers with delivered history score low and sail through. And a one-click 'always allow' override exists for any customer the engine gets wrong.
What's partial COD?
The shopper pays a small advance online and the rest on delivery — commitment without losing the COD comfort. It's the default action for risky-but-not-hopeless attempts.
The rest of the toolkit
Redefine your checkout.
See it live on your own store — a private preview link runs the real checkout for you before a single shopper sees it.