LOGISTICS · INTELLIGENCE

Stop the RTO bleed —
make couriers pay.

Every RTO is double freight and working capital locked in a truck for two weeks. ShipSense scores the risk before you ship, catches fake "customer unreachable" NDRs, and claws back what couriers owe you.

Get your free 7-day RTO auditBook a 15-min call →See how it works ↓
▶ THE TRIALone parcel · one night · scroll the whole story
COD-dominant
Indian e-com
20–30%
RTO on COD
₹100–150
cost per RTO
Industry benchmarks — your real numbers may differ.
REASONING ENGINE
PRODUCT PREVIEW
#INV-48219 · ₹1,240 · COD
560001 · Bengaluru, KA
›reading address tokens…
›matched 19,297 official pincodes
›560001 · n=42 → band 24–41% · never a bare number
›building density · high · flood MED
›12 NDRs · same timestamp → FAKE NDR
›evidence pack compiled · dispute filed
›RTO 0.82 → HOLD before dispatch · EV +₹37
EXPECTED-VALUE DECISION
HOLD → review before dispatch
Fake NDR · evidence builtRecovery · dispute raised
LIVE ENGINEDEL · 110001✓ delivereddemo
WHY SHIPSENSE
No fake metrics. No fabricated logos. Real numbers only.
🔒
0% courier-funded
Structurally independent
∑
Math-first, not magic
Bayesian · isotonic-calibrated
📍
Built in Mumbai
For India's D2C logistics
🔢
5 founding pilot slots
Founding cohort · early access
5 founding pilot slots openfounding pilots lock ₹9,999/mo + 12.5% for 24 months
Claim a slot →
THE PROBLEM

RTO is the silent tax
on Indian D2C.

~60%
of Indian e-com orders are COD
Industry benchmark · COD-dominant market · your split may differ
~25%
of COD orders return as RTO
Industry benchmark · ₹100–150 per RTO · your rate may differ

Every RTO means double freight, two weeks of blocked working capital, and dead packaging — with the courier writing their own failure report.

💡At 1,000 COD orders/month, that's ₹31,200 leaking silently every month — before ShipSense.Arithmetic on the industry benchmarks above — not a ShipSense measurement. Your audit returns your own figure.
ONE ORDER · FOUR MOMENTSILLUSTRATIVE
📦
COD order dispatchedWHAT EXISTS
Bluedart · 560001 · Bengaluru · standard route assigned
🚨
12 NDR attempts · same timestampIN PROCESS
🔍
ShipSense flags fake NDRTHE DECISION
✅
Freight recovered · capital freedYOUR SAVINGS
Click any step to explore⏸ pause
// TRY IT NOW · NO SIGNUP

Drop your shipment CSV.
See your RTO bleed in 10 seconds.

A quick estimate from your own orders — no number tweaking, no sales call. Parsed entirely in your browser. Nothing is uploaded or stored.

📄
Drag a CSV here, or click to upload
Any shipment export — Shiprocket, Delhivery, your panel. We look for date, amount, payment mode & status.
🔒 100% in-browser
● AWAITING YOUR FILE
Your bleed number appears here the instant you drop a file or run the sample.

This is the rough cut. The free audit returns your exact number — and which of these NDRs don't survive a timestamp check.

Get my exact number — free audit →
// THE_DECISION_ENGINE

Four moments.
One outcome: your money back.

No dashboards. No manual work. ShipSense runs quietly alongside every order — and acts when it matters.

📦
WHAT EXISTS
Order arrives
A new COD order enters your system. Address, pincode, buyer details — all captured.
ShipSense pulls the order context automatically — no integration overhead.
01
⚡
IN PROCESS
ShipSense analyzes
02
✋
DECISION
One clear call
03
💰
SAVINGS
Working capital freed
04
Click any step · or watch it run
LIVE ORDER FLOW
📦
WHAT EXISTS
Order arrives
ACTIVE
⚡
IN PROCESS
ShipSense analyzes
PENDING
✋
DECISION
One clear call
PENDING
💰
SAVINGS
Working capital freed
PENDING
THE REASONING ENGINEevery verdict in this flow comes with plain-language reasoning inside the product
// GAWAH · CUSTOMER WITNESS · LIVE CHANNEL

The courier says one thing. Gawah asks your customer.

Gawah — your customer becomes the witness. On a suspicious failed delivery, ShipSense sends one WhatsApp question. The one-tap reply becomes timestamped evidence from the only person who was actually at the door.

