Possible Seller Central sync issue: inconsistent order visibility may be affecting FBA inventory status and causing stranded inventory
Hi everyone,
I’ve now seen two separate issues in Seller Central that seem like they may be connected.
Issue 1:
One FBA SKU showed 3 units as customer ordered and went out of stock, but neither my order reports nor Seller Support could find any matching customer orders. I switched the SKU to FBM because it appeared unavailable. About 12 hours later, the same SKU appeared in stranded FBA inventory, with no reserved units and no visible buyer orders.
Issue 2:
At a different time, I checked Manage Orders in two browsers at the same time and saw different order histories. A recent order appeared in Firefox but was missing in Opera, even though both were logged into the same UK Seller Central account.
This makes me wonder whether Seller Central sometimes has a wider sync/display problem where:
buyer orders or temporary reserves are not consistently visible to sellers
different interfaces or browsers show different order states
inventory can be reduced by hidden or pending order activity
if the seller changes a SKU from FBA to FBM during that period, the FBA units may later become stranded after the system recalculates listing status
So my question is:
Has anyone seen evidence that inconsistent order visibility, pending payment verification, or hidden reserve states can affect FBA stock status and then lead to stranded inventory after a fulfilment-channel change?
My concern is that sellers may make decisions based on incomplete seller-facing data, while Amazon’s backend is holding a different status.
Thanks.
Possible Seller Central sync issue: inconsistent order visibility may be affecting FBA inventory status and causing stranded inventory
Hi everyone,
I’ve now seen two separate issues in Seller Central that seem like they may be connected.
Issue 1:
One FBA SKU showed 3 units as customer ordered and went out of stock, but neither my order reports nor Seller Support could find any matching customer orders. I switched the SKU to FBM because it appeared unavailable. About 12 hours later, the same SKU appeared in stranded FBA inventory, with no reserved units and no visible buyer orders.
Issue 2:
At a different time, I checked Manage Orders in two browsers at the same time and saw different order histories. A recent order appeared in Firefox but was missing in Opera, even though both were logged into the same UK Seller Central account.
This makes me wonder whether Seller Central sometimes has a wider sync/display problem where:
buyer orders or temporary reserves are not consistently visible to sellers
different interfaces or browsers show different order states
inventory can be reduced by hidden or pending order activity
if the seller changes a SKU from FBA to FBM during that period, the FBA units may later become stranded after the system recalculates listing status
So my question is:
Has anyone seen evidence that inconsistent order visibility, pending payment verification, or hidden reserve states can affect FBA stock status and then lead to stranded inventory after a fulfilment-channel change?
My concern is that sellers may make decisions based on incomplete seller-facing data, while Amazon’s backend is holding a different status.
Thanks.
3 replies
Angie_Amazon
Hello @Seller_kSZCywEhJQQ8J,
Thank you for bringing these concerns to our attention.
Regarding the FBA SKU showing customer ordered units with no matching orders:
This situation can occur due to temporary system sync delays or reserved inventory states. Here's what I recommend:
- Check your FBA Inventory page to see if these units are showing as "Reserved" - units can be reserved for customer orders that are in processing, or for FC transfers
- Review your Manage FBA Inventory report to see the detailed inventory status breakdown
- If units appear stranded after 12-24 hours, check the Fix Stranded Inventory page for any issues
The fact that the SKU later appeared in stranded inventory suggests there may have been a listing issue that temporarily made the inventory unavailable for sale while the system was attempting to process something.
Regarding the different order histories in different browsers:
Order display inconsistencies across browsers can occur due to:
- Browser caching - Different browsers cache data differently, which can show different states temporarily
- Session sync delays - If you're logged into multiple browsers simultaneously, there can be brief delays in data synchronization
- Filter settings - Ensure both browsers have identical filter settings (date range, order status, fulfillment channel)
To troubleshoot:
- Clear your browser cache in both browsers
- Log out completely and log back in
- Verify that all filter settings match exactly
- Check if the "missing" order appears after refreshing the page
My recommendation here, since you're experiencing what appears to be systematic visibility issues rather than isolated incidents, I strongly recommend:
Document everything - Take screenshots showing the discrepancies with timestamps
Contact Seller Support with specific examples, including:
- The SKU from Issue 1 with dates when it showed customer ordered units
- Screenshots from both browsers showing different order histories
- Your case IDs: [mention any existing case numbers]
You can contact them directly here.
— Angie
Seller_kSZCywEhJQQ8J
Thank you, but this reply is missing the main point.
I did already contact Seller Support when this happened. The support agent checked from their side and also could not find any matching customer orders. The FBA inventory status they saw was exactly the same as what I saw. Their advice was simply to wait 24 hours and monitor it.
So this was not just a case of me looking at the wrong page, using the wrong filter, or misunderstanding the screen.
On the browser point, I had already tested that:
I used Firefox and Opera at the same time
both were logged into the same UK Seller Central account
both had the same filters and parameters
both were hard refreshed with Fn + F5
the discrepancy still remained
So no, this was not obviously a browser cache issue.
Also, saying “Opera is unsupported” does not explain why Seller Support could not see the orders either. Unless Seller Support were also using Opera, the browser explanation does not fit the facts.
The real issue is this: both the seller and Seller Support were seeing the same absence of orders, while the SKU was still showing customer-ordered units. Later, the inventory moved into stranded status. That points to inconsistent seller-facing system data, not just a local browser problem.
Sellers are expected to make decisions based on what Amazon shows us. If Amazon shows stock as customer ordered, but neither the seller nor Seller Support can see the actual order, then telling the seller to clear cache and wait is not a real answer.
This is why I believe the problem is a Seller Central sync or backend visibility issue. Blaming the browser is just an easy way to avoid addressing the actual inconsistency.
If Amazon wants sellers to trust the inventory and order pages, then those pages need to reflect the real state of the system. In this case, they clearly did not.
Please do not reduce a system inconsistency to “try another browser” when Seller Support saw the same thing and could not explain it either.
Christine_Amazon
Hi @Seller_kSZCywEhJQQ8J
Can you please share the case ID with our seller support team?
Christine.
