Child ASINs disconnected from parent ASIN

Countries

Read only
Australia
Belgium
Brazil
Canada
Egypt
France
Germany
India
Italy
Japan
Mexico
Netherlands
Poland
Saudi Arabia
Singapore
Spain
Sweden
Turkey
United Arab Emirates
United Kingdom
United States
United States
imgSign in
Country changed
user profile
Seller_I8C35sGyzmuGe

Child ASINs disconnected from parent ASIN

We have two parent ASINs for which the child ASINs have been disconnected and are showing as independent/standalone listings. The interesting part is that in the backend of seller central the child ASINs show under parent but on the live site they are standalone listings. We have created two cases (one case for each parent ASIN) since early October but there have been no solution and an update on the cases.

Here are case numbers:

Parent ASIN 1 - 16369468641

Parent ASIN 2 - 16502956481

549 views
26 replies
30
Reply
26 replies
user profile
Seller_i6S8knzW6zU6Z

Hi @Seller_I8C35sGyzmuGe

Have you tried performing a partial update using a flat file to reconnect the child ASINs to the parent?

If you haven’t done this before, Amazon provides resources on how to work with flat files, which can be helpful. Assuming you’re somewhat familiar with flat files, here are the key columns to check for reconnecting child ASINs to a parent ASIN:

  • Make sure the parent_sku is correctly specified.
  • The variation_theme matches what is specified for the parent.
  • The variation attributes are filled out in the flat file.

If the parent ASIN already exists in the catalog, you don’t need a row for the parent ASIN—just one row for each child ASIN.

Hopefully, this helps get things back on track!

Kind regards, Michael

00
user profile
Seller_WBnGS7Ix3XiDX

@Seller_i6S8knzW6zU6Z gave some great advice. I have used the flat files to create the child ASIN many years ago. I have the same problem where they separated my medium size child ASIN, to be a product on its own. Can't tell you why.

The flat file wasn't easy, but you can try a few times. I finally got it right, and it showed up fixed, in 15 minutes.

It might speed things up since you are waiting. Although I would suggest you try it on your own, but they do offer partners to assist with this, for a fee, of course. Let us know if it worked.

Maybe there is a You Tube video to help also. Good luck!

20
user profile
Seller_I8C35sGyzmuGe

@Manny_AmazonI would appreciate if you can look into this.

10
user profile
Seller_pZwsXsAgyx51U

We're experiencing this issue with some of our products. Even if we successfully merge them back to the parent, Amazon will unmerge the child ASINs again. Based on a thorough review, Amazon wants to ensure that all child ASINs have the same information unless they differ in color or size. Additionally, sometimes Amazon updates the maximum character limit for parent titles, and if this limit is exceeded, it can cause the child ASINs to unmerge. Please make sure to check that as well. However, if you feel confident that they have the same information, you can create a case with Seller Support. Sometimes, it just requires double-checking all the information on the flatfile, you might need to tweak something and merge them again with a new parent.

10
user profile
Seller_rmjsYCGId4E6I

I had this problem, ask for a re- drive request. Call during the midnight hours or on the early morning weekend hours for the best luck. I find thats when I get the most helpful people.

00
user profile
Seller_Qg1FueblHU9RR

We have been having the same issue for more than a month with multiple ASINs and there is no help in sight.

40
user profile
Seller_1sZE5n9hympJR

We had this happen on a few where Amazon changed the product type and category on the one child, but did not change it on the parent. This never should've been changed and it separated the child off of the parent (stand-alone listing) because of the different information.

A case had to be opened for Amazon to put everything back on the child the way it originally was.

Another case had to be opened asking them to link the child back to the parent - using a file wouldn't put it back. It took many months because of course nothing is ever resolved on contact #1 or contact #15. Constant back and forth with the same inquiry and multiple cases, but eventually Amazon fixed it.

11
user profile
Seller_nBUcRErQhJ4JW

We have this happen now and then, Good luck with support. They have tools to fix it but wont, they will have an "internal team" ( a lame excuse) investigate and do nothing.

20
user profile
Manny_Amazon

Hello @Seller_I8C35sGyzmuGe,

Thanks for posting your inquiry. I've reviewed the details, and see that both cases are currently open with Support. Please allow the team time to review this and get back to you with an update. If you see that the case resolves later and still need help, let me know here and I'll look into seeing what options exist for escalation.

Regards,

- Manny

20
Follow this discussion to be notified of new activity