[Feature Request] Expose AWD Inventory Ledger Report via Reports API for movement history and financial reconciliation

[kmizzi]

Summary

The AWD API provides current inventory levels via listInventory, but sellers have no programmatic way to access AWD inventory movement history. The AWD Inventory Ledger Report exists in Seller Central (visible at /reportcentral/AWD_INVENTORY_LEDGER_REPORT/1) but is not accessible via the SP-API Reports API.

This creates significant challenges for sellers who need to:

• Track FIFO/weighted-average inventory costing through AWD
• Reconcile AWD movements with their accounting systems
• Detect and account for AWD inventory adjustments

---

Current State: What IS Available

✅ AWD API listInventory - Current inventory levels, expiration dates, prep details
✅ AWD API listInboundShipments - Inbound shipment status
✅ AWD API replenishment data - Units in transit to/from FBA

These are valuable, but they only show current state—not how we got there.

---

The Gap: What is NOT Available

❌ Historical inventory movements - When did inventory arrive at AWD? When did it ship out?
❌ Movement timestamps - Exact dates for receipts, transfers, adjustments
❌ Adjustment details - Damages, losses, corrections, inventory reconciliations
❌ AWD → FBA transfer history - Quantity, date, and cost basis for each transfer
❌ Receiving discrepancies - Shipped 100 units, AWD received 95—where's the delta?

---

Business Impact

1. Inventory Costing is Broken

Sellers using FIFO or weighted-average costing cannot track cost flow through AWD:

Purchase Order → AWD Receipt → AWD Storage → AWD → FBA Transfer → FBA Receipt → Sale
       ↑              ↑              ↑              ↑
   Cost known    Cost assigned   Cost sitting   Cost transferred
                  to AWD layer    in AWD         to FBA layer
                       ↑              ↑              ↑
                   ✅ Can infer   ❌ Can't track  ❌ Can't track
                   from PO        movements       when/how much

Without ledger data, we cannot:

• Know when inventory was received at AWD (to create cost layers)
• Know when inventory left AWD (to consume cost layers)
• Calculate accurate AWD inventory valuation at any point in time

2. Accounting System Integration Fails

For businesses integrating with ERPs (NetSuite, QuickBooks, SAP, etc.), AWD is a black box:

• Cannot book AWD receipts as inventory transactions
• Cannot track AWD → FBA as internal transfer journals
• Cannot detect shrinkage or post adjustment entries
• Month-end close requires manual Seller Central downloads

3. Audit Trail Does Not Exist

Without movement history:

• Cannot explain inventory variances to auditors
• Cannot trace a unit's journey through the supply chain
• Cannot identify when/where shrinkage occurred

4. The Workaround is Fragile

Currently, sellers must infer AWD outbound movements by:

1. Detecting FBA inbound shipments where shipFrom address matches AWD
2. Assuming the FBA receipt equals the AWD shipment

This is problematic because:

• It's delayed (we learn about AWD shipment when FBA receives, not when AWD ships)
• It's incomplete (no adjustment data, no discrepancy detection)
• It's fragile (address matching can fail)

---

The Ask

Primary Request: Expose the AWD Inventory Ledger Report via the Reports API

The report already exists in Seller Central. Exposing it via createReport / getReport would provide:

Field	Purpose
Date/Timestamp	When the movement occurred
FNSKU / MSKU / ASIN	Product identification
Event Type	Receipt, shipment, adjustment, transfer, etc.
Quantity	Units added or removed
Disposition	Sellable, unsellable, damaged, etc.
Reference ID	Link to shipment, transfer, or adjustment
Warehouse/FC	Which AWD facility

Alternative: Add historical movement data to the AWD API (similar to how FBA has ledger endpoints)

---

Why This Benefits Amazon

1. Increased AWD adoption - Sellers hesitant about AWD visibility will adopt more readily
2. Reduced support tickets - Fewer "where's my AWD inventory?" escalations
3. Ecosystem growth - 3rd party software can build complete AWD integrations
4. Competitive parity - Other 3PL solutions provide movement history APIs

---

Related

• Issue AWD in Reports API #4360 (closed) - "AWD in Reports API" - requested inbound shipment report
• Discussion #3430 - Original AWD API request thread

This request is specifically for the Inventory Ledger (movement history), which is distinct from the inbound shipment report discussed in #4360.

---

Community

If this gap affects your business, please 👍 this issue and comment with your use case. Specifically:

• What system are you trying to integrate? (ERP, custom, etc.)
• What's your current workaround?
• What's the business impact? (Hours spent, accuracy issues, etc.)

---

Thank you for considering this request. The AWD API has made great progress—adding ledger/movement history would complete the picture and enable proper inventory accounting for AWD users.