Product help

Help with FBA report auditing

Start with these report and reconciliation checks. There is no account, upload history, or server copy for support to inspect.

Safe support

Describe the behavior, not the report

Include the browser and version, operating system, file extension, report header names, approximate row count, and exact on-screen error. Do not include report rows, credentials, ASINs, SKUs, case IDs, costs, customer information, or screenshots containing them.

support@odvero.com Return to audit

Common issues

A report file is not accepted

Use a UTF-8 CSV, TSV, or tab-delimited TXT file no larger than 5 MB and 100,000 data rows. Export the Inventory Ledger detailed report and Reimbursements report without converting them to XLSX or PDF.

A required column is missing

Keep the original report headers. The ledger needs date, quantity, reason, and FNSKU or seller SKU. Reimbursements needs approval date, reason, reimbursed quantity, and FNSKU or seller SKU. A header-only Reimbursements report is valid.

A negative ledger row was not classified

This version deliberately supports only clearly identified fulfillment-center lost or misplaced events and warehouse-damaged events. Other reason codes, inbound, removal, customer-return, and ambiguous rows are left unsupported instead of being guessed.

A reimbursement says likely matched

The tool allocates net positive reimbursement quantity by item, supported reason category, and chronology. That is a review lead, not proof. Confirm the reimbursement ID, amount, reason, case, and later reversal in Seller Central.

The result disappeared after refresh

The workspace is not persisted and Odvero cannot recover it. Reopen the source reports and run the audit again, or export CSV and Markdown before leaving the page.

A download did not start

Check whether the browser blocked local downloads and retry. The CSV quotes every cell and neutralizes string values that spreadsheet software could interpret as formulas.