How MerchantSpring Shows Amazon Sales Performance by Product

This is where the Sales by Product report inside MerchantSpring becomes useful.

It lets sellers move beyond account-level numbers and see how each SKU or ASIN contributes to the overall result.

You can review important details such as brand, category, price, units sold, and other available performance metrics without exporting everything into a separate spreadsheet.

Learn More Here:

What Does Sales By Product Show?

Sales by Product shows performance at the level where sellers can connect a result to a specific product.

Instead of seeing only one total for the entire Amazon account, you can examine the products sitting behind that total.

The report can display product identifiers alongside information such as brand, marketplace category, selling price, and the number of units sold.

Additional columns can then be included when you need more context around the performance of a particular listing.

This makes the report useful for both a quick daily check and a more detailed product investigation.

Why Product-Level Analysis Matters

Account-level growth can hide major differences between the products inside the catalog.

A few strong listings may be carrying the account while several weaker listings quietly lose momentum.

The opposite can also happen when overall sales appear stable even though an important product has started declining.

Looking at each product separately helps you uncover those changes before they disappear inside the larger account total.

It also gives you a clearer way to answer practical business questions.

1. Which products generate the largest share of sales?

2. Which listings are selling more units after a price change?

3. Which products are underperforming compared with the previous period?

4. Which categories or brands contain the strongest individual products?

5. Which listings deserve more inventory, advertising support, or investigation?

How To Customize The Product View

The product view can stay simple when you only need a fast answer.

You can keep only the columns that matter for the question you are currently trying to solve.

For example, a quick sales check may require only the product name, price, units sold, and total sales.

A deeper investigation may require more advertising, profitability, comparison, or operational data.

The benefit is that you do not need to maintain one overcrowded report for every situation.

For a wider explanation of how this report connects with the rest of the platform, read my Complete MerchantSpring tutorial and platform review.

A Practical Product Analysis Workflow

The most useful analysis starts with a specific question rather than every available metric.

Once you know what you want to understand, the report becomes much easier to configure.

1. Choose the date range. Select a period that matches the decision you are making.

2. Add a comparison period. Compare the current result with a relevant earlier period when possible.

3. Select only useful columns. Remove data that does not help answer your current question.

4. Sort the report. Start with sales, units, price, or another metric connected to your goal.

5. Look for unusual movement. Identify products that changed more sharply than the rest of the catalog.

6. Investigate the cause. Review pricing, advertising, traffic, conversion, refunds, stock, or listing changes.

7. Record the next action. Turn the finding into a clear task for inventory, advertising, pricing, or listing management.

This process keeps the analysis focused and reduces the risk of getting distracted by columns that look interesting but do not lead to a decision.

What To Look For In Product Data

A strong or weak sales number is only the beginning of the analysis.

You still need to understand what changed around that number.

Sales And Units Sold

Sales and units should be reviewed together because higher revenue does not always mean stronger demand.

Revenue may rise because the price increased while the number of units sold remained flat or declined.

Price Changes

Price provides important context when a product suddenly sells more or fewer units.

A price reduction may improve volume without improving the product’s actual profit contribution.

Brand And Category Context

Brand and category details help you avoid comparing products that serve completely different markets.

A meaningful comparison usually involves products with similar functions, audiences, prices, or seasonal demand patterns.

How Large Catalog Sellers Can Use This Report

Product-level reporting becomes more valuable as the number of products increases.

A seller with a small catalog may already know how each listing performs without opening a report.

That becomes much harder when the business manages hundreds of products, several brands, or multiple marketplaces.

The product report gives the team one place to sort the catalog and quickly identify which listings deserve attention.

A useful approach is to begin with the largest movements rather than reviewing every product in the same amount of detail.

1. Review the products generating the most sales.

2. Find products with the largest positive or negative period change.

3. Check products with unexpected pricing or unit movement.

4. Investigate important products that no longer follow their normal trend.

5. Move from the product report into deeper advertising, profitability, or operational reports only when needed.

Sellers building a broader software stack can also explore my guide to Multi-channel eCommerce software and tools.

When To Keep The Report Simple

A simple report is usually better for recurring checks and routine team meetings.

It keeps the most important numbers visible and makes unusual changes easier to notice.

You can then open a deeper view only for the products that require more investigation.

This prevents the team from wasting time discussing dozens of metrics for products that are already performing normally.

When To Run A Deeper Investigation

A deeper analysis makes sense when a product behaves differently from what you expected.

The unexpected movement may come from demand, but it may also be connected to advertising, pricing, inventory, refunds, conversion, or listing issues.

The product report helps you find the listing that needs attention before you move into those more detailed areas.

That sequence is much faster than opening every report and hoping the problem becomes obvious.

Common Product Analysis Mistakes

The report becomes less useful when the data is reviewed without context or a clear decision in mind.

1. Looking only at revenue. Revenue can rise while units, profit, or conversion move in the wrong direction.

2. Comparing unrelated products. Different prices, audiences, categories, and seasons can make the comparison misleading.

3. Using too many columns. An overcrowded view makes important changes harder to notice.

4. Ignoring the comparison period. A current number means more when you can see how it changed.

5. Reacting to one unusual day. Short-term movement may not represent a real trend.

6. Finding a problem without assigning an action. Analysis creates value only when the team knows what to do next.

Watch The Complete MerchantSpring Tutorial

Sales by Product is one part of a much larger analytics and reporting platform.

The complete tutorial below shows how this report connects with MerchantSpring’s dashboards, channel analytics, customer insights, profitability tools, operations, advertising, and reporting features.

Final Thoughts

MerchantSpring’s Sales by Product report gives sellers a practical way to understand what is happening beneath the account total.

You can keep the view focused when you need a quick performance check and expand it when a product requires deeper investigation.

That flexibility helps sellers spend less time moving data between tools and more time acting on the products that need attention.

You can also browse my collection of Amazon seller software reviews, tutorials, and discounts to compare MerchantSpring with other tools in your business stack.