Amazon Seller Central is full of useful reports. That is the good news and the trap.
The good news: Business Reports, payments, FBA inventory, returns, Brand Analytics, Account Health and advertising exports can tell you a lot about how Amazon is behaving. You can see sessions, conversion rate, Buy Box percentage, ordered product sales, units, refunds, fees, stock and campaign performance. For a single-channel seller, that may feel like a complete operating system.
For a multi-channel brand, it is not. Seller Central explains Amazon. It does not automatically explain whether Amazon deserves the next unit of stock, the next advertising euro, the next promotion or the next operational hour compared with bol.com, Shopify, Walmart, Kaufland, TikTok Shop or a Mirakl retailer.
The named mistake I see is treating Seller Central reports as the decision instead of the evidence. A team opens Detail Page Sales and Traffic by Child Item, sees a product with 21% conversion and €18,600 ordered product sales, and immediately increases Amazon ads. Nobody checks that the same SKU has only 16 days of FBA cover, a 9% return rate, a settlement reserve due next week, and 34% contribution margin on Shopify bundles. Seller Central was not wrong. The reporting room was missing.
My stance: brand owners need an Amazon Seller Central reporting room. Not another exported spreadsheet. A weekly decision layer that takes the best Seller Central evidence and reconciles it with margin, inventory, advertising, returns, payout timing and channel role before money moves.
This guide is written for brand owners selling across Amazon and at least one other channel, especially teams doing roughly 1,000+ orders a month or spending from €1.5K on marketplace ads. At that size, Seller Central reporting is no longer “checking Amazon”. It is part of capital allocation.
What existing Seller Central reporting advice gets right
The public advice on Seller Central reports is genuinely useful. Jungle Scout is right to focus sellers on Business Reports, especially Detail Page Sales and Traffic by Child Item. Sessions, page views, Buy Box percentage, ordered product sales and unit session percentage are still some of the fastest ways to understand whether a listing has a traffic problem, a conversion problem or an offer problem.
Helium 10 also makes a fair point: many growth opportunities are hiding in simple Seller Central metrics. A product with strong conversion but low sessions may need more traffic. A product with high sessions and weak conversion may need listing, price, review or offer work before more advertising. SellerApp’s breakdown of Business Reports is helpful for sellers who need to understand the difference between sales dashboard views, Sales and Traffic, parent ASIN reporting and child ASIN reporting.
DataHawk and MerchantSpring push the conversation toward broader marketplace analytics: executive KPIs, SKU profitability, advertising effectiveness, inventory, Buy Box shifts and multi-account dashboards. Sellerboard’s positioning around real profit is also valuable because Amazon revenue without fees, refunds, COGS, PPC and indirect costs can be very misleading.
Reddit discussions show the operator pain behind the polished guides. Sellers ask which Seller Central reports others actually review month over month, which tools can show revenue, expenses, PPC, FBA fees, net profit and refunds in one place, and how to automate daily or weekly extracts. One recurring complaint is very practical: Seller Central can be clunky, and if you want the same Business Report view tomorrow, you often rebuild the path again.
So the market has plenty of tutorials about where to click and which metrics matter. The gap is different: who is allowed to act on those metrics when the brand sells in more than one place?
The missing angle: Seller Central needs decision rights
Seller Central reports become dangerous when every metric gets equal authority. A conversion rate should not automatically move ad budget. A Buy Box percentage should not automatically move price. An inventory alert should not automatically pull stock from another channel. A settlement drop should not automatically pause campaigns. Each report should have a defined decision right.
Think of Seller Central as a witness, not the judge. It gives evidence about Amazon demand, offer quality, customer behaviour, fulfilment, cash and compliance. The reporting room decides what that evidence is allowed to change.
In FiveX, this is exactly where multi-channel analytics earns its keep. Seller Central data is useful on its own, but the real decision improves when it sits next to product contribution margin, bol.com performance, Shopify orders, returns, inventory runway, advertising spend and payout data. A product can look like an Amazon winner and still be the wrong place to allocate the next 500 units.
The reporting room should answer four questions every week:
- What changed in Seller Central? Sessions, conversion, units, ordered product sales, Buy Box, returns, stock, fees, payouts and ad performance.
- Is the change commercially clean? Contribution margin, refund lag, fulfilment cost, coupon impact and PPC pressure.
- Does another channel have a better claim? bol.com margin, Shopify bundle economics, Walmart stock requirements, wholesale commitments or retail-media timing.
- What action is permitted? Scale ads, hold budget, move stock, adjust price, refresh content, investigate returns, or do nothing.
The five Seller Central report lanes that matter
You do not need every Seller Central export in every meeting. You need a small set of lanes with clear purpose.
1. Demand quality: Business Reports
Use Detail Page Sales and Traffic by Child Item as the demand-quality lane. The key fields are sessions, page views, ordered product sales, units ordered, unit session percentage and Buy Box percentage. The goal is not to admire conversion rate. The goal is to classify the SKU.
A practical rule: if sessions are rising and unit session percentage is stable or improving, Amazon demand is probably becoming cleaner. If sessions rise while conversion falls, the product may be receiving weaker traffic or losing offer strength. If conversion improves while sessions stay flat, the SKU may deserve traffic testing, but only after margin and stock are checked.
FiveX hook: in FiveX, Amazon demand can be viewed next to other sales channels and product groups, so a “conversion winner” is not judged in isolation. That matters when Amazon growth cannibalises a more profitable direct channel.
2. Profit quality: fees, COGS and contribution margin
Seller Central revenue is not enough. The reporting room needs SKU-level contribution margin after COGS, referral fees, fulfilment, storage, refunds, commissions, ad spend and channel-specific costs. This is where many Seller Central-only reviews break.
A product with €42 selling price and €27 after Amazon fees can look healthy until you add €14.80 landed COGS, €4.20 average PPC per order and €2.10 expected return cost. The contribution margin drops to €5.90, or 14%. If Shopify sells the same item in a bundle at €68 with €19.40 contribution margin, Amazon should not automatically receive the next stock allocation just because ordered product sales are higher.
FiveX hook: FiveX connects marketplace revenue with product costs, shipping, fees and ad spend so the reporting room can compare contribution margin by SKU and channel instead of arguing over gross sales.
3. Inventory permission: FBA, FBM and cross-channel stock cover
Inventory reports decide whether Amazon is allowed to receive more demand. The mistake is checking only whether Amazon has stock today. The better question is whether Amazon has enough stock to support the action you want to take.
If a SKU has 16 days of FBA cover and a replenishment shipment is 21 days away, raising Sponsored Products budget may create a stockout. If the same SKU has 41 days of bol.com stock and strong Dutch conversion, the action may be to redirect budget or stock, not to celebrate Amazon velocity.
The reporting room should classify every hero SKU as green, amber or red:
- Green: enough stock cover for the campaign window and replenishment risk is low.
- Amber: demand can continue, but budget increases need approval.
- Red: no budget increase, promotion or ranking push until replenishment is solved.
FiveX hook: FiveX inventory analytics can show stock, sales velocity and stockout risk across connected channels, which makes Amazon inventory permission a portfolio decision rather than a single-channel panic.
4. Advertising permission: ads only scale after margin and stock agree
Seller Central Business Reports and Amazon Ads often tell different parts of the same story. Business Reports may show improving conversion. Campaign Manager may show acceptable ACOS. Neither metric should scale budget alone.
Advertising permission should require three yeses: the SKU has enough contribution margin, enough stock cover and enough evidence that paid traffic is incremental or strategically useful. Otherwise the ad team can accidentally buy demand that operations or finance would have rejected.
A simple rule: if ACOS is below target but contribution margin is under 10% after returns, do not scale. If ACOS is high but the SKU is a launch product with 90 days of stock and strong cross-channel repeat purchase, you may still fund a controlled test. The reporting room exists to make those trade-offs explicit.
5. Cash and exception lane: payments, returns and account health
Payments and returns are the least glamorous reports and often the most important. Ordered product sales can rise while cash gets tighter because reserves, reimbursements, refunds, promotions or settlement timing move against you.
Account Health also belongs in the reporting room. Late shipment issues, cancellation risk, invoice defects, policy warnings or listing suppressions should change what ads and stock are allowed to do. Buying more demand for a SKU with unresolved account-health risk is not growth. It is pressure on a weak point.
Scenario 1: the Amazon winner that should not get more stock
Imagine a brand selling a premium lunchbox across Amazon, bol.com and Shopify.
- Amazon ordered product sales: €38,400 in 30 days
- Amazon sessions: 18,900
- Amazon unit session percentage: 14.8%
- Amazon ACOS: 22%
- FBA stock cover: 18 days
- Amazon contribution margin after fees, COGS, PPC and expected returns: €6.20 per unit
- Shopify bundle contribution margin: €16.80 per unit equivalent
- bol.com stock cover: 46 days with 11.5% conversion
A Seller Central-only review says: “Great conversion, profitable ACOS, add stock and raise ads.” The reporting room says something more precise: Amazon demand is real, but FBA cover is too thin and Shopify bundles earn 2.7 times more contribution per unit. The decision is to hold Amazon budget, transfer only 300 units to FBA, reserve 500 units for Shopify bundles, and review again after replenishment lands.
The trade-off is uncomfortable because Amazon has the loudest dashboard. But profit does not care which dashboard is loudest.
Scenario 2: the weak conversion SKU that deserves a controlled test
Now take a home storage brand with a new organiser set.
- Amazon ordered product sales: €9,800 in 30 days
- Sessions: 12,400
- Unit session percentage: 4.1%
- Buy Box percentage: 97%
- Return rate: 3.2%
- FBA cover: 74 days
- Contribution margin before ads: 38%
- Sponsored Products spend: €620 with 41% ACOS
- bol.com conversion on the same product family: 12.6%
A shallow review might cut Amazon ads because ACOS is ugly and conversion is weak. The reporting room sees a different possibility. The offer has stock, margin and Buy Box stability. Returns are low. bol.com proves the product family can convert. The issue may be Amazon listing content, image sequencing or keyword intent, not product economics.
The decision is not to scale blindly. It is to run a two-week controlled test: refresh the main image and first three bullets, isolate five exact-match keywords, cap spend at €35 per day, and require conversion to move from 4.1% to at least 6.5% before any broader budget release.
That is the difference between “ACOS bad, cut it” and “evidence incomplete, test the bottleneck”.
Scenario 3: the payout surprise that should freeze promotions
A beauty brand plans a 20% Amazon coupon for a hero serum because Business Reports show 24,000 sessions and 12.2% conversion. The ad team wants to support the coupon with €90 per day in Sponsored Products. On the surface, that looks sensible.
The cash lane changes the decision. Last settlement was €14,700 lower than forecast because refunds and reserves hit together. The same SKU has a 10.8% return rate, and two wholesale invoices are due in nine days. If the coupon runs, contribution margin falls from €8.40 to €2.10 per unit before incremental ad spend. The promotion may win rank and lose cash.
The reporting room chooses a smaller move: no sitewide coupon, no budget increase, only a €500 keyword test against the highest-margin variation, and a new review after the next settlement clears. Boring? Yes. Smart? Also yes.
How to run the weekly Seller Central reporting room
Keep it operational. A good reporting room does not need 90 slides. It needs a consistent agenda and a decision log.
- Open with exceptions. Stockouts, suppressed listings, account-health warnings, settlement shocks, abnormal returns and margin changes.
- Review demand quality. Which SKUs gained or lost sessions, conversion and Buy Box strength?
- Check profit quality. Did contribution margin change because of fees, COGS, returns, promotions or PPC?
- Assign inventory permission. Which SKUs are green, amber or red for demand creation?
- Approve or reject ad actions. Budget increases, keyword tests, bid cuts and campaign holds need written reasons.
- Compare channel claims. Does Amazon deserve the next unit more than bol.com, Shopify, Walmart or another marketplace?
- Log the decision. Owner, action, metric trigger, review date and rollback rule.
The named mistake to avoid here is spreadsheet theatre: exporting more tabs, adding more colours, and still leaving the meeting without a decision. If a metric does not change an action, it is background context, not a reporting-room item.
The FiveX way: from Amazon reports to marketplace decisions
FiveX is built for this exact gap. Seller Central is a rich source of evidence, but multi-channel brands need that evidence connected to the rest of the business. In FiveX, teams can bring marketplace revenue, product profitability, ad performance, stock, returns and channel performance into one operating view.
That changes the weekly conversation. Instead of asking “what happened in Amazon?”, the team can ask “which SKU deserves the next euro, unit and hour?” Instead of manually stitching sales, fees and ad spend together, the team can look at contribution margin and advertising impact by product. Instead of treating inventory as a separate spreadsheet, stockout risk can sit next to sales velocity and campaign decisions.
There is also a cultural benefit: fewer opinion fights. When finance, marketing and operations all work from the same product-level view, Seller Central reports stop being ammunition and become evidence.
Final takeaway
Amazon Seller Central reports are valuable. They are just not enough on their own once your brand sells across several channels.
Use Seller Central to understand Amazon demand, conversion, offer quality, inventory, returns and cash. But do not let those reports move money without cross-channel context. The next profitable decision may be to scale Amazon ads. It may also be to protect Shopify stock, shift attention to bol.com, delay a coupon, investigate returns, or hold cash until the next settlement clears.
The best operators do not worship dashboards. They build rooms where dashboards earn decision rights.