Returns split into yours and not yours
Transit damage, counterfeits, a wrong item sent and failed deliveries are counted and set aside. Only returns a product fact could have prevented are compared.
Find the missing facts your returns are telling you about
Send your order history with the reasons people gave. We join it to your catalogue, show which missing product information goes with returns, and after a repair, whether that slice of returns actually moved.
Your returns already say what the listing left out
Every return comes with a reason: too large, not as described, does not work with my device. Most teams read those as one rate to drive down, and the reasons sit in a report nobody joins back to the product page.
Some returns are about the parcel, the courier or a buyer who changed their mind, and no listing change touches them. Others are about a fact the shopper needed and could not find: the dimensions, the compatibility, the material. Those are the ones a better product page could have prevented, and they are the only ones we count.
Not every return is yours to fix. The ones that are, the listing could have prevented.
A return rate says something went wrong. The reason says what to fix
Read against the products missing the fact it names, a return reason becomes a repair list.
Return rate
Illustration- Dimensions
- Compatibility
- Material
- Transit damage
- Failed delivery
How does Return Verification work?
Three steps, on data you already have. Nothing goes on your site.
01You
Export orders and returns
One category of your catalogue, and six to twelve months of orders with the return reason. No names, phone numbers or addresses: a file that carries them is refused.
02Us
We join returns to the evidence
Each reason is read for the product fact it names. We compare return rates between products that record that fact and products that do not, within the same brand and price band, and say plainly when there are too few orders to tell.
03Both
Repair, then verify
After your team fills the gap, the repaired products are compared with similar ones that were not repaired, over the same weeks, so a season or a promotion does not take the credit. Share your costs and the verified change is valued with your numbers.
What you get
The facts that go with returns, ranked
For each attribute, the return rate where it is missing against where it is recorded, with an interval and the one sentence the result supports. An association, never a claimed cause.
Proof a repair moved the right returns
A matched comparison against unrepaired products over the same period, with a check that the two were moving together before the repair.
Value at your own costs
Only a verified reduction is valued, only with the costs you give us, and net of any orders the repair may have cost. We never estimate your logistics.
Ranking for purchases that stay bought
With the Decision API, the same history can rank products by how often they come back for a fixable reason. It is off until you send history, and a share of shoppers never sees it.
What Return Verification will and will not do
What this does
- Show which missing product facts go with returns in your own order history
- Verify whether a repair moved the returns it was meant to move
- Value a verified change with the costs you give us
- Say when there are not enough orders to tell, instead of guessing
What it does not do
- Promise fewer returns. Nothing has been measured on your orders yet, and a result from another shop is not evidence about yours
- Treat every return as fixable. Transit damage, fraud and failed deliveries are not product information
- Predict which shopper will return something. It reads products and reasons, not people
- Cut returns at any cost. A clearer listing can lose an order that would have been kept, and the valuation shows that rather than hiding it
The ones that decide it
What data do you need?
One category of your catalogue and six to twelve months of orders: the product, the order date, the return date, the return reason, and the payment method if you have it. No personal data of any kind.
Our marketplace's return reasons are vague. Does that matter?
Yes, and we measure how much. A code like 'return in original or sealed condition' mixes a change of mind with a size problem. Where a buyer's comment or the marketplace's own reassessed reason exists, we use it, and the report shows how much of your return volume the codes leave unclear.
How is this different from Decision Verification?
Decision Verification re-measures your catalogue: can it now answer what shoppers ask. Return Verification checks the outcome that costs you money: did the returns that missing fact went with actually fall.
Do you need access to our store?
No. It runs on exports. If you later report order outcomes through the API, the same analysis keeps itself current.
Is it a forecast?
No. It looks back at returns that happened and tells you which listings to fix. We do not sell return prediction.
Start with the returns you already have
One category, its orders and the reasons people gave. The first answer comes from a file.
Talk to us
Nothing is priced until a pilot has run on your own orders.