Got another barcode problem again (for another FBA labeled shipment)
What a joke
Not sure what the motivation is for this issue, they’re already charging for FBA labeling.
Welcome to the club.
We had the same call, and when they wouldn’t address our questions or assertions, we told them to “finish their script” put the phone on speaker and had a forklift operator on their break sit in the office, and go “uh-huh” and “no questions” while the rest of us went back to work.
Just to rub salt in my current open wounds, just got a shipment problem for barcodes not scanning at FBA
Shipment contained 8,184 units on 2 pallets. 28 of them won’t scan. Right…Sure…
Professionally printed, identical, digital press labels that have no UV coating on them to avoid this bull ■■■■. Still get screwed.
Dispute time. The good news is I saved the verbiage I used the last time that got accepted. Copy/Paste - send it!
Dispute and request picture proof. They won’t find it and basically remove that garbage off your problematic shipment count. It’s fuqin bonkers.
Yup, we always to dispute. We don’t always win.
Re-surfacing this with SAS. I have a call with them on Wed, on my birthday of all days.
Nah, they’ll send a picture, where the picture of the barcode will scan, but claim it’s unscannable.
Hasn’t happened to us yet. Usually, the response is “we could not locate the problematic units…blah blah blah. We have removed the problematic shipment…blah blah blah”
If they did have proof they would send it, but they don’t lately.
But maybe you’re right 
Depends on the situation, but I’ve definitely received a picture that was scannable with a barcode problem..
That’s happened to us a few times in recent years as well, but we’ve always been able to point out their own error (not that Amazon has ever admitted it in writing 
).
Happy Birthday you pre-Turkey baby!
{{{ pre-Turkey just sounded less offensive than pre-Stuffed … 
}}}
And you weren’t able to point out that you could scan the picture and they’re mentally misformed?
Their automated machine ruled it as unscannable, so it stuck. It’s hard to overturn a machine decision. This one was also for a small number of units so it didn’t affect my problem rate much so I didn’t persist in appealing it.
Thanks very much. Sometimes my b-day is on Turkey Day but leap year is gonna make it awhile before it happens again.
2012, 2018, 2029, 2035, 2040, 2046, 2057, 2063, 2068, 2074, 2085, 2091, 2096
Will have to wait and see I suppose. Good to know.
You know how impossible it’s going to be for Amazon to find the 28 bottles out of the 8K? LOL
They may have been sold by the time they get around to their “investigation”.
If they claim they found them, then it’s a lie, plain and simple.
Someone should sue Amazon over this bs. It’s outlandish. What exactly has Amazon accomplished by introducing this? They waste more time documenting and reporting this stuff then they could ever make back in fees to fix what wasn’t broken. Is this some kind of power trip? Daddy coming to slap us on the wrist with a ruler for being bad boys and girls?
They are aggravating their “partners” and treating them like crap which is nothing new but as far as I can tell, the system launched in 2019 (Nov to be exact) because that’s when it started for us.
They “catch” this stuff on the belt scanners as each and ever single unit is scanned - another insane practice. Could you imagine receiving 2 pallets of 8K+ units in 200 something cases of 24, opening it all up, tossing the cardboard, lining these things up on a belt to be scanned / counted? Then they have to put them in totes and boxes and move them all around to once again be scanned in at their final destination? There’s gotta be a better way.
My last SAS manager worked in an Amazon DC as a manager. He told me all about the belt scanners and what crap they are and the complete receiving process.
Not to speak of the FC damage
They will take a picture of your barcode and find something wrong like “too reflective” and say it’s a label when its printed on the actual product, or some teeny weenie shift in one of the letters below the bar code to assert is out of policy despite the letters not being a bar code.
When they send a picture of our uncorrected bar code, we reply with “you did not replace the bar code on this item, so why should we?”
Thanks for this. Forgot to put this BS on my agenda for my call with SAS tomorrow AM.