Power BI product profitability analysis for every item you sell
Power BI product profitability analysis shows how much each item, category and brand earns once landed cost, discounts and returns come off the selling price. It helps product and pricing teams decide what to promote, reprice or retire. Our consultants build the model inside your own Microsoft tenant, and you review it at a weekly demo.
- Margin per item
- Landed cost included
- Range decisions with facts
Last updated
What does Power BI product profitability analysis tell you?
Best sellers and best earners are not the same list. An item can top the volume chart because it sells at a thin margin. Another sells slowly but earns well on every unit. Without both views, range decisions rest on habit.
Margin by product sets the two side by side. A scatter chart places each item by sales and by margin rate. Then four groups appear: stars, volume drivers, niche earners and candidates for review.
Trends add a further signal. For example, a product whose margin slides month after month may suffer from rising supplier cost or creeping discounts. So the page splits the change into its causes before anyone blames the sales team.
Item-level margin measures for pricing decisions
Each measure works at item level and rolls up to category, brand and supplier.
Gross margin amount
Subtract cost of goods sold from net sales. The amount shows how much each item adds in currency.
Gross margin rate
Divide the margin amount by net sales. Then items of very different price become comparable.
Landed cost
Add freight, duty and handling to the purchase price, because the supplier invoice alone understates what an item costs.
Discount depth
Compare the list price with the price achieved. A widening gap shows where margin leaks.
Return cost
Subtract refunded sales and add handling cost per returned unit, so heavily returned items lose their false shine.
Contribution per unit
Divide contribution after variable costs by units sold. Planners use it when capacity or shelf space is short.
Which cost data does product margin reporting in Power BI need?
Sales lines carry the revenue side: item, date, quantity, price and discount. The cost side is harder. Some systems stamp a cost on each sales line at posting time. Others hold only a current standard cost per item.
That difference changes the answer. If the model multiplies past quantities by today's cost, last year's margin shifts whenever a cost changes. Therefore we prefer the cost recorded at the time of sale. When only a cost history exists, we match each sale to the cost valid on its date.
Overhead needs a decision from finance, not from us. Some teams stop at contribution after variable costs. Others spread fixed overhead across products with a driver such as machine hours. We build either, but the page keeps allocated overhead in its own column. For the full set of finance statements around it, see power bi financial reporting.
Mistakes in Power BI product profitability analysis
A margin report misleads when one of these slips in.
- Averaging margin rates instead of dividing total margin by total sales
- Applying today's cost to sales from earlier periods
- Leaving inbound freight and duty out of item cost
- Ignoring returns and the cost of handling them
- Judging bundle items separately from the bundle
- Dropping a low-margin item that pulls in other sales
How we deliver Power BI product profitability analysis
Cost rules come first, since the design depends on them.
Confirm the cost basis
First finance tells us which cost applies: actual, average or standard. We then document it on one page.
Model sales and cost
We relate sales lines, cost history and the product hierarchy, and we add landed cost components where data exists.
Tie margin to the books
Next total margin in the model goes against the income statement for closed months.
Build the decision pages
Finally we design the scatter, the ranking and the trend pages, then hand the file to your analysts.
Product profitability in Power BI: common questions
Why do totals differ in Power BI product profitability analysis?
Usually because of how a rate is calculated. A margin rate must divide total margin by total sales at each level. If a column stores the rate per line and the visual averages it, the total comes out wrong. We write the rate as a measure, so every subtotal recalculates correctly.
Can product profitability in Power BI include overhead?
Yes, if finance provides a rule. We hold the overhead pool and its driver in tables and let a measure spread the cost. However, allocated overhead can make a sound product look weak. So the page shows contribution before overhead as well, and readers can compare both views.
How can a reader tell why a product's margin changed?
A waterfall chart breaks the change into price, cost, volume and mix effects. Power BI includes this visual. For deeper questions, the decomposition tree lets a user split a margin figure by customer, region or channel in any order. Together they turn a vague concern into a named cause.
Does it work for services as well as goods?
Yes. For services, the cost side comes from time entries and labor rates instead of purchase prices. The structure stays similar: revenue per service line, direct cost and contribution. Still, the quality of time recording sets the limit. We check that first and tell you what the data can support.
How do we begin working together?
Call (480) 485-7373 or request the free 30-minute assessment online. You then receive a written scope with fixed contents. Power BI Agency is a division of Sataware Technologies, independent of Microsoft, with a small team. All work happens in your tenant, and we do not resell licenses.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.