Seller Forums
user profile
Seller_pEGO9YjE8hL3x

Brand Hijacked

I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.

The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.

I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)

I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.

I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.

Case ID = 12256032482

Are any of the mods able to help at all pls - @Sandy_Amazon

41 views
1 reply
Tags:Brand Registry
00
Reply
user profile
Seller_pEGO9YjE8hL3x

Brand Hijacked

I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.

The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.

I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)

I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.

I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.

Case ID = 12256032482

Are any of the mods able to help at all pls - @Sandy_Amazon

Tags:Brand Registry
00
41 views
1 reply
Reply
1 reply
user profile
Ana_Amazon

Hello @Seller_pEGO9YjE8hL3x,

My name is Ana, from the community manager team. Thank you for reaching out and sharing the details of your case.

Based on Case ID 12256032482, the internal team confirmed that your brand "Missloved" is active in Brand Registry, and they attempted to process the brand update for your ASINs under parent ASIN ending in Q77H. Additionally, we can confirm that ASIN ending in KER2 is already displaying under the brand "Missloved" on the live product detail page.

The brand revert to "LessThanTenQuid" was declined as this brand has been tombstoned and cannot be reactivated without re-registration. The migration to "Missloved" for remaining ASINs was declined due to policy restrictions, as the brand attribute does not match. 

To continue investigating and escalate this properly, could you please provide:

  • The exact error message you see when trying to list or edit your ASINs — a screenshot would be ideal. Specifically, where do you see the brand "WHAPELQ" mentioned? Is it in a listing error, a brand approval request, or somewhere else?
  • A direct link to one of the hijacked product pages showing the incorrect brand — since B01LWPKER2 is already showing under "Missloved," we need to identify which specific ASINs are displaying "WHAPELQ."
  • Any additional Case IDs you may have opened regarding this issue, so we can review the full history.

This information will help us pinpoint exactly how and where the WHAPELQ brand is affecting your listings, and allow us to escalate to the correct specialist team.

Kind regards,

Ana

00
Follow this discussion to be notified of new activity
user profile
Seller_pEGO9YjE8hL3x

Brand Hijacked

I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.

The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.

I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)

I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.

I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.

Case ID = 12256032482

Are any of the mods able to help at all pls - @Sandy_Amazon

41 views
1 reply
Tags:Brand Registry
00
Reply
user profile
Seller_pEGO9YjE8hL3x

Brand Hijacked

I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.

The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.

I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)

I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.

I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.

Case ID = 12256032482

Are any of the mods able to help at all pls - @Sandy_Amazon

Tags:Brand Registry
00
41 views
1 reply
Reply
user profile

Brand Hijacked

by Seller_pEGO9YjE8hL3x

I have circa 190 asins that have had their brand name changed to WHAPELQ, this asins were originally set up using the brand LessThanTenQuid unfortunately this mark the IPO did not approve.

The listings were created in 2016 and the rules were a little different then, I recall having that brand in my brand registry but at some point it dropped off most probs as there was no valid trademark for it.

I`m now at a position where I have most ASINs blocked as I need approval for this hijacked brand value (relates to chinese company accoding to IPO)

I have requested Amazon to revert but met with no success, I have over 500 units in FBA which are now sat there and I`m at wits end what to do.

