Magento 2 Reporting Pro adds a set of reporting screens to the Magento Admin for looking at sales and customer data. Instead of checking several Magento screens and putting the numbers together manually, the extension keeps the main sales, product and customer figures in one place.
The reports are useful for day-to-day checking as well as for preparing data for a client, sales team or purchasing team. Depending on the report, you can look at customers, guests, products, categories or manufacturers, apply a date range, change the columns and export the result.
Customer reports also include segmentation and RFM information. This makes it possible to see not only how much a customer has purchased, but also how recently and how often they have purchased.
| Item | Details |
|---|---|
| Composer Package | toweringmedia/module-reporting-pro |
| Magento Module | Toweringmedia_ReportingPro |
| Product Type | Sellable Magento 2 Extension |
The easiest way to understand Reporting Pro is to look at the questions it helps answer:
The extension also provides a Custom Report Builder for saved report definitions and export options for working with the report data outside Magento.
Magento 2 Reporting Pro)Please refer to the installation guide for the installation steps:
The Reporting Pro settings can be found in the Magento Admin under:
Stores > Configuration > Towering Media > Reporting Pro
There are two settings in this section. These are worth checking before using the reports on a live store.
| Setting | Description | Example |
|---|---|---|
| Counted Order Statuses | Select the order statuses that should be counted by the reports. Custom order statuses created in the store can be selected as well. | Complete, Closed, Pending |
| Manufacturer Attribute | Enter the product attribute used for the manufacturer name. Sales by Manufacturer uses this attribute when grouping the products. | manufacturer |
Maximum Rows Per Export controls how many rows can be written to an export file.
The default value is 50000.
If a store has a large amount of data, increasing this value should be done carefully because larger exports need more server resources.
The Customer Segmentation settings are used when the extension decides which segment a customer belongs to.
The values should not simply be copied from one store to another. A wholesale store, for example, will normally have very different order sizes from a small retail store.
| Setting | Description | Example |
|---|---|---|
| Corporate Category Keywords | Comma-separated category keywords used as one of the Corporate checks. | cookie,platter,catering,bulk |
| Corporate Average Order Value | Average order value used as a Corporate customer check. | 1500 |
| Corporate Average Units Per Order | Average units per order used as a Corporate customer check. | 40 |
| Units That Make An Order Large | Number of units of one product that makes an order a large order. | 12 |
| Large Orders Before Corporate | Number of large orders required for this Corporate check. | 2 |
| Days of Silence Before At Risk | Number of days without an order before the customer is considered At Risk. | 90 |
| Recency Score Bands (Days) | Day values used for the Recency part of the RFM score. | 14,30,60,90 |
| Frequency Score Bands (Orders) | Order-count values used for the Frequency part of the RFM score. | 1,3,6,12,20 |
| Monetary Score Bands (Base Currency) | Spending values used for the Monetary part of the RFM score. | 250,750,2000,5000 |
The Magento Use system value option can be used where it is available. This is useful when the same setting should be inherited instead of being entered separately for every store view.
The reporting screens follow a similar Magento Admin layout. Most screens have Filters, Export, Default View and Columns controls. Reports that support charts show the chart above the grid, followed by totals and the report rows.
This is the main dashboard for a quick overview.
At the top it shows:
Below that are the top customers and top categories.
The Revenue and Orders chart gives a simple view of how sales and order volume changed during the selected period.
The Custom Report Builder is where saved report definitions are listed.
The screen shows the report name, grouping, number of columns and type.
A new report can be created from this screen, and existing saved reports can be managed from the Action column.
This report is useful when you want to see sales by customer and also keep guest orders in the same report.
The grid shows:
This screen combines customer details with the segment information calculated by Reporting Pro.
Along with the customer name and email, it shows:
Category Product Report is useful for checking which products are generating sales inside each category.
The report shows:
There is also a Top 10 Categories by Revenue chart.
This report groups sales by the manufacturer attribute configured in Reporting Pro.
It includes:
The report can also show a comparison with the previous period.
Sales Detailed is an order-level report.
Select an Order Window first and the report returns the matching orders.
The screen contains order, customer, billing, shipping, email and shipping-method information.
This report is also intended for detailed exports, so it contains more order information than a normal summary report.
Product Performance is the report to use when you want to compare products and their sales results.
The default view can group configurable products with their variants.
If individual child SKUs are required, change the SKU View to Show every SKU.
Where cost has been entered for the product, the report also shows:
This report starts from the customer and shows the products and categories that customer has purchased.
It includes:
This report shows the products purchased by each customer and ranks them by sales.
The grid includes:
The Top 10 Products by Revenue chart provides a quick summary.
Customer Loyalty Ranking gives a longer-term view of customer activity.
It shows:
After installation or an upgrade, these are the checks I would normally run before considering the extension ready on a store:
composer install and ./bin/check before a release.First check the date range. This is the most common reason for an empty report.
Then check Counted Order Statuses and make sure the reporting data has been built or refreshed.
Check the date range and the counted order statuses.
Also check the comparison period selected on the dashboard.
Check the Manufacturer Attribute under Reporting Pro configuration.
The report uses the attribute configured there.
Check the segmentation thresholds.
Corporate and At Risk decisions depend on those settings, and the RFM score bands also affect the displayed score.
Look at the SKU View.
Group by configurable combines variants under the parent, while Show every SKU lists the child SKUs separately.
Check the Order Window and any active filters.
Sales Detailed is based on the orders that fall inside the selected window.
Check Maximum Rows Per Export.
The configured value is a limit for the export. If you increase it, make sure the server has enough memory for a larger file.
Check the Reporting Pro reporting data.
The reporting screens use the extension's reporting aggregates and fact data, so those tables need to be up to date.
Follow the upgrade instructions for the installed version.
Where the release requires it, run:
php bin/magento setup:upgrade php bin/magento setup:di:compile