Miva Merchant Modules and Applications Search

• 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.

Price: $45.00 Upgrade Cost: $0 Upgrade Terms (If Any): N/A
Compatibility: N/A Versions: 5.x+
Other Module Compatibility: N/A

From: Coupon Modules
Relevance: 82.67%%

Rating: (0) Votes: (0) Hits: (821) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Coupon Redemption v5 <-- Just click this link and then add to your favorites!

4 Hide Prices Pending Customer Approval - Professional Version Latu /

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
• Fully-customizable, template-based merchant notification & customer notification email messages
• 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
• Admin-Friendly navigation - quickly sort, search, approve, edit & delete customer records
• Optional merchant email notification sent when new accounts created by customers
• Optional customer email notification sent to the customer upon approval of account

Professional Version also available.

Module Configuration Screens

Display & Messages Email Notification Attributes & Options

Admin Utility Screens

View & Select Customers Customers Approval View & Select Customers (customer approved) Create New Customer

Store Screens

Price Message (product list & categories) Price Message (product display) Customer Message (customer account) Pending Message (all screens)

Compatibility

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

Installation & Configuration Instructions

Token & Template Information

• Email to any of your drop-ship manufacturers listing the Ship To address and the products to be shipped if using real time creditcard authorization. The module will sort out which drop shippergets which emails, including listing the products to be shipped. Unlike some other vendors' drop ship notification modules, this one only includesthe products belonging to the associated drop shipper. Thus a drop shipper doesnot see the products being supplied to the customer by other drop shippers when the order contains multiple product sources. Youcan still use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processingverified the charge, then forward to the drop shipper. This would savehand entering the order. In addition to the email, an archive flatfile is created which you can use to easily track sales activity related to each of your drop-ship manufacturers.
• Email to Ship To or Bill To or both thanking them for a donation to your sponsored charity on your site.
• Email to your shipping department listing Ship To addressand products ordered if using real time credit card authorization. Products section can be cut/folded to result in a shipping label with your company address included. If notusing real time authorization, use the pending mailbox technique similarto the drop shipper scenario above.
• Email a promo coupon code if a customer purchases a specificproduct or from a list of products
• Email service, warranty, shipping and contact information on specific products or product lines
• Send an email to your cell phone's inbox when orders are placed in your store (requires a cell phone plan that assigns an email address to your phone).
• You own a mall with multiple stores within the mall. Thosestore owners rent the stores from you for a percentage of their gross. Use mail manager as an audit tool to track theirsales. In addition to the autoresponse email, mail manager produces a flat file with order ID, date, product name, product code, quantity, price for each, and price extended. Periodically retrieve that flat file and import into a spreadsheetfor easy analysis.
• The included Mail Manager Report module can display the contents of that flat file through admin. It can filter the report by specific timeperiods (daily, weekly, monthly) within reason. The limits of your PC or server may prevent very lengthy reports for excessively long time periods. It can also limit the report to only one product code. Since the templates canbe designed for each vendor, you can create individual vendor flat files with a corresponding report for each vendor.
• Literally, you can have a different autoresponder for everyproduct in your store.

However, Mail Manager has a somewhat open architecture sothat other events can also trigger an automated response. For example:

• Send a welcome email before the order completes, but afterthe customer completes the registration process (for those thatcreate an account)
• Send a thank you for rating a product (using our Rate This system)along with a coupon code for taking the time to do so
• You can use the ifvar script or var token in these "other event" emails. For example, generate a unique coupon code with a module token and insert it in the welcome email to give the new customer an incentive to buy now.
• Use a render token to send an email from any page in the store. For example, put it on the product page to send a specific email when a specific product's page is viewed by a customer who is logged in. The email goes to their password recovery address (but could be bill to or ship to address). If you want it sent to a hard coded address, e.g. yours to monitor traffic,you would put your email address in the 3rd parameter of the token. The uses of this feature are endless. Send a coupon to entice customers to buy when they visit specific product screens. Tell them about other products related to the one they just viewed.

As you can see, the uses of this Mail Manager are quite diverse. Some of the variable features configured through admin for each template are:

