Does the first Amazon FBA reimbursement scan require Seller Central credentials?

No. The first-pass workflow is designed around seller-exported reports and does not require a Seller Central password, API connection or automated agent access.

What FBA reimbursement windows does the scan check?

Recovery OS versions deadlines by event date. Amazon's October 15, 2025 update includes 60 days for lost or damaged items, 45-105 days after refund or replacement for customer returns, 15-135 days from shipment creation for lost removal orders, and 120-day windows for specified removal damage and grading cases.

How is manufacturing cost handled in the scan?

For policy paths where Amazon uses manufacturing or source cost, the scan compares seller-supported cost to the reimbursement basis and excludes shipping, handling, customs duties and other costs Amazon states are outside that manufacturing-cost definition.

Does a flagged Amazon FBA event mean money has been recovered?

No. A flag is a candidate for review. Recovery OS keeps candidate value, posted Amazon credits and cash actually received in separate ledger states.

RECOVERY OS · AMAZON FBA

Find missed FBA reimbursements before the claim window closes.

A seller-controlled reconciliation scan for lost or damaged inventory, customer returns, removal orders and reimbursement mismatches. Start with exported Seller Central reports—no password, no API connection and no automated claim filing in the first pass.

Request a scope-only scan See all Recovery OS lanes

Public intake is scope-only. Do not upload Seller Central credentials, API keys, bank information, supplier invoices or sensitive account exports through the public form.

Why this lane is worth testing

Short, policy-driven windows

Amazon's current FBA reimbursement windows can be as short as 60 days for lost or damaged items. A deadline-first reconciliation can surface cases that deserve seller review before they expire.

Export-only first pass

The first scan can work from Reimbursements, Inventory Ledger, returns and removal-order exports. That keeps the initial workflow read-only and avoids a long Seller Central integration.

Seller stays in control

Recovery OS prepares evidence and deadline status. The seller decides whether and how to file. No claims are submitted automatically and no Amazon agent access is used in this version.

What the engine checks

FC lost / damaged gapInventory-ledger loss or damage events with no matched automatic reimbursement.

Customer-return gapRefund or replacement events reconciled against return outcomes and reimbursements inside the applicable window.

Removal-order lossLost removal shipments reconciled against receipts, reimbursements and the current filing window.

Removal damage / gradingDamage or grading events reviewed only when event linkage and policy timing are supportable.

Manufacturing-cost mismatchSeller-supported source cost compared with Amazon's reimbursement basis, excluding shipping, handling and customs costs that Amazon's policy excludes.

Auto-reimbursement + deadline QAAlready-reimbursed events are removed first; remaining candidates are classified OPEN, NOT YET OPEN, AT RISK, EXPIRED or UNKNOWN.

Minimum data for the first-pass scan

Reimbursements + Inventory Ledger

Event date, event type, SKU/FNSKU/ASIN, quantity, reimbursement reference and amount where available.

Returns + removal reports

Customer-return and removal-order identifiers, dates, quantities and current outcomes for cross-report reconciliation.

Optional source-cost evidence

A seller-provided manufacturing or source-cost table is used only when validating a cost-basis discrepancy. Supporting invoices are not requested through the public form.

A synthetic dataset can be used to validate the workflow before any real seller data is handled.

Evidence Pack, not a black-box recovery number

Each candidate carries the event, SKU/FNSKU/ASIN, source-report rows, auto-reimbursement match, current policy window, missing evidence and recommended seller action. Recovery OS keeps candidate value, posted credit and cash received separate.

Candidate→Seller review→Filed by seller→Credit posted→Cash received

Pilot pricing experiment

FIXED-FEE RECONCILIATION SCAN

$495

Proposed pilot for one marketplace, up to 90 days of bounded clean exports and up to 1,000 event rows. Includes written findings and Evidence Pack. No contingency fee, Seller Central login or claim filing is activated by this page.

Best-fit seller

Established FBA seller with meaningful inventory throughput, a recent unreconciled period and the ability to export the relevant Seller Central reports.

Target first value

Initial exception list the same day or within one business day after clean exports are received; evidence validation comes before anything is called recoverable.

Current Amazon policy points used by this scan

Claim windows effective October 15, 2025: lost/damaged within 60 days; customer returns 45–105 days after refund/replacement; removal lost 15–135 days from shipment creation; removal damaged within 120 days of delivery; removal grading within 120 days of removal; re-evaluation within 90 days.

Reimbursement basis effective March 10, 2025: eligible pre-order lost/damaged inventory is reimbursed using manufacturing/source cost; Amazon states that shipping, handling, customs duties and other costs are excluded.

Automation boundary: Amazon added Agent Policy requirements effective March 4, 2026 for automated software or AI agents accessing Amazon Services. This pilot avoids agent access entirely.

Amazon: FBA claim-window update Amazon: manufacturing-cost reimbursement policy Amazon: 2026 Agent Policy / BSA update Amazon: authorize a Service Provider

Why we are not promising a recovery amount

Amazon already proactively reimburses many simple FBA loss/damage cases, current windows are narrow, and the reimbursement basis changed. A flagged event can be auto-reimbursed, expired, unsupported or valid. The scan is designed to prove which state applies before any seller action.