Brand Owners: Amazon Seller Central Reports to Check Weekly

You open Seller Central on Monday and sales look broadly on track. Then someone asks why a bestseller needs another discount, why the next payout looks light, and why a product with stock at FBA isn't available to buy. The revenue dashboard alone won't answer those questions.

That's the weakness in a sales-first review. You can miss a Featured Offer loss that began late in the week, irrelevant searches consuming ad spend, or inventory adjustments that make your replenishment forecast wrong. By the time the topline changes enough to attract attention, your team may already have approved another purchase order or increased bids.

The Amazon Seller Central reports to check weekly should support specific decisions: fix the offer, reduce waste, replenish stock, recover money, or correct a product problem. Each review needs a metric, an action threshold, and someone responsible for the next step. Where Amazon publishes a threshold, use it. Elsewhere, set an internal trigger based on your economics rather than borrowing an arbitrary percentage.

Monday operating rule: Start with Business Reports, then check Account Health and inventory availability before changing advertising. A campaign adjustment won't fix an unavailable product or a policy restriction.

Keep the marketplace, currency, ASIN group, and reporting period consistent. Save the exports so next Monday's discussion starts with evidence, not competing screenshots.

1. Business Reports Detail Page Sales and Traffic by Child ASIN

Open Seller Central > Reports > Business Reports > Detail Page Sales and Traffic by Child ASIN. Compare ordered product sales, units ordered, sessions, page views, Featured Offer percentage, and Unit Session Percentage at the variation level, not just across the parent listing.

Use the previous completed week against the preceding week, adding the equivalent seasonal period when useful. Amazon's Business Reports guidance supports a seven-day comparison and downloading sales and traffic reports for deeper analysis.

Decide whether to fix traffic or conversion

Build a standing spreadsheet with child ASINs as rows and a week-over-week change beside each metric. Your red flag is a meaningful departure from that ASIN's normal performance without a planned promotion, price change, or availability explanation.

• Sessions falling, conversion steady: Investigate advertising reach, keyword visibility, and offer availability before rewriting the listing.
• Sessions steady, conversion falling: Check price, delivery promise, reviews, images, and competing offers.
• Featured Offer share falling: Inspect the offer listing and pricing before assuming the content has stopped working.
• Revenue steady, units falling: Check whether price increases or product mix are disguising weaker demand.

Say a household-goods brand loses sales on a single color variation while sibling variations remain stable. If sessions haven't changed, inspect that variation's offer, images, and availability before making parent-wide edits.

Don't average individual ASIN conversion percentages to report portfolio conversion. Amazon's sales-and-traffic documentation distinguishes order-item session percentage from other conversion measures and supports calculating aggregate performance from the underlying totals. Keep metric definitions consistent, and use total ordered product sales as the denominator when calculating TACoS.

2. Sponsored Products and Sponsored Brands Search Term Report

A high-spend search term isn't automatically wasteful. A relevant query can deserve investment even when its short-term return looks weak, while an irrelevant query deserves exclusion before it consumes more budget.

In Campaign Manager, open reporting and create the available Sponsored Products and Sponsored Brands Search Term reports. Export customer queries with spend, clicks, orders, attributed sales, ACoS, and ROAS, then sort by spend descending.

Use contribution margin as the spending limit

Your red-flag threshold is the amount you can afford to spend acquiring an order, not a universal click count. Work from selling price minus product cost, fulfillment, selling fees, and expected returns, then decide how much contribution you're willing to allocate to acquisition.

• Irrelevant query: Add an appropriate negative keyword after checking that it won't block valuable searches.
• Relevant query without orders: Compare spend with allowable acquisition cost and check attribution maturity before cutting it.
• Consistently converting query: Test dedicated exact-match targeting with its own bid and budget.
• Good clicks, weak purchases: Inspect the advertised ASIN's offer and listing before buying more traffic.

For a pet brand, searches for free products may be clearly unsuitable for a paid premium toy. A relevant durability query deserves a different response: inspect the product page and bid economics rather than excluding it merely because the latest report shows no orders.

Use converting language to inform your Amazon backend keywords, without turning search-term harvesting into keyword stuffing. Magnitude Marketing's ecommerce PPC guide offers broader campaign context, but your account's contribution margin should govern bid decisions.

Keep competitor advertising separate from infringement. Bidding on your brand name isn't, by itself, evidence that a seller has violated your rights.

