Items marked hidden and disabled for purchase still sold

[WylieE]

We've had several instances of customers buying items that have been marked hidden *and* disabled for purchase. Our admin staff is frustrated as we've oversold a few items and are wanting to know how this could happen?

My best guess is the items were already in a customer's basket. I've managed to recreate this scenario by adding an item to my cart, disabling the item and checking out. This seems like a good sized bug.

Does AC do any checking of items in a basket against inventory/purchase status during checkout? Our admin staff enable and disable items on a regular basis. This could turn in to a larger problem.


Thanks,

[compunerdy]

You have to mark them with a visibility of private..

I know, it didnt make sense to me when I had this same issue either.

Although Private marked items can still be purchased as part of a kit.

[WylieE]

That doesn't make sense. I've tested it and it works, but it still doesn't make sense. Does disable purchase *only* control the appearance of a buy button?

On a related thought, we are not currently managing inventory through AC. If we enable inventory management, what happens if a customer adds an item to their basket, we run out of stock and the customer attempts to check out? Would that keep the customer from checking out?

[compunerdy]

I know..and yes that is only to remove the button I was told.

It would give them a error message. But I do still get items that go negative once in awhile but I cannot figure out how or why as we still have no audit trail system.

[WylieE]

Our admin staff is complaining that several of the items they have marked disabled and private have recently been sold on our site. For one product in particular, I double checked their work and confirmed the item had been disabled/private.

