Page 1 of 1

Our customers are still being over charged

Posted: Sat Nov 07, 2020 10:40 pm
by Lfrailey173
Some of our customers are still being over charged.

Can you please check order #55574 for buyer #17390. The AllPro system removed the quantity 5% discount on the fruit leather and the free shipping the customer qualified for after he clicked checkout, the $13.80 was added back in. The exact same thing happened to this same customer back in July.

Today buyer #31855 called unhappy that they received their bank statement and were over charged on order #55228. Their order qualified for free shipping however after clicking place order the shipping fee was added back into their total and they were charged $87.80 instead of $81

We have refunded both these customers.

We also contacted you via the support Monday morning Nov 2nd when order #55574 was brought to our attention from the customer. As as of today (Saturday) no one from AllPro support has responded to help us with this issue...our console support would only let us text you on 970-612-1515...someone texted back that "Yes, we will be open for one more hour" and "If you need help, please press the Support button from you AllProWebTools account".... which we did and it only listed the option of text message or forum...both chat and screenshare said "currently unavailable" this was at 8am our time 1pm your time. So we are are now trying the forum since we've still not heard about what you are doing to resolve this over charging issue that is creating a very poor experience for our customers.

Re: Our customers are still being over charged

Posted: Mon Nov 09, 2020 11:42 am
by Kathlein
A Screen Share support will be necessary to assist you with this issue. Here is a video that will help you get access to Screen Share support.

You can learn more about our support policies and available hours here:

Re: Our customers are still being over charged

Posted: Fri Nov 13, 2020 12:48 pm
by Lfrailey173
We did a screenshare on Monday about this and have had no further feedback or follow up on the issue, has it been addressed? resolved? fixed?