Countries
Read only
Best invoice submission practices for self manufactured / private label item w/ authenticty inquiry?
Hi Amazon Sellers! thank you in advance for the help.
- We received a product authenticity complaint (1:900 ASIN sale ratio)
- Our ASIN is a rigid 15" x 15" plate, rated 4.8 stars, that we end-manufacture in house (cut/deburr/polish, add protective film etc) from large generic sheets of various source materials.
- We have our own (Brand: workphlo) the item is created under, and crafted the images and listing. There is no 'other version' of the particular item.
- Our 365-day invoices are plentiful from our supply chain, though logically the source material VENDOR NAMES do not match our end-result (private label) Brand ID, as they are various generic source materials from fabricators etc. For example, if there's a sticker label on the end-product, do we include an invoice from the sticker company? Every piece that came into the end-product?
- Our brand name, matches our store name, and we're the only ones that make this item.
I've heard people say brand creators (when the item says Brand: Your Brand, under the title) have to invoice-themselves transferring from Production to Inventory, in order to show the robot-like Amazon process a Vendor Name matching the Private Label, but surely this is wrong?
What best invoice submission practices / response should be used, with your own branded SKUS?
7 replies
Seller_Qbd0RsfZFEZBY
It is common for the Brand/Manufacturer to be the business entity and the retailer be a DBA of that entity. The Brand/Manufacturer can then invoice the retailer.
Atlas_Amazon
Hello @Seller_zKzU6ewFNhNe0
Thank you for the information provided regarding the concerns with your ASIN. I understand that there is an authenticity concern associated with the product. An authenticity violation will require providing information to show the sourcing such as an invoice or other supply chain documentation.
We would advise on providing the documentation that will show how your supply chain is set up. This could be material invoices that will give our team more insight into your sourcing. Have you attempted to submit anything as of now? Be sure to verify that it does meet the requirements set forth in our responsible sourcing policy.
Please continue to refer to this thread with any questions or updates that you have regarding the concern.
Best,
Atlas
Seller_9Uf78DYSZ2lcW
I have not had to deal with Authenticity but at one point Amazon needed me to prove with invoices that I had sent in product (in order to get reimbursed for lost product in fba.) Since I manufacture the product myself, it isn't like I get an invoice from a supplier for my product (I get raw materials from other suppliers but those invoices are not going to match the products I sell. As in I can't circle an item on the invoice and say it is the ASIN) So I had my "manufacturing division" create an invoice for my "retail division" so that I could send it to Amazon. Seems silly since it is all really just ME but it worked.
You might also use your GS1 registration for the UPC of the product to show it is your product and you are the brand owner. Do you have Brand registry? Maybe you also need to write yourself a letter of authorization to sell your product on Amazon. (This is probably more necessary if the Amazon seller account doesn't 100% match the Trademark holder business name.)
Then again, I don't have brand registry for my products so I'm not totally sure how all that works out but I know I've seen plenty of people posting that Brand registry support isn't very supportive most of the time.
Seller_zxOQqDcuolNFm
We have had 3 product authenticity complaints in a similar situation. When discussing with an Amazon representative on another issue, we were told to send in a letter stating that we are the manufacturer of the product, provide a link to the product on our Web site showing this product, and provide an invoice from our vendor showing sufficient purchase of raw materials to manufacture the volume we sell on Amazon. All three complaints were resolved immediately by this documentation.
Similar Discussions