WHATSAPP · GAWAHILLUSTRATIVE
Hi Rahul, we tried to deliver your order SS-48219 today but the courier marked it as not delivered. Quick check — did a delivery agent actually call or visit you?
No one contacted me
Asked to reschedule
I refused the order
label: customer_denied_contactEVIDENCE
courier said “unavailable” · the witness says no one came → contradiction on record
● THE WITNESS LOOP
01
Courier logs an NDR
“customer unavailable” · the claim goes on trial
02
Your customer gets one WhatsApp question
did anyone actually call or visit? One tap to answer
03
The tap becomes sworn evidence
timestamped contradiction, weighted by reply speed
04
Gawah feeds the detector + dispute
every answer makes the fake-NDR engine sharper
Built & verified: approved WhatsApp templates in English & Hindi, a registered business sender, and the reply-to-evidence pipeline — verified end to end. It goes live on your orders the moment you connect; replies land as labelled data in your dashboard, never mocked.
Conversation above is illustrative · your customers see your brand.
THE INTERVENTION

The cheapest RTO is the one that got paid for before it shipped.

COD orders come back at a multiple of the prepaid rate. Rather than quote you somebody else's festive-quarter statistic, the free audit shows you your own COD-versus-prepaid split first. Then this engine goes after the gap: it moves the riskiest COD orders to prepaid before dispatch, and measures whether that actually worked.

01
Every COD order is scored before dispatch
Six rules decide whether an order is even a candidate: it is COD, it sits above your risk threshold, the order value clears the economics, there is dispatch runway left, there is a contactable number on file, and no offer has already gone out.
02
Eligible orders are split — on purpose
Assignment is deterministic, from a hash of the order id and your own salt. Reproducible, auditable, immune to a retrying job re-rolling the dice. A fifth of eligible orders are held back and touched by nothing.
03
One WhatsApp message, in the customer's language
Hindi, Marathi or English, chosen from the delivery state with your override. The order is framed as already packed — because it is. A UPI link, a small incentive, priority dispatch. One reminder if there is no action, and only one: a second reads as harassment and burns your sender reputation.
04
Paid flips to prepaid. Unpaid ships as COD.
Nothing implies the order is at risk of cancellation, because that is both untrue and damaging to your brand. The customer who ignores the message gets exactly the delivery they already asked for.
05
The held-back fifth is what makes the number real
Those orders ship untouched and some of them fail. That is a cost we choose. Without them, any rupee figure we quote you is unfalsifiable — you could not tell our intervention apart from a good month.
WHERE THIS FEATURE USUALLY GOES WRONG
The incentive is derived, not guessed
It comes off your courier rate card and your own margin, and it is hard-capped at half the expected gain on that order. If the discount plus gateway fee would exceed the order's gross margin, we skip the order instead of quietly losing you money.
Higher margin means we nudge less
Converting a healthy order you would have kept anyway is margin destruction wearing a dashboard. The engine asks for a payment on fewer orders as your margin rises, not more.
Nothing sends until you switch it on
Per-merchant kill switch, an explicit send allowlist, and a hard block on contacting anything in the held-back group. All three are on by default.
CURRENT STATUS
The rails are live and tested end-to-end on synthetic orders. No consignee has been contacted yet — sending stays behind a kill switch until a merchant's own holdout is configured. When we show you a rupee figure, it will have come from your shipments, not ours.
How we measure the result →
// HAZRI · REACHABILITY CHALLENGE

A courier can argue with a witness. It cannot argue with a number it never saw.

Gawah asks your customer what happened. Hazri asks their handset to prove it was reachable. ShipSense publishes the fingerprint of a six-digit code to an append-only ledger before the code is ever sent — then asks the consignee to type it back. A number nobody could guess, returning from a phone the courier logged as unreachable.

