3PL and FBA inventory reconciliation: find lost units before the claim window closes

Brands that split stock between a 3PL and Amazon FBA keep three sets of books for the same units: the 3PL's warehouse system, Amazon's Inventory Ledger, and the catalog that drives listings and reorders. They rarely agree, and the gaps between them are where units, cash and claim deadlines go missing.

Why don't 3PL, FBA and catalog counts match?

Counts drift for five ordinary reasons, and two of them are timing, not loss.

• In-transit units. A replenishment shipment leaves the 3PL's on-hand count days before Amazon receives it. Untracked by shipment ID, it looks like a loss.
• Receiving variances. Your 3PL or Amazon receives a delivery short, over or with the wrong item. Units without correct labels can land under an Amazon-created "Amazon.Found" merchant SKU, and show as stranded inventory until listed.
• Shrinkage. Damage, mispicks, miscounts and theft. Amazon logs these as lost, damaged or found adjustments; a 3PL may only surface them at the next cycle count.
• Identifier mismatches. The 3PL tracks its item code, Amazon tracks FNSKU, your catalog tracks your SKU. One unmapped bundle breaks the comparison.
• Inventory states and cut-offs. Fulfillable, reserved, researching and unfulfillable are separate buckets, and Amazon's ledger shows "unknown events" mainly when parts of one event fall in different reporting periods. Totals taken at different cut-offs show variances that aren't real.

Where does inventory go missing between the 3PL and FBA?

Every handoff has its own evidence and its own clock.

Stage	What drifts	Evidence	Clock
Supplier to 3PL	Short, over or wrong-item receipts	PO, supplier invoice, receiving report	Your supplier and 3PL terms
Inside the 3PL	Shrinkage, miscounts	Cycle counts, WMS adjustment log	Your 3PL contract
3PL to FBA	Shipped, not yet received	Shipment ID, tracking, bill of lading	Auto-close 45 days after creation (75 international)
FBA receiving	Units expected vs located	Shipment Contents tab, ownership and delivery proof	Claim within 9 months of delivery
Inside FBA	Lost, damaged, found	Inventory Ledger, Inventory Defect and Reimbursement portal	Claim within 60 days of the report
Catalog	Sellable quantity wrong	Listing quantities, replenishment plan	Every day you sell or reorder

What does monthly reconciliation actually cost?

The visible cost is time: exporting counts from every system, lining them up and chasing rows that don't tie.

The larger costs are quieter:

• Expired recoveries. A monthly close can use half the 60-day window for fulfillment center losses before anyone looks, and a variance carried over can miss it entirely.
• Bad reorder math. If the catalog counts units stuck in receiving or researching, replenishment triggers late and you stock out.
• Bills and margins you can't check. Amazon Supply Chain's guide to 3PL pricing says storage is typically billed by the space your inventory occupies. When records and shelves disagree, you can't check that bill, and paper-only units overstate inventory value and margin.
• Unexplained write-offs. Untraced variance becomes a year-end adjustment with no record of where the units went.

To size your gap, multiply the units in unexplained variance by landed cost, add reconciliation hours at a loaded hourly rate, then add claims that expired unfiled.

How does Amazon reconcile FBA shipments, and what are the deadlines?

Each inbound shipment moves through In transit, Delivered, Checked in, Receiving and Closed. It closes once every unit is confirmed received or 45 days after creation (75 international), whichever is first. Reconciliation usually takes 2 to 30 days, occasionally 60, and investigation opens only after Closed. Then the clocks are strict:

• Inbound shortages: file within nine months of verified delivery, one claim per shipment. You need proof of ownership, such as a supplier invoice with date, product names and quantities, and proof of delivery: for LTL or FTL, a carton count and pickup weight document stamped by Amazon at the fulfillment center; for small parcel, active tracking IDs. Editable files like spreadsheets are not accepted.
• Fulfillment center losses: file within 60 days of the loss appearing in the Inventory Ledger or the Inventory Defect and Reimbursement portal.

The Inventory Ledger is Amazon's record: a running balance per FNSKU and disposition with up to 18 months of history. It replaced six older inventory reports, Amazon recommends reconciling by FNSKU, and it is available through the Selling Partner API, which makes a daily automated match possible.

How does Growth OS reconcile 3PL and FBA inventory daily?

Growth OS is built to make reconciliation a daily job. It is deployed on your own accounts and infrastructure and connects to your Amazon and 3PL data. Custom code we build is yours, the base is licensed to you, and your data stays yours.

1. Pull every source daily. Ledger detail, FBA inventory states and inbound status through SP-API, your 3PL's on-hand, receipts and adjustments (by API or file export), and catalog quantities.
2. Map identifiers once. SKU, FNSKU, ASIN and 3PL item code, bundles included.
3. Match three ways. On each side, opening balance plus receipts and adjustments, minus shipments and removals, should equal closing balance; in-transit units are held by shipment ID.
4. Flag variances with evidence. Anything over your threshold becomes a record with the rows behind it and its claim deadline.
5. Route the fix. FBA losses and inbound shortages are queued as reimbursement claims for your team to review and file in Seller Central; 3PL discrepancies go to your warehouse contact.
6. Write back true stock. Reconciled, sellable quantities flow to the catalog and replenishment.

Where your 3PL or ERP needs a custom connector, we build it on the base system. The reconciliation and sync layer draws on the work behind Seller7, a multi-marketplace seller OS used by 700+ sellers across 20+ marketplaces.

Find your reconciliation gap

A quick test: for your top 20 SKUs, add 3PL on-hand, units in transit to Amazon, and every FBA bucket (fulfillable, reserved, researching, unfulfillable, still receiving). Compare the total with units owned per your books, and the sellable part with your catalog. If either doesn't tie and nobody can say why, the gap is worth closing.

The free Quick Scan in the Ops Gap Diagnostic works from five standard Amazon reports and returns your top three operations gaps, each with a yearly dollar estimate. The paid Deep Diagnostic covers every gap on every channel you sell on, with evidence. If you already know the gap, see how Growth OS closes it.