Found 350 Modules or Applications that might fit the bill
Use caution when considering any modules from modStop. Their support has been reported by umpteen Miva Merchant users as suspect and worse. Some of their modules are simple and shouldn't require support. Please contact us with any questions concerning them or their modules.
This module allows you to automatically include attribute or option price information in the attribute prompt shown when adding a product to your basket. These prices are dynamically generated based on any price groups, discounts, currency formatting (including conversions using our CurrencyTrk module) or other dynamic changes the shopper may be affected by. It also simplifies administration - if you hard-code price information into attribute prompts, not only will it not change based on the shopper's currency settings, price groups, etc., but if you have a price change you will need to update the price in two separate places for each attribute or option. With this module all price displays are updated automatically.
Admin configuration options allow you to specify the format of the display using special tokens for the original prompt and the attribute/option price. Each different attribute type (Radio Buttons, Checkboxes, etc) can have different display formatting settings for both attributes with a price, and those without (free attributes).
The NetPush Advanced Inventory Module allows Miva Merchant store owners to track inventory within Miva Merchant all the way down to the attribute/option level. The module has numerous configuration settings that should allow the admin to display and track any simple or complex inventory configuration. Inventory levels are only adjusted at checkout time so there is no need to worry about old baskets causing inventory problems. The module comes with an import and export module that allows administrators to easily update inventory levels by using csv files.
We suggest using template modules like Viking Coder's Product Templates and
Category Templates if you want better control of the look and feel of your pages with regards to inventory. This will allow you to use tokens for display. Otherwise, you will have to settle for built in hook point displays that are built into the module and are configurable through the administration area.
The Advanced Inventory Module will send email when stock goes below certain configurable low stock level and can disable products when stock goes below the out of stock level. Administrators can also customize every message shown to the user. Fine grain customizations are made easy because the module allows product level configuration settings the ability to override global inventory configuration settings. This allows Miva Merchant Administrators the ability to customize inventory configurations for every product, if he or she wishes.
Notes:
OpenUI Tokens This module can be used with OUI OpenTokens. To use the module with Viking Coders template modules, see the OpenToken instructions and examples in the documentation on the NetPush.com site.
Product Upsell This module does not show stock information on the product upsell screens at this time. Stock is still tracked in the basket and checkout, but no current stock level is shown on the upsell screens during checkout unless you are using alternatives like tokens in templates.
Basket Redirect and Error Message The user is automatically redirected to the basket screen if he or she adds items to the basket that makes the product go out of stock or if the product is already out of stock. The error message is shown above the basket screen using a hook point in the Open UI. The message is configurable in the admin area.
Checkout Screen Error If configuration is setup to do so, the module will block a user from checking out if their basket has an item that is out of stock. This message is shown automatically at the top of the screen. The message is configurable in the admin area.
Pipes ( | ) Product codes, attribute codes, and option codes must not contain the pipe character. NetPush Advanced Inventory uses the pipe to delimit for lookups. Pipes in your codes will cause the module not to work correctly.
Requirements:
Open UI 4.723+ This module requires that you have OpenUI installed in your store. The module uses hook points in the OpenUI. You must have OpenUI version 4.723 or higher if you plan to use the OpenToken functionality available in this module. Please see the OpenUIsite for information about latest versions and bug fixes.
Miva Empressa 3.96+ This module requires that you have Miva Empressa 3.96 or higher. The module uses functionality that is only available in newer versions of the Empressa Engine. Miva regularly releases new versions of Miva Empressa and the Virtual Machine to add new functionality and fix bugs. If you are on an older version, consider contacting your hosting company. You can find the Miva Empressa version at the top left hand of your Store Administrator when you first login. It should show your Miva Merchant version and your Miva Empressa version.
Miva Merchant 2.x, 3.x, and 4.x This module should work with most versions of Miva Merchant. In order to use the deactivate product option, you must be on version 3.0+. All testing and development was done on versions 4.13+.
Global Configuration Screen
All inventory settings will use the global configuration settings found in the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. One may override these settings for products (see product level settings below). Each product must also be manually turned on before tracking starts. See product settings below.
Configuration Settings
Use NetPush Inventory You must set this to "Yes" if you want the module to be turned on. If this is set to "No", the module will not do anything.
Amount considered out of stock Usually this would be 0, but it can be set to any number, including negative numbers. Once the stock level reaches this number, it will be considered out of stock.
Deactivate when product level is out of stock In Miva Merchant versions that support it, the module will turn the Active flag for a product to off, if the product reaches the out of stock level. This only works on the product level, not for the attribute/option level.
Allow purchase even after out of stock Turning this on will allow customers to purchase products even after they go below the out of stock level. This could be a backorder situation.
Automatically remove from basket When a user adds products to the basket, the products will be removed if it makes the inventory go below the out of stock level and the admin is not allowing purchases when products are out of stock. Please take note that this option could cause problems if other modules are installed that also act on the basket.
Send Low Inventory Notices Turn this on to receive email warnings when inventory goes below the low inventory level.
Amount considered low The level that is considered low. Use this setting to trigger emails that will warn you when inventory is hitting a low level.
Low Email To Address Set this to the email address of the person who should be receiving emails when stock is at a low level.
Low Email From Address Set this to the email address that should be set as the from address in low stock emails.
Low Email Subject The subject of the low stock email. This field has token replacement.*
Low Email Body This is the body of the low stock email. This field has token replacement.*
Automatically change stock levels Turn this on if you want the system to subtract stock when a user purchases. If this is set to "No", the system will not update stock levels.
Show out of stock messages Turn this on to show out of stock messages on the product page when stock goes below the out of stock level.
Show in stock messages Turn this on to show how much stock is left on the product page.
Out of Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
In Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
Other Messages*
Out of Stock - Basket Line Marker This helps the user to see which products have gone out of stock when looking at the basket. A red asterisks may be a good indicator for the user.
Out of Stock - Basket This message is shown to the user above the basket when a product has gone out of stock when adding, updating, or looking at the basket. Products can go out of stock at anytime, even after a user adds it to their basket. This is because stock levels only change after checkout.
Out of Stock - Checkout This message is similar to the out of stock basket message. It is shown on the payment screen during checkout. This should be considered one final inventory check before allowing the user to purchase.
* Token Replacement This module has a few built in tokens for messages that allow you to give yourself and the user more detailed information. Some of the tokens below can only be used on certain screens, or in emails.
%%stock%% - Displays the current stock level. (1,2,3) %%basket_quantity%% - Displays the amount in the basket and is unlikely to be used. (1,2) %%available%% - Displays the amount of stock left before hitting the out of stock level. (1,2,3) %%oos_level%% - Displays the out of stock level. (1,2,3) %%line_items%% - Displays a list of line items that are effected. (1,2) %%product_id%% - Displays the product id. (1,2,3) '%%product_code%% - Displays the product code. (1,2,3) %%product_name%% - Displays the product name if available. (3) %%attribute_code%% - Displays the attribute code, or None if the effected product is only being tracked at the product level. (1,2) %%option_code%% - Displays the option code, or None if the affected product is only being tracked at the product level. (1,2)
1. Is used for the low stock email body and subject 2. Is used for the out of stock basket message and out of stock checkout message 3. Is used for the in stock and out of stock messages on the product pages.
Product Configuration Screen
All inventory settings will use the global configuration settings found in
the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. To override these settings at the product level, go to the product in the administration area and click on "NetPush Advanced Inventory". You will see the settings below.
Configuration Settings
Use NP Inventory on this Product You must set this to "Yes" if you want to track inventory on the product. You must manually set this to "Yes" for every product that you want to track. If this is not set to "Yes", no inventory tracking will take place. By default, no product is tracked.
Override Global Settings If this is set to "Yes" the configurations settings will be taken from the individual product screen instead of from the Global configuration settings found under under system extension configuration. If set to "No", the module will use the global settings from above when doing inventory for the product. The default is to use the global settings.
Amount considered out of stock Overrides same setting under Global Configuration.
Deactivate when product level is out of stock Overrides same setting under Global Configuration.
Allow purchase even after out of stock Overrides same setting under Global Configuration.
Automatically remove from basket Overrides same setting under Global Configuration.
Send Low Inventory Notices Overrides same setting under Global Configuration.
Amount considered low Overrides same setting under Global Configuration.
Low Email To Address Overrides same setting under Global Configuration.
Low Email From Address Overrides same setting under Global Configuration.
Low Email Subject Overrides same setting under Global Configuration.
Low Email Body Overrides same setting under Global Configuration.
Automatically change stock levels Overrides same setting under Global Configuration.
Show out of stock messages Overrides same setting under Global Configuration.
Show in stock messages Overrides same setting under Global Configuration.
Out of Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
In Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
Other Messages*
Out of Stock - Basket Line Marker Overrides same setting under Global Configuration.
Out of Stock - Basket Overrides same setting under Global Configuration.
Out of Stock - Checkout Overrides same setting under Global Configuration.
Setting Product Inventory Levels
The administrator can set product inventory levels by going to the product page within the Miva Merchant admin area and clicking on NetPush Advanced Inventory. This is the same screen as the product level configuration. Product inventory levels are shown below the configuration area. To add new inventory, use the yellow add button. To edit inventory, click white add button next to the inventory entry.
The module checks inventory by looking at a unique combination of Product Code, Attribute Code, and Option Code. When entering stock levels, you enter the codes separated by a pipe. For example, shirt1|color|red, where shirt1 is the product code, color is the attribute code, and red is the option code. If you do not set an inventory level for an existing product attribute combination, no tracking is done. Setting a stock level of -9999 has the same effect.
Inventory at a product level You may choose to only track inventory at a product level in combination with or not at an attribute level. To enter a stock level for a product, simply use prodcode||. This tells the system that you are tracking the product code, but not the attributes or options by leaving them blank. Using -9999 for a stock level will temporarily turn inventory tracking off.
Inventory at the attribute level (checkbox, select box, radio buttons) Checkbox - prodcode|attrcode|(the last field should be left blank, as checkboxes have no options) Select Box and Radio Buttons - prodcode|attrcode|optcodeAll 3 are required and must be unique, even if you are using attribute templates. If you are using normal templates in combination with attribute templates, make sure you do not give them duplicate code names.
Using Advanced Inventory with Template Modules and OpenTokens
The Advanced Inventory Module can be used with 3rd party template modules like the ones from Viking Coders by using Open UI tokens on product pages to display current inventory levels. Please note that token support has not been completely tested as of yet.
%module|npinventory|stock_level% Returns the stock level for the product, attribute, option combination. To ensure that this works correctly, you should set g.NPI_Product_Code, g.NPI_Attribute_Code, and g.NPI_Option_Code to the current product code, attribute code, and option code. On a checkbox, make sure to set g.NPI_Option_Code = ''. On a product level, make sure to set the attribute and option variables to ''. After these globals are set, call the token. If the return value is -9999, the item is not being tracked.
%module|npinventory|stock_available% Same as above but shows the amount available.
%module|npinventory|oos_level% Same as above but shows the out of stock level.
%module|npinventory|stock_list% This token will set a global variable that contains an array of structures. You must set g.NPI_Product_Code equal to the current product code before calling the token. This array contains all of the product code, attribute code, and option code combinations for a specific product. It also contains the available stock, out of stock level, and other information shown below. This token makes it easy to create a stock table using OpenUI tokens in Viking Coders templates or in a product header or footer. Code examples are available in the help pages on the NetPush.com site. Array Structure: g.NP_Inventory_StockList[i]:attribute_code - Attribute Code g.NP_Inventory_StockList[i]:option_code - Option Code g.NP_Inventory_StockList[i]:stock_level - Stock Level g.NP_Inventory_StockList[i]:oos_level - Out of stock level g.NP_Inventory_StockList[i]:available - Stock Level minus out of stock level g.NP_Inventory_StockList[i]:allow_pur - Allow purchases even if out of stock from admin settings g.NP_Inventory_StockList[i]:low_amount - Low amount from admin settings g.NP_Inventory_StockListLen - Variable that tells you how many items are in the array (represented by i above)
Discount your product base prices based on the number of items ordered of identical products, eg 1-3 = standard price, 4-6 = lower, etc. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Discount product prices based on quantity ordered - Easy from - to price breaks in a single input - Unlimited price break ranges - Fixed price or percentage off regular price - Optional automatic start and stop dates for volume pricing - Use our time zone offset to adjust the time that the date changes - Each product can have different price breaks and dates - Can use price groups with percentage discounts - Optionally apply price group discount "on top of" volume price breaks - Can exclude price groups from volume pricing - Can exclude all except specific price groups - Hide or display table which depicts price breaks - Include a quantity input in the table on category pages - Volume price can be applied on identical products or can amalgamate - Can amalgamate discounts of different attributes in the same product - Optional "as low as" to replace regular price - Optional strike thru of regular price followed by volume price - Can put all or some of your store products on sale within seconds - Can remove all volume pricing in the store within seconds - Flat file import for quick update - Optional wild card can apply same volume pricing to all products - Export volume pricing settings to flat file - Use render tokens to place "as low as" and table on applicable screens - Licensed by domain, unlimited stores under one MIVA Merchant mall pay no additional license fee
Feature Details: This module's admin interface provides an easy to enter "from - to cost" format. You can literally have as many ranges as you want to type in. See the image below for example syntax. You can either use actual values to replace the base price or percent of price to be subtracted from the product base price. These price differentials are added directly in the admin interface under the product edit screen. You only apply these price differentials in the products that you want to use them.
This module applies the price in your low,high, cost groupings. If you do not include a grouping at the single item level, it will use the method for pricing in your store. It onlyactivates if you include a low, high, cost grouping. For example: 6|10|12% 11|20|14% 21|999|16%
The module only uses price groups when using the percentoff discount calculation. If you enter fixed prices for the quantity ranges, then price groups are ignored. Keep in mindthat the percent discounts could be over and above the discountalready given if you are using price groups.
You can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volumepricing and hide the table from them completely. Conversely,you can exclude everybody from volume pricing except specific price group members. Customers must be logged in to identify the price group they are in before the volume pricing module can qualify or disqualify them from volume pricing if you are using the price group restrictions.
The percentage discounting method subtracts the percent discount from the base price. Base price does not include attribute prices. To apply the percentage, simply include the percent symbol (%) in the line. If you are using cost method for your store (other than price groups), you will not be able to use the percentage discounting method. Instead, use the actual value method.
If you are using another third party module which overrides prices in the basket and recomputes them using the price in the product record, youmay not be able to use this module. Other third party modules may notrecognize that it needs to apply the calculations in this module.
The module recognizes identical products. Hence different product codes will change the product enough that the discountwon't apply. For example 3 red shirts and 6 blue shirts willnot give the discount of 9 shirts. Rather, they'll get the discount rate of 3 for one of the line items and 6 for the other.
You can amalgamate quantities so in the example above, as long as the product code is the same and the color variation is done with attributes, all 9 items would get the volume discount for 9 items. You have the option for each product code to amalgamate quantities or treat varied attributes as different products.
You can optionally include a table on the product (PROD) andcategory (CTGY) screens displaying the rates as generatedfrom the products' volume discount record. You can optionallyhave a quantity input in that table display on the category screen. These options areconfigured through admin.
If you want to have a sale on one or moreitems. Simply set the volume to 1 or more with a specific discount percentage and you have a sale with as low as display. You can use the token %product_price_f% to further highlight that witha strike thru. To make this feature even more useful, youcan enter a starting and ending date for the sale so that itwill start and end automatically.
For ease of entry, a flat file import module is included. You can put all product codes in the flat file or use an asterisk (*) and one lineof "rules" to apply the volume price to all products in thestore. Create a storewide sale, e.g. 10% off in seconds with a specific start and stop date. Then just as quickly removeall settings at your leisure after the sale. There is also a volume price export so you can quickly build your flat file, then edit or add to it. This is useful when you want to have a storewide sale on all products butretain volume prices on your regularly discounted items. Export the volume prices. Import your sale settings. Importyour volume discounts on the few you want to maintain at pre-sale prices.
The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server. This would be the case in most of the server setups. For those that are not, we are in the process of converting the code for that remaining, very small group of MIVA Merchant stores. At this time we have not had a problem. Modules will be moved to the top of the queue as needed.
Hide Prices Pending Customer Approval module Tremendously useful for wholesalers and other store owners who want to limit access to a known, and approved, customer base. Product prices can be hidden until a customer's account has been approved by the store's owner. Access to the site can also be restricted, requiring customers to login. Includes an administrative utility for review & approval of customer accounts and assigning of price & availability groups. Fully compatible with OpenUI OpenTokens and third-party template-based modules.
Professional Version Features:
Price & Availability Groups support integrated into utility module - easily select a price & availability group while approving a customer
Require Customers to login - customers can be required to login (or create an account) before being granted access to anywhere in the store or to the product-related pages
OpenUI OpenTokens fully supported
Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Display Attribute-Option prices on Product Display screen
Plus all the features of the Standard Version
Summary of of Standard Version Features:
Multiple modes for hiding prices - prices can be hidden until a account approved or until a customer creates/logs-in to an account.
"Add To Cart" and the "Buy One Now" buttons are also hidden.
Prices & buttons hidden on the Product List, Categories, Search Results, and Product Display screens
Optional, fully-customizable message can be displayed in place of the hidden prices, on the customer accounts screen & on all screens for accounts that are pending approval
Two modules in one - includes a feature-rich administrative utility module for approving and managing customers
"Quick approval" feature for approving new customer accounts
Compatible with compiled Miva Merchant version 4.14 thru 4.2.
OpenUI OpenTokens OpenUI OpenTokens are fully supported.
Template-Based Modules Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Requires OpenUI.
Details
The "Hide Prices Pending Customer Approval" module contains a wealth of functionality and customizable options. It's tremendously useful for wholesalers and other store owners that want to limit access to a known, and approved, customer base.
Product Prices Hidden Product prices can be hidden until a customer's account has been approved by the store's owner. Optionally, prices can be hidden until a customer creates or logs-in to an account (without requiring approval of the account).
Buttons Too The product prices - and the "Add To Cart" and the "Buy One Now" buttons - can be hidden on the Product List, Categories, Search Results, and Product Display screens. An optional, fully-customizable message can be displayed in place of the hidden prices.
Require Customer Login Customers can be required to login (or create a new account) before being granted access to the entire store or to the product-related pages (Product Listing, Categories, Search, Product Display & Basket screens).
For instance - The module can be configured to "Hide Prices Pending Approval of Customer Account" and to "Require Login to View Products".
With this configuration:
Customers could access the storefront but would be prevented from accessing the Product Listing, Categories, Search, Product Display & Basket screens. They could of course also access the Login & Create New Accounts screens.
Once the customer logged in or created a new account, they would then be able to view the Product Listing, Categories, Search & Product Display screens, but the prices would be hidden.
Once the account was approved by the store's administrator, the customer would be able to login and view product prices.
Multiple Levels of Price Display & Access Restriction
Display of Prices:
Hide Prices Pending Approval of Customer Account
Hide Price Unless Customer Has Account
Show Prices - (Disables Module)
Access to Store:
No Login Required to Access Store
Login Required at Storefront
Login Required to View Products
Customer Messages An optional & customizable "Customer Account Pending Approval" message can be displayed just below the Miva Merchant header. An optional & customizable message can also be displayed on the Customer Account & Customer Information screens. This can be used to inform the customer of the store's policy for accessing the product prices.
For example: "Approval of customer account is required. Please complete the customer account form. You will be notified by email when your account is approved."
Two Modules In One It's actually two modules - a OpenUI system module and an administrative utility Module. The system module customizes the store's look and feel and limits access to prices. The administrative utility module provides the store owner with the ability of reviewing and approving customer accounts.
It's also a feature-rich, admin-friendly customer management utility.
Choose the way you approve customer accounts - accounts can now be approved using either the standard Customer admin or the administrative utility module.
Quick Approval of Customer Accounts The Approve Customers administrative utility module also has a "quick approval" feature. A store's administrator can quickly search for a new customer by login, email address, or other keyword - then approve the customer with one click.
Admin-Friendly navigation - Sort Customers by newest, by id, or by login. Search by login, name or other keyword. Easily scroll through customer records, choose how many are displayed per page, go to first or last record, approve, edit or delete records.
Integrated Price & Availability Groups Support The store administrator can also assign customers to a price and/or availability group at the same time that accounts are being approved.
Template-based Merchant Notification of New Accounts An optional email notification can be sent to a specified address whenever a new account is created by a customer. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Template-based Customer Notification of Approved Accounts An optional email notification can be sent to the customer whenever their account is approved. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Display Attribute-Option Prices Attribute & option prices on the product display screen.
Fully customizable attribute-option prompt template gives you complete control over their display
Works with all types of attributes, drop-down menus, radio button, checkboxes, text fields & memo fields
Modifies both the Product Display & Missing Attributes screens
Completely compatible with Miva Merchant price groups
Older Modules Not Available Compiled! No Longer Available!
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #2 includes the abilities to:
Add Agreement Page before Checkout. The checkout button on the navbar and the Buy 1 Now buttons on the Category Screen, Search Screen and Product List calls an agreement page to which the customer has to agree or dissagree. Choosing agree takes you to login/checkout. Not agree takes you back to the storefront. Will display either image or grey button.
Create a horizontal display with no image. Displays Product Name, Description, Retail Price, Discount, Your Price, Weight, and Quantity. Retail price is controled as an adjustable percent of markup over price. Will display either image or grey button.
Add calculated Retail Price and Discount Price on Category Screen. Retail price is controled as an adjustable percent of markup over price.
Add calculated Retail Price and Discount Price on Product Display. Retail price is controled as an adjustable percent of markup over price.
Add calculated Retail Price and Discount Price on Product Display. Retail price displays the Cost Field.
Remove weight from the Product Display if the weight is Zero.
Remove the Place Order Without Account from the login screen and directs the customer to login on initial store access.
Redirect Add 2 Basket on Category Screen and Product Display to return to Product List.
Remove Price from Product Screen.
Move Product Description to Right of Image and Removes Weight from Product Display.
Add the Product Description to the Category Screen just above the addone and buyone Buttons.
Add Category Tree to Login Screen.
Add Category Tree to Search Screen.
Replace Code with hyperlinked Thumbnail on Product List.
Replace Code with hyperlinked Thumbnail on Search Screen.
Make Basket Contents Required Before Checkout on the Category Screen Only. Includes Basket Contents Continue Shopping and Continue Checkout links.
Move all text, attributes, everything below image on Product Display.
Reduce the Attribute Text Box display from 40 to 30 on the Product Display and on the Attribute Screen.
Leave shoppers in Basket Contents when clicking on Add to Basket in Product Display page only.
Create an Alternate Information display on the Category Screen below the Name. Alternate Information is entered in the Product Data Field separated from the Description by a ^. Product Display shows regular description.
Display a different html menu for each button on the Navigation Bar.
Buy Buttons go direct to Checkout on Category Screen and Product Display. No Quantity in Basket, Weight, Attributes or Quantity. Primarily for stores with few products or single purchase type items.
Create a Button Up-Button Down effect. If the alternate button exists it will display for the selected button. If it does not exist the selected button will not display.
Remove Price, Total Price, Shipping Cost and Sales Tax from Category Screen, Product Display, Product List, Basket Contents, Search, Invoice and all Checkout Screens.
Remove price only from the Category Screen.
Remove Add One To Basket and buy One Now buttons from Cagegory Screen, Product Display, Product List, and Search Screen.
Remove Category Tree and replace NavBar with message: Our Mall is temporarily closed for maintenance. Please check back soon.
Remove Price, Quantity and Add to Basket Button on the Product Display Screen if the price is zero. Displays Call for Price instead.
Remove Price, Quantity, Add to Basket and Buy 1 Now Button on the Category Screen if the price is zero. Displays Call for Price instead.
Create a horizontal display of all information and displays more products on screen. Will display either image or grey button.
Add Attributes and Quantity to Category Screen.
Place Click to Print for your Records button at the top of Invoice centered.
All extensions are designed to just Plug AND PLay in OpenUI stores. Designed/Written by Luray Williams.
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
Customers order more, and more frequently when its easy for them to know what the price of a product is going to be. Dynamic Attribute Pricing will do just that, reqardless of how your pricing is assigned. Dynamic Attribute Pricing shows your customers to total price of the product they want to order, even when that product's attributes and options add to or subtract from the initial price.
This module is compatible with OpenUI or Viking Coder's Category Page Templates and Product Page Templates. With OpenUI, a "Total Price: " display appears above the add quantity to basket button. With VikingCoder's Templates, you have place the Total Price: token and add to basket button anywhere you want in the templates. The displayed total changes with option selections that have an associate price increase (decrease) and with the quantity select.
With either OpenUI or Template, the module will automatically add any additional price associated with the option, to the display of the option. For example: Some Option ($2.00).
To control the quantity a customer can order, the module presents a tab in the Add/Edit Product screen. This tab shows the following options:
For example, if you entered 3,6,9,12,15,18, etc, the customer could only order in multiples of 3.
Will also allow image swapping with CPT and PPT! You can display a larger image for attributes where the product image is by including name="PRODImage" with your product image code.
Discount your product prices based on the number
of items ordered of identical products, eg 1-3 =
standard price, 4-6 = lower, etc.
The admin interface provides an easy to enter "from - to cost" format. You can literally have as many ranges as you want to type in. See the image below for example syntax. You can either use actual values or percent of price to be subtracted from the product price. These price differentials are added directly in the admin interface under the product edit screen. You only apply these price differentials in the products that you want to use them.
This module applies the price in your low, high, cost groupings. If you do not include a grouping at the single item level, it will use the method for pricing in your store. It only activates if you include a low, high, cost grouping.
For example: 6|10|12% 11|20|14% 21|999|16%
The module only uses price groups when using the percent off discount calculation. If you enter fixed prices for the quantity ranges, then price groups are ignored. Keep in mind that the percent discounts will be over and above the discount already given if you are using price groups.
In the compiled version you can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volume
pricing and hide the table from them completely. Customers
must be logged in to identify the price group they are in before
the volume pricing module can disqualify them from volume pricing.
The percentage discounting method subtracts the percent discount from the base price. Base price does
not include attribute prices. To apply the percentage,
simply include the percent symbol (%) in the line. If
you are using cost method for your store (other than
price groups), you will not be able to use the percentage
discounting method. Instead, use the actual value method.
If you are using another third party module which overrides prices in the basket and recomputes them using the price in the product record, you will not be able to use this module. Other third party modules will not
recognize that it needs to apply the calculations in this module.
The module recognizes identical products. Hence different attributes will change the product enough that the discount won't apply. For example 3 red shirts and 6 blue shirts will not give the discount of 9 shirts. Rather, they'll get the discount rate of 3 for one of the line items and 6 for the other.
The module for the compiled version of merchant DOES have the ability to amalgamate quantities so in the example above as long as the product code is the same, all 9 items would get the volume discount for 9 items. You have the option for each product code to amalgamate quantities or treat varied attributes as different products.
You can optionally include a table on the product (PROD) and category (CTGY) screens displaying the rates as generated from the products' volume discount record. You can see an example of that with our best seller products. You can optionally have a quantity input in that table display. These options are configured through admin.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the table display on the product page so that it better fits your desired look. New configuration options added for the table display. Also, the ability to display the lowest price in place of the standard price when volume pricing effects the product, the store is using the OpenUI, the store is version 4.14 or higher, and there are no other 3rd party modules effecting the price display. This feature is useful if you want to have a sale on one or more items. Simply set the volume to 1 or more with a specific discount percentage and you have a sale with as low as display. You can use the token %product_price_f% to further highlight that with a strike thru. To make this feature even more useful, you can enter a starting and ending date for the sale so that it will start and end automatically. For ease of entry, a flat file import module is included. You can put all product codes in the flat file or use an asterisk (*) and one line of "rules" to apply the volume price to all products in the store. Create a storewide sale, e.g. 10% off in seconds with a specific start and stop date. Then just as quickly remove all settings at your leisure after the sale. There is also a volume price export so you can
quickly build your flat file, then edit or add to it. This
is useful when you want to have a storewide sale on all products but retain volume prices on your regularly discounted items. Export the volume prices. Import your sale settings. Import your volume discounts on the few you want to maintain at
pre-sale prices. The volume price can also be used in our compiled
Fast Data Feed module for
froogle submissions and our
Static Catalog Generator which creates static html pages for better search engine indexing.
The Categories in Basket Screen module provides enhanced display of your basket screen with: 1) categories the product is in, 2) thumbnail image of the product, and 3) combined prices of products + attributes into a single price for each product.This module is for MIVA Merchant 5.x.We also have the corresponding module for an older version of Merchant.
This module is licensed to one domain.It may be used in more than one store within the same domain without additional licensee fees.
The tokens are added to the 'bask' and 'invc' page templates to implement the features you want to use in this component module.
You can insert the category name directly below the product name in the Basket (BASK) and Invoice (INVC) screens.When a product is in more than one category, the module displays all of them.Each category name is linked to the corresponding category list screen in the Basket Screen.
In addition to categories in the basket, the module also provides the url for the thumbnail image which can be displayed in the basket.The thumbnail display is not in the built-in basket display so this module provides that extra feature.
Also, the module creates a basket price sum variable which can optionally be displayed in the basket and invoice.This price variable combines the product's basket base price with its attribute prices so that you can show the sum total for the product and hide the individual attribute prices in the basket.If you want to allow customers to see the amounts itemized, you can even make a link to the basket screen and pass a parameter that shows the basket with the product and attribute prices separated by using a conditional display.Creating a sum variable which is different from the original display variable was done to prevent potential conflict with other vendor's 3rd party modules.I could have intercepted the price and changed the variable used for regular price display, but that would likely have led to conflicts as more vendors create modules that effect price display in the basket.So instead, you have both variables and can choose which to display.For those who also want to have combined prices in the merchant and customer emails, you can use the Emporium Plus Mail Manager module which has tokens for this purpose.
Take master control of your Product Attributes. This module is packed with features like menu-driven control of MIVA Merchant product attributes. You can control field attributes, prompt/image locations and options, multi-column radio attribute options, and much more. Module features are configurable using the menu-driven admin interface, Product Display Layout, Missing Attributes PATR Page, OUS1 Checkout: Upsell Product (Single) Page and UATR Upsell: Missing Product Attributes (Single) Page templates. These templates are automatically created using your current template versions, when the module is initially installed. Attributes can also be displayed on other product related pages. This gives you master control over the look and feel of your product attributes.
The ADS Attribute Master Module Features:
Simple Module Installation and Configuration
Automatic installation and assignment of PROD, PATR, OUS1 and UATR pages with required item.
Automatic installation and assignment of revised Product Display Layout, Missing Product Attributes, Checkout: Upsell Product (Single) and Upsell: Missing Product Attributes (Single) templates. Current version history templates are used to generate revised templates. Previous template versions will be available through version history.
Menu-driven control of new features. No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
Radio Button Control Features:
Extra Tag Attributes
Attribute Image/Prompt Location
Attribute Image/Prompt Style Wrapper using provided token
Options Image/Label Location
Option Image/Label Style Wrapper using provided tokens
Display Option Price Adder when applicable
Table/Style Attributes
Number of Option Columns
Drop-Down List Control Features
Adds <Select One> at the top of the list
Extra Tag Attributes
Image/Prompt Location
Display Option Price Adder when applicable
Image/Prompt Style Wrapper using provided token
Checkbox Control Features
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided tokens
Display Attribute Price Adder when applicable
Text Field Control Features
Size Attribute
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided token
Display Attribute Price Adder when applicable
Text Area Field Control Features
Cols Attribute
Rows Attribute
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided token
Display Attribute Price Adder when applicable
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with Item "ads-attrmaster", Product Display Layout, Missing Attributes PATR Page, OUS1 Checkout: Upsell Product (Single) Page and UATR Upsell: Missing Product Attributes (Single) Page templates that are pre-installed and configuredwith this module.
Original templates and/or Merchant "Original" templates will not be modified by this module and can be restored, using the new Version history features, at any time.
No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
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.
The ultimate Miva Merchant autoresponder module - send specialized emails at the completion of the order. These emails are in addition to or in place of the standard emails which are sent at order completion, e.g. merchant notification, customer confirmation, vendor specific notification, and even cell phone emails. It also can send welcome emails when a new customer account is created. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Autoresponder - specialized emails at the completion of the order - Merchant notification and customer confirmation - Vendor and product specific templates - Can limit sending based on a specific attribute/option code for a product - Include coupons or promo codes when specific products ordered - Optionally require an input to allow the email, e.g. a response from Addendum - Easy to use checkbox configuration of vertical or horizontal layout emails - Highly configurable free form template layout emails with embedded tokens - HTML or text email formatting - Archive flat file is created for each template, easily track sales activity - Mail Manager Report module can display the flat file contents by time period or product - Ship to, bill to and other email addresses for each template - Send emails to your company's internal departments, e.g. shipping - Emails to web enabled cell phones as abbreviated messages - Open architecture so that other events can also trigger an automated response - Can resend emails when the customer knows and enters their order number and email address - Use render token to send an email from any pagein the store - Send a welcome email before the order completes and optionally include a promo code, customer login and password - Include 3rd party data with module tokens, e.g. Addendum responses - Display shipping and payment invoice messages - Create packing slip and label emails - Ship to country address formatted according to the applicable country's postal recommendations - Restrict email to a specified order dollar value range, reward big spending customers with a coupon - Restrict email to a specified list of countries, thus allowing for language specific emails
Feature Details. In admin, you create one or more template emails. Eachtemplate can be different, i.e. what it displays, how the data is oriented on the screen/paper, and what product(s) triggers the autoresponder. Most responses are triggered by the product codes purchased. Some example uses:
Email to any of your drop-ship manufacturers listing the Ship To address and the products to be shipped if using real time creditcard authorization. The module will sort out which drop shippergets which emails, including listing the products to be shipped. Unlike some other vendors' drop ship notification modules, this one only includesthe products belonging to the associated drop shipper. Thus a drop shipper doesnot see the products being supplied to the customer by other drop shippers when the order contains multiple product sources. Youcan still use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processingverified the charge, then forward to the drop shipper. This would savehand entering the order. In addition to the email, an archive flatfile is created which you can use to easily track sales activity related to each of your drop-ship manufacturers.
Email to Ship To or Bill To or both thanking them for a donation to your sponsored charity on your site.
Email to your shipping department listing Ship To addressand products ordered if using real time credit card authorization. Products section can be cut/folded to result in a shipping label with your company address included. If notusing real time authorization, use the pending mailbox technique similarto the drop shipper scenario above.
Email a promo coupon code if a customer purchases a specificproduct or from a list of products
Email service, warranty, shipping and contact information on specific products or product lines
Send an email to your cell phone's inbox when orders are placed in your store (requires a cell phone plan that assigns an email address to your phone).
You own a mall with multiple stores within the mall. Thosestore owners rent the stores from you for a percentage of their gross. Use mail manager as an audit tool to track theirsales. In addition to the autoresponse email, mail manager produces a flat file with order ID, date, product name, product code, quantity, price for each, and price extended. Periodically retrieve that flat file and import into a spreadsheetfor easy analysis.
The included Mail Manager Report module can display the contents of that flat file through admin. It can filter the report by specific timeperiods (daily, weekly, monthly) within reason. The limits of your PC or server may prevent very lengthy reports for excessively long time periods. It can also limit the report to only one product code. Since the templates canbe designed for each vendor, you can create individual vendor flat files with a corresponding report for each vendor.
Literally, you can have a different autoresponder for everyproduct in your store.
However, Mail Manager has a somewhat open architecture sothat other events can also trigger an automated response. For example:
Send a welcome email before the order completes, but afterthe customer completes the registration process (for those thatcreate an account)
Send a thank you for rating a product (using our Rate This system)along with a coupon code for taking the time to do so
You can use the ifvar script or var token in these "other event" emails. For example, generate a unique coupon code with a module token and insert it in the welcome email to give the new customer an incentive to buy now.
Use a render token to send an email from any page in the store. For example, put it on the product page to send a specific email when a specific product's page is viewed by a customer who is logged in. The email goes to their password recovery address (but could be bill to or ship to address). If you want it sent to a hard coded address, e.g. yours to monitor traffic,you would put your email address in the 3rd parameter of the token. The uses of this feature are endless. Send a coupon to entice customers to buy when they visit specific product screens. Tell them about other products related to the one they just viewed.
As you can see, the uses of this Mail Manager are quite diverse. Some of the variable features configured through admin for each template are:
Show or hide any of the data elements
Orient your email either horizontally or vertically
There is also a free form template using an extensive list of tokens and mini-scripts to customize the emails that are sent at the time of order completion. They can vary from mimics of the standard merchant notification and customer confirmation emails to brief order notifications for better acceptance within cell phone emails. The emails can be plain text or HTML formattedemails for better readability. You can change the fonts, colors,layout and even add images to your confirmation and notificationemails. If your shipping and payment modules are configured withinvoice notices, these can be included in the emails with a token. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create packing slip and label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template. In the free form template you canalso set the time so that it can be offset from the server time,thus display for a different time zone in each of your emails.
Customize your email and store's physical address
Designate email recipient, i.e. Ship To and/or Bill To and/or fixed email address
List full or partial Ship To and/or Bill To address
Restrict email to a specified order dollar value range, reward big spending customers with a coupon for their next visit
Restrict email to a specified list of countries, thus allowing for language specific emails
Resend order emails if the customer knows and enters the order number and email which match the actual order. The form for these two data elements can be placed anywhere you can edit the store user interface, e.g. headers, footers, welcome screen.
You can specify the product code and an attribute/option value that must also be met before the email will be sent. This is particularly useful when the emails are used for vendor notification. A certain product might bedrop shipped by two different vendors and the only difference is the selected attribute/option value.
Insert a "require" token that has to be met before the email will be allowed. As example,have a checkbox using Addendum to ask a customer if they want to be added to a list server (mailing list). Then if they check the box, the "yes" response is sent to Mail Manager. The Mail Manager can then generate a specifically formatted email to activate an email address at your list server, if you have one.
Write a different body for each of the email templates you add
List products and prices or just the products without prices
Link the email usage to one or more product codes or entire inventory with wildcard
No need to go to each product to link the email, a copy and paste froma flat text file will add hundreds instantly
I'd be surprised if you find that this capability exists anywhere in any mid-priced shopping cart system. Autoresponders that fill in the blanks are one thing, but this is a store owner, pre-planned autoresponse for a specific product. Within your store, you could have dozens of different responses (individual or grouped) or a wildcard response for all of the products. You can use itto make connections not directly related to sales, yetlinked to a specific sale.
Customer buys a kayak from your store. Tell them about the kayak camp 20 miles from your store and give them the 800number of the guy with the info about a big get together next month.
Customer buys an orchid from you which would lead you to believe he/she may have a specific variety you have been looking for. You autorespond with your want list for your nursery inhopes of finding the needle in a haystack.
As you can see, this list could be endless. Targetted, intelligent autoresponders are designed to increase your store'sbusiness and decrease the amount of time employees spend on sendingout product specific, emails.
The pre-formed templates are easy to configure and do not require programming experience. For the more experienced, you also have the option of using tokens and mini-scripts in free form templates. An example free form template is included with the install documents.
This module will show the resulting discounts from using the Merchant Price Group Feature. You can use: Markup From Cost, Discount From Retail, and Cost to show discounts to your customers. The amount of discounting is controlled through the admin in the Price Group feature. You also have control over whether you show the customer a higher or lower discount based on the Price Groups they are assigned to.
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #3 includes the abilities to:
Replace Category Tree with Alternate HTML Menu. Requires HTML file in Root Directory.
Move Top Navigation Bar to the Left Column. Category menu eliminated or, if one exists, replaced with an html file on top of page.
Remove all Account and Login Functions.
Gentle Forced Login! Remove Price, Add to Basket and Buy One Now buttons from all Screens until Login.
Remove Search Button from Navigation Bar. With this, you will likely use a search form in Category Tree.
Place HTML above the NavBar. Requires HTML file in Root Directory.
Basket Contents Required Before Checkout all Screens. Requires gifs, see insts in top of module file.
Category Screen Table Display with Quantity Select Option. Displays grey button or gif.
Tighten display on Category Screen and Product Display and Store Front. Removes space at top and left of main body display.
Create Horizontal Display of Four Thumbnails in a Row on the Category Screen. Displays only Thumbnail Images.
Place Thumbnail Image on the right of the Product Name, Price, Quantity in Basket and Add to Basket button on Category Screen. Tight vertical display with horizontal rule.
Replace Weight with More Info popup JavaScript on Product Display. Requires HTML file in Root Directory and installation of javapophead.mv.
Header portion of JavaScript. Creates a 330 x 250 window. Can be used with your own JavaScript or programs in this Pack.
Image displayed on the right of information on the Product Display Screen.
Move All Text and Add to Basket to Right of Image in Product Display. Tightens display.
Display two columns of thumbnail images with price and add to basket button on search screen. Requires Add to Basket gif.
Display Category Tree and two columns of thumbnail images with price and add to basket button on search screen. Requires Add to Basket gif.
Display three columns of thumbnail images with price and add to basket button on search screen. Requires Add to Basket gif.
Display Category Tree and three columns of thumbnail images with v - price and add to basket button on search screen. Requires Add to Basket gif.
Move Search for: box to top of Category Tree. Removes Search for: box from top of main body. Category Tree displays on Search Screen.
Search in Category Tree, Two thumbs in a Horizontal Row Search Screen Display. Removes Search for: box from top of main body. Category Tree displays on Search Screen. Requires Add to Basket gif.
Search in Category Tree, Three thumbs in a Horizontal Row Search Screen Display. Removes Search for: box from top of main body. Category Tree displays on Search Screen. Requires Add to Basket gif.
Remove Search box from Search Results Display.
Display four columns of thumbnail images with price and add to basket button on search screen. Requires Add to Basket gif.
Place Thumbnail Image on the Attribute Screen.
Place full sized image on the attribute Screen.
Add Hyperlink to Product Name on Product List Screen.
Display Two Columns of thumbnail images with price and add to basket button on Product List screen. Requires Add to Basket gif.
Display Three Columns of thumbnail images with price and add to basket button on Product List screen. Requires Add to Basket gif.
Display four columns of thumbnail images with price and add to basket button on Product List screen. Requires Add to Basket gif.
Display Category Tree and Two Columns of thumbnail images with price and add to basket button on Product List Screen. Requires Add to Basket gif.
Display Category Tree and Three Columns of thumbnail images with price and add to basket button on Product List Screen. Requires Add to Basket gif.
All extensions are designed to just Plug AND PLay in OpenUI stores. Designed/Written by Luray Williams.
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
This extension module 'cleans up' the basket and invoice/email display of attributes, consolidating all attribute pricing information into the actual product price.
Attribute price is calculated as a percent of the product price. For example, if you wanted to charge 40% of the product price for an upgrade or larger size. Utilizes the attribute price and option price field for adding percents.
Negative percentages may also be used for discounting the product price.
With Kitmaker, you can combine several related products into a kit and offer them as a group price. You can also combine unrelated products to establish a bundle offering. This product contains both the Kit Maker module and the Strike Thru module.
You simply enter a percentage discount in your admin and Miva Merchant will sum the prices of the individual items, then apply that discount to calculate the new kit price. If you change the price of a kit component, the kit price will be re-calculated when you update the kit assembly in admin AND when the kit product is displayed on the screen=PROD in merchant.
The kit component list can be displayed in the narrative description area on the product screen. You can display it at the beginning or end of the description or leave it off altogether. Each of the kit components is listed as a link to the individual product's screen so that customers can review the full description of each component. Each kit has the option to show or hide the percent savings.
If you want to show the full price as a strike thru you can select in admin to automatically calculate the product cost equal to the original prices of all of the components. Then install the striker.mv module (included with Kit Maker) and it will display a strike thru for all products where the cost exceeds the price, not just those products which are kits.
If using the OpenUI, the code is inserted automatically. If using the MMUI look and feel, two edits are required in the mmui.mv file for Kit Maker and one edit is required if you want to add the Strike Thru capability to your store.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the list of kit components on the product page so that it better fits your desired look. The kit component display can either use the default display (store owner does not need to know html) or the template which allows the store owner to rearrange the kit component display with or without thumbnail images.
Limitation: This module does not have inventory management oversight of the individual components for display or decrementing. If your components are such that they may likely be depleted, then you will need to scrutinize sales to
determine when to remove the kit from the shelf.
An example of a product assembled using Kit Maker is at
1AA00102.
Now you can easily customize and display varying price and cost fields.
With Price Wizard, you can opt to display the price field, cost field or another field calculated by both price and cost fields. You can optionally show customers their overall savings on a per product basis.
Price information can be optionally displayed on product, category, product list or search screens.
This module allows a Merchant store owner to import attributes (text, textarea, checkbox, radio, and select) and options from an easily edited/managed flat file. The module also allows the type "template" to be specified if you have previously added the corresponding template through admin. It will not create the templates and its internal attributes/options. The module will also delete product attributes which the store owner identifies for deletion. For those sites with time-out problems, multiple flat files can be used to break up the number of attributes and options being imported at one time. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Normally, additions are made based on the product code. A typical version 5.x entry inthe flat file for a radio button attribute for a specific product would be: A|1AA00004|version|radio|Merchant Version:|0|0|1|graphics/en-US/mmui/blades.gif||| O|1AA00004|version|5X|5.xx|0|0|1||1|0 O|1AA00004|version|4X|4.xx (add $1.00)|1|1|0||2|0
The key for the field values is: A|product_code|code|type|prompt|price|cost|required|image|template code|display order|weight O|product_code|attribute_code|option_code|prompt|price|cost|default|image|display order|weight
This module also allows you to import the same attributes/options by category code. That way you can fill all of the products in a category withthe same attributes. This saves considerable typing in the flat file.
If for some reason you want to delete attributes, you can easily delete all attributes related to a product code.
The attribute and option EXPORT module is distributed with the IMPORT module. It creates a flat file in the format described above so that the data can bere-imported after off-line editing.It does not export the templates.
Charge your customers by the variable size of the item they are ordering. This module is used to calculate prices on items which are priced, e.g. by the foot, by the inch, or other units of measure. This is particularly useful when the store owner does not want to have a pull down select list of infinite values.
The module also eliminates the common hack that stores have used which involved using the number of the items added to the basket to adjust charges. This module allows the customer to specify two dimensions (e.g. length and width) as item attributes on the product screen (PROD) and still be able to order more than one of that item. Not for upsell products. For example, ordering four 8" X 10" picture frames involves entering 8 in the length attribute and 10 in the width attribute and entering 4 in the add to basket quantity input.
The store owner determines the storewide number of free units (if any), e.g. square inches, and the lowest and the highest values that can be used in the measurement. The store owner can also use price groups to vary the dimension pricing for applicable customers. The attributes type is usually text but could be select list pull down. It cannot be a template. The attribute prompts can read whatever the store owner desires to direct the customer to enter the numeric measurement. If you are using our Attribute Prompt vs Code module, that prompt will also display on the basket, invoice and emails instead of the attribute code. The store owner's settings are configured in admin.
The customer enters the dimensions to form the combined units (e.g. square inches) and the module calculates the price based on the calculated units times the price of the first dimension attribute.
This module allows a Merchant store owner to import attributes (text, textarea, checkbox, radio, and select) and options from an easily edited/managed flat file. The module also allows the type "template" to be specified if you have previously added the corresponding template through admin. The module will also delete product attributes which the store owner identifies for deletion. For those sites with time-out problems, multiple flat files can be used to break up the number of attributes and options being imported at one time.
Normally, additions are made based on the product code. A typical version 2.x entry in the flat file for a radio button attribute for a specific product would be: A|1AA00004|version|radio|Merchant Version:|0|0|1|| O|1AA00004|version|2X|2.xx|0|0|1| O|1AA00004|version|1X|1.xx (add $1.00)|1|1|0|
The key for the field values is: A|product_code|code|type|prompt|price|cost|required|image|template code O|product_code|attribute_code|option_code|prompt|price|cost|default|image
This module also allows you to import the same attributes/options by category code. That way you can fill all of the products in a category with the same attributes. This saves considerable typing in the flat file.
If for some reason you want to delete attributes, you can easily delete all attributes related to a product code.
The attribute and option EXPORT module is distributed with the IMPORT module. It creates a flat file in the format described above so that the data can be re-imported after off-line editing. It does not export the templates.
In the compiled version you can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volume
pricing and hide the table from them completely. Customers
must be logged in to identify the price group they are in before
the volume pricing module can disqualify them from volume pricing.
