Title: Feed processed successfully (zero errors) but variation relationship not updating in catalog — Oak Frame child not appearing in family
Hello,
I am hoping someone has encountered this situation and can offer guidance.
Background: In June 2026 I restructured my variation families by deleting and recreating parent SKUs. This inadvertently left stale blocked parent-child relationships in Amazon's backend for my Oak Frame child ASINs. These blocked relationships were causing Error 8801 whenever I tried to reattach the Oak Frame children to their parents via flat file.
What has been done so far:
- Seller Support confirmed the blocked relationship for the test ASIN (B0H5N8GJDF) was deleted from their system
- Seller Support submitted a catalog refresh for this ASIN
- I submitted a flat file to reattach the child to its parent (batch ID 94854020635)
- The feed processed with 1 SKU processed, 1 successful, zero errors, zero warnings.
The problem: Despite all of the above, the catalog has not updated. The customer-facing product page still shows only two variation buttons. The backend Edit Product page still shows only 2 variations. The Oak Frame child is listed as "This product is not part of a variation" in its own Edit Product page.
It has now been over 25 hours since the successful feed submission with no change.
I have approximately 149 Oak Frame child ASINs across my catalog with this same issue. I need to understand why a successfully processed feed is not being reflected in the catalog before proceeding with the bulk fix.
Has anyone experienced a situation where a feed processes with zero errors but the catalog does not reflect the change, specifically for variation relationships? Is there a known solution beyond what has already been attempted?
Any guidance from sellers or Amazon staff would be greatly appreciated.
@Michelle_Amazon
@Rose_Amazon
@Sunnie_Amazon
@Jim_Amazon
@Danika_Amazon
@Emet_Amazon
@Cooper_Amazon
@Bryce_Amazon
Title: Feed processed successfully (zero errors) but variation relationship not updating in catalog — Oak Frame child not appearing in family
Hello,
I am hoping someone has encountered this situation and can offer guidance.
Background: In June 2026 I restructured my variation families by deleting and recreating parent SKUs. This inadvertently left stale blocked parent-child relationships in Amazon's backend for my Oak Frame child ASINs. These blocked relationships were causing Error 8801 whenever I tried to reattach the Oak Frame children to their parents via flat file.
What has been done so far:
- Seller Support confirmed the blocked relationship for the test ASIN (B0H5N8GJDF) was deleted from their system
- Seller Support submitted a catalog refresh for this ASIN
- I submitted a flat file to reattach the child to its parent (batch ID 94854020635)
- The feed processed with 1 SKU processed, 1 successful, zero errors, zero warnings.
The problem: Despite all of the above, the catalog has not updated. The customer-facing product page still shows only two variation buttons. The backend Edit Product page still shows only 2 variations. The Oak Frame child is listed as "This product is not part of a variation" in its own Edit Product page.
It has now been over 25 hours since the successful feed submission with no change.
I have approximately 149 Oak Frame child ASINs across my catalog with this same issue. I need to understand why a successfully processed feed is not being reflected in the catalog before proceeding with the bulk fix.
Has anyone experienced a situation where a feed processes with zero errors but the catalog does not reflect the change, specifically for variation relationships? Is there a known solution beyond what has already been attempted?
Any guidance from sellers or Amazon staff would be greatly appreciated.
@Michelle_Amazon
@Rose_Amazon
@Sunnie_Amazon
@Jim_Amazon
@Danika_Amazon
@Emet_Amazon
@Cooper_Amazon
@Bryce_Amazon
3 replies
Seller_e7Ucgb0T3KE8r
still no change. oak product is still orphaned. seems amazon used API to directly intervene and edit the catalog last night at 3:37am. But still the oak product is orphaned. This feels so hopeless at this point. Just banging my head against the wall for 2 weeks straight. Ugh. Maybe the update just needs time to propagate through the system. If this is taking so long and is so impossible to accomplish for one single ASIN, what hope do I have of fixing the 150 others?
Manny_Amazon
Hello @Seller_e7Ucgb0T3KE8r,
Thanks for posting here. I have reviewed the details of your issue and have confirmed that the correct info was given to you via case #20937190101 on July 6. This issue relates to usage of a third-party application connected to your account — Shopify Marketplace Connect. Please refer to this update from the team and feel free to reply to them if you have any further questions.
Regards,
- Manny
