Found 694 Modules or Applications that might fit the bill
Use caution when considering any modules from modStop. Their support has been reported by umpteen Miva Merchant users as suspect and worse. Some of their modules are simple and shouldn't require support. Please contact us with any questions concerning them or their modules.
This module will set the category display to 10 products per page on ALL categories. Instead of setting the display number in the category set-up of EVERY category, you can use this little module.
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 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.
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.
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.
Older Modules Not Available Compiled! No Longer Available!
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #2 includes the abilities to:
Add Agreement Page before Checkout. The checkout button on the navbar and the Buy 1 Now buttons on the Category Screen, Search Screen and Product List calls an agreement page to which the customer has to agree or dissagree. Choosing agree takes you to login/checkout. Not agree takes you back to the storefront. Will display either image or grey button.
Create a horizontal display with no image. Displays Product Name, Description, Retail Price, Discount, Your Price, Weight, and Quantity. Retail price is controled as an adjustable percent of markup over price. Will display either image or grey button.
Add calculated Retail Price and Discount Price on Category Screen. Retail price is controled as an adjustable percent of markup over price.
Add calculated Retail Price and Discount Price on Product Display. Retail price is controled as an adjustable percent of markup over price.
Add calculated Retail Price and Discount Price on Product Display. Retail price displays the Cost Field.
Remove weight from the Product Display if the weight is Zero.
Remove the Place Order Without Account from the login screen and directs the customer to login on initial store access.
Redirect Add 2 Basket on Category Screen and Product Display to return to Product List.
Remove Price from Product Screen.
Move Product Description to Right of Image and Removes Weight from Product Display.
Add the Product Description to the Category Screen just above the addone and buyone Buttons.
Add Category Tree to Login Screen.
Add Category Tree to Search Screen.
Replace Code with hyperlinked Thumbnail on Product List.
Replace Code with hyperlinked Thumbnail on Search Screen.
Make Basket Contents Required Before Checkout on the Category Screen Only. Includes Basket Contents Continue Shopping and Continue Checkout links.
Move all text, attributes, everything below image on Product Display.
Reduce the Attribute Text Box display from 40 to 30 on the Product Display and on the Attribute Screen.
Leave shoppers in Basket Contents when clicking on Add to Basket in Product Display page only.
Create an Alternate Information display on the Category Screen below the Name. Alternate Information is entered in the Product Data Field separated from the Description by a ^. Product Display shows regular description.
Display a different html menu for each button on the Navigation Bar.
Buy Buttons go direct to Checkout on Category Screen and Product Display. No Quantity in Basket, Weight, Attributes or Quantity. Primarily for stores with few products or single purchase type items.
Create a Button Up-Button Down effect. If the alternate button exists it will display for the selected button. If it does not exist the selected button will not display.
Remove Price, Total Price, Shipping Cost and Sales Tax from Category Screen, Product Display, Product List, Basket Contents, Search, Invoice and all Checkout Screens.
Remove price only from the Category Screen.
Remove Add One To Basket and buy One Now buttons from Cagegory Screen, Product Display, Product List, and Search Screen.
Remove Category Tree and replace NavBar with message: Our Mall is temporarily closed for maintenance. Please check back soon.
Remove Price, Quantity and Add to Basket Button on the Product Display Screen if the price is zero. Displays Call for Price instead.
Remove Price, Quantity, Add to Basket and Buy 1 Now Button on the Category Screen if the price is zero. Displays Call for Price instead.
Create a horizontal display of all information and displays more products on screen. Will display either image or grey button.
Add Attributes and Quantity to Category Screen.
Place Click to Print for your Records button at the top of Invoice centered.
All extensions are designed to just Plug AND PLay in OpenUI stores. Designed/Written by Luray Williams.
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
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 Category Manager module allows you to have multiple category templates in a single store. You can have a different template for every category in your store if you want. The templates use the standard store morph technology template editor in MIVA Merchant 5. While basic knowledge of how to edit MIVA Merchant 5 templates is required, there are two example templates provided in addition to the built in ctgy page template. Getting started is not that difficult. Don't miss our introductory price of this versatile module.
Features: - Multiple category templates in a single store - One or more categories can be assigned to use a specific template - Default template is used for categories which do not have a custom template assigned - Custom pagination in addition to the default Previous and Next buttons - Can limit products displayed per page to a specific number for each template or can list all on one page - Customer can sort products within the category in real time dynamically - Breadcrumb navigation included - Sub-category navigation included
Feature Details. Multiple page templates. Using the built-in store morph technology, you can edit the page templates just like the built-in page templates, including recall, notes, and indexing of previous versions. Include typical render tokens on the custom category pages from other 3rd party modules (sold separately) which you have in your store, e.g. rate this, wait list, best seller, and others.
Easy assignment of categories to templates. Once you create the template you can assign one or more categories to it. This can be done from the Category Edit screen or if you are using the Emporium Plus Category Import module (sold separately), you can import the template assignment right along with importing new categories into the store. No need to import the categories with one module and then use a separate module to assign them to templates.
Default page for unassigned categories. The default ctgy page template is used for all categories which have not been assigned to a specific custom template. This makes processing more efficient as the Category Manager runs a quick lookup to determine if it needs to run certain more complex processing routines, like advanced pagination.
Advanced page navigation. Several pagination variables are available to write detailed page navigation links. You can have the typical 1 2 3 4 etc. Or you can break up long lines with arrows, dots, dashes, etc to fill in a gap. You can also display the page number of the total number of pages. This pagination is similar to that used in the Emporium Plus Power Search module for Merchant 5. As a point of reference for the customer, you can even include how many products are listed in the category.
Flexible pagination. Each category template can have a different setting for the number of products to display on a page. Initially, the customer will see the number you set. However, customers using broadband may want to see all the product in a category on a single page, so there is an option to list all.
On-the-fly sorting. The products are initially displayed in the sort order which the store owner has previously setup in the normal admin sorting. The customer can then change the sort order based on their desires. Available sort fields are name, code, price, date items were added to the store, or the default store setup. They can be sorted ascending or descending.
Breadcrunb navigation. The module includes optional breadcrumb navigation. An array is created which holds the current category name and its parents up to the top level category. With standard MIVA Merchant template code, you can create a quick link to higher categories like Home > Software > Developer Bundles
Sub-category navigation. You can display the sub-categories of a parent category on the category page, e.g. below the parent category's name. The array can be displayed like you want it using standard MIVA Merchant template code.
We cannot link to our demo stores from MivaCentral so if you'd like to see a couple of the live pages demonstrating single or multiple column layout of products, please contact us for links. Those pages demonstrate the variable layout of products, breadcrumb navigation, on-the-fly sorting, and sub-category navigation.
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 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 for 700+ 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.
Features:(some features are only in the compiled version) - 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 (openui hook point or token) 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 (openui token) 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 than category name. This way they can create codes which will put their categories in the order they want. While most may actually coincide with category names being 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. Most stores will sort the products by name. The very quick sort is done storewide with one button click. The storewide sort results in the products being sorted in all of the category screens, the product list screen, and the search screen.
Compiled version additional features: New in the compiled version for Merchant 4.14 and newer, 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 the products 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 the top for more customer visibility. You can also list up to 999 product codes in the order you want them and 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 OpenUI hook points or tokens. You can also elect to count the products in each category. If you do, the counts will be 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 the category tree. It simply shows the previously stored totals. This option cannot be used in stores which use availability groups to hide products from some customers because the totals would show the amounts for all products in each category. The sorter module provides OpenUI hook points to display the products in category total after the category name. To use that option, your store needs to have the OpenUI installed. Alternatively, the module has a token which can be run by other 3rd party modules to report the products in category totals. That method may or may not require the OpenUI, depending on the module which is going to use the token. If you have OpenUI version 4.935 or newer, the Sort Categories and Products link appears in the upper admin menu under the Categories and Products headings.
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
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 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.
Discount your product prices based on the number
of items ordered of identical products, eg 1-3 =
standard price, 4-6 = lower, etc.
The admin interface provides an easy to enter "from - to cost" format. You can literally have as many ranges as you want to type in. See the image below for example syntax. You can either use actual values or percent of price to be subtracted from the product price. These price differentials are added directly in the admin interface under the product edit screen. You only apply these price differentials in the products that you want to use them.
This module applies the price in your low, high, cost groupings. If you do not include a grouping at the single item level, it will use the method for pricing in your store. It only activates if you include a low, high, cost grouping.
For example: 6|10|12% 11|20|14% 21|999|16%
The module only uses price groups when using the percent off discount calculation. If you enter fixed prices for the quantity ranges, then price groups are ignored. Keep in mind that the percent discounts will be over and above the discount already given if you are using price groups.
In the compiled version you can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volume
pricing and hide the table from them completely. Customers
must be logged in to identify the price group they are in before
the volume pricing module can disqualify them from volume pricing.
The percentage discounting method subtracts the percent discount from the base price. Base price does
not include attribute prices. To apply the percentage,
simply include the percent symbol (%) in the line. If
you are using cost method for your store (other than
price groups), you will not be able to use the percentage
discounting method. Instead, use the actual value method.
If you are using another third party module which overrides prices in the basket and recomputes them using the price in the product record, you will not be able to use this module. Other third party modules will not
recognize that it needs to apply the calculations in this module.
The module recognizes identical products. Hence different attributes will change the product enough that the discount won't apply. For example 3 red shirts and 6 blue shirts will not give the discount of 9 shirts. Rather, they'll get the discount rate of 3 for one of the line items and 6 for the other.
The module for the compiled version of merchant DOES have the ability to amalgamate quantities so in the example above as long as the product code is the same, all 9 items would get the volume discount for 9 items. You have the option for each product code to amalgamate quantities or treat varied attributes as different products.
You can optionally include a table on the product (PROD) and category (CTGY) screens displaying the rates as generated from the products' volume discount record. You can see an example of that with our best seller products. You can optionally have a quantity input in that table display. These options are configured through admin.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the table display on the product page so that it better fits your desired look. New configuration options added for the table display. Also, the ability to display the lowest price in place of the standard price when volume pricing effects the product, the store is using the OpenUI, the store is version 4.14 or higher, and there are no other 3rd party modules effecting the price display. This feature is useful if you want to have a sale on one or more items. Simply set the volume to 1 or more with a specific discount percentage and you have a sale with as low as display. You can use the token %product_price_f% to further highlight that with a strike thru. To make this feature even more useful, you can enter a starting and ending date for the sale so that it will start and end automatically. For ease of entry, a flat file import module is included. You can put all product codes in the flat file or use an asterisk (*) and one line of "rules" to apply the volume price to all products in the store. Create a storewide sale, e.g. 10% off in seconds with a specific start and stop date. Then just as quickly remove all settings at your leisure after the sale. There is also a volume price export so you can
quickly build your flat file, then edit or add to it. This
is useful when you want to have a storewide sale on all products but retain volume prices on your regularly discounted items. Export the volume prices. Import your sale settings. Import your volume discounts on the few you want to maintain at
pre-sale prices. The volume price can also be used in our compiled
Fast Data Feed module for
froogle submissions and our
Static Catalog Generator which creates static html pages for better search engine indexing.
Implement customer product ratings and reviews within Miva Merchant. The 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: - Rate with a numerical/verbal score for each product - Review each product with narrative critique - Customers login prior to rate and review - Configurable message if not logged in - All customers can view ratings/reviews without logging in - Limit customer to one rating/review per product - Customer can edit their prior rating/review of the product if logged in - Ratings are averaged and graphically displayed - Graphics display on product and/or expanded search, category and product list screens - Store owner can replace default heart images with their own - Optional email notification to store when new rating is made - Auto-approve or admin approve before allowing display in the store - Admin reports for easy deletion, analysis, and approval - Admin reports to screen, export to flat file, and optionally email flat file to store - Easily remove malicious customer prank ratings - Easily remove all ratings by a specific customer account login - Easily remove ratings/reviews of a specific product code - List all unapproved ratings/reviews for easy approval of one or more - Summary report for all ratings/reviews on a specific product - Summary report for all ratings/reviews by a specific customer - Admin reports with hot links of the customer logins so you can quickly view rater details - Sort the reviews in the order you want them displayed - Module comes with default layout for both the entry form and display - Easily replace the default layout with customizable template entry form and display - Use render tokens for placement of display and/or prompt in the page template screens - Optionally use tokens in the display template for listing the rater's identity - Allow customer to include identity with their email, name, or location (automatically filled in from their customer account) - Exclude specific product codes from being rated - Integrate with the Emporium Plus Mail Manager module to send a promo email to the ratee, thanking them for the rating - Limit number of reviews on the product page with a "more" link to show all - Licensed by domain without need for multistore license if same domain
Feature Details. The purpose of Rate This module is to allow customers (who have signed in) to provide their rating/review of products offered in the store.The module allows a customer one review on each productthey choose to rate/review. They can go back and change their rating and review as it is controlled by their login and password. The average customer rating is displayed graphically with whole or half images. This graphical display can be on the product screen, the category listscreen or both. The default images are hearts, but the mall owner can substitute any graphics he/she wants. Customers can also leave narrative comments about products they wish to review.
All customers, not just those logged in, are able to view the ratings and reviews made by other customers.
In the event that a malicious customer enters prank ratings, the admin interface allows removal of all ratings by specific customers. Since the module has an email alert feature (if turned onby the store owner), you will know what ratings are being left for your products. There is also a report generator to list all ratings on a specific product code or all ratings by a specific customer.
You can also display and/or delete the ratings of a specific product from the individual product edit screen.
Using a render token, place the Rate This button on the product page so that it better fits your desired look. You canlimit the number of reviews which appear on the product page with a "more"link to show all. You can sort the order of the reviews within the product edit screen so that customers see the reviews in the order you want them seen. You can also require admin approval before the rating/review is displayed to customers visiting your store. Admin reports can be displayed to screen, exported to flat file, and optionally email the flat file to the store. The admin rating reports which display the login have a hot link to the customer login so you can quickly view who the rater is.
Configure through admin, the text and tokens in both the display and prompt for this module as they are customizable templates which can replace the default layouts. You can allow the customer to include their email, name, or location (automatically filled in from their customer account) along with the reviews, depending on the demographicyou choose to allow in the store. As example, a typical rating might be Reviewer: John in Anglikon, Switzerland 05/14/2001 Great tool and simple to install
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.
You've got your store spidered by the search engines, you're showing up in the search engine results, but you just can't seem to improve your rankings...Search Engine Tweak Pro (SETPro) is here to help!
Search engines take into account many factors when ranking web results, and one of the most important is proper page content optimization. Miva Merchant's dynamic page creation is not designed to be search engine friendly with how it creates and displays the page content. This is where SETPro comes in to play with a number of optimizations and enhancements for product and category screens. These optimizations are primarily done with the Google search engine in mind, but are also relevant to most other popular search engines.
PRODUCT SCREENS:
Product Name Tags:
Allows you to set the product names on the product screens to a preferred heading tag, bold, or none (
,
,
,
, ).
The keywords to focus on for an individual product page are typically contained within the product name. Making the product name a larger font size using the heading tags, compared to most of the other page content, adds extra weight to those keywords when rankings are determined.
Remove Store Name In Product Title Bar:
Optionally strips out the store name in the product screen title bars.
Page titles are extremely important to search engines. Miva Merchant adds the store name in the browser window's title bar along with the product name. This is a good thing, but it may also make it undesireable by diluting the product name keywords with an unnecessary store name, thus giving less weight to your keyword focus.
Product Description at Top of HTML Body:
Optionally placed at the very top of the page, just after the
tag in the page code, this displays the product name followed by the first 200 characters of the product description. Any HTML used in the description is stripped out before being displayed at the page top.
Stock Miva Merchant nests a considerable amount of hidden tables within one another. It makes for an adequate display but search engines don't see page content as the viewer does. That creates a large amount of page code that pushes the product descriptions far down the page, even possibly tripping up some older search engines. It's best to have your real keyword content as far up the page code as possible, creating more keyword weight and improving relevancy for the product pages. It's recommended to use either this option or the commented out feature described below, but not both.
Commented Out Product Description at Top of HTML Body:
Optionally placed at the very top of the page, just after the
tag in the page code. This option adds the product name followed by the first 200 characters of the product description text, commented out (hidden from view). Any HTML used in the description is stripped out before it's added to the top of the page code.
This is the same as the product description display above, except that the description and title are commented out, essentially invisible, at the top of the page. Most search engines will ignore comment tags but some may take them into account. This is an elegant alternative to actually displaying the product name with description at the top of the page, leaving the page as it's meant to be displayed. It's recommended to use either this option or the displayed product description feature described above, but not both.
CATEGORY SCREENS:
Category Name Tags:
Allows you to set the category names on the category screen, to a preferred heading tag, bold, or none (
,
,
,
, ).
The keywords to focus on for an individual category page are typically contained within the category name. Making the category name a larger font size using the heading tags, compared to most of the other page content, adds extra weight to those keywords when rankings are determined.
Remove Store Name In Category Title Bar:
Optionally strips out the store name in the category screen title bars.
Page titles are extremely important to search engines. Miva Merchant adds the store name in the browser window's title bar along with the category name. This is a good thing, but it may also make it undesireable by diluting the category name keywords with an unnecessary store name, thus giving less weight to your keyword focus.
Product Links in Line-Item Listings:
Optionally replaces the product name with a linked product name, when a line-tem listing is used. This is mainly for category screens, but also applies to related products, search results, and product list screens.
Search Engines add additional keyword weight to pages using those keywords contained in incoming anchor text (links) from other pages.
Product Short Description in Line-Item Listings:
Optionally adds a short product description under the product name when a line-item listing is used. Mostly used for category screens, but also applies to related products, search results, and product list screens when line-item formatting is used. Choices are:
None
Product Description (First 200 characters with stripped out HTML code)
Product Short Description (Displays from the OpenUI Short Description Field)
Particularly helpful with non-descriptive category screens or related product areas, by adding more useful content for search engines to index. Also useful for adding varied keyphrases by use of the product's Short Description field.
Sort related products on the individual product page display. Miva Merchant has a feature which allows you to include products that are related to a specific product on the page of that specific product. Hence, if a customer is interested in one product, he or she may see other products that would be of interest or that work well with the primary product they are looking at. Unfortunately, Miva Merchant out-of-the-box just lists those products in random order. You can sort products in Miva Merchant either through the tedious manual admin sorting or you can use our Sort Categories and Products module. Either way, the Sort Related Products module will inherit from that sorting order defined by the store owner for the rest of the product sorting in Merchant.
This module is for OpenUI only. It works with standard OpenUI and Luray William's Related Products Line Layout Display.
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.
The Search Friendly Links module replaces the links in the category tree and category pages of Miva Merchant with “short links” that are more search engine friendly. Miva Merchant uses long links with 4 variables. Some search engines will not follow these links while they will follow shorter links with fewer variables.
Key Benefits
Generates short-links in the category tree and category pages in Miva Merchant
Interprets short-links from any web page or email
Benefits of shorter links
Short links are generally more likely to be followed by Search Engine spiders
Easy to write (and remember) direct links to products and categories in your store
Long links may word-wrap in some email systems, causing them not to link properly
Shorter links are less likely to word wrap
Search engines frequently will not read links with multiple variables (a.k.a. “long links”) such as those produced by Miva Merchant
A typical Miva Merchant link such as:
http://www.yourstore.com/pathto/merchant.mv? Store_Code=ST&Screen=SFNT&Category_Code=CTGY1&Product_Code=PRD1
The reduction in the number of variables helps with search engine spiders
Short links are always interpreted and understood by your store when the module is installed and turned on. Therefore, any “short” external link can be used even if you have turned off the display of the short links.
Long links are always interpreted and understood by your store; so previous search engine listings and external links continue to work normally.
The “display” of the short links in your store can be disabled, though the store will continue to interpret the short links from external sources (ie: the companion product Search Friendly Store Map, emails and mailing list, etc)
The Search Friendly Links module can produce best results when used in conjunction with the companion product Search Friendly Store Map. The store map product will generate a static HTML page containing Search Friendly Links to every product and category in your store! Search engines tend to give static HTML pages (and the links on these pages) higher precedence and ranks. When used together, these two products generally enhance search engine positioning.
New In v4.02/v4.52:
Directory Style Short Links: http://www.yourstore.com/page/SC/PROD/CAT1/PROD1
OpenUI Token and Copernicus OpenUI SuperMod Template Compatible
***NOTE: In order to generate the short links with only one variable, each of the included variables are separated with a forward-slash ("/") character. Thus, no category or product should have this character in the category or product code.
Example Usage
A storefront owner that sells cakes and jelly beans online wants to improve the search engine positioning of the store. He has an attractive storefront and has made it very customer friendly (yep, you guessed it – he’s using the Copernicus Customer Service Suite) but the only shoppers who come to his site are repeat customers who originally heard about his site through “word of mouth.” He knows that if he could just get listed in the major search engines he could increase his sales, but he can’t understand why his site has not been “spidered” by the search engines. He’s not ready to “pay per click” with search engines like Overture, he just wants to get listed.
As a result of his frustration about his search engine placement (or actually, lack thereof), the storefront owner has been learning a lot about search engine optimization (SEO). He has learned that the reason his website has no placement on the search engines is because Miva Merchant produces dynamic pages with links that are not read by the spiders and robots sent out by search engines to find websites. The links are too long (those spiders are so impatient!) and spiders disqualify them due to having too many variables. Of course, he knows that it’s also very important that his pages are full of good content that can be easily logged by the search engines.
The Solution: The Search Friendly Links module will quickly solve the long links problem that this storefront is having. The Search Friendly Links module turns the long links for each category and product page into “short links” that are easily read by those spiders and robots. Further, he likes to make posts to the “Dessert-lovers” email forum; but every time he posts a link to one of his products, the links are so long they “word-wrap” and become un-clickable! So he installs the Search Friendly Links module, and starts posting short links to his products. Now his links look better in his store and his email, and the spiders are happier too!
Image Wizard Pro goes beyond the standard Image Wizard Standard Module, giving you more options and flexibility for your Miva Merchant store. The Pro version allows you to display up to 10 product images on the product display screen, and provides additional options for the standard Miva Merchant product screen and related products listings.
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.