Why my compliance document was "incomplete, inaccurate otherwise conflicting" and couldn't be used for classificaton

Mind you, this is an ASIN that flirts with 7 digits a year and has been active since 03/2020…

If you can’t see the mistake at first glance:

→ The hazard code and statement from SDS in section 2 is "H304 and May be fatal if swallowed and enters in airways when the correct form as per the Regulation “GHS” is “H304 and May be fatal if swallowed and enters airways”.

I have always sucked at my prepositions… one oft he hardest things of learning a second language

I don’t fault you, it isn’t not correct.

Sad that AI is that “dumb”.

I can barely one language but at least I can actually understand not just “predict” what should be the next few words.

My poor wife (she’s 'Murrican) and has taught me a lot. But when it comes to “in, on, at” she’s straight up told me “don’t worry, people don’t understand your pronunciation anyway, use whichever one you want.” :laughing:

Got an email this morning, the SDS got accepted and the ASIN will be re-classified (oh dear…) “in the shortest time possible” after removing the “in”

Hope they only mess with the ASIN and not the ASIN family

:crossed_fingers:

…and has it been? :sweat_smile:

It has. It hasn’t.
No actual issues since. Just the joy of dealing with Amazon.
But on the other hand, I have this beauty: (@ASV_Vites would have a conniption if this was his screen, but in all honesty, I’m quite offended by it)

I have always kept that with straight 0s except for very sporadic situations. Never had a red sign for more than a couple days (at most), except for one time that I had to deal with the indescribable delight of brand registry abuse (I’m well protected with uspto, but that’s a bit boohoo to Amazon that first penalizes and then checks)

The sad part is that the 4 “violations” are Amazon telling me that I’m selling products with state restrictions (no :poop:, Sherlock. I’m the one who asked Amazon to enforce the state restrictions)

I can appeal the violations, but they don’t have any impact on anything (other than my physique). The listings are active everywhere, except for the states where they are supposed to be suspended. I shouldn’t have a violation (I have had restrictions on my products since at least 2023), but I fear that appealing it may actually cause more harm than good.

Idk if maybe @Dogtamer or @oneida_books could give me their $0.02 cents and confirm if it’s ok to just ignore that red eyesore and let it linger. Again, I have the documentation of the cases opened with Amazon where I asked for the restrictions and they gave the :+1:t3: to implementing them, so it should be a slam dunk. But, do I really want to mess with children on two different families that combine to a significant chunk of change?

I got the shivers from just seeing that. Good luck!

I don’t typically recommend leaving Restricted Product violations unaddressed, but given the parameters you’ve described, and Amazon’s response re: re-classification, that’s not the case - you have addressed the concern.

I’d be inclined to follow the ‘ignore’ route here, because I agree that any appeal is at least as likely to stir an unwelcome pot as not.

thank you, @Dogtamer I agree with everything you just said

I don’t mean to scare you, but change the date back a few years to now on the policy violation page. Every single geographic restriction is flagged as a violation, dating back to their launch date.

I have cases with seller support on a few of them, definitely not going to do them all at once, especially the 2024 ones because there is no reason for a violation to be on a geo-restriction notice in 2024. I also made a new post on the forums after the appeals response told me they don’t handle appeals. I tagged mods so hopefully they can look into it for all of us.

I am trying to let them know that restrictions are not violations and this is happening to everyone, so fingers crossed.

My best sellers all have state restrictions. So I certainly hope that it gets fixed.
It’s the same problem as always, a nice account is working flawlessly and well, let’s send some bots to rock the boat. Almost as if they kept a counter of how long it’s been since the last time a seller had to open a case with SS. “nope, 5 months, it’s too long, let’s create a problem where there was nothing”

Amazon can’t leave something that works alone. Every time you get into a new project with Amazon a new statistic that you didn’t know is pushed on you and simply creates more stress. Idk why they do it. Doing business is hard enough as it is, but it’s like Amazon enjoys keeping sellers on edge and nervous of things outside their control.

Hope your voice is heard and starts to fix the issue for the rest of us!

Today, it still shows violation on the numbers page but if you go into the violations page it now says “Jurisdictionally restricted”
FINALLY :partying_face: