FBA Found Missing Units, Created “.missing1” MSKU, Now 101 Units Stranded and Backend Status Inconsistent
Hello,
I am hoping a Community Manager can assist, as standard Seller Support has not been able to resolve this issue.
Summary:
Shipment ID: FBA195NCC8M7
We shipped 110 units in this shipment. Amazon initially marked them as missing. We opened an investigation and the units were eventually found.
However, instead of being returned to the original SKU, Amazon created a new system-generated MSKU:
FBA195NCC8M7.missing1
Those recovered units are now showing as stranded inventory (101 units remaining) with the stranded reason “Create a new listing.”
The issue:
- The listing is live.
- The detail page is live and purchasable.
- The item appears active in Manage Inventory (both fulfillment methods).
- Customers can purchase it right now.
- We are Brand Registered and the brand owner.
Yet Seller Support claims that “in the backend” the listing is deleted and we must create a new listing.
If I attempt to create a new listing, Seller Central warns that the product is already listed in our inventory, so creating a duplicate would violate catalog policy.
Additional concerns:
- Amazon Retail is appearing as a seller on the detail page.
- I currently have 101 stranded units with an auto-removal date.
- I am concerned that inventory recovered from the missing shipment was not properly reattached to the original SKU and may now be misassociated in the catalog.
Seller Support responses have been inconsistent. I have been told:
- The listing is deleted.
- The listing is active but deleted in the backend
- Create a new listing.
- Wait 24–48 hours and it may disappear.
There is clearly a backend catalog or MSKU association issue between the original SKU and the system-generated “.missing1” SKU.
Relevant Case IDs:
19431315451
19485914311
What I need:
- The recovered inventory reassociated with the original SKU.
- Removal of the stranded “.missing1” MSKU.
- Confirmation that recovered inventory is properly attributed and not misassociated.
- Clarification on why Amazon Retail is appearing while we have stranded units from the same shipment.
We are not willing to create a duplicate listing for an existing product, as that would compromise catalog integrity.
If a Community Manager can escalate this to the inventory reconciliation or catalog team, it would be greatly appreciated.
Thank you.
FBA Found Missing Units, Created “.missing1” MSKU, Now 101 Units Stranded and Backend Status Inconsistent
Hello,
I am hoping a Community Manager can assist, as standard Seller Support has not been able to resolve this issue.
Summary:
Shipment ID: FBA195NCC8M7
We shipped 110 units in this shipment. Amazon initially marked them as missing. We opened an investigation and the units were eventually found.
However, instead of being returned to the original SKU, Amazon created a new system-generated MSKU:
FBA195NCC8M7.missing1
Those recovered units are now showing as stranded inventory (101 units remaining) with the stranded reason “Create a new listing.”
The issue:
- The listing is live.
- The detail page is live and purchasable.
- The item appears active in Manage Inventory (both fulfillment methods).
- Customers can purchase it right now.
- We are Brand Registered and the brand owner.
Yet Seller Support claims that “in the backend” the listing is deleted and we must create a new listing.
If I attempt to create a new listing, Seller Central warns that the product is already listed in our inventory, so creating a duplicate would violate catalog policy.
Additional concerns:
- Amazon Retail is appearing as a seller on the detail page.
- I currently have 101 stranded units with an auto-removal date.
- I am concerned that inventory recovered from the missing shipment was not properly reattached to the original SKU and may now be misassociated in the catalog.
Seller Support responses have been inconsistent. I have been told:
- The listing is deleted.
- The listing is active but deleted in the backend
- Create a new listing.
- Wait 24–48 hours and it may disappear.
There is clearly a backend catalog or MSKU association issue between the original SKU and the system-generated “.missing1” SKU.
Relevant Case IDs:
19431315451
19485914311
What I need:
- The recovered inventory reassociated with the original SKU.
- Removal of the stranded “.missing1” MSKU.
- Confirmation that recovered inventory is properly attributed and not misassociated.
- Clarification on why Amazon Retail is appearing while we have stranded units from the same shipment.
We are not willing to create a duplicate listing for an existing product, as that would compromise catalog integrity.
If a Community Manager can escalate this to the inventory reconciliation or catalog team, it would be greatly appreciated.
Thank you.
9 replies
Seller_RW2hhNpmNDVQL
Sorry to be a bother, but if any community manager can chime in and do an internal check, that would be great. Customer Support refused to escalate anything and "kindly" requested me to create a new listing despite already having an FBA and FBM listing live for this UPC/ASIN.
@Manny_Amazon@Glenn_Amazon@Christine_Amazon
Seller_xo4Akj7FBBnfC
@Seller_RW2hhNpmNDVQL, while posting your Case IDs in the original post certainly helps, there's never a guarantee that a mod will find this thread and offer to assist.
Have you tried reaching the Captive Team, as described in this earlier thread?
NR_Amazon
@Seller_RW2hhNpmNDVQL Thank you for posting to the forums! This can happen sometimes due to labeling/barcode issues, or because the FBA and Manage inventory SKUs or ASINs for this listing do not match. This could be because the product ID, such as the UPC or ASIN, changed, or because there is no listing in Manage inventory for this SKU.
I have escalated over your case details to determine if they are able to assist any further outside of the guidance that has already been provided by the Seller Support team. Please be on the lookout for an update on this thread, or for a new case to be generated on your behalf.
Thank you!
NR_Amazon
Seller_RW2hhNpmNDVQL
Hello @NR_Amazon and @JiAlex_Amazon,
I wanted to provide a brief update and request clarification following the most recent case response.
Case ID: 19508272791
We have now received two different explanations regarding the intake classification of our units.
The initial explanation provided by support stated that the FNSKU was “unscannable at intake,” resulting in the units defaulting to manufacturer barcode processing.
The most recent response indicates that the barcode format was altered from Amazon’s standard specification and therefore did not meet automated fulfillment center requirements.
These describe two distinct conditions:
• A scan failure due to unreadable barcode
• A format non-compliance despite being scannable
For context, our labels are printed using a 300 DPI thermal printer on black-on-white, non-reflective stock in accordance with Amazon’s published printer requirements. The barcodes scan successfully across multiple devices, including when tested against the fulfillment center image that was provided.
The only modification applied was minor text alignment to avoid automatic truncation in the generated label layout. The barcode encoding itself was not modified.
If the issue is something straightforward such as label dimensions, required margins, or strict adherence to the exact generated layout without any adjustment, we are fully prepared to correct that immediately. However, we have not yet received a clearly defined compliance point that explains which specific requirement was not met.
Given the difference between “unscannable” and “format altered,” we would appreciate any additional internal clarification you may be able to obtain regarding which intake condition actually occurred and what specific specification triggered the reclassification.
We are fully committed to compliance and simply want to ensure that the corrective action matches the true root cause.
Thank you for your continued assistance.
