We are using the native Amazon Connector (BC201020), importing seller-fulfilled orders.
I originally set up an item as a stock item and added its ASIN as an Alternate ID (Global type) on the Cross-Reference tab. We later decided the item should be a non-stock item instead. I created the non-stock item, removed the cross-reference row from the stock item (and saved), and added the same ASIN as a Global cross-reference on the non-stock item.
When the Amazon Connector imports an order containing that ASIN, it errors out saying the cross-reference exists on two items — both the original stock item and the new non-stock item.
**What I've checked:**
- Reopened the stock item (IN202500) — the cross-reference row is not visible on the Cross-Reference tab.
- The non-stock item (IN202000) shows exactly one row for the ASIN, Alternate Type = Global.
- Only one UOM row exists per item; no duplicates within either item.
**Questions:**
1. Is there a place other than the item's Cross-Reference tab (e.g., a residual row in INItemXRef by different AlternateType, or a hidden UOM variant) where the old mapping could still be living?
2. Does the Amazon Connector cache a SKU → InventoryID resolution in prepared data or in BCSyncStatus/BCEntityStats such that clearing/reprepping is required after moving a cross-reference between items?
3. If so, what's the recommended reset — delete the failed sync record on Process Data (BC501500) and re-prepare, or something more involved?
