@comchatx/cx-amazon-claims-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 (45) 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 +110 -4
  5. package/prompts/claims-audit.md +5 -0
  6. package/prompts/fee-check.md +5 -0
  7. package/prompts/inbound-shortfall.md +5 -0
  8. package/prompts/reimbursement-value.md +5 -0
  9. package/prompts/returns-check.md +5 -0
  10. package/skills/claim-filing/SKILL.md +46 -0
  11. package/skills/claim-filing/references/conduct.md +31 -0
  12. package/skills/claim-filing/references/filing.md +62 -0
  13. package/skills/claim-filing/references/no-door.md +34 -0
  14. package/skills/claim-filing/references/reads.md +79 -0
  15. package/skills/claim-filing/references/recovery.md +52 -0
  16. package/skills/claim-filing/references/windows-and-stores.md +28 -0
  17. package/skills/claim-value/SKILL.md +45 -0
  18. package/skills/claim-value/references/basis.md +25 -0
  19. package/skills/claim-value/references/disputes.md +29 -0
  20. package/skills/claim-value/references/lines.md +31 -0
  21. package/skills/claim-value/references/reversals.md +22 -0
  22. package/skills/claim-value/references/rule.md +31 -0
  23. package/skills/claim-value/references/sourcing-cost.md +43 -0
  24. package/skills/fee-claims/SKILL.md +43 -0
  25. package/skills/fee-claims/references/certification.md +29 -0
  26. package/skills/fee-claims/references/fee-kinds.md +76 -0
  27. package/skills/fee-claims/references/measurement.md +33 -0
  28. package/skills/fee-claims/references/reads.md +37 -0
  29. package/skills/fee-claims/references/windows.md +37 -0
  30. package/skills/return-claims/SKILL.md +37 -0
  31. package/skills/return-claims/references/edges.md +37 -0
  32. package/skills/return-claims/references/outcomes.md +48 -0
  33. package/skills/return-claims/references/reads.md +25 -0
  34. package/skills/return-claims/references/windows.md +24 -0
  35. package/skills/shipment-claims/SKILL.md +36 -0
  36. package/skills/shipment-claims/references/disposals.md +33 -0
  37. package/skills/shipment-claims/references/inbound-programs.md +33 -0
  38. package/skills/shipment-claims/references/inbound.md +49 -0
  39. package/skills/shipment-claims/references/reads.md +31 -0
  40. package/skills/shipment-claims/references/removals.md +49 -0
  41. package/skills/warehouse-claims/SKILL.md +45 -0
  42. package/skills/warehouse-claims/references/ledger.md +49 -0
  43. package/skills/warehouse-claims/references/paid-without-claim.md +66 -0
  44. package/skills/warehouse-claims/references/scope.md +57 -0
  45. package/skills/warehouse-claims/references/windows-and-idr.md +39 -0
