@comchatx/cx-amazon-finance-playbook 0.0.0-stage → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (71) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +13 -2
  3. package/README.zh-CN.md +14 -0
  4. package/package.json +106 -4
  5. package/prompts/fees-review.md +5 -0
  6. package/prompts/money-where.md +5 -0
  7. package/prompts/product-earnings.md +5 -0
  8. package/prompts/refunds-review.md +5 -0
  9. package/prompts/settlement-check.md +5 -0
  10. package/research/README.md +65 -0
  11. package/research/areas/fulfilment-charges.md +881 -0
  12. package/research/areas/money-flow.md +1204 -0
  13. package/research/areas/product-profit.md +719 -0
  14. package/research/areas/reconciliation.md +722 -0
  15. package/research/areas/refunds-reimbursements-adjustments.md +813 -0
  16. package/research/areas/selling-fees.md +1019 -0
  17. package/research/areas/tax-and-invoices.md +721 -0
  18. package/research/beyond/sellers-tools-and-research.md +930 -0
  19. package/research/method/finance-surface.md +928 -0
  20. package/skills/fees-and-charges/SKILL.md +36 -0
  21. package/skills/fees-and-charges/references/fulfilment-charges.md +92 -0
  22. package/skills/fees-and-charges/references/inbound-freight.md +51 -0
  23. package/skills/fees-and-charges/references/program-fees.md +69 -0
  24. package/skills/fees-and-charges/references/selling-fees.md +87 -0
  25. package/skills/fees-and-charges/references/where-fees-land.md +51 -0
  26. package/skills/money-flow/SKILL.md +37 -0
  27. package/skills/money-flow/references/booking.md +18 -0
  28. package/skills/money-flow/references/currency.md +56 -0
  29. package/skills/money-flow/references/deferral.md +44 -0
  30. package/skills/money-flow/references/holds.md +46 -0
  31. package/skills/money-flow/references/payouts.md +73 -0
  32. package/skills/money-flow/references/reads.md +60 -0
  33. package/skills/money-flow/references/reserves.md +32 -0
  34. package/skills/money-reads/SKILL.md +39 -0
  35. package/skills/money-reads/references/finances.md +42 -0
  36. package/skills/money-reads/references/history.md +40 -0
  37. package/skills/money-reads/references/payouts.md +32 -0
  38. package/skills/money-reads/references/products.md +26 -0
  39. package/skills/money-reads/references/questions.md +54 -0
  40. package/skills/money-reads/references/reports.md +32 -0
  41. package/skills/money-reads/references/roles-and-tools.md +34 -0
  42. package/skills/product-earnings/SKILL.md +39 -0
  43. package/skills/product-earnings/references/amazon-views.md +58 -0
  44. package/skills/product-earnings/references/economics-dataset.md +52 -0
  45. package/skills/product-earnings/references/import-tax.md +42 -0
  46. package/skills/product-earnings/references/profit-choices.md +88 -0
  47. package/skills/product-earnings/references/research.md +12 -0
  48. package/skills/product-earnings/references/stock-and-landed-cost.md +60 -0
  49. package/skills/refunds-and-reimbursements/SKILL.md +41 -0
  50. package/skills/refunds-and-reimbursements/references/claims.md +41 -0
  51. package/skills/refunds-and-reimbursements/references/lines-and-reads.md +53 -0
  52. package/skills/refunds-and-reimbursements/references/refunds.md +58 -0
  53. package/skills/refunds-and-reimbursements/references/reimbursements.md +87 -0
  54. package/skills/refunds-and-reimbursements/references/tools.md +20 -0
  55. package/skills/refunds-and-reimbursements/references/value-recovery.md +72 -0
  56. package/skills/settlement-reconcile/SKILL.md +40 -0
  57. package/skills/settlement-reconcile/references/accounts-and-stores.md +36 -0
  58. package/skills/settlement-reconcile/references/books-and-tools.md +92 -0
  59. package/skills/settlement-reconcile/references/completeness.md +41 -0
  60. package/skills/settlement-reconcile/references/outside-the-settlement.md +59 -0
  61. package/skills/settlement-reconcile/references/payouts-and-transactions.md +63 -0
  62. package/skills/settlement-reconcile/references/settlement-report.md +42 -0
  63. package/skills/settlement-reconcile/references/timing-and-deferral.md +66 -0
  64. package/skills/tax-lines/SKILL.md +37 -0
  65. package/skills/tax-lines/references/china.md +61 -0
  66. package/skills/tax-lines/references/eu-uk.md +58 -0
  67. package/skills/tax-lines/references/imports.md +18 -0
  68. package/skills/tax-lines/references/lines.md +48 -0
  69. package/skills/tax-lines/references/other-marketplaces.md +37 -0
  70. package/skills/tax-lines/references/reads.md +40 -0
  71. package/skills/tax-lines/references/us.md +37 -0
