Allow your customers to enter an offer price for a product that is in your products database.
You can also use it for auction high bidder purchases. This module is similar to our External
Product Purchase module. The difference is that Override Pricing is best suited for products
that are actually in your inventory so the customer sees the product image, description, etc that
they are offering/bidding on. With External Product Purchase, the customer is seeing a generic
product page where they enter the product name, ID, offer/bid price, and weight.
The offer or high bid is entered into the text attribute on the product page. The price in the
basket reflects that customer entered offer/bid price. The order will then continue as normal.
However, you can create a disclaimer that if the offer/bid is not accepted, the order will be
cancelled and payment refunded. Consult with an attorney on the best wording for your
disclaimer as you would not want to be required to sell at their entered price.
The attribute for the override pricing input can also be modified in admin if you are using the
OpenUI. You can select to shorten the input to 10 characters (size) or you can even make it a
hidden input. You can also have regular product attributes on the same product page.
For example, you may want to have an optional auction ID in case the item is going to be
sold in store and/or through auction. The link from the auction win could include the
auction ID and it would also pre-filled when clicked.
There are also some examples
of links and .htaccess re-write rules for making short url links for typical uses of this module in its online install/usage doc.
Limitation: There are some 3rd party modules which change the price in the
basket AFTER the item has already been added to the basket. Most notable are those which
re-do all of the prices if a customer is in a price group but forgot to login at the beginning of shopping. If you are going to get one of those modules, make sure it 1) only changes the
price if the basket price and actual product price are the same (which means no special
actions had been taken on the price when it was put in the basket initially), 2) it does not
make the basket price higher than the current basket price as the Override Price module
which controlled the actual addition of the item to the basket should be the module to
determine the offer/bid price. If you already have a module which makes those sweeping
basket price changes without regard for the module that put the product in the basket, you
may want to contact that module's developer to see if they could add the two simple rules
above to their logic to reduce module conflict.
