I am trying to manually(not a feed)update a listing with new photos but keep getting an error message indicating my unit count and unit count type are invalid so my changes will not be accepted. It appears the unit count field likes to have a .0 at the end of all whole numbers which is what I tried to enter by using 10.0 to represent 10 units but I can’t seem to get the field to update so I can’t make any changes to the listing. I also tried to enter the word “count” for type in lower case as suggested but that doesn’t work either. Finally, I tried to upload a flat file changing just the unit count and unit count type fields but it seems like I will need to copy and paste 19 required fields for each variation to get the system to hopefully accept the update. Does anyone know why I can’t just indicate this item is a 10 count? It worked when I originally created the item.
Is it a box with ten identical items in it ? … or …
Is it a pack of 10 identical items in it?
Examples
A box of tea with 10 bags (not normally sold separate)
A pack of 10 cans of the same soup (which could be sold separate but bundled together)
Something like this could make a difference when putting in the listing.
It is a pack of 10 novelty straws made by us. The whole thing is a pain because the field is actually showing the correct input of 10 count but we can’t alter anything without getting caught up with this “invalid” warning.
There are 2 spots that have to be filled in for this. Number of items would be 10 to drive the 10-pack graphic.
Item package QTY should be 1.
IDK if Amazon has changed this since we last set up a listing (It’s been awhile), but if it hasn’t changed, this should fix this issue hopefully.
Customer is getting 1 (item package qty), but there are 10 straws (10-pack).
Honestly, the size should probably just be 10 and number of items 1, because they aren’t getting 10, 10 packs. This may also solve your problem while also not misleading buyers who tend to complain, even though it’s obvious.
With that said, PLENTY of sellers play with that 10 pack. I’ve seen sellers in my category put 100 Pack for 100 pills….
I have never entered a “.0” on any listing like this.
This field (I’m pretty certain) is not editable after it is no longer null. I would do a PartialUpdate file upload and leave it empty.
If that doesn’t work it’s likely there’s an error in the content that doesn’t match Amazon’s allowed choices. You might have to get the Catalog Team to fix it.
Sadly, this didn’t work but I did have the package quantity blank so I was hopeful for a bit. I will move on to flat file and hope a partial update works. Thanks though.
Flat file didn’t work. Seller support now tells me it is a “global issue” and nobody can update unit count or unit count type. Since this error is preventing me from making any changes to the listing I don’t know why more sellers aren’t asking about the issue. Is this just a new way for seller support to get rid of you by saying to wait a few days because it is a “global issue?”
It’s a new card in their Rolodex of excuses so you say they were helpful in the survey.
Sorry you can’t solve this yet….
FWIW we have the same issue. It may actually be a problem for some of us and possibly not for others. I can’t use count at all and even using something like ounces from the pull down doesn’t work.
-Ana
I believe the listing I am trying to update started out in handmade so the transfer of listings to the regular catalog may have messed things up. We shall wait and see since I am out of ideas.
We’ve got 4 listings showing as “At Risk of Suppression” for Unit Count / Unit Count Type.
Showed up yesterday, actually I didn’t even notice it, our SAS manager did and reached out.
Lots of talk on the NSFE about this. There’s some sort of glitch that apparently has been going on for awhile.
All 4 of our listings already have the correct unit count / type on the backend and displaying correctly on their PDPs. When simply adding it back in by using the “recommended” fix workflow, nothing changes in terms of the warning.
Opened case with the knowledge that it would need to be escalated through SAS and was told everything would update within 48 hours. Got a day to wait but I would bet my life it’s not going to be fixed so already have all our escalation materials ready to send at 48 hours and 1 min (email scheduled)
Quick response from SAS today below:
Hi Steve,
A lot of my colleagues are discussing having this same issue; let’s wait by end of day, and escalate.
Best regards
I haven’t seen a mod response to any of the threads related to this on the NSFE which is weird. Hopefully they fix this soon. To sum it up, it’s not you, it’s Amazon again…. Something is wrong and hopefully it will be fixed soon. Maybe 1 last AWS fire they forgot to put out.