WHATSAPP · HAZRIILLUSTRATIVE
step 1 · ledger
fingerprint written & anchored — before the message is sent
The courier reported nobody was available. If you were, reply with this code so we can put it on record: ••••••
••••••
fingerprint matches · committed before reply
the handset the courier called unreachable returned a code it could not have guessed
● WHY IT HOLDS UP
01
Committed before it was sent
the fingerprint is written to an append-only ledger first — the order is checkable, not asserted
02
Anchored outside ShipSense
the ledger head is published to an independent third-party timestamp log
03
Signature-verified on the way back
every inbound reply is checked against Twilio's HMAC before it counts
04
Recomputable by the courier
the pack ships the inputs — they can rebuild the hash themselves and try to break it
What it does not prove: that a rider never came to the door. Hazri establishes that the consignee's committed number responded at a stated time — nothing more. An echo that arrives long after the logged attempt is carried as context, not as a rebuttal. Absence of a challenge is never evidence against a courier.
EVIDENCE STRENGTH · FOUR CUMULATIVE RAILS
Each rung requires every rail below it. Evidence collected out of order credits nothing — a recording with no opener receipt does not make a case bronze.
BRONZE
Opener receipt
Our WhatsApp reachability message reached the customer — delivered, read, or replied to.
SILVER
+ verified echo
Bronze, plus the customer's own number typed back the committed code inside the evidentiary window.
GOLD
+ voice recording
Silver, plus a recorded call with a denied-contact outcome — playable directly from the pack.
PLATINUM
+ sealed custody
All three rails, with the recording consent-flagged, hashed and vaulted. The difference from gold is custody, not content.
NO RAIL YET
Most disputes sit here, and the product says so rather than inventing a grade. Until the opener receipt exists there is no rung to stand on — the pack states exactly which rails are missing and why.
These describe how strongly a dispute is corroborated. They do not assert recovery, outcome, or courier liability — that is for the courier to assess and for you to decide.
CHECK IT YOURSELF

A screenshot can be edited. This can’t.

Anyone can change a photo, a PDF or a screenshot afterwards — and nobody would know. So we built the evidence to tell on itself. You don’t have to trust ShipSense, and neither does your courier.

1
We seal the evidence
The moment a pack is created, we take a fingerprint of it — a code made from the contents themselves.
2
We publish it outside ShipSense
That fingerprint goes into an outside record we cannot edit, delete or backdate. Not even we can rewrite it later.
3
Anyone can re-check it
Our checker rebuilds the fingerprint from scratch and compares. It matches only if nothing changed — one altered character and it fails.
What this means for you: when you hand a courier an evidence pack, they can check it themselves and see it has not been touched since the day it was sealed — including by us. That is the difference between an argument and a record.
Open the free checker →No sign-up, no account. Works for anyone holding a pack — you, your courier, or their lawyer.
Said plainly: this proves the pack has not been altered since it was sealed. It does not, on its own, prove who is right in a dispute — that is what the four rails above are for. Under the hood it is a SHA-256 fingerprint checked against an append-only chain whose head is anchored to a public timestamp log; the checker recomputes it in front of you.
Built & verified: the commit-before-send ledger, the external anchor, the signature check and the reply-to-evidence path all run today, and the full loop has been proven end to end on a real handset in our own testing. It activates on your orders when your pilot starts. No customer results are claimed here — ShipSense has no real shipment book yet, and every figure in the product is labelled with where it came from.
AI VOICE NOTES

A human-sounding nudge, before the parcel moves

ShipSense sends a short WhatsApp voice note in your brand's name — confirming the address, checking availability, or nudging COD to prepaid. Three real samples below.

COD → Prepaid nudge
Tap to hear the sample
Availability check
Tap to hear the sample
Address confirm
Tap to hear the sample

Samples for illustration. Voice notes stay switched off until your pilot starts and you enable them — nothing is sent to your customers before then.

// THE_MOAT

Everyone in your logistics stack is paid by the courier. We're the only one that isn't.

Follow one rupee. Where it's paid decides whose side each player is on — and why no aggregator can do what we do.

The industry standard
Courier
files the fake NDR
commission
Your aggregator
earns on every shipment
Looks away
The ShipSense model
You
the merchant
flat fee
ShipSense
₹0 from couriers
Audits & recovers
▾ THE CONFLICT

Your aggregator takes a cut of every courier shipment. Exposing courier fraud would shrink its own revenue — so the fake NDRs slide through, and you eat the RTO.

Everyone paid by the courier protects the courier. We're the only one paid by you.

Structural independence

We take a flat fee from you and zero rupees from couriers. No volume rebates, no kickbacks — so nothing stops us naming courier fraud.

0% courier-funded
Courier accountability

Fake 'customer unavailable' and 'address not found' NDRs get cross-examined, packed into timestamped evidence packs, and disputed with your courier.

evidence → dispute → ₹ back
Buyer-risk network

A privacy-safe signal that flags repeat COD-refusers across brands. Works on hashed tokens — send hashed numbers and the engine works identically.

cross-brand · privacy-safe
An aggregator that exposes courier fraud loses its courier revenue.
We have no such conflict. You can't out-engineer a moat that's structural.
See it on your data →
// THE_CATEGORY

Three tools fight RTO.
Only one goes after the courier.