I do however have a brand that is in brand registry which I attempted to migrate to but Amazon rejected this and also stated my previous brand which was no longer in brand registry was tombstoned. At the very least I`d like to revert back to LessThanTenQuid for now.

Case ID = 12256032482

Are any of the mods able to help at all pls - @Sandy_Amazon

Tags:Brand Registry
00
41 views
1 reply
Reply
1 reply
1 reply
Quick filters
Sort by
user profile
Ana_Amazon

Hello @Seller_pEGO9YjE8hL3x,

My name is Ana, from the community manager team. Thank you for reaching out and sharing the details of your case.

Based on Case ID 12256032482, the internal team confirmed that your brand "Missloved" is active in Brand Registry, and they attempted to process the brand update for your ASINs under parent ASIN ending in Q77H. Additionally, we can confirm that ASIN ending in KER2 is already displaying under the brand "Missloved" on the live product detail page.

The brand revert to "LessThanTenQuid" was declined as this brand has been tombstoned and cannot be reactivated without re-registration. The migration to "Missloved" for remaining ASINs was declined due to policy restrictions, as the brand attribute does not match. 

To continue investigating and escalate this properly, could you please provide:

  • The exact error message you see when trying to list or edit your ASINs — a screenshot would be ideal. Specifically, where do you see the brand "WHAPELQ" mentioned? Is it in a listing error, a brand approval request, or somewhere else?
  • A direct link to one of the hijacked product pages showing the incorrect brand — since B01LWPKER2 is already showing under "Missloved," we need to identify which specific ASINs are displaying "WHAPELQ."
  • Any additional Case IDs you may have opened regarding this issue, so we can review the full history.

This information will help us pinpoint exactly how and where the WHAPELQ brand is affecting your listings, and allow us to escalate to the correct specialist team.

Kind regards,

Ana

00
Follow this discussion to be notified of new activity
user profile
Ana_Amazon

Hello @Seller_pEGO9YjE8hL3x,

My name is Ana, from the community manager team. Thank you for reaching out and sharing the details of your case.

Based on Case ID 12256032482, the internal team confirmed that your brand "Missloved" is active in Brand Registry, and they attempted to process the brand update for your ASINs under parent ASIN ending in Q77H. Additionally, we can confirm that ASIN ending in KER2 is already displaying under the brand "Missloved" on the live product detail page.

The brand revert to "LessThanTenQuid" was declined as this brand has been tombstoned and cannot be reactivated without re-registration. The migration to "Missloved" for remaining ASINs was declined due to policy restrictions, as the brand attribute does not match. 

To continue investigating and escalate this properly, could you please provide:

  • The exact error message you see when trying to list or edit your ASINs — a screenshot would be ideal. Specifically, where do you see the brand "WHAPELQ" mentioned? Is it in a listing error, a brand approval request, or somewhere else?
  • A direct link to one of the hijacked product pages showing the incorrect brand — since B01LWPKER2 is already showing under "Missloved," we need to identify which specific ASINs are displaying "WHAPELQ."
  • Any additional Case IDs you may have opened regarding this issue, so we can review the full history.

This information will help us pinpoint exactly how and where the WHAPELQ brand is affecting your listings, and allow us to escalate to the correct specialist team.

Kind regards,

Ana

00
user profile
Ana_Amazon

Hello @Seller_pEGO9YjE8hL3x,

My name is Ana, from the community manager team. Thank you for reaching out and sharing the details of your case.

Based on Case ID 12256032482, the internal team confirmed that your brand "Missloved" is active in Brand Registry, and they attempted to process the brand update for your ASINs under parent ASIN ending in Q77H. Additionally, we can confirm that ASIN ending in KER2 is already displaying under the brand "Missloved" on the live product detail page.

The brand revert to "LessThanTenQuid" was declined as this brand has been tombstoned and cannot be reactivated without re-registration. The migration to "Missloved" for remaining ASINs was declined due to policy restrictions, as the brand attribute does not match. 

To continue investigating and escalate this properly, could you please provide:

  • The exact error message you see when trying to list or edit your ASINs — a screenshot would be ideal. Specifically, where do you see the brand "WHAPELQ" mentioned? Is it in a listing error, a brand approval request, or somewhere else?
  • A direct link to one of the hijacked product pages showing the incorrect brand — since B01LWPKER2 is already showing under "Missloved," we need to identify which specific ASINs are displaying "WHAPELQ."
  • Any additional Case IDs you may have opened regarding this issue, so we can review the full history.

This information will help us pinpoint exactly how and where the WHAPELQ brand is affecting your listings, and allow us to escalate to the correct specialist team.

Kind regards,

Ana

00
Reply
Follow this discussion to be notified of new activity