11 comments

  • Official comment
    Avatar
    Meg

    Hi there, Michael! 

    I am sorry that you are still running into this. 

    Unfortunately, we have not received any new information or updates from Amazon regarding the wrongly assessed manual processing fees. They know this is an issue within their Send to Amazon workflow, but last official word we received from them regarding a fix was that one was released as of 02/27/23. This is their reply: 

    “Thanks for reaching out. We deployed a fix for this issue on 2/27/23. Could you please advise if you have seen this issue for shipments created after 2/27/23? ...For Sellers who already received incorrect manual processing fees, we are in the process of identifying eligible Sellers to reimburse for incorrect fees.”

    As you are aware, this fix was unsuccessful as sellers have still been assessed these fees since this fix was released over 2 months ago.

    We are still recommending that users reach out to the Seller Support SP API team for assistance recuperating any incorrectly assessed manual processing fees.

    Our support team can provide you with information for specific shipments which were charged these fees which should help you open up a case. Please open a ticket with our support team at support@inventorylab.com with the shipment IDs that were assessed for this fee. 

    We will be on the lookout for a message to our support team from you! 

    Comment actions Permalink
  • Avatar
    Christina

    Hi there, Steven! We haven't gotten any word on this yet from Amazon, though we do know they are investigating this matter in Q4 and will look to fix that bug in their system as soon as they are able.

    I'm sorry that we don't have any updates on whether or not they will be fully refunding those incorrect fees, but we will do our best to keep folks up to date on this as soon as we know more.

    If you'd like to open a case with Amazon for a specific shipment of yours that received a Manual Processing Fee in error, then please submit a ticket to us at support@inventorylab.com with that shipment ID and we'd be glad to provide you with any Selling Partner API data as needed for proof to show their support team.

    0
    Comment actions Permalink
  • Avatar
    Yolande Wakeham

    Amazon stated that that the box-level information feed upload file didn't contain information about what items were in which boxes. I did provide this information in Inventory Lab though so it looks like there was an issue with Inventory Lab syncing with the new Amazon Shipment portal to provide the information. I have tried to contact Inventory Lab about this and they just try and palm it off to Amazon. Neither party wants to admit fault and so it's us sellers who have to bare the cost, as usual.

     

    0
    Comment actions Permalink
  • Avatar
    Zed

    Hey Yolande! I apologize for the difficulties! We've heard back from Amazon that these fees were in fact incorrectly charged on Amazon's end, and any users who have these fees should reach out to Seller Support for additional assistance, so I'm sorry to hear that you've been passed around! I do see you have a ticket in with us, our team will investigate and reach back out via email with any information we might be able to provide directly to help in this situation.

    0
    Comment actions Permalink
  • Avatar
    Yolande Wakeham

    Unfortunately the response email I received from Inventory Lab was just a reiteration of their first palming off of responsibility. 

    0
    Comment actions Permalink
  • Avatar
    Hadi Ossaily

    we have had the same issue. this is happened last month and now this month again. Did anyone have any luck with getting the processing fees back? we have had no luck with that. 

     

    0
    Comment actions Permalink
  • Avatar
    Kelley

    Hi there, Hadi! I'm sorry you've run into this issue with manual processing fees again.

     

    Previously, we were advised that this issue need to be resolved from Amazon's end as the fee was being charged incorrectly through their system.

     

    If you can confirm that you did enter box contents, then you should not have been charged any manual processing fees. If you were charged manual processing fees and shouldn't have been, then you will need to reach out to Seller Support's API team and open a case with them, to see if they can help rectify the situation. Since Amazon is the one who applies the fees, they will be responsible for correcting this issue.

     

    In the meantime, we have opened a case with Seller Support's API team to look into this, just in case we could get some headway into resolving the issue from their end.

     

    Since we do not have direct access to any seller's Amazon Seller account, we would like to ask for a screenshot of the manual processing fees applied to a shipment for a seller who should not have had that fee applied. Please open a ticket with our support team at support@inventorylab.com with the shipment IDs that were assessed for this fee, along with a screenshot of the fees. To obtain this, please navigate to the shipping queue in Seller Central, select "View Shipment" and take a full screenshot of the area where the fees are mentioned, along with the shipment ID visibly.

     

    We'll keep an eye out for a message from you! 

    We still recommend that sellers experiencing this issue reach out to Seller Support and open their own cases as well, as our case with their team is a hopeful failsafe to bring the issue to their attention again. But we will certainly do our best to inform their team of what's going on. :-)

    0
    Comment actions Permalink
  • Avatar
    Michael Gregorio

    Any news from Amazon on this. I keep getting charged the 0.15 for every item and ever shipment since the new work flow started.

     

    0
    Comment actions Permalink
  • Avatar
    John Monferdini

    I have been completely unsuccessful in getting any fees reimbursed. IL continues to tell me that "this is a known issue" and Amazon continues to tell me that they "have corrected the issue." Yet, I am still stuck with MPFs that were incorrectly assessed and neither party is willing to acknowledge their mistake and repay my lost fees. It is moments like this where I lose faith in "doing the right thing because it is the right thing to do." Regardless, I've lost 5-6 hours of my life trying to "prove" something to Amazon's Seller Support that is seemingly unprovable. I hope that you are more successful than myself in getting these charges reversed. Best of luck, Rad

    0
    Comment actions Permalink
  • Avatar
    Christina

    Hello, John!

    I'm so sorry for the runaround treatment that you've been experiencing in regards to getting the Manual Processing Fee issue addressed. It's never our intention to pass off responsibility or to be less helpful than we possibly can be! We completely understand your frustration in not having this handled as quickly as we all would like. 

    If you'd like, you may open a ticket with us at support@inventorylab.com. In it, please mention that you've been charged MPFs erroneously as well as a specific shipment ID within the last 30 days that has been affected by this issue, and we'd be glad to help ensure that everything was transmitted from our system properly. However, past that, it will be upon Amazon to reimburse any improperly-assessed fees as necessary as they are the ones who would have charged the fees. I'm sorry that we cannot directly resolve the issue from our end!

    We'll look out for your email if you'd like to get in touch regarding this.

    0
    Comment actions Permalink
  • Avatar
    Hadi Ossaily

    i have opened so many cases with Amazon for this. they have charged me over $3000 in fees that they refuse to return. I have escalated these cases so many times. They even sent me a message saying that they will reimburse me however after waiting a few weeks they didn't reimburse it. I opened a few other cases letting them know that they didnt reimburse me and at the end the told me they wont reimburse me. What a rabbit hole they sent me through!

    0
    Comment actions Permalink

Please sign in to leave a comment.