There are only two staff members that change inventory status information and both swear they did not make any change. Both are highly efficient and reliable. (Yes, I know we're all human.)

Data doesn't just change on its own. We have inventory management turned off. Are there any other processes that could alter inventory status information. Data corruption???

[Logan Rhodehamel]

Can you post what version of AbleCommerce you had this trouble with?

[WylieE]

That would help, wouldn't it?

Code: Select all

PLATFORM: ASP.NET
VERSION: 7.0.3
BUILD: 12458
MSSQL v2005
AC SCHEMA v2005

AjaxControlToolkit: 1.0.20229.20821
AxInterop.ZRush_ShipRush5: 1.0.0.0
CommerceBuilder: 7.3.12065.0
CommerceBuilder.AbleCommerceTax: 7.3.12396.0
CommerceBuilder.AcTestProvider: 1.0.0.0
CommerceBuilder.AustraliaPost: 7.1.0.0
CommerceBuilder.AuthorizeNet: 7.0.9764.0
CommerceBuilder.BankOfCanada: 7.3.0.0
CommerceBuilder.CanadaPost: 7.0.0.0
CommerceBuilder.Configuration: 7.3.12065.0
CommerceBuilder.CyberSource: 7.0.9310.0
CommerceBuilder.Data: 7.3.12065.0
CommerceBuilder.DataClient.Api: 7.0.3.1
CommerceBuilder.DataClient.Csv: 7.0.34.0
CommerceBuilder.DHLInternational: 7.2.11307.0
CommerceBuilder.ECB: 7.0.0.0
CommerceBuilder.FedEx: 7.0.9725.0
CommerceBuilder.GoogleCheckout: 7.0.10052.0
CommerceBuilder.InternetSecure: 7.0.9764.0
CommerceBuilder.LinkPoint: 7.0.9764.0
CommerceBuilder.Paradata: 7.0.9764.0
CommerceBuilder.PayFlowPro: 7.0.10061.0
CommerceBuilder.PayJunction: 7.2.11284.0
CommerceBuilder.PayPal: 7.3.12238.0
CommerceBuilder.Protx: 7.3.12327.0
CommerceBuilder.Services: 7.3.12065.0
CommerceBuilder.SkipJack: 7.0.9764.0
CommerceBuilder.UPS: 7.0.10041.0
CommerceBuilder.USPS: 7.0.9728.0
CommerceBuilder.Web: 7.3.12065.0
ComponentArt.Web.UI: 2008.2.1267.3
ConfiguredItems: 1.0.0.0
CyberSource.Base: 2.0.0.0
CyberSource.Clients: 5.0.2.0
CyberSource.Clients.XmlSerializers: 5.0.2.0
CyberSource.WSSecurity: 2.0.0.0
CybsWSSecurityIOP: 1.0.0.0
DevExpress.Data.v6.3: 6.3.3.0
DevExpress.Utils.v6.3: 6.3.3.0
DevExpress.XtraBars.v6.3: 6.3.3.0
DevExpress.XtraEditors.v6.3: 6.3.3.0
DevExpress.XtraGrid.v6.3: 6.3.3.0
edtFTPnet: 1.2.4.0
FredCK.FCKeditorV2: 2.5.2912.21007
ICSharpCode.SharpZipLib: 0.85.5.452
Interop.ZRush_ShipRush5: 1.0.0.0
LinkPointTransaction: 1.0.1797.29766
log4net: 1.2.10.0
MAX.USPS: 1.0.0.0
Microsoft.Practices.EnterpriseLibrary.Common: 2.0.0.0
Microsoft.Practices.EnterpriseLibrary.Data: 2.0.0.0
Microsoft.Practices.ObjectBuilder: 1.0.51205.0
Microsoft.Web.Preview: 1.2.61025.0
nStuff.UpdateControls: 1.2.0.0
NVelocity: 7.2.0.0
PaygatewayNET: 3.0.0.0
paypal_base: 4.2.1.0
PFProCOMLib: 1.0.0.0
PFProdotNET: 0.0.0.0
skmMenu: 2.2.2991.25093
UPSOnlineInterface: 1.0.0.0
UsaEpay: 1.0.0.0
USAePayAPI: 1.5.2818.15473
Validators: 1.0.0.0
WarmothBody: 1.0.0.0
WebChart: 1.1.1.6
wwHoverPanel: 1.85.0.0

[WylieE]

Bump. Anyone ever encounter this scenario?

[AbleMods]

I've never seen it happen, although there are a number of reasons that make it possible:

1. Item was in a Wishlist before it was marked as prohibit purchase.
2. Item was in a basket before it was marked as prohibit purchase.
3. Customized add-to-cart code somewhere in the storefront that doesn't respect the prohibit purchase flag like the Able code does.

[WylieE]

I've never seen it happen, although there are a number of reasons that make it possible:

1. Item was in a Wishlist before it was marked as prohibit purchase.
2. Item was in a basket before it was marked as prohibit purchase.
3. Customized add-to-cart code somewhere in the storefront that doesn't respect the prohibit purchase flag like the Able code does.

Thanks for the response.

I recall doing some testing and IIRC, items that have been marked Private should be pulled out of the cart during checkout. That *should* eliminate options 1 & 2.

[AbleMods]

Ok let's back up a sec. Are you seeing items marked as private being purchased or items marked as disable-purchase being purchased?

[WylieE]

Ok let's back up a sec. Are you seeing items marked as private being purchased or items marked as disable-purchase being purchased?

Items marked disable *and* private. It is my understanding this should prohibit any purchase, yet we've had a couple items go through.

At this point, the staff are adamantely swearing up and down they properly marked the items and saved their changes. I've even double checked their work.

[compunerdy]

It is the same for me having items sell and go negative inventory. Somehow there is a way for people to bypass the safety measures..I just cant figure out how. People generally say the items where in their wishlists but every time I try and add a item to a wishlist and then buy it when it is out of stock the system catches it. So how are some people getting past the checks?? I dunno.

[paularonw]

We are still having this problem. We diligently manage our store to ensure that any item that is Out of Stock we mark the item PRIVATE and the inventory level is set to 0. So far, we have not been checking "disable purchase", but we will start.

This problem has persisted since we started using Able Commerce, any more comments on how/why this could happen?

We use the following version:
PLATFORM: ASP.NET
VERSION: 7.0.3
BUILD: 12458
MSSQL v2008
AC SCHEMA v2005

[Shopping Cart Admin]

Hello,

Another way this can happen. If you have order inventory status set to de-stock on Order Paid rather than Payment Authorized, this can happen.
This is the most common scenario, there are other order status setting which could make this happen.

e.g. Three people order the same thing BEFORE order number one or two have been 'de-stocked'.

[paularonw]

We destock on Payment Pending, Shipment Pending and Completed Orders...

Name Report Cancelled Stock Triggers
Payment Pending X Destock Order Placed
Shipment Pending X Destock Order Paid
Completed X Destock Order Shipped
Order Paid No Shipments
Problem Restock Payment Authorization Failed
Payment Capture Failed
Cancelled X Restock Order Cancelled
Fraud X None

Anything you see from this set-up to cause problems?

[Shopping Cart Admin]

Howdy,

De-stock will only happen once, so having it on so many just makes it kida confusing. When do you get a payment pending status? I'm not sure that's a useful status to de-stock on. re-stock on auth failed also doesn't 'seem' useful. I don't even see 'Payment Authorized'?

[paularonw]

Here is better look at current config (attached).

[paularonw]

So you suggest just Destock once. I'd like to do it as early as possible then and go with Order Placed, then Restock when Problem (list payment Authorization Failed or Payment Capture Failed). Does that make sense?

[WylieE]

We disable purchase but do not mark it as private. If the part is already in the customer's basket, they can check out. To avoid this, we search for and remove out of stock items from BasketItems. Fortunately, we manufacture most of the items we sell, so we're rarely out of stock.

[paularonw]

Putting the configuration of order statuses aside, this issue is happening AFTER we've set the inventory to Zero and AFTER we've set the Item to "Private".

This issue actually has nothing to do with the point when the inventory is destocked. We are already at Zero stock, with a Private item and an order is still placed. The inventory goes to -1 (negative 1).

No, we do not allow Backorders.

How do you suppose this is happening?

[paularonw]

We disable purchase but do not mark it as private. If the part is already in the customer's basket, they can check out. To avoid this, we search for and remove out of stock items from BasketItems. Fortunately, we manufacture most of the items we sell, so we're rarely out of stock.

WylieE... How do you search BasketItems? This might be a good step for us to include. We will also "Disable from Purchase" as an extra measure.

[hassonmike]

To avoid this, we search for and remove out of stock items from BasketItems.

How does one go about doing this?