By Naeela
Use the Amazon Inventory Ledger report to explain how a defined stock balance changed, then investigate any difference before signing off the month. Start with Summary for the movement totals and Detailed for the underlying events. Keep 3 decisions separate: reconciling units, valuing inventory and establishing any reimbursement entitlement. A workbook can balance while the stock is damaged, unavailable or incorrectly valued. It can also show an unexplained difference without proving that Amazon owes the brand money.
Key Takeaways
- Use 2 views for different jobs: Summary checks the period's balances and movements; Detailed traces individual events and references.
- Freeze 1 report scope before calculating: period, location aggregation, identifiers and disposition. Adding country totals to their fulfillment-center components counts overlapping inventory.
- Amazon's official documentation describes 18 months of historical movements in Detailed. Preserve the source exports you need rather than assuming indefinite recovery later.
- A hypothetical 1,000-unit opening balance with the movements below should close at 880 units. A reported 875 requires a 5-unit explanation, not a balancing entry labeled “Other.”
What does the Inventory Ledger report establish?
It records inventory quantities and movements within a defined scope. Amazon's official FBA report documentation describes Summary as an inventory statement covering starting balance, receipts, customer orders, returns, adjustments, removals and ending balance. Detailed supports investigation of movements such as shipments, returns, damage, loss and found stock.
That is useful evidence for a close, but it doesn't finish the accounting. A quantity record does not determine the appropriate cost basis, reserve, impairment or legal ownership treatment. Nor does a “lost” event, on its own, establish an open reimbursement claim. Those decisions need their applicable policies and supporting records.
The reader most likely to need this control is the controller or Amazon lead at a brand generating about $5M+ a year on Amazon. The month-end workbook shows one quantity, the dashboard shows another, and the team wants a number it can sign off. Begin by defining what each number measures. A current availability snapshot and a historical month-end balance may both be correct while answering different questions.
Our inventory planning guide explains why stock present in the network isn't necessarily buyable cover. The ledger helps trace the quantity. The forecast still needs its disposition and credible availability date.
What population are you actually reconciling?
Write the scope above the calculation. Include the marketplace or store, period boundaries, country or fulfillment-center aggregation, product identifiers, disposition and report-generation date. Keep the source file unchanged and work from a separate analysis copy.
An ASIN can be too broad for an exception. Amazon's report documentation allows filters for fulfillment network SKU (FNSKU), merchant SKU (MSKU) and ASIN, including active FNSKU mappings for an MSKU or ASIN. If a dashboard collapses those mappings while your export isolates one FNSKU, the totals won't represent the same population. Check the mapping before concluding that units disappeared.
Location aggregation creates a similar problem. Summary can aggregate by country or fulfillment center. A country total and its component FC rows are alternative levels of view, not independent stock to add together. A transfer may change where units sit without representing a sale or a disappearance from the network. Preserve the location scope through the investigation.
Keep reporting periods nonoverlapping. If you refresh a monthly export, replace the corresponding analysis rows or identify the revision. Appending the new copy beneath the old one doubles the same movements. Summing daily snapshots of ending stock across a month is another mistake: it produces a total of snapshots, not the quantity left at month end.
Disposition matters too. Sellable units, damaged units and stock in other states should not be silently collapsed into an availability answer. A movement from one disposition to another can reduce a sellable balance without reducing all stock by the same amount. Inspect both sides where the report records a reclassification, rather than treating every negative movement as shrink.
When should you use Summary, and when should you open Detailed?
Use Summary to locate the unexplained movement. Use Detailed to find the event that explains it. Don't begin by manually examining every row when the difference may come from a mismatched month or location.
| Decision | Starting evidence | What it cannot establish alone |
|---|---|---|
| Does the period roll forward? | Summary balances and movement categories | Which individual event caused a residual |
| Which event needs investigation? | Detailed event, reference, quantity, location and disposition | Whether a reimbursement is owed |
| Can the stock support demand? | Reconciled quantity plus current status and availability evidence | A guaranteed future sellable date |
| What value belongs in the accounts? | Quantity evidence plus finance's cost and valuation records | Value from a unit count alone |
Detailed includes fields such as reference ID, event type, quantity, fulfillment center, disposition, reason, and reconciled or unreconciled quantities. Availability of a field doesn't make it a complete diagnosis. Trace the reference to the relevant record, then check that its reason and supporting evidence agree.
Amazon describes both API ledger reports as requested-only. That doesn't prevent a separate integration from requesting and refreshing them. It does mean that the presence of a scheduled spreadsheet or dashboard shouldn't be confused with proof that a fresh underlying report arrived successfully.
How do you build a roll-forward without forcing it to balance?
Normalize movement signs only after checking the actual export's definitions. If a customer-shipment quantity is already negative, subtracting that signed value again creates a false increase. Keep raw fields beside normalized calculations so another person can inspect the treatment.
In this hypothetical example, the movements are expressed as signed changes. Don't apply the same addition to every raw Summary column: the fields aren't interchangeable.
| Movement | Signed units |
|---|---|
| Starting balance | 1,000 |
| Receipts | +500 |
| Customer shipments | -620 |
| Customer returns | +40 |
| Removals | -30 |
| Lost units | -20 |
| Found units | +10 |
| Expected ending balance | 880 |
The calculation is 1,000 + 500 - 620 + 40 - 30 - 20 + 10 = 880. Suppose the matched closing report shows 875. Record a residual of negative 5 units and assign an investigation. Don't change a movement to make the bottom line agree.
Start with the cheap checks. Is the period identical? Was an export appended twice? Does the closing balance use the same location and disposition? Did a negative field get reversed? Then inspect Detailed for the unresolved event and its references. A 5-unit disposition movement might explain a sellable-only difference, but that is a hypothesis until the actual records establish it.
Keep transfers and in-transit quantities explicit. Don't add them into the bridge merely because the report contains a column for them. Check how the selected balance defines its population and whether those units are already represented elsewhere. When comparing reports, write a separate scope bridge for any difference in treatment.
An explained residual can still require action. A documented disposal may reconcile quantity perfectly while exposing an avoidable stock decision. A later found event may explain an earlier loss, but both records need their chronology and identifiers. Reconciliation tells you where to investigate next; a zero residual doesn't prove the operation is healthy.
How do you investigate a difference without turning it into a claim too soon?
Create an exception record with the product identifiers, period, location, disposition, quantity, event type and reference. State what remains unknown and which record could resolve it. “Five units don't reconcile” is a useful starting fact. “Amazon owes us for five units” is a separate conclusion.
For a receipt difference, trace the inbound reference and the corresponding shipment evidence. For a removal, compare the authorized request with processed outcomes. For a loss followed by a found event, check that the records concern the same population and that the later event hasn't already resolved the exception. Don't combine unrelated positives and negatives just because they cancel numerically.
Preserve the distinction between a reason code and the business explanation. The code may direct you to damage, a transfer or another adjustment, but it doesn't show who approved the original replenishment or whether the brand's bookkeeping recognized the event correctly. The operator and controller have different parts of the investigation.
When escalation is necessary, send the smallest evidence packet that establishes the discrepancy and the decision required. Our Seller Support evidence guide covers case documentation. A clean packet reduces reconstruction work; it doesn't guarantee a platform decision, a payment or a response date.
What should stop a close when an export is empty or stale?
An empty file should trigger validation, not a zero-inventory conclusion. Amazon's documentation says Summary can return empty data when the requested start and end dates don't fit the chosen aggregation. It specifies complete month boundaries for monthly data and matching week boundaries for weekly data. The documented defaults are country aggregation and monthly periods.
Check the request before diagnosing missing inventory. Confirm the period, aggregation, filters and report status. A daily check made with an unintended monthly default may not answer the daily question at all. Change the request deliberately and retain the failed request's parameters in the investigation record.
Freshness needs its own check. Record when the export was obtained and the latest relevant event period it contains. A file downloaded today can still contain stale underlying data. Conversely, a quiet SKU might legitimately have no new events. Use expected activity and other appropriate inventory records to distinguish those situations; don't infer an outage from an unchanged row.
Set an internal stop rule before close. For example, finance might withhold sign-off for a material SKU when the required period is missing or expected receipts are absent from an otherwise completed export. The materiality threshold belongs to the brand. No universal refresh promise or automatic close deadline follows from this method.
Keep unresolved items visible if the business must proceed with a provisional number under its accounting policy. Name the owner, evidence gap and next review date. A provisional close is a controlled management decision. Silently treating the last good file as current evidence hides the very uncertainty the control should expose.
How do units, inventory value and reimbursement stay separate?
Maintain separate conclusions for each. The unit worksheet explains quantity movement. The valuation work applies the brand's cost and accounting policies to the supported population. A claim assessment establishes eligibility, evidence and any applicable process under current terms.
Suppose a hypothetical reconciled population contains 880 units and finance uses an assumed original unit cost of $12. The gross extension is $10,560. That multiplication doesn't establish realizable value, sellable stock or a receivable. Damaged condition, reserves, ownership and other accounting treatments may change the financial conclusion.
The same restraint applies to loss. Don't multiply every negative quantity by retail price and call the result recoverable revenue. A customer shipment is usually an expected movement, a transfer may remain in the network, and a loss may later be found or already addressed. Current eligibility and supporting evidence must be checked separately before anyone promises cash.
We would refuse a recovery estimate built solely from unexplained ledger negatives. It may make an attractive sales pitch, but the brand could plan working capital around money it never receives. The accountable recommendation is narrower: reconcile the event, establish its status, then evaluate the actual next action.
What should the close evidence packet contain?
Keep the original exports, scope definition, calculation and exception register together. Add the references that explain material differences and the controller's separate valuation conclusion. The final reviewer should be able to reproduce the ending quantity without editing the source data or guessing which month a tab represents.
State whether the result is reconciled, provisional or unresolved. Show the quantities behind material open items and assign each one an owner. A task such as “check inventory” leaves the decision unclear. “Confirm the disposition and reference for the five-unit residual before sign-off” gives the operator something they can complete.
Use the same control next month, with a versioned export and explicit handling of revised periods. Investigate repeated exceptions as an operating problem. If one receiving flow continually fails the close check, the response may involve shipment preparation or timing, not a better spreadsheet. Connect the finding to the SKU-level contribution review before funding more demand against an unreliable stock assumption.
Where does ALFI fit, and where does it not?
ALFI fits when an established brand needs inventory truth connected to demand, advertising, catalog decisions and contribution. Naeela leads strategy and accountability conversations, while senior operators own delivery. Our 18-client ceiling protects the attention needed to carry an exception beyond the report and into a decision.
We won't accept a PPC-only mandate that makes us responsible for profit while hiding stock and cost records. A client must provide access and economic context; we owe clear ownership, candid advice and follow-through. That boundary can mean declining revenue rather than selling a disconnected service.
An internal controller with a sound operating team may only need a reporting integration, an accountant or a specialist claims review. Use that narrower help when it solves the actual gap. ALFI doesn't replace professional accounting judgment or turn inventory events into guaranteed recoveries.
What is the difference between Inventory Ledger Summary and Detailed?
Summary groups balances and movements for a selected period and location scope. Detailed supplies event-level information such as references, quantities, fulfillment centers and dispositions. Use Summary to locate the difference, then Detailed to investigate it. Neither view alone determines inventory valuation, confirms reimbursement eligibility or establishes when stock will become buyable.
How much history does the Detailed report provide?
Amazon's official report documentation describes 18 months of historical inventory movements in Detailed. Preserve required source exports and supporting records under your own retention policy. Don't assume an integration's advertised backfill or stored history changes Amazon's native report coverage. Verify the actual report and integration when retrieving an older period.
Why might a Summary export contain no rows?
An invalid combination of date boundaries and aggregation can return empty data, according to Amazon's documentation. Check the requested period, location scope, product filters and report status before treating emptiness as a stock result. Monthly and weekly requests require their appropriate period boundaries. An empty export does not establish zero inventory.
Does a lost or unreconciled quantity mean Amazon owes reimbursement?
No. It identifies inventory evidence that needs investigation. Check the event, reference, later movements and current claim rules, including whether the matter has already been resolved. Quantity reconciliation and reimbursement eligibility are separate decisions. Don't promise cash, use retail price as a default recovery amount or assume every negative event is loss.
What to do this week
Choose one material FNSKU and one completed month. Freeze the report scope, preserve Summary and Detailed exports, and reproduce the ending balance with signed movement checks. Investigate the residual before adjusting the workbook. Have finance record valuation separately and route any potential claim through its own evidence review.
If nobody owns the connection between that stock truth and the Amazon growth plan, discuss ALFI's end-to-end operating mandate. If an internal owner already does, give them a repeatable close packet and authority to stop an unsupported sign-off.
