Returns show up too late
Returns come back weeks later, after the monthly report has gone out. Last month's revenue always looks higher than it was, and profit gets revised after decisions have already been made.
Solutions by problem
A returned order costs shipping twice, loses the marketplace fee and sometimes the goods too. DataxLand calculates return rate, cancellation rate and return costs by channel, product and month, then puts them next to profit after fees so you see how much returns really take.
Free plan with no time limit · No card required · Sample workspace ready in minutes
Returns come back weeks later, after the monthly report has gone out. Last month's revenue always looks higher than it was, and profit gets revised after decisions have already been made.
The shop-wide average return rate hides the handful of items with problems in their description, sizing or packaging.
Return shipping, handling fees and damaged goods have no line of their own in the settlement file. Add them up by hand and it's easy to miss half the cost.
Every big promotion brings a wave of return requests. Without putting ticket counts next to order counts, it's hard to tell whether support is overloaded or a product is faulty.
Si answers with approved metrics, their source and confirmation level.
Definitions come from the analytics packs; Si, dashboards and reports use exactly these.
| Metric | Definition | Unit |
|---|---|---|
| Return rate | Returned orders divided by valid orders.= returned_orders / Valid orders | Ratio (%) |
| Return cost | Return shipping cost borne by the shop. Does NOT include refunds to buyers (already deducted in net revenue). | Currency |
| Cancellation rate | Cancelled orders divided by total orders.= cancelled_orders / all_orders | Ratio (%) |
| Valid orders | Orders that were not cancelled (standard status other than cancelled). | Count |
| Net revenue | Line value after line discounts and allocated order vouchers, minus refunds to buyers. Refunds are deducted only here. | Currency |
| Seller-paid shipping cost | Outbound shipping cost paid by the shop, allocated to lines by line revenue. | Currency |
| Net profit after fees and ads | Net revenue received minus COGS, marketplace fees, payment fees, shipping, return costs and advertising.= Contribution margin - allocated_ad_spend | Currency |
| Support tickets per 100 orders | Order-linked support tickets divided by valid orders, times 100. Shows how many tickets there are for every 100 orders.= Order-linked support tickets * 100 / Valid orders | Number |
| Order-related ticket share | Support tickets linked to an order divided by all support tickets created in the period.= Order-linked support tickets / Support tickets | Ratio (%) |
Connect your marketplaces or upload order files with delivered, cancelled and returned statuses; the status table is standardised by the industry pack.
Si proposes which statuses mean returned and which mean cancelled; adjust them if a marketplace uses different names, then approve.
Set thresholds for return or cancellation rate; when refreshed data crosses one, an alert goes to Telegram or Slack.
On each refresh, orders are updated to their latest status from the source and metrics are recalculated for the period of the order. Last month's figures can therefore change when new returns arrive, and the next build reflects that.
Yes, if your source has a return reason column. You can then filter and ask Si by reason like any other dimension; if not, the metrics still work by product and channel.
Yes, if the tool is in the connector catalogue or can export files. With tickets tagged by order ID you get tickets per 100 orders and the share of tickets about orders.
Free plan with no time limit · No card required · Sample workspace ready in minutes