• Show or hide any of the data elements
• Orient your email either horizontally or vertically
• There is also a free form template using an extensive list of tokens and mini-scripts to customize the emails that are sent at the time of order completion. They can vary from mimics of the standard merchant notification and customer confirmation emails to brief order notifications for better acceptance within cell phone emails. The emails can be plain text or HTML formattedemails for better readability. You can change the fonts, colors,layout and even add images to your confirmation and notificationemails. If your shipping and payment modules are configured withinvoice notices, these can be included in the emails with a token. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create packing slip and label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template. In the free form template you canalso set the time so that it can be offset from the server time,thus display for a different time zone in each of your emails.
• Customize your email and store's physical address
• Designate email recipient, i.e. Ship To and/or Bill To and/or fixed email address
• List full or partial Ship To and/or Bill To address
• Restrict email to a specified order dollar value range, reward big spending customers with a coupon for their next visit
• Restrict email to a specified list of countries, thus allowing for language specific emails
• Resend order emails if the customer knows and enters the order number and email which match the actual order. The form for these two data elements can be placed anywhere you can edit the store user interface, e.g. headers, footers, welcome screen.
• You can specify the product code and an attribute/option value that must also be met before the email will be sent. This is particularly useful when the emails are used for vendor notification. A certain product might bedrop shipped by two different vendors and the only difference is the selected attribute/option value.
• Insert a "require" token that has to be met before the email will be allowed. As example,have a checkbox using Addendum to ask a customer if they want to be added to a list server (mailing list). Then if they check the box, the "yes" response is sent to Mail Manager. The Mail Manager can then generate a specifically formatted email to activate an email address at your list server, if you have one.
• Write a different body for each of the email templates you add
• List products and prices or just the products without prices
• Link the email usage to one or more product codes or entire inventory with wildcard
• No need to go to each product to link the email, a copy and paste froma flat text file will add hundreds instantly

I'd be surprised if you find that this capability exists anywhere in any mid-priced shopping cart system. Autoresponders that fill in the blanks are one thing, but this is a store owner, pre-planned autoresponse for a specific product. Within your store, you could have dozens of different responses (individual or grouped) or a wildcard response for all of the products. You can use itto make connections not directly related to sales, yetlinked to a specific sale.

• Customer buys a kayak from your store. Tell them about the kayak camp 20 miles from your store and give them the 800number of the guy with the info about a big get together next month.
• Customer buys an orchid from you which would lead you to believe he/she may have a specific variety you have been looking for. You autorespond with your want list for your nursery inhopes of finding the needle in a haystack.

As you can see, this list could be endless. Targetted, intelligent autoresponders are designed to increase your store'sbusiness and decrease the amount of time employees spend on sendingout product specific, emails.

The pre-formed templates are easy to configure and do not require programming experience. For the more experienced, you also have the option of using tokens and mini-scripts in free form templates. An example free form template is included with the install documents.

Price: $45.00 Upgrade Cost: $0 Upgrade Terms (If Any): N/A
Compatibility: N/A Versions: 5.x+
Other Module Compatibility: N/A

From: Customer Management Support Modules
Relevance: 71.84%%

Rating: (0) Votes: (0) Hits: (657) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Mail Manager v5 <-- Just click this link and then add to your favorites!

7 Power Search Weiland / Miva Central

The Power Search module is a plugin module which implements field specific, keyword searching within a Miva Merchant 2.x storefront. License is for ONE mall. Within that single mall, it can be used in multiple stores without additional license.

The purpose of powrsrch.mv is to allow a customer to search one or more fields which are made selectable by the store owner. The store owner can choose any fields within the products.dbf structure to be available. If you have an altered products.dbf structure, it will even allow selection of those additional fields (see screen shot below).

You can also exclude a word or phrase. An example of an exclude word usage might be: You sell health food but want the ability for customers to NOT list ingredients they are allergic to. So in the product name field you might have Soup. Then if you have a field in your database called Ingredient the customer could check the name and ingredient fields for searching. In the keyword input they would put soup. In the exclude input they could put MSG. It would search both fields. If it found soup in either it would compile those products to the list. But if the word MSG appeared in either field, it would remove it from the list.

Specific category, if selected, allows one category only searches. This feature may be too intimidating if you have hundreds of categories as the pull down select would be quite long.

New for the compiled version is the ability to specify a price range for the search. Also, in the compiled version we added the ability to display links to numbered pages when the search results exceed the number of matches displayed on a single page. You can use OpenUI Tokens to place the search form in several locations in your store. You also have the ability to replace the default form with one which you design with your own html (for those who know how to write html forms). The alternate html form can also be placed at one of seven different locations on the storefront screen. You'll use the default form as a template and can then add your own layout to improve the look and feel. Also if you are using the compiled Power Search AND the compiled Tell A Friend module, customers can send the search string from Power Search to friends. The store owner also has the ability to allow customers to search the category headers and footers for the search word. Because this may slow the search, you should only use it if your store has a moderate number of categories, e.g. 100 or less. Faster servers may get decent search times with many more than that though. Added new search algorythms "Any of these", Exact phrase", and "Start at beginning". Store owners can create a list of words which will not be searched in the "All of these" or "Any of these" searches. These are words like a, an, the, and, or. It will not exclude those words in the "Start at the beginning" or "Exact phrase" searches. If you choose to use the "search single category" listing, you can modify that from the admin control panel and only list certain categories in the select list, but provide searches of all of their sub-categories. This top down search adds greater flexibility over how broad you will allow your customers to filter the categories. After going to the product page from a Power Search rendered search, a convenient "return to search" link on the product page will bring the customer back to the original search page if using OpenUI.

