@comchatx/cx-amazon-claims-playbook 0.0.0-stage → 0.1.1
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.
- package/LICENSE +21 -0
- package/README.md +13 -2
- package/README.zh-CN.md +14 -0
- package/package.json +110 -4
- package/prompts/claims-audit.md +5 -0
- package/prompts/fee-check.md +5 -0
- package/prompts/inbound-shortfall.md +5 -0
- package/prompts/reimbursement-value.md +5 -0
- package/prompts/returns-check.md +5 -0
- package/skills/claim-filing/SKILL.md +46 -0
- package/skills/claim-filing/references/conduct.md +31 -0
- package/skills/claim-filing/references/filing.md +62 -0
- package/skills/claim-filing/references/no-door.md +34 -0
- package/skills/claim-filing/references/reads.md +79 -0
- package/skills/claim-filing/references/recovery.md +52 -0
- package/skills/claim-filing/references/windows-and-stores.md +28 -0
- package/skills/claim-value/SKILL.md +45 -0
- package/skills/claim-value/references/basis.md +25 -0
- package/skills/claim-value/references/disputes.md +29 -0
- package/skills/claim-value/references/lines.md +31 -0
- package/skills/claim-value/references/reversals.md +22 -0
- package/skills/claim-value/references/rule.md +31 -0
- package/skills/claim-value/references/sourcing-cost.md +43 -0
- package/skills/fee-claims/SKILL.md +43 -0
- package/skills/fee-claims/references/certification.md +29 -0
- package/skills/fee-claims/references/fee-kinds.md +76 -0
- package/skills/fee-claims/references/measurement.md +33 -0
- package/skills/fee-claims/references/reads.md +37 -0
- package/skills/fee-claims/references/windows.md +37 -0
- package/skills/return-claims/SKILL.md +37 -0
- package/skills/return-claims/references/edges.md +37 -0
- package/skills/return-claims/references/outcomes.md +48 -0
- package/skills/return-claims/references/reads.md +25 -0
- package/skills/return-claims/references/windows.md +24 -0
- package/skills/shipment-claims/SKILL.md +36 -0
- package/skills/shipment-claims/references/disposals.md +33 -0
- package/skills/shipment-claims/references/inbound-programs.md +33 -0
- package/skills/shipment-claims/references/inbound.md +49 -0
- package/skills/shipment-claims/references/reads.md +31 -0
- package/skills/shipment-claims/references/removals.md +49 -0
- package/skills/warehouse-claims/SKILL.md +45 -0
- package/skills/warehouse-claims/references/ledger.md +49 -0
- package/skills/warehouse-claims/references/paid-without-claim.md +66 -0
- package/skills/warehouse-claims/references/scope.md +57 -0
- package/skills/warehouse-claims/references/windows-and-idr.md +39 -0
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Reads: the FBA Returns report and the replacement link
|
|
2
|
+
|
|
3
|
+
## The FBA Returns report
|
|
4
|
+
|
|
5
|
+
- `GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA` lists only units received at a fulfilment centre; it is updated daily, can only be requested, is tab-delimited and answers to Pricing or Amazon Fulfillment (RT32, SU3).
|
|
6
|
+
- A refund given without a return is never in it (RT32).
|
|
7
|
+
- `return-date` is the date the returned unit was processed at the centre (the help page as the listing pack read it), not the refund date; the claim clock counts from the refund or replacement (RT33).
|
|
8
|
+
- Column names differ by source: the SP-API page has `order-id` and `license-plate-number`, the help page as the listing pack read it has `lpn`, and Openbridge, a data vendor, gives `amazon-order-id` and `lpn`; which of these a seller's file carries is read in Amazon's documents, not yet seen on a live account (RT34).
|
|
9
|
+
- Dispositions are written with a space on Amazon's help page as the listing pack read it (`CUSTOMER DAMAGED`) and with an underscore in a practitioner's copy (`CUSTOMER_DAMAGED`); read in Amazon's documents, not yet seen on a live account (RT35).
|
|
10
|
+
- Status values appear in sentence case, capitalised differently, in two copies of Amazon's page, and partly in UPPER_SNAKE in one ERP's filters (`IMMEDIATE_DISPOSAL`); read in Amazon's documents, not yet seen on a live account (RT35).
|
|
11
|
+
- `reason` is chosen by the buyer from a list; Amazon's codes and their descriptions are held by the listing pack (RT38).
|
|
12
|
+
- Amazon's SP-API pages state no look-back for the returns, replacements and reimbursements reports (SU16).
|
|
13
|
+
- No SP-API notification announces an FBA customer return's receipt or grading; `SHIPMENT_TRACKING_MILESTONE_CHANGED` carries `RETURN_RECEIVED`, a carrier-tracking milestone its schema does not tie to FBA customer returns (RT40).
|
|
14
|
+
|
|
15
|
+
## The replacement link
|
|
16
|
+
|
|
17
|
+
- `GET_FBA_FULFILLMENT_CUSTOMER_SHIPMENT_REPLACEMENT_DATA` covers only NA and IN stores and needs Amazon Fulfillment (RT20).
|
|
18
|
+
- Elsewhere the link from a replacement to its original is Orders v0 `IsReplacementOrder` / `ReplacedOrderId`, deprecated, or Orders v2026-01-01 `associatedOrders` with `REPLACEMENT_ORIGINAL_ID` (RT20, SU37).
|
|
19
|
+
- Whether the orders read shows every replacement outside NA and IN, customer-service replacements included, is read in Amazon's documents, not yet seen on a live account (RT20).
|
|
20
|
+
|
|
21
|
+
## The money side
|
|
22
|
+
|
|
23
|
+
- The Reimbursements report's columns and `reason` values: @comchatx/cx-amazon-finance-playbook, skill refunds-and-reimbursements.
|
|
24
|
+
- What a paid row says about its claim and its value: ../claim-value/SKILL.md.
|
|
25
|
+
- How a report is asked for and landed: the amazon-sp-api skill's references/door.md.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# The customer-return window
|
|
2
|
+
|
|
3
|
+
## The rule
|
|
4
|
+
|
|
5
|
+
- The window counts from the customer refund or replacement date (RT4).
|
|
6
|
+
- Amazon refuses a claim filed before the window opens or after it closes (RT4).
|
|
7
|
+
- The day counts differ by store and Amazon's posts disagree; the window is read for the seller's store on *Customer return claims* as the seller sees it signed in in Seller Central, and in the latest Seller Forums News post on claim windows for that store, read by plain GET (RT4).
|
|
8
|
+
- This pack reads a News post's store from the post object's `marketplaceId`, which stays the same on every forum host; on four posts checked the field named the post's own store, and Amazon does not document it (RT5, FC45).
|
|
9
|
+
- The returns report's `return-date` is the processing date at the centre, not the refund date the window counts from (RT33).
|
|
10
|
+
- Where a refund's date posts in the seller's money: @comchatx/cx-amazon-finance-playbook, skill refunds-and-reimbursements.
|
|
11
|
+
|
|
12
|
+
## Amazon's statements, read 2026-11-13, none picked
|
|
13
|
+
|
|
14
|
+
- US: News 81c3235d, posted 2024-07-24, effective 2024-10-23, states the window after the refund or replacement date and that claims must not be submitted before it opens (RT4, RT5, EC5).
|
|
15
|
+
- Canada: News 6605eede, the same announcement posted 0.7 seconds apart from the US issue, states a different window for Canada, effective 2024-10-23 (RT5).
|
|
16
|
+
- UK (News d0fc997e, 2024-10-10; 9a92846d, 2025-01-15), Sweden (News 1101821c, 2025-01-15) and Australia (News d8f9a56c, 2025-08-14): each states the window counted from the refund or replacement date for its store (RT4).
|
|
17
|
+
- US staff post 0e07abc1 of 2026-08-13 states a window whose end differs from the US News post's (EC5).
|
|
18
|
+
- Chinese media of 2025-01 reported a US move to another window; no US post read carries it, and the posts of 2025-01-15 with that window are the Sweden and UK issues (RT7).
|
|
19
|
+
- Which of these statements the claim tool enforces for a store is open: read in Amazon's documents, not yet seen on a live account (RT4, EC5).
|
|
20
|
+
|
|
21
|
+
## The not-returned clock
|
|
22
|
+
|
|
23
|
+
- 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 (RT1).
|
|
24
|
+
- Amazon staff posts state that number for the US and Canada; where the seller sees it for any other store is open, not yet seen on a live account (RT1).
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: shipment-claims
|
|
3
|
+
description: "What Amazon owes a seller for FBA units lost, damaged or short on the way into Amazon or back out, keyed by shipment or removal order. Inbound: a shipment received short or damaged, receiving discrepancies, Research missing units on the Contents tab, CLOSED and the eligibility date, overages, proof of ownership and delivery, partnered against own carrier, small parcel against LTL, carrier-damaged arrivals, the US prep change, the end of commingling, AWD and AWD-to-FBA shipments, AGL freight, loss with a forwarder. Outbound: removals lost, short, damaged or different, grading disputes, the removal reports, cancelled removal units, removal and disposal without a unit, liquidation shortfalls, dangerous-goods disposals and stranded removals; where each window is stated per store. For any question about a shipment to Amazon that arrived short or damaged, or a removal, disposal or liquidation Amazon may owe for."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
## Into Amazon
|
|
7
|
+
|
|
8
|
+
Amazon's policy covers units lost or damaged at a facility or by a carrier operated by or for Amazon, if, among other conditions, the seller sent the plan's items and quantities (IN1, IN39).
|
|
9
|
+
Arrivals classed distributor damaged or damaged by inbound carrier were damaged before receipt; Amazon names the seller's carrier as the route (IN2).
|
|
10
|
+
The window is a per-store length from verified delivery, filed after the shipment is closed; Amazon states it for the US and for the UAE, Saudi Arabia and Egypt, and no page read states it for the UK, the EU or JP (IN7, IN8, IN9, IN35, IN36).
|
|
11
|
+
No operation returns the verified delivery date, the eligibility date or the reconciliation result; Seller Central shows them (IN10, IN29).
|
|
12
|
+
Amazon allows one claim per shipment and declines further ones (IN17, FL7).
|
|
13
|
+
Window, research, evidence, carriers, overages: references/inbound.md.
|
|
14
|
+
Prep and labels, commingling, AWD, AGL, first mile: references/inbound-programs.md.
|
|
15
|
+
|
|
16
|
+
## Out of Amazon
|
|
17
|
+
|
|
18
|
+
A removal claim covers units lost or damaged by Amazon or a carrier Amazon used on the way to the seller's return address; each 2024 automation post says these are filed by hand (RM1, RM2).
|
|
19
|
+
Kinds: lost in transit; damaged in transit; damaged, different or incomplete units received; grading disputes on customer returns (RM3).
|
|
20
|
+
The route is "Resolve a removal order issue", keyed by removal order ID (RM4).
|
|
21
|
+
Windows and their anchors differ by store and date, and Amazon's US texts disagree with each other (RM6, RM7, RM8, RM10).
|
|
22
|
+
The claim asks for a shipment ID that no SP-API report read carries; read in Amazon's documents, not yet seen on a live account (RM14, RM15).
|
|
23
|
+
Windows, grading, evidence, value: references/removals.md.
|
|
24
|
+
Cancelled units, fees, disposals, liquidation, dangerous goods, stranded units: references/disposals.md.
|
|
25
|
+
|
|
26
|
+
## Reads and the seller's steps
|
|
27
|
+
|
|
28
|
+
No operation opens an inbound or removal claim or attaches its evidence; each is the seller's step in Seller Central (IN29, RM35, SU12).
|
|
29
|
+
Reports, operations, roles and their pitfalls: references/reads.md.
|
|
30
|
+
Calls and reports: the amazon-sp-api skill's references/door.md.
|
|
31
|
+
Shipment state: @comchatx/cx-amazon-stock-playbook, its stock-inbound skill.
|
|
32
|
+
What a claim pays: ../claim-value/SKILL.md.
|
|
33
|
+
Filing routes, limits and conduct: ../claim-filing/SKILL.md.
|
|
34
|
+
Units lost inside the network after receipt: ../warehouse-claims/SKILL.md.
|
|
35
|
+
Customer returns and their grading: ../return-claims/SKILL.md.
|
|
36
|
+
Inbound and removal fees charged wrongly: ../fee-claims/SKILL.md.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Cancelled removals, fees, disposals, liquidation, dangerous goods, stranded units
|
|
2
|
+
|
|
3
|
+
## Cancelled units and per-unit fees
|
|
4
|
+
|
|
5
|
+
- Amazon cancels removal-order units that are not available for removal, for example units tied to a pending customer order; cancelled units stay in Amazon's network or were sold (Jameson_Amazon, 2024-11-12; PrepVia) (RM25).
|
|
6
|
+
- Removal and disposal fees now post per unit as each unit is removed or disposed, where they once posted when the whole order completed; the change date is per store, read on each store's News post by plain GET (US post 2f4edad8, article 2026-01-29; UK post 862f270b, posted 2026-04-09) (RM26).
|
|
7
|
+
- Under per-unit charging, a removal or disposal fee with no matching shipped or disposed unit for that order and FNSKU has no basis in Amazon's stated rule, by the research's inference from that rule; read in Amazon's documents, not yet seen on a live account (RM26, RM27).
|
|
8
|
+
- Fee rates and where the charge posts: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
|
|
9
|
+
- A removal fee disputed as wrongly charged: ../fee-claims/SKILL.md.
|
|
10
|
+
|
|
11
|
+
## Disposals
|
|
12
|
+
|
|
13
|
+
- The policy (US PDF 2024-12-18) excludes units disposed of at the seller's request, by Amazon's exercise of a right, or pending disposal, while practitioners (Seller Labs, 2026-03-18; Seller Investigators) claim units Amazon disposed of without a request as reimbursable; the two disagree (RM28).
|
|
14
|
+
- Because a grading dispute needs the unit returned, a disposed unit cannot be graded in dispute, and an automated or required disposal can remove that path; this is the research's inference from Amazon's text (RM13).
|
|
15
|
+
|
|
16
|
+
## Liquidation
|
|
17
|
+
|
|
18
|
+
- The removals page's scope sentence covers units on their way to the seller's returns address; liquidation units go to a liquidator, and no Amazon text read names a claim for liquidation units lost before the liquidator or for proceeds below the typical recovery Amazon staff describe (Topher_Amazon, 2025-06-23) (RM44).
|
|
19
|
+
- A liquidation buyer's damage or shortfall comes back as `RemovalShipmentAdjustmentEvent`, a negative `RevenueAdjustment` against the removal order, not as a reimbursement; a liquidation sale posts as `RemovalShipmentEvent` with `TransactionType` `WHOLESALE_LIQUIDATION` (RM29).
|
|
20
|
+
- The US liquidation payment event `FBALiquidationEvent` carries no quantity and no SKU (`PostedDate`, `OriginalRemovalOrderId`, `LiquidationProceedsAmount`, `LiquidationFeeAmount`); units liquidated per FNSKU are read from `RemovalShipmentEvent` lines and joined to Removal Order Detail by order id; read in Amazon's documents, not yet seen on a live account (RM45).
|
|
21
|
+
|
|
22
|
+
## Dangerous goods
|
|
23
|
+
|
|
24
|
+
- Amazon may dispose of units of a product it classes unfulfillable dangerous goods, stating the Business Solutions Agreement as the basis, and the eligibility reason code `FBA_INB_0015` asks the seller to contact Seller Support within a number of business days of the notice, read in the notice and in `getItemEligibilityPreview` reason text (Amazon Fulfillment) (RM38).
|
|
25
|
+
- Under the Australian Business Solutions Agreement (PDF 2024-06-12, F-7.2, F-7.3), Amazon may dispose of an Unsuitable Unit at once for a safety, health or liability risk, the seller "deemed to have consented", otherwise after a notice period; title passes to Amazon, which may keep any proceeds; other stores' agreements were not read (RM39).
|
|
26
|
+
- No Amazon text read makes a unit disposed of after a dangerous-goods classification reimbursable, a classification the seller holds wrong included: the US policy PDF of 2024-12-18 excludes units failing FBA product restrictions and units disposed of by Amazon's right, Seller Support's relayed text says such units "may be subject to disposal without reimbursement", and staff called an immediate disposal after DG-programme approval "the correct actions" (2026-08-10); sellers ask under the lost-and-damaged policy, with no outcome read (RM40).
|
|
27
|
+
- The challenge Amazon names against a dangerous-goods classification is the review: a safety data sheet or exemption sheet within the time Amazon states, failing which the units are disposed of at the seller's expense; it runs before disposal, and no route after disposal was read (Michelle_Amazon, 2025-06-06) (RM41).
|
|
28
|
+
- Sellers report that a removal order cannot be created, or fails, while an ASIN stands classified as dangerous goods, so units can be disposed of without having left (2024-08-02; 2025-12-04) (RM42).
|
|
29
|
+
|
|
30
|
+
## Stranded units
|
|
31
|
+
|
|
32
|
+
- By the research's reading of the policy's wording, a removal of stranded units is a removal like any other once the units leave, under the removals page's scope, windows and evidence, and a disposal under the stranded settings, or with no setting, falls in the policy's excluded classes (RM43).
|
|
33
|
+
- Stranding itself: @comchatx/cx-amazon-stock-playbook, its stuck-stock skill.
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# Inbound programmes: prep and labels, commingling, AWD, AGL, first mile
|
|
2
|
+
|
|
3
|
+
## Prep and labels
|
|
4
|
+
|
|
5
|
+
- For US shipments created from 2026-01-01, units arriving without proper prep and item labelling are not reimbursed if damaged or "untraceable"; shipments created before keep Amazon's prep service even if they arrive later; this covers inventory reaching US FBA through AWD, AGL, Amazon SEND and Supply Chain Portal (Jameson_Amazon, US, 2025-12-01; the boundary day is the research's reading of "created before" and "created after") (IN23).
|
|
6
|
+
- A plan's creation date is `createdAt` from `getInboundPlan` or `listInboundPlans`, and the prep and label owner per item is `prepOwner` and `labelOwner` (Amazon Fulfillment) (IN23).
|
|
7
|
+
|
|
8
|
+
## The end of commingling
|
|
9
|
+
|
|
10
|
+
- Amazon's UK and Canada News posts of 2025-12-08 announced that commingling ends for inventory shipped from a date the posts state, read by plain GET; brand representatives with a manufacturer barcode need no Amazon sticker, while resellers and products without one use Amazon stickers; the posts say nothing about reimbursement (IN24).
|
|
11
|
+
- PPC Land (2026-03-24) reports that after the change units arriving without the required barcode are flagged defective and not reimbursed; a practitioner's report (IN25).
|
|
12
|
+
|
|
13
|
+
## AWD inbound and AWD to FBA
|
|
14
|
+
|
|
15
|
+
- AWD shipment claims take the window of the MCF inventory reimbursement policy, counted from verified delivery to the AWD site, with one claim per shipment and one AWD facility claim per box, filed by support case; units lost in AWD transit to an FBA centre are reimbursed under the MCF policy and valued by its methodology (AWD service terms, 2026-01-14) (IN26, IN17).
|
|
16
|
+
- The "MCF inventory reimbursement policy" the AWD terms name is the page *Supply Chain Portal (SCP) Reimbursements policy - Amazon Supply Chain Services (ASCS)* on supplychain.amazon.com, linked at each of its five mentions; its window, cap and valuation are its own, read there by plain GET, and its eligibility requires an MCF account "in Active state" (IN34, FL27).
|
|
17
|
+
- The AWD terms set a filing window for fee claims on box dimensions, counted from the charge date (section 4.2), read on the terms by plain GET (IN33).
|
|
18
|
+
- The AWD model returns expected and received quantity per SKU for an AWD inbound shipment (`getInboundShipment` with `skuQuantities=SHOW`) in product units, cases or pallets, and Amazon's tutorial says no AWD report is in the API; the role is Amazon Warehousing and Distribution, outside the five, and would open that count (IN27).
|
|
19
|
+
- AWD to FBA replenishment shipments carry FBA shipment IDs; for missing units on them staff opened cases and asked for proof of ownership, not proof of delivery (KJ_Amazon, US, 2025-02-13) (IN28).
|
|
20
|
+
|
|
21
|
+
## Amazon Global Logistics
|
|
22
|
+
|
|
23
|
+
- Under the *Amazon Global Logistics Freight Service Terms* (dated 2026-01-14), Amazon bears risk of loss only from receipt at Origin until delivery at Destination, which means an Amazon facility; for China-origin ocean carriage the contracting party is Beijing Century Joyo Courier Co., Limited, and claims go only against that party, not the carrier (IN37).
|
|
24
|
+
- For a sealed container Amazon could not count, delivered with the seal intact, Amazon is not liable for shortages or damage unless proximately caused by its own independent action, nor for loss caused by inadequate packaging (IN37).
|
|
25
|
+
- An AGL Freight loss or damage claim is a written notice within a period counted from delivery, or from the scheduled delivery date for lost cargo; legal action has its own period from Amazon's written disallowance; a credited amount not contested in writing within a stated period is a complete settlement (IN38).
|
|
26
|
+
- Recovery is limited per shipment for an ocean bill of lading to the US unless higher liability was agreed in writing at booking, otherwise by the convention or the customs-declared value, whichever is less, with a cumulative cap per period; the seller must prove negligence of Amazon, its contractor or the performing carrier, and must insure the cargo itself (IN38).
|
|
27
|
+
- Each AGL period and limit is read on the terms as dated on supplychain.amazon.com by plain GET; Amazon's Seller Central AGL claims page is one cx cannot read, and the seller sees it signed in (IN38).
|
|
28
|
+
- AGL's billing clauses: @comchatx/cx-amazon-finance-playbook, its fees-and-charges skill.
|
|
29
|
+
|
|
30
|
+
## The first mile
|
|
31
|
+
|
|
32
|
+
- By the research's reading of the policy's scope sentence, loss before Amazon signs, with a carrier or forwarder the seller engaged, falls outside it; Amazon's Chinese article names forwarder, warehouse and customs counting errors and cartons broken in transit as causes of in-box shortfalls (gs.amazon.cn, 2025-08) (IN39).
|
|
33
|
+
- Practitioners describe first-mile recovery as a claim against the forwarder or airline under its contract, each theirs: an exception noted on the delivery document at receipt, a short written notice for hidden damage, weight-based convention limits unless the cargo was insured, and a set of AWB or bill of lading, commercial invoice, packing list and photos (百运网, 2026-11-09); 深圳美辰物流 (AMZ123, 2023-10-27) tells a carrier problem from a warehouse problem by the tracking (IN40).
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Inbound claims: scope, window, research, evidence, carriers, overages
|
|
2
|
+
|
|
3
|
+
## Scope at the door
|
|
4
|
+
|
|
5
|
+
- Amazon's FBA reimbursement policy covers items lost or damaged "at a facility or by a carrier operated by Amazon or on behalf of Amazon", one of its conditions being that the seller sent "the exact items and quantities stated in your shipping plan" (US policy PDF 2024-12-18; DE 2025-02-24) (IN1).
|
|
6
|
+
- Arrivals classed "distributor damaged" or "damaged by inbound carrier" were damaged before Amazon received them; they are unfulfillable and removed, and the reimbursement route Amazon names is the seller's carrier (NR_Amazon, US, 2025-04-11) (IN2).
|
|
7
|
+
- Loss before delivery, while the goods are with a carrier or forwarder the seller engaged, is outside the policy's scope sentence and is claimed under the seller's contract with that carrier; that scope reading is the research's inference from the sentence (IN39).
|
|
8
|
+
- Amazon's policy puts shipment-to-Amazon claims in its pre-order class, valued at sourcing (earlier manufacturing) cost; the "estimated proceeds" sentence is struck in the rendered US 2024-12-18, US 2025-02-24 and JP 2025-02-19 texts, so it is the pre-2025 basis (IN21).
|
|
9
|
+
- What that basis pays, and the cap: ../claim-value/SKILL.md.
|
|
10
|
+
|
|
11
|
+
## The window, store by store
|
|
12
|
+
|
|
13
|
+
- The window for units missing from an inbound shipment is a per-store length counted from verified delivery to the fulfilment centre, and the request is filed after the shipment is closed; no operation states it (IN7).
|
|
14
|
+
- US: stated by Amazon moderator Indy_Amazon (2026-08-13), by gs.amazon.cn articles of 2025-03 and 2025-08 marked for the US store, and by a seller quoting the help page (2024-09-26); read in Amazon's documents, not yet seen on a live account (IN7).
|
|
15
|
+
- UAE, Saudi Arabia and Egypt: Amazon's post *Update on reimbursement claim window eligibility on FBA* (posted 2024-08-06, in force from 2024-09-05) sets a minimum and a maximum count of calendar days from the delivery date, issued as three threads, one per store (IN8).
|
|
16
|
+
- None of Amazon's News posts on claim windows for the US, Canada, the UK, Sweden or Australia names a window for shipments to Amazon (IN9).
|
|
17
|
+
- UK: the redline of 2024-12-11 changes the claim windows from 2025-01-09 "except for shipment to Amazon claims" and does not state the inbound length (IN35).
|
|
18
|
+
- EU stores and JP: the EU redline set of 2024-08-20 carries no Shipment to Amazon page and the JP policy of 2025-02-19 names the claims with no length; a UK staff post of 2025-06-06 gives a filing limit for lost or damaged inventory naming no kind and no start, and a UK seller relayed a Seller Central refusal by age since arrival (2025-01-08) (IN36).
|
|
19
|
+
- Where today's value is read for the seller's store: Amazon's help page *FBA inventory reimbursement policy: Shipment to Amazon claims* (GEYPWTSQRTXXXMVB), which cx cannot read and the seller sees signed in; the store's Seller Forums News post on claim windows, read by plain GET; and the shipment's eligibility date on its Contents tab, which the seller sees (IN7, IN11).
|
|
20
|
+
- Practitioners state inbound windows no Amazon page read supports, each theirs: Refunzo (2026-01-18), 百运网 (2026-05-27), Helium 10 and SELLERLOGIC for the EU, and AMZ123 (2025-05-19) (IN31).
|
|
21
|
+
|
|
22
|
+
## Closed, eligible, researched
|
|
23
|
+
|
|
24
|
+
- Amazon's pages define `CLOSED` as all units received or, where counts disagree, a timeout from shipment creation whose length the pages state differently: sell.amazon.com *How to track FBA shipments* (modified 2025-10-03), gs.amazon.cn (2025-08) and a staff post (2023-10-10); the v0 model gives no timeout, and status per shipment is read with `getShipments` (v0) or `getShipment` (2024-03-20) (IN14).
|
|
25
|
+
- A shipment can sit Delivered for some days before Checked-in, longer at peak, up to a maximum Amazon's Chinese article states (gs.amazon.cn, 2025-08); with a partnered carrier it shows Shipped at pickup, with the seller's own carrier once valid tracking is entered (IN32).
|
|
26
|
+
- Seller Central shows per shipment whether it is eligible for investigation and an estimated date; staff call that date standard procedure and say discrepancies "can auto-correct during the receiving process, but it's not guaranteed" (Angie_Amazon, US, 2026-04-09) (IN11).
|
|
27
|
+
- "Investigation completed – shipment contents counted and confirmed" means Amazon matched boxes to the plan and counted the units; the units are then no longer eligible for research, Selling Partner Support adds units it locates, and otherwise Amazon deems them short-shipped and pays nothing (Julia_Amzn, UK, 2024-08-20) (IN12).
|
|
28
|
+
- Submitting a research request creates a Selling Partner Support case whose number shows on the Contents tab; staff give the research's duration as a range, not a rule, read on sell.amazon.com's tracking guide and staff posts, and say not all discrepancies are reimbursed (IN13, FL30).
|
|
29
|
+
- Amazon's Chinese article says a request sent to Seller Support will likely be sent back to the shipment's item page, and that the research does not change the seller's existing inventory (gs.amazon.cn, 2025-08) (IN18).
|
|
30
|
+
- Amazon allows one claim per shipment and declines further claims for it (IN17, FL7).
|
|
31
|
+
|
|
32
|
+
## Evidence
|
|
33
|
+
|
|
34
|
+
- For lost units Amazon asks for the shipment ID; proof of ownership (a supplier invoice, another seller's receipt or the manufacturer's signed packing slip, with purchase date, product names, quantity, issuer and buyer); and proof of delivery: for LTL/FTL an Amazon-stamped document with box count and total weight at pickup, for small parcel active tracking IDs (IN15, FL24).
|
|
35
|
+
- Lost units are filed on the shipment's Contents tab, damaged units through a support case (IN15).
|
|
36
|
+
- Ownership documents are accepted only in a non-editable format (PDF, JPG, JPEG, PNG, TIFF); pro forma invoices and contracts are refused, and the price paid may be hidden (gs.amazon.cn, 2025-03) (IN16).
|
|
37
|
+
- Amazon's Chinese pages name 库存所有权证明 and, for LTL/FTL, a carrier's 提货单 that "须经亚马逊盖章"; Chinese practitioners name the forwarder's stamped 签收单 instead and report that warehouses often do not stamp at receipt (百运网, 2026-05-27; AMZ123, 2024-05-12); whether a 签收单 alone meets the LTL/FTL requirement is read in Amazon's documents, not yet seen on a live account (IN41).
|
|
38
|
+
- Small parcel with the seller's own carrier: the SCP page and Hopted's copy of the FBA page tie payment to the tracking ID being on the shipment; Amazon's FBA texts read list tracking IDs among what to have ready and require a unique tracking code per box, without tying payment to it in words (IN5).
|
|
39
|
+
|
|
40
|
+
## Partnered carrier against the seller's own
|
|
41
|
+
|
|
42
|
+
- For a loss by an Amazon-partnered carrier, staff told a seller to file with Amazon under the Shipment to Amazon policy, with proof of ownership and proof of delivery (TaylorR_Amazon, US, 2024-11-29); that the seller cannot claim from the partnered carrier is a seller's statement and UPS's answer as a seller relayed it, on no Amazon page read (IN3).
|
|
43
|
+
- A carrier's proof of delivery shows that boxes arrived, not what was in them: a Seller Support email of 2023-08-07 declined a partnered-carrier loss on that ground, and the seller later relayed a refund in progress (IN4).
|
|
44
|
+
|
|
45
|
+
## Overages
|
|
46
|
+
|
|
47
|
+
- Overages are researched through the same Action required menu ("Extra units shipped"; shortages under "Units not shipped" or "Research missing units"), and no Amazon page read states that an overage offsets a shortage (IN19).
|
|
48
|
+
- The Contents tab and the v0 items list shipped against received per SKU, so an overage on one SKU and a shortage on another are separate lines (IN20).
|
|
49
|
+
- Practitioners count a shortfall two ways, side by side and theirs: per shipment and SKU (PrepVia, 2026-08-25; 优麦云, 2024-06-05), or across shipments, which sellers report fulfilment centres doing; no practitioner read recommends netting for a claim (IN20).
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# Reads: what the SP-API shows for a shipment or removal claim, and what it cannot do
|
|
2
|
+
|
|
3
|
+
## Inbound
|
|
4
|
+
|
|
5
|
+
- Shipped against received per SKU is `QuantityShipped` beside `QuantityReceived` in the v0 items list (Amazon Fulfillment) (IN20).
|
|
6
|
+
- No Fulfillment Inbound operation (v0 or 2024-03-20) returns a delivery, check-in, receiving or closed date, so the window's start cannot be read from the API (IN10).
|
|
7
|
+
- Its proxies are the first `Receipts` event in `GET_LEDGER_DETAIL_VIEW_DATA`, the selected delivery window or carrier appointment (`getShipment`, `listTransportationOptions`) and the carrier's tracking; the ledger proxy is read in Amazon's documents, not yet seen on a live account (IN10).
|
|
8
|
+
- Distributor-damaged and carrier-damaged arrivals are read as dispositions in `GET_LEDGER_DETAIL_VIEW_DATA` (Amazon Fulfillment); their spelling there is read in Amazon's documents, not yet seen on a live account (IN2).
|
|
9
|
+
- A small-parcel tracking ID is read at `getShipment` `trackingDetails.spdTrackingDetail` and written with `updateShipmentTrackingDetails` (IN5).
|
|
10
|
+
- In the 2024-03-20 model each SPD tracking ID carries `trackingNumberValidationStatus` (`VALIDATED`, `NOT_VALIDATED`, `NOT_SUPPORTED`, the last meaning Amazon cannot find tracking for it), and the model asks that a number not validated after a stated time be verified and updated (IN6).
|
|
11
|
+
- No operation exposes a shipment's research eligibility or eligibility date, the "Investigation completed" line, the reconciliation result, the claim window or Amazon's verified delivery date; these are Seller Central views under Shipping Queue, Contents or Reconcile (IN29).
|
|
12
|
+
- The payment for an inbound claim is read in `GET_FBA_REIMBURSEMENTS_DATA`, which answers to Pricing or Amazon Fulfillment (IN21, SU3).
|
|
13
|
+
|
|
14
|
+
## Removals and disposals
|
|
15
|
+
|
|
16
|
+
- Removal Order Detail is order by SKU by disposition, with requested, cancelled, disposed, shipped and in-process quantities and the fee; Removal Shipment Detail is shipment by SKU, with carrier and tracking; both need Pricing or Amazon Fulfillment and can only be requested (RM20, SU3).
|
|
17
|
+
- Amazon's FBA Reports page gives no value sets for `order-type`, `order-status`, `order-source` or `disposition`; practitioners (GorillaROI; SellerSpace; InventoryLab) report Return, Disposal and Liquidations (also Donation), Pending, Completed and Cancelled (spelling varies), and Sellable and Unsellable (RM21).
|
|
18
|
+
- Neither removal report has a store or marketplace column, and ERPs report that in NA and EU unified accounts they cannot tell which store a removal belongs to (Lingxing; SellerSpace) (RM22).
|
|
19
|
+
- Removal Shipment Detail carries no shipment-id column and no delivery date; read in Amazon's documents, not yet seen on a live account (RM15).
|
|
20
|
+
- The ledger detail's `VendorReturns` event type is where removals post, by the research's reading of the FBA Reports page; read in Amazon's documents, not yet seen on a live account (RM32).
|
|
21
|
+
- `listTransactions` links removal lines by the related identifier `REMOVAL_SHIPMENT_ITEM_ID`; Finances v0 links them by `MerchantOrderId` (the removal order id) and `RemovalShipmentItemId` (RM30).
|
|
22
|
+
- Finances v0 `listFinancialEvents` names Finance and Accounting, Amazon Fulfillment in NA and FE, and AISP in the EU (SU5).
|
|
23
|
+
- Practitioners report removal reimbursements under the reasons `REMOVAL_ORDER_LOST` and `REMOVAL_ORDER_DAMAGED`; Amazon publishes no reason list (Synder; Lingxing) (RM31).
|
|
24
|
+
- Liquidation events and their join: references/disposals.md.
|
|
25
|
+
|
|
26
|
+
## What no operation does
|
|
27
|
+
|
|
28
|
+
- No operation opens an inbound or removal claim, requests inbound research, attaches evidence, cancels a removal order or contests a dangerous-goods classification; each is the seller's step in Seller Central (IN29, RM35, SU12).
|
|
29
|
+
- Reading a filed case is the Support API's (`listCases`, `getCase`, `listContacts`), on Selling Partner Support (Restricted), a role outside the five; it would open the status, dates, subject, contacts and attachments of the seller's cases, and nothing here is built on it (SU8, IN13).
|
|
30
|
+
- AWD inbound counts need Amazon Warehousing and Distribution, a role outside the five (IN27).
|
|
31
|
+
- AWD inbound and its claim rule: references/inbound-programs.md.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Removal claims: scope, windows, grading, evidence, value, shipments
|
|
2
|
+
|
|
3
|
+
## Scope and route
|
|
4
|
+
|
|
5
|
+
- A removal claim covers eligible units lost or damaged by Amazon, or by a carrier Amazon used, after they left an Amazon facility on the way to the seller's return address; it does not cover units returned because the seller broke a policy (EU redline 2024-08-20; Hopted copy of the US page) (RM1).
|
|
6
|
+
- Every removal claim is filed by hand: each Amazon automation post of 2024 says so, and nothing read to 2026-11-13 announces removal automation; the IDR portal (announced 2025-01-21 for the US store) excludes removals and warehouse disposals (RM2, FL5).
|
|
7
|
+
- Amazon's removal claim kinds are lost in transit; damaged in transit; damaged, different or incomplete units received; and grading disputes on customer returns (RM3).
|
|
8
|
+
- The Seller Central route is the "Resolve a removal order issue" tool (G9ZB3H4DP4H72U6R), keyed by removal order ID (Indy_Amazon, US, 2026-08-13) (RM4).
|
|
9
|
+
- A removal claim needs the ASIN to comply with FBA restrictions at claim time; a seller reports an accepted removal claim later refused because the ASIN was deactivated as prohibited (2025-05-24) (RM33).
|
|
10
|
+
- A seller reported a suspension after several removal-loss requests (2019); Amazon's conduct rule on premature or high-volume requests is in ../claim-filing/SKILL.md (RM34, FL11).
|
|
11
|
+
|
|
12
|
+
## Windows, store by store
|
|
13
|
+
|
|
14
|
+
- A lost-in-transit removal claim has both an earliest and a latest filing day, and the other kinds a latest day counted from delivery back; the lengths are per store and per date (RM6).
|
|
15
|
+
- US: the post of 2024-07-24 (81c3235d), in force from 2024-10-23, counts lost in transit from shipment creation and "all other removal claims" from delivery back; before it, the US help page counted the earliest day from the last confirmed movement and every claim from the removal date (Hopted copy; the same text struck in the EU redline of 2024-08-20) (RM6).
|
|
16
|
+
- US, again: Amazon's staff post of 2026-08-13 gives removals a length counted "of the shipment being delivered or lost" that matches the pre-2024 page, not any News post; Amazon's own texts disagree, and none read says which governs (RM10).
|
|
17
|
+
- Australia: the post of 2025-08-14, in force from 2025-10-15, changed every removal window, moved the grading anchor from delivery to the date of removal and added a re-evaluation window; no post with a US marketplace field carrying these was found (RM7).
|
|
18
|
+
- UAE: the post of 2024-08-06, in force from 2024-09-05, counts lost removals from the ship date where the US, Canada, UK and Sweden posts count from creation, and gives damaged, different or incomplete units a window of their own from delivery (RM8).
|
|
19
|
+
- Amazon's texts give three anchors for the earliest day of a lost-removal claim (creation, ship date, last confirmed carrier movement); that a claim filed before it is refused as too early is a practitioner's report (ReclaimHQ) (RM9).
|
|
20
|
+
- A News post's windows are read as the store its post object names; no removal-related post read names its store in its own text (RM5).
|
|
21
|
+
- Where today's value is read for the seller's store: *FBA inventory reimbursement policy: Removals claims* and the "Resolve a removal order issue" tool, which cx cannot read and the seller sees signed in, and the store's latest Seller Forums News post on claim windows, read by plain GET; which window and anchor the tool enforces is read in Amazon's documents, not yet seen on a live account (RM6, RM9).
|
|
22
|
+
- Practitioner pages of 2026 state two different window sets, neither citing a store: PrepVia, Mr Prime and ReclaimHQ against SellerSprite, Olifant and Marketplace Officer (RM37).
|
|
23
|
+
- Some Chinese guides render the help page's "no sooner than" earliest day as a latest day (百运网, 2025-04-05) (RM36).
|
|
24
|
+
|
|
25
|
+
## Grading disputes
|
|
26
|
+
|
|
27
|
+
- A grading dispute concerns customer returns Amazon graded customer-damaged or defective; it needs the unit physically returned through a removal order and adds an explanation of the disagreement to the claim (EU redline 2024-08-20) (RM11).
|
|
28
|
+
- Its length and anchor (delivery of the removal back, or the date of removal from the network) are per store and per date; for the US the older page text counts from delivery and the post in force from 2024-10-23 takes grading in under "all other removal claims" only by inference, and the live US page is unread by a permitted route (RM12).
|
|
29
|
+
- Because a grading dispute needs the unit returned, a disposed unit cannot be its subject, and an automated or required disposal can remove that path before the seller acts; this is the research's inference from Amazon's text (RM13).
|
|
30
|
+
- Grading on customer returns themselves: ../return-claims/SKILL.md.
|
|
31
|
+
|
|
32
|
+
## Evidence
|
|
33
|
+
|
|
34
|
+
- Amazon's list for a removal claim: removal order ID; shipment ID with active tracking or proof of delivery; ASINs or FNSKUs and quantities; LPN; images of the units, their packaging, the shipping box and the shipping label; and, for grading, an explanation (EU redline 2024-08-20; the US copy lacks the label image) (RM14).
|
|
35
|
+
- Removal Shipment Detail has no shipment-id column and no delivery date, so the shipment ID the claim asks for is in no SP-API report read; read in Amazon's documents, not yet seen on a live account (RM15).
|
|
36
|
+
- Mr Prime (2026-10-01) notes that photos of the box, label and units can be taken only when the parcel is opened, and a seller thread (2026-06-25) reports Seller Support asking for per-unit unboxed photos with LPN stickers; both are practitioners' reports (RM16).
|
|
37
|
+
- Chinese practitioners treat a continuous unboxing video as the core evidence; no Amazon text read names video (RM17).
|
|
38
|
+
|
|
39
|
+
## Value
|
|
40
|
+
|
|
41
|
+
- Removal claims before a customer order are valued at sourcing cost, and units unsellable when removed at "a reduced estimated cost"; the redlines strike the earlier "estimated proceeds" sentence for removal claims in the US, UK, Japan and Canada (Chinese) texts; the US 2024-12-18 and UK 2024-12-11 texts name "manufacturing cost", the US 2025-02-24 and JP texts "sourcing cost" (RM18).
|
|
42
|
+
- The JP English redline (2025-02-19) names sourcing cost for removal claims, *Manage Your Sourcing cost* on the IDR portal and a periodic refresh of estimates after 2025-04-01; the store is read from its currency, "consumption tax" and its path (RM46).
|
|
43
|
+
- The valuation rule, the cap and the dispute: ../claim-value/SKILL.md.
|
|
44
|
+
|
|
45
|
+
## Lost, short, wrong and damaged removal shipments
|
|
46
|
+
|
|
47
|
+
- A removal order can ship as many parcels from several fulfilment centres over weeks (US staff; PrepVia, 2026-08-25); Amazon gives no fixed processing time, and one order's actual span is read from its own `request-date`, `shipment-date` and `last-updated-date` in Removal Order Detail (RM23).
|
|
48
|
+
- A removal order can show "Completed" and charged while some of its tracking numbers never moved (a seller thread, 2025-06-13) (RM24).
|
|
49
|
+
- Removal Shipment Detail omits cancelled and disposed units, which Removal Order Detail carries per order, SKU and disposition (RM20).
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: warehouse-claims
|
|
3
|
+
description: "Inventory Amazon lost or damaged after receiving it: warehouse lost and damaged units (Lost_Warehouse, Damaged_Warehouse), units lost in transfers between centres, Pan-European FBA, EFN and Remote Fulfillment, at AWD, in an MCF order, and Vine units; whether Amazon pays warehouse losses without a claim in the seller's store, as each store's News post announced it, and the UK staff post that contradicts the UK posts; how each store sets the lost-or-damaged window and where it is read; what the IDR portal covers; the Inventory Ledger's misplaced, damaged, found and correction codes, the Transaction Item ID, researchingQuantity and found units netted against lost ones; and the exclusions. For any question about units Amazon misplaced, lost or damaged in its warehouses, whether Amazon already paid for them, why a ledger row shows lost, found or researching, or whether a warehouse loss can still be claimed."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
## What counts
|
|
7
|
+
|
|
8
|
+
Eligible units lost or damaged by an Amazon centre, or a facility run for Amazon, after receipt, reported in the Inventory Ledger, in Amazon's older policy text, via a third-party mirror (FC1).
|
|
9
|
+
|
|
10
|
+
## Paid without a claim
|
|
11
|
+
|
|
12
|
+
Amazon announced proactive reimbursement of FC-lost units store by store: the US and Canada from 2024-11-01, the UK from 2025-01-15; no such post was found for other stores (FC3, FC4).
|
|
13
|
+
A post's store is the `marketplaceId` in its own post object, not the forum host; checked on four posts, the field is not documented by Amazon (FC45).
|
|
14
|
+
A UK staff post of 2026-04-06 says UK warehouse-lost units currently need a manual claim, automatic reimbursement disabled since 2022-08, against Amazon's UK News posts; neither is picked (FC5).
|
|
15
|
+
|
|
16
|
+
## The window
|
|
17
|
+
|
|
18
|
+
Set per store, changed by announcement, counted from Amazon's report of the event, as read on 2026-11-13 (FC9, FC10).
|
|
19
|
+
cx reads it from the latest News post on claim windows whose `marketplaceId` is the store, by plain GET; the seller sees *FBA inventory reimbursement policy* signed in; no SP-API operation returns it (FC9).
|
|
20
|
+
|
|
21
|
+
## The IDR portal
|
|
22
|
+
|
|
23
|
+
Announced for the US store on 2025-01-21; covers warehouse lost, warehouse damage and customer returns, not missing-from-inbound, removals or warehouse disposals; no SP-API operation returns its lists, and using it is the seller's step in Seller Central (FL5, FC13, FC14, SU12).
|
|
24
|
+
|
|
25
|
+
## The ledger
|
|
26
|
+
|
|
27
|
+
In third-party reproductions of Amazon's ledger help, loss is M or 5; centre damage is 6, 7, E, H, K or U, each followed by P; N and O also move units because of a reimbursement (FC22).
|
|
28
|
+
The ledger's grammar: @comchatx/cx-amazon-stock-playbook, its stock-position skill.
|
|
29
|
+
|
|
30
|
+
## Beside this skill
|
|
31
|
+
|
|
32
|
+
Opening, evidencing and answering a case are the seller's steps in Seller Central (SU12).
|
|
33
|
+
Routes and evidence: ../claim-filing/SKILL.md.
|
|
34
|
+
Value, cap, sourcing cost, reversals: ../claim-value/SKILL.md.
|
|
35
|
+
Inbound, AWD-to-FBA shortfalls and removals: ../shipment-claims/SKILL.md.
|
|
36
|
+
Returns and outbound losses: ../return-claims/SKILL.md.
|
|
37
|
+
Fees: ../fee-claims/SKILL.md.
|
|
38
|
+
How a call is made and a report is asked for and landed: the amazon-sp-api skill's references/door.md.
|
|
39
|
+
|
|
40
|
+
## References
|
|
41
|
+
|
|
42
|
+
[paid-without-claim.md](references/paid-without-claim.md): automation by store, posts, UK contradiction, choices.
|
|
43
|
+
[windows-and-idr.md](references/windows-and-idr.md): the window, where it is read, the IDR portal.
|
|
44
|
+
[ledger.md](references/ledger.md): codes, Transaction Item ID, researching, netting, pitfalls.
|
|
45
|
+
[scope.md](references/scope.md): transfers, AWD, cross-border, MCF, Vine, exclusions.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# The ledger, found against lost, and what the API carries
|
|
2
|
+
|
|
3
|
+
The ledger's grammar (event types, reason codes, reconciled and unreconciled quantity): @comchatx/cx-amazon-stock-playbook, its stock-position skill.
|
|
4
|
+
How a call is made and a report is asked for and landed: the amazon-sp-api skill's references/door.md.
|
|
5
|
+
|
|
6
|
+
## The codes this skill reads
|
|
7
|
+
|
|
8
|
+
- Lost is M or 5, misplaced (FC22).
|
|
9
|
+
- Damage at a centre is 6, 7, E, H, K or U, each followed by a P row (FC22).
|
|
10
|
+
- Found is F and N; O is a correction; D is disposed (FC22).
|
|
11
|
+
- N and O also move units because of a reimbursement, so a net that counts N as a find can count a reimbursement as a recovered unit (FC25, VR40).
|
|
12
|
+
- The code table is Openbridge's and Reason Automation's reproduction of Amazon's ledger help (FC22).
|
|
13
|
+
- Whether a store's file carries codes outside that table is read in Amazon's documents, not yet seen on a live account (FC22).
|
|
14
|
+
- For a reimbursed unit, whether an N or O row appears, and on what date against the report's `approval-date`, is read in Amazon's documents, not yet seen on a live account (FC25).
|
|
15
|
+
|
|
16
|
+
## Transaction Item ID
|
|
17
|
+
|
|
18
|
+
- Amazon locates the Transaction Item ID in the Inventory Ledger, and a practitioner pastes the ledger's `Reference ID` into "Check warehouse damaged reimbursement status", so an adjustment row's `Reference ID` serves as the Transaction Item ID by practitioner use (FC17).
|
|
19
|
+
- Whether that tool accepts the ledger's `Reference ID` is read in Amazon's documents, not yet seen on a live account (FC17).
|
|
20
|
+
|
|
21
|
+
## Researching
|
|
22
|
+
|
|
23
|
+
- `getInventorySummaries` returns `researchingQuantity`, "the misplaced or warehouse damaged units that are actively being confirmed at our fulfillment centers"; it is the only SP-API field that names misplaced units (FC30).
|
|
24
|
+
- How its age buckets line up with the M rows, and when a unit leaves researching, is read in Amazon's documents, not yet seen on a live account (FC30).
|
|
25
|
+
|
|
26
|
+
## Amazon's own checks
|
|
27
|
+
|
|
28
|
+
- Amazon's older policy text, as a third-party mirror shows it, names three pre-claim checks: Manage FBA Inventory shows the unit was not found or restored; the Inventory Ledger gives the date and adjustment code; the Reimbursements report, "by FNSKU and date", shows it was not already reimbursed (FC20).
|
|
29
|
+
- A practitioner (My Amazon Guy, 2025-10-31) relays seller reports of found units coming back months after a reimbursement, the reimbursement reversed and the units sometimes expired and charged for removal or disposal (FC28).
|
|
30
|
+
- One practitioner reports reversals of part of one account's 2023 reimbursements (FC29).
|
|
31
|
+
- How a reversal is read: ../claim-value/SKILL.md.
|
|
32
|
+
|
|
33
|
+
## Practitioners' ways, side by side (theirs, none picked)
|
|
34
|
+
|
|
35
|
+
- Selecting open losses: Spaghetti filters the ledger detail's Adjustments on M and 5 with an unreconciled quantity of at least one; 知无不言 drops blank and zero unreconciled rows of the older reconciliation report and reads the M rows; Seller Labs flags negative rows with the misplaced, damaged and disposed reasons (FC23).
|
|
36
|
+
- Netting: per pair of rows, M then F nets to zero (ZonGuru); per FNSKU, E and M against F and N, a negative difference read as missing stock (连连) (FC24).
|
|
37
|
+
- Matching a loss to a payment: Seller Labs matches by FNSKU and date range, not FNSKU alone, because no identifier links a ledger adjustment to a Reimbursements report row (FC27).
|
|
38
|
+
|
|
39
|
+
## Pitfalls of the data
|
|
40
|
+
|
|
41
|
+
- N and O can stand for a reimbursement, not a find (FC25).
|
|
42
|
+
- A found unit can appear at another centre, on another date, or under another FNSKU through codes 3 and 4; a net on the summary view by country hides this, while the detail view carries each row's `Fulfillment Center` (FC26).
|
|
43
|
+
|
|
44
|
+
## What the SP-API carries
|
|
45
|
+
|
|
46
|
+
- Finances v0 describes `FBAInventoryReimbursement` as occurring "if a seller's inventory is damaged"; `LostOrDamagedReimbursement` is an Easy Ship type, not FBA (FC31).
|
|
47
|
+
- The AWD API model, the Data Kiosk schemas and the notification schemas carry no field for lost, damaged or reimbursed units (FC32).
|
|
48
|
+
- No notification type announces a reimbursement or a ledger adjustment (SU31).
|
|
49
|
+
- The ledger names Amazon Fulfillment as its only role; the Reimbursements report answers to Pricing or Amazon Fulfillment (SU2, SU3).
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
# Paid without a claim, store by store
|
|
2
|
+
|
|
3
|
+
## Amazon's announcements
|
|
4
|
+
|
|
5
|
+
- Amazon's US News post of 2024-07-24 says it will "proactively reimburse you for … items that are lost in our fulfillment centers … as soon as an item is reported as lost" (FC3).
|
|
6
|
+
- The same post says "almost all" warehouse-lost, warehouse-damaged and customer-return cases "will now be proactively reimbursed", a manual claim remains for any unit not reimbursed, and all removal claims stay manual (FC3).
|
|
7
|
+
- The Canada post of the same day is the same text with its own customer-return window; the finance pack cites the Canada post, not the US one (FC41).
|
|
8
|
+
- The UK News post of 2024-10-10 announced the UK start of 2025-01-15 (FC4).
|
|
9
|
+
- The US, UK and Canada valuation posts of 2024-12-18 each restate "We now offer automatic reimbursements for items lost in our fulfil(l)ment cent(re|er)s" (FC4).
|
|
10
|
+
- The Sweden, Saudi Arabia, Egypt, UAE and Australia posts change windows only (FC4, FC11, FC42).
|
|
11
|
+
- No automation post was found, by a search of forums and media, for DE, FR, IT, ES, NL, PL, BE, IE, SE, JP, AU, IN, MX, BR, AE, SA, EG, TR or SG; a Chinese practitioner (AMZ123) assigns the 2025 date to Europe, and the post's own store field narrows it to the UK (FC4).
|
|
12
|
+
- Whether automatic `Lost_Warehouse` rows arrive in a store with no automation post is read in Amazon's documents, not yet seen on a live account (FC4).
|
|
13
|
+
|
|
14
|
+
## The UK contradiction
|
|
15
|
+
|
|
16
|
+
- A UK staff post (Jameson_Amazon, 2026-04-06) says UK warehouse-lost inventory "Currently requires manual claim submission", automatic reimbursement disabled since 2022-08, with a window counted from "the event" (FC5).
|
|
17
|
+
- The same post says warehouse damage to sellable units is reimbursed automatically within a period it states, and damage whose source disposition was customer damaged, inbound carrier damaged, expired or distributor damaged is "Eligible for manual claims" (FC19).
|
|
18
|
+
- Amazon's UK News posts state automatic lost reimbursement (2024-10-10 with a start date; 2024-12-18, "We now offer") and a shorter manual window (2024-10-10; 2025-01-15) (FC5).
|
|
19
|
+
- Both are Amazon's statements for the UK store; neither is picked (FC5, EC27).
|
|
20
|
+
- On value, the same staff post describes "estimated proceeds - your item's value minus applicable fees", while the UK News posts of 2024-12-18 and 2025-02-28 and the UK policy PDF of 2025-02-24 move pre-order losses to sourcing cost (FC35, VR2).
|
|
21
|
+
- A seller in that thread reports an "Amazon estimated" value below the manufacturer's own selling price, the invoice figure not given (FC35).
|
|
22
|
+
- Whether UK `Lost_Warehouse` rows arrive with a blank `case-id` after 2025-01-15 or only on a case is read in Amazon's documents, not yet seen on a live account (FC5, EC27).
|
|
23
|
+
|
|
24
|
+
## Where cx reads it for the seller's store
|
|
25
|
+
|
|
26
|
+
- What Amazon paid in a store is read in `GET_FBA_REIMBURSEMENTS_DATA` (Pricing or Amazon Fulfillment): whether `Lost_Warehouse` and `Damaged_Warehouse` rows with a blank `case-id` arrive after the store's automation date, against the ledger's lost and damaged adjustments in `GET_LEDGER_DETAIL_VIEW_DATA` (Amazon Fulfillment) (EC27, SU2, SU3).
|
|
27
|
+
- That a blank `case-id` means Amazon paid unasked is a reading, not Amazon's statement; it is read in Amazon's documents, not yet seen on a live account (EC27).
|
|
28
|
+
- The store's announcement is its latest Seller Forums News post on reimbursement whose `marketplaceId` is that store, read by plain GET (FC4, FC45).
|
|
29
|
+
|
|
30
|
+
## How a post's store is read
|
|
31
|
+
|
|
32
|
+
- A thread opens on every forum host; `selectedMarketplaceId` follows the host, while the `marketplaceId` in the post object stays the same on every host (FC45).
|
|
33
|
+
- On four posts whose store is fixed by their own words, the field named that store; Amazon documents neither the field nor its meaning (FC45).
|
|
34
|
+
- One News text is issued as a separate thread per store, and the copies differ in their values, so a value read in one thread is that store's only (FC46).
|
|
35
|
+
- On a seller's post the field is the store the seller posted under, which can differ from the store the post discusses (FC47).
|
|
36
|
+
|
|
37
|
+
## The posts, by store
|
|
38
|
+
|
|
39
|
+
- 81c3235d, 2024-07-24, US: the automation start and the windows from 2024-10-23 (FC3, FC41).
|
|
40
|
+
- 6605eede, 2024-07-24, Canada: the same text with its own customer-return window (FC41, FC46).
|
|
41
|
+
- c6da88ce, e62a8ace, 96a05f4a, 2024-08-06, Saudi Arabia, Egypt, UAE: the window set effective 2024-09-05 (FC11).
|
|
42
|
+
- d0fc997e, 2024-10-10, UK: automation from 2025-01-15; windows from 2025-01-09 (FC4, FC9).
|
|
43
|
+
- 2de1ef2f, 2024-10-16, US: a seller relaying Amazon's text on the window change of 2024-10-23 (FC7).
|
|
44
|
+
- 68864b6f, a941ac02, da761b17, 2024-12-18, US, UK, Canada: "We now offer automatic reimbursements" (FC4).
|
|
45
|
+
- 1101821c and 9a92846d, 2025-01-15, Sweden and UK: windows only (FC5, FC9).
|
|
46
|
+
- b175b700, 2025-01-21, US: the IDR portal launch (FC13).
|
|
47
|
+
- 0252e05d, 2025-02-28, UK: the postponed move of pre-order losses to sourcing cost for the UK (FC35).
|
|
48
|
+
- d8f9a56c, Australia: the claim-windows post effective 2025-10-15 (FC42).
|
|
49
|
+
- 2f44617d, 2026-04-06, UK staff: lost units manual, sellable damage automatic (FC5, FC19).
|
|
50
|
+
- 0e07abc1, 2026-08-13, US staff: scope, the window's start, replenishment at sourcing cost (FC2, FC10).
|
|
51
|
+
- 5b46fd45, 2021-04-07, UK, a seller quoting Amazon: the researching text (FC6).
|
|
52
|
+
- c0d6d3da, a seller's post with the UK field, about Pan-EU sales in Italy, Spain and France (FC47).
|
|
53
|
+
|
|
54
|
+
## History
|
|
55
|
+
|
|
56
|
+
- Amazon's 2021 text, as a seller quoted it, says that for adjustments after 2021-03-19 Amazon handles the researching duration, so sellers need not wait it out to file (FC6).
|
|
57
|
+
- A Chinese practitioner (雨果网, 2019-06-12) reports rows showing "Damaged at Amazon" with "Transfer to holding" as already reimbursed (FC43).
|
|
58
|
+
- Amazon's Chinese FBA FAQ says warehouse-damaged units cannot be removed and are reimbursed automatically and written off (FC44).
|
|
59
|
+
|
|
60
|
+
## The seller's choices (stated, none picked)
|
|
61
|
+
|
|
62
|
+
- Waiting for an automatic payment relies on Amazon's stated automation (FC3).
|
|
63
|
+
- Filing as soon as an event appears: Amazon's conduct paragraph names "insufficiently researched or premature requests" among activity that may bring delayed support, monitoring or account action, and the US moderator put claims at one per shipment or event in 2026 (FL7, FL11).
|
|
64
|
+
- The window runs from Amazon's report of the event in either case (FC10).
|
|
65
|
+
- For a UK store, the staff post's lost window and the News posts' window are each Amazon's statement; the store's policy page, which cx cannot read and the seller sees signed in, shows the store's window (FC5, FC9).
|
|
66
|
+
- The value of pre-order losses and the sourcing cost: ../claim-value/SKILL.md.
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
# What counts, and where the edges are
|
|
2
|
+
|
|
3
|
+
## What counts
|
|
4
|
+
|
|
5
|
+
- Amazon's older policy text, as a third-party mirror shows it, covers eligible units "lost or damaged by an Amazon fulfillment center or a facility operated on behalf of Amazon, after Amazon receives them from you", reported "in your Inventory Ledger report" (FC1).
|
|
6
|
+
- Amazon's US and UK policy PDFs of 2025-02-24 carry the general clause: an item "lost or damaged at a facility or by a carrier operated by Amazon or on behalf of Amazon" is replaced with a new item of the same FNSKU or reimbursed (FC1).
|
|
7
|
+
- US staff (2026-08-13) and the US and UK PDFs put "lost and damage claims during inventory replenishment handled by Amazon or on behalf of Amazon" at sourcing cost (FC2, VR4).
|
|
8
|
+
- The evidence Amazon names is the date or location of the loss (for example the FC ID), the Transaction Item ID or FNSKU, and proof of ownership; for a unit unsellable when lost, Amazon "may request additional information or documentation" to set a reduced value (FC18).
|
|
9
|
+
- Routes and evidence by kind: ../claim-filing/SKILL.md.
|
|
10
|
+
|
|
11
|
+
## Transfers between centres
|
|
12
|
+
|
|
13
|
+
- A unit lost in a transfer between centres has no claim type of its own in Amazon's pages read; by the research's reading, not Amazon's statement, the ledger shows it as an adjustment, with units in transit kept in "In Transit Between Warehouses" (FC36).
|
|
14
|
+
|
|
15
|
+
## AWD and AWD to FBA
|
|
16
|
+
|
|
17
|
+
- Amazon's AWD service terms (dated 2026-01-14) replace or reimburse units lost or damaged at an AWD facility or by an Amazon-operated carrier; the facility window starts "on the date that the Unit was identified by Amazon as lost or damaged", and valuation follows the MCF reimbursement methodology (FC37).
|
|
18
|
+
- The MCF policy the AWD terms name is the Supply Chain Portal reimbursements page, so an AWD claim's window, cap and valuation are read there by plain GET (IN26, IN34).
|
|
19
|
+
- Amazon's AWD help text, as a seller quoted it on 2024-09-17, promises "fair value" reimbursement when AWD finds fewer boxes than received "during facility audit or replenishment of boxes to the FBA network", on a case to Selling Partner Support (FC38).
|
|
20
|
+
- Sellers' threads (2025) describe AWD-to-FBA replenishment shipments as carrying FBA shipment ids and replenishment order ids, with their shortfalls pursued as inbound shortfalls, and report Amazon asking for carrier tracking they cannot hold (FC39).
|
|
21
|
+
- Whether AWD-to-FBA shortfalls appear as negative receipts or as adjustments, and under which reimbursement `reason`, is read in Amazon's documents, not yet seen on a live account (FC39).
|
|
22
|
+
- Inbound shortfalls: ../shipment-claims/SKILL.md.
|
|
23
|
+
|
|
24
|
+
## Cross-border: Pan-European FBA, UK–EU and EFN
|
|
25
|
+
|
|
26
|
+
- No Amazon page read names a claim type, window, route or reimbursing store for a unit lost while Amazon moves it across borders, or for EFN stock (FC48).
|
|
27
|
+
- By the research's reading, the ledger records such a loss as an adjustment at a centre, with `Country` and `Store` on each row and the move as `WhseTransfers`, and Amazon's AU agreement (2024-06-12) lets it "move Units among facilities" and reimburses loss "while they are being stored" under the FBA Guidelines (FC48).
|
|
28
|
+
- A reimbursement's store and currency are read from the Reimbursements report's `currency-unit`, Finances v0 `AdjustmentEvent.StoreName` and `AdjustmentAmount.CurrencyCode`, and Finances v2024-06-19 `marketplaceDetails.marketplaceId`; no Amazon page read states the rule (FC49).
|
|
29
|
+
- The Reimbursements report has no store or marketplace column; the ledger detail carries `Country` and `Store` (SU52).
|
|
30
|
+
- A developer reports the Reimbursements report returning the same rows whatever `marketplaceIds` names within a region (SU24).
|
|
31
|
+
- One ERP tells sellers to file in the Seller Central of the store where the event happened; no Amazon page read states this (FL40).
|
|
32
|
+
- In which store, report and currency a cross-border loss posts is read in Amazon's documents, not yet seen on a live account (FC48, FC49).
|
|
33
|
+
|
|
34
|
+
## NA Remote Fulfillment
|
|
35
|
+
|
|
36
|
+
- Under Remote Fulfillment the units stay in US centres while offers sell on Amazon.ca, Amazon.com.mx and Amazon.com.br; no page read states the store or currency of a reimbursement for such a unit (FC50).
|
|
37
|
+
- Whether such a reimbursement posts in a currency other than the US dollar is read in Amazon's documents, not yet seen on a live account (FC50).
|
|
38
|
+
|
|
39
|
+
## MCF orders
|
|
40
|
+
|
|
41
|
+
- An MCF order lost or damaged on the way to the buyer is claimed under Amazon's MCF terms, not as an FC-operations claim (FC51).
|
|
42
|
+
- Amazon's MCF pages exclude orders "marked as delivered by the carrier" and MCF fees, and the India page excludes MCF used to fulfil Amazon orders or to remove stock (FC51).
|
|
43
|
+
- Their window, value basis and cap are their own, read by plain GET on the Supply Chain Portal reimbursements page and on Amazon India's *Reimbursements for your MCF orders* (FC51).
|
|
44
|
+
- Losses on the way to an Amazon buyer: ../return-claims/SKILL.md.
|
|
45
|
+
|
|
46
|
+
## Vine units
|
|
47
|
+
|
|
48
|
+
- Vine units are FBA inventory ("FBA inventory must be sent to Amazon fulfillment centers for products to be shipped to Vine Voices"), and no Amazon page read addresses one lost or damaged before it reaches the Vine Voice (FC52).
|
|
49
|
+
- How Vine shipments appear in the ledger, and whether a unit lost on its way to a reviewer gets a `Lost_Outbound` row, is read in Amazon's documents, not yet seen on a live account (FC52).
|
|
50
|
+
|
|
51
|
+
## Exclusions
|
|
52
|
+
|
|
53
|
+
- Amazon's eligibility list in the US and UK policy PDFs of 2025-02-24 excludes units pending disposal or disposed of, defective or customer-damaged units, units outside FBA product restrictions, and, in the US, units on cancelled or deleted shipments; it names no exclusion for expiry, recall or force majeure (FC54).
|
|
54
|
+
- On expired stock damaged at a centre, the UK staff post of 2026-04-06 lists it as "Eligible for manual claims" (FC54, FC19).
|
|
55
|
+
- Amazon's AU agreement (2024-06-12) disclaims liability for failure to perform "by reasons, events or other matters beyond our reasonable control" and makes the seller responsible for recall costs; no reimbursement page or post read applies either to a unit lost in a centre; the US agreement's clauses were not re-read (FC55).
|
|
56
|
+
- A seller enrolled in FBA Damaged Inventory Ownership keeps its enrolled Amazon-fault damaged units in its unfulfillable stock, and they "will not be eligible for damage reimbursements"; the enrolment is on a page cx cannot read, which the seller sees signed in, and no SP-API read shows it (RT11).
|
|
57
|
+
- Whether the store's policy page names expiry, recall or force majeure among its exclusions is read in Amazon's documents, not yet seen on a live account (FC54).
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# The FC window and the IDR portal
|
|
2
|
+
|
|
3
|
+
## The window's rule
|
|
4
|
+
|
|
5
|
+
- Before the 2024 change, Amazon's policy text, as a third-party mirror shows it, counted the FC window from "the date the item was reported lost or damaged in your Inventory Ledger report" (FC7).
|
|
6
|
+
- A seller on the US store relays Amazon's text that from 2024-10-23 the eligibility windows, except for shipment-to-Amazon claims, were shortened (FC7).
|
|
7
|
+
- Chinese practitioners give a pre-2024 length that no Amazon text read supports (FC8).
|
|
8
|
+
- The window is set per store and changed by announcement; posts read carry windows for the US, Canada, the UK, Sweden, Saudi Arabia, Egypt, the UAE and Australia, and none was found for DE, FR, IT, ES, NL, PL, BE, IE, JP, IN, MX, BR, TR or SG; read 2026-11-13 (FC9).
|
|
9
|
+
- It counts from Amazon's report of the event, not the seller's discovery: "after the item was reported lost or damaged" (US, Canada and UK News), "the date the loss or damage event appears in your reports" (US staff, 2026-08-13), "the date the unit is marked as … 'Misplaced'" (Saudi Arabia) (FC10).
|
|
10
|
+
- The Saudi Arabia, Egypt and UAE window set, effective 2024-09-05, counts calendar days from the "Inventory Adjustment report" and was issued for those three stores, not for the US, the UK or the EU; only the Egypt copy lists carrier-damaged returns and lost customer returns, and the set links a summary page, unread, that cx cannot read (FC11).
|
|
11
|
+
- The UK staff post of 2026-04-06 counts the lost window from "the event" and says damaged claims are "Available immediately after the damage event is visible", with no end stated, against the UK News posts (FC5, FC9).
|
|
12
|
+
|
|
13
|
+
## Where cx reads a store's window
|
|
14
|
+
|
|
15
|
+
- The store's latest Seller Forums News post on claim windows, the one whose `marketplaceId` is that store, by plain GET (FC9).
|
|
16
|
+
- *FBA inventory reimbursement policy* as the store shows it, a page cx cannot read, which the seller sees signed in (FC9).
|
|
17
|
+
- No SP-API operation returns a window (FC9).
|
|
18
|
+
- Which window the store's policy page shows today, and whether Contact Us refuses a lost-unit claim outside it, is read in Amazon's documents, not yet seen on a live account (FC9).
|
|
19
|
+
|
|
20
|
+
## Pitfalls of the sources
|
|
21
|
+
|
|
22
|
+
- The US staff post of 2026-08-13 sends sellers to "Reports > Fulfillment > Inventory Adjustments", and the Middle East posts and the Supply Chain Portal policy count from the "Inventory Adjustment report", which Amazon retired on 2023-01-31 for the Inventory Ledger (FC12).
|
|
23
|
+
- The Supply Chain Portal reimbursements policy is a different programme from Seller Central FBA, for an active MCF account; its window, cap and fallback values are its own, read on that page by plain GET (FC40, FL27).
|
|
24
|
+
|
|
25
|
+
## The ledger's reach
|
|
26
|
+
|
|
27
|
+
- The ledger detail's look-back is stated on Amazon's *FBA Reports* page; no Amazon page read says what becomes of a loss row still unreconciled past it (FC53, SU15).
|
|
28
|
+
- A report's look-back and a claim's window are different facts (SU18).
|
|
29
|
+
- Whether an unreconciled M row persists to the edge of the ledger's reach, and is later reimbursed, found or dropped, is read in Amazon's documents, not yet seen on a live account (FC53).
|
|
30
|
+
|
|
31
|
+
## The IDR portal
|
|
32
|
+
|
|
33
|
+
- News_Amazon announced the Inventory Defect and Reimbursement portal on 2025-01-21 in a thread whose store is the US; no launch post for another store was found (FC13).
|
|
34
|
+
- Its scope is warehouse lost, warehouse damage and customer returns; it "doesn't include defects under missing from inbound, removals or warehouse disposals" (FL5).
|
|
35
|
+
- It is reached from the FBA dashboard's Inventory menu or from the Reimbursements report; its help page is one cx cannot read, which the seller sees signed in (FL5).
|
|
36
|
+
- Practitioners (eComEngine, My Amazon Guy) describe its pages as Overview, Eligible for Claim, In Progress, Resolved and Defect Status Trend, with resolutions Reimbursed, Reconcile and Ineligible, built from the ledger, the customer returns report and the policy (FC15).
|
|
37
|
+
- No operation or schema in Amazon's SP-API models returns its Eligible-for-Claim list, its statuses or its resolution reasons (FC14).
|
|
38
|
+
- Using the portal is the seller's step in Seller Central; no SP-API operation acts in it (SU12).
|
|
39
|
+
- Whether the portal exists outside the US, and whether its Eligible-for-Claim rows match candidates rebuilt from the ledger and the Reimbursements report, is read in Amazon's documents, not yet seen on a live account (FC13, FC14).
|