Per-row basket
Available with an amount and usable rows.
Trend reading
Read average basket without mixing levels.
Average basket can be very useful, but only if you know whether it refers to a row, an order or a customer.
In short
Average per row does not mean the same thing as average per order.
Quick read
What to remember
A short page to know what to check, what to avoid and when to use RGAnalyzer.
Order value
Reliable only with a real order or invoice number.
Monthly trend
Useful when dates are sufficiently complete.
Simple method
Separate basket and trend
Read the calculation level first, then look at revenue evolution over a comparable period.
Check
- Check whether the file contains a reliable order number
- Compare periods of comparable duration
- Read the trend together with changing customers and products
- Keep the basket calculation level visible
Avoid
- Presenting per-row basket as order value
- Reading monthly growth without checking the period
- Mixing returns, discounts or credits without showing them
- Comparing a full month with a partial month
RGAnalyzer
What RGAnalyzer separates
The report shows basket value only at the level the file can support.
Always separated from order value.
If order data is missing or groups too many rows, order value is hidden.
The report highlights recent change when it is readable.
FAQ
Useful questions
Why is order value unavailable?
Because the file does not contain a reliable order number. RGAnalyzer avoids showing a misleading number.
What does MoM mean?
It is the change from one period to the previous one, for example one month versus the previous month.
When should average basket be read?
When you want to understand average value per row or order, not only total revenue.