Skip to content

Best practices for global ASIN-level KPI rollups

Roll up by ASIN family first and marketplace second, convert at fixed monthly rates, split VAT-inclusive EU revenue from US figures, and keep channels visible.
·5 min read
Amazon ExpansionAmazon FBAOrganic Ranking
Joel Turcotte Gaucher

Joel Turcotte Gaucher

Founder

Flapen cover for Best practices for global ASIN-level KPI rollups: a product video shoot with a phone on a gimbal in the studio

Roll up by ASIN family first, marketplace second, and never sum raw currencies. Convert at a fixed monthly rate, separate VAT-inclusive European revenue from US ex-tax revenue, and keep channel splits visible inside each rollup. An aggregate that hides one failing marketplace behind five healthy ones is the standard failure.

The short version

  • The product is the unit, the marketplace is the dimension. Group by ASIN family, then slice by country, never the reverse.
  • Currency policy beats currency precision. One fixed monthly conversion rate, stated on the report, applied everywhere.
  • Tax treatment is silently different. European displayed prices generally include VAT; US figures are pre-tax. Summing them overstates Europe.
  • Averages are where failures hide. Every rollup needs a one-click path down to the single worst marketplace.
  • Keep traffic sources separate through the rollup. Blending paid and organic at global level destroys the only diagnostic split that matters.

Why you cannot see what happened last week

If you sell the same product in six countries, you have felt this: every export disagrees, the German numbers include tax while the American ones do not, currency moves masquerade as demand moves, and the blended global figure is stable while two marketplaces are quietly dying. The rollup is not a reporting nicety. It is the difference between managing a global account and managing a rumor about one.

Flapen operates brands across all 23 Amazon marketplaces with localized content in English, German, Spanish, and French, so the conventions below are the ones our own reporting runs on.

Three rollup architectures compared

Marketplace-first ASIN-family-first Channel-first
Groups by Country, then product Product family, then country Traffic source, then product
Answers well "How is Germany doing?" "How is this product doing worldwide?" "Is paid carrying the whole account?"
Fails at Spotting a product weak everywhere Spotting a country-level problem Almost everything else
Best for Tax, fees, and operations reviews Product and creative decisions Advertising reviews only

The decision rule: build ASIN-family-first as the primary structure, because products are what you actually make decisions about, then let marketplace and channel be the two drill-down dimensions inside it. Teams that build marketplace-first end up with six country reports and no product view, and product decisions get made on the biggest market's data alone.

Channel deserves a special note. There are five ways a listing gets traffic: organic, paid, promotions, influencer and creator content, and off-channel sources, and most sellers actively run two. A global rollup that blends them all into one sessions number cannot tell you whether Spain is weak because of demand or because paid was never activated there. Carry the channel split through every level of the rollup, even where some channels read zero. The zeros are findings.

The conventions that keep a rollup honest

  1. Fix the exchange rate monthly. Pick a rate on the first of the month, state it on the report, convert everything with it. You are measuring demand, not running a treasury desk.
  2. Normalize the tax base. Strip VAT from European revenue before comparison, or report both bases labeled. Mixed bases inflate EU performance against US by the tax margin.
  3. Compare conversion locally, not globally. Conversion norms differ by marketplace, so judge each country against its own history. A localization gap surfaces here first, and the fix is listing optimization in that language, not a global panic.
  4. Report inventory cover in weeks, per marketplace. Units mislead when sales velocity differs tenfold between countries.
  5. Always show the worst cell. Whatever the aggregate says, print the single worst ASIN-marketplace pair on the same page. It is the earliest warning you will get.

What a blended rollup will not tell you

It will not tell you where the problem is, and at global scale that is the entire job. A flat global revenue line can contain a US decline offset by a German ramp, a currency tailwind hiding a unit decline, or one ASIN's collapse padded by a launch elsewhere. Every one of those calls for a different action this week, and the blended number recommends none of them. The test for any global report is simple: can you get from the top-line figure to the responsible ASIN-marketplace pair in two clicks? If not, the rollup is a scoreboard, not an instrument.

For a rollup of your own account built this way, start with the free audit at Flapen.

Keep learning

Frequently Asked Questions

Share this post
The Flapen Weekly Product Research report, an Amazon niche shortlist scored 0–100 with its score radar on the cover

The weekly niche report

Product research, in your inbox

Every niche that cleared the bar this week: what it sells for, what it costs to enter, and why it passed. When we get one wrong, we publish the correction.