AbleCommerce Shopping Cart Software

One of my clients has noticed that she is able to repeat an order even though one or more items in the order have been locked or have purchase disabled. This occurs even if there is only 1 item in the order and it is locked or disabled for purchase.

This presents a major problem if a customer reorders the product and it is no longer available or is locked for some reason. If the order is allowed, the customer must be contacted and told the order is not valid and, if using auth and capture, the payment must be refunded.

Does anybody know how to prevent this behavior or has anybody else run into this problem?

I don't know if anyone has reported it with a repeat of a previous order, but I think someone reported it with items a customer had in the basket that were subsequently changed or made inactive. It sounds like the same problem- contents of basket aren't checked with current product status when basket is old.

This is also a problem is someone places a order and didnt pay for example...so you mark the order as cancelled. Then a month or so later they decide to pay for the order and this will allow the customer to purchase out of stock items etc..

Can somebody from Able Commerce let us know if this is an error or if it is working as designed, please?

Wow that's weird. I just had a customer this weekend who was able to pay for an order that I had cancelled.

My normal procedure is to void the authorization and then cancel the order. The customer logged back into his account, applied new payment information and then waited for the order to ship. Since it was (still) marked as Cancelled, nothing happened on our side - we had no way of knowing he had applied new payment info.

I never thought of that scenario - granted it took 9 months for someone to do it, but still I never thought a customer could do anything to an order once it was marked as cancelled

I don't have any problem with a person paying on a cancelled order, but I do have a problem with the status not being changed to paid when a payment is made. This will result in a rude awakening for both the customer and the merchant.

It appears there needs to be more logic wrapped around the statuses to account for more scenarios such as the paid on a cancel order.

A bug report about reorder and discontinued / locked / unavailable items has already been logged. I am adding another bug about the cancelled order issue.

Cancelled orders could be cancelled for a good reason (suspected fraud?) and we (AC) should not be un-cancelling them automatically. So the customer should not be able to place payment for a cancelled order unless you (the merchant) moves the order out of the cancelled state. (Bug 6840)

Logan,

How would customers make payments on abandoned orders that have been cancelled? I think customers should have that opportunity. Is there another status that we can use for that scenario?

In my opinion, the "Cancelled" status should be somewhat of a hard-code status. Nothing visitor side should be accomplishable on an order with a Cancelled status.

Here's an idea: what about adding a "Locked" checkbox field on the order status table? Then the site admin could decide which statuses are unable to have visitor-side revisions or payments applied to them? Visitor side could be changed to only allow visitor-to-order interaction if the order status "locked" checkbox is false.

Then, I could lock my Cancelled and Fraud statuses but not lock the others. I think that would give me both the flexibility and control needed.

Sounds like a plan to me.

I like the idea as well. The majority of our orders are cancelled for lack of payment. But if the customer gets a 'wild hair' and they want to make payment on a previous order let's make it easy for them. And make sure the status becomes paid after payment.