Checkout tools work before dispatch. Workflow tools work after NDR. Neither touches the gap between — where couriers write their own failure reports and your money disappears.

CHECKOUT TOOLS
GoKwik · Razorpay Magic

Filter the buyer

INTERVENES
Pre-purchase

Blocks risky carts and nudges COD buyers toward prepaid. Useful — but its work ends at dispatch.

⚠ No power once parcel leaves warehouse.
NDR WORKFLOW TOOLS
Pragma · Clickpost NDR

Chase the customer

INTERVENES
Post-dispatch NDR

Reattempt prompts and address confirmation flows. They trust the courier actually tried to deliver.

⚠ They believe the courier. ShipSense doesn't.
SHIPSENSEONLY SHIPSENSE
Forensic intelligence layer

Audit the courier

INTERVENES
Post-dispatch · forensic

Assumes the logistics network can be adversarial. Builds evidence. Puts the courier's failure report on trial.

Every failure report gets cross-examined, and the evidence is yours to dispute with.
CAPABILITY
Checkout
NDR Tools
ShipSense
Blocks bad orders at checkout
✓
—
—
Reattempt prompts via WhatsApp
—
✓
—
Address re-confirmation flow
—
✓
—
Detects fake NDR timing patterns
—
—
✓
Builds legal-grade evidence packs
—
—
✓
Files disputes with your approval
—
—
✓
Recovery Wallet — tracks clawed-back ₹
—
—
✓
Courier accountability scorecard †
—
—
✓
Network risk from other brands
—
—
✓
Capabilities covered
2 / 9
2 / 9
7 / 9 ↑
† Courier accountability reporting runs on your own real shipment book. ShipSense does not publish a courier-named accountability figure computed on sample or seeded data — that number appears only once your real shipments back it.
How to read this table. It compares categories of tool, based on each vendor's publicly documented positioning as of July 2026 — not a hands-on benchmark, and not a claim that any named product cannot do a thing. Vendors ship fast and feature sets overlap; if we have a row wrong, tell us and we will correct it. The rows in the ShipSense column describe capabilities that exist in the product today, not results delivered for a customer — ShipSense is pre-pilot and has recovered no money to date.
They reduce the RTO number. ShipSense asks whether the failure was real.
The gap between dispatch and resolution is where your money disappears. That gap is the only thing ShipSense works on.
THE BLEED METER

See what RTO is quietly costing you.

Move the sliders. The bleed is your own arithmetic on industry benchmarks. What ShipSense can claw back is a question for your audit — not something we'll guess at on a landing page.

MONTHLY ORDERS5,000
AVERAGE ORDER VALUE₹1,200
RTO RATE (% OF COD)26%
RTO cost = ₹125/order (₹100–150 industry benchmark midpoint). Slider defaults are benchmarks — replace them with your own figures.
BLEEDING OUT PER YEAR
₹19,50,000
1,300 RTOs/mo × ₹125 × 12 months
your inputs · your arithmetic
HOW MUCH OF IT IS CONTESTABLE
Depends on how many of your failed deliveries were never actually attempted.
We won't put a percentage here. ShipSense has filed no disputes and recovered no rupees yet — no pilot has run. The 7-day audit reads your own NDR log and tells you which failures are contestable and what they're worth.
Get your exact number — free 7-day audit →
THE PROOF

Wemeasuresavingsthehonestway.

A random holdout group ships exactly as before. The rest get scored, held, or converted. We measure the gap. That gap — once it clears 95% confidence — is the only number we will ever report as your savings. We have not run a cohort yet, so there is no number here to show you.

Randomised holdout
Orders are split into control and treatment. Control ships without any ShipSense intervention.
ATE calculation
Average Treatment Effect = control RTO − treatment RTO. Measured on your data, not industry averages.
95% confidence gate
Result is flagged 'calibrating' until the sample is sufficient. We never claim early.
Reported delta only
We report the causal improvement — not your baseline, seasonality, or market shifts.
SAVINGS · CAUSAL PROOF
method: randomised holdout · awaiting first cohort
Control group
ships without ShipSense
—
Treatment group
ShipSense active
—
ATE = control − treatment RTO
awaiting first pilot
no cohort has run — no confidence interval exists yet
SAVED THIS MONTH
—
populates from your holdout
Fee model
flat + share of recovered ₹
Savings report
causal delta only
Pilot fee
paid, not credited
ShipSense has no real shipment book yet. This panel stays empty until your own holdout fills it.
PRICING

A flat fee. Plus a share of what we recover.

