We’re pulling Amazon Seller Central data via the amazon_sp connector and have found two gaps in the FBA Inventory Planning report mapping. First, the aged inventory surcharge is not coming through: the connector still exposes the legacy long-term storage fee fields (estimated-ltsf-next-charge, projected-ltsf-9-mo, qty-to-be-charged-ltsf-9-mo, and the 6/12-month equivalents), and all of them return null on every row. Amazon has replaced long-term storage fees with the aged inventory surcharge and renamed the corresponding report column, which appears in Seller Central as “Estimated aged inventory surcharge.” For example, SKU SPC17X44BLK shows $356.77 and SKU EWBBTWOOD shows $24.88 in Seller Central, but both return null through the connector. Second, the inventory age buckets are incomplete: the connector provides inv-age-181-to-330-days and inv-age-331-to-365-days, which match Seller Central exactly, but there are no fields for the 366–455 and 456+ tiers, and the inv-age-365-plus-days field returns null on all rows. SKU SPC17X44BLK has 143 units in the 366–455 bucket that are invisible to us. Please map the current aged inventory surcharge column and add the 366–455 and 456+ age tier fields. Separately, the connector returns 447 rows for this account while Seller Central shows 699 SKUs — we’d like to understand whether that difference is expected filtering or a second gap.