Power Search (version 4.63) has been tested with OpenDB (version 2.2) and is compatible. In tests by James at Copernicus, the Power Search improved the performance of the already, very fast, SQL searches.
118k products in the database, 2456 categories, two search terms "PC133 RAM"
- Normal Miva Merchant Search: ~60 seconds
- OpenDBv2 Standard Search: TT time=07s0620u
- OpenDBv2 Power Search (limit to code, name & desc fields and no category specific search): TT time=05s0259u

For store owners who have found their searches take too long, you can reduce the search time by only searching one or two fields. The Merchant default is eight fields, including fields such as weight. Now, how useful is that? Finally.... the store owner has control without editing the db.mv code library.

The total number of products found is displayed along with the list of products matching the search criteria.

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. Additionally, it helps you identify keywords which might be useful to include in the narrative descriptions or the meta tag for search engine submissions.

This module works with both the MMUI and OpenUI User Interfaces (versions 2.22-4.x). If using the MMUI, six edits in the mmui.mv file are required, and one optional edit if you want to remove the archaic standard Merchant, keyword search. If you have compiled Merchant (4.14 or newer) that requires editing and re-compiling, so for compiled Merchant, OpenUI is required unless you have the compiler license. If you are using the OpenUI, Power Search plugs into the OpenUI without editing OpenUI modules and there is no need for compiling in Merchant 4.14 and newer.

See the screen shot below, then check out the selected field search in our store. We have about 600 products in our store so you can get an idea of search speed on a moderate speed server.

The Power Search function can also be used for pre-defined form pulldowns in your store. As an example, the genre and decade searches on the left side of this screen 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 products.dbf.

Price: $25 Upgrade Cost: $15 Upgrade Terms (If Any): N/A
Compatibility: OpenUI Versions: 4.x, 4.14.x and Above (Available Compiled)
Other Module Compatibility: N/A

From: Store Search Modules
Relevance: 61.73%%

Rating: (0.00) Votes: (0) Hits: (1482) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Power Search <-- Just click this link and then add to your favorites!

8 Wait List Manager Weiland / Miva Central

Customers can identify products that they would like to purchase but are currently out of stock. Once you place the product in stock, you can run the Send Email routine from the admin interface. It sends an unlimited number of notifications as one process, using Miva Engine functions to prevent timeout. Each waiting customer will receive an email telling them that the product is back in stock.

If you are using my Inventory Management (IM) module (version 2.x or 3.x) or Miva's Inventory Management (version 4.x), the wait list manager will automatically insert the Wait List link on the product page when the quantity is zero or less (version 2.x or 3.x) or out of stock (version 4.x configurable on a product by product basis). If you have modified your IM (version 2.x or 3.x) to allow ordering at less than zero to a specified lower amount, you can modify the Wait List Manager to account for that. In 4.x, this is determined by the global default or individual product's "out" setting. You can even block the automatic link insertion by including the product code in the blocking list through the admin interface. If you are not using an Inventory Management module, you can still use the Wait List Manager by manually inserting the link into the product description of products you want to "Wait List". In the case of "other" inventory management systems, you can insert the link into the code that those systems generate for out-of-stock messages.

When the customer clicks the Wait List link they are taken to a form to verify/enter their email address. If they are logged in, it inserts their email address for them. If not, they just type it in. The form also lists the number of other customers waiting for the item if that number is 5 or above (just to the right of the product name). This will give customers a sense of urgency when they receive the in-stock notification. When they add themselves to the list, you have the option (in admin) of sending them a thank you (for their interest) email. If you employ this option, it will also tell them their position on the Wait List. When products are in short supply, that may be something your customers would like to know. Also, if they are already on the Wait List, and sign up again, it will not duplicate their record, rather it will email them that they are already on the list and what their current position is on the list.

The admin configuration screen allows you to vary the name and/or image associated with this program so you aren't locked into the term "Wait List". You can also change the colors and fonts in the form along with the verbage in the form and notification email. You may even want to pass on a coupon code in the notification email for customers who have been waiting for a product.

