Strong Amazon revenue can hide an unprofitable SKU. A trustworthy profitability review requires joining product costs with sales, fees, advertising, fulfillment, returns, promotions, and inventory data, rather than treating Seller Central performance metrics as a profit statement. That distinction is central to reconciling Amazon seller KPIs with actual profitability.
An audit is a revenue protection exercise, not a periodic report review. Start with the problems that could interrupt selling, then work through lost sales, margin leakage, inventory exposure, and administrative controls. A beautifully optimized detail page won't help if an unresolved policy violation prevents you from selling the product.
Build your Amazon account audit checklist around a shared action register. Every finding needs a severity level, an accountable owner, a deadline, and supporting evidence.
- Critical: Selling privileges, product compliance, account access, or payment security require immediate attention.
- High: Suppressed priority listings, significant offer losses, approaching stockouts, and negative contribution margin need active intervention.
- Routine: Content improvements, campaign refinements, and documentation cleanup belong in the scheduled work queue.
Use this as a monthly operating rhythm, with a full review each quarter and an additional review whenever Amazon sends a policy notice or a key metric changes materially. Those are recommended operating cadences, not Amazon requirements. The deliverable isn't a presentation. It's a ranked list of decisions your team can execute.
1. Account Health Dashboard and Performance Metrics
Open Seller Central > Performance > Account Health before reviewing sales. Record the marketplace, account status, unresolved violations, appeal status, and the orders behind performance warnings.
Amazon requires Order Defect Rate below 1%, measured over 60 days, and seller-fulfilled Late Shipment Rate below 4%, measured over 10-day or 30-day periods; negative feedback, qualifying guarantee claims, and chargebacks can contribute to ODR, while late shipment confirmations contribute to LSR, according to Amazon's seller-performance guidance. Treat those limits as boundaries, not operating targets.

Trace the cause, not just the score
Amazon's marketplace-specific Account Health Rating runs from 0 to 1,000, with 200 to 1,000 classified as Healthy and 100 to 199 as At Risk; repeat-policy exposure can create immediate deactivation risk after five infringement violations or two restricted-products violations within 180 days, under Amazon's AHR policy. Keep an evidence repository and compliance calendar, rather than assuming a healthy overall score resolves individual violations.
- Order-level investigation: Match defects to SKUs, packaging, fulfillment partners, and customer complaints.
- Shipping verification: Compare expected ship dates with actual confirmation timestamps and warehouse dispatch records.
- Corrective action: Document the root cause, completed fix, prevention control, and responsible owner.
- Additional checks: Review Pre-fulfillment Cancel Rate, Valid Tracking Rate, buyer messages, and current thresholds displayed in your account.
For example, if late confirmations cluster around a fulfillment partner, establish whether orders shipped late or whether its integration transmitted confirmations late. Those problems require different fixes. Save dated snapshots so the team can distinguish improvement from a temporary change in the measurement window.
2. Brand Registry Status and IP Ownership Verification
A Brand Registry access gap can stall catalog corrections and leave enforcement dependent on someone outside your company. Start in Brand Registry: confirm the enrolled brand, rights owner, administrator, and users who can submit reports. Then compare those records with your trademark documentation, legal entity, and the brand names shown on your priority ASINs.
A manufacturer whose packaging, trademark, and detail page show different versions of its name should resolve the mismatch before creating replacement ASINs or filing broad complaints. Preserve dated evidence, identify the correct brand identity, and use the relevant catalog or Brand Registry process.
Keep ownership, permissions, and evidence aligned
Maintain one current record for the trademark and authorization documents, rights-owner contacts, and Brand Registry administrators. Map priority ASINs to their SKUs, marketplaces, and displayed brand names, noting unresolved corrections. Remove access for former employees or representatives when they no longer have a business reason to retain it.
Review permissions for Brand Analytics, A+ Content, Stores, Sponsored Brands, Transparency, and Report a Violation where those tools apply. Missing access warrants investigation, but it does not identify the cause by itself. Check account roles and eligibility before opening a support case.
For suspected infringement, retain dated screenshots, affected ASINs, seller details, and purchase documentation when appropriate. An unauthorized seller is not automatically selling counterfeit goods. Identify the specific rights or policy issue, then choose the matching enforcement route. Search your brand name and product terms for confusingly similar branding, and distinguish evidence of infringement from ordinary competitor visibility.
3. Listing Quality, Catalog Accuracy, and Suppression Review
Start with the listings that cannot be bought. In Seller Central, open Manage All Inventory, filter for suppressed, inactive, incomplete, and unavailable offers, then open the live detail page for each result. The status column can lag or show only part of the problem.
Rank fixes by revenue exposure and catalog risk. A hero ASIN with a broken variation or missing required attribute outranks a weak bullet point on a low-velocity accessory. A merge that touches reviews or identifiers carries more account risk than a routine title cleanup.

