A common case would be size. For shirts that are size XXL, you might wish to add a dollar to the price for an item. In that case, you can define a column in the standard pricing database pricing which is named ``XXL''. If a value is found in that column it will be added to the price for the item. Negative numbers result in subtraction if you wish to reduce the price based on an attribute.
Numbers that begin with an equals sign (=) are used as absolute prices -- and are interpolated for MiniVend tags
first, so you can use subroutines to set the price. To facilite
coordination with the subroutine, the session variables item_code and item_quantity are set to the code and quantity of the item being evaluated. They would be
accessed in a global subroutine with $Vend::Session->{item_code}
and $Vend::Session->{item_quantity}.
The pricing information must always come from a database because of security.
See CommonAdjust for another scheme that makes the same adjustment for any item having the attribute -- both schemes cannot be used at the same time. (This is true even if you were to change the value of $Vend::Cfg->{CommonAdjust} in a subroutine -- the pricing algorithm is built at catalog startup.)
PriceAdjustment size
Can be set in the Locale settings to allow different price adjustment fields for different currencies (MV3.07 and up).