3. Inventory Health Report and Inventory Performance Index

Open Manage Inventory Health and Inventory Performance before approving replenishment. Review IPI alongside sellable stock, stranded inventory, aging, inbound shipments, and expected demand.

Amazon's IPI documentation identifies excess and aged inventory, FBA sell-through, and stranded listings as relevant factors, and recommends approximately 30 to 60 days of expected sales coverage. Treat that guidance as a planning reference, not a substitute for supplier and receiving lead times.

Replenish against lead time, not anxiety

Calculate days of cover = sellable units ÷ expected daily unit sales. Your stockout trigger is cover falling below the time required to manufacture, transport, receive, and make replenishment available, including your operating buffer.

The opposite trigger is inventory you're unlikely to sell economically before additional holding costs outweigh the expected contribution.

• Low cover with inbound stock: Verify shipment status and expected availability before placing another order.
• High cover with slowing demand: Reduce replenishment and compare promotion, removal, and continued storage.
• Stranded units: Resolve the listing or offer issue before treating those units as usable supply.
• Declining IPI: Investigate its underlying inventory problems rather than chasing the score in isolation.

Say a skincare brand appears short on stock, but its next shipment is already receiving. Another purchase order could create excess inventory without preventing the immediate availability gap. The correct action is to investigate receiving progress and adjust demand exposure.

Amazon's Manage Inventory Health documentation combines sales history, weeks of cover, aging, estimated storage fees, and inbound status for this reason. Review your account's current limits alongside our explanation of Amazon FBA capacity limits rather than assuming a single IPI cutoff explains every restriction.

4. Account Health Dashboard and Performance Notifications

Check Performance Notifications before interpreting the dashboard's green indicators. Open each active notification, identify the affected ASIN or account issue, and record the response deadline displayed in Seller Central.

Then open Performance > Account Health. Amazon's Account Health Rating guidance classifies 200 to 1,000 as Healthy, 100 to 199 as At Risk, and 99 or lower as Unhealthy. A healthy rating doesn't give you permission to ignore unresolved violations or the deadlines attached to them.

Don't wait for an account-level score change to investigate an active policy violation. Read the notice and address the specific issue.

Match the corrective action to the cause

For seller-fulfilled orders, review Order Defect Rate, cancellation performance, late dispatch, and tracking performance against the requirements shown for your marketplace and fulfillment method. The red flag is either a requirement breach or a worsening operational trend that could produce one.

A carrier handoff problem needs different work from a content complaint. For shipping issues, inspect order-level confirmation timestamps, carrier scans, handling settings, and the warehouse handoff process. For a policy complaint, preserve the notice, listing version, supporting documents, and corrective-action record.

Say late dispatch begins rising after a warehouse changes its collection schedule. Increasing handling promises may prevent further unrealistic commitments, but the team still needs to correct the handoff and confirmation workflow. An appeal alone won't repair fulfillment.

Maintain a log containing the issue, root cause, owner, submission date, supporting evidence, and status. Weekly review is the management checkpoint, not the monitoring frequency: we monitor account health daily and handle Seller Support cases so smaller issues don't become suspension risks.

5. Brand Analytics Search Query Performance Report

A product can receive plenty of clicks and still lose purchases to competing offers. Search Query Performance helps you separate visibility problems from shopping decisions after discovery.

For eligible brand-registered accounts, open Brand Analytics > Search Query Performance and select the available brand or ASIN view. Maintain a fixed group of commercially important queries so your weekly comparison doesn't change whenever a different keyword becomes interesting.

Read the funnel without overclaiming causation

Track query volume, impression share, click share, cart-add share, and purchase share where available. Your red flag is a persistent deterioration at a specific stage of the funnel, supported by enough query activity to justify action.

• Impressions without comparable clicks: Inspect search-result relevance, main image, title, price, and delivery promise.
• Clicks without comparable purchases: Check the detail page, variation selection, reviews, offer quality, and customer expectations.
• Falling query volume: Separate weaker category demand from a loss of your own competitive position.
• Improving shares without stronger sessions: Confirm the query's scale and reporting scope before declaring a meaningful gain.

Say a cookware listing attracts shoppers searching for induction-compatible pans, but the listing buries compatibility information. Clearer bullets, images, and comparison content are more defensible first moves than raising bids.

