Found 846 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.
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)
Display a brief summary of items currently in each customer's basket as they shop within a Miva Merchant store, provide a storefront display of the shipping charges, and list their recently visited product pages in your store with quick link and add button.
Features: (some features are only in the compiled version - see details below)
- Summarize basket contents on most Merchant screens
- List product name or code, quantity, and price
- Use image to alert new additions made to basket
- Display a checkout link when order minimum is reached
- Use store's assigned shipping modules to preview shipping options and charges
- List recently visited product pages with easy add to basket button
- Optionally use OpenUI token to place the mini-basket in many places on the screen
- Optionally use token to place visit history outside of the mini-basket
- Owner can monitor live activity of customers visiting product pages through admin
- Customize mini-basket look in admin (color, size, headings)
- Built-in link to view main basket
- Optionally hide mini-basket if no products are in it
- Licensed per domain
- OpenUI or MMUI compatible (OpenUI recommended in compiled Merchant)
The Mini-basket "view" is configured in the admin interface. The title of the Mini-basket, column headings, font size and color are configurable. You also have the option of a checkout link appearing in the Mini-basket when a specific order subtotal has been reached, thus allowing for minimum orders if you have disabled the checkout button in the standard Merchant nav bar. You can also allow customers to preview shipping options and costs with a single click if they enter ship to location info. Customers do not need to be logged in to view the shipping options. The Mini-basket title, checkout
button, and shipping option link can be displayed with either text or image. The basket title is linked to the full basket contents
display and the checkout is linked to the checkout screens. The shipping option
link runs the installed shipping modules to display the available methods.
In the compiled version of Merchant we have included
footsteps of customers' recent travels to the product pages in the store. The display remains closed unless the customer clicks the link for the recent visits, thus not taking too much space. When displayed, an Add to basket button can be included so the customer can easily add products which they had visited earlier and now they want
to add them without having to search or drill down though the categories. This reminder of pages visited lessens the chance of forgetting something before the customer checks out. The convenient links allows the customer to quickly go back and take a look at the products again. The
recent visit history will remain available for the length the store owner has set for basket timeout. Additionally, for your customers who login, you can have the history availability
extended for any number of additional hours, as they are more likely to return and make a purchase. The recent visit history can be included within the mini-basket table or outside of it. If you want to place the visit history outside of the mini-basket, you can use tokens in the header and footers of screens if you are using the OpenUI. We
have included a "view" feature in admin that allows the store owner to monitor live activity in the store. All recent product page visits are listed the admin screen. Customers not using cookies or whose browser is creating a different session ID with each page click will not be able to display their recent history, however the store owner will still be able to see the pages currently being visited.
In the compiled version are new admin configuration options, e.g. border
color and text to display when the basket is empty. If you are using one of the sort shipping modules like our Shipping List or our Sort Shipping Plus Free Shipping Option or the Shipping SuperMod from Copernicus, you can configure the Mini-basket module to use the sort
order of those modules. You can configure the product
data column to display the full product name, or code, or a portion of the product name (20, 30, or 40 characters). In addition to the several locations available using OpenUI
hook points, you can use OpenUI tokens to place the display within headers and footers of the Miva Merchant screens. You can also make the mini-basket invisible until at least one item is added to the basket. You can also include an image in the mini-basket immediately after addition of a product to the basket. Many times customers don't realize
a product was added so they click the Add to Basket button again. By displaying a noticeable, e.g. animated, image in the mini-basket, their attention is drawn to the basket and they clearly see the addition was made.
License is for ONE mall. Within that single mall, the module can be used in multiple stores without additional license. It functions within both the Miva Merchant (mmui.mv) and OpenUI (oui.mv) look and feel modules, appearing at either the top or bottom of the category column. If using the mmui.mv, you will add one line to the mmui.mv file. Note that if your Merchant version is 4.14 or newer, you'll need to edit and recompile the mmui.mv to mmui.mvc (compiler license from Miva Corp required). Hence, OpenUI is highly recommended if you are using Merchant 4.14 or newer. If using the OpenUI, the hook is automatically set when you install the module. There are several hook point screen locations available, of which one can be selected in the module's admin screen.
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.
The StatCat module is both an admin module and a basket interface module. The primary purpose of StatCat is to generate static catalog pages (indexes and sub-pages) directly from your Miva Merchant products and category databases so that search engines will add your pages to their index. Presumably this will allow customers to find your store amongst the millions of web sites on the Internet. As such, the pages generated are basic html pages with links to sub-pages, basket page and individual product pages in your Miva Merchant system. Each page contains your store title, meta description, meta keywords, footers along with the products. Category pages also contain category headers and footers.
Although these are static html pages, they have direct links which allow customers to add the products to their basket which is maintained in your Miva Merchant shopping cart system. If you are using the CIM Inventory Manager or Miva Corp's new Inventory Manager (in Merchant 4.x), it will even check the stock level and return an out of stock message if stock level is depleted
** Caution: If you are using Merchant 4.0 and its Inventory Management system that deducts products from inventory when they are placed in the basket, you should select to NOT use the Add to Basket buttons if you have one-of-a-kind items. The reason for this is that some robots and other indexing software may even follow links which contain the ? and & characters. This could result in the stock level decrementing to zero and out-of-stock emails being sent. The products won't be removed from inventory completely, as they will be re-stocked when you run the Admin:Delete Expired Shopping Baskets. This undesirable situation does not exist in Merchant versions 2.x or 3.x. It is also not a problem in Merchant 4.x if your store does not use the Miva Corp Inventory Management or your product stock levels are not likely to be depleted with one or two passes of the indexing program.
The store owner determines which page the customer will go to when they select to add a product to the basket. They can be taken either to the basket for review or back to the static page they just selected from. Both processes are automatic and do not require Javascript or meta refresh routines. Either click through destination can be used on either of the sort options, store owner choice. In addition to the functionality of this module, it provides an excellent example of how to interface static pages with the Miva Merchant system with return to the correct static page.
Quick links on each sub-page allow the customer to return to the index or go straight to their basket for review and checkout.
Below the sub-pages the store owner can even generate individual product pages. These product pages contain the full sized image and description. If the store uses the Flexible Product Description module and the product record contains a Keyword field, those product specific keywords are added to the store's generic keywords which are already in all of the static pages.
The store owner can decide whether to display the price for each item on the static pages. Since these pages are static and cannot function interactively to determine customer price groups or discounts, the hide price routine has its place. However, if the store has no price groups and discounts are calculated on basket totals or discount coupons, the price listing is useful.
The static pages also have no way to restrict access. So if your store is one which does not allow certain products to be shown to all customers, then this module is not for you, unless you can place all of those restricted products in specific categories. In which case, you could then sort pages by category and simply delete those categories' pages.
This module is for Miva Merchant 2.x, 3.x and 4.x. It works with both the Miva Merchant look and feel (mmui.mv) and the OpenUI look and feel (oui.mv). If using the mmui.mv, there are two edits that need to be made to the mmui.mv file.
StatCat produces pages similar (mirror) to the layout in Miva Merchant with admin control. The following configuration settings are made within the standard Miva Merchant admin interface: Page title, home URL, optional title/store logo, title background color, title foreground color, category title header size, number of product columns on the category sort page, Meta description of the site, Meta keywords on the site, return action after adding a product to the basket, option to hide the prices, category column background color, category column foreground color, category column font, category column size, product background color in the category sorted pages, product foreground color in the category sorted pages, product font and size in the category sorted pages, optional display of thumbnail images in the category sorted pages, store front page welcome screen, search button input, product descriptions on category pages, and page footer.
Once generated, the index pages can be linked to your main home page. The catalog can be left in the directory it is generated in or copied to any web site (or multiple web sites) to increase search engine visibility. The links to images and back to your Merchant.mv store will work across servers. An example of this remote distribution can be seen at my Yahoo/Simplenet web site. The limitation to the remote distribution is that these remote static pages are one way, ie. placing a product in the basket will take the customer to the main Merchant.mv, but not back to the remote static page. They would then continue shopping in Merchant.mv. This limitation exists only if the static pages are not in their original catalog directory. If they are in the catalog directory on the local server with Merchant.mv, then return to the static pages is one of your options in admin.
The StatCat also has the ability to generate static pages which can be placed on a disk and used as a catalog which can be mailed or given out to potential customers. When using this option, links to your web site or the shopping cart are suppressed. An example of this type of catalog can be seen online. It has no links to the cart and the images are virtual to the static html pages.
When generating the catalog, the store owner has the option of restricting the html output to a list of specific categories. This is particularly useful when the store owner wants to place their static pages on remote servers which have specific themes in a mall environment. Some categories may "fit in" and some may not. This also might be useful if you want to create disks with only certain categories of products on them to be given to customers.
Note 1: StatCat uses the first letter of the product name to name the sub-pages. If you use illegal characters for the first letter of product names, you will not be able to generate the by-name catalog. An example would be the left bracket, as some might have put the font tag at the beginning of the product name. If that is the case, use the by-category catalog.
Note 2: If you have an excessively large products database, you will probably not be able to run StatCat on a server without timing out. However, you should be able to run it in MivaMia if you have a mirror of your store on your PC. You would then need to upload the static pages manually. This store of 600 products took about 5 seconds to generate the category pages.
Click through returns to the originating static page after addition (alternatively you can have it remain at the merchant.mv basket)
This example contains StatCat generated individual product pages
Several new features have been added to the compiled version; background image, functional navigation bar, "smart" metatags, extensive implementation of keyword and header and footer usage, product page names can be product code or name ending with html, inclusion of product links at the top or bottom listed as featured products or similar designation, include any fields in the products database on product pages (including modified structure), optionally hide subcategories on category pages as applicable, additional product page links such as "check availability or latest prices", and export to any directory within the store's path (creates directory if it does not exist). Discontinued (inactive) products can continue to have modified static pages generated so that search engine links remain viable, yet do not result in errors when linked to the store. Additionally, affiliate codes can be included with every link so that the static catalog pages can be given to affiliates who wish to mirror your catalog at their site. If you are using the OpenUI, StatCat adds "smart" metatags to your merchant.mv so that when the customers (and search engines) click from your static pages to your actual store, the pages will contain metatags related to category headers, product descriptions and product keywords (if used). It also reverses the title tag with the category and product screens so that the category or product name appear first, then the store name. If your store has our Volume Pricing module version (4.53 or higher) installed, StatCat can optionally include the volume price table on the static pages. When creating the static product pages, a flat file is created in the background which can be used for a data feed file for submission to FroogleTM. It contains the header and data for the basic file format.
The purpose of Power Search is to allow a customer to search one or more fields which are allowed by the store owner. The store owner can choose any fields within the products database and/or the custom product fields (Miva Corp built-in utility module) database to be searchable. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Implements field specific, keyword searching - Uses store morph technology to build templates with version history - Customer selects the fields to search and the sort order they want the results displayed - Search the whole store or limit to one category - Search by all (AND), any (OR), exact phrase, or begins with - Display total found, number of pages, and links to each page when the results exceed one page - Use the same product list layout as original search or alter for your needs - Can limit search to a specific price range - Use in conjunction with the Emporium Plus Tell A Friend module to send searches to a friend - Product page "return to search" link takes customers back to the same search page - View admin log of searched words/phrases for marketing and keyword identification - Maintain compatibility with 3rd party modules which use the MIVA Corp custom product fields - Create pre-defined select list searches on a single field - License per domain/mall
Feature Details. Easily editable templates. The module has five templates which can be used for each section of the search page. The templates have full versionhistory and use standard Merchant 5 template coding for easy update and rollback of changes. Each template is pulled into the location you want it on the search page using a render token. The templates are field selection, category selection,search scope/type, page counter and links, and product list layout.
Search specific fields and sort results. Allow a customer to search one or more fields which are made selectable by the store owner. The store owner can choose, in the admin screen, any fields within the products database or the MIVA Merchant built in custom product fields database to be available. The Power Search module uses a mirror database of your products, custom fields and categories; much like the big search engines use. By creating a mirror before the search is made, many operations to join multiple databases togethercan be avoided, so the customer gets a much faster search. Customers can also sort the results on fields like name, code, price, cost, when they were added to the store, or the default display order the store owner established for productlists. The build of the mirror database goes quite quickly and is a maintenance procedure you will do periodically. The small amount of time you take to build the mirror will save your customers significant amounts of time in their searches vs searches which don't use an optimized mirror database. Buildingthe mirror is not required just because products are added, deleted, or edited; as those processes update the mirror automatically without needing a rebuild. See the install doc for details.
Category selectable. Customers can use the category selector to select just one category to search. The default is to search the whole store. You can use the built in token which lists all categories with one or more products in them oryou can build your own select list of only certain categories.
Multiple search types. The customer can select how they want to search the database. The default is to search for products where all (boolean AND) of the keywords entered are found in the record. The customer can broaden that search so that any (boolean OR) of the words are found in the record. They can search by exact phrase so that the words must appear in thesame order in the record as was entered in the search input. They can also search the fields where the data in the field begins with the search string. This is useful for things like finding all of the products whose NAME begins with a specific letter and allows you to have a list of A-Z links that implement that specific search.
Advanced pagination. The module can display the total number of products found which match the search condition. Additionally, the pagesare numbered, e.g. Page 3 of 20, when results exceed the configurable number of products per page. You can also display alist of page numbers and links to those pages so the customer can jump to the page they want to look at. This pagination is similar to that used in the Emporium Plus Category Manager module.
Product layout template can be customized. In the 'srch' page template, there is a "search results layout". If you are happy with that layout, you can copy and paste the contents of that template into the Power Search module's product layout template. You can then modify the layout in the Power Search admin screen.
Price range searching. While searching the price field might be useful in some cases, a more popular search is price range. Within the searchable fields section, the customer has the option of entering a low and high price to create a range. If left blank, the search will not be filtered by price range.
Tell a friend module interface. If the store is using the Emporium Plus Tell A Friend module, customers can send the search string from Power Search to friends. The link in the email will go to the same page of products that the customer was on when they clicked the Tell A Friend button.
Return to search page link. After going to the product page from a Power Search rendered search, a convenient "return to search" link on the product page can bring the customer back to the original search page.
Search log with admin report. In admin, you can view the log of search words/phrases which your customers have used. This helps you from a marketing standpoint to determine the most sought after products and possibly the need to carry a new product. Additionally, it helps you identify keywords which might be useful to include in the narrative descriptions or the meta tags for search engine submissions and even local searches in your store. As example, while you might have a product called flip flops, customers might be searching for thong sandals (which is the same thing). But if you had not used those words in your description, you may have lost the sale. The log can be purged in the admin screen to reduce its size as desired.
Optimized search of built-in custom product fields. This module does not require that you use a proprietary 3rd party module for the custom product fields. It uses the built-in custom product fields module from MIVA Corp, thereby ensuring compatibility with other 3rd party modules which use those same custom product fields. No need to go down that proprietary datafield path of no return. As example, the Emporium Plus Template Data Feed module can use the built-in custom product fields to populate feeds to just about any search engine and shopping index with those "special" fields those indexes require.
Live examples. We cannot link to our demo Merchant 5 store from MivaCentral so if you'd like to see a couple of the live pages demonstrating searches, please contact us for the link. You can check out the selected field search in our test store which has about 600 products with multiple custom product fields. Try some searches so you can get an idea of search speed.
Pre-defined selectors. The Power Search function can also be used for pre-defined select pulldowns in your store. An example of genre and decade searches are in the lower left column of our test store's storefront screen. It will search a specific field, with store owner pre-defined selections. This same technique can be used for things like manufacturer searches if you have a manufacturer field in your custom product fields.
Liberal licensing. License is for ONE domain/mall. Within that single mall, it can be used in multiple stores without additional licenses.
This module requires that you are using MIVA Engine v5.03 or newer. When you log into admin, you can see which version of the engine is in use in your store.
Communication of order status with your customers is a critical element in the overall success of your store. Provide order status change emails to customers, keep track of order changes with backend administrative notes, and provide customers with an easy login view of their order status and invoice. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Order status updated in admin including tracking numbers and admin notes - Bulk update several orders' status with a single click - Status change emails with tracking links can optionally be sent to customers - Unlimited number of templates for the status change emails - Quick inventory adjustment when orders are cancelled - End of day (EOD) productivity report for all dates, a range of dates, or specific date - EOD display all records or just the records with a specific status - EOD contains links to the order edit screen for easy viewing of an individual order - EOD display of products sold summary reports - Run a Stock Level Report (SLR) to determine which items are nearing depletion - Editable interface to change the inventory levels of all/any products in the SLR - Export the SLR for mass editing/importing or to interface with your office backend - Annotate progress updates from multiple departments within the order record - Progress is visibile to other admin entities within your store at all times - Customers can view their order status history including tracking links and product lists - Order status history can use default or store built template - Customers can view their invoice within current orders from the order status history or the link in the confirmation email - Customers can view their order status and shipping tracking by entering their order number and email - Customers can have one click re-order from invoices in the current orders - Auto-assign customer membership to price groups based on their order total history
Feature Details. Provide order status change emails to customers, keep track of order changes with backend administrative notes, and provide customers with an easy login view of their order status and invoice. Easily manage customer communication with this module and the related modules below.
The membership system allows you to automatically include customers into price groups when they log into your store and is based on their prior purchase history. You set up your price groups as you would any price groups and assign the applicable products to those groups. Then you specify a trigger level required for the customer to be a member of each group. You can insert tokens into the applicable screens, e.g. customer edit, welcome back returning and new customers. Then when they log in, the token runs the order history for the status codes you specify (e.g. F for filled), sums the totals, and checks to see if they meet a membership level. If they do, they are inserted into the highest qualified price group.
In addition to enhanced communication with your customers, you may want to manage product levels associated with orders and cancelled orders. Miva Merchant allows you to track stock levels of your products online. As products are placed in the basket, the level is decremented. If the order is not completed, the products are returned to the shelf when you delete expired baskets. If the order is cancelled, the products are not automatically returned to stock in the core Miva Merchant. The customer and product management modules interface with the built in internal inventory management (IM) system to improve the overall IM usability.
In the administrative interface:
Shipping tracking numbers, entered through admin, display in the customer account and the status update email (can be linked directly to the shipper tracking page)
Change the order status and optionally send the customer an order status email which can vary based on the style of the status email chosen. Email styles are created using templates with tokens for insertion of specific variables. Can update several orders at once with the bulk status update feature.
Run an end of day-productivity report for all dates, a range of dates, or a specific date displaying all records or just the records with a specific status. A convenient link to the order edit screen makes viewing an individual order quick and easy.
Re-establish inventory levels for a product when an order has been cancelled (auto-restock) or new quantities are put in your inventory.
Run a Stock Level Report to determine which items are nearing depletion or all products being managed for inventory. The module admin console includes an easily editable interface to change the inventory levels of all/any products in the report.
Export a flat file of product codes, quantity, and product name for easy mass editing/importing or to interface with your office backend systems or for re-import into Merchant itself.
Additional order related data can be added in the admin screen; employee code making the status change, date of the change, narrative notes about the order, numeric value (e.g. for adjustments). Multiple admin updates can be made to each order's record by any department within your store (packing, shipping, accounting, returns, etc).
From the customer account record:
Customers can view the status of all of their orders, including update information (e.g. tracking numbers) which is entered by the store owner through admin. The order status history display can be modified by the store owner with a template and tokens. You can even include hot links to carriers' tracking systems with the number filled in. You'll need to enter your carrier tracking URLs into the module's admin configuration screen. The number of carrier URLs you include in admin is not limited.
Customers can view their previous invoices as long as they are in online batches or still in the unbatched orders.
Even after orders and batches are deleted (you may delete processed orders to save disk space) the customer can still review the basic products listed in their order along with the shipping and payment info.
Customers can re-order/duplicate a previous order with a single click from the invoice (order details page) which are still in online batches (i.e. not deleted) or as yet unbatched orders.
Be sure to take a look at our other related modules which can enhance store - customer - vendor communication even further. They include:
Contact Manager - provide a support interface without needlessly including your email on your store's pages for spam harvesters to capture
Event Reminder - customers and store admin can schedule reminders to themselves or others for specific events/tasks at specific times
Follow-on Contact - generate after sales communication at pre-determined points of time in the future
Mail Manager - generate template emails (with tokens) as HTML or text as an auto-response, e.g. as customer order confirmation or even welcome emails
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.
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.
If you don't know which OpenUI product you need, then THIS IS THE ONE!
The OpenUI Advanced (formerly OpenUI Standard) is ULTIMATE enhancement for your Miva Merchant store! Too many features to even begin to list, and all for a VERY LOW PRICE!! It gives you all of the features you are already used to from OpenUI Look & Feel Basic, and the following addons are include:
And the new OpenUI Turbo (double your OpenTokens speed!)
The OpenUI Look & Feel module replaces your MMUI module and provides central 'hooks' through which module developers may easily add features and performance enhancing solutions without having to reinvent the wheel with each Merchant release.
UDPATED VERSION - NEW AND IMPROVED!
We went all out with this latest release of the OpenUI. We have included the following enhancements:
OpenBatches™ - This simplifies order processing in Miva Merchant like never before. You no longer have to go back and forth between the left-hand tree and right-hand main window. From the right hand main window, searchable lists allow you to search, view, edit, or delete batches. This screen also allows you to view orders within a particular batch via OpenOrders™, shows if you have new orders, and even enables you to create a new batch. This all happens from ONE interface.
OpenOrders™ - Using the main window, you now have a searchable order list that allows you to filter by all orders, only unbatched orders, or by orders within an individual batch. You can further filter by order number, product code, order total range, and by date and time range. From this screen, you can also edit and delete individual orders. Once again, this all happens in ONE interface.
An optional statistics interface that works with both the OpenBatches™ and OpenOrders™can be unlocked with the purchase of an OpenUI Pro license key. Find out your top sellers, revenue generators, sales by the hour and day, and much MORE! Read More Detailed Information!
This additional license key is solely for statistics features and will have NO impact on existing or future OpenUI installations. All stores will continue to function with the same capabilities as before and include the great features listed below.
Shorter URLS for Google - It was recently announced in a newsletter geared toward search engines and Miva Merchant that category and product pages without the store code in the url were being readily indexed by the top search engine in the world, Google. If you only have one store, the OpenUI will automatically remove the store code from all urls in the category tree, product list, search results, and basket contents screen. If you have two stores, your store code will remain in the url.
Example:Instead of merchant.mv?Screen=CTGY&Store_Code=CODE&Category_Code=CATEGORY, it will be: merchant.mv?Screen=CTGY&Category_Code=CATEGORY This applies to compiled stores with the mvc extension as well.
Feature added based on recommendations from JMH Web Services (jmhonline.net). *This information has been updated to reflect new findings from JMH. Google now does not have a problem with the store code.
Category and Product Names First in Title Tags- Miva Merchant and previously the OpenUI put your store name before the category and product names in their respective screens title tag (i.e. Store Name: Category or Product Name). Depending on the length of your store name, your category and product titles may not be appearing in your search engine listings title phrase! With the new and improved OpenUI, your category and product titles will be first in the title tag, resulting in better listings within search engines (i.e.Category or Product Title: Store Name).
Feature added based on recommendations from JMH Web Services (jmhonline.net).
A New (Optional) Interface for the Miva Merchant Navigation Bar (navbar)- You now have better (and more) control over which navigation buttons are displayed, as well as many other features including:
Ability to specify cellpadding and cellspacing of navbar.
Optional navbar background image.
Options to align navbar (i.e. Full, Center, Left, Right).
Ability to change navbar buttons including the logo to space, text, etc.
Token replacement in the Cell "links" can be done using the %VAR(varname )% convention. For example, to include the g.sessionurl, just use "%VAR(g.sessionurl)%". To include the store id, use "%VAR(Stores.d.id)%". Most available variables can be used, but they will all be filtered through the encodeentities() function before they are substituted.
Feature added based on recommendations from Rich Chatfield (customMvDesign.com).
Support for New Attribute Types Built-In- New Attribute Types were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Support for module Order Tabs Built-In- module Order Tabs were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Body and Head Tag Options - You don't need additional modules anymore for these two fields if you use the latest version of the OpenUI! Include javascript, cascading style sheets, meta tags, margin height and width, preload images, and much more. For example:
<Select One> Option for Drop-Down Lists - You can now include Select One as the default prompt for attributes, shipping options, and payment option drop-down lists. The default prompt is also customizable for each one. (i.e i.e <Choose Color>, <Select A Shipping Method>, <Select Payment Method>)
The OpenUI Look & Feel Pro License Key unlocks a special feature of the latest OpenUI module. Once you unlock this feature with your license, you will be able to see the total stats for the orders in one batch, all unbatched orders, or all orders regardless of classification. The stats page gives a total sales summary, and then breaks the total sales down by day-of-the-week and time of day (by the hour) the orders were made. The stats page also lists the top selling products and top revenue generators for the specified parameters. The stats are based on the filtering options you currently have set, allowing you to specify exactly what information you would like to generate. For example, if you are in the customer screen on the OpenOrders™ tab and click on the stats button, you will see the stats of that customer's order only. If you have filtered the orders based on the order total and the date range, then the stats will be based on this filter. The stats button gives you immense flexibility because it allows you to view stats using a single filter or any combination of filters. For example, you can see the top 20 products from those that purchased SOMEPRODUCT, or those that have spent over a designated amount....or use both filters. All these resources are available simply by clicking the stats button, which appears on both the OpenOrders™and OpenBatches™ screens.
This additional license key is solely for the new stats features and will have NO impact on existing or future Open UI installation. All stores will continue to function with the same capabilities as before. You can purchase a key by clicking here.
The OpenUI Look & Feel Basic...this is the low-cost, entry-level OpenUI Look & Feel product that is required for running the many 3rd Party Modules currently available. (formerly OpenUI Standard)
It can be enhanced with OpenUI addons, such as the following:
And the new OpenUI Turbo (double your OpenTokens speed!)
The OpenUI Look & Feel module replaces your MMUI module and provides central 'hooks' through which module developers may easily add features and performance enhancing solutions without having to reinvent the wheel with each Merchant release.
UDPATED VERSION - NEW AND IMPROVED!
We went all out with this latest release of the OpenUI. We have included the following enhancements:
OpenBatches™ - This simplifies order processing in Miva Merchant like never before. You no longer have to go back and forth between the left-hand tree and right-hand main window. From the right hand main window, searchable lists allow you to search, view, edit, or delete batches. This screen also allows you to view orders within a particular batch via OpenOrders™, shows if you have new orders, and even enables you to create a new batch. This all happens from ONE interface.
OpenOrders™ - Using the main window, you now have a searchable order list that allows you to filter by all orders, only unbatched orders, or by orders within an individual batch. You can further filter by order number, product code, order total range, and by date and time range. From this screen, you can also edit and delete individual orders. Once again, this all happens in ONE interface.
An optional statistics interface that works with both the OpenBatches™ and OpenOrders™can be unlocked with the purchase of an OpenUI Pro license key. Find out your top sellers, revenue generators, sales by the hour and day, and much MORE! Read More Detailed Information!
This additional license key is solely for statistics features and will have NO impact on existing or future OpenUI installations. All stores will continue to function with the same capabilities as before and include the great features listed below.
Shorter URLS for Google - It was recently announced in a newsletter geared toward search engines and Miva Merchant that category and product pages without the store code in the url were being readily indexed by the top search engine in the world, Google. If you only have one store, the OpenUI will automatically remove the store code from all urls in the category tree, product list, search results, and basket contents screen. If you have two stores, your store code will remain in the url.
Example:Instead of merchant.mv?Screen=CTGY&Store_Code=CODE&Category_Code=CATEGORY, it will be: merchant.mv?Screen=CTGY&Category_Code=CATEGORY This applies to compiled stores with the mvc extension as well.
Feature added based on recommendations from JMH Web Services (jmhonline.net). *This information has been updated to reflect new findings from JMH. Google now does not have a problem with the store code.
Category and Product Names First in Title Tags- Miva Merchant and previously the OpenUI put your store name before the category and product names in their respective screens title tag (i.e. Store Name: Category or Product Name). Depending on the length of your store name, your category and product titles may not be appearing in your search engine listings title phrase! With the new and improved OpenUI, your category and product titles will be first in the title tag, resulting in better listings within search engines (i.e.Category or Product Title: Store Name).
Feature added based on recommendations from JMH Web Services (jmhonline.net).
A New (Optional) Interface for the Miva Merchant Navigation Bar (navbar)- You now have better (and more) control over which navigation buttons are displayed, as well as many other features including:
Ability to specify cellpadding and cellspacing of navbar.
Optional navbar background image.
Options to align navbar (i.e. Full, Center, Left, Right).
Ability to change navbar buttons including the logo to space, text, etc.
Token replacement in the Cell "links" can be done using the %VAR(varname )% convention. For example, to include the g.sessionurl, just use "%VAR(g.sessionurl)%". To include the store id, use "%VAR(Stores.d.id)%". Most available variables can be used, but they will all be filtered through the encodeentities() function before they are substituted.
Feature added based on recommendations from Rich Chatfield (customMvDesign.com).
Support for New Attribute Types Built-In- New Attribute Types were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Support for module Order Tabs Built-In- module Order Tabs were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Body and Head Tag Options - You don't need additional modules anymore for these two fields if you use the latest version of the OpenUI! Include javascript, cascading style sheets, meta tags, margin height and width, preload images, and much more. For example:
<Select One> Option for Drop-Down Lists - You can now include Select One as the default prompt for attributes, shipping options, and payment option drop-down lists. The default prompt is also customizable for each one. (i.e i.e <Choose Color>, <Select A Shipping Method>, <Select Payment Method>)
The OpenUI Look & Feel Pro License Key unlocks a special feature of the latest OpenUI module. Once you unlock this feature with your license, you will be able to see the total stats for the orders in one batch, all unbatched orders, or all orders regardless of classification. The stats page gives a total sales summary, and then breaks the total sales down by day-of-the-week and time of day (by the hour) the orders were made. The stats page also lists the top selling products and top revenue generators for the specified parameters. The stats are based on the filtering options you currently have set, allowing you to specify exactly what information you would like to generate. For example, if you are in the customer screen on the OpenOrders™ tab and click on the stats button, you will see the stats of that customer's order only. If you have filtered the orders based on the order total and the date range, then the stats will be based on this filter. The stats button gives you immense flexibility because it allows you to view stats using a single filter or any combination of filters. For example, you can see the top 20 products from those that purchased SOMEPRODUCT, or those that have spent over a designated amount....or use both filters. All these resources are available simply by clicking the stats button, which appears on both the OpenOrders™and OpenBatches™ screens.
This additional license key is solely for the new stats features and will have NO impact on existing or future Open UI installation. All stores will continue to function with the same capabilities as before. You can purchase a key by clicking here.
Manage coupon addition and redemption functions within a Miva Merchant 2.2x, 3.x or 4.x storefront with this plugin module. License is for ONE mall. Within that single mall, it can be
used in multiple stores without additional license.
Features: (some features are only in the compiled version)
- Configurable prompt
- Configurable action
- Configurable redemption
- Configurable coupon rejection messages
- OpenTokens for use in OpenObjects
- Searchable coupon database with pagination
- Easy view admin for coupon content and historical usage
- Coupon codes can be individually assigned
- Import coupon codes from flat file in bulk
- Autogenerate coupon codes with token
- Assign coupon code as a series for affiliate purposes
- Global scope or for specific products
- Checkout coupons one per order
- Instant coupons on product pages, multiple per order
- Fixed amount or percentage of eligible products discounting
- Specific product eligibility can be scoped to the attribute level
- Minimum order level for redemption
- Establish expiration dates
- Line item display in basket after redemption
- Single use coupons
- One per customer coupons
- Multiuse coupons (can be limited)
- Free shipping coupons
- Limit the country, state or zip a coupon can be used for
- Combination of free shipping and order discount (% or fixed) coupon
- Easy deletion of expired coupons
- Coupon report identifies coupon usage
Feature Details. You can add coupons through the standard Miva Merchant admin interface and include usage criteria.
An unlimited number of coupons can be assigned to the store and each identified with a coupon code. Once you have added the module to the store, you can add coupons in the Order Fulfillment section of the admin interface. When you select the Add icon, you will have several input fields to fill in. You must enter a unique code for your coupon. This is the code that you will give to customers so they can shop and redeem the coupon (one per order). It can be any combination of letters and/or numbers.
The compiled version has a coupon generation function. You can embed a token in your welcome email or notification emails generated with our
Mail Manager module. A unique coupon code will be created and is based on the coupon template you designate. You can have an unlimited number of templates and an unlimited number of coupons copied from them. If you are not using our Mail Manager, you can still activate the generator by placing the token in the invoice header if you are using the OpenUI.
If you have a lot of coupons you want to load into the system quickly, the compiled version has a coupon import from flat file module
An optional expiration date can be included which will prevent its use if the date has passed. Enter it in the year, month, day format, eg. 20000724 would be July 24, 2000. If you leave this field blank the coupon will never expire. However, you can still delete it manually through the admin interface.
A fixed value OR percentage discount off the order total is assigned to each coupon. The default is fixed value/price,
eg $5.00 off the order total. If you put the % sign in the next input field AFTER the value field, it will calculate the coupon value based on the assigned percent of the order total. The %, if used, is entered in the separate field to the right for that purpose. If left blank, the calculation will be based on the fixed value of the coupon. See the note below about restricting discount calculations to specific products instead of the order total. A maximum redemption value can be assigned to each coupon in Merchant 4.x.
If you enter the letter S in the field to the right, the
coupon will be used to allow free shipping (compiled version only) for the entire order. Other criteria for the coupon must be met, e.g. minimum order amount, eligible products, etc.
Optionally, a coupon can be allowed only when an order total reaches a specific amount. For example, you can give a 10% discount when the order total reaches $200 as an incentive or promo. In all cases where a raw value is used, you must make this value equal to or greater than the value of the coupon. If you use the percent calculation, this value can be any value, including zero.
Based on your state's tax requirements, the coupon can be designated to reduce the sales tax or not reduce it. The coupon's tax effect is on the order total, not on individual products. For example, in some states, a store coupon reduces the cumulative value of products purchased before the sales tax is applied, hence you would want it to reduce tax. The exception to doing this is if your products are likely to be non-taxable, making a coupon reduce tax could result in a negative tax calculation. Another type coupon might be the manufacturer coupon. In some states, manufacturer coupons do not decrease the tax liability. You should determine your state's tax requirements before adding coupons to your store.
Coupons can either be used:
multiple times - The coupon can be used at every visit by any customer who shops at your store. This is usually used as a promo to customers, user lists, clubs, etc. They often have a short expiration date to limit their use. A typical usage might be a special holiday sale, eg 10% off everything in the store if used by a specified date. This would eliminate the need for special price groups if the intent is that everybody who has the coupon code can use it.
only one time for each customer - The coupon can only be used for one visit per customer. When the same customer shops at your store a second time, if he/she uses the same coupon code, it will be rejected. This is probably the most common coupon and is usually used in print ads or as a promo, eg. "$5.00 off on your next visit".
only one time for a unique coupon code - The coupon can only be used once. Once any customer has used this code, it becomes unavailable for any other purchase. This is often used as a customer relations tool, eg "sorry for the inconvenience, please accept this coupon.....".
You can restrict usage of a coupon in your store so that it can be used only if a specific product code is ordered. You can list several product codes, any of which in the basket would make the coupon valid if the other requirements are met. Leaving the product code blank means that customers do not have to order a specific product as long as they meet the other requirements the store owner has specified. If you check the box to the left of the product code list AND are using the percentage discount, only those products in the code list will be used in the calculation using the qualifying products subtotal. If you do not check the box, the percentage discount will be applied against the order total. In Merchant 4.0, you can use a wildcard for the product list, e.g. 1AA* would make all products beginning with 1AA eligible for the coupon discount.
New in the compiled version of the coupon module is the ability to restrict the coupon usage down to the attribute level. For example, you can limit the coupon to product codes beginning with 1AA and the attribute "Version" with the option of "4.5". The
format for the input would be 1AA*~Version~4.5|
Alternatively, if you precede the product list with a - (minus) character, the coupon will be excluded from use with those product codes. You canNOT specify it to the attribute level like the include above. (compiled version only)
Appropriate error messages are displayed when coupons don't meet the usage criteria established by the store owner. When the shopper enters a coupon code at checkout that is not valid based on the criteria you establish, he/she will see an error message just below the coupon code input when the checkout form is re-displayed. One coupon can be redeemed per order on the checkout page.
In admin, the coupons can be easily displayed and edited. The coupons are displayed in a table format with configurable number of coupons per page displayed. The entire coupon database is searchable by coupon code or portion of the coupon code.
Expired coupons can be removed from the database (to cut down on disk usage) one at a time or in mass. In admin, you can either put a check in the remove column and select update or select purge expired coupons, then select update.
A historical database, which can be imported and analyzed in database or spreadsheet software, is maintained on all coupons used. The couponuz.dbf can be FTPd to your PC for further analysis in MS Access, MS Excel, or other data management software. This could be useful in determining which coupons bring you the most activity. The number of uses for each coupon is displayed in the admin table in Merchant 4.0
New in the compiled version is the coupon usage report. You can summarize or list each coupon used for a specific time period. You can also restrict the output to a specific coupon code or a string of characters in a coupon code. This latter is useful when you have assigned a series of coupons to an affiliate or advertising campaign. You can determine how much business was brought in with the coupons from various sources.
The compiled version of this module can use OpenTokens instead of hook points within OpenObjects. The OpenDesigner screen lists the OpenObjects which can replace all or some screens within the OpenUI user interface. The OpenObjects provide a template screen which contains the existing hook points (backward compatibility), OpenToken capability, and the ability to move output around within the OpenObject screen. Since the tokens in this module conform to OpenToken functionality, they may be used in other template type screens.
MMUI and OpenUI compatible. If you are using MMUI, there are two required edits in the mmui.mv. If using MMUI in
a compiled version of Merchant (4.14 and newer), you will need to edit and recompile the mmui.mv (expensive proposition). Thus, with compiled Merchant, we recommend using OpenUI instead of the MMUI user interface.
Manage coupon addition and redemption functions within a Miva Merchant 5.x storefront with this plugin module. License is for ONE mall. Within that single mall, it can be used in multiple stores without additional license. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features:- Configurable prompt - Configurable action - Configurable redemption - Configurable coupon rejection messages - Uses tokens to place input on pages - Searchable coupon database with pagination - Easy view admin for coupon content and historical usage - Coupon codes can be individually assigned - Import coupon codes from flat file in bulk - Autogenerate unique coupon codes with token - Assign coupon code as a series for affiliate purposes - Global scope or for specific products - Checkout coupons one per order - Instant coupons on product pages, multiple per order - Fixed amount or percentage of eligible products discounting - Specific product eligibility can be scoped to the attribute level - Minimum order level for redemption of checkout coupons - Establish expiration dates - Line item display in basket after redemption - Single use coupons - One per customer coupons - Multiuse coupons (can be limited) - Free shipping coupons - Limit the country, state or zip a coupon can be used for - Combination of free shipping and order discount (% or fixed) coupon - Easy deletion of expired coupons - Coupon report identifies coupon usage
Feature Details. You can add coupons through the standard Miva Merchant admin interface and include usage criteria.
An unlimited number of coupons can be assigned to the store and eachidentified with a coupon code. Once you have added the module to the store, you can add coupons in the Order Fulfillment section of the admininterface. When you select the Add icon, you will have several input fields to fill in. You must enter a unique code for your coupon. Thisis the code that you will give to customers so they can shop and redeemthe coupon. It can be any combination of letters and/or numbers.
You canembed a token in your welcome email or notification emails generated with our Mail Manager (Emporium Plus - Weiland) module. A unique coupon code will be created and is based on the coupon template you designate. You can have an unlimited number of templates and an unlimited number of coupons copied from them. If you are not using our Mail Manager, you can still activate the generator by placing the token in the invoice header. If you are using our Tell A Friend (Emporium Plus - Weiland) module, you can embed the unique coupon code in the emails that customers send when referring their friends to your store. The coupon generation is also useful when it is embedded into the follow on contact emails that our Follow On Contact (Emporium Plus - Weiland) module sends out.
If you have a lot of coupons you want to load into the system quickly,there is a coupon import from flat file module
An optional expiration date can be included which will prevent its useif the date has passed. Enter it in the year, month, day format, eg. 20000724 would be July 24, 2000. If you leave this field blank the coupon will never expire. However, you can still delete it manually through the admin interface.
A fixed value OR percentage discount off the order total is assigned to each coupon. The default is fixed value/price, e.g. $5.00 off the order total. If you put the % sign in the next input field AFTER the value field, it will calculate the coupon value based on the assigned percent of the order total. The %, if used, is entered in the separate field to the right for that purpose. If left blank, the calculation will be based on the fixed value of the coupon. See the note below about restricting discount calculations to specific products instead of the order total. A maximum redemptionvalue can be assigned to each coupon.
Free shipping coupon option. If you enter the letter S in the field to the right of the value field, the coupon will be used to allow free shipping for the entire order. Other criteria for the coupon must be met, e.g. minimum order amount, eligible products, etc.
Optionally, a coupon can be allowed only when an order total reaches a specific amount. For example, you can give a 10% discount when the order total reaches $200 as an incentive or promo. In all cases where a raw value is used, you must make this value equal to or greater than the value of the coupon. If you usethe percent calculation, this value can be any value, including zero.
Based on your state's tax requirements, the coupon can be designated toreduce the sales tax or not reduce it. The coupon's tax effect is onthe order total, not on individual products. For example, in some states, a store coupon reduces the cumulative value of products purchased before the sales tax is applied, hence you would want it to reduce tax. The exception to doingthis is if your products are likely to be non-taxable, making a coupon reduce tax could result in a negative tax calculation. Another type coupon might be the manufacturer coupon. In some states, manufacturer coupons do not decrease the tax liability. You should determine your state's tax requirements before adding coupons to your store.
Coupons can either be used:
multiple times - The coupon can be used at every visit by any customer who shops at your store. This is usually used as a promo to customers,user lists, clubs, etc. They often have a short expiration date to limittheir use. A typical usage might be a special holiday sale, eg 10% offeverything in the store if used by a specified date. This would eliminatethe need for special price groups if the intent is that everybody who hasthe coupon code can use it. In the compiled version you can limit the number of times a multiple coupon is redeemed.
only one time for each customer - The coupon can only be used for one visit per customer. When the same customer shops at your store a secondtime, if he/she uses the same coupon code, it will be rejected. This isprobably the most common coupon and is usually used in print ads or as a promo, eg. "$5.00 off on your next visit".
only one time for a unique coupon code - The coupon can only be used once. Once any customer has used this code, it becomes unavailable for any other purchase. This is often used as a customer relations tool, e.g. "sorry for the inconvenience, please accept this coupon.....".
Global or product related. You can restrict usage of a coupon in your store so that it can be used only if a specific product is ordered. You can list several product codes,any of which in the basket would make the coupon valid if the other requirements are met. Leaving the product code blank means that customers do not have to order a specific product as long as they meet the other requirements the store owner has specified. If you check the box to the left of the product code list, and are using the percentage discount, only those products in the code list will be used in the calculation using the qualifying products subtotal. If you do not check the box, the percentage discount will be applied against the order total. Youcan use a wildcard for the product list, e.g. 1AA* would make all productsbeginning with 1AA eligible for the coupon discount.
Use instant coupons on the individual product pages and for specific products. These coupons are redeemed at the product page and instantly appear in the basket as a line item discount related to a specific product. Unlike the global checkout coupons, customers can redeem multiple instant coupons in a single order. From a marketing standpoint this gives the merchant the opportunity to offer a promo code atthe product level which gives an impending event (expiration of the promo)to encourage sales while not lowering the value of the product with an overtprice discount.
You can restrict the coupon usage down to the attribute level. For example, you can limit the coupon to product codes beginning with 1AA and the attribute "Version" with the specific option value of "4.5". The format for the input would be 1AA*~Version~4.5|
If you precede the product list with a - (minus) character,the coupon will be excluded from use with those products.
You can limit the coupon to be used only if the customer is in a specific zone. You can use ONE of six possible zone limitations for each coupon (ship to: country, state or zip; bill to: country, state or zip).
Appropriate error messages are displayed when coupons don't meet theusage criteria established by the store owner. When the shopper entersa coupon code that is not valid based on the criteria you establish, he/she will see an error message just below the coupon codeinput when the page is re-displayed.
In admin, the coupons can be easily displayed and edited. The couponsare displayed in a table format with configurable number of coupons per page displayed. The entire coupon database is searchable by coupon code or beginning portion of the coupon code.
Expired coupons can be removed from the database (to cut down on disk usage) one at a time or in mass. In admin, you can either put a checkin the remove column and select update or select purge expired coupons, then select update.
A historical database, which can be imported and analyzed in database orspreadsheet software, is maintained on all coupons used. The couponuz.dbfcan be FTPd to your PC for further analysis in MS Access, MS Excel, or other data management software. This could be useful in determining which coupons bring you the most activity. The number of uses for each coupon is also displayed in the admin table.
The coupon usage report module can provide historical data within your admin. You can summarize or list each coupon used for a specific time period. You can also restrict the output to a specific coupon code or a string of characters in a coupon code. This latter is useful when you have assigneda series of coupons to an affiliate or advertising campaign. You can determine how much business was brought in with the coupons from various sources.
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.
The OpenUI SuperMod provides you with advanced display and formatting capabilities for any Miva Merchant store using OpenUI. By inserting “Virtual Modules” into the OpenUI SuperMod and using templates and tokens throughout the store, you can control the look and feel of Miva Merchant in a whole new way. The OpenUI SuperMod allows you to harness the power and flexibility of OpenUI!
Key Benefits Include:
New Directly edit and modify the templates that control the screen output of your store! All of the templates can be fully customized to your needs, and are fully compatible with any OpenUI Token-enabled modules.
New Create New Screens for your store using Templates! Create forms and surveys, have the contents of the form emailed to you after submission!
Page Template capabilities without module conflicts
Nearly unlimited possibilities for store layout enhancements
Create OpenUI Virtual Modules with a few mouse clicks instead of paying a programmer to develop a fully custom module
Display any text, HTML or variable at any OpenUI Hook Point
Dozens of free “plug-in” Virtual Modules can be downloaded from the Copernicus Website
All Virtual Modules are supported on both uncompiled and compiled Miva Merchant
Simple GUI based Virtual Module development interface, allows:
Value Assignments
Variable-value Assignments
Text/HTML screen output
Variable screen output
Tokenized screen output
Conditional execution
Simple arithmetic assignments
OpenUI Return-hook overrides for selectively hiding or displaying screen sections
NEW! DynamicTemplates™ Scripting Engine
NEW! Direct SQL Queries for OpenDBv2/MvSQL-QUERY
Templates are available for the following screens!
Standard Shopping Screens:
SFNT/LOGN/ACNT/SRCH/PLST/BASK: Store front screen, login screen, customer account screen, store search screen, product list screen, basket contents screen
CTGY: Category screen(s)
Generic store wide category screen template
Category specific screen templates
Category screen templates applied to categories with similar category codes
PROD: Product screen(s)
Generic store wide product screen template
Product specific screen template
Product screen templates applied to products with similar product codes
Standard Checkout Screens
OINF: Order Information screen
OSEL: Order Shipping and Payment Selection Screen
OPAY: Order Payment Information
INVC: Invoice Screen
Free Virtual Modules:
Add Contact Us Button
Body Tag Insert
Change All Prices To "FREE"
Change CTGY Next/Prev Table Width
Change 'Login' to 'Sign In'
Custom Shipping Messages
Head Tag Insert
Hide All Prices
Hide Create New Account
Hide Order w/out Account
Move Continue Button (to center)
Move Continue Button (to left)
No Category Tree
No Weight
Prohibit Shoppers from Altering the Quantity in the Basket
Remove BASE HREF tag
Remove PROD Screen Links
Remove Product Code Links in Basket
Store Front URL
Remove Global Header from Invoice Screens
Remove Other State / Province from Address Screens
Third-party module compatible
Product Page Templates
NEW! No Purchase Links if Zero Price
NEW! No Weight if Zero
NEW! Third-party module compatible
NEW! Best Sellers Display Template
NEW! Category Path?Breadcrumbs Template
NEW! Category Storefront Template
NEW! Mini-Basket Template
NEW! Expanded Category Tree
OpenUI Token Support: The OpenUI SuperMod supports OpenUI and third-party tokens through the OpenUI provided token functions. OpenUI token
support is available in:
Uncompiled: OpenUI v4.56+
Compiled: OpenUI v4.74+
NEW! Copernicus Template Library: The Copernicus Template Library includes over 15 special purpose tokens for OpenUI, and is include FREE with the OpenUI SuperMod!
NEW! OpenUI Enumerator Included! The OpenUI Enumerator is now included FREE with the OpenUI SuperMod!
Third-party Module Compatible Templates: The OpenUI SuperMod allows you to include template files anywhere in your Miva Merchant store, optionally not skipping any other output or hook points. Thus, you can include a template on any screen without compromising existing module compatibility.
NEW! DynamicTemplates™ Engine:
Now featuring the very first ever lightweight template scripting engine for OpenUI and Miva Merchant(tm), DynamicTemplates allow you to create scripted templates! Includes control structures, variable assignments and conditional displays!
NEW! Direct SQL Queries for OpenDBv2 & MvSQL-QUERY:
Users of OpenDBv2 now have direct SQL query capabilities for Miva Merchant! Never before avialable, this feature is a must for advanced display capabilities using OpenUI and OpenDB!
Product Capabilities:
The OpenUI SuperMod can be used for most display
modifications and tweaks, even those that are conditional. With the advent of OpenUI Expression evaluation, almost any Miva Merchant API function can be called from within a template or a VMod. This provides the ultimate in display and execution control within your Miva Merchant store.
*Note: While many API functions are available, general database creation and writing routines are not provided by the OpenUI SuperMod or OpenUI
unless you are using MvSQL-QUERY and OpenDBv2 Therefore custom programming that requires new databases is not possible.
Miva Merchant: v4.00 - v4.13 OpenUI Required: Any Version Miva Merchant: v4.14+ OpenUI Required: Any Version, latest version requierd for token and API function calls.
Please note: The OpenUI Enumerator is included free of charge with this distribution.
Collect supplemental, required or non-required responses fromcustomers at checkout. You can add as many additional checkoutquestions to your form as you want, within reason. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Collect supplemental, required or non-required responses from customers at checkout - Export responses to a delimited flat file - View responses in the file with a searchable admin report - Display responses in the include modified invoice emails and batch reports and invoice screen - Include response data in the order export file created by our inexpensive EZ Batch Report module (sold separately) - Configure text label for each question to preceed the responses in the emails and reports - Special instructions for the order, e.g. shipping needs - Collect responses from survey or poll questions - Customer entered gift card messages - Questions displayed in a table which the store owner designs with standard HTML - Limit the display of questions based on specific product codes - Limit the display of questions based on the ship to country of the order - Used in conjunction with our Mail Manager module, activate sending of specific emails - Assign a fee to one response, for example gift wrapping fee, donation, or rush handling - Insert a negative fee (vs positive fee) for impromptu sales, etc - One or more responses can be required before customer can proceed - Highlighted error message when required response(s) are omitted - Tokens can be used to refill the responses if the page is redisplayed due to missing info - Our standard version contains the features you'd expect in competitors' pro version
Feature Details. The responses are exported to a delimited text file which can beimported into most database management systems for further analysis. Youcan also have those responses appear in the Miva Merchant Email notification and batchprocessing (modified email and batch modules included in the zip file). Use the module for the customer to add specialinstructions for the order, collect responses from survey or pollquestions, allow the customer to fill out gift card messages, include salesman orrepresentative code, etc.
The admin interface allows you to build the form withyour store's questions using standard html syntax. Hence,you can make the response collection table match the restof your store's look and feel. You can have text, radio, select drop down list, text area, and checkbox inputs designed the way you want them. Add css if you like or use typical fonts and table tags.
You can place the questions on one of the three checkout screens. You simply add the tokens to the page templates per the install doc.
You can also specify one or moreof the questions to be required. Customers will not be able to completethe checkout if they do not respond to the required questions.
You can purge old questions from the active file and place them in ahistorical file in order to improve response time during order batchprocessing retrieval. The optional order batch retrieval uses the modified core batch report which is included in the zip distribution file.
You can limit the display of Addendumquestions based on specific product codes. If you list productcodes in the admin input, the questions will only be displayedif one of those products is in the basket at checkout. Youcan also use the wild card product code like 1AA*. If theapplicable products all begin with the same characters, youcan use the asterisk. This can only be used for the beginningcharacters in the product codes.
You can alsolimit the display of questions to specific ship to countries.
You can optionally includethe questions in the emails along with the responses by using the modified email modules which are included in the zip distribution file.If using our Mail Manager (sold separately) module you can have a question (checkbox) which will trigger a specific email, e.g. opt-in mailinglist signup. You can also include the questions and responseson the invoice (last page after payment completes). Theresponses for the batch report are retrieved from an indexeddatabase for faster access.
You can alsoattach a fee to a specific answer to one question if youplace the questions on either the customer information orshipping/payment selection screens.
The included Addendum View report featureallows you to search (within admin) the addendum filefor specific responses. For example, you might have a questionfor a specific requested shipping date. Simply search the filefor orders which have requested the delayed shipping for thatdate. The order numbers can be returned and fed into our EZ Batchreport (sold separately) for a tailored report for a specific shipping date. Another popular use of Addendum is to collect the salesman or representativecode with an order. Not only can you display the code in the batch report,but if you use Addendum View to create a list of orders attributed to thatsalesman, you can make a batch printout for each salesmanwith only their orders on it if you are using our EZ Batch Report (sold separately). You can also include the Addendum responses in the order export file that EZ Batch creates.
Limitation: When used in a store which uses PayFlowlink, PayPal or iTransact payment systems, you will need to placeyour questions on either the customer information screenor the shipping and payment selection screen. Thosepayment systems transport the customer to another domain.Hence, the module needs to save the responses to a filebefore the customer is transported off-site. When thecustomer returns from the off-site payment screens backto your store, the responses will be retrieved for savingto flat file or display in your merchant notification email.
The included modified merchant email and batch reports will display the Addendum resposes. Additionally, the batch report can provide page breaks between each order for better printouts (incoices). Also, the merchant notification email allows you to insert tokens in the subject line so you can include things like the order number, order total, and customer name in the subject of the email.
Compare this module with our competitors' pro or advanced or ultimate versions. Those are just words tacked onto a module name. Don't let our low price fool you - compare features and you will find this module probably contains all of the features found in theirs plus we have several additional features. The Addendum module has been in use since Merchant version 1.x and continually enhanced with each version. Our competitors will try to keep up, but the simple choice is, why get a shadow when you can get the "original".
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.
Recalculate the basket prices based on the price group a customer is in when they log in. Normally, if a customer is not logged in when they place items in the basket, the basket price will be a non-price group price, even after they log in at check out.
Features: - Automatically recalculate basket prices when logging in - Exclude specific product codes from the recalculation - Safety check price change to ensure it does not raise it - Token available to force recalculation in addition to the automatic log in recalculation (Merchant 5.x only)
Feature Details. Automatically recalculate. When the customer logs in, the module will determine the price group status of the customer. If they are in a price group, it will recalculate the prices in the basket to reflect the price group prices of the items.
Product exclusion. In some cases, you may not want to recalculate the basket price for specific products. As example, there are 3rd party modules which adjust the basket price based on other factors set by those modules. The External Product Purchase (sold separately), Size Pricing, Dimension Pricing, Override Pricing modules allow the customer to enter values in the products' attributes which ultimately effect the basket prices of the products. This product exclusion feature lets you exclude those products from the recalculation process. The basket price will remain as it was calculated by the 3rd party module that originally controlled the addition of the product into the basket.
Safety check. The module will verify that the price group recalculation will actually lower the price. Some 3rd party modules discount item prices at the time they are added to the basket, based on a variety of factors. An example of this is Volume Pricing (sold separately). If the customer orders in quantity and you have set the threshold so they will get a price break for multiples of the item, the item will be added to the basket at a price lower than its individual item price. In some cases, that value could even be lower than price group prices. The recalculation module will compare the two prices and use the lower of the two for the basket price.
Additional token. The additional token feature is in the Merchant 5.x version of the module only. This module will make the recalculation at the time the customer logs in. In some cases, you might want to force the process again. For example, the Emporium Plus Customer and Product Administration module (sold separately) has an automatic price group promotion feature. If you set that to occur when they log in, it actually happens when the screen displays at the point you place the token to do that. As the recalculation module does its automatic feature before the screen displays, the customer would not get the full advantage of a promotion to a new price group. Hence, if you are using a price group promotion feature in another 3rd party module, you can follow that process with a forced basket price group recalculation.
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.
Volume pricing at the category level. Easily offer a fixed discount (not percentage) based on the number of items in the basket and the categories those items are in. We also have the corresponding module for an older version of Merchant.
Features: - Discount based on number of items ordered - Set up to 4 tiers of discounts per category group - Can have 8 groups (each containing one or more categories), each with 4 different discount tiers - Category wide, multi-category or store wide discounts - Optionally apply discount after other discounts have lowered the subtotal - Discount shows at checkout as separate line item - Optionally display updated discount in basket prior to checkout - Can use wildcard instead of entering category codes for the group - Can either include or exclude a single price group, e.g. Wholesale, to be able to use the discount
Feature Details: In admin, the store owner configures the trigger levels (number of items needed to activate the discount) and thecorresponding fixed amount off. The store owner can designate 1 - 4 trigger levels so that he/she can vary thediscount based on the number bought. Reward the customer; the more the customer buys, the higher the discount.
The storeowner then includes a list of category codes that willbe used in the calculation. Use this module for category-wide or store-wide fixed discounts. If using store-wide, make sure the discount doesn't exceed the priceof the potentially summed products. If using category-wide,make sure the discount does not exceed the price of the lowestpriced product in the category.
The discount amount will appear during checkout on the screen after the customer has entered their shipping method. You can optionally display the discount in the basket prior to checkout.
In admin you can setup eight separate groups withtheir own four-tiered discount and categories. Hence, if you want to discountone category of products with one set of rules (levels) and another category with a different set of rules, you can now do this. Multiple categories can be assigned to each group. As the basket is scanned, the discount is applied based on each group's rules, then summed together at checkout. You can optionally display the updated discounts prior to checkout in the regular basket screen, recalculating and updating discounts based on changing basket contents.
You can choose one price group, e.g. Wholesale, which is not eligible for the discount since they presumably already benefit from significantly lower prices. Or if you don't want to exclude, you can include the one group. This would be useful if you want to apply a fixed amount off for that price group rather than use Merchant's percent off price group calculations. This would allow you to discount different fixed amounts from different groupings (categories) of products.
You can use the asterisk (*) to replace the category codes. When the module encounters the asterisk instead of category codes, it considers all further products eligible. As example, the asterisk in the first group would make all products in the store eligible for the discount. On the other hand, category codes in the first group would apply the first group rules to those categories. Then if there is an asterisk in the second group, all other products in the store woulduse those discount rules.
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.
Volume pricing at the category level. Easily offer a discount based on the number of items inthe basket and the categories those items are in. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Discount based on number of items ordered - Set up to 4 tiers of discounts per category group - Can have 8 groups (each containing one or more categories), each with 4 different discount tiers - Category wide, multi-category or store wide discounts - Optionally apply discount after other discounts have lowered the subtotal - Discount shows at checkout as separate line item - Optionally display updated discount in basket prior to checkout using render token - Can use wildcard instead of entering category codes for the group - Can exclude a single price group, e.g. Wholesale, from receiving the discount
Feature Details: Thedefault is to calculate product charges in the specifiedcategory(ies) (including attribute charges) to determinethe subtotal to discount. You canoptionally include non-product charges in the calculation.
In admin, the store owner configures the triggerlevels (number of items needed to activate the discount) and thecorresponding percentage off. The store owner candesignate 1 - 4 trigger levels so that he/she can vary thepercentage discount based on the number bought. Reward thecustomer; the more the customer buys, the higher thediscount percentage.
The storeowner then includes a list of category codes that willbe used in the calculation. Use this module forcategory-wide or store-wide discounts.
The discount amount willappear during checkout on the screen after the customer hasentered their shipping method. This allows Merchant toinclude (optionally) any miscellaneous fees or coupons redeemedon the Shipping - Payment selection screen so the subtotal willbe adjusted before the discount.
In admin you can setup eight separate groups withtheir own four-tiered discount and categories. Hence, if you want to discountone category of products with one set of rules (levels) and another categorywith a different set of rules, you can do this. Multiple categories can beassigned to each group. As the basket is scanned, the quantities are subtotaledfor each group. The discount is applied based on each group's rules, then summedtogether at checkout. You can optionally display the updated discounts prior to checkout in the regular basket screen, recalculatingand updating discounts based on changing basket contents.
In admin, you can chooseone price group, e.g. Wholesale, which is not eligible for the discount since theypresumably already benefit from significantly lower prices.
You can use the asterisk(*) to replace the category codes. When the module encounters the asterisk instead ofcategory codes, it considers all further products eligible. As example, the asterisk inthe first group would make all products in the store eligible for the discount. On the other hand,category codes in the first group would apply the first group rules to those categories.Then if there is an asterisk in the second group, all other products in the store woulduse those discount rules.
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.
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #5 includes the abilities to:
Begin_Screen & General
multinavbars.mv - Alternate Navigation Bar Menus. Will display a different Alternate HTML Menu for each screen. Displays normal Navbar for any missing HTML file files.
newframe.mv - Basket Contents Required Before Checkout. Checkout is called in NEW SCREEN. Useful to break out of frames.
bodyheader.mv - Adds a Perpetual Header to the Body of ALL screens.addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
Store Front Screen
nocattreesfnt.mv - Removes Category Tree from Store Front Screen.
Category Screen
adddesccatexp.mv - Places Description below quantity in basket on Category Screen Expanded Display.
addmorecatexp.mv - Add More Info Button to Category Screen Expanded. Displays either gif or grey button. Displays above "Add to Basket" and "Buy One Now" buttons.
addmorecatline.mv - Add More Info Button to Category Product Line Display Screen. Displays either gif or grey button. Displays left of "Add to Basket" and "Buy One Now" buttons.
addquancat.mv - Add Quantity and Box to Category Screen.
addthumbcatline.mv - Add thumbnail image on the Left End of the Category Screen Product Line Display
nocodelinknamectgy.mv - Remove "Code" and add a link to "Name" in the Category Screen Product Line Display.
autodefaultimg2X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 2.X ONLY.
autodefaultimg3X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 3.X ONLY.
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
Product Display Screen
autodefaultimg2X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 2.X ONLY.
autodefaultimg3X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 3.X ONLY.
autoimggifjpgprod.mv - Automatically displays either GIF or JPG images. No need to set path in admin. Displays a default image named notavail.jpg for Images not found. Version 2.X and 3.X.
autoimgjpgprod.mv - Automatically displays JPG images. No need to set path in admin. Displays a default image named notavail.jpg for Images not found. Only searches for JPG images. Version 2.X and 3.X.
autoimggifprod.mv - Automatically displays GIF images. No need to set path in admin. Displays a default image named notavail.gif for Images not found. Only searches for GIF images. Version 2.X and 3.X.
noattribqtyprod.mv - Remove Quantity and Attributes in Product Display Screen.
Product List Screen
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
addthumbplst.mv - Adds Thumbnail Image on the Left End of the Product Line Display on the Product List Screen.
nocodelinknameplst.mv - Removes "Code" and adds a link to "Name" on Product Line Display on the Product List Screen.
addmoreplstline.mv - Adds More Info Button on the Product Line Display on the Product List Screen.
Search Screen
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
addthumbsrch.mv - Adds Thumbnail Image on the Left End of the Product Line Display on the Search Screen.
nocodelinknamesrch.mv - Removes "Code" and adds a link to "Name" on Product Line Display on the Search Screen.
addmoresrchline.mv - Adds More Info Button to Related Products on the Search Screen.
Related Products
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknamerel.mv - Removes "Code" and adds a link to "Name" to Related Products on the Product Display Screen.
addmorerelated.mv - Adds More Info Button to Related Products on the Product Display Screen.
addthumbrelatedprod.mv - Adds Thumbnail Image on Left End of Line to the Related Products on the Product Display Screen.
noaddrelatedprod.mv - Removes Add to Basket from Related Products on the Product Display Screen.
nonamerelatedprod.mv - Removes Name from Related Products on the Product Display Screen.
nopricerelatedprod.mv - Removes Price from Related Products on the Product Display Screen.
nocoderelatedprod.mv - Removes Code from Related Products on the Product Display Screen.
Upsell Screens
dispthumbupsell.mv - Displays Thumbnail instead of Full Sized Image on the Upsell Screen.
nocodeupsell.mv - Removes "Code" from the Upsell Screen.
nowtupsell.mv - Removes "Weight" from the Upsell Screen.
Almost all of these Extension Modules are completely "Plug-N-Play". Designed/Written by Luray Williams.
If you are not using OUI version 3.11 or above you must upgrade to at least version or these modules may not run correctly. The latest version of Open UI can be downloaded at http://www.openui.org
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #4 includes the abilities to:
## Indicates user configurable in Admin through Sytem Extension Configuration.
Begin_Screen & General
cattreemouseover.mv - ## - Creates Mouseover effect on links throughout store. Colors and Fonts set in Admin Interface. Works in IE Only.
chgpriceall.mv - ## - Change the Field Label of Price on all screens. Your new label set in Admin Interface.
ifzeroprice.mv - ## - Eliminates display of $0.00 when price is zero. User can replace price with a message. Message can be email link that includes Product Code and name in the subject line. Create the email address. Select to display or not display "Add" and "Buy" buttons. Select which screens will be effected. Admin Interface control.
logoutcattree222.mv - Places logout link below customer name in the Category Tree. Merchant 2.22 only.
navbargone.mv - Remove Navigation Bar from top of display all screens.
nocattree.mv - Removes the Category Menu display from the Category Tree. Remainder of Category Tree functions still active.
nopriceifzeroall.mv - If price is $0.00 it will not display on any screens.
altnavbar.mv - Replace top NavBar with HTML menu. Works on all servers.
Category Screen
EZthumbCAT.mv - ## - Create your own Thumbnail Display on the Category Screen. Select the number of thumbs per row, whether other information displays to the right or below the thumb. Select Product Information you wish to display. Create additional Table to contain your display. Table features set in admin. Features selectable through Admin Interface.
addcodecat.mv - Adds Product Code to Category Screen.
addwtcat.mv - Adds Weight display to the Category Screen.
Product Display Screen
addtobuyprod.mv - Change "Add to Basket" to "Buy Now" and take customer to Checkout on Product Display Screen.
noqtybsktcodeprod.mv - Remove Quantity in Basket and Code from Product Display Screen.
popupimgprod.mv - Clicking on the Image in the Product Display calls a Popup Window 450 X 450 to display Detail View. Places "Click for larger view" below image. Images named with "Product_Code.jpg" are automatically called from the graphics/00000001 file.
Product List Screen
moreinfoplst.mv - Replaces "Add to Basket" and "Buy one Now" with "More Info" button that directs customer to the Product Display Screen.
noaddplst.mv - Removes "Add to Basket" from Product Display Screen.
nobuttonsplst.mv - Removes "Add to Basket" and "Buy One Now" buttons from Product Display Screen. nobuyplst.mv - Removes "Buy One Now" button from Product Display Screen.
nocodeplst.mv - Removes Product Code and Makes link from Product Name in Product List Screen
nonameplst.mv - Removes Product Name from the Product List Screen.
nopriceplst.mv - Removes Price from the Product List Screen.
Search Screen
noaddsrch.mv - Removes "Add to Basket" button from Search Screen.
nobuttonssrch.mv - Removes "Add to Basket" and "Buy One Now" buttons from Search Screen.
nobuttonsmoreinfosrch.mv - Replaces "Add to Basket" and "Buy One Now" buttons with "More Info" button that takes customer to the Search Screen.
nobuysrch.mv - Removes "Buy One Now" button from Search Screen.
nocodesrch.mv - Removes Product Code and Makes link from Product Name in Search Screen
nonamesrch.mv - Removes Product Name from Search Screen
nopricesrch.mv - Removes Price display from the Search Screen. Invoice Screen
nostoretimeinv.mv - Removes Time Stamp from Invoice Screen. OUI 2.60 and above only.
nostoreaddrinv.mv - Removes Company Name and Address information from Invoice Screen. OUI 2.60 and above only. Checkout Screens
altfieldscheckout.mv - ## - "Ship to:", "Bill to:", "Fax Number:" and "Company" field labels can be changed through Admin Interface. Changes display on all Checkout Screens and Invoice Screen.
noshipcheckout.mv - ## - Remove Shipping Selection Box and Shipping Price from all Checkout Screens and Invoice. Add your message as replacement through Admin Interface and select where to display.
Almost all of these Extension Modules are completely "Plug-N-Play". Designed/Written by Luray Williams.
If you are not using OUI version 2.45 or above you must upgrade to at least version or these modules may not run correctly. The latest version of Open UI can be downloaded at http://www.openui.org
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
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
The sorter module gives you the ability to sort your Miva Merchant categories and products very quickly from an easy to use, admin interface. The typical sort time for700+ products is 1-2 seconds. In the latest version of the module, you can also capture the number of products in each category for quick lookup at runtime for use in the category tree or other Merchant pages. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Sort categories by name, code or entry date - Sort products by name, code, price or entry date (ascending or descending) - Sort entire store or sort one category at a time - Sort products within categories by name, code, price or entry date (ascending or descending) - Categories do not all have to be sorted the same way - Move specific products to the top of the product list, search and category pages with a quick mass input - Display an image before the product name for products with a sort order number lower than the trigger number established by the store owner - Count products in each category for later display at runtime to reduce server load and page view time
Feature Details. You can sort the categories by name, code, or entry date. Many stores find that their categories are best sorted by category code rather thancategory name. This way they can create codes which will put their categoriesin the order they want. While most may actually coincide with category namesbeing alphabetical, stores can rearrange the categories to put things like "Specials"or "Close Out" at the top of bottom of the list. The customer does not see the category code, they only see the results of the sorted list.
The products can be sorted by name, code, price, or entry date. The product sorting can be done either as either ascending or descending. Moststores will sort the products by name. The very quick sort is done storewide with a couple button clicks. The storewide sort results in the products being sorted in all of the category screens, the product list screen, and the search screen.
You can sort the products within individual categories differently than the sorting in the store at large. So while the product list and most categories might be sorted alphabetically, you could have others sorted by price as ascending or descending. You can sort theproducts by a specific category and then on the next screen, make minor changes to re-arranged that sorting. This gives you the ability to move certain products to thetop for more customer visibility.
You can also move to the top of the list up to 999 product codes in the orderyou want them. They can appear before any other products on the product list, search and each category screen. This ability to assign a sort order number also makes it possible to display an image, e.g. new or hot, to all products with a sort order number less than the trigger you assign using a token.
You can also elect to count the products in each category. If you do, the counts willbe available at runtime in Merchant. By having the data in a quick lookup table, Merchant does not have to count the products in each category as it displays the category list in a 3rd party module's category tree. It simply shows the previously stored totals. This option cannot be used in stores which use availability groups to hide products fromsome customers because the totals would show the amounts for all products in eachcategory. The sorter module uses a token to display the products-in-category total after the category name if you are using a 3rd party category tree template module.
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.
In the compiled version of Merchant we have included
footsteps of customers' recent travels to the product pages in the store. The display remains closed unless the customer clicks the link for the recent visits, thus not taking too much space. When displayed, an Add to basket button can be included so the customer can easily add products which they had visited earlier and now they want
to add them without having to search or drill down though the categories. This reminder of pages visited lessens the chance of forgetting something before the customer checks out. The convenient links allows the customer to quickly go back and take a look at the products again. The
recent visit history will remain available for the length the store owner has set for basket timeout. Additionally, for your customers who login, you can have the history availability
extended for any number of additional hours, as they are more likely to return and make a purchase. The recent visit history can be included within the mini-basket table or outside of it. If you want to place the visit history outside of the mini-basket, you can use tokens in the header and footers of screens if you are using the OpenUI. We
have included a "view" feature in admin that allows the store owner to monitor live activity in the store. All recent product page visits are listed the admin screen. Customers not using cookies or whose browser is creating a different session ID with each page click will not be able to display their recent history, however the store owner will still be able to see the pages currently being visited.
