Skip to content

Solutions by problem

Get returns and cancellations under control before they eat your profit

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

What DataxLand solves

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.

No idea which products get returned

The shop-wide average return rate hides the handful of items with problems in their description, sizing or packaging.

Return costs buried in shipping fees

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.

Support swamped after every sale

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.

Ask Si

Si answers with approved metrics, their source and confirmation level.

  • “Which product had the highest return rate in September?”
  • “What share of profit after fees did returns cost this month?”
  • “Which channel's cancellation rate jumped versus last month?”
  • “How many support tickets per 100 orders came in after the last sale?”

Metrics behind this page

Definitions come from the analytics packs; Si, dashboards and reports use exactly these.

MetricDefinitionUnit
Return rateReturned orders divided by valid orders.= returned_orders / Valid ordersRatio (%)
Return costReturn shipping cost borne by the shop. Does NOT include refunds to buyers (already deducted in net revenue).Currency
Cancellation rateCancelled orders divided by total orders.= cancelled_orders / all_ordersRatio (%)
Valid ordersOrders that were not cancelled (standard status other than cancelled).Count
Net revenueLine value after line discounts and allocated order vouchers, minus refunds to buyers. Refunds are deducted only here.Currency
Seller-paid shipping costOutbound shipping cost paid by the shop, allocated to lines by line revenue.Currency
Net profit after fees and adsNet revenue received minus COGS, marketplace fees, payment fees, shipping, return costs and advertising.= Contribution margin - allocated_ad_spendCurrency
Support tickets per 100 ordersOrder-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 ordersNumber
Order-related ticket shareSupport tickets linked to an order divided by all support tickets created in the period.= Order-linked support tickets / Support ticketsRatio (%)

How to start

  1. 1

    Connect orders and statuses

    Connect your marketplaces or upload order files with delivered, cancelled and returned statuses; the status table is standardised by the industry pack.

  2. 2

    Approve how statuses are read

    Si proposes which statuses mean returned and which mean cancelled; adjust them if a marketplace uses different names, then approve.

  3. 3

    Set alerts

    Set thresholds for return or cancellation rate; when refreshed data crosses one, an alert goes to Telegram or Slack.

What you get

  • Return rate, cancellation rate and return costs by channel, product and month, all on one definition.
  • Profit after fees with return costs already deducted, so the monthly figure reflects the cash actually left.
  • Alerts on thresholds or unusual changes, without waiting for the month-end report.

Frequently asked questions

If an order is returned the following month, which month does it count in?

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.

Does DataxLand know why items were returned?

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.

I use a separate customer support tool. Can I combine it?

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.

Try it with sample data first, free

Free plan with no time limit · No card required · Sample workspace ready in minutes