Triage: can the customer buy the right product?
Work each priority ASIN from purchase blockers outward: product type and required attributes, brand and pack quantity, variation family, dimensions, title, bullets, images, and A+ Content. Compare the page to the physical packaged product and the approved specification before editing; mismatches often sit between attributes, media, and copy rather than inside one field.
| Finding | What to record before closing |
|---|---|
| Suppressed or incomplete offer | Exact error, correction submitted, case ID, purchasable status |
| Variation problem | Parent and child logic, whether items are truly the same product, review impact |
| Copy or image mismatch | Attribute value, package photo, live mobile view, owner signoff |
Treat images, search terms, and merges as separate controls
Use product photo guidelines for sellers as a production reference, then confirm current category requirements inside Amazon before approving assets. Keep compliance and persuasion separate: an image can pass policy and still fail to show pack contents, scale, or compatibility.
Check customer language from advertising and Brand Analytics against titles, bullets, and backend terms only after availability is stable. Do not consolidate duplicate-looking ASINs until you confirm the products are identical and the correction follows catalog policy; a rushed merge can turn a content defect into a catalog-control problem. Close the finding by rechecking the live page and inventory status.
4. Buy Box Share, Pricing Health, and MAP Compliance
The Featured Offer can be lost for four different reasons, and price is only one.
Before touching repricers, pull Business Reports > Detail Page Sales and Traffic by ASIN, where available, alongside Pricing > Pricing Health. Compare consistent periods and annotate promotions, stockouts, offer changes, handling-time edits, and repricer adjustments. Rank findings by revenue at stake and account risk: a hero ASIN losing the Featured Offer outranks a long-tail reseller dispute.
Work each commercially important ASIN through one evidence chain: winning seller identity, delivered price, fulfillment method, delivery promise, availability, eligibility, and what changed. One clean example: your merchant-fulfilled promise slips while a competitor keeps faster FBA delivery. Lowering the floor buys orders at worse margin and leaves the operational gap intact.
Set repricer floors from unit economics: fulfillment, fees, returns, promotions, business pricing, promotion stacking, and expected advertising support. Keep channel policy separate from platform eligibility. Use a documented minimum advertised price monitoring process for reseller price patterns, and keep unauthorized-seller, counterfeit, authenticity, or condition complaints in their own lane with dated screenshots and purchase records.
A MAP breach, an unauthorized reseller, and a counterfeit offer are different findings. Don't combine them into a generic removal request.
Judge the fix by contribution after the change. If Featured Offer share rises while margin falls, the finding stays open. Where enforcement is warranted, assign one case owner and retain evidence matched to the contractual, legal, or platform route.
5. Advertising Account Structure and Efficiency Benchmarks
A branded campaign can look efficient while capturing demand that would have converted anyway. That misread is the most common advertising finding I see, so open Campaign Manager with SKU economics and inventory availability beside it. Review Sponsored Products, Sponsored Brands, and Sponsored Display separately, then split branded demand, category discovery, competitor targeting, and product targeting.
ACoS, advertising spend divided by attributed sales, shows reported ad efficiency. TACoS, advertising spend divided by total sales, shows advertising intensity across the channel. Neither metric replaces contribution margin, and neither proves incrementality.
Two reports carry most of the diagnostic weight here, and they answer different questions:
| Report | What it covers | How to use it in the audit |
|---|---|---|
| Sponsored Products Search term report | Customer search terms, or inferred best-match terms for non-search placements, that generated at least a click, with a 65-day lookback window | Find converting queries, irrelevant traffic, and candidates for negative keywords or negative product targets |
| Sponsored Products Targeting report | Configured targets in campaigns that received an impression, measured against impressions, clicks, spend, orders, and sales | Compare keywords, product targets, and match types against what was actually configured |
Search terms describe what shoppers typed or matched. Targeting data describes what you set up. Mixing the two produces the wrong fix.
Each finding lands in one of three decisions. Expansion moves proven queries into controlled tests with clear budgets and ownership. Waste negates irrelevant traffic and investigates inefficient but relevant terms before pausing them. Structure separates branded terms and distinct commercial objectives so performance stays interpretable. Rank them by revenue at stake: a waste finding on your highest-velocity ASIN outranks a cosmetic restructure.
Model the economics with the free Amazon profit calculator, then work the Amazon PPC audit checklist for campaign-level execution. Skip universal efficiency benchmarks. Products with different margins, launch objectives, and replenishment constraints need different thresholds.
6. FBA Inventory Health, Storage Fees, and Aged Stock Risk
Storage fees rarely sink an account. Cash trapped in aged stock does. A SKU sitting in the fulfillment network for months ties up capital you could deploy on a winner, and the fee meter keeps running while you decide what to do with it.
Pull Inventory Performance, inventory-age data, stranded inventory, and replenishment recommendations into one view, then rank every finding by cash at risk and sales at risk rather than by which report looks worst. Amazon's Inventory Performance Index affects fulfillment-center storage capacity; its sell-through calculation uses the preceding 90 days, while its in-stock measure examines 30-day availability weighted by SKU sales over the preceding 60 days, according to Amazon's inventory performance explanation. Keep those measurement windows straight or you'll compare reports that measure different things.