Interpretation guardrail: A gap between click share and purchase share identifies where to investigate. It doesn't prove which image, price, or competitor caused the gap.

Don't describe Search Query Performance as a clean organic-ranking report. Advertising and shopping behavior can both influence the journey you're examining, and the report isn't a complete view of every competitor's business.

Use it to form a testable hypothesis. Make a focused change, preserve the reporting scope, and compare subsequent performance with Business Reports and advertising results before expanding the change across the catalog.

6. FBA Reimbursements Report

Start with the inventory discrepancy, not with the reimbursement total. A payment entry tells you that Amazon recorded a reimbursement; it doesn't establish that every eligible loss has been resolved.

Download Reports > Fulfillment > Reimbursements, then compare relevant entries with Inventory Ledger, inventory adjustments, and inbound shipment records. Amazon describes Inventory Ledger as an inventory statement covering receipts, sales, returns, removals, damage, losses, and adjustments, with the prior week's aggregated data generally available by Monday's end of day.

Escalate unexplained movements with evidence

Your red flag is an inventory movement that remains unexplained after checking its disposition, event history, and related reimbursement. Don't impose an arbitrary loss percentage that lets valuable discrepancies escape review.

• Inbound shortage: Compare shipped and received quantities with the shipment's reconciliation status.
• Lost or damaged inventory: Match the inventory event to any reimbursement, reversal, or subsequent found-unit adjustment.
• Possible fee error: Verify product measurements and transaction details before requesting a correction.
• Unclear eligibility: Check the current policy and case instructions for that event type before filing.

Say a home-goods shipment shows fewer received units than the packing list. Preserve the shipment ID, carton records, proof of delivery, and shipping documents, then follow the reconciliation process when the shipment becomes eligible. Don't describe every receiving delay as a reimbursable loss.

Our guide to Amazon FBA reimbursements explains how to organize that recovery workflow. Keep open cases separate from paid reimbursements and close them only after verifying the outcome.

We file only legitimate, well-documented claims through Amazon's standard processes. Automated mass-filing isn't a substitute for reconciling the event and assembling the evidence.

7. Customer Returns Report

A return reason is useful only when someone acts on it. Open Reports > Fulfillment > Customer Returns, export the completed reporting period, and group the records by ASIN, reason, disposition, and status.

Your red-flag threshold should be a recurring reason that departs from the SKU's normal pattern, especially after a packaging, supplier, or listing change. Don't apply an apparel benchmark to a consumable, and don't assume every customer-selected reason is a confirmed diagnosis.

Separate expectation problems from product defects

Route each cluster to the team that can correct it:

• Not as described: Compare the title, images, dimensions, finish, included components, and variation selection with the shipped product.
• Damaged on arrival: Inspect packaging specifications, shipment records, and available customer evidence.
• Defective or not working: Ask product quality to inspect failure patterns, instructions, and manufacturing lots where traceable.
• Poor inventory recovery: Review returned-unit disposition and determine whether the units can legitimately return to sale.

Say an appliance listing shows a metallic finish while the selected variation ships in black. Correcting the image and variation presentation addresses the expectation mismatch. A discount won't fix the reason customers are returning it.

Calculate recovery rate as sellable returned units divided by total returned units, and use it alongside refund and handling costs when reviewing SKU contribution. Keep the comparison period consistent because returns processed this week may relate to orders placed earlier.

Amazon's FBA report documentation supports using inventory event records to reconcile customer returns and subsequent movements. Match a return's physical disposition with the financial refund rather than assuming both occurred together.

Finish the review with an assigned action: update the listing, inspect a production lot, revise packaging, or investigate fulfillment handling. A reason-code chart without an owner won't change the next shipment.

8. Payments Date Range Reports and Settlement Reports

A bank deposit is cash received, not your only valid revenue figure and certainly not profit. Ordered sales, posted transactions, refunds, reserves, and settlement timing answer different questions.

Open Finance > Manage Payments or the Payments pages available in your account. Use Transaction View, Date Range Reports, and Settlement Reports to explain the movement from customer activity to net proceeds and bank deposits; Amazon's Seller Central finance overview describes access to transaction details including product charges, taxes, expenses, and other amounts.

Explain the variance before disputing it

Your red flag is an unexplained residual after aligning reporting periods and classifying timing differences. A raw gap between Business Reports and a deposit isn't enough to establish a fee error.