@@ -0,0 +1,813 @@
1
+ # Refunds, reimbursements and adjustments as money
2
+
3
+ Read 2026-11-09 by the research seat. Tags: **[official]** Amazon's own page, post or model (title + URL + date read); **[opinion]** a named practitioner, vendor or seller (who is named); **[research]** published study or court record; **[seat]** this seat's reasoning, never a position; **[command-verified]** a command run over a clone of Amazon's models repository (https://github.com/amzn/selling-partner-api-models, commit db2936aa, 2026-10-29, message "SPAPI October Release Finance API Rollback") or over a page downloaded on 2026-11-09.
4
+
5
+ Method. Seller Central help pages (G-pages) are JavaScript shells to a plain GET on every host tried (`.com`, `.co.uk`, `-europe`, `-japan`, `.in`, `.com.au`, `.ca`, both `/gp/help/external/` and `/help/hub/reference/external/`), and the help-hub content API was not used (preamble). Amazon's rules are therefore quoted from what renders server-side: Seller Forums News posts and Amazon staff replies (`sellercentral*.amazon.*/seller-forums/discussions/t/<id>`, fetched with curl and stripped of HTML), sell.amazon.com blog posts, the developer-docs markdown pages (`https://developer-docs.amazon/sp-api/docs/<slug>.md`, each with an `updatedAt` stamp), the models, and help-page text relayed by the listing playbook (read 2026-10-14 through the content call by that seat) or by forum posts (marked "relayed"). A forum post's age is shown by the forum as "N months ago"; where the post itself carries no date, the approximate month is computed from 2026-11-09 and marked "≈".
6
+
7
+ ## What this covers
8
+
9
+ **Scope.** Money that flows back across a sale after it posts: customer refunds (FBA and seller-fulfilled), what of a refund is taken from the seller and what is given back, returnless and partial refunds, restocking fees, prepaid return labels charged to the seller, replacements; A-to-z Guarantee claims, chargebacks and SAFE-T claims as debits and credits; FBA inventory reimbursements (what Amazon pays without a claim, how value is computed, the claim windows as dated facts, reversals, cash vs inventory); and the "adjustment" lines of Finances and the settlement report. Each is tied to its identifiers (order id, adjustment item id, reimbursement id, case id, FNSKU) and to the file or operation that records it. Also (gap fill, 2026-11-10) the value a returned or unsellable unit brings back through FBA Grade and Resell, FBA Donations and Amazon Resale (§ J); liquidation as money is in `fulfilment-charges.md`. Claims as a job — finding what Amazon owes and filing — belong to a later plugin; this file records what that plugin would add (§ What only Seller Central shows, P-ref-30).
10
+
11
+ **Skills it would feed.** The pack's profit/earnings skill (a refund lowers a product's earnings by more than its principal; a reimbursement raises them, usually not to the sale value); a settlement/payout reading skill (which settlement and Finances lines are refunds, claims, reimbursements and reserves, and how they join to orders); and a shared `references/` file on refund and reimbursement money (column meanings, the identifier joins, the dated windows). The stock playbook (brief 307) owns the inventory ledger and the stock states; this file uses the ledger only where money needs it.
12
+
13
+ **Why a senior operator cares.** On a large FBA account, refunds are the second-largest line after fees, and they are not the mirror of a sale: the principal, tax and promotion are reversed, the referral fee comes back less an administration fee, and the FBA fulfilment fee is gone. Reimbursements arrive weeks or months after the loss, under a different id, on a different settlement, at a value Amazon now sets from the seller's sourcing cost, and can be reversed later. A-to-z claims and service chargebacks are funded from the seller's balance. Anyone who books "net sales minus refunds" without these rules misstates margin per SKU, and anyone who does not track the windows below loses money that can no longer be claimed.
14
+
15
+ **Dated changes since 2025-01-01** (each is sourced in § Amazon's own rules):
16
+ - 2024-10-23 / 2025-01-09 — claim windows set to 60 / 45–105 / 15–75 / 60 days: News post 6605eede (posted 2024-07-24) gives 2024-10-23; News post d0fc997e (posted 2024-10-10, British spelling, "Changes to programme policies") gives 2025-01-09; the EU post 1101821c (posted 2025-01-15) says the policy "has been updated" with the same windows (F). Forum thread ids are shared across hosts, so no page names the store each post addresses.
17
+ - 2024-11-01 / 2025-01-15 — proactive reimbursement of FC-lost items: 2024-11-01 in 6605eede, 2025-01-15 in d0fc997e, same text otherwise (E).
18
+ - 2025-03-31 — reimbursement at manufacturing ("sourcing") cost for losses before a customer order; first announced for 2025-03-10, then moved (E).
19
+ - 2025-08-01 — India: SAFE-T no longer pays for primary packaging damage or broken/open seals on Easy Ship, Self-Ship and Seller Flex orders (D).
20
+ - ≈2025-10 — FBA partial refunds without return (US, UK, DE, FR, IT, ES) (A).
21
+ - 2025-10-15 — new claim windows: 60 / 45–105 / 15–135 / 120 / 120 / re-evaluation 90 (News post d8f9a56c, posted 2025-08-14) (F).
22
+ - ≈2025-11 — FBA Returnless Resolutions enrolment by price (US, $1–$75) (A).
23
+ - 2026-01-01 — US: shipments created from this date that arrive without proper prep and labelling are not eligible for reimbursement if damaged or untraceable (E).
24
+ - 2026-01-26 — seller-fulfilled refund window from two business days to four calendar days before Automated Refund; an auto-refund forfeits SAFE-T except lost-in-transit / wrong delivery confirmation (A, D).
25
+ - 2026-01-28 — Finances v0 gains `EBTRefundReimbursementOnlyEventList`; Data Kiosk Sales and Traffic gains B2B refund and claim metrics (§ API).
26
+ - 2026-02-08 — US seller-fulfilled: Amazon Prepaid Return Labels required regardless of item value (high-value exemption ended) (A).
27
+ - 2026-02-16 — US SAFE-T filing window from 60 to 30 days (D).
28
+ - 2026-03-31 — commingling ends; stock not correctly labelled may be untraceable and not eligible for reimbursement (gs.amazon.cn; § What practitioners add, Chinese sources).
29
+ - 2026-07-29 — Finances v2024-06-19 `listSummary` and `listBalances` (release note). The same note announced a `SETTLEMENT_ID` filter on `listTransactions`; the model added it on 2026-10-28 (commit df7c6298) and the "Finance API Rollback" commit db2936aa (2026-10-29) removed it, and the live reference lists only `FINANCIAL_EVENT_GROUP_ID` and `ORDER_ID`. `SETTLEMENT_ID` filters `listSummary` (§ API).
30
+ - ≈2026-07 — Returnless resolutions restated by Amazon as "available to all sellers on a Professional selling plan who use" FBA, with rules by price, category or return reason (A).
31
+ - 2026-08-13 — an Amazon staff post (Indy_Amazon, 0e07abc1) states claim windows that differ from the 2025-10-15 News post (F, conflict).
32
+
33
+ Value-recovery dates (gap fill, 2026-11-10; each sourced in § J):
34
+ - 2024-08-07 — US News post: FBA Grade and Resell is "an optional fee-based service" (J1).
35
+ - 2025-02-24 — EU News post: Grade and Resell in the UK, France, Germany, Italy, Spain, Czech Republic and Poland "without any programme fees (we'll provide 60 days notice before introducing any fees)" (J1).
36
+ - 2025-09-11 — sell.amazon.com: Grade and Resell offered to FBA sellers (US blog) (J1).
37
+ - 2025-09-30 — US: FBA Liquidations becomes the default for unsold inventory where no automated settings are configured. The 2025-08-22 News post named the US and Canada; Amazon's correction (relayed) says US only, Canada unchanged (J2).
38
+ - 2025-10-30 — US: FBA Donations becomes mandatory when Dispose is selected; opted-out sellers are re-enrolled (correction, relayed; first announced for 2025-09-30) (J2).
39
+ - 2026-02-03 — Grade and Resell: watches, jewelry, luggage, shoes and apparel added; used prices follow the new price automatically; ASIN inclusion (opt-in) (J1).
40
+ - 2026-03-09 — US: yearly donation certificates for FBA Donations on the Donations page (J2).
41
+
42
+ ## Amazon's own rules
43
+
44
+ ### A. Customer refunds: what moves, who triggers it, when
45
+
46
+ **A1. What a refund reverses, in the model's words.** A refund is carried in Finances v0 as a `ShipmentEvent`-shaped item under `RefundEventList` ("A shipment, refund, guarantee claim, or chargeback"). The refund-only fields are `ItemChargeAdjustmentList` ("A list of charge adjustments associated with the shipment item. This value is only returned for refunds, guarantee claims, and chargeback events."), `ItemFeeAdjustmentList`, `PromotionAdjustmentList`, `CostOfPointsReturned`, and `OrderAdjustmentItemId` ("An Amazon-defined order adjustment identifier defined for refunds, guarantee claims, and chargeback events"). The charge types a refund can carry are the `ChargeComponent` values, including `Principal`, `Tax`, `MarketplaceFacilitatorTax-Principal/-Shipping/-Giftwrap/-Other` ("The tax that is withheld on…"), `Discount`, `ShippingCharge`, `ShippingTax`, `Giftwrap`, `GiftwrapTax`, `Goodwill` ("The amount of money that is given to a buyer as a gesture of goodwill or to compensate for pain and suffering in the buying experience"), `RestockingFee` ("The charge that is applied to the buyer when returning a product in certain categories"), `ReturnShipping` ("The amount of money that is given to the buyer to compensate for shipping the item back if we are at fault"), `PointsFee`, `GenericDeduction` ("A generic bad debt deduction"), `FreeReplacementReturnShipping` ("The compensation for return shipping when a buyer receives the wrong item, requests a free replacement, and returns the incorrect item"), `PaymentMethodFee`, `ExportCharge`, `SAFE-TReimbursement`, the India `TCS-*` family and `PaidthroughEBT`. `FeeType` has no closed list; it points to the fee schedule and "FBA features, services and fees". [official] [command-verified] (`models/finances-api-model/financesV0.json`, definitions `ShipmentEvent`, `ShipmentItem`, `ChargeComponent`, `FeeComponent`; read 2026-11-09.)
47
+
48
+ **A2. The referral fee comes back less a refund administration fee.** US: on a refund Amazon returns the referral fee "minus the applicable refund administration fee, which is the lesser of $5.00 or 20% of the applicable referral fee". [official] (Selling on Amazon fee schedule, https://sellercentral.amazon.com/help/hub/reference/external/G200336920, version 119, read 2026-10-14 by the listing seat, `research/angles/price-position.md` §H.) UK wording, relayed by a seller from the help page: "When you create a full refund for a non-BMVD product, Amazon retains 20% of the original order-related fees, up to a maximum of £5, for each line item in the refund. This amount is held back as a refund administrative fee." "When you create a partial refund for a non-BMVD product, Amazon retains 20% of the original order-related fees, up to a maximum of £5, for each line item in the refund and credits you with a proportional amount of the Referral Fee originally charged for the order based on the percentage of the item price refunded to the buyer." "If you refund two different items in an order, Amazon retains up to £5 for each item, for a maximum of £10". BMVD is "Books, Music, Video and DVD" (separate rules). [official, relayed] (Seller Forums EU, "Refund Cost", reply by Seller_zKEt2RiaID5EU quoting the help page, https://sellercentral-europe.amazon.com/seller-forums/discussions/t/3e43da0c-1b96-473b-9898-fe57db2e48bb, read 2026-11-09.) UAE: a seller quotes the same rule "up to a maximum of AED 15, for each line item in the refund" (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/22c4dcb2-808c-4dd5-ae10-f914306c57b9, read 2026-11-09) [official, relayed]. The cap's currency and amount differ per store; the base differs in wording (US "applicable referral fee", UK "original order-related fees").
49
+
50
+ **A3. The FBA fulfilment fee is not refunded on a customer refund.** No Amazon page read states this in so many words. Sellers state it in forum threads: in 22c4dcb2 (2024-11-04) a UAE seller writes that on a re-sold return "amazon again will charge the same fulfillment fee"; in f29481bb (UK, 2024-03-08) a seller asks whether the gap on a refund "is … the FBA fee waivered plus an % admin fee". [opinion] (The earlier quote "any fees related to fulfillment of the order by Amazon will not be refunded, however you will be credited the final value fees" is a paraphrase: exact wording not found on d8f86449, 22c4dcb2 or f29481bb, 2026-11-10; b2b31952 is cited only by a partial id and was not re-read.) The model does not settle it either way: `FeeType` has no closed list (A1), so the model neither lists nor excludes a fulfilment-fee line in `ItemFeeAdjustmentList` [command-verified]. A refund without a return also leaves the unit with the buyer. A3 is a practitioner fact with an official gap; see Open questions.
51
+
52
+ **A4. Who can trigger a refund on a seller-fulfilled order.** Amazon lists the cases in which it "automatically issues refunds for returns": "Refund at first scan: … eligible requests that are authorized automatically through our Prepaid Return Label program are refunded automatically once the buyer drops off the return at a designated carrier location." "Returnless refunds: We'll issue returnless refunds to buyers if you have a returnless refund rule enabled in your return settings or if the order value is less than $25 for a non-US return." "A-to-z Guarantee claims: If a buyer submitted an A-to-z Guarantee claim and the investigator determined that you were at fault, we may issue a refund to the buyer and deduct the amount from your Seller Central account." "Chargebacks…" and "Customer Service refunds: If a buyer reaches out to Amazon customer service about a return-related issue, customer service may issue a refund on your behalf to protect the customer's experience." Return shipping: "Customers pay when they change their mind, like accidental orders, with fees deducted from their refund. For issues like defective items or shipping errors, sellers cover the costs." "For seller-issued refunds, you can apply a restocking fee for damaged or materially different items, or returns not covered by the Amazon Return Policy." ("For FBA orders, Amazon handles returns": paraphrase; exact wording not found on the page, 2026-11-10.) [official] (sell.amazon.com blog, "How to manage Amazon customer returns for seller-fulfilled orders", Mickey Toogood, 2025-04-15, https://sell.amazon.com/blog/manage-customer-returns, read 2026-11-09.)
53
+
54
+ **A5. Seller-fulfilled refund deadline (dated change 2026-01-26).** "Effective January 26, 2026, the Fulfilled by Merchant (FBM) refund process will be updated … The processing window for refunds will extend from two business days to four calendar days before Automated Refund triggers." "If you don't process a refund within four calendar days of receiving a returned item, we may issue an automatic refund. In these cases, you won't be eligible for Seller Assurance for e-Commerce Transactions (SAFE-T) claim reimbursement except for specific situations such as when returned items are lost in transit or delivery confirmation was incorrect through no fault of your own." Amazon names the Guided Refund workflow (GRW), "which allows you to grade returned items, apply appropriate restocking fees, and upload evidence". [official] (Seller Forums News, "Update to seller-fulfilled refund process by January 26, 2026", News_Amazon, posted 2025-12-23 (page `datePublished`), https://sellercentral.amazon.com/seller-forums/discussions/t/11268c92-5a5c-4125-9e59-49e433d0d151, read 2026-11-09.)
55
+
56
+ **A6. Prepaid return labels (US seller-fulfilled; dated change 2026-02-08).** "Effective February 8, 2026, all US sellers must use the Amazon Prepaid Return Label (APRL) program for customer returns of seller-fulfilled orders regardless of item value. This change eliminates the previous high-value exemption". "The APRL program automatically provides customers with prepaid return shipping labels through Buy Shipping Services. This streamlined process reduces the refund cycle time from 14 to 7 days". Category exemptions remain: "Handmade, certified preowned watches, non-physical items, dangerous goods, and extra-large or heavy items". The first article (2026-01-09) was removed and republished 2026-02-09 "to clarify that this requirement is for US seller-fulfilled orders". [official] (News_Amazon, "Prepaid return labels required for high-value items", https://sellercentral.amazon.com/seller-forums/discussions/t/9fa92037-c19b-4f03-82b5-7221bd0efa71 and …/c1eae42b-ead4-4c63-a007-aefbca44a867, read 2026-11-09.) Earlier: international sellers without a US return address must "issue a returnless refund or provide a prepaid international return shipping label within two days of a return request", or "we may refund the customer on your behalf and charge the amount to your seller account" (effective 2024-09-16). [official] (News_Amazon, "Update to international returns", https://sellercentral.amazon.com/seller-forums/discussions/t/682481b7-54ca-40e3-b578-7a98988817e3, read 2026-11-09.) The label's cost and who pays it are in the seller-fulfilled returns report (`label_cost`, `label_to_be_paid_by`) and, as money, in Finances `AdjustmentEvent` type `PostageBilling` ("The amount paid by a seller for shipping labels") / `PostageRefund` (§ I).
57
+
58
+ **A7. FBA returnless and partial refunds (dated).** Launch, ≈2024-08: "We've launched FBA Returnless Resolutions, a new program that helps you streamline returns by offering customers a full refund without having to return the item." Ineligible: "dangerous goods, heavy and bulky items, and those with an average sales price greater than $75". [official] (News_Amazon, "Streamline returns with Returnless Resolutions", https://sellercentral.amazon.com/seller-forums/discussions/t/ab90097c-c14c-4e2a-a241-68eac52ae500, read 2026-11-09.) By price, ≈2025-11 (US): "Set a price between $1.00 and $75.00 … you grant customers a refund and allow them to keep the item, saving you the fees associated with high return rates, customer returns processing, storage, and removals." "We monitor refund requests for signs of fraud and only offer returnless resolutions to eligible customers who don't have a history of returns abuse." [official] (…/d31d6e3f-24ed-4870-b57b-a4d7a0d74eb8.) ≈2026-07: "It is available to all sellers on a Professional selling plan who use Fulfillment by Amazon (FBA). You set the rules … by price range, product category, or return reason". [official] (News_Amazon, "Reduce return costs with returnless resolutions", …/8f6ea88b-8672-426e-accb-7c9d7f6d911a.) Partial refunds, ≈2025-10: "You can now offer partial refunds to customers without requiring physical returns for your Fulfillment by Amazon (FBA) products in the US, the UK, Germany, France, Italy, and Spain"; "Set your preferred partial refund percentage"; tracked "in your FBA Returns dashboard, marked as Complete – Return not expected in the Return status column." [official] (News_Amazon, "Manage FBA returns with partial refunds", …/5935f007-115c-47f2-8ea9-49d8d8c441c4, all read 2026-11-09.) A returnless refund is not reimbursed: it is a refund the seller chose to fund. "There are currently no downloadable reports for FBA Returnless Resolutions"; returnless returns "count toward the ASIN's average return rate"; "The high return rate fee is not charged for returns that are successfully given to customers through FBA Returnless Resolutions." [official] (FBA Returnless Resolutions, G3RZC8DVQCDTCQ3B v8, read 2026-10-14 by the listing seat, `research/angles/returns.md`.)
59
+
60
+ **A8. Return windows set how long refunds keep arriving.** "In most cases, buyers can request to return an item within 30 days of receiving it. We may make case-by-case exceptions and accept return requests beyond 30 days of receipt"; eligible FBA baby items "within 90 days"; holiday purchases (2025: 1 Nov–31 Dec) returnable to 2026-01-31. [official] (FBA customer returns policy G200379860 v24; Extended Holiday Returns policy G201725760 v15; read 2026-10-14 by the listing seat.) So a refund can post outside any fixed window after the sale, and the refund's posting date is the only date Finances carries for it [seat].
61
+
62
+ **A9. Replacements.** The FBA Replacements report "Contains replacements that have been issued to customers for completed orders", NA and IN stores, Amazon Fulfillment role only, with `replacement-reason-code`, `replacement-amazon-order-id` and `original-amazon-order-id`. [official] (Fulfillment by Amazon (FBA) Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-fba.md, updatedAt 2026-10-13, read 2026-11-09.) The FBA customer returns reimbursement window counts from "customer refund or replacement" (F). An Amazon moderator: when the original of a replacement is not returned in time, "you are entitled to a reimbursement" under "FBA inventory reimbursement policy: Customer Return policy". [official, staff] (Joey_Amazon, https://sellercentral-europe.amazon.com/seller-forums/discussions/t/8d381f28-a83e-4ca8-bce5-2f9778efaf49, read 2026-11-09.)
63
+
64
+ **A10. Amazon Business.** Amazon's customer return policy "also applies to purchases made through your Amazon Business account" [official, customer help page via search snippet only, https://www.amazon.com/gp/help/customer/display.html?nodeId=GKM69DUUYKQWKWX7]. Data Kiosk Sales and Traffic separates `unitsRefundedB2B`, `refundRateB2B`, `claimsAmountB2B` and `claimsGrantedB2B` ("only populated when the seller is a B2B seller"), added 2026-01-28. Deferred B2B (invoiced) money carries `DeferredContext.deferralReason` "`B2B` (invoiced orders)". [official] [command-verified] (`analytics_salesAndTraffic_2024_04_24.graphql`; `finances_2024-06-19.json`; SP-API release notes 2026-01-28.)
65
+
66
+ ### B. A-to-z Guarantee claims
67
+
68
+ - "For assigned claims, we will reimburse the buyer and debit your Seller Account or cancel any future payment, as applicable." "If you do not respond to our request for additional information within 72 hours, we will grant the Claim in favor of the customer, and your account will be debited for the Claim amount." "Once a Claim is granted to the customer and your account has been debited, you have 30 calendar days to submit an appeal". [official, via search snippets of Amazon's A-to-z Guarantee claims G27951 and Appeal an A-to-z Guarantee claim G202041210, https://sellercentral.amazon.com/gp/help/external/G27951, https://sellercentral.amazon.com/help/hub/reference/external/G202041210; pages are JS shells; snippets read 2026-11-09.]
69
+ - Debit and defect are separate: Amazon can debit the claim "but have not counted the claim against your Order Defect Rate" (Amazon notification text quoted by a seller) [opinion, relayed].
70
+ - Buy Shipping "Claims Protected" labels shield "Package didn't arrive" claims when conditions are met (quoted by sellers from the help page) [opinion, relayed]. Who funds a protected claim is Amazon's; the seller is not debited [seat, from "protection"; open].
71
+ - In Finances v0: `GuaranteeClaimEventList`, same item shape as a refund (A1). In the Payments Transaction view, "A-to-z Guarantee Refund" is a filter (survey `04-job-money.md` §1). Data Kiosk: `claimsAmount` ("Monetary amount of filed A-to-z guarantee claims"), `claimsGranted`, and in seller analytics `accountHealthAtozClaimOrderCount` ("A-to-z Guarantee claim that was not denied, applies to seller-fulfilled orders only"). [official] [command-verified]
72
+ - "Orders with an A-to-z Guarantee claim are not eligible for SAFE-T claims." [official, via search snippet of Reimbursement for seller-fulfilled orders G202188810.]
73
+
74
+ ### C. Chargebacks
75
+
76
+ "Fraud-related: We're responsible for handling payment-related fraud chargebacks, like stolen credit cards or other payment fraud attempts." "Service-related: Amazon sellers are responsible if the chargeback is due to a service-related reason, like non-receipt of the product." Flow: "Amazon notifies the seller involved in a service-related chargeback and requests information related to the order. The seller reviews the Amazon chargeback alert and has the opportunity to issue a refund or represent their case by providing evidence that the transaction was valid. The customer's bank makes the final decision". "the final outcome potentially taking 90 days or longer"; "respond within seven calendar days of the email date". Generic mechanics: "If the bank decides in favor of the seller, the credit is reversed and the funds are returned to the seller." Account Health shows "Chargeback claim" rates for seller-fulfilled and FBA orders separately, "divided by the number of orders in a 60-day period". [official] (sell.amazon.com blog, "How to manage Amazon chargebacks", Mickey Toogood, 2025-12-01, https://sell.amazon.com/blog/chargebacks, read 2026-11-09.) In Finances v0: `ChargebackEventList` (refund item shape, A1); a won representment returns money as a later event [seat; the model names no reversal type for chargebacks]. Data Kiosk seller analytics `accountHealthChargebackClaimOrderCount` ("applies to both seller-fulfilled and amazon-fulfilled orders"). [official] [command-verified]
77
+
78
+ ### D. SAFE-T claims (seller-fulfilled)
79
+
80
+ - Window (US, dated change 2026-02-16): "Effective February 16, 2026, the SAFE-T claim filing window for US seller-fulfilled orders will change from 60 days to 30 days. This update aligns with our standard US return period and A-to-z claim appeal window." "the 30-day window starts from either the return delivery scan at your warehouse or the refund date, whichever comes later. For lost shipments, the window begins from the last scan event." "This change doesn't affect any claims that are currently in progress." [official] (News_Amazon, "US SAFE-T claim filing window changes to 30 days on Feb 16", ≈2026-01, https://sellercentral.amazon.com/seller-forums/discussions/t/d95b0e44-60fc-4c16-b690-3626c9a3c43c, read 2026-11-09.)
81
+ - Auto-refund forfeits SAFE-T (2026-01-26, A5). Prepaid-label high-value returns are pointed to SAFE-T (A6).
82
+ - India (dated change 2025-08-01): "the SAFE-T reimbursement policy for Easy Ship, Self-Ship and Seller Flex orders will be updated … we will no longer process SAFE-T reimbursement claims for the following return reasons: Product primary packaging or box damage; Broken or open seals". [official] (News_Amazon, sellercentral.amazon.in, https://sellercentral.amazon.in/seller-forums/discussions/t/3fc74ac2-d8d7-4eb6-af8a-2a78feb965f6, read 2026-11-09.)
83
+ - As money: Finances v0 `SAFETReimbursementEvent` ("A SAFE-T claim reimbursement on the seller's account": `SAFETClaimId`, `ReimbursedAmount`, `ReasonCode` "Indicates why the seller was reimbursed", items with `itemChargeList`); charge type `SAFE-TReimbursement`. The seller-fulfilled returns flat file carries `SafeT Action reason`, `SafeT claim id`, `SafeT claim state`, `SafeT claim creation time`, `SafeT claim reimbursement amount`, `Refunded Amount`. [official] [command-verified] (financesV0.json; Returns Reports, https://developer-docs.amazon/sp-api/docs/report-type-values-returns.md, updatedAt 2026-10-28.)
84
+
85
+ ### E. FBA inventory reimbursements: scope, automation, valuation
86
+
87
+ **E1. What the policy covers (Amazon staff summary, posted 2026-08-13).** "Warehouse lost", "Warehouse damaged", "Shipment to Amazon (Missing from Inbound)", "Removals lost or damaged", "Customer return not received — … If the customer was refunded but the item was never returned, in most cases we'll charge the customer and reimburse you. If a customer returns your item to a fulfillment center within 60 days of the refund, we'll first determine the condition of the returned item. If the returned item is sellable, we'll return the item to your inventory. If the returned item is unsellable, we'll determine who is responsible for the condition. If Amazon is responsible for an unsellable return, we'll reimburse you and will not add the item back to your inventory. Amazon will not reimburse you for returned items that are damaged by a customer". Ineligible accounts: "Accounts in blocked, terminated, or fraud status aren't eligible". [official, staff] (Indy_Amazon, "FBA Lost Your Inventory? Steps to File a Reimbursement Claim", https://sellercentral.amazon.com/seller-forums/discussions/t/0e07abc1-9026-4540-a005-153d9e78bf04, read 2026-11-09.) The FBA customer returns policy adds: "our reimbursement decisions are based on the actual physical condition of the item when evaluated at our fulfillment center, not the buyer's selected reason." [official] (G200379860 v24, listing seat 2026-10-14.) A seller (pricing in £, posted 2025-04-14 on the .com forum) quotes the customer-return reimbursement policy: "If customer does not return your item to an Amazon fulfillment centre within 45 days of the refund (return less refund), we will issue a reimbursement and credit your account for the item." [official, relayed] (https://sellercentral.amazon.com/seller-forums/discussions/t/b12b6190-c9f8-45dd-ab39-dcd13dfbdb44, read 2026-11-10.) The staff post (60 days) and the relayed policy (45 days) differ; see F. Amazon's own policy text (redlined US policy PDF, created 2024-12-18, E4) lists the eligibility conditions: the item "is registered in FBA at the time it is lost or damaged", complies with FBA restrictions and requirements, the seller sent "the exact items and quantities stated in your shipping plan", the shipment "is not in canceled or deleted status", the item is not pending or subject to disposal, "is not defective and was not damaged by a customer", and "the seller's account must be in normal status" while a claim is filed, reviewed or appealed. [official]
88
+
89
+ **E2. Automatic ("proactive") reimbursement.** Two Amazon News posts, both reachable on every forum host (thread ids are shared across `.com`, `-europe`, `.co.uk`, `.de`), give different dates for the same text. 6605eede was posted 2024-07-24 (2024-11-01 start; windows from 2024-10-23); d0fc997e was posted 2024-10-10 (2025-01-15 start; windows from 2025-01-09) and is written in British spelling ("minimising", "Changes to programme policies"); the EU post 1101821c (posted 2025-01-15) says the policy "has been updated". A per-store rollout (US first, Europe later) fits all three posts, but no page names the store; Chinese media report both dates (2024-11-01: AMZ123 1RKMP8FS; 2025-01-15: 亿恩网 30129) without naming one either. [official dates; per-store reading is seat] The quoted texts: "Starting November 1, 2024, we'll proactively reimburse you for Fulfilment by Amazon (FBA) items that are lost in our fulfilment centres. We'll issue the reimbursement as soon as an item is reported as lost by the fulfilment centre, which you can track in the Reimbursements report" (…/6605eede-df8e-4498-803f-cb612d95d7ce) and "Starting January 15, 2025, we'll proactively reimburse you…" (…/d0fc997e-de50-4100-9803-76b7993b66df). Both: "Almost all reimbursement claims related to warehouse lost and damaged and customer returns cases will now be proactively reimbursed. However, if you do not receive an automatic reimbursement and you believe that your inventory has been lost or damaged, you will need to file a manual claim. Additionally, all removal claims will still need to be filed manually." [official] (News_Amazon, "Update on Reimbursement Automation and Eligibility Window to file reimbursement claims", read 2026-11-09.) Low-inventory-level fees caused by Amazon inbound delays: "we'll automatically reimburse you" [official] (Low-inventory-level fee GV43F6S76Y9DHYRH v29, listing seat).
90
+
91
+ **E3. The IDR portal and what it leaves out.** "you can more efficiently manage all your inventory-related defects and reimbursements within warehouse lost, warehouse damage, and customer returns, in one convenient place through the IDR portal." "Note that the portal doesn't include defects under missing from inbound, removals or warehouse disposals." Path: FBA dashboard → Inventory → Inventory Defect and Reimbursement, or through the Reimbursements report. [official] (News_Amazon, "Inventory Defect and Reimbursement portal now available", https://sellercentral-europe.amazon.com/seller-forums/discussions/t/b175b700-09c4-4350-8a22-24f60a724042, read 2026-11-09.)
92
+
93
+ **E4. Valuation: sourcing ("manufacturing") cost, effective 2025-03-31.** "Effective March 10, 2025, we'll reimburse you based on the product manufacturing cost of the affected inventory. 'Manufacturing cost' means your cost to source a product from a manufacturer, wholesaler, reseller, or produce the item if you are the manufacturer. It excludes costs such as shipping, handling, customs duties, or other costs." Choice: "We'll provide a manufacturing cost estimate for you. This estimate is based on a comprehensive evaluation of comparable products sold by Amazon, by other sellers, and through wholesale channels. You can provide your manufacturing costs directly. If you don't provide your own costs, we'll automatically apply our estimate which you can change when you're ready." "For items that are lost or damaged after a customer order in Amazon's store, we'll continue to reimburse you for the sales price on the original order minus applicable fees." The definition was "updated on December 19, 2024". [official] (News_Amazon, "Update to the FBA inventory reimbursement policy", https://sellercentral.amazon.com/seller-forums/discussions/t/68864b6f-0ab8-41ef-be18-069c33df6336; EU copy …/a941ac02-d389-409a-9d62-00ab9db5bc4a; read 2026-11-09.) **Then moved:** "The updated Fulfillment by Amazon (FBA) inventory reimbursement policy will now go into effect on March 31, 2025, instead of March 10, 2025. We made this change to give you more time to manage your costs through the Manage Your Sourcing Cost page in the Inventory Defect and Reimbursement portal." "All sellers will have access to this page by February 28, 2025". [official] (News_Amazon, "New effective date for FBA inventory reimbursement policy", https://sellercentral.amazon.com/seller-forums/discussions/t/ed8abc33-a1d5-417d-b2e2-03b789099833, read 2026-11-09.) The staff restatement (≈2026-08): "For shipment to Amazon claims, removals claims, and fulfillment center operations claims that occur before fulfillment, we will reimburse you the sourcing cost of the item. … For items that were in unsellable condition when lost, damaged or removed from the Amazon fulfillment network, we will reimburse at a reduced estimated cost of the unit, and we may request additional information or documentation to help us determine this adjusted value." [official, staff] (Indy_Amazon, E1.) The page name changed from "Manage Your Manufacturing Cost" (Dec 2024 post) to "Manage Your Sourcing Cost" (Feb 2025 post, 2026 staff post).
94
+
95
+ **E4a. The policy text itself (redlined US policy, Amazon's PDF).** Amazon's "FBA inventory reimbursement policy" as revised for the manufacturing-cost change, a public PDF on Amazon's asset host (https://m.media-amazon.com/images/G/01/rainier/help./PC__Kiwi_Comms_redlined_policy_US_clean.pdf; Chinese copy `…US_clean-zh_cn.pdf`; PDF created 2024-12-18; read 2026-11-10 by plain GET), still says "March 10, 2025" (it predates the move to 2025-03-31) and adds: "The maximum reimbursement amount for a single unit of any FBA eligible item is $5,000"; "we replace that item with a new item of the same FNSKU or reimburse you for it"; "If a reimbursement was made in error, or if a reimbursed item is later found and returned to your inventory, we reserve the right to reverse the reimbursement credit"; reimbursed units, "including lost items that are found after reimbursement, may be listed for sale on Amazon warehouse or other channels"; a submitted cost may be declined if it is "an outlier", forged, on an account suspected of fraud, or repeats a decision "within the last 30 days" with no new information; for post-order events the estimated sale price compares "The median price at which you have sold the item on Amazon over the past 18 months", other sellers' median, and current list prices; "Estimated proceeds means the estimated sale price … minus referral fees and fulfillment fees"; for a customer-return claim "we calculate the reimbursement value as the refund amount or the sales price of the replacement item on the original order minus applicable fees"; "If you don't agree with our valuation of a unit, you can file a claim on Contact Us in Seller Central within 60 days after we have issued the reimbursement." The PDF gives no claim windows (it links to the per-claim pages). [official]
96
+
97
+ **E5. What is not reimbursed.** Customer-damaged returns (E1); "Shipments created after January 1, that arrive without proper prep and item labeling won't be eligible for reimbursement if damaged or untraceable" (US; prep and labelling services end for shipments created from 2026-01-01, including inventory from AWD, AGL, Amazon SEND and Supply Chain Portal that goes through FBA) [official, staff] (Jameson_Amazon, https://sellercentral.amazon.com/seller-forums/discussions/t/5c63f045-b956-447b-9e6d-410b1e2a05bb); returns when the seller disables returns evaluation: "All returns will be marked as defective and won't be eligible for reimbursements if damaged" [official, staff] (Ezra_Amazon, "Fulfilment by Amazon Returns", https://sellercentral-europe.amazon.com/seller-forums/discussions/t/aaf11b9d-dcc7-4df1-be41-e6e364a2cdcf); items "subject to recall, are defective or in violation of Amazon policies" and items "disposed of at your request" (survey `04-job-money.md` §4.4, from the Supply Chain Portal policy and an Amazon reply); accounts "in blocked, terminated, or fraud status" (E1). All read 2026-11-09.
98
+
99
+ **E6. Cash or inventory.** The reimbursements report splits `quantity-reimbursed-cash`, `quantity-reimbursed-inventory` and `quantity-reimbursed-total`; staff and the report's column names are the only description ("reimbursed by cash and inventory", the Reimburse Details mapping of GorillaROI says the same) [official column names; opinion for the reading]. An inventory reimbursement puts a unit back and moves no money [seat].
100
+
101
+ **E7. Reversals.** Help-page text relayed by a seller: "Amazon can reverse reimbursements in two cases (See 'Reimbursement Type' > 'Reimbursement_Reversal'): If the reimbursement was issued incorrectly; If the lost inventory is later found and returned to your stock", tracked in the Reimbursements report. [official, relayed] (Seller_i6S8knzW6zU6Z quoting https://sellercentral.amazon.com/help/hub/reference/GMGJASYYNYLXKLXE, in https://sellercentral.amazon.in/seller-forums/discussions/t/27d8ba3f-3216-424c-a7ab-ecb55c9c2719, read 2026-11-09.) The report's `original-reimbursement-id` and `original-reimbursement-type` columns link a reversal to what it reverses [official column names]. Sellers report reversals of reimbursements more than a year old with no matching ledger receipt, after their own claim window has closed ("amazon has no claim window for when they can randomly reverse reimbursements but I have one") [opinion] (https://sellercentral.amazon.com/seller-forums/discussions/t/58e0b08d-db92-40dd-a2a8-c2c9d6c2e475, ≈2025-12).
102
+
103
+ **E8. Fee reimbursements.** Dimension/weight overcharge: "our measurement will govern"; request "within 90 days of the date on which the fee was charged" [official] (FBA fees reimbursement policy: Weight and dimensions GL7U4JFSDXUTQAJ v14, listing seat 2026-10-14). Fee corrections credit through `ChargeRefundEvent` ("`ReasonCode` … For example, `SubscriptionFeeCorrection`") or adjustments [official model; mapping is seat].
104
+
105
+ ### F. Claim windows as dated facts
106
+
107
+ | Claim | 6605eede (posted 2024-07-24, eff. 2024-10-23) / d0fc997e (posted 2024-10-10, eff. 2025-01-09) / EU 1101821c (posted 2025-01-15) | d8f9a56c (posted 2025-08-14, eff. 2025-10-15) | Indy_Amazon 0e07abc1 (staff, posted 2026-08-13) |
108
+ |---|---|---|---|
109
+ | Lost or damaged in FC | "no later than 60 days after the item was reported lost or damaged" | "Within 60 days of reported loss or damage" | "within 60 days of the date the loss or damage event appears in your reports" |
110
+ | FBA customer returns (refunded, not returned / returned wrong or damaged) | "between 45-105 days after the customer refund or replacement date. Claims must not be submitted before 45 days" | "Between 45-105 days after customer refund or replacement" | "no sooner than 60 days after the customer refund … and within 18 months" |
111
+ | Removal lost in transit | "15-75 days from the shipment-creation date" | "Between 15-135 days from shipment creation" | "within 18 months of the shipment being delivered or lost" |
112
+ | Other removal claims / removal damaged | "within 60 days of the shipment being delivered back to you" | "Removal orders damaged: 120 days from shipment delivery date" | (as above) |
113
+ | Removal grading | — | "120 days from date item was removed from our fulfilment network" | — |
114
+ | Re-evaluation of a claim | — | "Within 90 days of initial claim" | — |
115
+ | Shipment to Amazon (missing from inbound) | not in these posts | not in this post | "after your shipment is closed/finalized … and within 9 months" |
116
+
117
+ Sources [official], every quote re-read from the raw page on 2026-11-10, posting dates from each page's `datePublished`: News_Amazon "Update on Reimbursement Automation and Eligibility Window…" (…/6605eede…, "Also starting October 23", and …/d0fc997e…, "Starting January 9, 2025"); News_Amazon EU "Update on eligibility window to file reimbursement claims" (https://sellercentral-europe.amazon.com/seller-forums/discussions/t/1101821c-7ff1-495a-b8a5-71ff01e3afc3, same windows, posted 2025-01-15); News_Amazon "Update to FBA inventory reimbursement claim windows", "Effective October 15, 2025" (https://sellercentral.amazon.com/seller-forums/discussions/t/d8f9a56c-882f-437c-ad34-cccd11cfa465); Indy_Amazon staff post (E1). All read 2026-11-09. Prior windows were 18 months [opinion, consistent across vendors; survey §4.3].
118
+
119
+ Other windows: FBA fee/dimension 90 days (E8); SAFE-T 30 days US from 2026-02-16 (D); A-to-z appeal 30 calendar days (B); chargeback reply 7 calendar days (C). Inbound reconciliation: shipments "created after February 1, 2024 are automatically closed after 45 days (domestic shipment) and 75 days (international shipment)"; reconciliation "usually takes 2 to 30 days, and up to 60 days in some cases" [official, via search snippet of Reconcile your shipment, https://sellercentral.amazon.com/gp/help/external/201214140; JS shell]. The Supply Chain Portal/AWD policy (a different program) says "no later than nine months after the verified date of a shipment delivery" (survey §4.3).
120
+
121
+ **The conflict.** The 2026-08-13 staff post restates windows (customer returns 60 days to 18 months; removals 18 months) that match neither the 2025-10-15 News post nor the earlier ones, and its 60-day customer-return wait differs from the relayed policy's 45 days (E1). Amazon's policy page itself (G200213130) is a JavaScript shell and was not read. The News post is the dated, announced rule; the staff post may restate an older page. Amazon's own Chinese pages (gs.amazon.cn, now redirecting to globalselling.amazon.com; articles dated 2025-03 and 2025-08) state the US missing-from-inbound window as "9个月内" / "最迟九个月内(美国站)" after delivery to the FC, agreeing with the staff post; no News post read gives a missing-from-inbound window. The Chinese FBA FAQ's "45天" is about the original unit of a free *replacement* order ("关于原订单中的退件商品,买家需要在45天内退回到仓库"), not a refunded unit; the earlier reading of it as agreeing with the relayed 45-day refund text was wrong. No gs.amazon.cn page found states the 2024/2025 or 2025-10-15 windows. Page by page: 6605eede and d0fc997e and 1101821c say 60 / 45–105 / 15–75 / 60; d8f9a56c says 60 / 45–105 / 15–135 / 120 / 120 / 90; the staff post says 60 / MFI 9 months / returns 60 days to 18 months / removals 18 months; gs.amazon.cn says MFI 9 months (US); the relayed policy text (b12b6190, 2025-04-14) says a unit not returned within 45 days of the refund is reimbursed. No source is picked here. Which one Amazon's claim forms enforce is a live-account question (Open questions 1).
122
+
123
+ ### G. The Reimbursements report as Amazon defines it
124
+
125
+ `GET_FBA_REIMBURSEMENTS_DATA`: "Contains itemized details of a seller's inventory reimbursements, including the reason for the reimbursement. Content updated daily." "This report can only be requested." Columns: `approval-date`, `reimbursement-id`, `case-id`, `amazon-order-id`, `reason`, `sku`, `fnsku`, `asin`, `product-name`, `condition`, `currency-unit`, `amount-per-unit`, `amount-total`, `quantity-reimbursed-cash`, `quantity-reimbursed-inventory`, `quantity-reimbursed-total`, `original-reimbursement-id`, `original-reimbursement-type`. Roles: Pricing, Amazon Fulfillment. [official] (FBA Reports .md, updatedAt 2026-10-13, read 2026-11-09.) Amazon publishes no list of `reason` values on any page read; Seller Central's Reimbursements report help page (G200732720) is a JS shell. Values seen in practice are under § What practitioners add.
126
+
127
+ ### H. Settlement and transaction views
128
+
129
+ The V2 flat file condenses money into `amount-type`, `amount-description`, `amount`: "The `amount-type` and `amount-description` columns contain the type of charge or fee you have incurred, and indicates whether different fees are related to a common type. Amount values always populate in a single `amount` column, so there's no need to parse the rows to find a number, even if new fees or transaction types are introduced in the future. Additionally, amounts are displayed in local currency formats (for example, `95,00` for EU instead of `95.00`)." Refund and adjustment rows carry `adjustment-id` and `merchant-adjustment-item-id`. [official] (Settlement Reports .md, updatedAt 2026-10-14, read 2026-11-09.) No Amazon page lists `transaction-type` or `amount-description` values. The Payments Transaction view filters include "Refund, Chargeback Refund, A-to-z Guarantee Refund, Service Fees and Paid to Amazon", last 24 months only (survey §1, Amazon staff posts).
130
+
131
+ ### I. Adjustments in the Finances v0 model
132
+
133
+ `AdjustmentEvent.AdjustmentType` — the model's complete list [command-verified]:
134
+ - `FBAInventoryReimbursement`: "An FBA inventory reimbursement to a seller's account. This occurs if a seller's inventory is damaged."
135
+ - `ReserveEvent`: "A reserve event that is generated at the time a settlement period closes. This occurs when some money from a seller's account is held back."
136
+ - `PostageBilling`: "The amount paid by a seller for shipping labels."
137
+ - `PostageRefund`: "The reimbursement of shipping labels purchased for orders that were canceled or refunded."
138
+ - `LostOrDamagedReimbursement`: "An Amazon Easy Ship reimbursement to a seller's account for a package that we lost or damaged."
139
+ - `CanceledButPickedUpReimbursement`: Easy Ship, "used only in the India marketplace."
140
+ - `ReimbursementClawback`: "An Amazon Easy Ship reimbursement clawback from a seller's account. This occurs when a prior reimbursement is reversed. This value is used only in the India marketplace."
141
+ - `SellerRewards`: "An award credited to a seller's account for their participation in an offer in the Seller Rewards program. Applies only to the India marketplace."
142
+
143
+ `AdjustmentItem`: `Quantity` ("the number of units in the seller's inventory when the `AdjustmentType` is `FBAInventoryReimbursement`"), `PerUnitAmount`, `TotalAmount`, `SellerSKU`, `FnSKU`, `ProductDescription`, `ASIN`, `TransactionNumber` ("The transaction number that is related to the adjustment"; release note: "Amazon Shipping customers can use this to get an invoice number"). `AdjustmentEvent` has `PostedDate`, `StoreName`, `AdjustmentAmount`. **None of** `ReserveDebit`, `ReserveCredit`, `WAREHOUSE_DAMAGE`, `REVERSAL_REIMBURSEMENT`, `FREE_REPLACEMENT_REFUND_ITEMS`, `MISSING_FROM_INBOUND` or `PostageBilling_*` occurs anywhere in the models clone [command-verified: `grep -rl` over `models/` and `schemas/`, 2026-11-09]. Those names are what sellers see in responses and settlement files (§ What practitioners add); the model's list is not closed in practice.
144
+
145
+ Other v0 event lists that move refund, claim or reimbursement money [command-verified]: `RefundEventList`, `GuaranteeClaimEventList`, `ChargebackEventList`, `SAFETReimbursementEventList`, `RetrochargeEventList` (`Retrocharge`, `RetrochargeReversal`; `BaseTax`, `ShippingTax`), `ChargeRefundEventList`, `ServiceFeeEventList`, `DebtRecoveryEventList` (`DebtPayment`, `DebtPaymentFailure`, `DebtAdjustment`), `RemovalShipmentEventList` / `RemovalShipmentAdjustmentEventList` (`WHOLESALE_LIQUIDATION`; "A negative value indicates a full or partial refund owed to the buyer"), `FBALiquidationEventList` ("used only in the US marketplace"), `EBTRefundReimbursementOnlyEventList` (2026-01-28: "Amazon refunds the seller, and then the seller refunds the customer"), `TDSReimbursementEventList`, `TaxWithholdingEventList`, `AdhocDisbursementEventList`, `ValueAddedServiceChargeEventList`.
146
+
147
+ ### I2. How A-to-z, chargeback and SAFE-T money posts, face by face (verifier, 2026-11-10)
148
+
149
+ | Event | Finances v0 | Finances v2024-06-19 | Settlement V2 flat file |
150
+ |---|---|---|---|
151
+ | A-to-z claim granted (debit) | `GuaranteeClaimEventList`, items of the `ShipmentEvent`/`ShipmentItem` shape with `ItemChargeAdjustmentList`, `ItemFeeAdjustmentList`, `PromotionAdjustmentList` ("only returned for refunds, guarantee claims, and chargeback events") and `OrderAdjustmentItemId` [official, command-verified] | `transactionType` documented only as `Shipment`; no public sample of an A-to-z transaction was found; item id `ORDER_ADJUSTMENT_ITEM_ID` exists for this family [official model; values open] | `transaction-type` `A-to-z Guarantee Refund`. A public AU mapping (abinashstack, upper-cased by its author, re-read 2026-11-10) books its rows as `ItemPrice` `Principal` / `Tax`, `ItemFees` `Commission` / `RefundCommission` and `ItemWithheldTax` `MarketplaceFacilitatorTax-Principal`, the same parts as a refund [opinion, command-verified] |
152
+ | Chargeback (service-related, debit) | `ChargebackEventList`, same item shape [official, command-verified] | `Chargeback` seen as a `transactionType` in public pulls (§ What practitioners add) [opinion] | `transaction-type` `Chargeback Refund` (wimoor table, re-read 2026-11-10) [opinion, command-verified] |
153
+ | Chargeback won by the seller (credit back) | No event type named for it in the model [command-verified] | Not seen | Not seen; Amazon's words: "the credit is reversed and the funds are returned to the seller" (sell.amazon.com, 2025-12-01) [official] |
154
+ | SAFE-T reimbursement (credit) | `SAFETReimbursementEventList` → `SAFETReimbursementEvent` (`PostedDate`, `SAFETClaimId`, `ReimbursedAmount`, `ReasonCode` "Indicates why the seller was reimbursed", `SAFETReimbursementItemList` with `itemChargeList`, `productDescription`, `quantity`); charge type `SAFE-TReimbursement` "The SAFE-T claim amount for the item" [official, command-verified] | Not seen in any public pull | `SAFE-T_REIMBURSEMENT` as transaction-type and amount-description with amount-type `OTHER_TRANSACTIONS` in the AU mapping (upper-cased by its author) [opinion, command-verified] |
155
+ | Reserve against such claims | v0 `AdjustmentType` `ReserveEvent` | `listBalances` `ACCOUNT_LEVEL_RESERVE`: "Balance reserved as a safety measure to cover potential liabilities such as refunds, chargebacks, or other claims. Based on sales volume, product category, and account history." [official, command-verified] | `Current Reserve Amount` / `Previous Reserve Amount Balance` [opinion] |
156
+
157
+ What a debit on these lines carries back (whether the referral fee returns less the refund administration fee, as on a refund) is shown in public files only for A-to-z (the AU mapping's `Commission` / `RefundCommission` rows); for chargebacks and for the v2024-06-19 face it is a live-account question (Open questions 10, 11).
158
+
159
+ ### J. Value recovered from returned and unsellable units: Grade and Resell, Donations, Amazon Resale (gap fill, 2026-11-10)
160
+
161
+ A returned FBA unit that is not put back in sellable stock and not reimbursed can still produce money, or cost money, through Amazon's value-recovery programmes. Liquidation as money (`FBALiquidationEvent`, the EU/CA liquidations referral fee) is in `fulfilment-charges.md` § H4 and P-ful-11, and removal and disposal fees are in § H there; this section covers the rest. The Seller Central help pages for these programmes (FBA Grade and Resell GUA6RV6UA4DR2MFK; FBA Donations VCFMKLPUTBXE7L5) are JavaScript shells to a plain GET on `.com` and `.co.uk` (tried 2026-11-10). Their text is quoted below from News posts, Amazon staff posts, sell.amazon.com, and a seller's 2021 copy of the UK help page.
162
+
163
+ **J1. FBA Grade and Resell.**
164
+ - What it is: "FBA Grade and Resell allows you to recover value on unfulfillable inventory by having Amazon grade and relist eligible items as Used, instead of returning, removing or disposing the inventory. When you submit an item, Amazon evaluates the condition and creates the listing on your behalf, with you as the seller on record. You set the price and manage the listing, just like you would for your current new and used items." [official, staff] (Jameson_Amazon, "Get answers about FBA Grade and Resell at an Ask Amazon event today, December 10th", posted 2024-11-21, https://sellercentral.amazon.com/seller-forums/discussions/t/78c455ed-3390-4c08-8d62-6a83d285e265, read 2026-11-10.) The staff answers in that thread are behind "Show replies" (JavaScript) and were not read.
165
+ - Grades: "eligible FBA returns are inspected to see if they can be relisted with one of four Used conditions: 'Like New,' 'Very Good,' 'Good,' or 'Acceptable.'" [official] (sell.amazon.com blog, "Give returns a second life with FBA Grade and Resell", Mickey Toogood, 2025-09-11, https://sell.amazon.com/blog/announcements/fba-grade-and-resell, read 2026-11-10.)
166
+ - US: "The FBA Grade and Resell program is an optional fee-based service, with the flexibility to unenroll at any time." [official] (News_Amazon, "Give returns a second life with FBA Grade and Resell", posted 2024-08-07 (page `datePublished`), https://sellercentral.amazon.com/seller-forums/discussions/t/3fa4fa3c-d2a0-4233-b668-6785a5695dcc, read 2026-11-10.)
167
+ - EU: "You can now recover up to 80% of your product value from unfulfilled customer returns through the FBA Grade and Resell programme. This programme automatically evaluates and lists your returned items in used condition. You have full control over pricing without any programme fees (we'll provide 60 days notice before introducing any fees). This service is currently available to sellers in the UK, France, Germany, Italy, Spain, Czech Republic and Poland." Enrolment: Settings → Fulfilment by Amazon → "Automated unfulfillable settings" → "Enrol in value recovery options" → "Set your recovery rates per condition tier". [official] (News_Amazon, "Recover up to 80% value from returns with FBA Grade and Resell", posted 2025-02-24, https://sellercentral.amazon.co.uk/seller-forums/discussions/t/ef44a47a-bf4d-4075-a5af-23b4aa7b190e, read 2026-11-10.) "Up to 80%" is Amazon's marketing ceiling, not a rate.
168
+ - 2026-02-03 changes: categories added ("Watches, Jewelry, Luggage, Shoes, Apparel"); "Used item prices now update automatically to match New item pricing and discount percentages"; "When any Used item price is adjusted manually that item is opted out of automatic updates"; "Sellers can now handpick up to 2,000 ASINs that they want to include in the program or enroll their entire catalog, excluding specific items"; out-of-stock graded SKUs are "automatically removed from the inventory management view". [official] (sell.amazon.com blog, "New features and updates to Amazon's FBA Grade and Resell program", Mickey Toogood, 2026-02-03, https://sell.amazon.com/blog/announcements/fba-grade-and-resell-updates, read 2026-11-10.)
169
+ - History: UK first ("now available in the UK and will be available in the US by the end of the year"; DE, FR, IT, ES "by early 2022") [official] (News_Amazon EU, "Planet-friendly alternatives for returned and overstock FBA items", posted 2021-08-18, https://sellercentral-europe.amazon.com/seller-forums/discussions/t/f8f019e56ed2b63ea795cd315071bc3f, read 2026-11-10). A 2022 Amazon email quoted on the Japan forum: "Amazon will also continue to waive all fees related to Grade and Resell program through 2022", and "We use the same grading process as Amazon Warehouse Deals" [official, relayed] (https://sellercentral-japan.amazon.com/seller-forums/discussions/t/cabf4fef557d8ad4c7c8683192f2d745, posted 2022-07-29, read 2026-11-10).
170
+ - **The money rules, from the UK help page as copied by a seller on 2021-06-30** (GUA6RV6UA4DR2MFK; the copy is five years old and its fee waiver and £15 floor are dated; the current page was not readable) [official, relayed] (Seller Forums EU, "Haven't seen this before", https://sellercentral-europe.amazon.com/seller-forums/discussions/t/31050ea5859ae91f630bb83cd936ba06, read 2026-11-10):
171
+ - "At the time of relisting, a processing fee will apply. No processing fee will apply for submitted items that are graded as Unsellable."
172
+ - "Referral fees and FBA fulfilment fees still apply."
173
+ - "Standard removal fees do not apply to submitted FBA Grade and Resell items. If you dispatch to an address or dispose of the inventory after an item is graded and relisted, removal fees will apply."
174
+ - "Once the FBA Grade and Resell removal order is submitted, inventory storage fees will cease to accrue for that inventory. For items graded as Used, the clock restarts on long-term storage fees and monthly storage fees once your item is listed."
175
+ - "Once an item is graded as Used, a SKU is generated for your new listing under the parent ASIN." "All SKUs in FBA Grade and Resell begin with amzn.gr to allow you to search for and track graded inventory in Seller Central. The listings will display in your inventory reporting tools, and payments will be displayed in the Payments Dashboard."
176
+ - "A maximum of five SKUs will be generated for your used listing under the parent ASIN: four used conditions and one unsellable." "If your item is graded as Unsellable … The unsellable item will appear with a new FNSKU, beginning with amzn.gr, under the parent ASIN."
177
+ - "The initial list price for a used item is calculated based on your discount percentage values multiplied by the new item price at the time of relisting."
178
+ - Tracking: "You can track the status of graded items in the Removal Order Detail report. The total number of inventory you have submitted to the programme shows in the Requested Qty column. The Completed Qty column shows inventory that has been graded."
179
+ - "To ensure a net positive transaction after fees are applied, inventory must have a minimum calculated average sales price (ASP) of £15" (2021, UK).
180
+ - **What follows for money** [seat]: a graded unit sells as an ordinary order of the seller's, under a SKU the seller did not create, priced as a share of the new price, with referral, fulfilment and (where charged) processing fees. Its proceeds sit under the amzn.gr SKU, not under the SKU whose refund created the unit. The current fee basis per store is read at run time; the only per-unit US figures found are a practitioner's (§ Facts for human readers only).
181
+
182
+ **J2. FBA Donations and the 2025 enrolment changes.**
183
+ - "The Fulfillment by Amazon (FBA) Donations program helps sellers donate unwanted product, including returns and eligible overstock FBA inventory." "By default, all US sellers who use FBA are enrolled in the FBA Donations program." "The language used in Seller Central for donating your products currently says 'Dispose' or 'Donate/Recycle' to refer to donations." "Since sellers who use FBA are automatically opted into the program, any product that is returned and is ineligible for resale may automatically be donated." "Don't know if you donated? Check your Removal Order Detail Report." "Your donation certificate will be generated on a yearly basis and can be found on the Donations page in Seller Central. The donation certificate contains the quantity and description of your inventory that was donated through the program in the previous year." It "can be used to receive a tax benefit when filing taxes." Partner: Good360, since 2019. [official] (sell.amazon.com blog, "Sellers who use FBA Donations now have access to donation certificates", Sidny Oshinsky, 2026-03-09, https://sell.amazon.com/blog/announcements/fba-donation-certificate, read 2026-11-10.)
184
+ - Fee: an Amazon moderator quotes the help page: "When you request disposal of eligible overstock, returned, or other unwanted FBA inventory in US fulfillment centers, Amazon makes it available to select US charities. Our usual disposal fees apply." [official, staff] (Topher_Amazon, "Removal Order Fees", thread posted 2024-02-20, https://sellercentral.amazon.co.uk/seller-forums/discussions/t/cadc9497-4cc1-40c5-937c-25e2d8874a21, read 2026-11-10.) So a donated unit moves money one way: a disposal fee out, no proceeds in.
185
+ - Stores: "FBA Donations, which started in the US and the UK in 2019 and in France in 2020"; partners "Good360, Age UK and Secours populaire français". [official] (News_Amazon EU, 2021-08-18, above.)
186
+ - Enrolment change, as announced: "On September 30, 2025, we'll update the enrollment process for the US and Canada … The FBA Liquidations program … will become the default option for your unsold inventory. If you haven't configured your automated fulfillable settings and automated unfulfillable settings, you'll automatically be enrolled in the Liquidations program. You can still opt out of the Liquidations program at any time. The FBA Donations program … will become mandatory. As of September 30, 2025, you won't be able to opt out. If you've previously opted out, you will be re-enrolled. There are no changes to the fees for either program." [official] (News_Amazon, "Enrollment changes for FBA Liquidations and Donations programs", posted 2025-08-22, https://sellercentral.amazon.com/seller-forums/discussions/t/8a402163-2acc-41b0-b4ea-fe6c9b763856; Canada copy …amazon.ca/…/faf1e3b4-9d24-4bda-97ec-0928f92e478f; read 2026-11-10.)
187
+ - Correction, as relayed by a seller who received it on 2025-09-30: "The changes described below apply to the US only. The FBA Liquidations and Donations programs are unchanged in Canada. Also, the change to the US FBA Donations program has been delayed until October 30, 2025." "On October 30, 2025, the FBA Donations program … will become mandatory in the US if you select Dispose. … You can unselect Dispose and choose other channels, such as Return, Grade and Resell, or Liquidations, at any time." [official, relayed] (Sellers Ask Sellers, "Enrollment changes for FBA Liquidations and Donations programs", reply posted 2025-09-30, https://sellersasksellers.com/t/enrollment-changes-for-fba-liquidations-and-donations-programs/6434, read 2026-11-10.) No Amazon News post of the correction was found; the original News post still reads US and Canada, 2025-09-30.
188
+
189
+ **J3. Amazon Resale (formerly Amazon Warehouse).**
190
+ - Amazon's reimbursement policy text: reimbursed units, "including lost items that are found after reimbursement, may be listed for sale on Amazon warehouse or other channels" (policy PDF, E4a) [official]. Grade and Resell uses the grading process of Amazon Warehouse ("Amazon Warehouse uses the same process to evaluate customer returns", UK help copy, J1; "the same grading process as Amazon Warehouse Deals", 2022 email, J1) [official, relayed].
191
+ - The rename: Amazon announced Amazon Warehouse as Amazon Resale in a corporate blog post in August 2024 ("That's where Amazon Resale comes in", quoted by Digital Commerce 360, 2024-08-20, https://www.digitalcommerce360.com/2024/08/20/amazon-resale-replaces-warehouse-with-rebrand/); UK: "Amazon checks, refurbishes, tests and resells returned items" (ChannelX, 2024-10, https://channelx.world/2024/10/amazon-renames-amazon-warehouse-to-amazon-resale/) [opinion, press quoting Amazon; the aboutamazon post itself was not found]. That Amazon Resale "features only Amazon Retail products, and not items from third party sellers" was seen only in search snippets of trade press (EcommerceBytes, unreachable) [snippet].
192
+ - **What follows for money** [seat]: a seller's unit sold through Amazon Resale is Amazon's unit by then (reimbursed, or found after reimbursement), so the seller's money on it is the reimbursement (and any reversal, E7), never resale proceeds. A seller-owned used offer of the same ASIN, on the other hand, is the seller's Grade and Resell SKU (J1). The two are told apart by the seller of record, not the condition.
193
+
194
+ **J4. Where Amazon shows recovered value.** Seller Central's Returns and Recovery Insights has "A Recovery tab" covering "Grade and Resell, liquidation, removal and disposal value" [official] (listing seat, `research/angles/returns.md`, read 2026-10-14). No SP-API operation or report was found for that tab [command-verified: no operation in `tools/ops.tsv`; no report type in the FBA Reports page mentions Grade and Resell, donations or recovery, `grep -i 'grade\|resell\|donat\|recovery'` over report-type-values-fba.md (updatedAt 2026-10-13), 2026-11-10]. The Removal Order Detail report carries Grade and Resell submissions and donations (J1, J2) with `order-type`, `requested-quantity`, `disposed-quantity`, `in-process-quantity` and `removal-fee`; Amazon lists no `order-type` values.
195
+
196
+ ## The SP-API and report faces
197
+
198
+ Roles are from Role Mappings for SP-API Operations (`web01/role-mappings.md`, updatedAt 2026-10-28) and Role Mappings for SP-API Types (`web01/role-mappings-for-types.md`, updatedAt 2026-09-09); "door" = the four roles sellers tick today (Product Listing, Pricing, Brand Analytics, Finance and Accounting); AF = Amazon Fulfillment (being asked for). Rates are from the models [command-verified].
199
+
200
+ | Read | Carries | Model / page | Rate (rps / burst) | Role | Notes and pitfalls Amazon names |
201
+ |---|---|---|---|---|---|
202
+ | Finances v2024-06-19 `listTransactions` (`GET /finances/2024-06-19/transactions`) | Every posted transaction incl. refunds, claims, reimbursements, adjustments; `relatedIdentifiers` (`ORDER_ID`, `SHIPMENT_ID`, `FINANCIAL_EVENT_GROUP_ID`, `REFUND_ID`, `INVOICE_ID`, `DISBURSEMENT_ID`, `TRANSFER_ID`, `DEFERRED_TRANSACTION_ID`, `RELEASE_TRANSACTION_ID`, `SETTLEMENT_ID`); item ids `ORDER_ADJUSTMENT_ITEM_ID`, `COUPON_ID`, `REMOVAL_SHIPMENT_ITEM_ID`, `TRANSACTION_ID`; `breakdowns`; `contexts` (ProductContext asin/sku/`fulfillmentNetwork`) | `finances_2024-06-19.json` | 0.5 / 10 | Finance and Accounting (door) | `transactionType` "Possible value: `Shipment`" only; `description` examples "`Order Payment`, `Refund Order`"; "`breakdownType` is an open-ended string; Amazon does not publish a closed list of values" (Get the latest transactions .md, updatedAt 2026-09-24, not the model); ">180 days apart → empty"; "might not include orders from the last 48 hours"; empty pages with `nextToken`; filterable only by `FINANCIAL_EVENT_GROUP_ID` and `ORDER_ID` ("the only `relatedIdentifier` with filtering capabilities at the moment"); the 2026-07-29 release note's `SETTLEMENT_ID` filter was added to the model 2026-10-28 (df7c6298) and removed 2026-10-29 (db2936aa), and the live reference lists only the two; `SETTLEMENT_ID` still comes back as a related identifier in responses (model enum) and filters `listSummary`; includes `DEFERRED` unless filtered. Guide: listing by order finds "refunds, chargebacks, or order adjustments, which can occur days, weeks, or even months later" (List Transactions Associated with an Order .md, updatedAt 2026-09-09). |
203
+ | `listSummary`, `listBalances` | Net proceeds by breakdown (`Sales`, `Expenses`, `Refunds` in the example) per period or `SETTLEMENT_ID`; balances incl. `ACCOUNT_LEVEL_RESERVE` ("to cover potential liabilities such as refunds, chargebacks, or other claims") | same | 0.5 / 10 | Finance and Accounting | Added 2026-07-29. |
204
+ | Finances v0 `listFinancialEvents`, `…ByOrderId`, `…ByGroupId` | Event lists of § I | `financesV0.json` | 0.5 / 30 | `listFinancialEvents`: AISP (EU), **Amazon Fulfillment (NA, FE)**, Finance and Accounting; `ByGroupId`: AISP (EU), F&A; `ByOrderId`: F&A | Deprecated 2025-07-21, removal 2027-08-27 (Deprecations); "Deferred events don't appear … until they are released"; ByGroupId "only retrieves a group's data for the past two years". |
205
+ | `listFinancialEventGroups` | Settlement groups (`FinancialEventGroupId` → v2024 filter) | `financesV0.json` | 0.5 / 30 | AISP (EU), F&A | Not on the deprecation schedule. |
206
+ | `GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2` | Settlement rows with `transaction-type`, `amount-type`, `amount-description`, `adjustment-id`, `merchant-adjustment-item-id` | Settlement Reports .md (2026-10-14) | Reports API | Finance and Accounting | Cannot be requested; `getReports` only. Old flat/XML removed 2026-11-11. |
207
+ | `GET_DATE_RANGE_FINANCIAL_HOLDS_DATA` | Deferred transactions (`type`, `order-id`, `product-sales`, fees, `other`, `total`) | Payment Reports .md (2026-09-09) | Reports API | Finance and Accounting | "You must request the Deferred Transaction Report through the Payments Reports Repository on Seller Central before" the API can fetch it. |
208
+ | `GET_FBA_REIMBURSEMENTS_DATA` | § G | FBA Reports .md (2026-10-13) | Reports API | Pricing, Amazon Fulfillment (door via Pricing) | Request-only; daily. No reason-code list. |
209
+ | `GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA` | FBA returns received at an FC: `return-date`, `order-id`, `sku`, `asin`, `fnsku`, `quantity`, `fulfillment-center-id`, `detailed-disposition`, `reason`, `status`, `license-plate-number`, `customer-comments` | same | Reports API | Pricing, AF (door) | Returnless refunds "don't appear" (G200453320, listing seat). |
210
+ | `GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_REPLACEMENT_DATA` | Replacements (A9) | same | Reports API | **Amazon Fulfillment only** | NA and IN stores only. |
211
+ | `GET_FBA_FULFILLMENT_REMOVAL_ORDER_DETAIL_DATA`, `…_REMOVAL_SHIPMENT_DETAIL_DATA` | Removal quantities, `removal-fee`; shipped units, carrier, tracking (for removal-lost claims) | same | Reports API | Pricing, AF (door) | Detail "can be used to help reconcile the total number of items requested to be removed … with the actual number of items removed"; shipment detail "will not include canceled returns or disposed items". |
212
+ | `GET_LEDGER_DETAIL_VIEW_DATA`, `GET_LEDGER_SUMMARY_VIEW_DATA` | Adjustments (lost, found, damaged, disposed) with `Reason`, `Reference ID`, `Reconciled Quantity`, `Unreconciled Quantity` | same | Reports API | **Amazon Fulfillment only** | 18 months; `eventType=Adjustments`. Stock pack owns. |
213
+ | `GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE`, `GET_XML_RETURNS_DATA_BY_RETURN_DATE` | Seller-fulfilled returns: `Label cost`, `Label to be paid by`, `A-to-Z Claim`, `Resolution`, `Refunded Amount`, SafeT columns, `Order Amount` | Returns Reports .md (2026-10-28) | Reports API | Inventory and Order Tracking, DtC Shipping (Restricted) — **not door** | 60 days per report; excludes FBA returns and "Returnless refunds". |
214
+ | `GET_CSV_MFN_PRIME_RETURNS_REPORT`, `GET_XML_MFN_PRIME_RETURNS_REPORT` | Same fields, Seller Fulfilled Prime | same | Reports API | IOT, **Pricing**, DtC (R) (door via Pricing) | 60 days. |
215
+ | `GET_FLAT_FILE_MFN_SKU_RETURN_ATTRIBUTES_REPORT` (XML variant: IOT, DtC only) | Per SKU `provide_prepaid_label`, returnless eligibility | same | Reports API | IOT, DtC (R), Pricing (flat) | — |
216
+ | Data Kiosk `analytics_salesAndTraffic_2024_04_24` | `unitsRefunded`, `refundRate`, `claimsAmount`, `claimsGranted`, B2B variants; by date and by ASIN | schema | Data Kiosk | **Brand Analytics** (createQuery, door) | B2B fields 2026-01-28. |
217
+ | Data Kiosk `analytics_economics_2024_03_15` | `refundedProductSales` ("counted by refund request time"), `unitsRefunded`, `netProductSales`, `netProceeds` | schema | Data Kiosk | **Open**: Role Mappings (`createQuery`, 2026-10-28) and the Data Kiosk page say Brand Analytics for every operation; Amazon's correction (https://developer-docs.amazon/sp-api/changelog/correction-data-kiosk-role-requirements, 2024-07-02) says "The Economics dataset requires the Selling Partner Insights role." | `netProceeds` = "sales.netProductSales - sum of fees.charge.totalAmount - sum of ads.charge.totalAmount - (cost …) * sales.netUnitsSold": reimbursements are not in it [seat, from the formula]. |
218
+ | Data Kiosk `analytics_sellerAnalytics_2025_03_31` | `returns` (`returnedUnits` "including returnless refunds, mapped to the day each unit was shipped", `totalRefundAmount` "including all refunds", `returnedRate`; "a delay of about 45 days"); `refundsOrderCount`; account-health claim and chargeback counts | schema | Data Kiosk | Brand Analytics; some fields `@paamRights` | — |
219
+ | Support API v2025-02-01 `listCases` (POST as read), `getCase`, `listContacts` | Case `status` (`RESOLVED`, `TRANSFERRED`, `PENDING_MERCHANT_ACTION`, `PENDING_AMAZON_ACTION`), `subject`, dates, contacts | `support_2025-02-01.json` | 0.1 / 10 | **Selling Partner Support (Restricted)** — not door | Read only; no create. Would open the status of reimbursement and claim cases (the reimbursements report's `case-id`). Nothing is built on it. |
220
+ | Notification `TRANSACTION_UPDATE` | A posted transaction (`TransactionType`, `RelatedIdentifiers`, `TotalAmount`) | `TransactionUpdateNotification.json` | SQS | not listed in Role Mappings for Types | Needs an SQS destination; noted only. |
221
+
222
+ No operation in the models issues a refund, files a reimbursement claim, files or answers a SAFE-T, A-to-z or chargeback case, sets returnless or partial-refund rules, or writes a sourcing cost [command-verified: no such operation in `tools/ops.tsv`, 394 ops].
223
+
224
+ **Value-recovery faces (gap fill, 2026-11-10).** No model, operation or report type names Grade and Resell, donations or Amazon Resale [command-verified: `grep -i 'resell\|donat'` over `models/` and `schemas/` finds only `DeemedResellerCategory` (EU VAT) in the Orders model; 0 of 394 rows in `ops.tsv`]. The money reaches the existing faces:
225
+
226
+ | Read | What carries value recovery | Role (Role Mappings, 2026-10-28 / types 2026-09-09) | Notes |
227
+ |---|---|---|---|
228
+ | Finances `listTransactions` / v0 `ShipmentEventList`; settlement V2 | A graded unit's sale, under its `amzn.gr.` SKU (`ProductContext.sku`, v0 `SellerSKU`, settlement `sku`) [seat, from J1 "payments will be displayed in the Payments Dashboard"; open question 17]; liquidation as `FBALiquidationEvent` / `Liquidations` (fulfilment-charges H4) | Finance and Accounting (door) | No public file with an amzn.gr row was found; how the processing fee is labelled is open (open question 16). |
229
+ | Orders `getOrderItems` (v0) | `ConditionId` ("`New`, `Used`, …") and `ConditionSubtypeId` ("`Mint`, `Very Good`, `Good`, `Acceptable`, …") and `SellerSKU` per item [official, command-verified: `ordersV0.json`] | any of Amazon Fulfillment, Finance and Accounting, Pricing, Product Listing, … (door) | Tells a used (graded) sale from a new one on the order. |
230
+ | `GET_FBA_FULFILLMENT_REMOVAL_ORDER_DETAIL_DATA` | Grade and Resell submissions (requested / completed / in-process) and donations ("Check your Removal Order Detail Report"); `removal-fee` | Pricing, Amazon Fulfillment (door via Pricing) | Amazon lists no `order-type` values. |
231
+ | Data Kiosk `analytics_economics_2024_03_15` | amzn.gr MSKUs as their own rows with fee components (a practitioner's live pull, § What practitioners add) | open (P-ref-28) | — |
232
+ | Ledger detail | Graded and unsellable-graded units under amzn.gr SKUs / FNSKUs (J1) | Amazon Fulfillment only | Stock pack owns. |
233
+
234
+ ## What practitioners add
235
+
236
+ ### Values seen in practice (settlement, Finances, reimbursement reasons, ledger)
237
+
238
+ Amazon publishes no value list for any of these fields. The Seller Central help pages that might hold them (G200732720 Reimbursements report; GMGJASYYNYLXKLXE reimbursement types) are JS shells, and no one found quotes their lists. Every value below comes from third-party files or code on public GitHub repositories, vendor glossaries, or Amazon-repo GitHub issues filed by developers. **[cv]** = a grep or parse this seat's helper ran over a public file downloaded on 2026-11-09. All are [opinion] as to meaning. A value seen is a fact that it occurs. It is not a closed list.
239
+
240
+ **Settlement V2 `transaction-type`.**
241
+ - Seen: `Order`, `Refund`, `A-to-z Guarantee Refund`, `Chargeback Refund`, `other-transaction`, `ServiceFee`, `Order_Retrocharge`, `Refund_Retrocharge`, `Fee Adjustment`, `Liquidations`, `Liquidations Adjustments`, `SellerReviewEnrollmentPayment`, `CouponRedemptionFee`, `Lightning Deal Fee`, `Vine Enrollment Fee`.
242
+ - Sources: an accountant's US mapping, https://github.com/bbalajiarjun130/Accounting-Project (file "FBA MAR 5 - MAR 19 Prep file…csv"); the wimoor ERP lookup table of 136 settlement strings, https://github.com/wimoor-erp/wimoor/blob/master/init-config/mysql/%E6%95%B0%E6%8D%AE/db_amazon/t_amz_settlement_amount_description.sql [cv].
243
+ - An AU mapping (https://github.com/abinashstack/amazon-reconciliation/blob/main/data/amazon_settlement_configs_au.csv, upper-cased by its author) adds `SAFE-T_REIMBURSEMENT`, `SELLER_REWARDS`, `FBAFEES`, `AMAZONFEES`, `TRANSFERS`.
244
+ - A real file quoted in https://github.com/amzn/selling-partner-api-models/issues/5353 shows `other-transaction - Reversal` with amount-type `Inbound Defect Fee`.
245
+
246
+ **Settlement V2 `amount-type`.**
247
+ - Seen: `ItemPrice`, `ItemFees`, `Promotion`, `ItemWithheldTax`, `other-transaction`, `FBA Inventory Reimbursement`, `Cost of Advertising`.
248
+ - The AU mapping adds `MCF_INVENTORY_REIMBURSEMENT`, `POINTS`, `REFUND_FOR_ADVERTISER`.
249
+
250
+ **Settlement `amount-description` on refund rows** (Refund, A-to-z Guarantee Refund, Chargeback Refund):
251
+ - ItemPrice: `Principal`, `Shipping`, `ShippingTax`, `Tax`, `GiftWrap`, `GiftWrapTax`, `Goodwill`, `RestockingFee`, `ReturnShipping`.
252
+ - wimoor's definition of `Goodwill`: "Customer refund, not applied against a specific charge".
253
+ - ItemFees: `Commission`, `RefundCommission`, `ShippingChargeback`, `GiftwrapChargeback`, `DigitalServicesFee`, `RemoteFulfillmentCredit`.
254
+ - wimoor's definition of `RefundCommission`: "When a refund is issued, the fee charged against the original fee amount being refunded". This is the refund administration fee as practitioners label it.
255
+ - ItemWithheldTax: `MarketplaceFacilitatorTax-Principal/-Shipping/-Other/-RestockingFee`, `MarketplaceFacilitatorVAT-*`, `LowValueGoodsTax-*`.
256
+ - Promotion: `Principal`, `Shipping`, `TaxDiscount`.
257
+ - The US mapping also has `A2ZGuaranteeRecovery`, `CommissionCorrection`.
258
+ - wimoor alone has `Refund Reimbursal` ("Reimbursal of amount charged to seller for customer refund").
259
+
260
+ **Settlement `amount-description` on reimbursement rows** (`other-transaction` / `FBA Inventory Reimbursement`). Meanings below are from Synder's per-code glossary (https://synder.com/fees-amazon/), A2X ("Amazon seller reimbursements accounting", updated 2025-02-28, https://www.a2xaccounting.com/ecommerce-accounting-hub/amazon-seller-reimbursements-accounting) and Amalytix (https://amalytix.com/en/knowledge/controlling/amazon-seller-fees, updated 2026-10-20):
261
+ - `WAREHOUSE_LOST`; `WAREHOUSE_LOST_MANUAL` (paid "only after the seller initiates an investigation").
262
+ - `WAREHOUSE_DAMAGE`; `WAREHOUSE_DAMAGE_EXCEPTION` (paid after the seller asks).
263
+ - `MISSING_FROM_INBOUND`; `MISSING_FROM_INBOUND_CLAWBACK` (taken back when units are found).
264
+ - `REVERSAL_REIMBURSEMENT`.
265
+ - A2X: "When Amazon takes back the cash payment for a previous reimbursement and gives you inventory instead".
266
+ - Synder: "can appear as either a charge or a credit".
267
+ - `COMPENSATED_CLAWBACK` (reverses an earlier reimbursement, e.g. found stock).
268
+ - `FREE_REPLACEMENT_REFUND_ITEMS` (the original of a free replacement was not returned).
269
+ - `CS_ERROR_ITEMS`, `INCORRECT_FEES_ITEMS`, `INCORRECT_FEES_NON_ITEMIZED`, `RE_EVALUATION`, `INBOUND_CARRIER_DAMAGE`, `PAYMENT_RETRACTION_ITEMS`.
270
+ - `MULTICHANNEL_ORDER_LOST` / `_DAMAGED` (MCF).
271
+ - `REMOVAL_ORDER_LOST` / `_DAMAGED` (Synder pages and Lingxing's doc; not in any settlement mapping found).
272
+
273
+ **Settlement reserve and other adjustments.**
274
+ - Reserve: `Current Reserve Amount` and `Previous Reserve Amount Balance` on `other-transaction` rows.
275
+ - wimoor: "held back in a settlement period to cover potential expenses such as returns and refunds".
276
+ - Others seen: `MiscAdjustment`, `NonSubscriptionFeeAdj`, `BalanceAdjustment`, `BuyerRecharge`, `Shipping label purchase for return`, `PostageAdjustment`, `FBACustomerReturn`, `Payable to Amazon`.
277
+
278
+ **Finances v0 `AdjustmentType` seen in responses but not in the model.**
279
+ - `ReserveDebit` / `ReserveCredit` (in place of `ReserveEvent`); `WAREHOUSE_DAMAGE` (in place of `FBAInventoryReimbursement`), `REVERSAL_REIMBURSEMENT`, `COMPENSATED_CLAWBACK`.
280
+ - Source: https://github.com/amzn/selling-partner-api-models/issues/1363 (2021, closed by a bot, no Amazon answer).
281
+ - A 7-day pull of 477 events, written up 2026-05-22, gave the `PostageBilling_*` family:
282
+ - `PostageBilling_Postage`, `_Insurance`, `_PostageAdjustment`, `_FuelSurcharge`, `_TransactionFee`, `_ImportDuty`, `_Tracking`, `_SignatureConfirmation`;
283
+ - `PostageRefund_Postage`, `_PostageAdjustment`, `_Insurance`;
284
+ - `ReturnPostageBilling_Postage`, `_Tracking`, `_FuelSurcharge`, `_OversizeSurcharge`, `_DeliveryAreaSurcharge`;
285
+ - `ReserveDebit`, `ReserveCredit`, `Other`.
286
+
287
+ The write-up says the `PostageBilling_*` events carry "no `AdjustmentItemList`, no `OrderId`, no `SellerSKU`" (https://github.com/kuzyvladimir-maker/ss-control-center/blob/main/docs/ADJUSTMENTS_DIAGNOSIS_REPORT_2026-05-22.md) [cv].
288
+ - A probe dated 2026-08 adds `MiscAdjustment` (https://github.com/gon0801/goncloud-Orbit, finances-probe-2026-09-08.json) [cv].
289
+ - Lingxing's OpenAPI doc on v0 lists `WAREHOUSE_LOST_MANUAL`, `FREE_REPLACEMENT_REFUND_ITEMS`, `REMOVAL_ORDER_LOST`, `INCORRECT_FEES_NON_ITEMIZED`, `Goodwill`, `RestockingFee`, `ReturnShipping`, `PostageRefund_Postage`, `FailedDisbursement` (https://github.com/zach22-1999/lingxing-mcp/blob/main/skills/zach-lingxing-openapi-client/references/openapi_docs/Finance_bdOrder.md).
290
+
291
+ **Finances v2024-06-19 `transactionType` seen.**
292
+ - `Shipment` (description "Order Payment") (issue #4245); `Refund`.
293
+ - `ServiceFee`, `ServiceFee - Correction`, `ServiceFee - Reversal`, and `MiscellaneousLedgerAdjustment` (description `FBAStorageFeeAdjustment`), from a CSV pulled from `/finances/2024-06-19/transactions` (https://github.com/tznamenacekhome/amazon-ebay-ops-system/…/fee_transactions.csv) [cv].
294
+ - `Retrocharge` (description `RetroChargeRefund`) (issue #4271).
295
+ - `FBAInventoryReimbursement` (issue #4993; on its breakdown tree, Amazon Developer Services replied it "does not appear to be documented as expected behavior") [official reply].
296
+ - `Adjustment` (items `PostageBilling_PostageAdjustment`); `Compensation` (description `COMPENSATED_CLAWBACK`); `Chargeback`; `Transfer`; `RemovalShipment`.
297
+ - No sample of `GuaranteeClaim` was found.
298
+ - For reimbursements the reason rides in `description` (e.g. "MISSING_FROM_INBOUND, Customer Return").
299
+
300
+ **Finances v2024-06-19 `breakdownType`.**
301
+ - Seen in payloads: `Sales` → `ProductCharges` → `OurPricePrincipal`; `Expenses` → `AmazonFees` → `Commission`, `Base`; `FBAPerUnitFulfillmentFee`; `Tax`; `Sales` → `FBAInventoryReimbursement`; `Sales` → `Other`.
302
+ - A curated map adds these refund leaves: `OurPriceDiscount`, `OurPriceTax`, `RefundCommission`, `RestockingDeductionPrincipal` / `Tax`, `ShippingPrincipal`, `ShippingChargeback`, `GiftwrapChargeback`, `Promo`, `PointsReclaimed`, `FBAReversedReimbursement`, `CustomerReturnHRRUnitFee`, `DebtPayment`, `FailedDisbursement` (https://github.com/5starsunited/neonpanel-mcp-server, `list_financial_transaction_services/register.ts`) [cv; curated, not each seen in a payload].
303
+
304
+ **`GET_FBA_REIMBURSEMENTS_DATA` `reason`.**
305
+ - A 413-row India report (2026-04-22 to 05-22) gives `CustomerReturn` 263, `CustomerServiceIssue` 129, `Damaged_Warehouse` 12, `ReturnAdjustment` 7, `Lost_Outbound` 1, `Damaged_Outbound` 1 (https://github.com/prabhakar-stack/wearhouse-testing/blob/main/scripts/test_templates/reimbursements_0_30.tsv) [cv].
306
+ - US/CA audit code adds `Lost_Warehouse`, `Lost_Inbound`, `Reimbursement_Reversal` (https://github.com/Amal-Eldesouky/Reimbersment).
307
+ - `Damaged_Inbound` appears in flipledger (https://github.com/moge111/flipledger).
308
+ - `original-reimbursement-type` on `Reimbursement_Reversal` rows has been seen as `Damaged_Warehouse`, `CustomerReturn`, `Lost_Inbound`.
309
+ - `condition` has been seen as `NewItem`.
310
+ - flipledger's code pairs the reimbursements report's `Reimbursement_Reversal` with the settlement's `COMPENSATED_CLAWBACK`.
311
+
312
+ **Ledger adjustment `Reason` codes** (as far as money needs). Reason Automation's ledger help (https://help.reasonautomation.com/seller/inventory-ledger-details) matches the Openbridge gist "Adjustment types and reason codes" (https://gist.github.com/tspicer/006f51f798b9803bf0b0ef3fc93b4266) [cv]. The wording looks like Amazon's help text but was not confirmed against Amazon.
313
+ - `6 / 7 / E / H / K / U` (−): "Damaged at Amazon fulfillment center", from different source dispositions, "always followed by a P code increase".
314
+ - `M`, `5` (−): misplaced, "missing from a bin location".
315
+ - `F` (+): "missing inventory has been found".
316
+ - `N` (+): found, "incorrectly assigned … transferred to your account or because you received an Amazon reimbursement".
317
+ - `O` (−): correction, "incorrectly received … or because Amazon has reimbursed you for them".
318
+ - `D` (−): disposed.
319
+ - `P / Q`: disposition change.
320
+ - `3 / 4`: product redefinition.
321
+ - Reconciliation outcomes for damaged and misplaced units include "Reimbursed" ("Inventory for which you have been reimbursed"), "Inventory found" and "Inspected and disposition corrected" (https://gist.github.com/tspicer/d62e47ef7fc24d62136936a5d48f1800).
322
+ - One audit tool matches ledger `M` to `Lost_Warehouse` and `E` / `H` to `Damaged_Warehouse` by FNSKU and currency. Its comment says there is "no event ID" linking the ledger row to the reimbursement row (https://github.com/Amal-Eldesouky/Reimbersment/blob/main/audit_fba.py).
323
+ - Gerpgo computes lost as `M − F − N` (§ Chinese ERPs).
324
+
325
+ **Seat reading** [seat]. Three vocabularies carry the same events:
326
+ - The reimbursements report `reason` is CamelCase with underscores (`Lost_Warehouse`, `Reimbursement_Reversal`).
327
+ - The settlement amount-description and v0 AdjustmentType are UPPER_SNAKE (`WAREHOUSE_LOST`, `REVERSAL_REIMBURSEMENT` / `COMPENSATED_CLAWBACK`).
328
+ - The ledger uses one-letter reasons (`M`, `E`, `F`).
329
+
330
+ No published crosswalk exists. Amazon names none, so a join by FNSKU, date and quantity is the practitioners' route.
331
+
332
+ **Watch.** Improvado states that the "flat file behind the Payment All Statements report" is removed on 2026-11-11, and Amainvoice that "since March 25, 2026, Amazon has exclusively provided the Flat File V2 format". Neither cites Amazon. Amazon's deprecations page gives 2026-11-11 for the old settlement flat file and XML (§ API) [opinion; official for the date].
333
+
334
+
335
+ ### English-language recovery services and tools
336
+
337
+ All [opinion], the vendor's own words, read 2026-11-09 (quotes checked against the downloaded page unless noted).
338
+
339
+ | Who | What it detects or files | Its figure for what sellers are owed | Fee and filing route | On Amazon's automation, valuation, windows |
340
+ |---|---|---|---|---|
341
+ | **GETIDA** (https://getida.com/, /pricing/; blog "Amazon Reimbursement Policy – Decoded…", "The Hidden Fees in FBA Refunds…", Shaan Yusuf, undated, images 2024-07) | "inbound shipment discrepancies, lost removal orders, Amazon fees charged incorrectly"; units "lost, damaged, disposed of, overcharged with fees"; survey adds FNSKU reconciliation, pick-and-pack overcharge, wrong-FNSKU returns | "small discrepancies can stack up to 1-3% of revenue lost yearly"; "an average of 63% of previously unsuccessful claims approved" | "performance-based pricing starting at 20%"; "Pay nothing for the first $400"; "dedicated case management team" | **"Amazon auto pays sellers on 98.5%* FBA Customer Return issues within 64 days. Getida has a default setup of waiting 90 days before filing"** (from "over 2 million Getida sample data points"); warns that some providers file on days 60–63 and charge a fee on money paid automatically on "day 64+". Its policy post still lists 18-month windows (stale). |
342
+ | **Seller Investigators** (https://www.sellerinvestigators.com/; "part of the Carbon6 ecosystem") | "Canceled Shipments", "Receiving discrepancy", "Lost in the warehouse", "Unfair reimbursement", "Disposed by Amazon", "Refunded orders (not returned within 60 days)", "Customer refunded more than paid", "Wrong item returned", "Chargeback not refunded", "Removal Orders", "Incorrect weights and dimensions", "Overcharged orders" | — | "only pay a 25% commission fee when your money is back with you" | Ownership: SPS Commerce bought Carbon6 (announced 2025-01-02) and on 2026-06-30 "completed the sale of its 3P Revenue Recovery business" for "a cash payment of $9.5 million", buyer not named (SPS press release, https://www.spscommerce.com/press/sps-commerce-announces-agreement-to-sell-3p-revenue-recovery-business/). On the Q2 2026 call (2026-07-30, Motley Fool transcript) the CEO gave as reason "the take rate revenue model and some of the policy changes in 3P we saw from Amazon"; "loss on sale of $23.5 million". A reviewer (Trevor Fenner, ecommerceparadise.com, "SPS Revenue Recovery Review 2026") writes "independent analysis has shown Amazon's auto-reimbursement leaves behind approximately 40% of eligible reimbursements" without naming the analysis. SPS's own article (Jacqueline Nance, updated 2026-06-15) gives US customer returns "60-120 days" and UK "45-105 days", which disagrees with Amazon's 2025-10-15 post. |
343
+ | **Helium 10** Managed Refund Service and Refund Genie (https://www.helium10.com/tools/operations/managed-refund-service/, /refund-genie/) | Inbound "lost en route to Amazon, damaged in transit with Amazon Partnered Carriers"; warehouse "wrongly disposed … misplaced … lost during removal orders"; "incorrect FNSKU returns"; Refund Genie "does not include Inbound FBA shipment discrepancies" | "We can recover up to 1% of your annual revenue" | Managed: "Diamond users … 15% … Platinum users … 18%", filed as "an official member of the exclusive Amazon Emerald Program"; Refund Genie: "Zero Commissions", the seller files "manually … within Amazon Seller Central" | Pages still promise to "audit your last 18 months" (stale). Blog (Josh VanAkker, 2024-07-24): "over 90% of reimbursement claims are currently made within 60 days". |
344
+ | **SELLERLOGIC Lost & Found** (https://www.sellerlogic.com/en/amazon-lost-and-found/; blog by Anastasiia Yashchenko, updated 2025-02-03) | "Inbound Shipments", "Inventory / Stock", "FBA Fees", "Missing Returns", "Lost in Warehouse", "SAFE-T" | "medium-sized enterprises using FBA risk losing 3% of their annually generated turnover" | "25% commission on refunds actually received"; files "directly in Seller Central on your behalf" | Product page still says "Amazon does not reimburse you proactively" (stale); blog: "removal claims or customer return mishandling still require manual claim submissions". |
345
+ | **sellerboard** (blog 2026-07-14, https://blog.sellerboard.com/2026/07/14/amazon-fba-reimbursements-what-youre-owed-and-why-most-sellers-never-collect-it/; blog 2025-01-20) | Report of candidates; the seller opens the case ("Fulfillment by Amazon > Inventory Damaged or Lost in Warehouse"); survey adds "cases where Amazon reimbursed less than your product's cost of goods sold" | "roughly 1–3% of an FBA seller's annual revenue" ("Industry audits", none cited) | Subscription; does not file | "Automatic reimbursement covers a subset of lost-in-warehouse cases; entire categories (unreturned refunds, fee overcharges, many damage cases) require the seller to detect the discrepancy and file"; sellers without uploaded sourcing costs are "frequently reimbursed less than they should be". |
346
+ | **Refund Retriever** (https://www.refundretriever.com/amazon-refunds; not re-checked by curl) | "Damaged Inventory", "Lost Inventory", "Returns Not Sent Back", "Incomplete Return Process", "Missing from inbound", "Disposed of inventory", "Empty product returns" | — | "30% of the refunds recovered"; "submitted manually" | Still cites "March 10, 2025" and a "9-month window for inbound". |
347
+ | **Nova Data** (news 2025-11-28, https://novadata.io/resources/news/amazon-reimbursement-policy-manufacturing-cost; SAFE-T news 2026-01-26) | "Nine reimbursement categories" | "Recover $1,500-$3,000 annually" | Tool | Valuation: "Sellers report 50-75% lower recovery amounts. The average recovery dropped from $18.50 to $6.20 per unit for typical products" (no method). SAFE-T: "shrinks from 60 days to 30 days for US seller-fulfilled orders", from the later of return delivery scan or refund date — matches Amazon's post. |
348
+ | **Refunds Manager** (https://www.refundsmanager.com/) | Now pitches Amazon 1P (vendor) and Walmart: "shortages, chargebacks, co-op fees, and invoice discrepancies" | "$1B+ Recovered for clients" | "the applicable rate and terms agreed before work begins" | Not an FBA seller service today. |
349
+ | **SellerSprite** (Content Team, 2026-10-23) and **My Amazon Guy** (Noah Wickham, 2025-10-31) | — | — | — | SellerSprite lists the 2025-10-15 windows as Amazon's post does. My Amazon Guy reports found-after-reimbursement units reversed and then charged disposal ("charged fees to dispose of the very items Amazon lost"; one seller "$1,100" on a reversal). |
350
+
351
+ **What they say automation misses, in sum** (each named above): removals (all, Amazon's own words, E2); missing-from-inbound (outside the IDR portal, E3); refunds larger than the charge; returned units of the wrong FNSKU or empty boxes; reimbursements below cost where no sourcing cost was entered; reversals with no matching found unit; fee and dimension overcharges; chargebacks not credited back. Their own figures for the size of the gap (1%, 1–3%, 3%, "40% left behind") cite no method; GETIDA's 98.5%-within-64-days is the only figure on what automation *does* pay, with a stated sample basis. **Stale-page signal:** several vendor pages still state 18-month audits, "no proactive reimbursement" or the 2025-03-10 date [opinion, the pages themselves; seat reading].
352
+
353
+ ### Chinese-language sources: Amazon's Chinese pages, ERPs, media
354
+
355
+ Read 2026-11-09 by plain GET. Seller Central's Chinese help pages are JS shells as well.
356
+
357
+ **Amazon's own Chinese pages** (gs.amazon.cn, 亚马逊全球开店) [official]:
358
+ - 《你最关心的亚马逊库存管理问题,这次全解决!》, https://gs.amazon.cn/zhishi/article-250305-3 (2025-03).
359
+ - Inbound claims: "运营中心后的9个月内提交索赔。逾期提交的索赔将无法获得赔偿" (file within 9 months of arrival at the fulfilment centre; late claims are not paid).
360
+ - The IDR portal covers "库房丢失…库房残损…买家退货缺陷" (warehouse lost, warehouse damaged, customer-return defects).
361
+ - It shows three statuses: "符合赔偿要求:可提交索赔申请" (eligible, file a claim), "已解决" (resolved) and "处理中(审核中)…您无需操作" (in review, no action needed).
362
+ - It does not mention manufacturing cost.
363
+ - https://gs.amazon.cn/zhishi/article-250807-3 (2025-08): "必须在货件送达亚马逊运营中心的确切日期后最迟九个月内(美国站)提交索赔" (US: no later than nine months after delivery to the FC).
364
+ - FBA FAQ, https://gs.amazon.cn/north-america/fba/faq (undated):
365
+ - On a $0 replacement order: "关于原订单中的退件商品,买家需要在45天内退回到仓库,如果买家退回的换货商品没有按时退回库房,亚马逊则会按照相关赔偿政策对卖家的损失进行赔偿" (the original unit of a replacement must reach the warehouse within 45 days; if not, Amazon reimburses under its policy). This is about replacements, not refunds.
366
+ - "Warehouse Damaged商品无法创建移除订单,仓库会自动赔偿并移除数量" (warehouse-damaged units cannot be removed; they are reimbursed automatically and written off).
367
+ - https://gs.amazon.cn/news/news-notices-260112: from 2026-03-31 commingling ends, and "未正确贴标签的库存可能难以准确追踪,且不符合赔偿资格" (incorrectly labelled stock may be untraceable and not eligible for reimbursement). This is a dated change.
368
+ - https://gs.amazon.cn/zhishi/article-260604-2 (2026-06): "退款管理费…通常是原销售佣金的20%…在官方'退款管理费'政策中有明确说明" (refund administration fee "usually 20% of the original referral fee"). It states no cap.
369
+ - https://gs.amazon.cn/news/news-notices-240907 (2024-09-07), FBA returnless option:
370
+ - "卖家仍可收到销售佣金退款(减去管理费用)" (the referral fee still comes back, minus the administration fee).
371
+ - With returns evaluation disabled: "所有退货商品都将被标记为存在瑕疵,如果退货商品残损,则不符合赔偿要求" (all returns are marked defective, and damaged ones are not eligible).
372
+ - https://gs.amazon.cn/news/news-notices-210818 (2021-08-18), the old baseline: "您需要在收到退货后的2个工作日内发放退款。如果您未处理退款,亚马逊将代您为买家退款并从您的卖家账户扣除" (refund within two business days of receiving the return, or Amazon refunds the buyer and debits you). The 2026-01-26 change replaced it (A5).
373
+ - None of Amazon's Chinese pages found states the sourcing-cost valuation, the 2025-03-31 date, automatic reimbursement, the 2025-10-15 windows, SAFE-T's 30 days or the 4-day refund window. Chinese sellers meet these through the media.
374
+
375
+ **Chinese ERPs** [opinion, the vendors' own help docs]. None found files claims. Each estimates what is owed, gives a case template, and watches the Reimbursements report for the Case ID the seller enters.
376
+
377
+ | ERP | What it finds | How it values or books | Notes |
378
+ |---|---|---|---|
379
+ | **领星 Lingxing** (lingxing.com/help/article/FeeDiagnosis, FBAFeeDifference, Formulacheck, ProfitStatementnew1, finance) | Inbound shortfall ("货件签收的数量与发货数量有差异可提交索赔", received ≠ shipped can be claimed); FBA fee overcharge on wrong dimensions | "预计赔偿金额:= (实收FBA费-应收费用) x 该笔订单的购买数量" (expected = (fee charged − correct fee) × quantity), matched to Fee Adjustment rows. Profit line "9.FBA库存赔偿" (FBA inventory reimbursement) sums Adjustment descriptions incl. MISSING_FROM_INBOUND, WAREHOUSE_LOST, WAREHOUSE_DAMAGE, INCORRECT_FEES_ITEMS, CS_ERROR_ITEMS and REVERSAL_REIMBURSEMENT, so reversals net in the same line. "11.其他收入" (other income) holds A-to-z (GuaranteeClaim) and Safe-T. The referral-fee refund sits under "平台费退款额" (platform-fee refund), already net of the administration fee. Inventory "FBA盘盈亏" (FBA stock gain/loss) includes "亚马逊确认赔偿的数量" (units Amazon confirmed reimbursed). "货损一键入账" (book losses in one click) | Seller enters the Case ID; "每个case只能申请一个SKU,每天最多申请10个SKU" (one SKU per case, 10 SKUs a day); estimates "仅供参考" (for reference only). Its 2022 article still says 18 months. |
380
+ | **积加 Gerpgo** (help.jijiaerp.com docs/YzJZNk2y, 2026-08-25; NHwqDZVD, 2025-03-10; wDcMvo8B, 2026-04-09) | 索赔助手 (claim assistant): warehouse damaged and lost only | "预计赔偿金额 = 预计赔偿数量 * 最近一次赔偿单价(如果最近无赔偿单价,则取0)" (expected = units × the most recent reimbursed unit price, or 0). Lost = ledger reason M − F − N; damaged = reason E; already paid = Lost_/Damaged_Warehouse − Reimbursement_Reversal. Profit: "赔偿=赔偿收入+赔偿调整" (reimbursement = income + adjustments); "盘库采购成本 和 盘库头程成本" (purchase cost and first-leg freight of the adjusted units) are booked as cost, so the reimbursement offsets the loss | Ledger "前2个月…- 46天前" (from two months back to 46 days ago), daily at 04:00. A claim with no Case ID in the report after "10个自然日" (10 calendar days) is marked failed. Pitch: third parties charge "高达25%的佣金" (up to 25% commission). |
381
+ | **赛狐 Sellfox** (sellfox.com/help/features/fba-shipping-cost-difference) | FBA fee differences only | "实收FBA费-应收FBA费" (fee charged − correct fee); the "是否赔偿" (reimbursed or not) status is read from Amazon | A 2026-08-13 blog maps SAFE-T claims to MSKU in its profit report. |
382
+ | **易仓 ECCANG** (eccang.com/amazon.html; news/3687 2025-01-17; news/2855 2023-09-05) | "FBA库内丢失货损索赔面板" (in-warehouse lost/damaged claims panel), with templates, "无需额外分佣" (no extra commission); "买家退货未退款" (refunded but not returned) | Warehouse: "取60天内至15天前的盘库报告" (adjustments from 60 to 15 days ago). Returns: "取120天内~60天前的退款" (refunds from 120 to 60 days ago). Profit splits reimbursement into "客户相关赔偿、仓库赔偿、仓库其他赔偿、其他调整收入" (customer-related, warehouse, other warehouse, other adjustment income), each with a "是否参与利润计算" (counts toward profit or not) switch | A 2025-02-07 marketing piece claims round-the-clock batch filing, which its docs do not show. |
383
+ | **店小秘 Dianxiaomi / UpSeller** (upseller.com help-doc-article-2840, 2026-08-27) | — | Profit "FBA相关收入:FBA补贴、丢货赔偿款等" (FBA income: subsidies, lost-unit reimbursements) plus "其他收入" (other income) | No claims module found. |
384
+ | **优麦云 SellerSpace** (2024-06-05) | "库存损坏丢失索赔、货件丢失索赔和退货索赔" (warehouse, inbound, returns claims) | Data "授权前18个月到1个月前" (from 18 months to 1 month before authorisation) | "每个Case只申诉一个FNSKU…每天…不超过10个" (one FNSKU per case, ten a day). A claim with no result in 30 days lapses. |
385
+ | 马帮, 通途 | Not reachable (JS page) / not found | — | — |
386
+
387
+ No Chinese fee-based claims service with a current public price was found. 亿数通 (selmuch.com/518) dates from 2020. SellerHow (2026-08-16), in Chinese, says of Western services "25% 是这个品类的公价" (25% is the going rate). It notes that one service credits back its commission if Amazon reverses the reimbursement, while another contract is silent on it.
388
+
389
+ **Chinese media and forums** [opinion]:
390
+ - 雨果网, Lily-亚马逊 (cifnews.com/article/169411, 2024-12-25): "卖家一面倒的反对" (sellers are uniformly against it); "有些丢件,迟迟见不到亚马逊的所谓'自动赔偿',搞来搞去还是要自己提交申请" (some lost units never get the so-called automatic reimbursement, and you file anyway).
391
+ - 雨果网 from 五爷跨境圈 (cifnews.com/article/172804, 2025-03-31): the rule is "2025年3月31日起正式实施" (in force from 2025-03-31); "部分卖家因成本估算差异导致索赔被拒" (some claims are refused over cost-estimate gaps). This is the only Chinese source found with the delayed date. The others give 2025-03-10.
392
+ - AMZ123 跨境小蚂蚁 (amz123.com/t/LFOykLna, 2025-01-19) and 卖家之家 (m.mjzj.com/article/eawxbluj5am8, 2025-01-24), on the 2025-01-16 US notice: customer returns "由原来的60-120天,缩短至 45-105天" (from 60–120 to 45–105 days); FC 60 days; removal lost 15–75 days; other removals 60 days.
393
+ - 卖家之家 (m.mjzj.com/article/e85s4z0sjy80, 2024-12-27): manufacturing cost "不涵盖产品的运费、处理费、关税" (excludes freight, handling, duties), set on the "管理制造成本" (manage manufacturing cost) page.
394
+ - 亿恩网 (m.ennews.com/article-30129-1.html, ≈2024-12): automatic reimbursement "自2025年1月15日起" (from 2025-01-15). It quotes a seller: "亚马逊只报销制造成本,就是正大光明地让卖家为自己的错误买单" (paying only manufacturing cost openly makes sellers pay for Amazon's own mistakes).
395
+ - AMZ123 编辑 (amz123.com/ask/1RKMP8FS, 2025-06-14): automatic reimbursement "从2024年11月1日起" (from 2024-11-01); window "从原来的180天…缩减至…60天" (from 180 days to 60). The piece also says 18 months, so it contradicts itself.
396
+ - AMZ123 Summer (amz123.com/t/PPsYn6Sx, 2026-01-22): the SAFE-T window drops from 60 to 30 days on 2026-02-16, which matches Amazon's post.
397
+ - AMZ123 枫筝海外仓 (amz123.com/t/UP9ehtUA, 2026-02-12): the 4-calendar-day refund window from 2026-01-26. SAFE-T stays available for "扫码即退款" (refund at first scan) orders, returns lost in transit, refunds made within 4 days, and carrier delivery errors.
398
+ - AMZ123 老虎站外推广 (amz123.com/t/tg6kPptK, 2026-11-02): "一件售价50美元、采购成本12美元的产品…现在赔的是12美元。有卖家报告,赔偿金额平均下降了50%到75%" (a $50 item costing $12 is now reimbursed $12; sellers report 50–75% less); "入仓短装、退货未回库、移除丢失、费用多扣这几类,自动赔付基本不覆盖" (inbound shortages, unreturned returns, lost removals and fee overcharges are basically not auto-paid); "不维护成本数据,赔得更少" (no cost data, less paid).
399
+ - AMZ123 速推站外 (amz123.com/t/lzje26Gk, 2026-11-02): a repeat cost dispute within 30 days of a decision "平台可能不再接受" (may not be accepted); "不要把网上流传的近60天差额追回说法理解为所有卖家都拥有统一的60天补偿权利" (the "60-day top-up" story is not a universal right).
400
+ - 知无不言 十一郎与流氓 (wearesellers.com/question/101140, 2025-01/04): inbound loss "按照历史销售价的平均值来进行赔偿,但是如果后面货找到的话,还会扣除" (paid at the average historical price, and taken back if found); customer returns are "一般是亚马逊自动赔偿的,但是我们仍然需要去进行核对" (usually auto-paid, but still to be checked).
401
+ - 知无不言 Y13803977312 (wearesellers.com/question/126229, ≈2026-11-04): a damaged unit was reimbursed "11.83美金" ($11.83) before appeal; "亚马逊要的是可被证明的采购/生产成本…需要和发票保持一致" (Amazon wants a provable purchase or production cost that matches the invoice).
402
+
403
+ **What the Chinese sources change in this file** [seat reading]:
404
+ - Amazon's own Chinese pages (2025-03, 2025-08) still say nine months for inbound claims. This agrees with the ≈2026-08 staff post (F) and is a third Amazon statement on that window.
405
+ - The FAQ's 45 days concerns the original unit of a replacement order, not a refunded unit; it neither confirms nor contradicts the relayed 45-day refund text (E1) or the staff post's 60 (corrected by the verifier, 2026-11-10).
406
+ - The ERPs' profit treatment differs by vendor:
407
+ - Lingxing nets reversals inside one reimbursement line.
408
+ - Gerpgo books the reimbursed units' purchase and freight cost against the reimbursement.
409
+ - ECCANG lets the seller switch each reimbursement kind in or out of profit.
410
+
411
+ These are three accounting choices. Which one applies is the seller's choice.
412
+
413
+ ### Value-recovery SKUs and lines (gap fill, 2026-11-10)
414
+
415
+ All [opinion] unless marked; read 2026-11-10. **[cv]** = a grep over a public file downloaded today.
416
+
417
+ **The amzn.gr SKU as practitioners see it.**
418
+ - Shape: `amzn.gr.<seller SKU>-<random key>-<two-character code>`. Seen values: `amzn.gr.TW-BLU-BTH-4-iTlG9GVkiK8EKmva-LN`, `amzn.gr.LUX-PK2-TWL-TEL-qyCObLH5LN9JG-VG`, `amzn.gr.BTH-SHT-WHT-600-u72fnT-Qj6l-r-LN` (a US seller's live data, 2026-08; https://github.com/farhankauser-web/Daily-Sales-Dashboard, `docs/PHASE2_FBA_COMPONENTS_VALIDATION.md` § K1) [cv]; `amzn.gr.A5-BOOK-COVER-DESIGN-5-QaQJXV-PO` (a French store, https://github.com/icingerpower/AmzBooks, `AmzBooksLib/inventory/InventoryMoveTree.cpp`) [cv]. A German DATEV exporter matches `^amzn\.gr\.(.+)-([A-Za-z0-9]{10,20})-([A-Z0-9]{2})$` (https://github.com/donchrillo/jtl2datev, `core/verbringung_pricing.py`) [cv]. The ecomEngine guide (Jeanne Croteau, updated 2026-01-12, https://www.ecomengine.com/blog/fba-grade-resell) says the SKU is "based on the graded condition and type of defect". That `LN` / `VG` stand for Like New / Very Good is [seat]; Amazon publishes no code list.
419
+ - The join is fragile: AmzBooks strips the prefix and the last two dash parts to find the seller SKU, and falls back to a manual table for "~20 % of cases where Amazon shortened the SKU" [cv]. jtl2datev tries stems with one to three trailing segments removed, then the ASIN [cv].
420
+ - Where they show: a US seller saw amzn.gr MSKUs in Data Kiosk `economics` with `BaseFbaFulfilmentFee` and `FuelSurcharge` components (July 2026: 220 of 3,057 fee charges; about $2,062 of $303,803.40) [cv]. The same project books Date Range transaction rows whose description contains "grade and resell" as other income in one importer and as a logistics cost in another (`unified_txn_importer.py`, `finances_importer.py`) [cv]; the literal row text is not in the repository. A Spanish ledger tool separates "Unidades Grade & Resell (seller SKU "amzn.gr.…" o condición distinta de nuevo)" from sellable stock (https://github.com/jenfol92/AWS_businessIntelligense_Ia, `ledgerCountryStock.ts`) [cv]. A seller asked in Amazon's Ask Amazon thread about other system SKUs, "SKU's named Amazon.Found and some numbers" (78c455ed, 2024-11-21).
421
+ - No public settlement file, A2X or Link My Books page, or Chinese ERP help page on amzn.gr SKUs was found (searched 2026-11-10).
422
+
423
+ **How tools book a graded resale (cost of the unit).**
424
+ - sellerboard ("Handling Amazon Grade & Resell SKUs Correctly in Profit Analytics", 2026-01-22, https://blog.sellerboard.com/?p=3309): "COGS is deducted when the original (new) SKU is sold"; "The returned item does not return to sellable inventory, so its cost is not added back"; "If the graded item is sold and COGS is deducted again, the same physical unit is counted twice". It detects Grade & Resell SKUs automatically, shows the original SKU's COGS "for transparency", and "That COGS is excluded from profit calculations when the graded item is sold"; manual COGS on these SKUs "does not affect profit calculations".
425
+ - ConnectBooks ("How to Map Grade & Resell Items in Amazon", https://help.connectbooks.com/en/articles/13763093-how-to-map-grade-resell-items-in-amazon): map every Grade & Resell SKU to a non-inventory item "Grade & Resell", or "enter $0 as the Item Cost"; "Amazon fees still apply. Only the product cost is left out."
426
+ - jtl2datev (German DATEV export of intra-EU movements): values unmatched graded units ("B-Ware") at 10% of the purchase cost of the matched stem, floor €0.01, or a flat €0.10 [cv].
427
+ - Daily-Sales-Dashboard: excludes every `amzn.` MSKU from fee-impact analysis ("a DIFFERENT ECONOMIC EVENT from new-unit fulfilment") [cv].
428
+ - [seat] These differ on one point: whether the unit's cost was already written off (refund with an unsellable return, sellerboard and ConnectBooks) or is still carried (a returned unit put back as inventory, then regraded). Which holds depends on how the seller booked the return; it is the seller's choice.
429
+
430
+ **Fees and recovery, vendors' figures.** Seller Labs (2025-05-21, https://www.sellerlabs.com/blog/fba-grade-and-resell-strategy-2025/) prints a US processing fee table by size tier, charged "Only when items are successfully relisted", "no fee if the item is unsellable"; figures under Facts for human readers only. Synder's glossary: the fee is charged "for each unit that's successfully graded and relisted" and "covers Amazon's cost of inspecting, repackaging, and relisting the item" (https://synder.com/fees-amazon/grade-and-resell-fees/). SPS Commerce (Jacqueline Nance, updated 2026-08-07): "Sellers receive proceeds from the resale, less applicable program fees"; "Exact fee structures should be double-checked in Seller Central". ecomEngine: graded-SKU feedback shows on Voice of the Customer "by looking for the amzn.gr prefix".
431
+
432
+ **Seller reports.** "My experience with 'Grade and Resell' is that products end up returned as 'Unsellable', even if they are 100% new" (3fa4fa3c); "most of the grade and resell products were returned as defective" (ef44a47a).
433
+
434
+ **Chinese.** AMZ123 (2025-11-19, https://www.amz123.com/kx/L2cgS471): "亚马逊分级与转售"(Amazon Grade and Resell) has expanded from the US to the UK, Germany, France, Italy, Spain and Japan; sellers get "原价30%-80%的回收款" (30–80% of the original price); "预计可为卖家挽回20%-50%的退货成本" (expected to recover 20–50% of return cost); "部分卖家反馈该服务的定价偏低且流程较为耗时" (some sellers say pricing is low and the process slow). No source is named for the figures. No Lingxing, Gerpgo, Sellfox or ECCANG help page on amzn.gr SKU pairing was found.
435
+
436
+
437
+ ## Published research
438
+
439
+ None found on reimbursement accuracy or refund money. No independent study, journal article or audit of Amazon's FBA reimbursement accuracy was found; every "share of revenue owed" figure above is a vendor's, without method. No US court case on FBA reimbursement underpayment or on the refund administration fee was found. Adjacent cases, not about reimbursement accuracy (details from search results, documents not opened): *FTC v. Amazon.com, Inc.*, W.D. Wash. No. 2:23-cv-01495 (antitrust, includes fees); *In re Amazon Return Policy Litigation*, W.D. Wash. No. 2:23-cv-01372 (consumer refunds, reported settlement ≈$309M); the UK sellers' collective action at the Competition Appeal Tribunal (fees, self-preferencing) [research, unread]. The listing playbook's returns angle lists two return-behaviour papers (Cheng, Krikon, Murdock, CHIIR 2024; Turlo, Kessing, EMAC 2025); neither touches refund money.
440
+
441
+ ## Stable enough for a skill
442
+
443
+ 1. A customer refund is not the mirror of the sale: the charge lines (principal, tax, shipping, gift wrap, promotions, points) are reversed per `ItemChargeAdjustmentList` / `PromotionAdjustmentList`; the referral fee comes back less a refund administration fee; the FBA fulfilment fee is not returned [official model and fee schedule; fulfilment-fee point is practitioner, see Open questions].
444
+ 2. The refund administration fee is per line item, capped per store in local currency, and a partial refund returns a proportional referral fee (UK relayed help text; US fee schedule) — the cap and rate are read at run time.
445
+ 3. Refunds, guarantee claims and chargebacks share one item shape in Finances v0 and carry an `OrderAdjustmentItemId`; in v2024-06-19 they carry `ORDER_ID` / `REFUND_ID` related identifiers and an `ORDER_ADJUSTMENT_ITEM_ID` item identifier, so each joins back to its order and order item [official model].
446
+ 4. Listing transactions by `ORDER_ID` finds refunds, chargebacks and adjustments that post "days, weeks, or even months later" [official guide].
447
+ 5. Who triggers a refund on a seller-fulfilled order: the seller, refund at first scan (APRL), a seller's returnless rule, Amazon's automated refund after the deadline, A-to-z, chargeback, customer service [official, sell.amazon.com].
448
+ 6. A-to-z: an assigned claim refunds the buyer and debits the seller or cancels a future payment; an unanswered request for information grants it; a granted claim can be appealed; an order with an A-to-z claim is not SAFE-T-eligible [official, snippets]. The response time and the appeal window are read at run time.
449
+ 7. Chargebacks: Amazon carries fraud-related ones; the seller carries service-related ones; the bank decides [official]. The reply window and how long the outcome can take are read at run time.
450
+ 8. SAFE-T is the seller-fulfilled route to recover a refund the seller did not cause; its window (read at run time) and its exclusions are dated facts; an automated refund after the seller's deadline forfeits it except lost-in-transit or wrong delivery confirmation [official].
451
+ 9. FBA reimbursements cover warehouse lost, warehouse damaged, missing from inbound, removals lost or damaged, and customer returns not returned or returned unsellable through Amazon's fault; customer-damaged returns are not reimbursed [official].
452
+ 10. Most warehouse-lost/damaged and customer-return cases are reimbursed without a claim; removals always need a manual claim; the IDR portal excludes missing-from-inbound, removals and disposals [official].
453
+ 11. Value: losses before a customer order are paid at the seller's sourcing cost (Amazon's estimate unless the seller entered one), excluding shipping, handling, duties; losses after a customer order at the order's sale price minus fees; unsellable units at "a reduced estimated cost"; effective 2025-03-31 [official].
454
+ 12. A reimbursement can be cash or a unit put back; a reversal points to the original by `original-reimbursement-id/-type`; Amazon reverses when the payment was wrong or the unit is found [official columns and relayed help text].
455
+ 13. The claim windows are dated facts with three Amazon statements that disagree (F); a skill states each with its date and source and does not pick one.
456
+ 14. Several identifiers chain a reimbursement to its cause: `amazon-order-id` (customer-return cases), `case-id` (manual claims), `fnsku` (inventory), `reimbursement-id` ↔ `original-reimbursement-id` (reversals); the ledger's `Reference ID` names the inventory event [official columns; the chain is seat].
457
+ 15. Returnless and partial refunds are seller-funded refunds with no unit back and no reimbursement; they count toward the return rate; FBA Returnless Resolutions has no downloadable report; partial refunds show in the FBA Returns dashboard as "Complete – Return not expected" [official].
458
+ 16. Seller-fulfilled return labels bought through Amazon are charged to the seller when the return reason is the seller's (`PostageBilling` / `PostageRefund` in Finances; `label_cost`, `label_to_be_paid_by` in the returns report) [official].
459
+ 17. Data Kiosk economics counts refunds "by refund request time" and its `netProceeds` has no reimbursement term; the settlement and Finances count by posting date; seller analytics returns by ship date; the FBA returns report by FC processing date [official schemas and pages].
460
+ 18. The Finances v0 `AdjustmentType` list in the model has eight values; sellers see more in responses and settlement files; read the value, do not assume the list is closed [official model; practitioners].
461
+ 19. No API issues a refund, files a claim, answers an A-to-z/chargeback/SAFE-T case, sets returnless or partial-refund rules, or enters sourcing cost [command-verified].
462
+ 20. A returned unit that is neither restocked nor reimbursed can still bring money back as a Grade and Resell sale. That sale is an ordinary order of the seller's under an Amazon-generated SKU beginning `amzn.gr`, under the same parent ASIN, with referral, fulfilment and (where charged) processing fees [official, J1].
463
+ 21. An amzn.gr SKU joins back to the seller's own SKU only through its string and the parent ASIN; Amazon gives no linking field [official prefix and parent ASIN; practitioners for the string shape].
464
+ 22. A donated unit costs the usual disposal fee and brings no proceeds; the yearly donation certificate lists quantities and descriptions, not values [official].
465
+ 23. A unit sold through Amazon Resale is Amazon's, after a reimbursement; the seller's money on it is the reimbursement [official policy text; the money reading is seat].
466
+
467
+ ## What cx must read at run time
468
+
469
+ | Figure or state | Where |
470
+ |---|---|
471
+ | Refund administration fee rate and cap for the store | Fee schedule (G200336920 and store copies) — read the page; the refund's own `ItemFeeAdjustmentList` shows what was retained |
472
+ | Which refunds, claims, chargebacks, reimbursements posted, with amounts | `listTransactions` (by `ORDER_ID`, `FINANCIAL_EVENT_GROUP_ID`, date range ≤180 days); v0 `listFinancialEvents*` until 2027-08-27; settlement V2 file |
473
+ | The actual `transactionType`, `description`, `breakdownType`, `AdjustmentType`, `amount-description` values on this account | The responses and files themselves (open lists) |
474
+ | Reimbursements paid, reason, cash vs inventory, reversals | `GET_FBA_REIMBURSEMENTS_DATA` (Pricing role suffices) |
475
+ | Returns received at FBA and their disposition | `GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA` |
476
+ | Replacements | `GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_REPLACEMENT_DATA` (Amazon Fulfillment; NA, IN) |
477
+ | Lost/found/damaged events and unreconciled quantity | Ledger detail with `eventType=Adjustments` (Amazon Fulfillment) |
478
+ | Seller-fulfilled returns, label cost and payer, SAFE-T state | Returns-by-return-date reports (IOT/DtC — not door) or Prime returns (Pricing) |
479
+ | Current claim windows and whether they changed again | Seller Forums News and the policy page (G200213130) as the seller sees it |
480
+ | A-to-z response time and appeal window (moved from Stable 6; as read: 72 hours, 30 calendar days, US snippets, 2026-11-09) | A-to-z Guarantee claims (G27951), https://sellercentral.amazon.com/gp/help/external/G27951; Appeal an A-to-z Guarantee claim (G202041210), https://sellercentral.amazon.com/help/hub/reference/external/G202041210 — as the seller's own store shows them; no operation |
481
+ | Chargeback reply window and outcome time (moved from Stable 7; as read: seven calendar days, 90 days or longer, sell.amazon.com US, 2026-11-09) | "How to manage Amazon chargebacks", https://sell.amazon.com/blog/chargebacks; no operation |
482
+ | SAFE-T filing window and how it is counted (moved from Stable 8; as read: US 30 days from 2026-02-16, from the later of the return delivery scan and the refund date, last scan for a lost shipment, 2026-11-09) | Reimbursement for seller-fulfilled orders (G202188810), https://sellercentral.amazon.com/gp/help/external/G202188810, as the seller's own store shows it; News "US SAFE-T claim filing window changes to 30 days on Feb 16" (d95b0e44); no operation |
483
+ | The seller's sourcing cost per SKU as Amazon holds it | Only Seller Central (Manage Your Sourcing Cost); the seller's own COGS file is the seller's |
484
+ | Refund rate and claim amounts per ASIN | Data Kiosk Sales and Traffic (Brand Analytics) |
485
+ | Reserve held for refunds and claims | `listBalances` `ACCOUNT_LEVEL_RESERVE`; v0 `ReserveEvent` |
486
+ | Case status for a claim | Support API (restricted role, not held) or the seller's case log |
487
+ | Grade and Resell sales and their fees | Finances / settlement rows whose SKU begins `amzn.gr`; `getOrderItems` `ConditionId` / `ConditionSubtypeId`; the fee's label is read from the rows (open question 16) |
488
+ | Whether the seller is enrolled in Grade and Resell, Donations or Liquidations, and the discount per condition | Only Seller Central (FBA settings → Automated unfulfillable settings; Grade and Resell price settings) |
489
+ | Units submitted, graded, donated or disposed | `GET_FBA_FULFILLMENT_REMOVAL_ORDER_DETAIL_DATA` (Pricing role suffices) |
490
+ | The current Grade and Resell processing fee per store | The store's Grade and Resell help page and fee pages, as the seller sees them |
491
+
492
+ ## What only Seller Central shows
493
+
494
+ - **Filing**: the claim tools named by Amazon staff — "Check warehouse damaged reimbursement status", "Check FBA order reimbursement status", "Resolve a removal order issue", the shipment "Reconcile" tab, and Help → Get Support cases (E1); SAFE-T claim filing; A-to-z responses and appeals; chargeback representment ("Performance > Chargeback Claims"). No API files any of these.
495
+ - **The IDR portal** (defect status, actions taken, resolution rationale) and **Manage Your Sourcing Cost** (Amazon's estimate and the seller's entered cost). No API reads or writes either [command-verified, no operation].
496
+ - **Manage FBA Returns / FBA Returns dashboard** (refund date, unit received date, "Complete – Return not expected"), **FBA returns evaluation & ownership settings** (returnless by price, category, reason; partial refund percentage; returns evaluation on/off), **Manage Returns** for seller-fulfilled orders (authorise, refund with Guided Refund workflow and restocking fee). Only the reports in § API carry parts of this.
497
+ - **The case log** (Case Log). The Support API v2025-02-01 reads cases, status and contacts behind Selling Partner Support (Restricted), which the door does not hold; it creates nothing. Amazon's own Claude plugin skill `support-case-helper` creates no case: "By default this skill calls no SP-API tools" and it points the seller to the Help Center (`amazon-plugin-zip/skills/support-case-helper/SKILL.md`, read 2026-11-09).
498
+ - **The policy pages** themselves (G200213130 reimbursement policy; GMGJASYYNYLXKLXE reimbursement types; G200732720 Reimbursements report; G202188810 SAFE-T; G27951 A-to-z) render only in a browser.
499
+ - **The Payments Transaction view** filters (Refund, Chargeback Refund, A-to-z Guarantee Refund), 24 months.
500
+ - **Value recovery** (gap fill, 2026-11-10): the Automated unfulfillable settings (Grade and Resell, Liquidations, Dispose/Donate), the Grade and Resell price settings and ASIN inclusion list, the Donations page with its yearly certificate, and the Recovery tab of Returns and Recovery Insights. No API reads any of them [command-verified, no operation]; the Removal Order Detail report and the order and finance rows carry the outcomes (§ J).
501
+
502
+ What a later claims plugin would add (the seat's reading of the gap, not a plan): the joins that find what is owed (refunds without a return or reimbursement past the window opening; ledger lost/damaged units without a reimbursement; inbound shortfalls on closed shipments; removals shipped but not received; reversals without a found unit; reimbursements below the seller's cost), the window clock per case type with its dated source, the evidence a form asks for, and the hand-off to the seller to file in Seller Central [seat].
503
+
504
+ ## Facts for human readers only
505
+
506
+ Dated figures; a skill never states them, cx reads them at run time.
507
+ - Refund administration fee: US "lesser of $5.00 or 20% of the applicable referral fee" (G200336920 v119, 2026-10-14); UK 20% of order-related fees up to £5 per line item (relayed, 2026-11-09); UAE cap AED 15 (relayed).
508
+ - Claim windows (F table) as of 2025-10-15 and the staff restatement ≈2026-08; SAFE-T US 30 days from 2026-02-16; FBM refund deadline 4 calendar days from 2026-01-26; APRL refund cycle "from 14 to 7 days" (2026-02-08).
509
+ - FBA Returnless Resolutions price band $1.00–$75.00 (US, ≈2025-11); non-US seller-fulfilled returnless refund under $25 (sell.amazon.com 2025-04-15).
510
+ - Vendor fees: GETIDA from 20%; Seller Investigators 25%; Helium 10 Managed 15%/18%; SELLERLOGIC 25%; Refund Retriever 30% (all read 2026-11-09).
511
+ - Vendor claims of value lost: 1% (Helium 10), 1–3% (GETIDA, sellerboard), 3% (SELLERLOGIC), "approximately 40%" left by automation (ecommerceparadise), recoveries "50-75% lower" after the valuation change and "$18.50 to $6.20 per unit" (Nova); GETIDA "98.5%" of customer-return issues paid within 64 days.
512
+ - Grade and Resell (gap fill, 2026-11-10): US processing fee by size tier, charged only on relisting, $1.50 small standard (≤16 oz), $1.80 large standard (≤21 lb), $2.65 small/medium oversize (≤151 lb), $4.10 large/special oversize (Seller Labs, 2025-05-21; no Amazon page read gives these). EU: no programme fees, 60 days' notice before any (News, 2025-02-24). UK 2021: fees waived to 2021-12-31, minimum ASP £15 (relayed help copy). "Up to 80%" of product value (Amazon EU, 2025-02-24); "30%-80%" of the original price and "20%-50%" of return cost (AMZ123, 2025-11-19, unsourced). ASIN inclusion up to 2,000 ASINs (2026-02-03). Example discounts in the 2021 UK help copy: Like New 95%, Very Good 90%, Good 85%, Acceptable 80% of the new price (the seller sets these).
513
+ - One US seller, July 2026: amzn.gr MSKUs carried about $2,062 of $303,803 in FBA fulfilment-fee charges (Daily-Sales-Dashboard). A fact about that seller only.
514
+
515
+ ## Pages read
516
+
517
+ | Title | URL | Date read | Tag |
518
+ |---|---|---|---|
519
+ | Finances v0 model | local `models/finances-api-model/financesV0.json` | 2026-11-09 | official, command-verified |
520
+ | Finances v2024-06-19 model | local `models/finances-api-model/finances_2024-06-19.json` | 2026-11-09 | official, command-verified |
521
+ | Support API v2025-02-01 model | local `models/support-api-model/support_2025-02-01.json` | 2026-11-09 | official, command-verified |
522
+ | Data Kiosk schemas (economics, salesAndTraffic, sellerAnalytics) | local `schemas/data-kiosk/` | 2026-11-09 | official, command-verified |
523
+ | TransactionUpdateNotification schema | local `schemas/notifications/` | 2026-11-09 | official |
524
+ | Role Mappings for SP-API Operations / Types | local `web01/role-mappings.md` (2026-10-28), `role-mappings-for-types.md` (2026-09-09) | 2026-11-09 | official |
525
+ | SP-API release notes; deprecations | local `web01/sp-api-release-notes.md`, `sp-api-deprecations.md` | 2026-11-09 | official |
526
+ | Fulfillment by Amazon (FBA) Reports | https://developer-docs.amazon/sp-api/docs/report-type-values-fba.md (updatedAt 2026-10-13) | 2026-11-09 | official |
527
+ | Settlement Reports | https://developer-docs.amazon/sp-api/docs/report-type-values-settlement.md (2026-10-14) | 2026-11-09 | official |
528
+ | Returns Reports | https://developer-docs.amazon/sp-api/docs/report-type-values-returns.md (2026-10-28) | 2026-11-09 | official |
529
+ | Payment Reports | https://developer-docs.amazon/sp-api/docs/report-type-values-payment.md (2026-09-09) | 2026-11-09 | official |
530
+ | Get the latest transactions; List Transactions Associated with an Order; Determine payment transactions; Retrieve a financial summary | https://developer-docs.amazon/sp-api/docs/get-latest-transactions.md (2026-09-24), …/list-transactions-by-order.md, …/determine-payment-transactions.md, …/retrieve-financial-summary.md (2026-09-09) | 2026-11-09 | official |
531
+ | settlement-reports-attributes, fba-payments-reports-attributes (old slugs) | https://developer-docs.amazon/sp-api/docs/settlement-reports-attributes.md etc. | 2026-11-09 | Page Not Found |
532
+ | FBA inventory reimbursement policy G200213130 (8 host/path variants) | https://sellercentral.amazon.com/gp/help/external/G200213130 | 2026-11-09 | JS shell, unread |
533
+ | Update to FBA inventory reimbursement claim windows (eff. 2025-10-15) | https://sellercentral.amazon.com/seller-forums/discussions/t/d8f9a56c-882f-437c-ad34-cccd11cfa465 | 2026-11-09 | official |
534
+ | Update on Reimbursement Automation and Eligibility Window (Nov 1 2024 / Oct 23) | https://sellercentral.amazon.com/seller-forums/discussions/t/6605eede-df8e-4498-803f-cb612d95d7ce | 2026-11-09 | official |
535
+ | Update on Reimbursement Automation and Eligibility Window (Jan 15 2025 / Jan 9 2025) | https://sellercentral.amazon.com/seller-forums/discussions/t/d0fc997e-de50-4100-9803-76b7993b66df | 2026-11-09 | official |
536
+ | Update on eligibility window to file reimbursement claims (EU) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/1101821c-7ff1-495a-b8a5-71ff01e3afc3 | 2026-11-09 | official |
537
+ | Update to the FBA inventory reimbursement policy (manufacturing cost; Dec 19 2024 definition) | https://sellercentral.amazon.com/seller-forums/discussions/t/68864b6f-0ab8-41ef-be18-069c33df6336; EU https://sellercentral-europe.amazon.com/seller-forums/discussions/t/a941ac02-d389-409a-9d62-00ab9db5bc4a | 2026-11-09 | official |
538
+ | New effective date for FBA inventory reimbursement policy (Mar 31 2025) | https://sellercentral.amazon.com/seller-forums/discussions/t/ed8abc33-a1d5-417d-b2e2-03b789099833 | 2026-11-09 | official |
539
+ | Inventory Defect and Reimbursement portal now available | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/b175b700-09c4-4350-8a22-24f60a724042 | 2026-11-09 | official |
540
+ | FBA Lost Your Inventory? Steps to File a Reimbursement Claim (Indy_Amazon) | https://sellercentral.amazon.com/seller-forums/discussions/t/0e07abc1-9026-4540-a005-153d9e78bf04 | 2026-11-09 | official, staff |
541
+ | Amazon Prep Service (Jameson_Amazon reply) | https://sellercentral.amazon.com/seller-forums/discussions/t/5c63f045-b956-447b-9e6d-410b1e2a05bb | 2026-11-09 | official, staff |
542
+ | Fulfilment by Amazon Returns (Ezra_Amazon) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/aaf11b9d-dcc7-4df1-be41-e6e364a2cdcf | 2026-11-09 | official, staff |
543
+ | Concerns About Reversed Reimbursements (help text relayed) | https://sellercentral.amazon.in/seller-forums/discussions/t/27d8ba3f-3216-424c-a7ab-ecb55c9c2719 | 2026-11-09 | official, relayed |
544
+ | Reversed reimbursements and no inventory added back | https://sellercentral.amazon.com/seller-forums/discussions/t/58e0b08d-db92-40dd-a2a8-c2c9d6c2e475 | 2026-11-09 | opinion |
545
+ | "Manage your Sourcing Costs" … HALF | https://sellercentral.amazon.co.uk/seller-forums/discussions/t/cfea683e-d5f4-48d8-b84e-d88d3b5eeb98 | 2026-11-09 | opinion |
546
+ | Thoughts on FBA Returns Where the Item Is Never Returned (45-day policy relayed) | https://sellercentral.amazon.com/seller-forums/discussions/t/b12b6190-c9f8-45dd-ab39-dcd13dfbdb44 | 2026-11-09 | official, relayed / opinion |
547
+ | FBA return, customer refunded but item not returned (Amazon reply quoted) | https://sellercentral.amazon.ca/seller-forums/discussions/t/15c3abae-7d3a-4ad6-882e-797532dbb425 | 2026-11-09 | official, relayed |
548
+ | How to get reimbursed for a replacement order (Joey_Amazon) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/8d381f28-a83e-4ca8-bce5-2f9778efaf49 | 2026-11-09 | official, staff |
549
+ | US SAFE-T claim filing window changes to 30 days on Feb 16 | https://sellercentral.amazon.com/seller-forums/discussions/t/d95b0e44-60fc-4c16-b690-3626c9a3c43c | 2026-11-09 | official |
550
+ | Update to seller-fulfilled refund process by January 26, 2026 | https://sellercentral.amazon.com/seller-forums/discussions/t/11268c92-5a5c-4125-9e59-49e433d0d151 | 2026-11-09 | official |
551
+ | SAFE-T damage reimbursement policy (India, Aug 1 2025) | https://sellercentral.amazon.in/seller-forums/discussions/t/3fc74ac2-d8d7-4eb6-af8a-2a78feb965f6 | 2026-11-09 | official |
552
+ | Prepaid return labels required for high-value items (two posts) | https://sellercentral.amazon.com/seller-forums/discussions/t/9fa92037-c19b-4f03-82b5-7221bd0efa71; …/c1eae42b-ead4-4c63-a007-aefbca44a867 | 2026-11-09 | official |
553
+ | Update to international returns (Sep 16 2024) | https://sellercentral.amazon.com/seller-forums/discussions/t/682481b7-54ca-40e3-b578-7a98988817e3 | 2026-11-09 | official |
554
+ | Streamline returns with Returnless Resolutions; Enroll … by price in the US; Reduce return costs with returnless resolutions | …/ab90097c-c14c-4e2a-a241-68eac52ae500; …/d31d6e3f-24ed-4870-b57b-a4d7a0d74eb8; …/8f6ea88b-8672-426e-accb-7c9d7f6d911a (sellercentral.amazon.com) | 2026-11-09 | official |
555
+ | Manage FBA returns with partial refunds | https://sellercentral.amazon.com/seller-forums/discussions/t/5935f007-115c-47f2-8ea9-49d8d8c441c4 | 2026-11-09 | official |
556
+ | Refund Cost (UK help text relayed) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/3e43da0c-1b96-473b-9898-fe57db2e48bb | 2026-11-09 | official, relayed |
557
+ | FBA Fulfillment Fees charges to Seller on Customer Returns (AED cap relayed) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/22c4dcb2-808c-4dd5-ae10-f914306c57b9 | 2026-11-09 | official, relayed / opinion |
558
+ | Do we lose money when a customer refunds an item?; Refund fees | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/d8f86449-b706-4303-956f-04693cba61c4; https://sellercentral.amazon.co.uk/seller-forums/discussions/t/f29481bb-ca17-41bf-a861-537a55cc872d | 2026-11-09 | opinion |
559
+ | Returnless refund granted without rule (SEAmod reply) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/228e166c-7200-41f4-a058-f447db8ea58b | 2026-11-09 | opinion / staff |
560
+ | How to manage Amazon customer returns for seller-fulfilled orders | https://sell.amazon.com/blog/manage-customer-returns (2025-04-15) | 2026-11-09 | official |
561
+ | How to manage Amazon chargebacks | https://sell.amazon.com/blog/chargebacks (2025-12-01) | 2026-11-09 | official |
562
+ | A-to-z Guarantee claims G27951; Appeal G202041210; SAFE-T G202188810; Reconcile your shipment 201214140; customer return policy GKM69DUUYKQWKWX7 | sellercentral.amazon.com / amazon.com help | 2026-11-09 | official, search snippets only (JS shells) |
563
+ | EcommerceBytes "What's Worse than Lost FBA Inventory? When Amazon Finds It" (2025-06-29) | https://www.ecommercebytes.com/2025/06/29/whats-worse-than-lost-fba-inventory-when-amazon-finds-it/ | 2026-11-09 | unreachable (site ceased publication) |
564
+ | FBA inventory reimbursement policy, redlined US text (PDF, created 2024-12-18; Chinese copy `…-zh_cn.pdf`) | https://m.media-amazon.com/images/G/01/rainier/help./PC__Kiwi_Comms_redlined_policy_US_clean.pdf | 2026-11-10 (verifier) | official |
565
+ | Correction: Data Kiosk role requirements (2024-07-02) | https://developer-docs.amazon/sp-api/changelog/correction-data-kiosk-role-requirements | 2026-11-10 (verifier) | official |
566
+ | Amazon Selling Partner Claude plugin 1.0.0, `support-case-helper` | local `amazon-plugin-zip/skills/support-case-helper/SKILL.md` | 2026-11-09 | official |
567
+ | Listing playbook `research/angles/returns.md`, `price-position.md`, `inventory-and-fulfillment.md` | `git show origin/main:research/angles/…` | 2026-11-09 (their reads 2026-10-14) | reused, official per their sources |
568
+ | Survey `04-job-money.md`, `05-job-orders-returns-customers.md`, `02-surface-…md` | local | 2026-11-09 | reused |
569
+ | GETIDA; Seller Investigators; SPS press release 2026-06-30; SPS Q2 2026 call; Helium 10 MRS, Refund Genie, blog 2024-07-24; SELLERLOGIC; sellerboard 2026-07-14, 2025-01-20; Refund Retriever; Nova Data 2025-11-28, 2026-01-26; Refunds Manager; SellerSprite 2026-10-23; My Amazon Guy 2025-10-31; ecommerceparadise review | URLs in § What practitioners add | 2026-11-09 | opinion |
570
+ | GorillaROI Reimburse Details report page | https://www.gorillaroi.com/amazon-seller-central-reports/reimburse-details | 2026-11-09 | opinion |
571
+
572
+ | Chinese sources (gs.amazon.cn articles 250305-3, 250807-3, FBA FAQ, news-notices-260112 / 240907 / 210818, news-brand-250408, zhishi 260604-2) | URLs in § Chinese-language sources | 2026-11-09 | official |
573
+ | Lingxing, Gerpgo, Sellfox, ECCANG, Dianxiaomi/UpSeller, SellerSpace help docs; SellerHow; 亿数通 | URLs in § Chinese-language sources | 2026-11-09 | opinion |
574
+ | 雨果网 169411, 172804; AMZ123 LFOykLna, 1RKMP8FS, PPsYn6Sx, UP9ehtUA, tg6kPptK, lzje26Gk; 卖家之家 eawxbluj5am8, e85s4z0sjy80; 亿恩网 30129; 知无不言 101140, 126229 | URLs in § Chinese-language sources | 2026-11-09 | opinion |
575
+ | Settlement and Finances value sources (wimoor, bbalajiarjun130, abinashstack, ss-control-center, goncloud-Orbit, lingxing-mcp, neonpanel, tznamenacekhome, LAPrice90, prabhakar-stack, Amal-Eldesouky, flipledger, Deltologic) | github.com URLs in § Values seen in practice | 2026-11-09 | opinion, command-verified for values |
576
+ | SP-API models GitHub issues #1363, #4245, #4271, #4993, #5353 | https://github.com/amzn/selling-partner-api-models/issues/<n> | 2026-11-09 | opinion (developer reports); #4993 carries an Amazon reply |
577
+ | Synder fee glossary; A2X reimbursements accounting (2025-02-28); Amalytix seller fees (2026-10-20); Reason Automation ledger help; Openbridge gists | URLs in § Values seen in practice | 2026-11-09 | opinion |
578
+ | Improvado settlement sunset note; Amainvoice | https://improvado.io/product-updates/connectors/amazon-seller-central-settlement-report-sunset | 2026-11-09 | opinion |
579
+ | Give returns a second life with FBA Grade and Resell (News, US, posted 2024-08-07) | https://sellercentral.amazon.com/seller-forums/discussions/t/3fa4fa3c-d2a0-4233-b668-6785a5695dcc | 2026-11-10 | official |
580
+ | Recover up to 80% value from returns with FBA Grade and Resell (News, EU, posted 2025-02-24) | https://sellercentral.amazon.co.uk/seller-forums/discussions/t/ef44a47a-bf4d-4075-a5af-23b4aa7b190e | 2026-11-10 | official |
581
+ | Ask Amazon: FBA Grade and Resell (Jameson_Amazon, posted 2024-11-21) | https://sellercentral.amazon.com/seller-forums/discussions/t/78c455ed-3390-4c08-8d62-6a83d285e265 | 2026-11-10 | official, staff (staff answers not rendered) |
582
+ | Planet-friendly alternatives for returned and overstock FBA items (News, EU, posted 2021-08-18) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/f8f019e56ed2b63ea795cd315071bc3f | 2026-11-10 | official |
583
+ | Haven't seen this before (UK Grade and Resell help page GUA6RV6UA4DR2MFK copied by a seller, 2021-06-30) | https://sellercentral-europe.amazon.com/seller-forums/discussions/t/31050ea5859ae91f630bb83cd936ba06 | 2026-11-10 | official, relayed (2021 text) |
584
+ | Enroll in the Automated Grade and Resell program (2022 Amazon email quoted, JP forum) | https://sellercentral-japan.amazon.com/seller-forums/discussions/t/cabf4fef557d8ad4c7c8683192f2d745 | 2026-11-10 | official, relayed |
585
+ | Give returns a second life with FBA Grade and Resell (sell.amazon.com, 2025-09-11); New features and updates to Amazon's FBA Grade and Resell program (2026-02-03) | https://sell.amazon.com/blog/announcements/fba-grade-and-resell; https://sell.amazon.com/blog/announcements/fba-grade-and-resell-updates | 2026-11-10 | official |
586
+ | Sellers who use FBA Donations now have access to donation certificates (sell.amazon.com, 2026-03-09) | https://sell.amazon.com/blog/announcements/fba-donation-certificate | 2026-11-10 | official |
587
+ | Enrollment changes for FBA Liquidations and Donations programs (News, posted 2025-08-22; CA copy) | https://sellercentral.amazon.com/seller-forums/discussions/t/8a402163-2acc-41b0-b4ea-fe6c9b763856; https://sellercentral.amazon.ca/seller-forums/discussions/t/faf1e3b4-9d24-4bda-97ec-0928f92e478f | 2026-11-10 | official |
588
+ | Correction: Enrollment changes … (Amazon email relayed, posted 2025-09-30) | https://sellersasksellers.com/t/enrollment-changes-for-fba-liquidations-and-donations-programs/6434 | 2026-11-10 | official, relayed |
589
+ | Removal Order Fees (Topher_Amazon quoting the FBA Donations help page) | https://sellercentral.amazon.co.uk/seller-forums/discussions/t/cadc9497-4cc1-40c5-937c-25e2d8874a21 | 2026-11-10 | official, staff |
590
+ | FBA Grade and Resell GUA6RV6UA4DR2MFK (.com, .co.uk); FBA Donations program VCFMKLPUTBXE7L5 | https://sellercentral.amazon.com/gp/help/external/GUA6RV6UA4DR2MFK; https://sellercentral.amazon.com/gp/help/external/VCFMKLPUTBXE7L5 | 2026-11-10 | JS shell, unread |
591
+ | Orders v0 model (`ConditionId`, `ConditionSubtypeId`) | local `models/orders-api-model/ordersV0.json` | 2026-11-10 | official, command-verified |
592
+ | Amazon Resale rename coverage (Digital Commerce 360 2024-08-20; ChannelX 2024-10) | https://www.digitalcommerce360.com/2024/08/20/amazon-resale-replaces-warehouse-with-rebrand/; https://channelx.world/2024/10/amazon-renames-amazon-warehouse-to-amazon-resale/ | 2026-11-10 | opinion (press quoting Amazon) |
593
+ | sellerboard "Handling Amazon Grade & Resell SKUs…" (2026-01-22); ConnectBooks "How to Map Grade & Resell Items"; Synder Grade and Resell fees; Seller Labs (2025-05-21); ecomEngine (updated 2026-01-12); SPS Commerce (updated 2026-08-07); AMZ123 L2cgS471 (2025-11-19) | URLs in § Value-recovery SKUs and lines | 2026-11-10 | opinion |
594
+ | amzn.gr code: icingerpower/AmzBooks, donchrillo/jtl2datev, farhankauser-web/Daily-Sales-Dashboard, jenfol92/AWS_businessIntelligense_Ia | github.com URLs in § Value-recovery SKUs and lines | 2026-11-10 | opinion, command-verified |
595
+ | geekwire.com Amazon Resale rebrand | https://www.geekwire.com/2024/amazon-rebrands-used-goods-marketplace-to-amazon-resale/ | 2026-11-10 | unreachable (403) |
596
+
597
+ ## Open questions
598
+
599
+ 1. **Which claim windows Amazon's forms enforce.** The 2025-10-15 News post, the ≈2026-08 staff post and the relayed customer-return policy (45 vs 60 days; 105 days vs 18 months) disagree. A live account shows it in the claim tools' eligibility messages and in when automatic customer-return reimbursements land relative to the refund date.
600
+ 2. **Automation start date per store.** 2024-11-01 or 2025-01-15 (two Amazon posts with the same text); possibly two store rollouts. Reimbursements report `approval-date` and empty `case-id` per store would show.
601
+ 3. **FBA fulfilment fee on a refund.** Whether any refund line returns any part of it (e.g. when Amazon is at fault), read from `ItemFeeAdjustmentList` on real refunds.
602
+ 4. **How the refund administration fee is labelled** on this account: practitioners read settlement `RefundCommission` (and v2024 breakdown `RefundCommission`) as it; whether v0 `FeeType` uses the same name, and whether Data Kiosk economics' fee list carries it (its `PreviewFeeType` enum has `REFERRAL_FEES` and no refund-administration value) [command-verified for the enum].
603
+ 5. **`listTransactions` by `SETTLEMENT_ID`** — settled from Amazon's documents (verifier, 2026-11-10): not a filter (release note 2026-07-29 announced it; model added 2026-10-28, removed 2026-10-29 by db2936aa; live reference lists `FINANCIAL_EVENT_GROUP_ID` and `ORDER_ID` only). `listSummary` takes it.
604
+ 6. **`transactionType` values** in v2024-06-19 for refunds, A-to-z, chargebacks, SAFE-T, reimbursements, reversals and reserves on a real account (the model lists only `Shipment`).
605
+ 7. **Reimbursement `reason` values** beyond those seen in public files (P-ref-35), and the crosswalk between report `reason`, settlement `amount-description` and ledger `Reason` on one account (Amazon publishes none).
606
+ 8. **How a reimbursement is valued in practice**: compare `amount-per-unit` with the seller's entered sourcing cost (Seller Central only) and with the order's sale price for post-order losses; the "exactly half" report (UK forum) is one seller's case.
607
+ 9. **Whether reimbursements appear in v0 as `AdjustmentEvent` `FBAInventoryReimbursement` only**, or also under other names, and whether `Quantity`/`FnSKU` are filled.
608
+ 10. **Buy Shipping-protected A-to-z claims**: whether the debit ever posts and is reversed, or never posts.
609
+ 11. **Chargeback won**: which event returns the money (type and identifiers).
610
+ 12. **Replacement-not-returned reimbursement**: under which order id it posts (original or replacement) and after how many days.
611
+ 13. **Returnless and partial refunds in Finances**: how they are distinguishable from an ordinary refund (description, breakdown or context), since no report lists them.
612
+ 14. **Seller-fulfilled return label charges**: whether they post as `PostageBilling` adjustments, under which `amount-description`, and joined to which order.
613
+ 15. **Support API role**: whether the seller's app can be granted Selling Partner Support (Restricted), and what `subject` text reimbursement cases carry.
614
+ 16. **The Grade and Resell processing fee as a line**: its `amount-type` / `amount-description` in settlement V2, its v0 `FeeType` and its v2024-06-19 `breakdownType`; whether it rides on the graded sale or posts separately at relisting; and whether a US fee is charged today and at what rate (the only figures found are a vendor's).
615
+ 17. **Graded sales in Finances**: whether a graded sale posts as an ordinary `ShipmentEvent` / `Shipment` with the amzn.gr SKU in `SellerSKU` / `ProductContext.sku`, and whether `getOrderItems` shows `ConditionId` `Used` with the matching `ConditionSubtypeId`.
616
+ 18. **The amzn.gr SKU on this account**: what the two-character suffix codes are (LN, VG, PO … seen), and how often the seller SKU inside it is shortened so that it no longer matches.
617
+ 19. **Donations and disposal in the removal report**: which `order-type` and `disposition` values tell a donated unit from a recycled one, and under which line the disposal fee posts (`DisposalComplete` / `FBADisposalFee` are practitioners' names, fulfilment-charges.md).
618
+ 20. **Grade and Resell in the EU**: whether Amazon has introduced fees since the 2025-02-24 "no programme fees" post (60 days' notice was promised).
619
+
620
+ ## Positions
621
+
622
+ Each position is a fact a skill may state, with its sources (Amazon's first). None is a rule of behaviour. Positions marked [seat] enter no skill.
623
+
624
+ - **P-ref-1.** A customer refund reverses the sale's charge lines (principal, tax, shipping, gift wrap) and its promotions. The lines are listed per item in `ItemChargeAdjustmentList` and `PromotionAdjustmentList`, and refunds, guarantee claims and chargebacks share one item shape. Source: Finances v0 model `ShipmentItem` [official, command-verified].
625
+ - **P-ref-2.** On a refund, Amazon returns the referral fee minus a refund administration fee. The fee is charged per refunded line item and capped per store in that store's currency, and on a partial refund the referral fee comes back in proportion to the price refunded. The rate and cap are read from the store's fee schedule at run time. Sources: Selling on Amazon fee schedule G200336920 v119 (US); UK help text relayed on the Seller Forums (3e43da0c) [official]. Read at run time: Amazon's page Selling on Amazon fee schedule (G200336920), https://sellercentral.amazon.com/help/hub/reference/external/G200336920, as the seller's own store shows it, and the amount actually retained in a posted refund's fee lines (`listTransactions` breakdowns; v0 `ItemFeeAdjustmentList`).
626
+ - **P-ref-3.** Practitioners report that the FBA fulfilment fee does not come back on a customer refund. No Amazon page read says so, and the Finances model neither lists nor excludes such a line, because `FeeType` is an open list. Sources: Seller Forums threads 22c4dcb2, f29481bb [opinion]; financesV0 [command-verified]. A skill can state this only as practitioners' report until a live refund's `ItemFeeAdjustmentList` confirms it.
627
+ - **P-ref-4.** On seller-fulfilled orders, refunds come from the seller and also from Amazon on the seller's behalf: refund at first scan (prepaid labels), a returnless rule the seller set, the automated refund after the seller's deadline, A-to-z claims, chargebacks and customer service. A refund in the seller's books is therefore not always one the seller issued. Source: sell.amazon.com "How to manage Amazon customer returns for seller-fulfilled orders" (2025-04-15) [official].
628
+ - **P-ref-5.** From 2026-01-26, a seller-fulfilled return that is not refunded within four calendar days of receipt may be refunded automatically. Such an auto-refund cannot be recovered through SAFE-T, except when the item was lost in transit or the delivery confirmation was wrong. Source: News "Update to seller-fulfilled refund process by January 26, 2026" [official]. Read at run time: Amazon's page "Update to seller-fulfilled refund process by January 26, 2026", https://sellercentral.amazon.com/seller-forums/discussions/t/11268c92-5a5c-4125-9e59-49e433d0d151 (a Seller Forums News post on sellercentral.amazon.com, read 2026-11-09); no SP-API operation gives the deadline.
629
+ - **P-ref-6.** From 2026-02-08, US seller-fulfilled returns use Amazon Prepaid Return Labels whatever the item's value, apart from the named category exemptions. Labels bought through Amazon post as `PostageBilling` (and `PostageRefund` when a label is refunded) in Finances v0. The returns reports carry `label_cost` and `label_to_be_paid_by`. Sources: News 9fa92037; financesV0 `AdjustmentType`; Returns Reports page (2026-10-28) [official].
630
+ - **P-ref-7.** A restocking fee can apply to a seller-issued refund for a damaged or materially different item, or for a return outside Amazon's policy. In Finances it appears as the `RestockingFee` charge type. Return shipping is deducted from the refund when the buyer changed their mind, and paid by the seller when the item was defective or misshipped (`ReturnShipping`). Sources: sell.amazon.com 2025-04-15; financesV0 `ChargeComponent` [official].
631
+ - **P-ref-8.** FBA returnless and partial refunds are refunds the seller chose to fund. The unit stays with the buyer and no reimbursement follows. They count toward the return rate, and FBA Returnless Resolutions has no downloadable report. Partial refunds show in the FBA Returns dashboard as "Complete – Return not expected". Returnless refunds do not appear in the FBA customer returns report or the seller-fulfilled returns reports, but Data Kiosk seller analytics `returnedUnits` counts them ("including returnless refunds"). Sources: News ab90097c, d31d6e3f, 8f6ea88b, 5935f007; G3RZC8DVQCDTCQ3B v8; G200453320 (listing seat); Returns Reports page (2026-10-28); `analytics_sellerAnalytics_2025_03_31` [official].
632
+ - **P-ref-9.** For an assigned A-to-z claim, Amazon refunds the buyer and debits the seller or cancels a future payment. A request for information left unanswered for 72 hours grants the claim. A granted claim can be appealed within 30 calendar days. An order with an A-to-z claim is not eligible for SAFE-T. Sources: G27951, G202041210, G202188810 via search snippets [official]. Read at run time: Amazon's pages A-to-z Guarantee claims (G27951), https://sellercentral.amazon.com/gp/help/external/G27951, and Appeal an A-to-z Guarantee claim (G202041210), https://sellercentral.amazon.com/help/hub/reference/external/G202041210, as the seller's own store shows them (JavaScript pages, read here only through search snippets on 2026-11-09); no SP-API operation gives the response time or the appeal window.
633
+ - **P-ref-10.** Amazon carries fraud-related chargebacks. The seller carries service-related ones, such as non-receipt, and can refund or represent within seven calendar days. The bank decides, and the outcome can take 90 days or more. Source: sell.amazon.com "How to manage Amazon chargebacks" (2025-12-01) [official]. Read at run time: Amazon's page "How to manage Amazon chargebacks", https://sell.amazon.com/blog/chargebacks (sell.amazon.com, US, read 2026-11-09); no SP-API operation gives the reply window.
634
+ - **P-ref-11.** SAFE-T reimburses seller-fulfilled refunds the seller did not cause. In Finances v0 it posts as `SAFETReimbursementEvent` (with `SAFETClaimId` and `ReasonCode`) and the `SAFE-TReimbursement` charge. The returns report carries the claim id, state and reimbursement amount. The US window has been 30 days since 2026-02-16, counted from the later of the return delivery scan and the refund date, or from the last scan for a lost shipment. India has excluded packaging damage and broken seals since 2025-08-01. Sources: News d95b0e44, 3fc74ac2; financesV0; Returns Reports page [official]. Read at run time: Amazon's page Reimbursement for seller-fulfilled orders (SAFE-T, G202188810), https://sellercentral.amazon.com/gp/help/external/G202188810, as the seller's own store shows it (a JavaScript page, unread here), and the News post "US SAFE-T claim filing window changes to 30 days on Feb 16", https://sellercentral.amazon.com/seller-forums/discussions/t/d95b0e44-60fc-4c16-b690-3626c9a3c43c (US, read 2026-11-09); no SP-API operation gives the window.
635
+ - **P-ref-12.** FBA inventory reimbursement covers units lost or damaged in a fulfilment centre, shipments missing from inbound, removals lost or damaged, and customer returns that were refunded but not returned, or returned unsellable through Amazon's fault. Returns damaged by the customer are not reimbursed. Neither are accounts in blocked, terminated or fraud status, nor (US, shipments created from 2026-01-01) units that arrive without proper prep and labelling and are then damaged or untraceable. Sources: Indy_Amazon staff post 0e07abc1; Jameson_Amazon 5c63f045; G200379860 v24 [official].
636
+ - **P-ref-13.** Amazon reimburses most warehouse-lost, warehouse-damaged and customer-return cases without a claim, and records them in the Reimbursements report. Every removal claim is still filed manually. The IDR portal leaves out missing-from-inbound, removals and warehouse disposals. The start date is stated twice: 2024-11-01 (News 6605eede, posted 2024-07-24) and 2025-01-15 (News d0fc997e, posted 2024-10-10); no page says which store each addresses. Sources: News 6605eede / d0fc997e, b175b700 [official].
637
+ - **P-ref-14.** Since 2025-03-31, a unit lost or damaged before a customer order is reimbursed at the seller's sourcing ("manufacturing") cost: the cost of sourcing or making the item, excluding shipping, handling, customs duties and other costs. Amazon applies its own estimate unless the seller enters a cost on Manage Your Sourcing Cost. A unit lost or damaged after a customer order is reimbursed at the order's sale price minus applicable fees. A unit that was unsellable when lost is reimbursed at "a reduced estimated cost". Sources: News 68864b6f (posted 2024-12-18), ed8abc33 (posted 2025-02-28); staff post 0e07abc1 (2026-08-13) [official].
638
+ - **P-ref-15.** The 2025-03-31 date replaced the announced 2025-03-10. The page Amazon first called Manage Your Manufacturing Cost is now Manage Your Sourcing Cost. Source: News ed8abc33 [official].
639
+ - **P-ref-16.** A claim window is a dated fact, and Amazon's pages state different windows. Page by page (each re-read 2026-11-10; posting dates from the page):
640
+ - News 6605eede (posted 2024-07-24, effective 2024-10-23), News d0fc997e (posted 2024-10-10, effective 2025-01-09) and EU News 1101821c (posted 2025-01-15): FC lost/damaged "no later than 60 days after the item was reported lost or damaged"; customer returns "between 45-105 days after the customer refund or replacement date"; removal lost in transit "15-75 days from the shipment-creation date"; other removals "within 60 days of the shipment being delivered back to you".
641
+ - News d8f9a56c (posted 2025-08-14, effective 2025-10-15): lost or damaged "Within 60 days of reported loss or damage"; customer returns "Between 45-105 days after customer refund or replacement"; removal lost "Between 15-135 days from shipment creation"; removal damaged "120 days from shipment delivery date"; removal grading "120 days from date item was removed from our fulfilment network"; re-evaluation "Within 90 days of initial claim". It names no missing-from-inbound window.
642
+ - Staff post Indy_Amazon 0e07abc1 (posted 2026-08-13): warehouse lost/damaged "within 60 days of the date the loss or damage event appears in your reports"; missing from inbound "after your shipment is closed/finalized … and within 9 months"; customer returns "no sooner than 60 days after the customer refund … and within 18 months"; removals "within 18 months of the shipment being delivered or lost".
643
+ - gs.amazon.cn articles 250305-3 (2025-03) and 250807-3 (2025-08): missing from inbound within nine months of delivery to the FC (US).
644
+ - Policy text relayed by a seller (b12b6190, 2025-04-14): a unit not returned "within 45 days of the refund" is reimbursed.
645
+ - Valuation dispute: "within 60 days after we have issued the reimbursement" (policy PDF, 2024-12-18).
646
+
647
+ A skill states each figure with its page and date and picks none. Sources: as listed [official; b12b6190 official, relayed]. Read at run time: Amazon's page FBA inventory reimbursement policy (G200213130), https://sellercentral.amazon.com/gp/help/external/G200213130, as the seller's own store shows it (a JavaScript page, unread here), and the latest Seller Forums News post on the claim windows; no SP-API operation gives a window.
648
+ - **P-ref-17.** A reimbursement is paid in cash, as units put back in stock, or both (`quantity-reimbursed-cash`, `-inventory`, `-total`). Units put back move no money. Source: `GET_FBA_REIMBURSEMENTS_DATA` columns [official]; the money reading is [seat] and needs a live check.
649
+ - **P-ref-18.** Amazon reverses a reimbursement when it was paid in error or when the lost unit is found and returned to stock. A reversal row links to what it reverses through `original-reimbursement-id` and `original-reimbursement-type`. Sellers report reversals more than a year after payment, with no matching found unit in the ledger. Sources: help text GMGJASYYNYLXKLXE relayed (27d8ba3f); FBA Reports page [official]; forum 58e0b08d, My Amazon Guy 2025-10-31 [opinion].
650
+ - **P-ref-19.** `GET_FBA_REIMBURSEMENTS_DATA` can only be requested, is updated daily, and carries the 18 columns listed in § G. It needs the Pricing or Amazon Fulfillment role. Amazon publishes no list of its `reason` values. Sources: FBA Reports page (2026-10-13); Role Mappings for Types (2026-09-09) [official].
651
+ - **P-ref-20.** A reimbursement ties back to its cause through `amazon-order-id` (customer-return and post-order cases), `case-id` (manual claims; blank when Amazon paid on its own), `fnsku` / `sku` / `asin` (the unit), and `reimbursement-id` ↔ `original-reimbursement-id` (reversals). The meaning of a blank `case-id` is [seat] until checked on a live account. Source: FBA Reports page [official].
652
+ - **P-ref-21.** The model's Finances v0 `AdjustmentType` list has eight values. The four that are not India- or Easy Ship-only are `FBAInventoryReimbursement`, `ReserveEvent`, `PostageBilling` and `PostageRefund`. Responses and settlement files carry further names (e.g. `ReserveDebit`, `ReserveCredit`, `WAREHOUSE_DAMAGE`, `REVERSAL_REIMBURSEMENT`) that appear nowhere in the model, so the list is open in practice. Sources: financesV0 [command-verified]; practitioners (§ What practitioners add) [opinion].
653
+ - **P-ref-22.** Refunds, guarantee claims and chargebacks carry `OrderAdjustmentItemId` in v0. In v2024-06-19 they carry `ORDER_ID` / `REFUND_ID` related identifiers and an `ORDER_ADJUSTMENT_ITEM_ID` item identifier. The settlement V2 file carries `adjustment-id` and `merchant-adjustment-item-id`. These are the joins from a refund back to its order and order item. Sources: financesV0; finances_2024-06-19; Settlement Reports page [official].
654
+ - **P-ref-23.** Finances v2024-06-19 `listTransactions`:
655
+ - It needs Finance and Accounting and runs at 0.5 rps / burst 10.
656
+ - It returns nothing for a window longer than 180 days and may omit the last 48 hours.
657
+ - It includes deferred transactions unless filtered.
658
+ - Its `transactionType` is documented only as `Shipment`, and its `breakdownType` is an open string.
659
+ - Listing by `ORDER_ID` finds refunds, chargebacks and adjustments that post days to months after the order.
660
+
661
+ - It filters only by `FINANCIAL_EVENT_GROUP_ID` and `ORDER_ID`. `SETTLEMENT_ID` is not a filter: the 2026-07-29 release note announced it, the model added it 2026-10-28 (df7c6298) and the "Finance API Rollback" (db2936aa, 2026-10-29) removed it; it filters `listSummary`, and still appears as a related identifier in responses.
662
+
663
+ Sources: finances_2024-06-19 model; developer docs "Get the latest transactions", "List Transactions Associated with an Order"; listtransactions reference (2026-11-10, other verifiers) [official]. Read at run time: the rate and burst applied to the seller, from the `x-amzn-RateLimit-Limit` header of each `listTransactions` response (the model's table is the default, and "Selling partners whose business demands require higher throughput may have higher rate and burst values").
664
+ - **P-ref-24.** Finances v0 `listFinancialEvents`, `…ByOrderId` and `…ByGroupId` were deprecated on 2025-07-21 and are removed on 2027-08-27. `listFinancialEventGroups` is not on that schedule. All run at 0.5 rps / burst 30. Deferred events appear only once released. Sources: SP-API deprecations; financesV0 [official]. Read at run time: the rate and burst applied to the seller, from the `x-amzn-RateLimit-Limit` header of each `listFinancialEvents`, `listFinancialEventsByOrderId`, `listFinancialEventsByGroupId` and `listFinancialEventGroups` response.
665
+ - **P-ref-25.** Refunds are dated differently by different reads:
666
+ - The settlement file and Finances use the posting date.
667
+ - Data Kiosk economics counts `refundedProductSales` "by refund request time".
668
+ - Data Kiosk seller analytics attributes returns to the ship date, with ~45 days' delay.
669
+ - The FBA returns report uses the date the FC processed the return.
670
+
671
+ Which date the seller books is the seller's choice. Sources: Data Kiosk schemas; Settlement and FBA report pages [official].
672
+ - **P-ref-26.** Data Kiosk economics `netProceeds` subtracts fees, ads and cost from net product sales. Its formula has no reimbursement term. Source: `analytics_economics_2024_03_15` schema [official, command-verified]. That reimbursements are therefore missing from it is [seat].
673
+ - **P-ref-27.** `listBalances` reports an `ACCOUNT_LEVEL_RESERVE` "to cover potential liabilities such as refunds, chargebacks, or other claims". v0 `ReserveEvent` is "generated at the time a settlement period closes" when money is held back. Sources: finances_2024-06-19; financesV0 [official].
674
+ - **P-ref-28.** Roles for this area's reads:
675
+ - Through the door: Finances and the settlement V2 report (Finance and Accounting only), the reimbursements, FBA returns and removal reports (Pricing or Amazon Fulfillment), the Prime returns and flat return-attribute reports (Pricing), and Data Kiosk Sales and Traffic and seller analytics (Brand Analytics).
676
+ - Open: Data Kiosk Economics. Role Mappings and the Data Kiosk page say Brand Analytics for every operation; Amazon's correction page (2024-07-02) says "The Economics dataset requires the Selling Partner Insights role."
677
+ - Need Amazon Fulfillment: the ledger and replacements reports.
678
+ - Not ours: seller-fulfilled returns by return date (IOT / DtC Shipping, restricted) and the Support API (Selling Partner Support, restricted).
679
+
680
+ Sources: Role Mappings for Operations (2026-10-28) and for Types (2026-09-09) [official].
681
+ - **P-ref-29.** No SP-API operation issues a refund, files a reimbursement, SAFE-T or A-to-z claim, represents a chargeback, sets returnless or partial-refund rules, or enters a sourcing cost. Those happen only in Seller Central. The Support API reads cases and creates none. Amazon's own plugin skill `support-case-helper` calls no SP-API tool and points to the Help Center. Sources: ops.tsv (394 ops), support_2025-02-01 [command-verified]; amazon-plugin-zip [official].
682
+ - **P-ref-30.** [seat] What a later claims plugin would add over this pack: the joins that find what is owed (refunds with no return and no reimbursement once the window opens; ledger lost/damaged units with no reimbursement; inbound shortfalls; removals not received; reversals with no found unit; reimbursements below the seller's cost), the window clock per case type with its dated source, the evidence each form asks for, and case status (Support API, a restricted role).
683
+ - **P-ref-31.** Paid recovery services (GETIDA, Seller Investigators, Helium 10 Managed Refund Service, SELLERLOGIC, Refund Retriever) take a share of what they recover and file through Seller Central; their rates are under Facts for human readers only. Several of their pages still describe superseded rules (18-month audits, "no proactive reimbursement", the 2025-03-10 date). GETIDA reports, from its own sample, that Amazon pays almost all FBA customer-return issues on its own within about two months; no vendor's "share of revenue owed" figure cites a method. Sources: vendor pages read 2026-11-09 [opinion].
684
+ - **P-ref-32.** SPS Commerce, which bought Carbon6 (Seller Investigators) in 2025, sold its 3P revenue recovery business on 2026-06-30 for $9.5M. On its earnings call it named Amazon's 3P policy changes as a reason. Sources: SPS press release 2026-06-30; Q2 2026 call transcript [opinion, a vendor's own statement].
685
+
686
+ - **P-ref-33.** Settlement refund rows carry the refund's parts under `amount-type`: `ItemPrice` (`Principal`, `Shipping`, `Tax`, `Goodwill`, `RestockingFee`, `ReturnShipping`, …), `ItemFees` (`Commission`, `RefundCommission`, `ShippingChargeback`, …), `Promotion` and `ItemWithheldTax`. Practitioners read `RefundCommission` as the refund administration fee. Reimbursements arrive as `other-transaction` / `FBA Inventory Reimbursement` with a reason in `amount-description` (`WAREHOUSE_LOST`, `WAREHOUSE_DAMAGE`, `MISSING_FROM_INBOUND`, `REVERSAL_REIMBURSEMENT`, `COMPENSATED_CLAWBACK`, `FREE_REPLACEMENT_REFUND_ITEMS`, …). The reserve arrives as `Current Reserve Amount` / `Previous Reserve Amount Balance`. Amazon publishes no list of these values, so the values are read from the file. Sources: Settlement Reports page [official, columns]; public mapping files and vendor glossaries [opinion; values command-verified].
687
+ - **P-ref-34.** Values seen in Finances responses go beyond the model: v0 `ReserveDebit` / `ReserveCredit`, the `PostageBilling_*` / `PostageRefund_*` / `ReturnPostageBilling_*` families (reported to carry no order id or SKU), and v2024-06-19 `transactionType` values such as `Refund`, `Retrocharge`, `ServiceFee`, `Adjustment`, `Compensation`, `Chargeback` and `FBAInventoryReimbursement`. For reimbursements the reason rides in `description`. Amazon answered one developer that a reimbursement's breakdown tree "does not appear to be documented as expected behavior". Sources: SP-API models issues #1363, #4271, #4993; public pulls [opinion, command-verified for values]; financesV0 and finances_2024-06-19 [official, for what the model lists].
688
+ - **P-ref-35.** The Reimbursements report `reason` values seen are `CustomerReturn`, `CustomerServiceIssue`, `Lost_Warehouse`, `Damaged_Warehouse`, `Lost_Inbound`, `Damaged_Inbound`, `Lost_Outbound`, `Damaged_Outbound`, `ReturnAdjustment` and `Reimbursement_Reversal`. On reversal rows `original-reimbursement-type` names the reason being reversed. Sources: a public 413-row India report and audit code [opinion, command-verified]; FBA Reports page [official, columns].
689
+ - **P-ref-36.** The ledger names a loss by a one-letter `Reason`, the reimbursements report by a CamelCase `reason`, and the settlement and Finances by UPPER_SNAKE descriptions. Practitioners match ledger `M` (misplaced) to `Lost_Warehouse` and `E` / `H` to `Damaged_Warehouse` by FNSKU and currency, and say no event id links them. Ledger `F` / `N` (found) and the reconciliation outcome "Reimbursed" are the ledger side of a reimbursement or its reversal. Sources: Reason Automation ledger help and Openbridge gists (wording not confirmed against Amazon); audit code [opinion]; FBA Reports page (ledger columns) [official].
690
+ - **P-ref-37.** Amazon's Chinese pages state the US missing-from-inbound window as no later than nine months after delivery to the FC (gs.amazon.cn articles 2025-03 and 2025-08). The same pages say the IDR portal covers warehouse lost, warehouse damaged and customer-return defects, with three statuses: eligible to file, resolved, and in review. The Chinese FBA FAQ says the original unit of a free replacement order must reach the warehouse within 45 days or Amazon reimburses under the policy, and that warehouse-damaged units cannot be removed and are reimbursed automatically and written off. Sources: gs.amazon.cn article-250305-3, article-250807-3, north-america/fba/faq [official]. Read at run time: Amazon's page FBA inventory reimbursement policy (G200213130), https://sellercentral.amazon.com/gp/help/external/G200213130, as the seller's own store shows it (a JavaScript page, unread here); no SP-API operation gives a window.
691
+ - **P-ref-38.** From 2026-03-31, when commingling ends, stock that is not correctly labelled may be untraceable and not eligible for reimbursement. Source: gs.amazon.cn news-notices-260112 [official].
692
+ - **P-ref-39.** Chinese ERPs estimate what Amazon owes and track the Case ID the seller enters against the Reimbursements report. None files claims. How they value and book the money:
693
+ - Valuation: Gerpgo uses the latest reimbursed unit price; Lingxing and Sellfox use the fee difference × quantity.
694
+ - Booking: Lingxing nets reversals in one reimbursement line and puts A-to-z and SAFE-T under other income; Gerpgo offsets the reimbursed units' purchase and freight cost; ECCANG lets the seller count each reimbursement kind in or out of profit.
695
+
696
+ Sources: Lingxing, Gerpgo, Sellfox and ECCANG help docs [opinion]. Which treatment applies is the seller's choice.
697
+
698
+ - **P-ref-40.** Amazon's FBA inventory reimbursement policy text (Amazon's redlined US policy PDF, created 2024-12-18) states: a cap of $5,000 per unit; Amazon may replace a lost or damaged unit "with a new item of the same FNSKU" instead of paying; it may reverse a reimbursement made in error or for a unit later found; found reimbursed units may be sold through Amazon Warehouse or other channels; a customer-return claim is valued at "the refund amount or the sales price of the replacement item on the original order minus applicable fees"; post-order estimated proceeds are an estimated sale price (from 18-month median prices and current list prices) "minus referral fees and fulfillment fees"; a valuation dispute is filed "within 60 days after we have issued the reimbursement"; a repeat cost dispute within 30 days with no new information may be declined. The PDF predates the move of the effective date to 2025-03-31. Source: https://m.media-amazon.com/images/G/01/rainier/help./PC__Kiwi_Comms_redlined_policy_US_clean.pdf (read 2026-11-10) [official]. Read at run time: Amazon's page FBA inventory reimbursement policy (G200213130), https://sellercentral.amazon.com/gp/help/external/G200213130, as the seller's own store shows it (a JavaScript page, unread here); no SP-API operation gives the per-unit cap or the dispute windows.
699
+ - **P-ref-41.** A granted A-to-z claim and a chargeback post in Finances v0 as their own event lists (`GuaranteeClaimEventList`, `ChargebackEventList`), with the same item shape as a refund and an `OrderAdjustmentItemId`. In the settlement file they are the transaction types `A-to-z Guarantee Refund` and `Chargeback Refund`, read from public files (Amazon publishes no list). A SAFE-T reimbursement posts in v0 as `SAFETReimbursementEvent` with its claim id and reason code. The model names no event for a chargeback won back, and no public v2024-06-19 sample of an A-to-z or SAFE-T transaction was found. Sources: financesV0 [official, command-verified]; wimoor and AU settlement mappings [opinion, command-verified]; sell.amazon.com chargebacks (2025-12-01) [official].
700
+
701
+ - **P-ref-42.** FBA Grade and Resell grades eligible unfulfillable customer returns and relists them as Used ("Like New", "Very Good", "Good", "Acceptable") under the parent ASIN, "with you as the seller on record". Each graded listing gets an Amazon-generated SKU beginning `amzn.gr`; the 2021 UK text says at most five such SKUs are generated per used listing under the parent ASIN (four used conditions and one unsellable), though practitioners' files show amzn.gr SKUs with differing random keys for one product (P-ref-45), and a unit graded unsellable stays in unfulfillable inventory under a new FNSKU beginning `amzn.gr`. Payments for graded sales appear in the seller's Payments dashboard. Sources: Jameson_Amazon 78c455ed (2024-11-21) [official, staff]; sell.amazon.com (2025-09-11) [official]; UK help page GUA6RV6UA4DR2MFK as copied on 2021-06-30 (31050ea5) [official, relayed].
702
+ - **P-ref-43.** A graded unit's sale carries the referral fee and the FBA fulfilment fee, plus a processing fee charged at relisting; no processing fee is charged on a unit graded unsellable. Standard removal fees do not apply to units submitted to the programme; storage stops accruing on submission and restarts once a used unit is listed. The US News post (2024-08-07) calls the programme "an optional fee-based service"; the EU post (2025-02-24, UK, FR, DE, IT, ES, CZ, PL) says it runs "without any programme fees" with 60 days' notice before any. Rates are read at run time. Sources: UK help copy 31050ea5 [official, relayed, 2021 text]; News 3fa4fa3c, ef44a47a [official]. Read at run time: Amazon's page FBA Grade and Resell (GUA6RV6UA4DR2MFK), https://sellercentral.amazon.com/gp/help/external/GUA6RV6UA4DR2MFK, as the seller's own store shows it (a JavaScript page, unread here), and the fee as it posts on the seller's own settlement V2 and `listTransactions` rows (its label is open, open question 16); no SP-API operation gives the rate.
703
+ - **P-ref-44.** The used price of a graded unit is set by the seller as a discount per condition on the new price at relisting; since 2026-02-03 used prices follow changes to the new price and to the discounts automatically, until the seller prices a used SKU by hand. Since 2026-02-03 the seller can include up to 2,000 chosen ASINs or the whole catalogue less exclusions, and watches, jewelry, luggage, shoes and apparel are eligible. Enrolment sits in FBA settings → Automated unfulfillable settings. Sources: sell.amazon.com (2026-02-03); News ef44a47a; UK help copy 31050ea5 [official]. Read at run time: Amazon's page FBA Grade and Resell (GUA6RV6UA4DR2MFK), https://sellercentral.amazon.com/gp/help/external/GUA6RV6UA4DR2MFK, as the seller's own store shows it (a JavaScript page, unread here); no SP-API operation gives the ASIN limit.
704
+ - **P-ref-45.** Proceeds of a graded resale land under the amzn.gr SKU, not under the SKU whose refund produced the unit. The only links back are the parent ASIN and the SKU string: practitioners see `amzn.gr.<seller SKU>-<random key>-<two-character code>` (codes such as `LN`, `VG`, `PO`), and one tool reports that in about one case in five Amazon shortened the seller SKU so that the string no longer matches. Amazon publishes neither the format nor a linking field. Sources: UK help copy 31050ea5 (prefix, parent ASIN) [official, relayed]; AmzBooks, jtl2datev, Daily-Sales-Dashboard code and data [opinion, command-verified].
705
+ - **P-ref-46.** How a graded resale is costed is an accounting choice, and tools differ. sellerboard detects amzn.gr SKUs and excludes the original SKU's COGS from their profit, because the cost was booked when the original unit sold; ConnectBooks maps them to a non-inventory item at $0 cost with Amazon fees kept; a German DATEV exporter values unmatched graded units at 10% of the purchase cost; a US dashboard leaves `amzn.` SKUs out of fee analysis. Which treatment applies is the seller's choice. Sources: sellerboard (2026-01-22), ConnectBooks help, jtl2datev, Daily-Sales-Dashboard [opinion].
706
+ - **P-ref-47.** Graded units show as their own SKUs in the reads that carry SKUs: one US seller's live Data Kiosk `economics` pull (July 2026) returned amzn.gr MSKUs with FBA fulfilment-fee and fuel-surcharge components, and ledger tools separate amzn.gr rows from new stock. Orders v0 order items carry `ConditionId` (`New`, `Used`, …) and `ConditionSubtypeId` (`Very Good`, `Good`, `Acceptable`, …), which tell a used sale from a new one. No SP-API operation or report names Grade and Resell. Sources: ordersV0 [official, command-verified]; Daily-Sales-Dashboard, AWS_businessIntelligense_Ia [opinion, command-verified]; FBA Reports page, ops.tsv [command-verified].
707
+ - **P-ref-48.** A donated FBA unit costs the seller the usual disposal fee and returns no proceeds. US sellers are enrolled in FBA Donations by default, and returned units ineligible for resale may be donated automatically; in Seller Central donating appears as "Dispose" or "Donate/Recycle". Donations show in the Removal Order Detail report. A yearly donation certificate from the nonprofit partners, on the Donations page, lists the quantity and description of units donated the previous year; Amazon says it "can be used to receive a tax benefit", and how a seller treats it for tax is the seller's. The programme started in the US and UK in 2019 and France in 2020. Sources: sell.amazon.com (2026-03-09); Topher_Amazon quoting the help page (cadc9497); News EU (2021-08-18) [official].
708
+ - **P-ref-49.** Dated enrolment changes: the News post of 2025-08-22 announced for 2025-09-30, in the US and Canada, FBA Liquidations as the default for unsold inventory where no automated settings are configured (opt-out kept), and FBA Donations as mandatory with re-enrolment of opted-out sellers, "no changes to the fees". Amazon's correction (relayed by a seller, 2025-09-30) limits both to the US, leaves Canada unchanged, and moves the Donations change to 2025-10-30, applying "if you select Dispose". The News post itself still reads US and Canada, 2025-09-30. Sources: News 8a402163, faf1e3b4 [official]; sellersasksellers 6434 [official, relayed]. Liquidation money: `fulfilment-charges.md` P-ful-11.
709
+ - **P-ref-50.** Amazon's reimbursement policy text says reimbursed units, including units found after reimbursement, may be sold "on Amazon warehouse or other channels" (Amazon Warehouse was renamed Amazon Resale in August 2024). A seller's unit sold there is therefore one Amazon has already paid for; the seller's money on it is the reimbursement and any later reversal, not resale proceeds. Grade and Resell uses the same grading process as Amazon Warehouse. Sources: policy PDF (2024-12-18) [official]; UK help copy 31050ea5 and the 2022 email (cabf4fef) [official, relayed]; Digital Commerce 360 (2024-08-20) [opinion]. The money reading is [seat].
710
+ - **P-ref-51.** [seat] A returned FBA unit ends in one of these money outcomes, each on a different line and often a different SKU: restocked (no money; the refund stands); reimbursed by Amazon (a reimbursement line, E); graded and resold (a sale under an amzn.gr SKU less fees, J1); liquidated (proceeds less fees, fulfilment-charges H4); donated or disposed (a disposal fee, J2); returned to the seller (a removal fee). Netting a refund against what its unit later brought back needs the join of P-ref-45 and the removal report.
711
+
712
+ ## Verification
713
+
714
+ Verified 2026-11-10 by an adversarial verifier. Methods: plain GET of public pages, stripped of HTML locally. Forum posting dates come from each page's `datePublished`/`datetime` attributes. developer-docs pages were read as `.md`. Amazon's policy PDF was text-extracted locally. Models clone db2936aa was read with `python3 -I`/grep. Role rows came from `web01/role-mappings.md` (2026-10-28) and `role-mappings-for-types.md` (2026-09-09). No Amazon API host was called and no help-hub content call was made.
715
+
716
+ **What was checked.**
717
+ - All 39 positions, plus every [official] quote they rest on that can be reached without sign-in:
718
+ - 27 Seller Forums posts, re-read word for word (plus d8f86449 and f29481bb for A3): d8f9a56c, 6605eede, d0fc997e, 1101821c, 0e07abc1, 68864b6f, a941ac02, ed8abc33, b175b700, d95b0e44, 11268c92, 3fc74ac2, 9fa92037, c1eae42b, 682481b7, ab90097c, d31d6e3f, 8f6ea88b, 5935f007, 27d8ba3f, 5c63f045, aaf11b9d, 3e43da0c, 22c4dcb2, 8d381f28, b12b6190, 58e0b08d.
719
+ - Both sell.amazon.com blogs.
720
+ - Seven developer-docs pages.
721
+ - Seven gs.amazon.cn pages.
722
+ - financesV0 and finances_2024-06-19 (every definition and enum quoted, every rate).
723
+ - The three Data Kiosk schemas.
724
+ - Role Mappings, every row cited.
725
+ - The deprecation and release-note rows.
726
+ - The quotes that hold: A1, A2 (UK and UAE relayed text), A4, A5, A6, A7, A9, C, D, E1 (staff), E2, E3, E4, E5, E7, F, G, H and I, and the API-table quotes and rates.
727
+
728
+ **Changes (old → new; why; source).**
729
+ 1. **Dated changes, E2, F, P-ref-13, P-ref-16.**
730
+ - Old: "2025-01-09 … another post gives 2024-10-23"; "2025-01-15 … another gives 2024-11-01"; EU post "undated"; staff post "≈2026-08"; 2025-10-15 post undated.
731
+ - New, with the posting dates:
732
+ - 6605eede, posted 2024-07-24: windows from 2024-10-23, automation from 2024-11-01.
733
+ - d0fc997e, posted 2024-10-10, British spelling: windows from 2025-01-09, automation from 2025-01-15.
734
+ - EU 1101821c, posted 2025-01-15.
735
+ - d8f9a56c, posted 2025-08-14: effective 2025-10-15.
736
+ - 0e07abc1: posted 2026-08-13.
737
+ - Thread ids resolve on every forum host, so no page names the store each post addresses. The per-store reading is recorded as [seat]; neither date is picked.
738
+ - P-ref-16 now says which page states which window, with the page's words, and picks none.
739
+ 2. **Chinese FBA FAQ "45天"** (Chinese sources, F conflict, P-ref-37).
740
+ - Old: "a refunded unit not returned within 45 days… agrees with the relayed English policy".
741
+ - New: the page's sentence is about the original unit of a $0 replacement order. The earlier reading was wrong. Source: gs.amazon.cn/north-america/fba/faq.
742
+ 3. **A3 / P-ref-3.**
743
+ - Old: a quote "any fees related to fulfillment … will not be refunded…", and "the model has no type for reversing a fulfilment fee".
744
+ - New: that quote is not on d8f86449, 22c4dcb2 or f29481bb, so it is marked a paraphrase. Real seller words replace it. `FeeType` is an open list, so the model neither lists nor excludes the line.
745
+ 4. **A4.** "For FBA orders, Amazon handles returns" is not on the sell.amazon.com page. It is marked a paraphrase.
746
+ 5. **A5.** The posting date is 2025-12-23, not "2025-12-22 per a reply".
747
+ 6. **`SETTLEMENT_ID`** (dated changes, API table, P-ref-23, open question 5). It is aligned to the settled fact: not a `listTransactions` filter. It was added in df7c6298 (2026-10-28) and removed in db2936aa (2026-10-29), and it filters `listSummary`. The model still lists it in the response's `RelatedIdentifier` enum. The open question is closed.
748
+ 7. **Data Kiosk Economics role** (API table, P-ref-28).
749
+ - Old: "Brand Analytics".
750
+ - New: open. Role Mappings say Brand Analytics, while Amazon's correction page (2024-07-02) says "The Economics dataset requires the Selling Partner Insights role." P-ref-28 also now says that settlement V2 is Finance and Accounting only.
751
+ 8. **`breakdownType` quote.** It is attributed to "Get the latest transactions" (2026-09-24), not the model.
752
+ 9. **P-ref-8.** Added: Data Kiosk seller analytics `returnedUnits` counts returnless refunds, which the reports exclude.
753
+ 10. **E1 / E4a / P-ref-40 (new).** Amazon's redlined US policy PDF (m.media-amazon.com, created 2024-12-18; found through a search result) adds:
754
+ - the policy's eligibility list;
755
+ - a $5,000 per-unit cap;
756
+ - replacement in kind;
757
+ - found units sold through Amazon Warehouse;
758
+ - the customer-return valuation;
759
+ - the estimated-proceeds definition;
760
+ - a 60-day valuation dispute;
761
+ - the 30-day repeat-dispute rule.
762
+ 11. **§ I2 and P-ref-41 (new).** These fill the depth gap: how A-to-z, chargeback and SAFE-T money posts in v0, in v2024-06-19 and in the settlement V2 file, from the model and from two public settlement mappings re-read today.
763
+
764
+ **Count.** Checked 39. Changed 8: P-ref-3, 8, 13, 14 (dates only), 16, 23, 28, 37. Made [seat]: 0. Removed: 0. Added: 2 (P-ref-40, 41). No position states a behaviour rule. P-ref-16's "picks none" and P-ref-25's "seller's choice" are disciplines.
765
+
766
+ **Not verified.**
767
+ - Help-page text from the listing seat's 2026-10-14 reads: G200336920 v119 (US refund administration fee, P-ref-2), G3RZC8DVQCDTCQ3B, G200379860, G200453320 and GL7U4JFSDXUTQAJ. These are JS shells.
768
+ - The A-to-z search snippets for G27951, G202041210 and G202188810 (P-ref-9).
769
+ - The vendor pages behind P-ref-31 and P-ref-32.
770
+ - The practitioner values in P-ref-33 to 36 and 39. Only the wimoor and AU mappings were re-read, and only for the A-to-z, chargeback and SAFE-T rows.
771
+ - The Chinese media quotes.
772
+
773
+ **Cross-file disagreements for the lead.**
774
+ - `beyond/sellers-tools-and-research.md` line 23 labels 2025-01-15 as the US automation start. Amazon's earlier post (6605eede, posted 2024-07-24) gives 2024-11-01, and no page names the store. That file should carry both dates.
775
+ - `fulfilment-charges.md` and `sellers-tools-and-research.md` label the 2025-10-15 windows "(US)". The post (d8f9a56c) names no store and is written in British spelling.
776
+
777
+ **Gaps left.**
778
+ - The live G200213130 policy page and its per-claim windows (JS shell).
779
+ - Whether a granted A-to-z or chargeback debit returns the referral fee net of the administration fee on v0 and v2024-06-19, and which event returns a won chargeback.
780
+ - v2024-06-19 `transactionType` values for A-to-z and SAFE-T.
781
+ - A published crosswalk between reimbursement `reason`, settlement `amount-description` and ledger `Reason` (Amazon publishes none).
782
+ - An English-language Amazon page for the 45-day refund-not-returned rule (relayed only).
783
+
784
+ ### Gap fill (2026-11-10)
785
+
786
+ Depth gap named by the completeness critics: value recovered from returned or unsellable units through FBA Grade and Resell, FBA Donations and Amazon Resale, as money lines. The file did not cover it (liquidation is in `fulfilment-charges.md` and was not repeated). Method: plain GET of Seller Forums posts (posting dates from `datePublished`), sell.amazon.com blogs and developer-docs pages, stripped locally; `gh search code` and raw GETs of public GitHub files; greps over the models clone (db2936aa), `ops.tsv` and Role Mappings. No Amazon API host was called, no help-hub content call was made, nothing was written outside this file.
787
+
788
+ **Added.**
789
+ - Dated changes: a "Value-recovery dates" block (2024-08-07, 2025-02-24, 2025-09-11, 2025-09-30, 2025-10-30, 2026-02-03, 2026-03-09).
790
+ - § J (J1 Grade and Resell, J2 Donations and the 2025 enrolment changes, J3 Amazon Resale, J4 where recovered value shows), with Amazon's words from News posts, a staff post, sell.amazon.com and a relayed 2021 copy of the UK help page.
791
+ - § The SP-API and report faces: a value-recovery table (Finances/settlement rows by amzn.gr SKU, Orders `ConditionId`/`ConditionSubtypeId`, the Removal Order Detail report, Data Kiosk economics, the ledger) with roles.
792
+ - § What practitioners add: "Value-recovery SKUs and lines" (the amzn.gr SKU shape and its fragile join, how sellerboard, ConnectBooks, a DATEV exporter and a US dashboard book graded resales, vendor fee descriptions, seller reports, AMZ123).
793
+ - Stable enough 20–23; four run-time rows; one Seller-Central-only bullet; human-only figures (US processing fee table from Seller Labs, EU/UK fee notes, recovery percentages, one seller's fee share).
794
+ - Pages read: 17 rows. Open questions 16–20.
795
+ - Positions P-ref-42 to P-ref-51 (P-ref-51 is [seat]). None is a rule of behaviour; P-ref-46 and P-ref-48 leave costing and tax treatment to the seller.
796
+
797
+ **Gaps left.**
798
+ - The current Grade and Resell help page (GUA6RV6UA4DR2MFK) and FBA Donations help page (VCFMKLPUTBXE7L5): JavaScript shells. The money rules in J1 rest on a seller's 2021 copy of the UK page plus 2024–2026 News and blog posts.
799
+ - The current US Grade and Resell processing fee from an Amazon page: not found; only a vendor's table (Seller Labs, 2025-05-21).
800
+ - The settlement / Finances label of the Grade and Resell processing fee, and any public settlement or Finances file with an amzn.gr row: not found.
801
+ - A2X and Link My Books help on amzn.gr SKUs: not found by search. Chinese ERP (领星, 积加, 赛狐, 易仓) notes on amzn.gr SKU pairing: not found; only an AMZ123 news item.
802
+ - The staff answers in the Ask Amazon Grade and Resell thread (78c455ed): rendered only with JavaScript.
803
+ - An Amazon News post of the 2025-09-30 correction (US only; Donations from 2025-10-30): only the seller-relayed email.
804
+ - Amazon's own statement that Amazon Resale sells only Amazon Retail stock, and the aboutamazon rename post: only press coverage and search snippets.
805
+ - Whether FBA Donations runs outside the US, UK and France today, and the UK/FR disposal-fee basis for donated units.
806
+
807
+ ### Correction 1 (2026-11-10)
808
+
809
+ Brief 306 correction 1 and the plugin zen's item 4: a value that differs by marketplace or changes from year to year is looked up, not carried. Each position whose substance is such a value keeps the value as evidence and now ends with a "Read at run time:" sentence naming the operation (by its exact name, checked in the models clone db2936aa) or Amazon's page (title and URL) where it is read for the seller's own store. No other wording of a position was changed; nothing was renumbered or removed; nothing was re-researched. One plain GET confirmed that https://sellercentral.amazon.com/gp/help/external/G202188810 resolves (a JavaScript shell, as the other G-pages); no Amazon API host and no help-hub content call.
810
+
811
+ - **Positions changed (12):** P-ref-2 (refund administration fee rate and cap), P-ref-5 (seller-fulfilled four-calendar-day refund deadline), P-ref-9 (A-to-z 72-hour response, 30-day appeal), P-ref-10 (chargeback seven-day reply, 90-day outcome), P-ref-11 (US SAFE-T 30-day window), P-ref-16 (claim windows), P-ref-23 (`listTransactions` 0.5 rps / burst 10), P-ref-24 (v0 Finances 0.5 rps / burst 30), P-ref-37 (US missing-from-inbound nine months; 45-day replacement return), P-ref-40 ($5,000 per-unit cap; 60-day and 30-day dispute windows), P-ref-43 (Grade and Resell fees by store), P-ref-44 (2,000-ASIN inclusion limit).
812
+ - **Left as history or as no value:** the effective dates in P-ref-5, 6, 11, 12, 13, 14, 15, 38, 49 and the deprecation dates in P-ref-24 stay as facts of history; P-ref-6 and P-ref-12 state US rules with no figure.
813
+ - **Stable enough for a skill:** items 6, 7 and 8 carried the A-to-z response and appeal windows, the chargeback reply window and outcome time, and the US SAFE-T window; those values moved to three new rows of "What cx must read at run time", with where each is read.