亚马逊盘库是什么 ？ ？？？？盘货缘故原由代码和盘库报告下载要领大揭秘！
盘库
盘库报告显示了针对库存属性更改、误放库存、已找到库存和所有权更正等问题而对您的库存举行盘货的历史纪录。。。。。。。
盘货类型和缘故原由代码
盘库按类型和缘故原由代码分类。。。。。。。类型显示了盘货是提高照旧降低您的库存水平。。。。。。。缘故原由代码形貌了举行的盘货。。。。。。。
盘库通常成对举行。。。。。。。例如，，，，，若是您的库存属性从“可售”更改为“已逾期”，，，，，则会对您的库存举行两项盘货：可售库存镌汰，，，，，逾期库存增添。。。。。。。示例如下：
| 日期 | 生意商品编号 | FNSKU | 卖家 SKU | 商品名称 | 库存属性 | 运营中心 | 缘故原由 | 数目 |
|---|---|---|---|---|---|---|---|---|
| 2019 年 3 月 24 日 | 13895071006 | X0000COYXD | 2Y-IQFY-RUQV | How Deep Lies the Shadow | 可售 | LEJ1 | 库存属性更改 | -1 |
| 2019 年 3 月 24 日 | 13895071060 | X0000COYXD | 2Y-IQFY-RUQV | How Deep Lies the Shadow | 已逾期 | LEJ1 | 库存属性更改 | 1 |
下表列出了所有盘库缘故原由代码及其类型。。。。。。。
| 代码 | 类型 | 缘故原由 | 界说 |
|---|---|---|---|
| 6 | - | 在亚马逊运营中心残损 | 因承运人导致的残损库存水平降低。。。。。。。之后总是会将 P 代码提高至库房残损库存水平。。。。。。。 |
| 7 | - | 在亚马逊运营中心残损 | 逾期库存水平降低。。。。。。。之后总是会将 P 代码提高至库房残损库存水平。。。。。。。 |
| E | - | 在亚马逊运营中心残损 | 可售库存水平降低。。。。。。。之后总是会将 P 代码提高至库房残损库存水平。。。。。。。 |
| H | - | 在亚马逊运营中心残损 | 因买家导致的残损库存水平降低。。。。。。。之后总是会将 P 代码提高至库房残损库存水平。。。。。。。 |
| K | - | 在亚马逊运营中心残损 | 您的缺陷库存水平降低。。。。。。。后面始终是库房残损库存水平的 P 代码提高。。。。。。。 |
| U | - | 在亚马逊运营中心残损 | 您的经销商残损库存水平降低。。。。。。。后面始终是库房残损库存水平的 P 代码提高。。。。。。。 |
| D | - | 弃置库存 | 库存水平降低，，，，，由于库存已被弃置 |
| F | + | 找到库存 | 库存水平提高，，，，，由于发明缺失库存 |
| N | + | 找到库存 | 库存水平提高，，，，，由于之前过失分派的库存已转移到您的账户或者由于您收到了亚马逊赔偿 |
| M | - | 误放库存 | 库存水平降低，，，，，由于库存从运营中心的货位中缺失 |
| 5 | - | 误放库存 | 库存水平降低，，，，，由于库存从运营中心的货位中缺失 |
| 3 | + | 商品重新界说移入 | 两个具有自力编码 (SKU) 的商品被确定为统一商品。。。。。。。一个 SKU 将从您的库存中移除，，，，，并添加（代码 3）为另一个 SKU。。。。。。。 |
| 4 | - | 商品重新界说移出 | 两个具有自力编码 (SKU) 的商品被确定为统一商品。。。。。。。一个 SKU 将从您的库存中移除，，，，，并添加（代码 3）为另一个 SKU。。。。。。。 |
| O | - | 库存更正 | 由于您的库存被过失吸收或者亚马逊已向您赔偿，，，，，商品从您的账户中移出 |
| P | + | 库存属性更改 | 从其他库存属性中移除后，，，，，特定库存属性的商品将添加到您的库存中。。。。。。。这始终遵照代码 6、7、E、H、K、U 或 Q 盘货。。。。。。。 |
| Q | - | 库存属性更改 | 具有特定库存属性的商品会从您的库存中移除，，，，，然后作为差别的库存属性添加回您的库存。。。。。。。后面始终是 P 代码盘货。。。。。。。 |
库存属性
库存属性代表一件或多件商品的物理状态。。。。。。。
| 库存属性 | 库存状态 | 界说 |
|---|---|---|
| 可售 | 可售 | 具有商品信息中所述外观和功效的库存 |
| 保存瑕疵 | 不可售 | 不具有商品信息中所述外观或功效且没有显着残损的库存，，，，，例如，，，，，召回的商品 |
| 因买家导致的残损 | 不可售 | 由买家造成残损的库存 |
| 因分销商导致的残损 | 不可售 | 在吸收时代由卖家、供应商或经销商造成残损的库存 |
| 在库房泛起残损 | 不可售 | 在亚马逊运营中心泛起残损的库存 |
| 因承运人导致的残损 | 不可售 | 在吸收时代、在运往买家的途中或因退货而发回亚马逊的途中由承运人造成残损的库存 |
| 已逾期 | 不可售 | 已凌驾日期/批次中所述有用期/保质期的库存 |
提醒： 可通过移除不可售库存节约用度。。。。。。。
怎样阅读报告：在线和下载要领
您可以在卖家平台在线审查库存盘货，，，，，或通过下载盘库报告举行审查。。。。。。。
建议使用【在线审查】要领，，，，，以便快速审查盘库和调解。。。。。。。当调解盘库时，，，，，将提供盘库报告中的调解盘货或赔偿报告中的赔偿生意的链接。。。。。。。
建议使用【下载】要领，，，，，以便大规模相识盘库的调解状态。。。。。。。
在在线视图中，，，，，您可以按【缘故原由组】筛选盘库，，，，，如下表所示。。。。。。。
按盘货代码列出的缘故原由组
| 代码 | 缘故原由组 |
|---|---|
| 6、7、E、H、K、U | 已残损 |
| D | 弃置库存 |
| F、N | 已找到 |
| 5、M | 丧失 |
| 3、4、O、P、Q | 其他 |
在线审查您的盘库报告：
点击盘库报告中的【在线审查】选项卡。。。。。。。
在【行动日期】下拉菜单中选择所需的日期规模，，，，，然后在【缘故原由组】下拉菜单中选择缘故原由组。。。。。。。若是您将【缘故原由组】字段留空，，，，，则报告将显示所有盘货缘故原由。。。。。。。
若是您想进一步筛选效果，，，，，可以添加【卖家 SKU】、【FNSKU】、【运营中心】 或这些选项的恣意组合。。。。。。。
点击【天生报告】按钮。。。。。。。
注重： 若是盘库凌驾 50 个，，，，，报告将天生多个页面。。。。。。。使用报告顶部和右下角的快速链接在页面之间导航。。。。。。。
以下示例展示了凭证所选缘故原由组【丧失】、日期规模【已往 365 天】以及 【FNSKU】 X001SL 天生的报告。。。。。。。点击报告的【缘故原由】列中的【误放库存】可翻开调解状态。。。。。。。
| 日期 | 生意商品编号 | FNSKU | 卖家 SKU | 商品名称 | 库存属性 | 运营中心 | 缘故原由 | 数目 |
|---|---|---|---|---|---|---|---|---|
| 2019 年 7 月 23 日 | 2108808 | X001SL | SLU_2PK | SLU_PHOTO_2PK | 可售 | LGB3 | ? 误放库存 | -16 |
| 找到库存 | 5 | |||||||
| 剩余的误放或已残损库存 | 11 |
点击调解状态（在人生就是博·(中国)尊龙AG旗舰厅示例中为【找到库存】）以审查调解事务。。。。。。。在本示例中（拜见下表），，，，，可看到五个【找到库存】盘货缘故原由的总数目为 5。。。。。。。
日期 生意商品编号 FNSKU 卖家 SKU 商品名称 库存属性 运营中心 缘故原由 数目 2019 年 7 月 23 日 2108808 X001SL SLU_2PK SLU_PHOTO_2PK 可售 JFK8 ?找到库存 1 2019 年 7 月 23 日 210190912 X001SL SLU_2PK SLU_PHOTO_2PK 可售 DCA1 ?找到库存 1 2019 年 7 月 23 日 2101901 X001SL SLU_2PK SLU_PHOTO_2PK 可售 PHX6 ?找到库存 1 2019 年 7 月 23 日 210188746 X001SL SLU_2PK SLU_PHOTO_2PK 可售 MGE7 ?找到库存 1 2019 年 7 月 23 日 21188081 X001SL SLU_2PK SLU_PHOTO_2PK 可售 MKE1 ?找到库存 1
注重： 关于 2019 年 11 月 15 日之后未调解的【剩余的误放或残损库存】，，，，，您可能有资格凭证亚马逊物流丧失和已残损库存赔偿政策获得赔偿。。。。。。。
下载您的盘库报告：
点击盘库报告中的【下载】选项卡。。。。。。。
在【行动日期】下拉菜单中选择所需的日期规模。。。。。。。
针对想要使用的名堂，，，，，点击【请求 .csv 下载】或【请求 .txt 下载】。。。。。。。天生报告通常需要 1 到 45 分钟。。。。。。。
一旦报告状态从【举行中】变为【下载】，，，，，请点击【下载】按钮。。。。。。。
将文件生涯至您的电脑。。。。。。。
在电子表格或数据库程序（如 Microsoft Excel 或 Microsoft Access）中翻开报告。。。。。。。
示例如下：
| 盘货日期 | 生意编号 | fnsku | SKU | 商品名称 | 运营中心 | 数目 | 缘故原由 | 库存属性 | 已调解 | 未调解 |
|---|---|---|---|---|---|---|---|---|---|---|
| 2019-07-23 | 2108808 | X001SL | SLU_2PK | SLU_PHOTO_2PK | LGB3 | -16 | M | 可售 | 5 | 11 |
关于具有【在亚马逊运营中心残损】、【误放库存】或【找到库存】缘故原由代码的已调解数目，，，，，您可以在在线视图中获取更多信息。。。。。。。
关于具有在 2019 年 11 月 15 日之后爆发的【在亚马逊运营中心残损】和【误放库存】缘故原由代码的未调解数目，，，，，您可能有资格凭证亚马逊物流丧失和已残损库存赔偿政策获得赔偿。。。。。。。
调解事务
【误放库存】、【找到库存】和【在亚马逊运营中心残损】的盘库将举行响应的调解。。。。。。。您可以在在线视图和可下载视图中审查这些调解情形。。。。。。。
在线
当调解盘库时，，，，，将提供盘库报告中的调解盘货或赔偿报告中的赔偿生意的链接。。。。。。。
可下载
您将能够看到【误放库存】、【找到库存】和【在亚马逊运营中心残损】的【已调解】和【未调解】数目列。。。。。。。例如，，，，，当盘库获得赔偿或调解后，，，，，您将看到未调解数目镌汰而调解数目增添。。。。。。。
以下是在线视图的示例：
| 日期 | 生意商品编号 | FNSKU | 卖家 SKU | 商品名称 | 库存属性 | 运营中心 | 缘故原由 | 数目 |
|---|---|---|---|---|---|---|---|---|
| 2019 年 7 月 23 日 | 2108808 | X001SL | SLU_2PK | SLU_PHOTO_2PK | 可售 | LGB3 | ? 误放库存 | -16 |
| 找到库存 | 5 | |||||||
| 剩余的误放或已残损库存 | 11 |
以下是下载视图的示例：
| 盘货日期 | 生意编号 | fnsku | sku | 商品名称 | 运营中心 | 数目 | 缘故原由 | 库存属性 | 已调解 | 未调解 |
|---|---|---|---|---|---|---|---|---|---|---|
| 2019-07-23 | 2108808 | X001SL | SLU_2PK | SLU_PHOTO_2PK | LGB3 | -16 | M | 可售 | 5 | 11 |
下表列出了所有可能的原始事务和调解事务组合。。。。。。。
| 盘库缘故原由 | 调解缘故原由（显示在下拉菜单中） | 界说 |
|---|---|---|
| 在亚马逊运营中心残损 | 经由检查并纠正了库存属性 | 经检查发明未在运营中心残损的库存 |
| 已赔偿 | 您已获得赔偿的库存 | |
| 剩余的误放或已残损库存 | 尚未调解的剩余库存 | |
| 误放库存 | 找到库存 | 找到误放库存 |
| 已赔偿 | 您已获得赔偿的库存 | |
| 误放的已残损库存 | 【在亚马逊运营中心残损】库存被误放。。。。。。。 注重： 调解将应用到【在亚马逊运营中心残损】库存。。。。。。。 | |
| 剩余的误放或已残损库存 | 尚未调解的剩余库存 | |
| 找到库存 | 已找到涣黪库存 | 凭证亚马逊物流丧失和已残损库存赔偿政策，，，，，为赔偿丧失或已残损库存而举行替换的库存。。。。。。。 |
| 找到缺失库存 | 已找到误放库存 | |
| 库存所有权更正 | 分派过失的已找到库存已移至准确所有者 |
注重： 除【误放库存】、【找到库存】和【在亚马逊运营中心残损】库存以外的盘库不会在在线视图或可下载视图中显示调解缘故原由。。。。。。。
为什么我的商品被视察 ？ ？？？？
您会在“治理库存”页面和报告中发明一个新的库存分类，，，，，称为【视察】。。。。。。。这体现亚马逊运营中心正在起劲确认是否保存误放库存或库房残损库存。。。。。。。时间线将显示视察一连时间，，，，，绝不会凌驾 30 天。。。。。。。当被视察的库存获得赔偿或凌驾 30 天的一连时间后，，，，，您将通过盘库报告看到响应的盘货转换。。。。。。。关于 2019 年 11 月 15 日之后举行的盘库，，，，，您无需在 30 天内提出索赔，，，，，由于我们正在这 30 天内为您一连视察。。。。。。。
字段界说
| 在线问题 | 下载问题 | 形貌 |
|---|---|---|
| 日期 | 盘货日期 | 年/月/日 |
| 生意商品编号 | 生意商品编号 | 此商品盘货的唯一编号 |
| FNSKU | fnsku | 亚马逊分派的唯一商品编号，，，，，由运营中心使用 |
| 卖家 SKU | SKU | 卖家分派的唯一商品编号 |
| 商品名称 | 商品名称 | 亚马逊上宣布的商品的名称 |
| 运营中心编号 | 运营中心编号 | 正在盘货的运营中心 |
| 数目 | 数目 | 已盘货商品的数目 |
| 缘故原由 | 缘故原由 | 下载的文件显示缘故原由代码，，，，，在线审查显示详细形貌。。。。。。。请参阅本页面顶部的【盘货类型和缘故原由代码】表，，，，，相识完整的代码和说明。。。。。。。 |
| 库存属性 | 库存属性 | 商品处于可售照旧不可售/无法配送的状态 |
| 不适用 | 已调解 | 已通过其他盘货事务调解的商品数目 |
| 不适用 | 未调解 | 未通过其他盘货事务举行调解的商品数目 |
亚马逊官网原文详情：
Inventory adjustments
The Inventory Adjustments report shows the history of adjustments to your inventory in response to issues such as disposition changes, misplaced inventory, found inventory, and ownership corrections.
Adjustment types and reason codes
Inventory adjustments are categorized by type and reason code. The type shows whether an adjustment is an increase or decrease to your inventory level. The reason code describes the adjustment made.
Inventory adjustments often occur in pairs. For example, if your inventory changes disposition from sellable to expired, there will be two adjustments to your inventory: a decrease in your sellable inventory and an increase in your expired inventory. Here is an example:
Date Transaction Item ID FNSKU Merchant SKU Title Disposition FC Reason Quantity March 24, 2019 13895071006 X0000COYXD 2Y-IQFY-RUQV How Deep Lies the Shadow Sellable LEJ1 Inventory disposition change -1 March 24, 2019 13895071060 X0000COYXD 2Y-IQFY-RUQV How Deep Lies the Shadow Expired LEJ1 Inventory disposition change 1
The following table lists all inventory adjustment reason codes and their type.
Code Type Reason Definition 6 - Damaged at Amazon fulfillment center A decrease to your carrier-damaged inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. 7 - Damaged at Amazon fulfillment center A decrease to your expired inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. E - Damaged at Amazon fulfillment center A decrease to your sellable inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. H - Damaged at Amazon fulfillment center A decrease to your customer-damaged inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. K - Damaged at Amazon fulfillment center A decrease to your defective inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. U - Damaged at Amazon fulfillment center A decrease to your distributor-damaged inventory level. It is always followed by a P code increase to your warehouse-damaged inventory level. D - Inventory disposed of A decrease to your inventory level because inventory has been disposed of F + Inventory found An increase to your inventory level because missing inventory has been found N + Inventory found An increase to your inventory level because previously incorrectly assigned inventory has been transferred to your account or because you received an Amazon reimbursement M - Inventory misplaced A decrease to your inventory level because inventory is missing from a bin location in a fulfillment center 5 - Inventory misplaced A decrease to your inventory level because inventory is missing from a bin location in a fulfillment center 3 + Product redefinition transfer in Two products with separate identifiers (SKUs) are determined to be the same item. One SKU will be removed from your inventory and added (code 3) as the other SKU. 4 - Product redefinition transfer out Two products with separate identifiers (SKUs) are determined to be the same item. One SKU will be removed from your inventory and added (code 3) as the other SKU. O - Inventory correction Units transferred out of your account because they were incorrectly received to your inventory or because Amazon has reimbursed you for them P + Inventory disposition change Units of a certain disposition are added to your inventory after the removal from a different disposition. This always follows a code 6, 7, E, H, K, U, or Q adjustment. Q - Inventory disposition change Units of a certain disposition are removed from your inventory and then added back to your inventory as a different disposition. This is always followed by a P code adjustment.
Inventory dispositions
Inventory disposition represents the physical state of a unit or units.
Inventory disposition Inventory state Definition Sellable Sellable Inventory that looks and functions as described in the listing Defective Unsellable Inventory that does not look or function as described in the listing and is not visibly damaged, for example, a recalled product Customer damaged Unsellable Inventory that was damaged by a customer Distributor damaged Unsellable Inventory that was damaged by the seller, vendor, or distributor during receiving Warehouse damaged Unsellable Inventory that was damaged at an Amazon fulfillment center Carrier damaged Unsellable Inventory that was damaged by a carrier during receiving, while in transit to the customer, or while in transit back to Amazon due to a return Expired Unsellable Inventory that has passed its expiration date as described in Date/Lot Tip: You can save on fees by removing inventory that is unsellable.
How to read your report: online and download methods
You can see adjustments to your inventory online in Seller Central or by downloading the Inventory Adjustments report.
The View Online method is recommended for quickly seeing inventory adjustments and reconciliations. When there is a reconciliation for an inventory adjustment, a link is provided that will connect you to either the reconciliation adjustment in the Inventory Adjustment report or the reimbursement transaction in the Reimbursement report.
The Download method is recommended for understanding the reconciliation status of inventory adjustments at scale.
In the online view, you can filter inventory adjustments by Reason group, as shown in the table below.
Reason groups by adjustment code
Code Reason group 6, 7, E, H, K, U Damaged D Inventory disposed of F, N Found 5, M Lost 3, 4, O, P, Q Other
To see your Inventory Adjustments report online:
Click the View Online tab in the Inventory Adjustments report.
Select the desired date range in the Event Date drop-down menu and the reason group in the Reason Group drop-down menu. If you leave the Reason Group field blank, the report will show all adjustment reasons.
If you want to filter the results further, you can add the Merchant SKU, Fulfillment Network SKU, or FC, or any combination of those.
Click the Generate Report button.
Note: If there are more than 50 inventory adjustments, the report will generate multiple pages. Use the quick links at the top and bottom right of the report to navigate between pages.
Here is an example of a reported that was generated with the selected reason group Lost, the date range Last 365 days and the Fulfillment Network SKU X001SL. Clicking on Inventory misplaced in the report’s Reason column opens the reconciliation status.
Date Transactions Item ID FNSKU Merchant SKU Title Disposition FC Reason Quantity July 23, 2019 2108808 X001SL SLU_2PK SLU_PHOTO_2PK Sellable LGB3 ? Inventory misplaced -16 Inventory found 5 Remaining misplaced or damaged inventory 11
Click on the reconciliation status — in our example, Inventory found — to see the reconciliation events. In this case (see the illustration below), a total quantity of five can be seen for five Inventory found adjustment reasons.
Date Transactions Item ID FNSKU Merchant SKU Title Disposition FC Reason Quantity July 23, 2019 2108808 X001SL SLU_2PK SLU_PHOTO_2PK Sellable JFK8 ?Inventory found 1 July 23, 2019 210190912 X001SL SLU_2PK SLU_PHOTO_2PK Sellable DCA1 ?Inventory found 1 July 23, 2019 2101901 X001SL SLU_2PK SLU_PHOTO_2PK Sellable PHX6 ?Inventory found 1 July 23, 2019 210188746 X001SL SLU_2PK SLU_PHOTO_2PK Sellable MGE7 ?Inventory found 1 July 23, 2019 21188081 X001SL SLU_2PK SLU_PHOTO_2PK Sellable MKE1 ?Inventory found 1 Note: For Remaining misplaced or damaged inventory occurring after November 15, 2019, that has not been reconciled, you may be eligible for reimbursement under the FBA lost and damaged inventory reimbursement policy.
To download your Inventory Adjustments report:
Click the Download tab in the Inventory Adjustments report.
Select the desired date range in the Event Date drop-down menu.
Click either Request .csv Download or Request .txt Download for the format you prefer. It typically takes between 1 and 45 minutes to generate a report.
Once the report status changes from In Progress to Download, click the Download button.
Save the file to your computer.
Open the report in a spreadsheet or database program, such as Microsoft Excel or Microsoft Access.
Here is an example:
adjustment-date transaction-id fnsku sku product-name fulfillment-center quantity reason disposition reconciled unreconciled 2019-07-23 2108808 X001SL SLU_2PK SLU_PHOTO_2PK LGB3 -16 M SELLABLE 5 11 For reconciled quantities with reason codes for Damaged at Amazon fulfillment center, Inventory misplaced, or Inventory found, you can get more information in the online view.
For unreconciled quantities with reason codes for Damaged at Amazon fulfillment center and Inventory misplaced occurring after November 15, 2019, you may be eligible for reimbursement under the FBA lost and damaged inventory reimbursement policy.
Reconciliation events
Inventory adjustments for Inventory misplaced, Inventory found, and Damaged at Amazon fulfillment center will have corresponding reconciliations. You can see these reconciliations in both the online and downloadable view.
Online
When there is a reconciliation for an inventory adjustment, a link is provided that will connect you to either the reconciliation adjustment in the Inventory Adjustment report or the reimbursement transaction in the Reimbursement report.
Downloadable
You will be able to see reconciled and unreconciled quantity columns for Inventory misplaced, Inventory found, and Damaged at Amazon fulfillment center. For example, when an inventory adjustment is reimbursed or reconciled, you will see the unreconciled quantity decrease and the reconciled quantity increase.
Here is an example from the online view:
Date Transactions Item ID FNSKU Merchant SKU Title Disposition FC Reason Quantity July 23, 2019 2108808 X001SL SLU_2PK SLU_PHOTO_2PK Sellable LGB3 ? Inventory misplaced -16 Inventory found 5 Remaining misplaced or damaged inventory 11
Here is an example from the download view:
adjustment-date transaction-id fnsku sku product-name fulfillment-center quantity reason disposition reconciled unreconciled 2019-07-23 2108808 X001SL SLU_2PK SLU_PHOTO_2PK LGB3 -16 M SELLABLE 5 11
The following table lists all possible original event and reconciliation event combinations.
Inventory adjustment reason Reconciliation reason (displayed in drop-down menu) Definition Damaged at Amazon fulfillment center Inspected and disposition corrected Inventory that an inspection found was not damaged at the fulfillment center Reimbursed Inventory for which you have been reimbursed Remaining misplaced or damaged inventory The remaining inventory that has not been reconciled Inventory misplaced Inventory found Misplaced inventory that was found Reimbursed Inventory for which you have been reimbursed Damaged inventory misplaced Damaged at Amazon fulfillment center inventory that was misplaced. Note: The reconciliation will be applied to the Damaged at Amazon fulfillment center inventory.
Remaining misplaced or damaged inventory The remaining inventory that has not been reconciled Inventory found Replacement inventory found Inventory that was replaced to compensate for inventory lost or damaged, in accordance with the FBA lost and damaged inventory reimbursement policy. Missing inventory found Misplaced inventory that was found Inventory ownership correction Incorrectly assigned found inventory that was moved to the correct owner Note: Inventory adjustments other than Inventory misplaced, Inventory found, and Damaged at Amazon fulfillment center will not show a reconciliation reason in the online view or the downloadable view.
Why are my items being researched?
You will notice a new inventory classification in the Manage Your Inventory page and report, called Researching. This represents the misplaced or warehouse damaged inventory that is actively being confirmed at our fulfillment centers. A timeline shows the duration of the research, which will never exceed 30 days. Once the inventory being researched has been reimbursed or has exceeded the 30-day duration, you will see the corresponding adjustment transition over to the Inventory Adjustment report. For inventory adjustments occurring after November 15, 2019, you do not have to wait 30 days to file a claim because we are handling the 30 day researching duration for you.
Field definitions
Online header Download header Description Date adjustment-date DD-MM-YYYY Transaction Item ID transaction-item-id Unique ID for this item adjustment FNSKU fnsku Unique item ID assigned by Amazon and used by the fulfillment center Merchant SKU sku Unique item ID assigned by the seller Title product-name Name of the product as listed on Amazon Fulfillment Center ID fulfillment-center-id Fulfillment center where the adjustment is being made Quantity quantity Number of units adjusted Reason reason The download file displays codes while the online view shows descriptions. See the Adjustment types and reason codes table at the top of this page for full codes and descriptions. Disposition disposition Whether the item is in sellable or unsellable/unfulfillable condition N/A Reconciled Number of units reconciled with other adjustment events N/A Unreconciled Number of units not reconciled with other adjustment events
文章泉源：亚马逊官方网站