Amazon Relabeling Properly Labeled Product
So we’ve had a systemic problem that is getting worse.
We ship multiple SKU’s in the same shipment to FBA Warehouse (MDW2 almost exclusively).
Multiple days a week we either get a message from a customer that they have received the wrong item, or we get a message from Amazon that they have created a case to “investigate” an issue or an email that they are closing our listing until we make amendments for customer service issues, which are almost exclusively “Wrong Item Sent”.
Every single time we request pictures, and every picture we receive has a human generated sticker label placed over our properly labeled product. The photo attached shows a small label placed over our properly labeled product. This happens virtually every day.
When we get a message from a customer, we create a case in Seller Central, upload the photo, request a bin check on the incorrect item sent, and Amazon does an investigation. Typically, the result of the bin check is that they have “found defects” and fixed them, “found no defects” or “Found defects” and ask us for which ASIN the items should be labeled.
I’ve spoken countless times (over 50) with various levels of Amazon Seller Support with no success. Some have heard of the problem, and have said that we are doing the correct process by doing a Bin Check. I continually say “how is it possible that Amazon who charges us back for 25.5” sized boxes shipped into their DC’s, takes the time to isolate, print an actual label, adhere it to our product WITHOUT LETTING US KNOW OR CHARGING US but will charge us back and stop us from sending in product if a master carton is “too big” by less than an inch" “You are treating the symptom (bin checking product AFTER the problem has occurred instead of treating the DISEASE as to WHY they are relabeling properly labeled merchandise”
I can only speculate as to WHY this happens - some have said it’s to balance unbalanced counts. Anyway you look at this it’s crazy bad business. It costs a ton to relabel this merchandise. Customers 100% will get the WRONG PRODUCT when it is ordered, resulting in a huge return rate.
Does ANYONE have a solution here. I want the relabeling to stop. The only solution I can think of is to only send the SAME SKU in with each shipment, which is unrealistic for us (and should have to be)
11 replies
Seller_rpwxjC95NIJjm
If amazon cant scan the product, they search it up on the computer. As I can see, they labeled a different product, with the same brand. So they were being lazy.
Seller_d6BEjE7OOvMnp
Anyone else have this issue? Anyone have an answer. We have this problem with lots of our SKU’s
Seller_4XTCqF7P1oC7V
We have had the same issue and try to mitigate with several workarounds, but it still happens, just not as much.
I notice that the FNSKU label they placed over your label has the X in the front. This indicates that the manufacturer UPC cannot be used for this particular ASIN due to issues that have occurred with the UPC and other sellers. (I am assuming that your inventory settings are set for commingled inventory and you are sending with UPC barcodes) The X code separates your inventory from being commingled. Thus, if your label was the UPC, or the ASIN the FC receiving associated had no choice but to relabel this particular SKU.
If a majority of the re-labels start with X then that would be the reason for the high number of re-labels. The only way around that is to re-label yourself with the correct X label before sending to the FC
If the relabel starts with B and your product has the UPC barcode there would be no reason for the FC to relabel.
Seller_0cyXK0tcUcfsM
We have had this issue many times with amazon putting the incorrect label directly over the correct label. The only solution we have found is we never ship multiple FNSKU per shipment anymore. We do a separate shipment for each FNKSU. This solved the problem.
Seller_kWlmk7ANEJvB0
We have had the EXACT same problem with one of our SKUs. Glad I’m not the only one as I feel less crazy. It’s been a nightmare. Amazon has already done an investigation once. It’s two products that are similar, but look completely different and the price point is completely different. Amazon relabeled (for no reason - the MUPC was clearly visible) some of the cheaper product with labels for the more expensive one. So customers received a $40 product when they ordered a $160 one. Ugh. I did a removal order of most of the inventory (other than the stuff we just sent in). 2 of the 90 units had this issue. But the issue keeps on going because as a customer returns the item for not being the right item, Amazon sticks the return back into our inventory as “sellable.” I believe the issue happened at IND9, MQJ1, or ONT8.
Amazon Relabeling Properly Labeled Product
So we’ve had a systemic problem that is getting worse.
We ship multiple SKU’s in the same shipment to FBA Warehouse (MDW2 almost exclusively).
Multiple days a week we either get a message from a customer that they have received the wrong item, or we get a message from Amazon that they have created a case to “investigate” an issue or an email that they are closing our listing until we make amendments for customer service issues, which are almost exclusively “Wrong Item Sent”.
Every single time we request pictures, and every picture we receive has a human generated sticker label placed over our properly labeled product. The photo attached shows a small label placed over our properly labeled product. This happens virtually every day.
When we get a message from a customer, we create a case in Seller Central, upload the photo, request a bin check on the incorrect item sent, and Amazon does an investigation. Typically, the result of the bin check is that they have “found defects” and fixed them, “found no defects” or “Found defects” and ask us for which ASIN the items should be labeled.
I’ve spoken countless times (over 50) with various levels of Amazon Seller Support with no success. Some have heard of the problem, and have said that we are doing the correct process by doing a Bin Check. I continually say “how is it possible that Amazon who charges us back for 25.5” sized boxes shipped into their DC’s, takes the time to isolate, print an actual label, adhere it to our product WITHOUT LETTING US KNOW OR CHARGING US but will charge us back and stop us from sending in product if a master carton is “too big” by less than an inch" “You are treating the symptom (bin checking product AFTER the problem has occurred instead of treating the DISEASE as to WHY they are relabeling properly labeled merchandise”
I can only speculate as to WHY this happens - some have said it’s to balance unbalanced counts. Anyway you look at this it’s crazy bad business. It costs a ton to relabel this merchandise. Customers 100% will get the WRONG PRODUCT when it is ordered, resulting in a huge return rate.
Does ANYONE have a solution here. I want the relabeling to stop. The only solution I can think of is to only send the SAME SKU in with each shipment, which is unrealistic for us (and should have to be)
Amazon Relabeling Properly Labeled Product
So we’ve had a systemic problem that is getting worse.
We ship multiple SKU’s in the same shipment to FBA Warehouse (MDW2 almost exclusively).
Multiple days a week we either get a message from a customer that they have received the wrong item, or we get a message from Amazon that they have created a case to “investigate” an issue or an email that they are closing our listing until we make amendments for customer service issues, which are almost exclusively “Wrong Item Sent”.
Every single time we request pictures, and every picture we receive has a human generated sticker label placed over our properly labeled product. The photo attached shows a small label placed over our properly labeled product. This happens virtually every day.
When we get a message from a customer, we create a case in Seller Central, upload the photo, request a bin check on the incorrect item sent, and Amazon does an investigation. Typically, the result of the bin check is that they have “found defects” and fixed them, “found no defects” or “Found defects” and ask us for which ASIN the items should be labeled.
I’ve spoken countless times (over 50) with various levels of Amazon Seller Support with no success. Some have heard of the problem, and have said that we are doing the correct process by doing a Bin Check. I continually say “how is it possible that Amazon who charges us back for 25.5” sized boxes shipped into their DC’s, takes the time to isolate, print an actual label, adhere it to our product WITHOUT LETTING US KNOW OR CHARGING US but will charge us back and stop us from sending in product if a master carton is “too big” by less than an inch" “You are treating the symptom (bin checking product AFTER the problem has occurred instead of treating the DISEASE as to WHY they are relabeling properly labeled merchandise”
I can only speculate as to WHY this happens - some have said it’s to balance unbalanced counts. Anyway you look at this it’s crazy bad business. It costs a ton to relabel this merchandise. Customers 100% will get the WRONG PRODUCT when it is ordered, resulting in a huge return rate.
Does ANYONE have a solution here. I want the relabeling to stop. The only solution I can think of is to only send the SAME SKU in with each shipment, which is unrealistic for us (and should have to be)
11 replies
11 replies
Seller_rpwxjC95NIJjm
If amazon cant scan the product, they search it up on the computer. As I can see, they labeled a different product, with the same brand. So they were being lazy.
Seller_d6BEjE7OOvMnp
Anyone else have this issue? Anyone have an answer. We have this problem with lots of our SKU’s
Seller_4XTCqF7P1oC7V
We have had the same issue and try to mitigate with several workarounds, but it still happens, just not as much.
I notice that the FNSKU label they placed over your label has the X in the front. This indicates that the manufacturer UPC cannot be used for this particular ASIN due to issues that have occurred with the UPC and other sellers. (I am assuming that your inventory settings are set for commingled inventory and you are sending with UPC barcodes) The X code separates your inventory from being commingled. Thus, if your label was the UPC, or the ASIN the FC receiving associated had no choice but to relabel this particular SKU.
If a majority of the re-labels start with X then that would be the reason for the high number of re-labels. The only way around that is to re-label yourself with the correct X label before sending to the FC
If the relabel starts with B and your product has the UPC barcode there would be no reason for the FC to relabel.
Seller_0cyXK0tcUcfsM
We have had this issue many times with amazon putting the incorrect label directly over the correct label. The only solution we have found is we never ship multiple FNSKU per shipment anymore. We do a separate shipment for each FNKSU. This solved the problem.
Seller_kWlmk7ANEJvB0
We have had the EXACT same problem with one of our SKUs. Glad I’m not the only one as I feel less crazy. It’s been a nightmare. Amazon has already done an investigation once. It’s two products that are similar, but look completely different and the price point is completely different. Amazon relabeled (for no reason - the MUPC was clearly visible) some of the cheaper product with labels for the more expensive one. So customers received a $40 product when they ordered a $160 one. Ugh. I did a removal order of most of the inventory (other than the stuff we just sent in). 2 of the 90 units had this issue. But the issue keeps on going because as a customer returns the item for not being the right item, Amazon sticks the return back into our inventory as “sellable.” I believe the issue happened at IND9, MQJ1, or ONT8.
Seller_rpwxjC95NIJjm
If amazon cant scan the product, they search it up on the computer. As I can see, they labeled a different product, with the same brand. So they were being lazy.
Seller_rpwxjC95NIJjm
If amazon cant scan the product, they search it up on the computer. As I can see, they labeled a different product, with the same brand. So they were being lazy.
Seller_d6BEjE7OOvMnp
Anyone else have this issue? Anyone have an answer. We have this problem with lots of our SKU’s
Seller_d6BEjE7OOvMnp
Anyone else have this issue? Anyone have an answer. We have this problem with lots of our SKU’s
Seller_4XTCqF7P1oC7V
We have had the same issue and try to mitigate with several workarounds, but it still happens, just not as much.
I notice that the FNSKU label they placed over your label has the X in the front. This indicates that the manufacturer UPC cannot be used for this particular ASIN due to issues that have occurred with the UPC and other sellers. (I am assuming that your inventory settings are set for commingled inventory and you are sending with UPC barcodes) The X code separates your inventory from being commingled. Thus, if your label was the UPC, or the ASIN the FC receiving associated had no choice but to relabel this particular SKU.
If a majority of the re-labels start with X then that would be the reason for the high number of re-labels. The only way around that is to re-label yourself with the correct X label before sending to the FC
If the relabel starts with B and your product has the UPC barcode there would be no reason for the FC to relabel.
Seller_4XTCqF7P1oC7V
We have had the same issue and try to mitigate with several workarounds, but it still happens, just not as much.
I notice that the FNSKU label they placed over your label has the X in the front. This indicates that the manufacturer UPC cannot be used for this particular ASIN due to issues that have occurred with the UPC and other sellers. (I am assuming that your inventory settings are set for commingled inventory and you are sending with UPC barcodes) The X code separates your inventory from being commingled. Thus, if your label was the UPC, or the ASIN the FC receiving associated had no choice but to relabel this particular SKU.
If a majority of the re-labels start with X then that would be the reason for the high number of re-labels. The only way around that is to re-label yourself with the correct X label before sending to the FC
If the relabel starts with B and your product has the UPC barcode there would be no reason for the FC to relabel.
Seller_0cyXK0tcUcfsM
We have had this issue many times with amazon putting the incorrect label directly over the correct label. The only solution we have found is we never ship multiple FNSKU per shipment anymore. We do a separate shipment for each FNKSU. This solved the problem.
Seller_0cyXK0tcUcfsM
We have had this issue many times with amazon putting the incorrect label directly over the correct label. The only solution we have found is we never ship multiple FNSKU per shipment anymore. We do a separate shipment for each FNKSU. This solved the problem.
Seller_kWlmk7ANEJvB0
We have had the EXACT same problem with one of our SKUs. Glad I’m not the only one as I feel less crazy. It’s been a nightmare. Amazon has already done an investigation once. It’s two products that are similar, but look completely different and the price point is completely different. Amazon relabeled (for no reason - the MUPC was clearly visible) some of the cheaper product with labels for the more expensive one. So customers received a $40 product when they ordered a $160 one. Ugh. I did a removal order of most of the inventory (other than the stuff we just sent in). 2 of the 90 units had this issue. But the issue keeps on going because as a customer returns the item for not being the right item, Amazon sticks the return back into our inventory as “sellable.” I believe the issue happened at IND9, MQJ1, or ONT8.
Seller_kWlmk7ANEJvB0
We have had the EXACT same problem with one of our SKUs. Glad I’m not the only one as I feel less crazy. It’s been a nightmare. Amazon has already done an investigation once. It’s two products that are similar, but look completely different and the price point is completely different. Amazon relabeled (for no reason - the MUPC was clearly visible) some of the cheaper product with labels for the more expensive one. So customers received a $40 product when they ordered a $160 one. Ugh. I did a removal order of most of the inventory (other than the stuff we just sent in). 2 of the 90 units had this issue. But the issue keeps on going because as a customer returns the item for not being the right item, Amazon sticks the return back into our inventory as “sellable.” I believe the issue happened at IND9, MQJ1, or ONT8.