A flat monthly fee — invoiced by bank transfer or UPI — plus a share of freight we actually recover for you: 15% on Growth, 12.5% for founding pilots. Recover nothing, and you owe nothing beyond the flat fee. Prices exclude GST. Fair-use limits included: 100 verification calls and ₹300 of AI compute per store per month — we flag you well before you'd reach either. The free audit comes first either way, so you see your bleed before you pay a rupee.

Pilot
3-month founding pilot
₹4,999/mo
Paid, not credited · converts to founding ₹9,999/mo locked 24 months · cancel anytime
✓7-day RTO audit
✓RTO risk scoring
✓COD→prepaid conversion engine
✓Fake-NDR review queue
✓Recovery dispute prep
Get your free audit
RECOMMENDED
Growth
Scaling COD brands · up to 5,000 shipments/mo
₹14,999/mo
Plus 15% of freight we actually recover for you · founding pilots convert at ₹9,999/mo + 12.5%, locked 24 months
✓Everything in Pilot
✓Courier scorecards you can share
✓Priority disputes
✓5 team seats · PDF export
Get your free audit
Scale
5,000+ shipments · multi-brand · API
₹34,999/mo
Flat monthly · custom SLAs
✓Everything in Growth
✓Multi-brand support
✓Buyer-risk network access
✓Dedicated success lead
Get your free audit
Founding pilot promise: convert after your pilot and your rate is ₹9,999/mo + 12.5% of recovered freight, locked for 24 months (list ₹14,999 + 15%) — and if the audit finds nothing worth fixing, we'll tell you that too.
FAQ

Straight answers.

Do I need a Shiprocket account?+

No. ShipSense works off a simple CSV export from whatever you already use. No integration, no migration, no new courier account.

What exactly happens to my customers' phone numbers?+

Here's the actual mechanic, because "we take privacy seriously" isn't an answer. On ingestion the number is one-way hashed onto the shipment record, and the raw number is moved into a separate vault and cleared from the shipment. That vault is locked at the database level — no dashboard, no API key and no logged-in account can read it, including ours. It is reachable only by the service that places a call or sends a WhatsApp voice note, because you cannot dial a hash. Numbers are never used for marketing and never resold. Prefer we never hold a raw number at all? Send them pre-hashed — risk scoring works exactly the same, but voice notes and WhatsApp nudges switch off, because there is nothing left to dial. That's a real trade-off and it's yours to make, not ours. Customer names and emails, if you send them, are stored as you sent them — not hashed — so leave those columns out of your CSV if you'd rather we never saw them. Ask us to delete and we purge the shipment record and the vault together: completed within 7 days, confirmed in writing.

How fast do I see value?+

Seven days. Send last month's shipment CSV and we return a clear audit of where your RTO and NDR money is leaking — before you commit to anything.

What couriers do you support?+

Any of them. ShipSense sits on top of your existing couriers as an independent intelligence layer — we're not a courier or an aggregator, so we work with whatever you ship on.

Does ShipSense have customer results to show?+

Not yet, and we won't pretend otherwise. ShipSense is pre-pilot: no paying customers, no courier disputes filed, no money recovered to date. Every number on this site is either an industry benchmark, clearly labelled as such, or a calculation you ran yourself on your own inputs. The first real result we publish will be a customer's, with their name on it.

// FREE_RTO_AUDIT

Stop guessing. Get your real RTO number.

A free 7-day audit on your own shipment data. No credit card, no rip-and-replace — we read alongside your existing couriers.

✓
Your true RTO % — vs. what couriers report
✓
Your top bleeding pincodes — ranked by ₹ lost
✓
Recoverable estimate — fake NDRs + disputes you can claw back
Request your free audit
Two fields, ~20 seconds — the rest is optional.
No credit card · read-only access · your data stays yours.
EARLY ACCESS · NO CREDIT CARD

Send us last month's shipment CSV.
We'll show you exactly what you're losing — in 7 days.

Early access. No card. If the bleed we find isn't worth it, you walk — no pitch, no pressure.

✓ CSV in · bleed report out✓ 7 days · no Shiprocket account✓ read-only access · your data stays yours
ShipSense

A math-first logistics intelligence layer for Indian D2C. We score RTO before you ship, catch fake NDRs, and recover what couriers owe you.

MADE IN INDIA · MUMBAI
Built by Mohammed Arsh Khan
Founder & Creator, ShipSense
© 2026 ShipSense · Early accessTHE REASONING ENGINE INSIDE

Geist

Inter

Mono

00%
ShipSense
How it worksThe edgeFree toolsPricingFAQ