@@ -0,0 +1,25 @@
1
+ # Unsellable units, post-order losses, customer returns and the cap
2
+
3
+ ## Unsellable units
4
+
5
+ - Pre-order units unsellable when lost, damaged or removed are reimbursed at "a reduced estimated cost"; Amazon may ask for documents to set it, and no page gives the reduction (VR25).
6
+ - Japan's texts state the reduced estimate for removal claims of unsellable items only (VR25).
7
+ - Post-order units unsellable when lost or damaged are reimbursed at "the discounted sale price of that order minus applicable fees", with VAT also out in the UK and DE (VR26).
8
+ - That post-order sentence was inserted in the 2024-12 to 2025-02 redlines for the US, CA, UK and DE; the JP texts of 2025-02-19 carry none (VR26).
9
+ - The self-service dispute workflow applies an approved cost to pre-order events reimbursed as "sellable", by US-store staff (VR21).
10
+
11
+ ## Post-order losses and customer returns
12
+
13
+ - The US, CA, UK and DE redlines (2024-12 to 2025-02, rendered) and the JP English text strike "refund amount or the … of the replacement item" and insert "sales", reading "the sales price on the original order minus applicable fees" (VAT also out in the UK and DE; consumption tax in JP) (VR27).
14
+ - The US and CA Chinese texts insert "销售" only (VR27).
15
+ - The live *FBA inventory reimbursement policy* page is one the seller sees signed in, unread by a permitted route; which basis a store applies today, and whether a partial refund sets the value, is read in Amazon's documents, not yet seen on a live account (VR27).
16
+ - Japan's two texts of the same date differ: the English strikes the refund amount and replacement price, the Japanese keeps both and adds the original order's sales price beside them ("元の注文の販売価格、返金額または交換商品の価格から、適用される手数料と消費税を差し引いたもの") (VR42).
17
+ - A US-store seller (2026-08-05) reports a materially-different customer return reimbursed through removal handling at sourcing cost, below the buy cost, rather than at the order basis (VR33).
18
+ - Which customer returns are owed: ../return-claims/SKILL.md.
19
+
20
+ ## The per-unit cap
21
+
22
+ - Amazon caps the reimbursement for a single unit, and the cap differs by store in amount and currency (VR29).
23
+ - The cap for a store is on *FBA inventory reimbursement policy*, which the seller sees signed in, and in Amazon's dated redline PDFs (2025-02-24; JP 2025-02-19), read by plain GET; no operation returns it (VR29).
24
+ - No cap was found in any text read for AU, MX, IN, BR or other stores (VR29).
25
+ - A line paid at the cap on a unit worth more is paid as the policy states (VR29).
@@ -0,0 +1,29 @@
1
+ # Disputing a value
2
+
3
+ ## The window
4
+
5
+ - Amazon sets a window for disputing a reimbursement's valuation (VR20).
6
+ - Every policy text read (US, CA, UK, DE, FR, IT, ES, JP, and the US and CA Chinese texts) counts it from the reimbursement's issue (VR20).
7
+ - The one News post that states a re-evaluation window, d8f9a56c (posted 2025-08-14), was issued for the Australia store and counts it from the initial claim (VR20).
8
+ - The UK's text changed its length between the UK PDF of 2024-12-11 and the redline of 2025-02-24, and the redline does not mark the change (VR20).
9
+ - The length for a store is on *FBA inventory reimbursement policy*, which the seller sees signed in, and in that store's latest Seller Forums News post on claim windows, read by plain GET (VR20).
10
+ - Which window the self-service workflow enforces for a store, and whether any store besides Australia counts from the claim, is read in Amazon's documents, not yet seen on a live account (VR20).
11
+ - Which store a News post was issued for: ../warehouse-claims/SKILL.md.
12
+
13
+ ## The routes
14
+
15
+ - Every route is the seller's step in Seller Central; no SP-API operation files a dispute (VR18, SU12).
16
+ - US-store staff name a self-service Get Help workflow, "Dispute a reimbursement claim": it applies an already approved MYSC cost to pre-order events reimbursed as "sellable", missing-from-inbound included (VR21).
17
+ - Staff also name a "reimbursement re-evaluation tool" at its own help-hub address; that it is the same workflow is inferred, not confirmed (VR21).
18
+ - US-store staff name "Submit a reimbursement claim dispute" under Get Help, where documents are uploaded for human review (VR21).
19
+ - A case reopening is a third path, which staff say is a different process (VR21).
20
+ - What each changes: the self-service route applies an approved cost to pre-order events reimbursed as "sellable"; the dispute under Get Help takes uploaded documents for human review; a case reopening is its own process; which route, and whether, is the seller's choice (VR21).
21
+ - The policy's repeat rule covers "reimbursement amount dispute[s]" as well as cost updates, with its period on the policy page (VR22).
22
+ - In one US-store thread (2026-05-25, 2026-06-05), a cost approved after a reimbursement was paid at the estimate was refused as a case adjustment "Since the reimbursement was processed before your sourcing cost was approved", and staff pointed to the self-service dispute within its window (VR23).
23
+ - One seller reports a dated US case where the cost-update lock outlasted the dispute window; this is the seller's account (VR24).
24
+
25
+ ## Reading a dispute's outcome
26
+
27
+ - The Support API (`listCases`, `getCase`) needs Selling Partner Support (Restricted), outside the five; it would open the status, dates and contacts of the seller's cases, and nothing is built on it (SU8, SU10).
28
+ - Whether it shows valuation-dispute cases and their outcome is read in Amazon's documents, not yet seen on a live account (SU8).
29
+ - Where a case is filed and its evidence: ../claim-filing/SKILL.md.
@@ -0,0 +1,31 @@
1
+ # Reading a reimbursement line
2
+
3
+ ## What the line carries
4
+
5
+ - `GET_FBA_REIMBURSEMENTS_DATA` answers to Pricing or Amazon Fulfillment (SU3).
6
+ - It carries no column for the valuation basis, the cost in force, the cap or the store (VR30).
7
+ - From those columns it follows that whether a line is low shows only beside a basis read elsewhere: MYSC in Seller Central, the seller's own cost, or the order's basis; this is inferred, not Amazon's statement (VR30).
8
+ - The report's columns and how a line posts to money: @comchatx/cx-amazon-finance-playbook, its refunds-and-reimbursements skill.
9
+
10
+ ## The basis a line should have
11
+
12
+ - Whether `Lost_Outbound` and `Damaged_Outbound` lines take the pre-order or the post-order basis is unread; read in Amazon's documents, not yet seen on a live account (VR31).
13
+ - An approved cost applies to reimbursements issued after its approval, so it follows, by inference, that the cost to compare a pre-order line with is the one in force when it was issued, not today's MYSC value (VR8, VR32).
14
+ - Where an order's sale price and fees are read: @comchatx/cx-amazon-finance-playbook, its refunds-and-reimbursements skill.
15
+ - A seller-entered cost from SKU Central and the Revenue Calculator sits in Data Kiosk Economics, which Amazon's correction says needs Selling Partner Insights, outside the five, while its Data Kiosk page lists Brand Analytics (VR19, SU33).
16
+ - A materially-different return reported paid at sourcing cost: references/basis.md.
17
+
18
+ ## Units against cash
19
+
20
+ - Amazon may settle a valid claim by replacing the unit "with a new item of the same FNSKU" instead of paying, and such a line moves units, not money (VR34).
21
+ - What `amount-per-unit` and `amount-total` carry on a line with units put back is read in Amazon's documents, not yet seen on a live account (VR34).
22
+ - A unit put back arrives in the ledger as an N or O row: references/reversals.md.
23
+
24
+ ## Store and currency
25
+
26
+ - The report carries `currency-unit` per line and no store column; Finances v0 `AdjustmentEvent` carries `StoreName` and an ISO 4217 `CurrencyCode` per amount, with no marketplace id (VR43, SU52).
27
+ - No Amazon text read says in which store and currency a reimbursement posts for a unit lost in a Pan-European transfer, in another country's FC under EFN, or in US stock sold through Remote Fulfillment, or in which store its value is disputed; this is read in Amazon's documents, not yet seen on a live account (VR43).
28
+ - A developer reports that the report returns the same rows whatever `marketplaceIds` names (SU24).
29
+ - A sourcing cost is entered per marketplace, and the proof-of-value list asks for the currency of the transaction (VR7, VR13).
30
+
31
+ How a call is made and a report is asked for and landed: the amazon-sp-api skill's references/door.md.
@@ -0,0 +1,22 @@
1
+ # Reversals and found units
2
+
3
+ ## Amazon's rule
4
+
5
+ - Amazon's policy names two grounds for reversing a reimbursement: it was made in error, or the reimbursed item was found and returned to inventory (VR36).
6
+ - The policy states no time limit for a reversal and no rule for the amount reversed, in its English, Chinese and Japanese texts (VR36).
7
+ - Whether a reversal's amount ever differs from the original `amount-total`, and whether every reversal has a matching ledger row, is read in Amazon's documents, not yet seen on a live account (VR36).
8
+ - US-store staff send a seller who doubts a reversal to the inventory ledger, to see whether the units were added back, and to Seller Support; no staff post names a dispute window for a reversal (VR37).
9
+ - Raising a reversal with Seller Support is the seller's step in Seller Central; no SP-API operation does it (SU12).
10
+
11
+ ## What sellers report
12
+
13
+ - US-store sellers report reversals months after payment, in one thread more than a year after, including a unit "damaged" in the FC later reversed and added back as sellable, and bulk reversals with no unit visible as returned (VR38).
14
+
15
+ ## In the data
16
+
17
+ - An FBA reversal shows as report reason `Reimbursement_Reversal` and in settlement descriptions (VR39).
18
+ - Finances v0 `ReimbursementClawback` is an India-only Easy Ship value and does not mark FBA reversals (VR39).
19
+ - Ledger codes N and O move units "because you received an Amazon reimbursement" or "because Amazon has reimbursed you for them", so a row that adds units back is not always a physical find; read from that wording, N or O is an ownership move tied to a reimbursement, F a find (VR40).
20
+ - The ledger's codes in full: @comchatx/cx-amazon-stock-playbook, its stock-position skill.
21
+ - A reversal's report columns and settlement lines: @comchatx/cx-amazon-finance-playbook, its refunds-and-reimbursements skill.
22
+ - Found units netted against lost ones: ../warehouse-claims/SKILL.md.
@@ -0,0 +1,31 @@
1
+ # The valuation rule, dated
2
+
3
+ ## Before the move to sourcing cost
4
+
5
+ - Before the 2025 change, pre-order losses (shipment to Amazon, FC operations, removals) were valued at "estimated proceeds": an estimated sale price from median and list prices, "minus referral fees and fulfillment fees" (VR1).
6
+ - Amazon's redlines strike that whole block, so it was the pre-2025 pre-order method, not a post-order rule (VR1).
7
+ - Amazon's redlined policy PDFs keep struck text in their text layer: a text extraction mixes old and new wording, and only a rendering shows which is live (VR28).
8
+
9
+ ## Sourcing cost
10
+
11
+ - Pre-order losses are valued at sourcing cost from the date each store's text gives; the redlines regenerated on 2025-02-24 for the US, CA, UK, DE, FR, IT and ES, and the US and CA Chinese texts, carry a start after 2025-03-31 and the page name "Manage Your Sourcing Cost" (Chinese: 管理您的采购成本) (VR2).
12
+ - The FR, IT and ES redlines were read from their text layers only, not rendered (VR2).
13
+ - Amazon's US definition is the "cost to source a product from a manufacturer, wholesaler, or reseller, or to produce the item"; the first UK draft (2024-12-11) read "the cost to acquire, purchase, or produce the item", and the UK's 2025-02-24 text uses the US wording (VR3).
14
+ - Shipping, handling and customs duties are excluded in every version, Japan's included (VR3).
15
+ - Sourcing-cost valuation also covers losses "during inventory replenishment handled by Amazon or on behalf of Amazon to fulfillment centers or non-Amazon buildings in marketplaces where we provide the service" (VR4).
16
+ - The current text of *FBA inventory reimbursement policy* (G200213130) is a help page the seller sees signed in; cx reads the dated redline PDFs on m.media-amazon.com by plain GET (VR2, VR29).
17
+
18
+ ## Amazon's estimate
19
+
20
+ - Amazon's estimate is built from "comparable products sold by Amazon, by other sellers, and through other wholesale channels"; a declined seller cost leaves the previously approved amount or the estimate in force (VR5, VR9).
21
+ - From a date each store's text gives, Amazon refreshes its estimates periodically, alerts a seller whose provided cost is affected, and marks impacted items in MYSC's status column (VR5).
22
+ - Amazon states that a seller's cost data "is not shared with any other seller in Amazon's store, including Amazon Retail" (VR6).
23
+ - No SP-API operation reads or writes MYSC, and no model in Amazon's SP-API models holds a sourcing-cost field (VR18).
24
+
25
+ ## Japan
26
+
27
+ - Amazon's JP policy, in English and Japanese texts created 2025-02-19, values shipment-to-Amazon, removal and FC-operations claims at the item's sourcing cost ("原価"), entered on the IDR portal's "Manage Your Sourcing cost" page ("原価の管理"), with Amazon's estimate otherwise (VR41).
28
+ - The JP texts carry the same decline reasons and repeat rule, a per-unit cap in yen, and a valuation-dispute window counted from the reimbursement (VR41).
29
+ - The JP texts date the estimate refresh from 2025-04-01 and give no start date for the valuation itself (VR41).
30
+ - Whether the JP portal shows the 原価の管理 page today, and whether the JP live policy keeps the 2025-02-19 text, is read in Amazon's documents, not yet seen on a live account (VR16, VR41).
31
+ - The JP English and Japanese texts differ on the customer-return basis: references/basis.md.
@@ -0,0 +1,43 @@
1
+ # Manage Your Sourcing Cost
2
+
3
+ ## What it holds
4
+
5
+ - MYSC holds one sourcing cost per FNSKU per marketplace, chosen on a marketplace dropdown (VR7).
6
+ - A US-store staff post of 2026-04-10 says the page lists active FNSKUs "with planned shipments or current inventory", and in the same post that new ASINs appear only once "fully received and processed"; the two sentences disagree, and both are Amazon's (VR7).
7
+ - In US-store staff posts and relayed replies (2026-02 to 2026-05), an approved cost applies automatically to eligible pre-order reimbursements issued after its approval date; it does not revalue earlier ones and is not re-submitted periodically (VR8).
8
+ - MYSC shows only the current value and its last update, by one seller thread; whether the cost in force at a past date can be read anywhere is read in Amazon's documents, not yet seen on a live account (VR32).
9
+ - MYSC is evidenced for the US, CA, UK, DE, FR, IT, ES and JP (VR16).
10
+ - Entering or updating a cost is the seller's step in Seller Central; no SP-API operation reads or writes MYSC, and no model holds a sourcing-cost field (VR18, SU12).
11
+
12
+ ## Declines and limits
13
+
14
+ - Amazon may decline a cost for four policy reasons: an outlier, forged or illegible documents, an account suspected of fraud or violations, and a repeat within a stated period of a decision without new information (VR9).
15
+ - A declined submission leaves the previously approved amount or Amazon's estimate in force (VR9).
16
+ - The repeat period is on *FBA inventory reimbursement policy*, which the seller sees signed in, and in the dated redlines cx reads by plain GET (VR9, VR22).
17
+ - A US-store staff post (2025-11-25) says a value Amazon's system judges an outlier is rejected automatically, with no step to upload an invoice (VR10).
18
+ - US- and UK-store staff posts (2025-11-25, 2026-01-15) say Amazon does not tell the seller why an invoice was or was not accepted (VR10).
19
+ - The entered cost must equal the figure on the proof-of-value document; a mismatch is itself a decline reason (VR12).
20
+ - Amazon limits cost updates per FNSKU within a period: a Canada-store Seller Support reply relayed on 2025-03-19 and US-store staff posts of 2025-11-25 to 2026-02-24 state different counts, and no source read settles whether the count changed over time or differs by store (VR11).
21
+ - The count for a store is on the help page *Manage Your Sourcing Cost*, which the seller sees signed in, and a refusal shows in MYSC's Update status column as "Number of attempts exceeded"; which count holds today is read in Amazon's documents, not yet seen on a live account (VR11).
22
+ - Amazon states a maximum age for a proof-of-value invoice; two US-store staff posts (2025-06-12, 2025-12-01) state different ages, neither cites the help page, and which holds today is read in Amazon's documents, not yet seen on a live account (VR14).
23
+ - One seller reports a dated US case (2025-10-23) where a decline under the attempt lock outlasted the dispute window counted from the reimbursement; this is the seller's account (VR24).
24
+
25
+ ## Proof of value
26
+
27
+ - The fields Amazon's help page lists, as a seller copied it from the Canada store (2025-03-19): document name, number and date; the buyer entity as registered with Amazon, its address and tax ID; the issuer's name, address and ID; product code, description and quantity; the per-unit or net cost; the currency (VR13).
28
+ - Accepted documents, by that copy: manufacturer, wholesaler, purchase or commercial invoices; staff also name retail receipts, and a pro forma with proof of payment; formats in that copy are PDF, JPG, JPEG and PNG (VR13).
29
+ - For self-manufactured goods, staff name an internal cost document showing product, unit cost and date, component invoices with a cost breakdown, and a Seller Support case for manual review (VR15).
30
+ - A practitioner, Eagle Eye (2026-09-12), reports a multi-product invoice refused because the FNSKU's line could not be isolated, and the same invoice accepted through a support case with the line highlighted (VR17).
31
+
32
+ ## Chinese sellers' cost proofs
33
+
34
+ - Amazon's list asks for the buyer to be "your business name registered with Amazon" and for the currency of the transaction, and staff say the business name on the invoice "must exactly match your Amazon registration" (VR44).
35
+ - No Amazon text read states a required language, or rules on a mainland VAT invoice (发票), a 1688 order receipt or a payment-platform receipt; which of these Amazon accepts is read in Amazon's documents, not yet seen on a live account (VR44).
36
+ - An invoice whose buyer is a different entity from the selling account, such as a Hong Kong or mainland purchasing company buying for a US LLC, does not show the registered business as buyer; this is inferred from the field, not an Amazon ruling (VR44).
37
+ - Chinese practitioners (贾科斯 of 易销AI, 2025-08-07, Canada and Germany cases; AMZ123, 2024-12-27) report Chinese-language invoices refused and English ones accepted, and name these choices side by side, as theirs: a mainland VAT invoice (专票 or 普票) verifiable on the State Taxation Administration's check site; an English commercial invoice from the supplier in the store's currency with the supplier's tax number; a commercial or pro forma invoice from the supplier or forwarder; a contract with payment record and stamped receipt; customs papers, one of which a Canada-store case saw refused as unclear (VR45).
38
+
39
+ ## Another cost Amazon holds
40
+
41
+ - Data Kiosk `analytics_economics_2024_03_15` carries a seller-entered `cost.costOfGoodsSold`, which Amazon says comes from SKU Central and the Revenue Calculator, not MYSC (VR19).
42
+ - Whether that cost and the MYSC cost are one value is read in Amazon's documents, not yet seen on a live account (VR19).
43
+ - Amazon's correction page and its developer support (2025-04-23) say the Economics dataset needs Selling Partner Insights, a role outside the five, while the Data Kiosk and operations pages still list Brand Analytics; that read would open the `cost.costOfGoodsSold` field (VR19, SU33).
@@ -0,0 +1,43 @@
1
+ ---
2
+ name: fee-claims
3
+ description: "Whether an Amazon fee a seller was charged had a basis in Amazon's own rule, and what Amazon says about getting it back: FBA fulfilment, storage, returns and placement fees on a wrong measurement or size tier, Amazon's measurement against the seller's, remeasurement, the EU dimensions certification regime and its look-back, the itemised and non-itemised fee-error windows by store, one claim per charge, a referral fee on the wrong category, low-price FBA not applied, placement fees against the quote, partnered-carrier charges, the low-inventory-level fee, storage on lost, researching or stranded units, removal and disposal fees with no unit, unplanned prep, the inbound defect fee, AWD box fees, and what the Fee Preview, Storage Fees and Inbound Performance reports show. For any question about a fee that looks too high, a size tier that changed, a remeasure, or whether an overcharge can still be disputed in the seller's store."
4
+ ---
5
+
6
+ ## What counts
7
+
8
+ In this skill an overcharge is a fee charged on a basis Amazon's own rule did not support; a rise from an announced rate change, peak, surcharge or price band is not one (FE1, FE20).
9
+ Rates, fee lines and where each charge posts: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
10
+
11
+ ## Measurement
12
+
13
+ Outside EU certification, the measurement Amazon verifies sets every size-tier fee (FE2).
14
+ Each variation is its own product (FE3).
15
+ The SP-API Fee Preview keeps no history, and Velocity Sellers holds that Amazon sends no notice of a remeasure (FE19).
16
+ On Amazon.de and, from 2026-05-05, amazon.co.uk, .fr, .it and .es, certified seller dimensions set the fee; Amazon states an automatic look-back true-up for Amazon.de, and no Amazon page read states one for the US (FE5, FE6, FE7).
17
+ After a US remeasure, staff described past fees credited per order (2025-02-05); US sellers report refusals after a confirmed wrong measurement (FE13, FE14).
18
+
19
+ ## Windows
20
+
21
+ Amazon staff state a window from each charge's date for itemised FBA fee errors and a longer limit for non-itemised ones (US-store guide 2026-04-17, UK-store copy 2026-05-13); lengths: *FBA fees reimbursement policy: Weight and dimensions*, seen signed in, and the store's latest staff guide, read by plain GET (FE9).
22
+ Amazon allows one claim per fee charge under the weight-and-dimension and referral-fee policies; Amazon removed the referral-fee dispute window on 2022-03-16 (FE11, FE22).
23
+
24
+ ## The seller's steps
25
+
26
+ No SP-API operation requests a remeasurement, certifies dimensions or disputes a fee; each is the seller's step in Seller Central, an FBA fee error by the staff guide's "Fees Charged in Error" case (FE4, FE6, FE37, SU12).
27
+
28
+ ## Reads
29
+
30
+ Amazon's measurement on file is in `GET_FBA_ESTIMATED_FBA_FEES_TXT_DATA` and `GET_FBA_STORAGE_FEE_CHARGES_DATA` (Pricing or Amazon Fulfillment); a charge's date is `postedDate` in Finances `listTransactions` (Finance and Accounting) (FE17, FE9).
31
+ Data Kiosk `economics` would date a tier change but needs Selling Partner Insights, outside the five roles (FE18, FE50).
32
+ How calls and reports are made: the amazon-sp-api skill's references/door.md.
33
+
34
+ ## References
35
+
36
+ [measurement.md](references/measurement.md): measurement, remeasurement.
37
+ [certification.md](references/certification.md): EU certification.
38
+ [windows.md](references/windows.md): windows, referral fees, the route.
39
+ [fee-kinds.md](references/fee-kinds.md): low-price, placement, carrier, low-inventory, storage, removal, returns, prep, defect, AWD fees.
40
+ [reads.md](references/reads.md): reports, pitfalls, detection methods.
41
+ [claim-filing](../claim-filing/SKILL.md): case routes, evidence, conduct.
42
+ [claim-value](../claim-value/SKILL.md): what a reimbursement is worth.
43
+ [warehouse-claims](../warehouse-claims/SKILL.md), [shipment-claims](../shipment-claims/SKILL.md), [return-claims](../return-claims/SKILL.md): the units themselves.
@@ -0,0 +1,29 @@
1
+ # The EU certification regime
2
+
3
+ ## History
4
+
5
+ - From 2025-08-01, sellers with a German business address were asked to certify package dimensions for Amazon.de, as Valuezon relays Amazon (FE5).
6
+ - Amazon's Global Selling notice of 2026-03-06 called for certified dimensions on existing Amazon.de ASINs, large and heavy bulky items excluded, by a date stated on the notice (FE5).
7
+ - From 2026-05-05, certified dimensions calculate FBA fees on amazon.co.uk, amazon.fr, amazon.it and amazon.es, by Amazon's policy PDF created 2026-03-30 (FE5).
8
+ - cifnews and 九方 relay a standard-size phase and a large-item phase for the UK, France, Italy and Spain; those are their relays, not an Amazon post read (FE5).
9
+
10
+ ## The rules
11
+
12
+ - Certified means measured with a device that complies with the EU Measuring Instruments Directive, a tape measure among them (FE6).
13
+ - Existing dimensions not verified by the store's deadline are deemed certified, and new listings carry certified dimensions; on Amazon.de the dimensions entered at listing creation are the basis (FE6).
14
+ - Amazon validates the dimensions and may replace incorrect ones with its own certified dimensions; the seller's appeal goes through the remeasure widget, within the monthly limit (FE6).
15
+ - Certifying and appealing are the seller's steps in Seller Central; no SP-API operation shows or sets an ASIN's certification status (FE6, SU12).
16
+ - The stores, tiers and deadlines in scope are read on Amazon's *FBA item package dimensions certification policy* PDF and the Global Selling notice, both read by plain GET (FE5, FE6).
17
+
18
+ ## The look-back true-up
19
+
20
+ - Amazon's Amazon.de notice states that certified dimensions that lower FBA fees bring an automatic true-up of the difference for a stated look-back, worded for items sold on Amazon.de (FE7).
21
+ - Practitioners (cifnews, 九方) relay the same true-up for the UK, France, Italy and Spain; no Amazon page read states one for the US (FE7).
22
+ - The look-back length for the seller's store is read on that store's certification notice (FE7).
23
+ - How the true-up posts (one adjustment or per order, under which name, and whether it covers storage) is read in Amazon's documents, not yet seen on a live account (FE7).
24
+
25
+ ## The contradiction on storage
26
+
27
+ - Amazon's *Rate Card Europe Fees*, effective 2026-11-02, says Amazon's measurement governs storage volume (FE8).
28
+ - The certification policy says certified seller dimensions calculate "FBA fees" in the UK, France, Italy and Spain from 2026-05-05 (FE8).
29
+ - No page read says whether storage falls under certification; both texts stand with their dates (FE8).
@@ -0,0 +1,76 @@
1
+ # Fee kinds beyond measurement
2
+
3
+ ## Low-price FBA
4
+
5
+ - Amazon's Spain low-price FBA page (2026) says low-price FBA rates apply automatically to eligible units, with no enrolment; that a unit eligible on Amazon's stated criteria but charged the standard rate is a fulfilment-fee overcharge is the research's inference (FE31).
6
+ - The price thresholds and size limits by store are read on the store's low-price FBA page on sell.amazon.<tld>, read by plain GET (FE31).
7
+ - The US low-price FBA rule: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
8
+ - No Amazon page read states which price, at which moment, decides eligibility: read in Amazon's documents, not yet seen on a live account (FE31).
9
+ - Small and Light closed in 2023; the research reads a former Small and Light unit's fee under low-price FBA or the standard rate, with no separate claim of its own (FE49).
10
+ - No Amazon page read names a fee claim of Subscribe & Save's own; its fees are the order's fee lines, under the kinds here (FE48).
11
+
12
+ ## Inbound placement
13
+
14
+ - The placement fee shown in the shipping workflow is an estimate; the fee is charged a stated span after receipt, on the inbound location and the quantities received (US-store staff posts, 2024) (FE25).
15
+ - The no-fee optimized option needs compliance, including a stated minimum of identical cartons or pallets per item; the timing and the minimum are on Seller Central's *FBA inbound placement service fee*, which the seller sees signed in (FE25).
16
+ - The quote is `listPlacementOptions` (Amazon Fulfillment); plan compliance by plan, shipment and SKU is in Seller Central's placement fee report only (FE25).
17
+ - Amazon staff direct a seller to a Seller Support case when a placement fee is charged on a shipment never received; no page read says whether a lost-unit reimbursement includes the placement fee paid on that unit (FE26).
18
+
19
+ ## Partnered-carrier charges
20
+
21
+ - From 2025-06-12, on domestic US partnered-carrier shipments, a difference between the seller-entered and the carrier-measured weight, dimensions or freight class brings a credit or a charge, shown in the Inbound Performance dashboard; sellers report their disputes of such charges rejected (FE27).
22
+ - Confirming a partnered-carrier option agrees to its charge; voiding within the option's window refunds it in full, outside it charges "may apply", and a non-partnered shipment can be voided at any time (FE43).
23
+ - The window is `Quote.voidableUntil` from `listTransportationOptions` (Amazon Fulfillment), and `cancelInboundPlan` cancels the whole plan (FE43).
24
+ - No Amazon text read refunds a partnered charge once the void window has passed when the carrier never collected; UK sellers report Seller Support declining, and GETIDA and Threecolts list the kind as their own claim type (FE44).
25
+ - Amazon's staff guide names partnered-carrier charges in neither fee class, so no page read states their filing limit; which limit the "Fees Charged in Error" route applies is read in Amazon's documents, not yet seen on a live account (FE44).
26
+
27
+ ## Low-inventory-level fee
28
+
29
+ - Amazon credits low-inventory-level fees caused by Amazon or Amazon-managed inbound and processing delays, monthly, by a stated day of the following month (US-store News post, 2024-05-02) (FE28).
30
+ - The credit's timing and conditions are on Seller Central's *Low-inventory-level fee*, which the seller sees signed in; how much of a delay the credit covers is stated on no page read (FE28).
31
+ - The weekly fee flag and exemption per SKU are in `GET_FBA_INVENTORY_PLANNING_DATA` (Amazon Fulfillment) (FE28).
32
+
33
+ ## Storage on units Amazon no longer stores
34
+
35
+ - A US-store staff reply of 2025-04-30 says storage stops promptly once a unit is identified as lost or damaged; a storage line on units already adjusted out has no basis in that statement (FE38).
36
+ - No Amazon text read says whether storage charged between a loss and its identification is refunded, or whether a lost-unit reimbursement covers fees paid on the unit (FE38).
37
+ - A US-store staff reply of 2025-06-27 says no storage is charged on units in a created removal order during its processing (FE40).
38
+ - No Amazon text read says whether researching units bear storage (FE39).
39
+ - Whether the storage report's `average_quantity_on_hand` counts researching, lost or removal-pending units is read in Amazon's documents, not yet seen on a live account (FE39, FE40).
40
+ - Amazon names system errors among the causes of stranding, but no Amazon text read refunds storage on stranded units, and a seller's direct question drew no staff answer (FE42).
41
+ - Whether storage on stranding Amazon caused is ever credited, and by which route, is read in Amazon's documents, not yet seen on a live account (FE42).
42
+ - The units lost or damaged and their dates: ../warehouse-claims/SKILL.md.
43
+
44
+ ## Removal and disposal fees
45
+
46
+ - A removal or disposal fee error is a non-itemised FBA fee error under the staff guide's longer limit (FE41).
47
+ - Removal and disposal fees post per unit from a change date per store, read on each store's News post by plain GET; under per-unit charging, a fee with no matching shipped or disposed unit has no basis in Amazon's stated rule, by the research's reading (RM26, RM27).
48
+ - No Amazon text read says whether the reimbursement for a removal lost in transit includes the removal fee paid on it; vendors list "Lost Removal Order" as a claim for the units (FE41).
49
+ - The removal itself as a claim: ../shipment-claims/SKILL.md.
50
+
51
+ ## Returns processing fee
52
+
53
+ - Whether the per-return fee or the high-return-rate rule applies follows the product's category assignment, which Amazon decides; a support reply, as a seller relays it, held a shoe-care product to be in the shoes class and the fee accurate (FE29).
54
+ - Charged returns-fee units cannot be matched to individual returns from any report found: sellers report Seller Central's returns-fee report has no order numbers, and no SP-API report breaks the fee down (FE30).
55
+ - The returns fee's classes and thresholds: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
56
+
57
+ ## Unplanned prep and labelling
58
+
59
+ - Amazon applies prep or labels a shipment lacked, charges a fee per unit and flags the defect in the Inbound Performance dashboard; units with missing or defective labels are not eligible for reimbursement (FE45).
60
+ - Staff name the problems tab under the shipment summary as the route for disputing the fee, a seller's step in Seller Central (FE45).
61
+ - The dispute limit is stated two ways and both stand: from when the problem is reported, on the unread *Unplanned services* help page by search summary only; and under the staff guide's non-itemised limit (FE45).
62
+ - Which of the two a dispute meets in practice is read in Amazon's documents, not yet seen on a live account (FE45).
63
+ - Each fee per shipment, carton and FNSKU is in `GET_FBA_FULFILLMENT_INBOUND_NONCOMPLIANCE_DATA` (`problem-type`, `fee-type`, `fee-total`; Pricing or Amazon Fulfillment) (FE45).
64
+
65
+ ## Inbound defect fee
66
+
67
+ - By a US-store News post of 2026-10-30, Amazon waived the deleted or abandoned defect fee for international plans whose remaining shipments arrived within a stated span of the first receive, and reimbursed fees already charged without a claim, shown in the Reimbursements report (FE46).
68
+ - The waiver's scope is read on that News post by plain GET; no dispute window for the defect fee was found (FE46).
69
+ - Under which `reason` the credit appears in `GET_FBA_REIMBURSEMENTS_DATA`, and whether it carries the shipment ID, is read in Amazon's documents, not yet seen on a live account (FE46).
70
+
71
+ ## AWD box-dimension fees
72
+
73
+ - For AWD storage and transportation fees only, Amazon reimburses the difference between the fees charged and the fees on corrected box measurements; Amazon's measurement governs, and a box remeasure is limited per box and period (FE47).
74
+ - The request is filed within a window counted from the charge date, one claim per fee charge, to Amazon Support or the account manager as a research request, the seller's step (FE47, IN33).
75
+ - The window and limits are read on the dated *Amazon Warehousing & Distribution Service Terms* on supplychain.amazon.com, read by plain GET (FE47).
76
+ - AWD is not readable on the five roles (FE47).
@@ -0,0 +1,33 @@
1
+ # Measurement and remeasurement
2
+
3
+ ## Whose measurement sets the fee
4
+
5
+ - In this skill's grouping, a wrong measurement or size tier is one kind of overcharge; fulfilment, storage, aged-inventory, returns, removal and placement fees ride on it (FE1).
6
+ - Outside the EU certification regime, the weight and dimensions Amazon verifies set every size-tier-based fee (FE2).
7
+ - A US-store staff reply of 2023-11-14 says personal measurements are not accepted to contest a measurement, and that inconsistent FC measurements resolve to the largest (FE2).
8
+ - Amazon staff state that the measurement includes the packaging and loose bag flaps and handles, measured edge to edge, and name the packing material as the most common cause of seller-versus-FC differences (US-store staff posts, 2024-08-22 and 2025-04-30) (FE36).
9
+ - A packaging change after first receipt is a cause practitioners name for remeasures; that is Velocity Sellers' reading, not Amazon's (FE36).
10
+ - Each variation is its own product: one variation's fee is no evidence for another, and sellers report remeasures that changed one colour or size and not its siblings (FE3).
11
+ - In EU stores under certification the seller's certified dimensions set the fee instead: references/certification.md.
12
+ - The dimensional-weight divisor and size-tier rates by store: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
13
+
14
+ ## Remeasurement
15
+
16
+ - A remeasure needs a sellable unit in an FC; Amazon refuses one for an FNSKU remeasured a stated number of times in a stated period, or once the account's monthly limit is used (US-store staff posts, 2024-09-20 and 2025-04-30) (FE4).
17
+ - Amazon asks that only requests expected to change fees be filed, and a staff post says staff can add a request beyond the monthly limit when given a case ID (FE4).
18
+ - The per-FNSKU limit is on Seller Central's *Understanding item package weight and dimensions*, which cx cannot read and the seller sees signed in; the account's remaining count shows only in the Seller Central widget (FE4).
19
+ - No Amazon text read names a number for the monthly account limit; the practitioners' figures differ from one another and are theirs (FE4).
20
+ - Amazon states review times only for a few kinds, remeasurement among them, each on its own page (FL30).
21
+ - Requesting a remeasure is the seller's step in Seller Central; no SP-API operation requests or reads one (FE4, SU12).
22
+ - A US staff member called remeasurement a step before a successful fee reimbursement, in a case where Seller Support had set a wait before the remeasure; that is one statement, with no rule page behind it (FE12).
23
+
24
+ ## What follows a remeasure
25
+
26
+ - Amazon staff described a dimension correction paid as one "Fee Adjustment - Weight and Dimension Change" entry per affected order, under Transaction Type "Other" in Seller Central's Transaction View, with no reimbursement ID (US forum, thread of 2025-02-05) (FE13).
27
+ - So such a credit does not appear in `GET_FBA_REIMBURSEMENTS_DATA` under a reimbursement ID (FE13).
28
+ - The per-order entry is read in Amazon's documents, not yet seen on a live account; how it is typed in `listTransactions` and in settlement V2 is stated on no page read (FE13).
29
+ - US sellers report refusals, or no reimbursement, after Amazon confirmed a wrong measurement; in one thread staff advised a new case asking for an order-level audit and refund (FE14).
30
+ - Velocity Sellers, Leviathan Sellers, My Amazon Guy and Notifcentral each hold that a remeasure fixes future fees only; that is their reading (FE14).
31
+ - Whether any US fee adjustment posts by itself after a remeasure that lowers a tier, or only on request, is read in Amazon's documents, not yet seen on a live account (FE13, FE14).
32
+ - In one 2025 case, as a seller relays it, Selling Partner Support asked for a file listing, per FNSKU, the incorrect fee, the correct fee, the difference and the total; Amazon's staff guide asks for shipment IDs, FNSKUs and evidence such as measurements and photos (FE15).
33
+ - Case mechanics and the conduct Amazon penalises: ../claim-filing/SKILL.md.
@@ -0,0 +1,37 @@
1
+ # Reads, their pitfalls, and detection methods
2
+
3
+ ## The measurement Amazon used
4
+
5
+ - `GET_FBA_ESTIMATED_FBA_FEES_TXT_DATA` carries Amazon's dimensions and weight per SKU, `product-size-tier` in the US only and `product-size-weight-band` in the EU; it is a current snapshot (FE17).
6
+ - Its refresh interval and request limit are on the report's own entry in *FBA Reports* (SU20).
7
+ - `GET_FBA_STORAGE_FEE_CHARGES_DATA` carries dimensions, weight, `item_volume` and `product_size_tier` per FNSKU, FC and `month_of_charge`; both reports answer to Pricing or Amazon Fulfillment (FE17).
8
+ - Amazon keeps no history in the Fee Preview, and Velocity Sellers holds that Amazon sends no notice of a remeasure; so on the five roles a tier change is dated only by comparing dated copies of the report the reader kept (FE19).
9
+ - `getMyFeesEstimateForSKU` uses Amazon's measured dimensions once units are received and `getMyFeesEstimateForASIN` the catalogue size; the research reads a different fulfilment fee between them at one price as a sign the two differ (FE21).
10
+ - The SP-API Fee Preview has `product-group` and `estimated-referral-fee-per-unit` but no fee-category column, though Amazon's 2022 post says Seller Central's Fee Preview shows upcoming category changes (FE24).
11
+ - Whether the assigned fee category can be read through any SP-API surface is read in Amazon's documents, not yet seen on a live account (FE24).
12
+
13
+ ## Pitfalls in the money
14
+
15
+ - A fulfilment fee rises without any measurement change across the holiday peak, the fuel and logistics surcharge, a price-band crossing and an annual fee change (FE20).
16
+ - The dates of Amazon's fee changes and peak periods: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
17
+ - Fee corrections reach the seller's records under names Amazon does not list (`Fee Adjustment`, `INCORRECT_FEES_ITEMS`, `INCORRECT_FEES_NON_ITEMIZED`, `NonSubscriptionFeeAdj`, `RE_EVALUATION`), as vendors report them (FE33).
18
+ - Whether the two `INCORRECT_FEES_*` names match Amazon's itemised and non-itemised classes, and where they appear, is read in Amazon's documents, not yet seen on a live account (FE33).
19
+ - Finances reaches further back than the itemised window (FE32).
20
+
21
+ ## Outside the five roles
22
+
23
+ - Data Kiosk `economics` returns charged fees per product per date range with the properties that set them, Product Size Tier among them, split at Amazon fee-change dates; it would date a tier change (FE18).
24
+ - It needs Selling Partner Insights, a role outside the five, so nothing here is built on it; its start-date limit and retention are in the dataset's schema (FE50, SU33, SU34).
25
+ - On the five roles the same questions are read from dated Fee Preview copies, the Storage Fees report, Finances and the Inbound Performance and Reimbursements reports (FE50).
26
+
27
+ ## Practitioners' detection methods, side by side
28
+
29
+ | Choice | Expected fee from | Charged fee from | Flagged when | Whose (FE34) |
30
+ |---|---|---|---|---|
31
+ | Order-level difference, seller-kept expected fee | Amazon's estimate or the seller's own carton figures under the store's rates | the order's fee | any difference, valued as (charged − expected) × quantity | 领星 Lingxing (FE34, SU44) |
32
+ | Order-level difference against Amazon's estimate | the fee report's estimate | the order's fee | a difference above the vendor's own default, on recently shipped orders | 赛狐 Sellfox (FE34) |
33
+ | Baseline and diff | a dated earlier Fee Preview copy | the current copy | the fee moved with no price change | Velocity Sellers; My Amazon Guy; Notifcentral (FE34) |
34
+ | SKU estimate against ASIN estimate | `getMyFeesEstimateForASIN` | `getMyFeesEstimateForSKU` | the two differ at one price | the research's reading of Amazon's documentation (FE34, FE21) |
35
+
36
+ - Each method is its vendor's or practitioner's; none is Amazon's (FE34).
37
+ - Reported effects are single cases only, with no study of how often or how large overcharges are (FE35).
@@ -0,0 +1,37 @@
1
+ # Windows, one claim per charge, and the route
2
+
3
+ ## The two FBA fee windows
4
+
5
+ - Itemised FBA fee errors are fees tied to an ASIN or FNSKU, typically from weight or dimension errors: fulfilment, customer returns, monthly storage and long-term storage; their window is counted from each charge's date (FE9, FE16).
6
+ - Non-itemised FBA fee errors, such as removal or destroy order fees and prep and labelling fees, fall under a separate, longer limit (FE9, FE41).
7
+ - Amazon staff stated both in a US-store guide of 2026-04-17 and in a UK-store copy of 2026-05-13; no length was read for JP, CA, AU, IN, MX or any other store (FE9).
8
+ - Today's lengths for the seller's store are on Seller Central's *FBA fees reimbursement policy: Weight and dimensions*, which cx cannot read and the seller sees signed in, and on the store's latest Amazon staff guide on disputing charges, read by plain GET (FE9).
9
+ - Whether the windows differ in JP, CA, AU, IN or MX, and whether the itemised window counts from the fee's `postedDate`, the ship date or the settlement date, is read in Amazon's documents, not yet seen on a live account (FE9).
10
+ - A charge's date is `postedDate` in Finances `listTransactions` (Finance and Accounting), or `posted-date` in settlement V2 (FE9).
11
+ - Finances data reaches further back than the itemised window, so by the research's reading an older overcharge is visible in the data but past the limit Amazon staff state (FE32).
12
+ - Monthly and long-term storage are disputable as itemised fees by the staff guide, and the policy text names the storage reports as the source of the dimensions used; a support agent's 2025 line that storage fees "can never be reimbursed" is kept as a seller's report (FE16).
13
+
14
+ ## History
15
+
16
+ - A Chinese trade article dates the weight-and-dimension fee limit to about 2019-05, replacing a less strict one it does not state; that is 52by's report (FE10).
17
+ - The Australia News post that revised FBA inventory claim windows from 2025-10-15 does not cover fee claims (FE10).
18
+
19
+ ## One claim per charge
20
+
21
+ - Amazon allows one claim per fee charge under the weight-and-dimension fee policy and under the referral-fee policy (FE11).
22
+ - The weight-and-dimension text, as a seller quotes it, adds that one request is enough for an FNSKU (FE11).
23
+
24
+ ## Referral fees
25
+
26
+ - On 2022-03-16 Amazon removed the referral-fee dispute window and introduced fee category guidelines (FE22).
27
+ - A seller on the CA forum reports a phone agent citing an "Internal Policy" limit on referral reimbursement; it stands as a seller's report beside Amazon's News post (FE22).
28
+ - From 2023-01-13 a referral reimbursement is at the rate in force on the transaction date, disputes contrary to the guidelines then in force are declined, one claim is allowed per charge, and the policy does not apply to other fees (FE23).
29
+ - That policy was read in a UK-store staff post of 2024-05-24; no US-store text of it was read, and the policy as the store shows it is Seller Central's *Referral fees reimbursement policy*, which the seller sees signed in (FE23).
30
+ - The fee category Amazon assigned is not a column of the SP-API Fee Preview (FE24).
31
+
32
+ ## The route
33
+
34
+ - Amazon's staff guide names Help > Contact Us > Shipping & FBA > FBA Issue > "Fees Charged in Error" for FBA fee errors, and Selling Partner Support with the Custom Unified Transaction report for referral fees (FE37).
35
+ - Opening the case, attaching evidence and answering it are the seller's steps in Seller Central; no SP-API operation files, answers or reopens a fee dispute (FE37, SU12).
36
+ - The Support API needs Selling Partner Support (Restricted), a role outside the five, so nothing here is built on it; it would open the status, dates, subject, contacts and attachments of the seller's cases (SU8).
37
+ - Case routes by kind, evidence formats and the conduct Amazon penalises: ../claim-filing/SKILL.md.
@@ -0,0 +1,37 @@
1
+ ---
2
+ name: return-claims
3
+ description: "What Amazon owes an FBA seller on a customer order, keyed by the order id, when the refund, the return and the unit do not line up: a refund or replacement whose unit never came back, a return graded unsellable and the disposition that decides fault, FBA Damaged Inventory Ownership, a wrong item, empty box or switched return, a replacement whose original was not returned, a refund above the sale, a returns reimbursement taken back when the unit arrives, where each store states the customer-return window, the FBA Returns report and the replacements report, Lost_Outbound and Damaged_Outbound, returns under another FNSKU, MCF and seller-fulfilled returns outside the FBA claim, and Remote Fulfillment and EFN returns. For any question about a buyer refunded who kept the item, a return that came back damaged, empty or wrong, whether Amazon owes for it, or what the returns report shows for an order."
4
+ ---
5
+
6
+ ## What Amazon owes on a return
7
+
8
+ On an FBA order Amazon refunds or replaces for the seller and debits the seller; it reimburses, in most cases, a unit not returned within the store's set number of days of the refund, reimburses a unit returned unsellable through Amazon's fault, and restocks a sellable return with no money (RT1).
9
+ The reimbursement decision follows the unit's physical condition as evaluated at the fulfilment centre, not the buyer's chosen reason (RT2).
10
+ Where an FBA unit is lost, damaged or missing, or the wrong item is delivered to the buyer, Amazon, unless the seller caused it, replaces or refunds at its option and reimburses the seller under the FBA Guidelines (RT46).
11
+ Outcomes, fault, wrong items, replacements, refunds above the sale and take-backs: references/outcomes.md.
12
+
13
+ ## The window
14
+
15
+ The customer-return window counts from the refund or replacement date, and its day counts differ by store and Amazon's posts disagree; which statement the claim tool enforces for a store is open: read in Amazon's documents, not yet seen on a live account (RT4, EC5).
16
+ Each store's statements and where each is read: references/windows.md.
17
+
18
+ ## The unit side
19
+
20
+ The FBA Returns report lists only units received at a fulfilment centre, so a refund without a return has no row (RT32).
21
+ Its `return-date` is the processing date at the centre, not the start of the claim clock (RT33).
22
+ Columns, dispositions, statuses and the replacement link: references/reads.md.
23
+
24
+ ## Edges
25
+
26
+ Outbound loss before delivery, wrong-FNSKU and commingled returns, MCF and seller-fulfilled returns, Remote Fulfillment and EFN returns: references/edges.md.
27
+
28
+ ## What cx cannot do
29
+
30
+ No SP-API operation files a claim, replies to or reopens a case, or attaches evidence; each is the seller's step in Seller Central, where the IDR portal, announced for the US store on 2025-01-21, covers customer returns (SU12, FL5).
31
+ Routes, evidence and conduct: ../claim-filing/SKILL.md.
32
+ What a return reimbursement is worth, reversals and value disputes: ../claim-value/SKILL.md.
33
+ Units lost or damaged inside the warehouse: ../warehouse-claims/SKILL.md.
34
+ Units short on the way in: ../shipment-claims/SKILL.md.
35
+ A return fee charged in error: ../fee-claims/SKILL.md.
36
+ SAFE-T, A-to-z and refund money lines: @comchatx/cx-amazon-finance-playbook, skill refunds-and-reimbursements.
37
+ How a call is made and a report is asked for and landed: the amazon-sp-api skill's references/door.md.
@@ -0,0 +1,37 @@
1
+ # Edges: outbound loss, wrong FNSKU, MCF and seller-fulfilled, cross-border
2
+
3
+ ## Lost or damaged after the order, before delivery
4
+
5
+ - Where an FBA unit is lost, damaged, missing or the wrong item is delivered, Amazon, unless the seller caused it, replaces or refunds at its option and reimburses the seller under the FBA Guidelines, keeping its fees (RT46).
6
+ - Amazon's US policy redlines of 2024-12-18 and 2025-02-24 value a loss by whether it happened before or after the end customer's order, name only the customer-return claim under their post-order heading, and list no separate outbound claim kind (RT47).
7
+ - That a unit lost or damaged after the order and before delivery is handled as a customer-return case is the research's inference from that text (RT47).
8
+ - `Lost_Outbound` and `Damaged_Outbound` are Reimbursements report `reason` values seen in public files; no Amazon page read defines them and no SP-API model names them (RT48).
9
+ - Whether those rows arrive with no filed case and at which basis they are valued is read in Amazon's documents, not yet seen on a live account (RT48, VR31).
10
+ - Sellers of non-returnable FBA items in one US thread opened 2026-03-13 report refunds for buyer-reported transit damage denied at first contact for being non-returnable and approved on escalation; no Amazon reply in the thread states a rule (RT49).
11
+ - Seller 365, a recovery vendor, defines "Lost Outbound" as a shipment that leaves a centre and is never delivered, counting customer orders and lost removal orders in it (RT50).
12
+ - Shipping API v2 `createClaim` files a carrier claim on a parcel, not an FBA reimbursement (SU13).
13
+
14
+ ## Wrong-FNSKU and commingled returns
15
+
16
+ - Amazon defined commingling as fulfilling orders from the closest exact-match inventory "even if that inventory belonged to a different seller"; its UK and Canada News posts of 2025-12-08 end it for inventory shipped on or after a date they state, read by plain GET (RT51, IN24).
17
+ - No Amazon page read says to whose inventory a returned commingled unit is credited (RT51).
18
+ - Recovery vendors list returns received under a different FNSKU than ordered as a claim type; Amazon names no such kind in pages read (RT52).
19
+ - The returns report row carries `sku` and `fnsku` beside the order; that such a return would show there is the research's inference, and whether a seller's file holds one is read in Amazon's documents, not yet seen on a live account (RT52).
20
+
21
+ ## MCF and seller-fulfilled returns
22
+
23
+ - MCF units are the seller's to refund and return; an MCF return Amazon receives is returned or disposed at the seller's direction and cost, outside the FBA customer-return claim (RT44).
24
+ - An Amazon moderator's reply of 2026-04-23 pointed an FBA seller to SAFE-T and the Guided Refund Workflow, both seller-fulfilled programmes, so that reply is no rule source for FBA (RT43).
25
+ - `GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE` carries `Order Amount`, `Refunded Amount`, `Return delivery date`, `A-to-Z Claim` and five `SafeT` columns, with a per-request date span stated on Amazon's *Returns Reports* page (RT39).
26
+ - Its roles, Inventory and Order Tracking or Direct to Consumer Shipping (Restricted), are outside the five; were the app to hold either, it would open seller-fulfilled refunds against order amounts and SAFE-T claim states (RT39, SU47).
27
+ - The Seller Fulfilled Prime returns reports name Pricing and carry the same SAFE-T columns, for Prime orders only (SU48).
28
+ - SAFE-T and A-to-z claims as money: @comchatx/cx-amazon-finance-playbook, skill refunds-and-reimbursements.
29
+
30
+ ## Cross-border returns
31
+
32
+ - A Remote Fulfillment with FBA return is sent back to the US and is subject to the FBA customer-returns policy (RT53).
33
+ - From 2025-03-25 Amazon credits return fees on Remote Fulfillment returns in the Mexico and Brazil stores, automatically and within a period its US News post of 2025-03-10 states, read by plain GET, as a "Refund" transaction with details "Remote Fulfillment credit" (RT54).
34
+ - A return fee charged with no credit: ../fee-claims/SKILL.md.
35
+ - Amazon's EFN handbook (updated 2022-01) says that under EFN between the UK and the EU returned items are sent to the source store; sellers report returns landing in other EU centres and storage charged there (RT55).
36
+ - No page read states the store or currency of a cross-border return's reimbursement, and it is not yet seen on a live account (RT55).
37
+ - The Reimbursements report carries `currency-unit` and no store column, while the ledger detail carries `Country` and `Store` (SU52).
@@ -0,0 +1,48 @@
1
+ # Outcomes: what Amazon owes on a refunded or replaced FBA order
2
+
3
+ ## The three outcomes
4
+
5
+ - On an FBA order Amazon refunds or replaces on the seller's behalf and debits the seller (RT1).
6
+ - In most cases Amazon charges the buyer and reimburses the seller when the unit is not returned within the store's set number of days of the refund; US and Canada staff posts read 2026-11-13 state that number, and where the seller sees it for any other store is open, not yet seen on a live account (RT1).
7
+ - A unit returned sellable goes back to the seller's inventory and no money is owed (RT1).
8
+ - A unit returned unsellable is reimbursed only where Amazon is responsible for its condition (RT1).
9
+ - The decision follows the unit's physical condition as evaluated at the fulfilment centre, not the reason the buyer chose (RT2).
10
+ - Under the FBA Service Terms Amazon decides refunds on FBA units and notifies the seller when it holds the seller responsible; the seller may appeal within a period counted from that notification, and in Australia may also ask for the unsuitable unit back for inspection (RT29).
11
+ - The appeal period is the one in F-8.2 of the store's Business Solutions Agreement; Amazon's NA redline (2019) and AU agreement (2023) were read as PDFs (RT29).
12
+
13
+ ## Dispositions and fault
14
+
15
+ - `DAMAGED` and `CARRIER DAMAGED` read "We take responsibility for the damage" on Amazon's returns report help as the listing pack read it on 2026-10-14; Gorilla ROI's close copy of that table adds that ownership passes to Amazon and the unit is compensated under the reimbursement policy (RT9).
16
+ - In Gorilla ROI's copy of the same table, `CUSTOMER DAMAGED` and `DEFECTIVE` leave the unit in the seller's unsellable inventory (RT9).
17
+ - In that copy, `CUSTOMER DAMAGED` can mean only that the packaging was opened (RT9).
18
+ - A dispute of a customer-damaged or defective grade needs the unit physically returned through a removal order and is a removal claim; in Amazon's EU redline of 2024-08-20 the claim adds an explanation of the disagreement (RT13, RM11).
19
+ - The grading-dispute window's length and anchor are per store and per date, read on the store's removals-claims page or tool, which the seller sees signed in; Australia's News post of 2025-08-14, read by plain GET, counts it from the date the unit was removed from the network (RT13, RM12).
20
+ - As PPC Land quotes Amazon's text, a seller enrolled in FBA Damaged Inventory Ownership keeps enrolled Amazon-fault damaged inventory in its unfulfillable stock and decides its removal, and that inventory is not eligible for damage reimbursements (RT11).
21
+ - The enrolment's scope, all ASINs or a list, is on *FBA Damaged Inventory Ownership* as the seller sees it signed in; no SP-API read shows the enrolment (RT11).
22
+
23
+ ## Wrong item, empty box, switcheroo
24
+
25
+ - On Amazon's returns report help as the listing pack read it on 2026-10-14, the reason code `SWITCHEROO` is the buyer's claim "Amazon sent me the wrong item", not Amazon's finding that the buyer swapped the unit (RT18).
26
+ - The contract covers a wrong item delivered to the buyer, as it covers a unit lost, damaged or missing (RT46).
27
+ - Amazon's US policy redlines of 2024-12-18 and 2025-02-24 put the customer-return claim under "Post-Order Lost or Damaged Events", while sellers in two US forum threads of 2025 report wrong-item claims paid at sourcing cost, one dating it from 2025-04-01; which basis a store pays is read in Amazon's documents, not yet seen on a live account (RT17, VR27).
28
+ - One US seller reported on 2026-08-05 a materially different return reimbursed through removal handling at sourcing cost rather than the order basis (VR33).
29
+
30
+ ## Replacements
31
+
32
+ - Amazon may settle a lost, damaged, missing or wrong unit by shipping a replacement to the buyer and reimbursing the seller under the FBA Guidelines, keeping its fees (RT46).
33
+ - The customer-return window counts from the refund or replacement date (RT4).
34
+ - The replacement-to-original link in the reports and orders reads: references/reads.md.
35
+
36
+ ## Refund above the sale
37
+
38
+ - No Amazon page read provides for repaying a refund above the order's charge; the contract leaves refunds to Amazon and makes the seller pay where Amazon finds the seller responsible (RT24).
39
+ - Sellers on the EU forum in 2025 report FBA refunds of several times the order value, called "goodwill" or a "concession", refused for reimbursement (RT24).
40
+ - Recovery services list "refund overcharge" as a claim type (RT24).
41
+ - On seller-fulfilled orders, `Refunded Amount` beside `Order Amount` sits in `GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE`, whose roles, Inventory and Order Tracking or Direct to Consumer Shipping (Restricted), are outside the five; either would open those columns (RT39).
42
+
43
+ ## Reimbursed, then the unit comes back
44
+
45
+ - Under the FBA Service Terms, if a refunded or replaced unit comes back sellable and Amazon restocks it, the seller repays its Replacement Value; with the policy's reversal sentence this is the basis for taking back a returns reimbursement (RT30).
46
+ - Practitioners name the transaction description `COMPENSATED_CLAWBACK` ("Reversal of previous refunds") as Amazon taking back a reimbursement when a unit is found or a return arrives sellable; Amazon publishes no definition read here (RT31).
47
+ - Whether that description and the Reimbursements report's reversal row are one event is read in Amazon's documents, not yet seen on a live account (RT30, RT31).
48
+ - Reversal grounds, links and found units: ../claim-value/SKILL.md.