Project Detail

Description

First the bug fix: Virtuemart allows you to create a range of quantities for the price so that you can set 1 - 100 items for $3 and 101-200 items for $2 each. At the moment when our client does this the Ajax update does not pick up the second range so that the 101-200 still continues to be charged at $3 each. We need to fix this so that when they do add another range in any product the ajax update picks up.

Now the work:

1. Virtuemart has a system where the user defines order quantity with a minimum - maximum range (for example minimum purchase quantity of a product: 5 and maximum purchase quantity 20) and a step amount which determines the values which will populate the drop-down list: so that is the minimum quantity is 10 and the maximum 20 and the step amount is 5 the drop down list is populated automatically: 10-15-20. The client wants to be able to manually define these quantities so there is no automatic calculation so he wants, for example to be able to have the option to manually populate the drop down list himself with values he chooses so there is no step amount.

2. Need to program the ability to add an attribute which will work on the products in terms of range of quantity but adds a flat cost which can be pre-set at the final cost and not each individual product. Let me explain this a little more. At the moment every attribute works on the quantity so if you have an attribute with the value of $3 it is multiplied by the quantity you are purchasing (like 100 items) and appears at the end. The client wants to have the ability to do two things: 1. Have an attribute which adds a value to the total amount not the quantity. So this is a flat charge (maybe for processing, or applying some kind of binding). 2. He wants to have the ability to specify the cost of this flat charge depending on the quantity. For example he may decide to say that for 1 - 100 pieces the processing cost will be $3 and for 101 - 1000 pieces it will be $2.

3. Finally we need to create an attribute which adds the cost per item as a X value with another attribute and then they apply to a single item. Let me explain this further. At the moment every attribute there is works on single items. The client has some attributes which affect each other. For example, he may have 4-colour printing costing $1 which will then need to be multiplied by the number of pages (4, 8, 12 etc) to give a price which will then be applied to a purchase like 10 booklets. He needs in each product exactly that ability to add an attribute which will work the cost in relation to another attribute and both of these will be specified by him.