• Separate cash timing: Track reserves, deferred amounts, and settlement boundaries outside operating margin.
• Classify deductions: Distinguish referral fees, fulfillment, storage, refunds, advertising where charged, and adjustments.
• Add external costs: Include cost of goods, freight, and advertising billed outside the payment account.
• Inspect unfamiliar entries: Trace them to the underlying order, fee, or adjustment before opening a case.

Say a beauty brand's payout declines while ordered sales remain stable. If the difference is a reserve movement, the immediate issue is cash forecasting. If storage charges have increased, the corrective action belongs in inventory planning.

The discipline behind reconciling bank deposits and billing records applies here: match records, explain differences, and retain evidence. Use settlement reports to reconcile deposits and date-range transactions to analyze activity, without forcing unlike periods to agree.

Finish with a documented bridge from sales activity to net proceeds and cash. Contribution margin still requires your internal product and operating costs.

Where Each Weekly Seller Central Report Lives and What to Watch

On Monday, open the Business Reports detail page first. Its child-ASIN view shows where traffic, conversion, and sales are changing, so you can identify which products need attention before reviewing ads or inventory.

Use each row to make a decision, not just collect figures. For Business Reports, investigate a child ASIN when sessions or ordered sales fall against the comparison period, or when Unit Session Percentage weakens. Check the detail page and offer before changing traffic plans.

In the search term report, focus on spend without orders and terms generating sales. Review bids and search-term targeting, but allow for attribution lag before cutting a term. For inventory, investigate aged or stranded units and days of supply that do not fit demand; balance avoiding stockouts against holding excess inventory.

Account Health and notifications take priority when a policy issue or urgent deadline appears. In Search Query Performance, compare impression, click, and purchase shares to locate where a query loses momentum. Returns, reimbursements, and payments complete the review: use return reasons to identify product issues, check unpaid eligible reimbursements, and reconcile payment activity with sales and settlement cycles.

Turn the Monday Review Into a Weekly Audit You Can Trust

Make Monday's review a sequence of decisions, not a stack of exports. Open Business Reports first to establish which child ASINs gained or lost sales and traffic. The previous week's data is available by the end of Sunday, according to Amazon's Business Reports documentation. Because reports refresh on different schedules, record each export's reporting period and wait for inventory data to finish updating before treating a reconciliation as final.

Then check account health and inventory, followed by advertising, search-query performance, returns, reimbursements, and Payments. Move an urgent policy notice or unavailable bestseller to the top of the queue. For each report, name the metric, set a red-flag threshold that fits the account, and assign an owner and corrective action. A sales or conversion decline calls for an ASIN-level listing and offer check; wasted ad spend calls for search-term and bid review; a cash variance calls for transaction-level reconciliation.

Keep an exception log, not a screenshot archive

Record the reporting period, marketplace, ASIN, metric, trigger, likely cause, owner, next action, and status. Attach the relevant export or transaction evidence. Keep the log focused on decisions:

• Fix immediately: active policy problems, suppressed offers, and confirmed availability issues.
• Investigate before spending: conversion declines, unexplained inventory movements, and unfamiliar deductions.
• Test deliberately: listing changes, keyword expansion, bids, promotions, and replenishment adjustments.
• Verify afterward: confirm the action worked without creating a margin or inventory problem elsewhere.

For pricing, sales-rank context, and holding costs, Online Brand Growth's free Amazon Profit Calculator, Sales Rank Checker, and Storage Fee Calculator can support the review. Its free Unauthorized Seller Playbook covers reseller documentation and removal workflows. Online Brand Growth's Brand Registry & Enforcement service addresses unauthorized seller removal and MAP enforcement through legitimate, documented processes, not the assumption that every competing offer violates Amazon policy.

Automation can bring reports together, but the dates and definitions still need checking. Follow the principles of validating and governing automated reporting when combining sources with different refresh schedules.

Judge the review by the decisions completed: correcting an offer, stopping unprofitable spend, preventing an avoidable stockout, recovering an eligible loss, or explaining a cash variance. Start the next Monday by checking whether those actions held before approving further changes.

Online Brand Growth connects PPC, listing optimization, FBA operations, account health management, and business intelligence reporting. Visit Online Brand Growth or book a free strategy call to discuss reporting gaps affecting Amazon profitability.