@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
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 ComChatX
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,14 @@
1
- # Temporary Holding Version
1
+ cx reads your Amazon reports to check what Amazon may owe you: units lost or damaged in its warehouses, shipments received short, removals and returns that never came back, fees charged wrongly, and reimbursements paid low. For each, it says whether Amazon already paid and where your store's window is stated. You file claims in Seller Central: cx cannot open a case or send evidence.
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Some things you can ask:
4
+
5
+ - Did every unit from last month's removal orders come back?
6
+ - Does Amazon pay for units lost in its warehouse without a claim?
7
+ - Can filing many claims put my account at risk?
8
+
9
+ To read stock states and money lines in depth, also install [Amazon Stock Playbook](https://www.npmjs.com/package/@comchatx/cx-amazon-stock-playbook) and [Amazon Finance Playbook](https://www.npmjs.com/package/@comchatx/cx-amazon-finance-playbook).
10
+
11
+ ## What it uses
12
+
13
+ - **Amazon SP-API:** your Amazon selling account, connected on the Amazon SP-API plugin. cx reads your inventory ledger, reimbursements, returns, removals, shipments and fees there.
14
+ - **Amazon Seller Profile:** tells cx you sell on Amazon.
@@ -0,0 +1,14 @@
1
+ cx 读你的亚马逊报告,核对亚马逊可能该赔你的货和钱:仓库里丢失或损坏的货、入库少收、移除后没送回、退款后没退回,以及多收的费用和赔少了的赔偿。每一项都说明亚马逊赔过没有、索赔期限写在哪。索赔由你在卖家后台提交,cx 不能开案件,也不能上传证据。
2
+
3
+ 你可以这样问:
4
+
5
+ - 上个月的移除订单,货都送回来了吗?
6
+ - 仓库里丢的货,亚马逊会自己赔吗?
7
+ - 索赔提得多,会不会影响店铺?
8
+
9
+ 如果想深入看库存状态和资金明细,再装上[亚马逊库存分析手册](https://www.npmjs.com/package/@comchatx/cx-amazon-stock-playbook)和[亚马逊财务分析手册](https://www.npmjs.com/package/@comchatx/cx-amazon-finance-playbook)。
10
+
11
+ ## 用到的数据
12
+
13
+ - **Amazon SP-API**:你的亚马逊卖家账户,在 Amazon SP-API 插件里连接。cx 在这里读取库存流水、赔偿、退货、移除、货件和费用。
14
+ - **Amazon Seller Profile**:告诉 cx 你在亚马逊开店。
package/package.json CHANGED
@@ -1,6 +1,112 @@
1
1
  {
2
2
  "name": "@comchatx/cx-amazon-claims-playbook",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "0.1.0",
4
+ "description": "Checks what Amazon may owe you, and says where to claim.",
5
+ "license": "MIT",
6
+ "author": "ComChatX",
7
+ "comchatx": {
8
+ "name": "Amazon Claims Playbook",
9
+ "nameZh": "亚马逊索赔分析手册",
10
+ "about": "核对亚马逊可能该赔的货和钱,说明每类去哪索赔。",
11
+ "mark": {
12
+ "line": "clipboard"
13
+ },
14
+ "section": "extensions",
15
+ "order": 57,
16
+ "skills": {
17
+ "warehouse-claims": {
18
+ "zh": "查出亚马逊仓库里丢失或损坏、还没赔的货。",
19
+ "en": "Units lost or damaged in Amazon's warehouses, not yet paid."
20
+ },
21
+ "shipment-claims": {
22
+ "zh": "核对入库少收,以及移除没送到的货。",
23
+ "en": "Shipments received short, and removals that never came back."
24
+ },
25
+ "return-claims": {
26
+ "zh": "找出退款了却没退回、或退回不对的订单。",
27
+ "en": "Refunds whose item never came back, or came back wrong."
28
+ },
29
+ "fee-claims": {
30
+ "zh": "查出按错尺寸、重量或类目多收的费用。",
31
+ "en": "Fees charged on the wrong size, weight or category."
32
+ },
33
+ "claim-value": {
34
+ "zh": "看清赔偿按什么价算,哪些又被撤回。",
35
+ "en": "What a reimbursement was worth, and when it was taken back."
36
+ },
37
+ "claim-filing": {
38
+ "zh": "说明索赔在哪提交、要什么证据、期限在哪查。",
39
+ "en": "Where each claim is filed, its evidence, and where its window is stated."
40
+ }
41
+ },
42
+ "prompts": {
43
+ "claims-audit": {
44
+ "zh": "查一遍亚马逊可能该赔的货和钱,以及各自去哪索赔。"
45
+ },
46
+ "inbound-shortfall": {
47
+ "zh": "查最近几批入库有没有少收,差多少、要什么证据。"
48
+ },
49
+ "returns-check": {
50
+ "zh": "找出退款了但没退回、或退回不对的订单。"
51
+ },
52
+ "fee-check": {
53
+ "zh": "查 FBA 费用有没有按错尺寸、重量或类目收。"
54
+ },
55
+ "reimbursement-value": {
56
+ "zh": "看亚马逊的赔偿按什么价算、有没有被撤回的。"
57
+ }
58
+ },
59
+ "builds": [
60
+ {
61
+ "on": "cx-amazon-sp-api",
62
+ "need": "required"
63
+ },
64
+ {
65
+ "on": "cx-amazon-seller",
66
+ "need": "required"
67
+ },
68
+ {
69
+ "on": "@comchatx/cx-amazon-stock-playbook",
70
+ "need": "optional"
71
+ },
72
+ {
73
+ "on": "@comchatx/cx-amazon-finance-playbook",
74
+ "need": "optional"
75
+ }
76
+ ]
77
+ },
78
+ "homepage": "https://github.com/comchatx/cx-amazon-claims-playbook#readme",
79
+ "repository": {
80
+ "type": "git",
81
+ "url": "git+https://github.com/comchatx/cx-amazon-claims-playbook.git"
82
+ },
83
+ "bugs": "https://github.com/comchatx/cx-amazon-claims-playbook/issues",
84
+ "keywords": [
85
+ "pi-package"
86
+ ],
87
+ "type": "module",
88
+ "pi": {
89
+ "skills": [
90
+ "./skills"
91
+ ],
92
+ "prompts": [
93
+ "./prompts"
94
+ ]
95
+ },
96
+ "files": [
97
+ "skills",
98
+ "prompts",
99
+ "README.zh-CN.md"
100
+ ],
101
+ "scripts": {
102
+ "typecheck": "tsc --noEmit",
103
+ "test": "vitest run"
104
+ },
105
+ "devDependencies": {
106
+ "@earendil-works/pi-ai": "1.5.0",
107
+ "@earendil-works/pi-coding-agent": "1.5.0",
108
+ "@types/node": "26.2.0",
109
+ "typescript": "7.0.2",
110
+ "vitest": "4.1.11"
111
+ }
112
+ }
@@ -0,0 +1,5 @@
1
+ ---
2
+ description: "Find what Amazon may owe you, and where each claim is filed."
3
+ argument-hint: "[your words]"
4
+ ---
5
+ Find what Amazon may owe me: units lost, damaged or received short, removals that never came back, refunds whose item was never returned, and fees charged wrongly. For each, say what it rests on in my own reports, whether Amazon already paid it, and where the window for my store is stated. $@
@@ -0,0 +1,5 @@
1
+ ---
2
+ description: "Check whether your Amazon fees were charged on the wrong size or category."
3
+ argument-hint: "[your words]"
4
+ ---
5
+ Check whether Amazon charged my fees on the wrong size, weight or category: which products, since when, and which charges can still be disputed for my store. $@
@@ -0,0 +1,5 @@
1
+ ---
2
+ description: "Check your recent shipments to Amazon for units received short."
3
+ argument-hint: "[your words]"
4
+ ---
5
+ Check my recent shipments to Amazon for units received short: how many on which shipments, whether each can be claimed yet, and what Amazon asks to see. $@
@@ -0,0 +1,5 @@
1
+ ---
2
+ description: "See what Amazon's reimbursements were worth, and which were taken back."
3
+ argument-hint: "[your words]"
4
+ ---
5
+ Look at what Amazon has reimbursed me: what each payment was valued at, which look low against my own cost, and which were later taken back. $@
@@ -0,0 +1,5 @@
1
+ ---
2
+ description: "Find refunds whose item never came back, or came back wrong."
3
+ argument-hint: "[your words]"
4
+ ---
5
+ Find refunds where the item never came back to Amazon, or came back as something else or damaged by Amazon, and whether Amazon has already paid for each. $@
@@ -0,0 +1,46 @@
1
+ ---
2
+ name: claim-filing
3
+ description: "How an Amazon FBA reimbursement claim or Seller Central case is filed and followed up, and what cx can and cannot read or do in one: each kind's entry point and where its window is stated, one claim per shipment, event or fee charge, evidence formats, proof of ownership and delivery, case states, replying and reopening, the conduct paragraph and deactivations for claim abuse, third-party reimbursement services and Chinese tools (领星, 船长BI), the automated-agent duties and the Agent Policy, the Support API on a restricted role, every claims report with its role, lag and look-back, reads outside the app's roles, how a News post's store is read, and an amount owed as a formula over the seller's own reads. For any question about filing, following up or paying someone to file an FBA claim, whether many claims put an account at risk, or what cx can do about a claim, rather than whether a particular loss, return or fee is owed."
4
+ ---
5
+
6
+ ## Where a claim is filed
7
+
8
+ Every FBA claim and case is opened, evidenced, answered and reopened by the seller, or a user the seller authorises, in Seller Central (FL1, SU12).
9
+ Amazon may decline a claim that skips its kind's process or withholds requested information, and opens one only for an item not already reimbursed (FL2, FL3).
10
+ Entry points, evidence, limits and answers by kind: references/filing.md.
11
+
12
+ ## Conduct
13
+
14
+ Amazon names insufficiently researched or premature requests and many requests in a short time as conduct that can bring delayed support, monitoring or account action (FL11).
15
+ From 2026-03-04 the Business Solutions Agreement requires any automated agent accessing Amazon Services to identify itself, comply with the Agent Policy and cease access when Amazon asks (FL22).
16
+ Conduct, deactivations and third-party filers: references/conduct.md.
17
+
18
+ ## What cx reads
19
+
20
+ The claim reads sit on Amazon Fulfillment, Pricing and Finance and Accounting; no notification announces a reimbursement or a case change (SU2, SU3, SU5, SU31).
21
+ Every read with its role, lag and look-back: references/reads.md.
22
+
23
+ ## No door
24
+
25
+ No operation files a claim, opens or answers a case, attaches evidence, enters a sourcing cost, requests a remeasure or disputes a value; the Support API reads cases on a restricted role outside the app, and nothing is built on it (SU12, SU8).
26
+ Each step as the seller's step in Seller Central: references/no-door.md.
27
+
28
+ ## Windows and stores
29
+
30
+ Each kind's window is a per-store length on Amazon's page for that kind and in the store's News posts (FC9, RT4, IN7, RM6).
31
+ For warehouse losses and inbound shortfalls no operation returns or states it (FC9, IN7).
32
+ Where each is stated, and a forum post's store: references/windows-and-stores.md.
33
+
34
+ ## Recovery
35
+
36
+ Filing oneself, a commission service, a subscription or ERP tool, entering a sourcing cost or leaving a kind alone are the seller's choices (EC25).
37
+ The market and the amount owed as a formula: references/recovery.md.
38
+
39
+ ## Other skills
40
+
41
+ The windows table and warehouse losses: ../warehouse-claims/SKILL.md.
42
+ Inbound shortfalls: ../shipment-claims/SKILL.md.
43
+ Customer returns: ../return-claims/SKILL.md.
44
+ Fee overcharges: ../fee-claims/SKILL.md.
45
+ What a reimbursement is worth: ../claim-value/SKILL.md.
46
+ 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,31 @@
1
+ # Conduct: what Amazon penalises, third-party filers and agents
2
+
3
+ ## The conduct paragraph
4
+
5
+ - Amazon prohibits activity that interferes with its capacity to help other sellers; its examples are "submitting insufficiently researched or premature requests" and "submitting a large number of requests in a short time" (FL11).
6
+ - Sellers who repeat them "may receive delayed support on their cases or be subject to monitoring, investigation, and account action" (FL11).
7
+ - The paragraph stands in the 2021-04 UK-path policy PDF ("high volumes") and the 2025-02-24 US PDF, and Amazon's own messages quoted it in the Canada store in 2022 and in the US in 2024 (FL11).
8
+ - Amazon's 2022 Canada denial already used the later wording and added a catch-all, "or otherwise engaging in any other activity that interferes with our capacity to help other sellers" (FL42).
9
+ - The Supply Chain Portal policy carries its own version for MCF accounts, and for inbound adds that merchants generating many shipping problems may face investigation, monitoring and delayed reimbursements; no FBA page read carries that sentence (FL11, FL41).
10
+ - Selling Partner Support's restatement: "we decline requests that are not consistent with our policies", and "Amazon may close cases or limit support if you don't follow these guidelines" (FL12).
11
+ - The Seller Code of Conduct requires sellers to "Provide accurate information to Amazon … at all times" and to "Act fairly and not misuse Amazon's features or services", words that reach this pack through an Amazon staff member's quotation of an unread page (FL15).
12
+
13
+ ## What sellers report
14
+
15
+ - Deactivation notices sellers have posted for claims name Section 3 of the BSA, the Seller Code of Conduct, "FBA credit reimbursement abuse" and "repeatedly submitted improper claims for FBA reimbursement" (FL16).
16
+ - Sellers deactivated for claims report having used a third-party claims service, and one found the service still filing while the account was deactivated (FL17).
17
+ - DAM Law Firm writes that from 2026-03-04 the seller answers for every agent on the account; no Amazon page read states that the seller answers for a service's claims (FL17).
18
+ - Practitioners report a deactivation after an inbound shortfall was paid and the "found" units proved not to be the seller's (FL18).
19
+
20
+ ## Third parties and apps
21
+
22
+ - No Amazon page read bars or endorses third-party reimbursement services (FL19).
23
+ - SP-API AUP 2.11 binds an app acting for a seller to keep all submissions and communications "accurate, policy-compliant" and free of "frivolous or non-compliant contacts or degradation of Amazon support systems"; AUP 1.1 limits it to activities the seller has authorised (FL20).
24
+ - An SP-API developer that needs Amazon Portal access asks the seller to grant it through secondary user permissions, and must not request or share Amazon Portal usernames or passwords (FL21).
25
+
26
+ ## The agent duties from 2026-03-04
27
+
28
+ - From 2026-03-04 the BSA requires any automated software or AI agent accessing Amazon Services to identify itself as automated, comply with the Agent Policy and cease access when Amazon asks; Amazon may restrict its access, and continued use is acceptance (FL22).
29
+ - Amazon announced it in a US thread on 2026-02-17 and a Canada thread on 2026-02-19 (FL22).
30
+ - The Agent Policy's own text is unread; the user-agent string, the bar on mimicking human keystrokes and truthful answers are a practitioner's relay, and what the policy says beyond the three duties is read in Amazon's documents, not yet seen on a live account (FL22).
31
+ - Amazon's own `support-case-helper` skill fills a "Reported From" field with the running agent's name (FL23).
@@ -0,0 +1,62 @@
1
+ # Filing: entry points, evidence, limits and answers
2
+
3
+ ## Conditions on every claim
4
+
5
+ - Amazon's policy makes following the process for the claim kind, and giving all requested information, a condition: "We may decline your claim if you do not"; the Supply Chain Portal policy says the same for its programme (FL2).
6
+ - A claim is open only for an item Amazon has not already reimbursed, and Amazon's US moderator in 2026 tells sellers to check the Reimbursements report before filing by hand (FL3).
7
+ - The account-status condition widened: the 2021-04 UK-path text asked for normal status when filing; the 2025-02-24 US text asks for it when a claim is filed, under review and during any appeals; the US moderator in 2026 excludes blocked, terminated or fraud-status accounts (FL13).
8
+ - Claims are ineligible while the account is not in normal status, and a deactivated account is reinstated through Account Health (FL34).
9
+ - No Amazon page read charges a fee to file a claim; the costs Amazon names are declined claims, conduct consequences and reversals (FL37).
10
+
11
+ ## Entry points by kind
12
+
13
+ - Warehouse lost and warehouse damaged, and the IDR portal's rows: ../warehouse-claims/SKILL.md.
14
+ - Customer returns: ../return-claims/SKILL.md.
15
+ - Amazon locates the Transaction Item ID in the Inventory Ledger, and practitioners paste the ledger's `Reference ID` into the damaged-status tool (FC17).
16
+ - Amazon's 2026 staff instructions name an "Inventory Adjustments" report whose API type was removed on 2023-01-31, and Amazon does not state that the ledger's `Reference ID` is the Transaction Item ID; that the tool accepts it is read in Amazon's documents, not yet seen on a live account (FL6).
17
+ - The IDR portal, announced 2025-01-21 for the US store, covers warehouse lost, warehouse damage and customer returns, not missing from inbound, removals or warehouse disposals, and is reached from the FBA dashboard's Inventory menu or the Reimbursements report (FL5, FC13).
18
+ - Practitioners describe the IDR pages as Overview, Eligible for Claim, In Progress, Resolved and Defect Status Trend (FC15).
19
+ - No operation returns the IDR portal's lists or statuses; whether its rows match candidates rebuilt from the reports, and whether it exists outside the US, is read in Amazon's documents, not yet seen on a live account (FC14, FL5).
20
+ - Missing from inbound: Seller Central shows per shipment whether it is eligible for investigation and an estimated date it will be (IN11).
21
+ - Submitting an inbound research request through the Contents tab's Action required menu creates a Selling Partner Support case whose number shows on that tab (IN13, IN19).
22
+ - Amazon's Global Selling China article of 2025-08 advises submitting inbound research on the shipment's item page rather than to Seller Support (IN18).
23
+ - Removals: the "Resolve a removal order issue" tool, keyed by removal order ID (RM4).
24
+ - FBA fee errors, as Amazon's US and UK staff guides name them: Help > Contact Us > Shipping & FBA > FBA Issue > "Fees Charged in Error"; referral fees: Selling Partner Support with the Custom Unified Transaction report (FE37).
25
+ - A value dispute has two routes Amazon's staff name in US-store threads, the self-service "Dispute a reimbursement claim" and "Submit a reimbursement claim dispute" under Get Help, beside a case reopening (VR21).
26
+ - AWD: a seller quoted Amazon's AWD help on 2024-09-17 promising fair-value reimbursement on a case to Selling Partner Support when AWD finds fewer boxes than received (FC38).
27
+ - The Supply Chain Portal page is both the SCP policy for an active MCF account and the page the AWD terms link as the MCF inventory reimbursement policy; its claims and disputes go through the Supply Chain Portal's Contact Us (FL27).
28
+ - One ERP tells sellers to file each claim in the store where the event happened; no Amazon page read says so (FL40).
29
+ - Practitioners' menu paths and windows go stale: older Chinese and English guides cite paths and windows the 2024–2025 changes superseded (FL39).
30
+
31
+ ## One claim, one issue
32
+
33
+ - Amazon's denial text in the Canada store (2022) and the SCP page allow one claim per inbound shipment and decline further claims for it; the US moderator in 2026 put it as one claim per shipment or event (FL7, IN17).
34
+ - Amazon allows one claim per fee charge under the weight-and-dimension and referral-fee policies (FE11).
35
+ - Amazon's support rule, as US staff gave it in 2025, is one issue per case, and no new case while one is open for the same issue (FL8).
36
+ - No Amazon page read states a maximum of items per case or of cases per day; volume enters only as conduct (FL9).
37
+ - Practitioners' per-case and per-day figures conflict across AMZ123, Jungle Scout China, SellerSpace and 看点资讯, and cite no Amazon page (FL10).
38
+
39
+ ## Evidence
40
+
41
+ - Shipment-to-Amazon evidence is proof of ownership (itemised invoice, another seller's receipt or a packing slip, signed for a manufacturer) and proof of delivery: an Amazon-stamped delivery document for LTL or FTL, an active tracking ID per package for small parcel (FL24).
42
+ - Amazon accepts ownership documents only in a non-editable format (PDF, JPG, JPEG, PNG, TIFF), refuses pro forma invoices and contracts, and lets the seller hide the price paid (IN16).
43
+ - A removal claim asks for the removal order ID, shipment ID, ASINs or FNSKUs, quantities and images; the SCP page adds tracking or proof of delivery, the LPN and proof of cost (FL25).
44
+ - A fulfilment-centre claim names the date or location of the loss, the Transaction Item ID or FNSKU, and proof of ownership (FC18).
45
+ - A sourcing-cost document goes into Manage Your Sourcing Cost, not into a case (FL26).
46
+ - Amazon's US policy of 2025-02-24 lets Amazon decline a sourcing cost for documents "forged, tampered with, or illegible", or when the account is suspected of fraud or significant policy violations (FL14).
47
+ - What a value document must carry: ../claim-value/SKILL.md.
48
+
49
+ ## Answers
50
+
51
+ - Sellers see a case as "Pending Amazon Action" or "Pending Merchant Action", and a reply from the seller hands it back to Amazon (FL28).
52
+ - Whether a case in "Pending Merchant Action" closes by itself after a set time is read in Amazon's documents, not yet seen on a live account (FL28, FL31).
53
+ - A seller can extend a case by replying that more time is needed (FL33).
54
+ - Sellers report cases auto-marked "Answered" with no reply (FL31).
55
+ - Among the pages read, Amazon states review or reply times only for inbound research, remeasurement and the seller's reply to an inbound information request, each on its own page; the SCP policy states its own timing for MCF order claims (FL30).
56
+ - By Amazon's US staff in 2025, Professional sellers can e-mail, request a call or chat with support; Individual-plan sellers can only e-mail (FL38).
57
+ - A paid manual claim appears in `GET_FBA_REIMBURSEMENTS_DATA` with its `case-id`, the API's only link from a case to money (FL29).
58
+
59
+ ## Reopening
60
+
61
+ - Amazon tells sellers to reopen a closed case for questions rather than open a new one (FL32).
62
+ - After a "no further action" decision, Selling Partner Support says a seller is not to seek a different outcome by reopening the case or raising it in other cases, and that Amazon may close cases or limit support otherwise (FL12, FL32).
@@ -0,0 +1,34 @@
1
+ # No door: what no SP-API operation can do in a claim
2
+
3
+ ## What the models hold
4
+
5
+ - No operation among the 394 in Amazon's models files a claim, opens a case, attaches evidence or enters a sourcing cost (SU12).
6
+ - None updates, replies to or reopens an FBA reimbursement or support case, requests a remeasurement, disputes a fee or a reimbursement's value, or acts in the IDR pages (SU12).
7
+ - Each of these is done in Seller Central by the seller or a user the seller authorises (FL1).
8
+ - The models' one claim-creating operation, Shipping API v2 `createClaim`, files a carrier claim on one parcel by tracking ID, is not an FBA inventory reimbursement and is absent from the Role Mappings page (SU13).
9
+ - Amazon's agentic toolkit has no reimbursement or claims tool, and its `support-case-helper` sends the seller to the Seller Central Help Center when no such tool exists (SU14).
10
+
11
+ ## The Support API
12
+
13
+ - The Support API v2025-02-01 (`listCases`, `getCase`, `listContacts`) needs Selling Partner Support (Restricted), outside the app's five roles; nothing is built on it (SU8).
14
+ - It launched on 2026-09-30 (SU9).
15
+ - Its three operations are reads: `listCases` takes a sort order, a page size and a token, no date, case type, reimbursement, ID or marketplace; a case carries no type, amount or reimbursement ID; attachments come by an expiring `downloadUrl` (SU10).
16
+ - Amazon's pages contradict each other on it: the roles page says the role can "retrieve, search, and manage support cases", the model has no search filter and no write, and a tutorial describes a contact `status` the model lacks (SU11).
17
+ - Its model takes no marketplace parameter and states no history reach for `listCases`; how far back a seller's cases are listed is read in Amazon's documents, not yet seen on a live account (SU56).
18
+
19
+ ## The seller's steps in Seller Central
20
+
21
+ - Open a case or claim: by kind, references/filing.md.
22
+ - Request inbound research: the shipment's Contents tab Action required menu, which creates a Selling Partner Support case (IN13, IN19).
23
+ - Attach evidence: uploaded in the case or tool, in a non-editable format (IN16, FL24).
24
+ - Read an answer, reply or reopen: in the case in Seller Central, where a seller's reply hands it back to Amazon and a closed case is reopened for questions (FL28, FL32).
25
+ - Enter or update a sourcing cost: Manage Your Sourcing Cost, one cost per FNSKU per marketplace (VR7, FL26).
26
+ - Dispute a reimbursement's value: the Get Help "Dispute a reimbursement claim" workflow or "Submit a reimbursement claim dispute" (VR21).
27
+ - Request a remeasure: Seller Central's remeasure request, with conditions Amazon states (FE4).
28
+ - Dispute an FBA fee: Help > Contact Us, "Fees Charged in Error" (FE37).
29
+ - File a removal claim: "Resolve a removal order issue", by removal order ID (RM4).
30
+ - Use the IDR portal: the seller's step, from the FBA dashboard's Inventory menu or the Reimbursements report in Seller Central (FL5).
31
+ - No operation returns the IDR portal's lists, statuses or resolution reasons (FC14).
32
+ - Request the Deferred Transaction Report the first time: the Payments Reports Repository (SU30).
33
+ - Download the Payments Date Range Report: Seller Central only, no report type (SU29).
34
+ - File an MCF order claim on a Supply Chain Portal account: the Supply Chain Portal's Contact Us (FL27).
@@ -0,0 +1,79 @@
1
+ # Reads: every claims read with its role, lag and look-back
2
+
3
+ ## Roles
4
+
5
+ - A role grants operations, reports, feeds and notifications, and a read is allowed when the application holds at least one role Amazon names for it on *Role Mappings for SP-API Operations* and *Role Mappings for SP-API Types* (SU1).
6
+ - *Role Mappings for Types* still lists types the deprecation schedule removed, so a type's presence there does not show that it answers (SU40).
7
+ - Restricted roles require the developer to give additional information about data use and security controls (SU46).
8
+
9
+ ## Reports inside the five
10
+
11
+ - The ledger detail and summary, the replacements report, inventory planning, overage fees and customer shipment sales name Amazon Fulfillment as their only role (SU2).
12
+ - `GET_FBA_REIMBURSEMENTS_DATA`, the FBA customer returns report, both removal reports, inbound noncompliance, the fee preview and both storage fee reports answer to Pricing or Amazon Fulfillment; `GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL` also to Inventory and Order Tracking (SU3).
13
+ - The Reimbursements report carries `currency-unit` and no store or marketplace column, while the ledger detail carries `Country` and `Store` (SU52).
14
+ - A developer reports that `GET_FBA_REIMBURSEMENTS_DATA` returns the same rows whatever `marketplaceIds` names; whether it still does is read in Amazon's documents, not yet seen on a live account (SU24).
15
+ - The Seller Fulfilled Prime returns reports name Pricing among their roles, cover Seller Fulfilled Prime returns only and carry the `SafeT-…` columns and `Refunded-Amount` (SU48).
16
+ - The stranded and reserved inventory reports name Pricing or Amazon Fulfillment, are request-only and updated in near real time; the stranded report carries `date-stranded`, `stranded-reason` and `Date-to-take-auto-removal` (SU59).
17
+ - The removal shipment detail excludes cancelled returns and disposed items, and a developer reports that its "Return" rows carry no destination address (SU26).
18
+ - The Deferred Transaction Report (`GET_DATE_RANGE_FINANCIAL_HOLDS_DATA`, Finance and Accounting) must first be requested in Seller Central's Payments Reports Repository before the API can fetch it (SU30).
19
+ - No report type carries Seller Central's Payments Date Range Report; dimension-fee refunds that tools read there as `Fee Adjustment` are reached through Finances or the settlement report (SU29).
20
+ - Settlement reports are scheduled by Amazon and cannot be requested, and the Reports API keeps a report for a maximum stated in the Reports model (SU53).
21
+ - No report type read carries liquidation proceeds per removal order; they post as Finances v0 `FBALiquidationEventList` (SU58).
22
+
23
+ ## Operations inside the five
24
+
25
+ - Fulfillment Inbound v0 `getShipments`, `getShipmentItems`, `getShipmentItemsByShipmentId` and every v2024-03-20 operation name Amazon Fulfillment only (SU4).
26
+ - The other inbound reads the claim files use (`listTransportationOptions`, `listPlacementOptions`, `listShipmentPallets`, `listPrepDetails`, `listInboundPlanItems`, `getInboundPlan`, `getBillOfLading`, `getLabels`) and `getItemEligibilityPreview` name Amazon Fulfillment only (SU50).
27
+ - v2024-03-20 shipment items carry no received quantity; received units per SKU per shipment through the API are v0 `QuantityReceived` (SU32).
28
+ - MCF reads (`getFulfillmentOrder`, `listAllFulfillmentOrders`, `getPackageTrackingDetails`) name Amazon Fulfillment and carry `UNDELIVERABLE`, "Shipment damaged", "Lost by carrier", `CarrierDamaged` and `FulfillerDamaged`; no operation files an MCF claim (SU51).
29
+ - Finances v0 `listFinancialEvents` names Finance and Accounting, Amazon Fulfillment (NA and FE only) and AISP (EU only); `…ByOrderId` names Finance and Accounting only (SU5).
30
+ - Catalog Items `includedData=dimensions` needs Product Listing and gives catalogue dimensions; Amazon's measured dimensions for fees are in the fee preview and storage fee reports (SU6).
31
+ - Product Fees `getMyFeesEstimateForSKU` and `…ForASIN` accept any of twelve roles, `getMyFeesEstimates` Pricing or Product Listing, and each returns an estimate for a price, not a fee charged (SU7).
32
+ - Data Kiosk Sales and Traffic counts A-to-z Guarantee and chargeback claims; none of its metrics counts an FBA reimbursement claim (SU57).
33
+ - Data Kiosk Seller Analytics counts returned units by ship date with a return-data delay stated in its schema, on Brand Analytics by the operations page; whether a query is accepted on Brand Analytics alone is read in Amazon's documents, not yet seen on a live account (SU54).
34
+
35
+ ## Notifications
36
+
37
+ - No notification type announces a reimbursement, a ledger adjustment, an inbound receipt or discrepancy, or a support-case change (SU31).
38
+ - `TRANSACTION_UPDATE` fires on any new transaction and is not on *Role Mappings for Types*; whether it subscribes on the app's roles is read in Amazon's documents, not yet seen on a live account (SU31).
39
+
40
+ ## Lag
41
+
42
+ - Amazon sets a minimum interval between generations of an FBA report, one for near-real-time and one for daily reports, in the opening of *FBA Reports*; practitioners report it counts per seller and report type across applications (SU19).
43
+ - The fee preview's refresh interval, `dataStartTime` offset and per-seller request limit are on its *FBA Reports* entry (SU20).
44
+ - The Amazon-fulfilled shipments report's span per request, request cap (Seller Central requests count) and delay after shipping are on its *FBA Reports* entry (SU21).
45
+ - The long-term storage fee report's required span is on its *FBA Reports* entry (SU22).
46
+ - The removal shipment detail has returned different row counts for the same dates asked at different times, and Amazon Developer Services gave no guaranteed time for updates (SU25).
47
+ - An Amazon staff reply on a developer issue (2026-07-31) says Seller Central shows a ledger request's range in the store's local time, daylight saving included (SU28).
48
+ - A developer reports (2025-04-21) that the API refuses the ledger detail example `"eventType":""` Amazon's page still shows; that leaving `eventType` out returns all events is inferred from the page's stated default (SU27).
49
+
50
+ ## Look-back
51
+
52
+ - The ledger detail's look-back is stated in its description on *FBA Reports*, the only claims report whose look-back Amazon's SP-API pages state (SU15).
53
+ - No look-back is stated for the reimbursements, FBA returns, replacements and removal reports; an Amazon developer-support engineer said the Seller Central reports team keeps them; how far each answers is read in Amazon's documents, not yet seen on a live account (SU16).
54
+ - Amazon's help pages for the Reimbursements report, customer returns and the reimbursement policy serve a script shell to a plain GET, so their look-back text is unread (SU45).
55
+ - A data vendor's connector sets its own look-back and latency per report, read on the vendor's page (SU17).
56
+ - A report's look-back and a claim's window are different facts: a report reaching further back does not make an older event claimable (SU18).
57
+ - Some FBA reports are offered in some stores only, stated in each report's store-availability line on *FBA Reports* (SU23).
58
+ - Data Kiosk's earliest `startDate` and result retention are in each dataset's schema (SU34).
59
+
60
+ ## Reads outside the five, and what each would open
61
+
62
+ - Nothing is built on any of these; each names its role and what it would open (SU8, SU33, SU49).
63
+ - The Support API (`listCases`, `getCase`, `listContacts`), on Selling Partner Support (Restricted), would open the seller's cases, their status, dates, subject, contacts and attachments (SU8).
64
+ - A developer asked Amazon in 2026-10 how to add Selling Partner Support (Restricted) to an approved application apart from its other roles; no Amazon answer was posted (SU60).
65
+ - Data Kiosk Economics needs Selling Partner Insights, by Amazon's correction page and developer support, while the Data Kiosk and operations pages still list Brand Analytics; it would open charged fees per MSKU and period (SU33).
66
+ - Economics gained removal, disposal, deal, coupon and fuel fees on 2026-09-30 and lost FNSKU granularity on 2025-12-22, and its schema points to unread help pages for its fee types (SU35, SU55).
67
+ - `GET_V2_SELLER_PERFORMANCE_REPORT`, on Selling Partner Insights only and request-only, would open `accountStatuses` per marketplace and Account Health metrics (SU49).
68
+ - `GET_FLAT_FILE_RETURNS_DATA_BY_RETURN_DATE`, on Inventory and Order Tracking or Direct to Consumer Shipping (Restricted), would open seller-fulfilled returns with the SAFE-T columns, `Order Amount` and `Refunded Amount`; its span per request is on *Returns Reports* (SU47).
69
+ - Whether the app can be given Selling Partner Insights or Selling Partner Support (Restricted) is read in Amazon's documents, not yet seen on a live account (SU46, SU60).
70
+
71
+ ## Deprecations
72
+
73
+ - Finances v0 `listFinancialEvents`, `…ByGroupId` and `…ByOrderId` were deprecated on 2025-07-21; their removal date is the one on the *SP-API Deprecation Schedule* (SU36).
74
+ - Orders v0 was deprecated on 2026-01-28, with Orders v2026-01-01 (`searchOrders`, `getOrder`) as successor on the same roles; its removal date is on the schedule (SU37).
75
+ - The old settlement flat-file and XML reports were removed on 2026-11-11 (SU38).
76
+ - The schedule and a release note give different removal dates for `analytics_salesAndTraffic_2023_11_15` (SU39).
77
+ - The six inventory adjustment, receipt and reconciliation report types older claims guides name were removed on 2023-01-31 (SU42).
78
+ - No release note or deprecation from 2025-01 to 2026-11-04 adds, changes or removes an FBA claims report type, the ledger or the reimbursements report (SU41).
79
+ - 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,52 @@
1
+ # Recovery: the seller's choices and the amount owed
2
+
3
+ ## The choices, side by side
4
+
5
+ - Whether to file oneself, pay a share to a service, use a subscription or ERP tool, enter a sourcing cost, or leave a kind alone is the seller's choice; none is picked here (EC25).
6
+ - Filing in Seller Central oneself: no commission, the seller's own time, and every kind has its window (EC25).
7
+ - A commission service: it files for the seller, takes a share of what is paid, possibly including money Amazon would have paid anyway depending on the contract, and its look-back does not reopen closed windows (EC25, EC4).
8
+ - A subscription or ERP tool: it finds candidates and the seller files, for a fixed fee or none (EC25, EC23).
9
+ - Entering a sourcing cost on Manage Your Sourcing Cost: once Amazon approves it, eligible pre-order reimbursements issued after the approval date are valued at the seller's own cost instead of Amazon's estimate (EC25, VR8).
10
+ - Earlier payments, a declined entry and unsellable units: ../claim-value/SKILL.md.
11
+ - Leaving a kind alone: the money in that kind lapses when its window closes, and Amazon's automatic payments continue regardless (EC25).
12
+ - A vendor's fee, look-back and contract terms are read on the vendor's own page and contract; no Amazon page or SP-API read gives them (EC4, EC25).
13
+ - How seller tools book a reimbursement: @comchatx/cx-amazon-finance-playbook, its refunds-and-reimbursements skill.
14
+
15
+ ## The market
16
+
17
+ - No Amazon page read bars or endorses third-party reimbursement services (FL19).
18
+ - SPS Commerce bought Carbon6 (Seller Investigators, ChargeGuard), announced 2025-01-02 and closed 2025-02 by its two filings' dates, and announced on 2026-06-30 the completed sale of its 3P Revenue Recovery business at an estimated loss, citing its 1P focus (EC11).
19
+ - On its earnings calls SPS cited Amazon's policy changes and the take-rate model (EC11).
20
+ - The "short shipment" and "redispute" changes SPS said hurt recovery in 2026 concern, by the call's own words, suppliers' shipments to Amazon Retail, not FBA seller claims (EC14).
21
+ - Services publish success rates (GETIDA, Seller Investigators as AmpliSell relays it, Nova Data) that state no denominator or method (EC22).
22
+ - No Chinese tool or service found files claims for a commission at a current public rate; 船长BI offers a zero-commission assistant covering warehouse lost or damaged only, and 领星, 积加, 赛狐 and 易仓 estimate while the seller files (EC23).
23
+ - Lingxing ties a claim to its payment by a seller-entered CASE ID found in the Reimbursements report and shows the ledger `Reference ID` beside each candidate, under per-case and per-day limits of its own; other practitioners match by FNSKU and date range instead (SU43).
24
+ - Lingxing values a dimension overcharge as (fee charged − expected fee) × quantity, from the fee preview's measured dimensions, one method among those set side by side (SU44).
25
+
26
+ ## What is published, and what is not
27
+
28
+ - Amazon publishes no fulfilment-centre loss rate, no share of cases paid without a claim and no reimbursement total; every "share of revenue owed" figure found is a vendor's or tool maker's and states no method (EC6).
29
+ - Vendor figures from before Amazon's 2024 window changes, its automation dates or its 2025-03-31 move to sourcing cost measure a pool Amazon has since changed (EC7).
30
+ - The loss-rate inputs recovery calculators use (ecomcalctools, Captain BI) are not sourced (EC17).
31
+ - No peer-reviewed or industry study of FBA loss, damage or reimbursement rates was found; the nearest research measures store record inaccuracy, store shrink and online returns (EC18).
32
+ - Single sellers have published their own inbound accuracy and lost-unit counts, which are counts for one account, not rates for FBA (EC16).
33
+ - On customer returns vendors contradict each other: GETIDA reports Amazon auto-pays almost all FBA customer-return issues, sellerboard says unreturned returns are almost entirely seller-initiated (EC15).
34
+ - No page read gives the share of a seller's former recoveries left claimable after Amazon's 2024–2025 changes (EC28).
35
+
36
+ ## Amazon's words on the value
37
+
38
+ - For a unit lost or damaged before a customer order, the per-unit fall from Amazon's 2025-03-31 move to sourcing cost works out, as an inference from the two bases, to 1 − sourcing cost ÷ (sale price − fees), with the cost from Manage Your Sourcing Cost, which no operation reads (EC8).
39
+ - Amazon's spokesperson gave the change's purpose as "a more consistent approach as more sellers are using our supply chain services", and said specific cost data is not shared with any other seller, Amazon Retail included (EC9).
40
+ - Value per unit follows the moment of loss: before an order at sourcing cost, a customer return on a post-order basis after fees whose exact basis is contested; details in ../claim-value/SKILL.md (EC10).
41
+
42
+ ## The amount owed, as a formula
43
+
44
+ - A model inferred over Amazon's dated rules, not Amazon's, puts what an amount owed is made of, by kind, as units through the stage × incidence × value per unit × the share Amazon does not pay unasked; the window then cuts what can still be claimed (EC19).
45
+ - Units through the stage: `GET_LEDGER_SUMMARY_VIEW_DATA` receipts, or Fulfillment Inbound v0 `getShipmentItems` `QuantityReceived` (Amazon Fulfillment) (EC19, SU4).
46
+ - Incidence: the ledger detail's adjustment events against receipts, and v0 `QuantityShipped` against `QuantityReceived` (EC17).
47
+ - Value per unit: the seller's sourcing cost, or sale price and fees from `listTransactions` and the fee preview (EC8, EC19).
48
+ - The share Amazon pays unasked is a fact of the seller's store: whether `Lost_Warehouse` and `Damaged_Warehouse` rows with blank `case-id` arrive in its `GET_FBA_REIMBURSEMENTS_DATA` after its automation date, against the ledger's lost and damaged adjustments; that a blank `case-id` means paid unasked is read in Amazon's documents, not yet seen on a live account (EC27).
49
+ - For customer returns, the split is customer-return rows with blank against filled `case-id`, joined to refunds in `listTransactions` and to the FBA customer returns report (EC15).
50
+ - For a mismeasured SKU, what is left is the per-unit overcharge times the units charged inside the itemised fee window, while a non-itemised error reaches further back (EC21).
51
+ - The seller's own history of what Amazon paid is `GET_FBA_REIMBURSEMENTS_DATA`: `amount-total` by `reason`, cash against inventory quantities, reversals netted through `original-reimbursement-id`, on Pricing or Amazon Fulfillment (EC26).
52
+ - A store's remaining share is read from its own reimbursements, by `reason` and by blank against filled `case-id`, before and after its automation date and 2025-03-31; what that share is for a live store is read in Amazon's documents, not yet seen on a live account (EC28).
@@ -0,0 +1,28 @@
1
+ # Windows and stores: where each kind's window is stated
2
+
3
+ ## The windows by kind
4
+
5
+ - The table of windows by kind and store as read, and warehouse losses: ../warehouse-claims/SKILL.md.
6
+ - Read together, Amazon's windows and the services' look-backs mean, by inference, that what an audit can still claim is bounded by each kind's window in the seller's store, not by a service's look-back, so whether a look-back exceeds the window depends on the kind and on which statement governs the store (EC4).
7
+ - Warehouse lost or damaged: set per store and changed by announcement, stated on *FBA inventory reimbursement policy* (G200213130), which the seller sees signed in, and in the store's latest News post on claim windows, read by plain GET; no operation returns it (FC9).
8
+ - Customer returns: counted from the refund or replacement date, stated on *Customer return claims* (G9N934L7Y4SFWPJ4), which the seller sees signed in, and in the store's latest News post (RT4).
9
+ - Amazon's 2024 posts under one title give customer-return windows whose bounds differ between the US post and the Canada and UK posts, and a 2026-08-13 US staff post states a different one again; each is that store's statement on its date, and which the claim tool enforces is read in Amazon's documents, not yet seen on a live account (EC5).
10
+ - Missing from inbound: a per-store length counted from verified delivery, filed after the shipment is closed, stated on *FBA inventory reimbursement policy: Shipment to Amazon claims* (GEYPWTSQRTXXXMVB), which the seller sees signed in, and in the store's News (IN7).
11
+ - Removals: an earliest and a latest day for lost in transit and a latest day for other removal claims, per store and date, on the store's removals-claims page and its latest News post (RM6).
12
+ - Removal grading disputes: length and anchor per store and date, on the store's removals-claims page or tool (RM12).
13
+ - Valuation disputes: every policy text read counts from the reimbursement's issue, while Australia's News post counts from the initial claim; the length is on G200213130 as the seller's store shows it and in that store's latest News post (VR20).
14
+ - FBA fee errors: Amazon staff state a window from each charge's date for itemised fees and a longer limit for non-itemised ones, on *FBA fees reimbursement policy: Weight and dimensions* (GL7U4JFSDXUTQAJ), which the seller sees signed in, and the store's latest staff guide; the charge date is `listTransactions` `postedDate` (FE9, EC21).
15
+ - One Chinese claim assistant, 船长BI, states a fixed span a first claim reaches back; by inference, items in it outside the window Amazon applies to their kind are not claimable (EC24).
16
+ - Fee claims, valuation and inbound in detail: ../fee-claims/SKILL.md, ../claim-value/SKILL.md and ../shipment-claims/SKILL.md.
17
+
18
+ ## Where Amazon contradicts itself
19
+
20
+ - For UK warehouse-lost units, a UK staff post of 2026-04-06 says the claim is manual, with automatic reimbursement disabled there since 2022-08, against Amazon's UK News posts stating automatic reimbursement from 2025-01-15; both are stated, neither picked (FC5, EC27).
21
+ - Amazon announced automatic reimbursement of warehouse-lost units store by store, each in its own News thread with its own start date (2024-11-01 in the US and Canada; the UK in its own post), and no such announcement was found for any store besides the US, Canada and the UK (FC3, FC4).
22
+
23
+ ## A forum post's store
24
+
25
+ - A Seller Forums post's store is the `marketplaceId` in its own post object, the same on every forum host, while `selectedMarketplaceId` follows the host; Amazon does not document the field, and the reading was checked on four posts whose store their own words fix (FC45).
26
+ - Amazon issues one News text as separate threads per store with values that differ between the copies, so a value read in one thread is that store's value only (FC46).
27
+ - On a seller's post the field is the store the seller posted under, which can differ from the store the post discusses (FC47).
28
+ - The post-to-store table: ../warehouse-claims/SKILL.md.
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: claim-value
3
+ description: "How much an Amazon FBA reimbursement is worth, not whether one is owed, and when Amazon takes a paid one back: the basis a reimbursed unit is valued on (sourcing cost since Amazon's 2025-03-31 change, Amazon's estimate where the seller entered none, the reduced estimate for unsellable units, sale price minus fees after an order and on customer-return claims, where Amazon's texts differ), Manage Your Sourcing Cost and its limits and invoices, Chinese invoices (发票) and Japan's 原価の管理, the per-unit cap by store, the valuation dispute and what its window counts from, amount-per-unit in GET_FBA_REIMBURSEMENTS_DATA, units put back instead of cash, cross-border currency, and Reimbursement_Reversal rows and found units. For any question about why a reimbursement looks low, what a lost unit should have paid, a sourcing cost entry, re-evaluating a value, or a reimbursement Amazon reversed."
4
+ ---
5
+
6
+ ## What a loss is worth
7
+
8
+ A unit lost before a customer order is valued at sourcing cost from each store's own date, after 2025-03-31 in the US, CA, UK, DE, FR, IT and ES texts (VR2, VR4).
9
+ Sourcing cost is the seller's approved Manage Your Sourcing Cost (MYSC) figure, else Amazon's estimate (VR5, VR8).
10
+ A unit lost after an order is valued on the order; which basis a store applies today is read in Amazon's documents, not yet seen on a live account (VR27).
11
+ Unsellable units take a reduced estimated cost before an order; after one, the US, CA, UK and DE texts give the discounted sale price minus fees (VR25, VR26).
12
+ A per-unit cap differs by store; it is on *FBA inventory reimbursement policy*, which the seller sees signed in, and in Amazon's dated redlines, read by plain GET (VR29).
13
+
14
+ ## Sourcing cost
15
+
16
+ MYSC holds one cost per FNSKU per marketplace, entered by the seller in Seller Central; no SP-API operation reads or writes it (VR7, VR18).
17
+ An approved cost applies only to reimbursements issued after its approval, per US-store staff (VR8).
18
+ Amazon limits cost updates per FNSKU, counts differing by store and date, and invoice age, two US-store posts differing (VR11, VR14).
19
+
20
+ ## Disputing a value
21
+
22
+ A valuation dispute is the seller's step in Seller Central, within a window each store's text sets, counted from the reimbursement or, in Australia's News post, the claim (VR20, VR21).
23
+
24
+ ## Reading a line
25
+
26
+ `GET_FBA_REIMBURSEMENTS_DATA` names no basis, cost in force, cap or store (VR30).
27
+ A line with units put back moves stock, not money (VR34).
28
+
29
+ ## Taken back
30
+
31
+ Amazon's policy reverses for error or a found unit, with no stated time limit or amount rule (VR36).
32
+
33
+ How a call is made and a report is asked for and landed: the amazon-sp-api skill's references/door.md.
34
+ How a reimbursement posts to money: @comchatx/cx-amazon-finance-playbook, its refunds-and-reimbursements skill.
35
+
36
+ ## References
37
+
38
+ [rule.md](references/rule.md): the dated rule, the estimate, Japan.
39
+ [sourcing-cost.md](references/sourcing-cost.md): MYSC, limits, proofs, Chinese invoices.
40
+ [disputes.md](references/disputes.md): the window and its routes.
41
+ [basis.md](references/basis.md): unsellable, post-order, customer return, cap.
42
+ [lines.md](references/lines.md): a line's amount, units, currency.
43
+ [reversals.md](references/reversals.md): reversals and found units.
44
+ [warehouse-claims](../warehouse-claims/SKILL.md), [shipment-claims](../shipment-claims/SKILL.md), [return-claims](../return-claims/SKILL.md), [fee-claims](../fee-claims/SKILL.md): what is owed, by kind.
45
+ [claim-filing](../claim-filing/SKILL.md): where a claim is filed.