Module · Add-on

Find out what a return actually cost you — before the marketplace's settlement report does

Log every return and RTO shipment, record what actually came back at QC, and upload your settlement data to reconcile against it. A return that was never paid out gets flagged automatically — not buried three tabs deep in a spreadsheet.

Revenue leak flagged
Order ORD-1002 · SKU SKU-B
Unpaid return

Return was not paid out — net bank amount was zero or negative.

Amount ₹500.00
Illustrative — flags are generated from your own settlement data
What's actually included

Return tracking, QC, and reconciliation that catches what a spreadsheet misses

Every return logged from pickup to warehouse, QC recorded at intake, and settlement data reconciled against it automatically — with the one insight that actually matters surfaced first: was this return paid for, or not.

Return & RTO tracking

Log every return and RTO shipment by order, channel, courier and AWB — with a status you actually update as it moves.

Inbound QC at intake

Record the actual condition and quantity of what came back — good, damaged, missing parts, wrong item — the moment it's inspected.

Settlement reconciliation

Upload your Amazon or Flipkart settlement data and it's matched against your orders automatically — re-uploads skip rows you've already imported.

Unpaid returns, flagged automatically

A return where the net bank amount came in at zero or negative is flagged the moment its settlement row is imported — not something you have to go looking for.

Missing-settlement scan

On demand, check for returns that were QC'd weeks ago but never showed up in any settlement file at all — a different kind of leak than an unpaid return.

Track leaks to resolution

Every flag stays open until you mark it recovered or dismissed — an audit trail, not a one-time alert that disappears.

How it works

Four steps from a return landing to a flag resolved

1

Log the return

Channel, order reference, SKU, courier and AWB — as soon as a return or RTO is on its way.

2

Log QC on arrival

Condition and quantity received, recorded against the shipment the moment it's inspected.

3

Upload settlement data

A CSV in Opsetu's normalized format — matched against your orders and returns on import.

4

Review flagged leaks

Unpaid returns surface automatically — mark each one recovered or dismissed as you work through it.

Pricing

Start free, see your own numbers before you decide

Free trial — no card required

Log real return shipments and upload a real settlement file to see what it actually finds, before committing to anything.

Start your free trial
Questions

Before you upload real settlement data

Not yet — today it reads Opsetu's own normalized CSV format (order reference, SKU, row type, amounts). A direct adapter for raw Amazon/Flipkart export files is on the roadmap; for now you map your settlement data into the provided column format before uploading.

By the net bank amount on that return's settlement row — not just by whether it's labelled a return. A return that still paid out in full (common when a courier or warehouse is at fault) isn't flagged; one where the net amount was zero or negative is.

Rows already imported are skipped — you'll see how many new rows were actually added, and no duplicate leak flags get created for rows you've already reconciled.

Courier SLA auditing, automated NDR calling/IVR, and fraud or RTO risk scoring aren't part of this yet — they're roadmap items, not silently missing features.

See what your own returns data flags

Start a free trial and upload a real settlement file — the fastest way to know what's actually going unpaid.

Start your free trial