Amazon's guideline of roughly 30 to 60 days of expected sales gives you a starting range for replenishment and excess-stock review under its FBA inventory-management guidance. Adjust it for supplier lead time, seasonality, inbound uncertainty, and launch status before treating any SKU as overstocked.
Work findings in this order:
- Stockouts on high-contribution ASINs first. Compare forecast demand with available, reserved, and inbound units. A top seller going dark costs more than aged-stock fees on a slow mover.
- Stranded inventory second. Resolve the listing problem before assuming the units need discounting or removal.
- Aged stock last. Weigh promotion, liquidation, removal, and continued holding against contribution and current fees.
Replenishing a high-contribution core product can deserve scarce cash before promoting an obsolete accessory. Don't expedite stock just to defend sales volume when the incremental contribution won't cover the expense.
Run the numbers with the free FBA storage fee calculator using current marketplace assumptions. Check SKU-level fee eligibility too: Amazon's AWD guidance includes a 70% auto-replenishment threshold over the preceding 90 days and a 70-day combined historical supply requirement assessed across recent 30-day and 90-day periods, as detailed in its AWD and FBA fee guidance. AWD participation alone doesn't guarantee fee exemptions, so verify each SKU's actual eligibility before including savings in its margin forecast.
7. Reimbursement Recovery and Fee Leakage Audit
A short received shipment on a top ASIN can erase more contribution than a month of aged-stock fees, so start recovery work where revenue and policy risk are highest. Open Reports > Fulfillment > Reimbursements, or the equivalent report in your account, then tie every candidate case to shipment, inventory-adjustment, return, removal, and settlement records.
I rank the queue by dollars at stake and deadline pressure: inbound shortages on profitable movers, repeating fee overcharges, then lower-value return or removal differences. A discrepancy is not automatically payable. Confirm the event type, investigation status, evidence required, and claim window before filing.
Build one case register with the same anchors for every claim: inbound proof such as shipment ID, shipped and received quantities, carton data, and carrier evidence; the inventory trail across adjustment, damage, loss, return, or removal records; the money trail across reimbursement references, settlement entries, fee corrections, reversals, and unresolved differences; and claim administration covering eligibility, filing deadline, owner, evidence submitted, and next action.
For a short shipment, reconcile the manifest and receiving status before opening a claim. Filing early creates follow-up work and can duplicate a discrepancy Amazon already settled. Check packaged dimensions and weight against the values used for fees, document any measurement difference, and request review through the appropriate process before counting a retrospective credit.
Reconciliation rule: Close a recovery case only when the inventory or financial record supports the resolution.
After a fee correction, update SKU economics with the Amazon FBA profit margin calculator guide. Keep the recovery file aligned with clean books for ecommerce sellers by reconciling settlements and keeping reimbursements out of ordinary sales. Separate recurring fee savings from one-time recoveries before forecasting margin.
8. Account Security, User Permissions, Tax Settings, and Notifications
A catalog contractor leaves the business in March. In June, a deposit-method change nobody approved shows up in Account Info, and the recovery email on file still points at the contractor's address. That sequence is why the access review belongs in every audit, and why verbal confirmation that access was cleaned up is not evidence.
Open Settings > Login Settings, User Permissions, and Account Info, using the equivalent navigation shown in your account. Then work through the account in this order:
- Pull the full user list, including connected applications and API integrations, and match each entry to a current employee, agency, or tool the business still uses.
- Remove anything that fails the match. For each person who stays, confirm they hold an individual login and the narrowest permission set their job requires.
- Check verification settings and recovery methods. The recovery email and phone number should belong to the business, not to a person who might leave.
- Identify who can restore account access if the primary administrator is unavailable, and confirm that backup has tested the process.
- Review legal entity details, tax interview status, applicable tax documentation, deposit methods, and charge methods against what finance has on file.
Notifications deserve their own pass. Route operational and policy messages to a monitored shared mailbox, then name a primary owner and a backup for account-health notices, payment issues, customer-service escalations, and security alerts. A shared inbox without explicit responsibility is still an unmanaged queue.
On the tax side, check document status rather than assuming every form carries the same expiration rule. Have the finance or tax owner resolve discrepancies before anyone edits business information, and log who approved each sensitive change so the next reviewer can tell an authorized update from an unexplained one.
For the wider security posture around the account, guidance on how to protect your startup from cyber threats is a useful reference. Tailor Seller Central permissions to how your team operates rather than copying a generic template.
Amazon Account Audit Checklist: 8-Point Comparison Guide
| Audit Area | 🔄 Complexity and Resources | 📊 Expected Outcomes | ⭐ Ideal Use Case | 💡 Key Advantage |
|---|---|---|---|---|
| Account Health Dashboard and Performance Metrics | Moderate; weekly metric reviews, reports, and root-cause analysis | Fewer performance risks and earlier response to policy issues | Monitoring seller eligibility, fulfillment metrics, and account standing | ⚡ Provides measurable early warnings before thresholds are breached |
| Brand Registry Status and IP Ownership Verification | Moderate; trademark records, legal-entity checks, and ASIN mapping | Stronger brand control and access to brand tools | Protecting a registered brand and managing its Amazon presence | ⭐ Enables violation reporting, Brand Analytics, and enhanced brand content |
| Listing Quality, Catalog Accuracy, and Suppression Review | Moderate to high; ASIN-by-ASIN checks of attributes, images, and variations | Fewer suppressed listings and improved detail-page quality | Maintaining catalog accuracy and restoring listing visibility | ⚡ Correcting listing issues can recover visibility without added ad spend |
| Buy Box Share, Pricing Health, and MAP Compliance | Moderate; offer, pricing, and Buy Box monitoring | Improved offer competitiveness and protection of pricing discipline | Diagnosing Buy Box declines, unauthorized offers, or price erosion | 📊 Links offer conditions to a key sales and revenue indicator |
| Advertising Account Structure and Efficiency Benchmarks | High; campaign, search-term, bid, and margin analysis | Reduced wasted spend and better alignment of ads with profitability | Optimizing mature or complex advertising accounts | 💡 Connects advertising efficiency to contribution margin and total sales |
| FBA Inventory Health, Storage Fees, and Aged Stock Risk | Moderate; inventory, age, fee, and replenishment reviews | Lower avoidable storage costs and fewer stranded units | Managing excess, aging, or seasonal FBA inventory | 📊 Identifies inventory risks before fees or stockouts escalate |
| Reimbursement Recovery and Fee Leakage Audit | Moderate to high; shipment records, product measurements, and claims tracking | Recovered eligible reimbursements and corrected recurring fee errors | Reviewing FBA losses, inbound discrepancies, and overcharges | 💡 Can recover funds and reduce ongoing fees through corrections |
| Account Security, User Permissions, Tax Settings, and Notifications | Low to moderate; access, tax, banking, and alert checks | Reduced access risk and fewer missed alerts or payout holds | Securing account administration and maintaining operational continuity | ⭐ Helps prevent unauthorized changes and delays from outdated settings |
Turn Audit Findings Into an Operating Routine
The best Amazon account audit produces a prioritized action list, not the longest spreadsheet. Begin with active account-health warnings, compliance issues, access concerns, and open Plans of Action. Then address suppressed listings, Featured Offer losses, negative-contribution advertising, inventory exposure, and unresolved recoveries.
Rank findings using account risk, contribution at stake, urgency, confidence, and dependencies. Don't automatically put the largest revenue opportunity first. Restoring a listing may depend on compliance documentation, and expanding a profitable campaign may be inappropriate until replenishment is secure.
Give every finding a closeout standard
Your action register should make decisions easy to review:
- Finding and evidence: Identify the marketplace, ASIN or SKU, report period, screenshots, and relevant case IDs.
- Business impact: Separate revenue exposure, contribution opportunity, cash recovery, and avoided cost.
- Accountability: Name the decision-maker, execution owner, deadline, and escalation contact.
- Dependency: Record what must happen before the action can proceed safely.
- Validation: Define the evidence that proves the issue is fixed and the financial assumptions remain valid.
Keep estimates separate from realized results. A submitted reimbursement claim isn't recovered cash, and an approved listing edit isn't proof that the published page is correct. Similarly, a lower advertising bill doesn't establish better profitability if total contribution falls.
Use a weekly operations review to resolve blockers and a monthly financial review to reconcile SKU performance. During the full quarterly audit, revisit permissions, documentation, repricing controls, catalog accuracy, and assumptions that routine dashboards don't explain. Reopen the review sooner when policy notices or material operating changes justify it.
Monitor competitive visibility with the free sales rank checker, but interpret rank alongside availability, pricing, traffic, and contribution. A visibility change is a reason to investigate, not a complete diagnosis.
The most useful workflow connects teams. Advertising owners need inventory constraints before increasing budgets. Operations needs demand plans before committing cash. Finance needs fee corrections, returns, and advertising costs reflected in the SKU profit bridge, while brand owners need a clear distinction between channel-policy disputes and actionable infringement.
Once the urgent backlog is under control, prevention deserves a place in the same register. Add packaging checks where defects recur, approval controls where pricing changes create losses, and documented handovers where access becomes unclear. That's how the audit becomes an operating routine rather than a repeated cleanup exercise.
Online Brand Growth helps brands connect Amazon advertising, catalog management, FBA operations, and account health, with its 360 Brand Protection program covering unauthorized seller removal and MAP enforcement. Book a free strategy call to review your audit findings and prioritize the actions that protect selling access and contribution margin.
