Hi folks,
I want to confirm my understanding of some things about the new discount API. It's hard to phrase as a question, so I'll just ask: is all of the following correct? If not, please tell me where I missed the mark.
1. When the store updates the discount status of a shopper, it runs all the discount modules that are assigned to eligible price groups.
2. The store runs the discount modules in order by the Priority settings of the price groups, highest priorities first.
3. Some modules may run more than once, if they are assigned to more than one price group.
4. A module may operate in one of two ways: (A) it can adjust the existing item price, or (B) it can just override the existing price with a new number. Note that the "existing price" may be the product's normal price, or it may be a number that's already been adjusted by discount modules running at a higher priority.
5. So with type-A modules, there's a sort of chain or cascade of discounts, where each module modifies the price that was assigned by its predecessors. But a type-B module can ignore all its predecessors, and set any arbitrary price for the item.
6. This means that the concept of "priority" is a bit fuzzy for type-B modules. The one with the lowest Priority setting will run last; but that means it can override all the others. So the module with the lowest Priority may actually be the one that controls the item's price.
Yes? No? Some of both?
Thanks --
I want to confirm my understanding of some things about the new discount API. It's hard to phrase as a question, so I'll just ask: is all of the following correct? If not, please tell me where I missed the mark.
1. When the store updates the discount status of a shopper, it runs all the discount modules that are assigned to eligible price groups.
2. The store runs the discount modules in order by the Priority settings of the price groups, highest priorities first.
3. Some modules may run more than once, if they are assigned to more than one price group.
4. A module may operate in one of two ways: (A) it can adjust the existing item price, or (B) it can just override the existing price with a new number. Note that the "existing price" may be the product's normal price, or it may be a number that's already been adjusted by discount modules running at a higher priority.
5. So with type-A modules, there's a sort of chain or cascade of discounts, where each module modifies the price that was assigned by its predecessors. But a type-B module can ignore all its predecessors, and set any arbitrary price for the item.
6. This means that the concept of "priority" is a bit fuzzy for type-B modules. The one with the lowest Priority setting will run last; but that means it can override all the others. So the module with the lowest Priority may actually be the one that controls the item's price.
Yes? No? Some of both?
Thanks --