inspiran
commented
13 years ago I presume that you only want to limit the jersey number to a customer and not to one order. The customer could want to order multiple batches of the same jersey at different times.
This requirement does not really relate to inventory because the product is not yet manufactured at that time. The check should be ideally done when a product is added to the shopping cart. You would need to store the link between each product group (for which you want to have jersey numbers unique) with the customer and verify if the association is present. I'm not sure this should be in the Vespolina core but we should at least foresee a hook to have this kind of check implemented.
Can you please add this to the Use cases section on our wiki?
There isn't much existing in the way of product attributes at all yet, but I just wanted to throw in one of my use-cases to get a conversation going.
I have products such as team jerseys that can have attributes such as "jersey number" which can only be purchased by one customer, first-come-first-serve style. Notice it's not purchased only once: One customer could buy 4 jersey's with "#10" or just 1 but in either case no other customer (no other Order even) should be able to buy a jersey with that same attribute value. I am wondering on what level this would fall. It's sort of an inventory thing, but it also seems like the idea of an "exclusive attribute value" could exist irrespective of any inventory tracking... thoughts?