When editing an individual product in admin, you can also display all of the Wait List records associated with that product. They can be deleted manually in this screen if you don't plan to restock the item. There is also a handy link for mailing them to verify their continued interest in the item. For those not using an Inventory Management, this is also the screen that allows you to use Wait List to notify customers when an item is re-stocked. The Inventory Override works with either no online inventory system or inventory systems from other 3rd party module providers. Naturally, it also works with mine (version 2.x and 3.x) and Miva's (version 4.x) inventory systems. You can even limit the notification in this screen to just some of the waiting customers. This is useful when you only receive a small number of the out-of-stock item and there are many more waiting for it. Since the entries are arranged in order, it is easy to give those on the waiting list the longest, the first shot at the newly re-stocked item.

You can quickly get a summary of all of the items on "Wait List" to provide you with a re-order, based on demand, tool.

When you Send Email, the module searches all products with a stock level (if using mine or Miva's Inventory Management systems) above zero and checks the product code against the Wait List database. Pending Wait List customers are notified of the re-stock of the product and their Wait List record is then deleted.

This module works with both the Miva Merchant and OpenUI look and feel user interfaces. Minor editing is required if you are not using the OpenUI.

To help the store owner identify needs quickly, an optional CC email can be sent when an item is wait listed.

In the compiled version, you can use this module with the standard MMUI, as mmui.mv edits are not required in Merchant versions 4.14 and newer.

New in the compiled version is an alternate template form for the customer to enter their name and email address. This template can be HTML customized to suit your look and feel. If you are not skilled at coding HTML, you can still use the default (built in) form which is customized with colors, fonts, etc with easy inputs in admin.

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 like those provided by Viking Coders. Place the wait list button on the Merchant pages so that it better fits your desired look.

Version 2.x, 3.x Available

Price: $25 Upgrade Cost: $15 Upgrade Terms (If Any): N/A
Compatibility: OpenUI Versions: 4.x, 4.14-4.16x (Available Compiled)
Other Module Compatibility: N/A

From: Coming Soon Wait List Modules
Relevance: 56.68%%

Rating: (0.00) Votes: (0) Hits: (1324) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Wait List Manager <-- Just click this link and then add to your favorites!

9 QwkPatch 4TheBest.Net / Miva Central

QwkPatch protects merchants against various Miva Merchant bugs, such as duplicate order numbers, and exploits and validation limitations, such as hackers being able to checkout without paying, by doing additional system checks at various points during the shoppers visit in the store.

QwkPatch has a fully configurable error screen which accepts a token for display of the specific configurable error message returned when a given patch is triggered. For 4.x the error screen even automatically includes the normal page wrap, such as the global header, footer, and navigation for whatever user interface module you have installed.

Current QwkPatch Release: 2.00

Miva Merchant Compatibility: 2.22 - 4.22

QwkPatch has been extensively tested on Miva Merchant versions 2.25, 3.02, 4.12, 4.13, and 4.22. QwkPatch should work on all versions above 2.2 baring possible unknown bugs in various versions of Miva Merchant. On 2.x versions below 2.2 some of the patches may still work, but due to API limitations, and general instability with Miva Merchant versions below 2.2 we can't support use of the software on versions below 2.2. So if you want to try it, you do so at your own risk.

Miva Merchant 1.x can't use the software at all, because the API simply doesn't support it. So if you have a Miva Merchant 1.x store you want protected, you would have to have custom modifications done.

QwkPatch 2.00 Patch List

• Patch 1 - Payment Module Installed Check
  This patch does a check to make sure the payment method submitted for payment authorization is for a valid module installed in the store. Without this patch it is possible under certain circumstances for shoppers to bypass the need to enter in any payment information such as a credit card number, and skip right to the invoice. Without the patch you must therefore be very careful to manually cross reference all your orders to make sure you don't ship something that wasn't paid for. Also if you do any sort of electronic fulfillment, such as selling software, images, etc. then shoppers using this exploit would get the products before you even noticed there was a problem. This patch is not required if you are using Miva Merchant 4.16 or higher.
• Patch 2 - Add To Basket Availability Group Check
  This patch stops shoppers from being able to add an item to their basket that is part of an availability group they don't belong to. Without this patch it is possible for a shopper to add such an item to the basket, even if they haven't created a customer account, much less been assigned to the availability group.
• Patch 3 - Upsale Item Manual Basket Add Check
  This patch stops shoppers from manually adding an upsale item to their basket. If you use upsale you probably have worked hard to make sure certain free, or steeply discounted items are only presented to the shopper during checkout when they have certain items in their basket, and/or have met certain minimum purchase requirements. Without this patch a shopper can modify the url to manually add an upsale item to their basket. When doing so they can even get an item that was discounted to $0.00 which should have only been available with the purchase of specific expensive other items. If the free upsale item is the only thing they add to their basket they can even bypass the shipping, tax, and payment options and jump straight to the invoice.
• Patch 4 - Shipping Module Installed Check
  This patch does a check to make sure the shipping method submitted is for a valid module installed in the store. Without this patch it is possible for shoppers to bypass the shipping calculations and not pay any shipping charges on the order. Without the patch you must therefore be very careful to manually cross reference all your orders to make sure you don't ship something that didn't have the shipping charges paid for. This patch is not required if you are using Miva Merchant 4.16 or higher.
• Patch 5 - Shipping Charge Check
  This patch makes sure a shipping charge was actually added to the basket charges table. It is okay if the charge was set at a zero price because you offer free shipping under certain circumstances, but this patch makes sure a shipping module actually made that decision and added a zero charge, rather than there being no charge in the table. Without the patch you must therefore be very careful to manually cross reference all your orders to make sure you don't ship something that didn't have the shipping charges paid for. This patch is not required if you are using Miva Merchant 4.16 or higher.
• Patch 6 - Tax Charge Check
  This patch makes sure a tax charge was actually added to the basket charges table. It is okay if the charge was set at a zero price because no tax was required based on your tax module configurations, but his patch makes sure your tax module actually made that decision and added a zero charge, rather than there being no charge in the table. Without the patch you must therefore be very careful to manually cross reference all your orders to make sure you don't ship something which you didn't collect the proper taxes on. This patch is not required if you are using Miva Merchant 4.16 or higher.
• Patch 7 - Affiliate Status Check
  This patch stops affiliates from changing their status, or new affiliates from creating their account with a status of their choice. Without this patch it is posisble for affiliates that have not been approved yet, to change their status so that they are approved, or for new affiliates to set their initial status as approved. This patch is meaningless if you are using a version of Miva Merchant lower than 4.x.
  
  
• Patch 8 - Duplicate Order ID Check
  This patch helps prevent duplicate order numbers from being added to the orders database. Without this patch there are various circumstances that can cause duplicate order numbers to get entered into the orders database. To be clear, this patch doesn't stop duplicate order ids from being issued, nor does it prevent the automatic recovery of order numbers to the orphans database, what it does is generates a new order id for the about to be created order if the order id exists in the orders database.

Price: $39.97 Upgrade Cost: $0 Upgrade Terms (If Any): N/A
Compatibility: OpenUI Versions: 2.x, 3.x, 4.x
Other Module Compatibility: N/A

From: Store Features Modules
Relevance: 53.79%%

Rating: (0.00) Votes: (0) Hits: (1007) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark QwkPatch <-- Just click this link and then add to your favorites!

10 Mail Manager Weiland / Miva Central

The ultimate Miva Merchant autoresponder module - send specialized emails at the completion of the order. These emails are in addition to or in place of the standard emails which are sent at order completion, e.g. merchant notification, customer confirmation and even vendor specific notification.

Features: (some features are only in the compiled version)
- Autoresponder - specialized emails at the completion of the order
- Merchant notification and customer confirmation
- Vendor and product specific templates
- Include coupons or promo codes when specific products ordered
- Easy to use checkbox configuration of vertical or horizontal layout emails
- Highly configurable free form template layout emails with embedded tokens
- HTML or text email formatting
- Archive flat file is created for each template, easily track sales activity
- Mail Manager Report module can display the flat file contents by time period or product
- Ship to, bill to and other email addresses for each template
- Send emails to your company's internal departments, e.g. shipping
- Emails to web enabled cell phones
- Open architecture so that other events can also trigger an automated response
- Send a welcome email before the order completes and include a promo code
- Include 3rd party data with tokens, e.g. Addendum responses
- Display shipping and payment invoice messages
- Create packing slip and label emails
- Ship to country address formatted according to the applicable country's postal recommendations
- Restrict email to a specified order dollar value range, reward big spending customers with a coupon
- Restrict email to a specified list of countries, thus allowing for language specific emails
- MMUI and OpenUI compatible. No editing of the mmui.mv is needed and no OpenUI hook points are used

In admin, you create one or more template emails. Each template can be different, i.e. what it displays, how the data is oriented on the screen/paper, and what product(s) triggers the autoresponder. Most responses are triggered by the product codes purchased. Some example uses:

• Email to any of your drop-ship manufacturers listing the Ship To address and the products to be shipped if using real time credit card authorization. The module will sort out which drop shipper gets which emails, including listing the products to be shipped. You can still