Amazon Seller Reports: A Weekly Checklist for Sales, Stock and Profit

Amazon reports answer different questions. Listings tell you about products and stock. Orders tell you about purchases. Transactions explain the financial entries attached to selling activity.

A useful weekly review brings those views together without adding incompatible totals or treating missing information as a good result.

Here is a repeatable checklist for an Amazon seller using Margin Copilot. It is a suggested workflow, not a promise that every report reconciles automatically.

1. Choose a period you can compare fairly

Pick a review window and record the report download dates. Use the same marketplace, currency and comparable period lengths when examining changes.

A recent period can still contain incomplete financial activity. Purchase dates and transaction posting dates are not interchangeable, so an Orders total and a Transactions total for the same calendar dates need not match.

If a number looks surprising, check the date definitions and data freshness before changing the business.

2. Refresh products and available inventory

Import an Active Listings or Amazon Fulfilled Inventory report to refresh the product picture. Review quantities, search for priority SKUs and investigate low-stock items.

A listing price is not sales revenue. Available inventory is not evidence that those units sold. Keep this report focused on what you have and what may need attention.

Use the report-download FAQ for report locations and download guidance. Seller Central menus can differ by marketplace or change over time.

3. Review Orders for demand

Use an Orders report to examine units sold, product sales and recent activity. Margin Copilot's sales calculations exclude cancelled items and items with a quantity of zero or less.

Check the currency before comparing totals. Taxes, shipping and discounts also deserve a separate look rather than being mistaken for additional product earnings.

Useful questions include:

• Which SKUs sold more or fewer units?
• Did the average selling price change?
• Are low-stock products also important sellers?
• Does the review period contain enough activity to support a decision?

4. Review Transactions for financial movement

Transactions contain signed financial values, including charges and adjustments. Review those entries to understand net proceeds, fees, refunds and account-level financial activity.

Do not add an Orders sales figure to a Transactions figure and call the result revenue. They can describe overlapping activity from different perspectives.

Also, do not assume net proceeds are total business profit. Product costs and costs outside the attributable order entries still matter. Account-level service fees should not disappear simply because they are not allocated to individual SKUs.

5. Check product costs before reviewing profit

Maintain unit costs and their effective dates in the Costs area. A sale needs a cost record effective on or before its purchase date for historical contribution to be meaningful.

In Margin Copilot, attributable contribution uses single-SKU order net proceeds minus historical COGS. Multi-SKU orders are not arbitrarily split between products, and missing costs are not treated as zero.

If you use a separate SKU profitability report, remember that its profit figures are a different input from the order-and-transaction contribution view. Check the scope before comparing them, and never add the two profit totals together.

A fictional $100 improvement is less convincing if a large share of relevant sales still lacks costs. Fix coverage first, then decide what the change means.

6. Turn findings into a short action list

Choose a few decisions rather than trying to fix everything at once:

• Check replenishment options for a low-stock, healthy-contribution SKU.
• Investigate a negative-contribution product's price, fees and unit cost.
• Inspect refund-related changes before increasing stock.
• Add missing historical costs.
• Refresh an old report before acting on its alerts.

Margin Copilot's Action Center and Profit Intelligence can help surface issues from the imported data. Treat confidence and coverage information as part of the finding, not as fine print. A small sample or incomplete period may justify monitoring rather than an immediate price change.

Record what you chose to do and check the outcome at the next review. An alert identifies something to investigate; it does not establish the cause.

Start with the reports you already have

You do not need to rename supported report files: Margin Copilot recognizes the file type from its contents. Re-importing supported reports updates matching records rather than intentionally creating a second copy of the same sale.

Direct Amazon account linking is being worked on; the current workflow uses report uploads. Try the example gardening store first, or use the free profitability calculator for a quick cost-and-price scenario.

A good weekly review ends with a clear next action and a clear understanding of what the numbers do—and do not—cover.