Invento Software LimitedCase studyDistribution

BestinBrands: preparing ERPNext data for sales and inventory reports

BestinBrands’ sales reporting depended on preparing ERPNext data, uploading it to Salesforce and extracting it again for the final reports. Invento connected ERPNext to Power BI, with reusable preparation rules and a shared reporting model for sales and inventory analysis.

CompanyBestinBrands
IndustryDistribution and marketing
CountryBangladesh
Reporting projectERPNext·Power BI

Reporting depended on repeated preparation and transfers

BestinBrands distributes and markets international brands in Bangladesh. To review sales by product and location, the team prepared ERPNext data, uploaded it to Salesforce and extracted the results for its final reports. Each reporting cycle depended on those preparation and transfer steps.

BestinBrands’ Salesforce setup already produced monthly and yearly comparisons from the figures the team uploaded.

The team needed a reporting process that used the records in ERPNext without repeating that route through Salesforce each cycle.

BestinBrands reporting before Power BI: ERPNext data prepared and uploaded to Salesforce, which already automated monthly and yearly comparisons, then extracted for final reports.
Enlarge diagram

A Power BI reporting layer built around ERPNext

We connected ERPNext to Power BI and built the preparation, calculations and refresh process behind the reports. ERPNext remained the system of record. The new route removed the Salesforce upload and extraction steps for these reports, while the team continued to review the figures.

Connected ERPNext to Power BI

We configured the data gateway to supply ERPNext records to the reporting process. Business records stayed in ERPNext, while Power BI used the prepared data for analysis.

Built reusable preparation rules

We built cleaning, standardisation and business calculation rules into the pipeline. Each refresh applied those rules to fresh data, replacing preparation that had to be repeated for each reporting cycle.

Created the shared reporting model

We organised the relationships and calculations used by 124 recurring reports and more than 20 dashboards. The reports covered sales by brand, product, channel and location, along with inventory analysis.

Configured refresh and gateway fallback

We set up scheduled incremental refresh to process changed data and retain earlier periods for comparison. The gateway used two nodes, with a second node configured for fallback. Refreshes still needed monitoring.

ERPNext supplies records through a two node gateway, preparation rules and scheduled refresh to a shared Power BI model serving 124 reports and more than 20 dashboards. People still review the figures.
Enlarge diagram

Review the steps your team repeats

Bring one report and the steps used to prepare it. We can discuss which calculations and data preparation could run automatically.

Discuss your reporting workflow

Reports for brands, channels and inventory

Power BI extended the reporting available from ERPNext records. The team could examine sales by brand and product, compare channels and locations, and review stock positions using the same prepared data and reporting definitions.

Brand and productSales, quantities and period comparisons by brand, with product detail beneath the totals.
Channel and locationPerformance across distribution channels, stores and other reporting locations.
InventoryStock positions for the team’s inventory analysis.

Less preparation for the most complex report

Reusable preparation rules now supplied the Power BI reports, with the team retaining its review of the figures. Invento’s delivery team reported a shorter preparation time for the most complex recurring report.

Preparation time for the most complex recurring report

Before
3 to 4 days
After
About 1 day

Invento’s delivery team provided the estimates, which cover preparation of one complex recurring report, not the entire reporting workload.

Reports built on the shared model

124 recurring reports
More than 20 Power BI dashboards

Served through one shared model.

Preparing reports beforePreparing reports with Power BI
ERPNext data passed through Salesforce before the final reports were prepared.ERPNext data feeds the Power BI reporting process without that transfer stage.
Data preparation and transfers were repeated for each reporting cycle.Reusable rules prepared the data for the shared model.
People checked the figures before a report was used.People continued to review the prepared report.

Working with ERPNext and Power BI

Does Power BI replace ERPNext?
ERPNext remains the system of record. Power BI adds the reporting layer, using ERPNext data for sales, product, location and inventory analysis.
How does the reporting layer connect to ERPNext?
A data gateway connects ERPNext to the Power BI reporting process. The pipeline applies preparation rules, and the shared model holds the relationships and calculations used by the reports.
What happens if a gateway node becomes unavailable?
The gateway has two nodes, with the second configured for fallback if one becomes unavailable. Refreshes still need monitoring because a backup node cannot prevent every type of interruption.
How does the setup retain earlier reporting periods?
Scheduled incremental refresh processes changed data while retaining historical records for comparison. Refresh duration depends on the data, transformation rules and configuration.
What should we bring to a reporting consultation?
Bring one recurring report, its source systems, calculation rules and deadline. Include how it is prepared and who checks it. These details help identify which steps could run automatically and which checks should remain with your team.

Plan the preparation behind your next report

Bring a recurring report to a free consultation. We can review its sources, calculations and deadline, then discuss the steps that could run automatically and the checks your team should keep.

Book a Free Consultation