Found 150 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, as the name implies, is an affiliate manager. It tracks referrals to your store from your affiliates. You give an Affiliate code to them which they in turn can use in a link to your site or provide to others who can enter it on your site to give credit to the affiliate for their visit. You can set the amount to be paid out separately for each individual affiliate and the module tracks the accumulation and alerts you when payout is due. Payouts can be scheduled for any time period from daily to annually or set to occur when a particular payout amount has been accumulated.
A sampling of the module's features:
Store display settings can be configured separately for each affiliate so each can have their own "unique" look and feel
Payouts can be accumulated and for both hits and orders (as both a per order payout and as a percentage of the order total)
Payouts can be accumulated up to 5 levels deep (i.e. you can give payouts to those who refer other affiliates to your store)
Emails can be sent to the affiliates when orders result from their referral. The email can be in either text or html formatting.
The referral is gathered by the module itself w/ a link such as: http://yourstore.com/Merchant2/merchant.mv?AFFIL=affilcode No need for extra scripts to collect the referral.
The referral link can point to almost any page in your store. For example, you can point them directly to specific products or categories. Just add the AFFIL=affilcode to the URL that points to that page.
Customers can be redirected to a static web page after the referral is collected so the module can be used by those merchants who display their products on static pages.
Referrals can be held without crediting it to the affiliate if the customers pay with particular payment modules to avoid payouts for orders for which payment was not actually received.
The contents of the emails sent by the module and the invoices generated are fully configurable by the use of templates.
The referral code can be passed to your store either through the link from the affiliate's web site or it can be collected in a form on your site which can be positioned in up to 14 different positions. The content of that form is configurable with a template
The module can provide for a new page in your store at which customers can apply to be affiliates. That page can be linked to w/ links in up to 13 different positions on your store pages and the content of the new affiliates page is entirely configurable by the use of templates. Approval can be either automatic or pending your approval.
More information about the available features can be gleaned from the main Options page which you can see here.
This module provides your Affiliate Manager affiliates with an interface in your store where they can view and modify their personal data (permitting them to modify their settings is optional), view the orders and hits which have been credited to them, view the payouts which are pending and the payouts which have already been made.
The module uses the "templates and tokens" approach to displaying the information familiar to users of my other template modules. This approach provides for full control over the display of the various pages by simply modifying the HTML used to display that page; placing tokens to represent the data wherever you see fit. Two templates can be separately configured and you can select which of the two to use for your display. By default, one of these templates displays almost all of the affiliate's personal data and permits them to edit and update the information. The other template displays the same data but does NOT permit the affiliate to modify the data.
The display consists of a main page to which the affiliate first arrives with links on this page to pop-up windows for each of the other data pages. Images can of course be configured for each of the links and buttons on the various pages.
Note: This module requires that the Affiliate Manager be installed (and isn't of any use without it).
Note: This module requires ver. 3.9x or higher of the Miva Engine.
Take a look over the shoulder of a Miva Merchant professional as he takes you through every step, every module (almost), every function. Complete with "live" comments unedited, you'll learn while feeling like you're sitting next to a Miva Guru.
This tutorial subscription is different than all other Miva Merchant training methods because it is constantly updated, there are OpenUI and MMUI tutorials, as well as extensive tutorials on most popular third party modules, including offline products like Storeman. With the cooperation of third party developers, when a module is updated, or a new module is released, Merchant How To will create a new tutorial.
And more as it is released. Click the link to see examples of tutorials.
NOTES: Please allow up to 24 hours for activation. Tutorial Flash files can be large, so it is recommended that you have a broadband Internet connection to enjoy the tutorials. This tutorial subscription is new, so not all tutorials listed at MerchantHowTo.com are immediately available. Also, since this subscription is essentially electronic distribution of knowledge, and since there are several examples and a list of tutorials available prior to purchase, no refunds can be granted on these tutorials.
Get dedicated-server performance and better search engine optimization from a module.
If your site is bogging down from too many "just looking" visitors, or if your finding your Merchant Store pages not getting into search engines, then Merchant Optimizer is the perfect tool for you. Merchant Optimizer works by creating exact copies of your store's screens, saving them as standard HTML pages in an alternate directory. These static pages are much easier for your server to serve to your customers and for search engines to scan and index. With a few additional tricks, you direct all browsing to be done in the static pages, or just use the static pages as entry points for your Merchant store's dynamically generated screens. You can create separate static pages for different affiliates, or even for different domains, using your store for example, to create a mirror site that can be used under a different domain. For example, you can have a copy of your store's screens, on www.mysite.com, then create another site called www.myothersite.com....and have both sites point shoppers into your Merchant store. (This second store could be configured with an affiliate link, and those hits tracked by any compatible affiliate module such as Merchant's built in affiliate module or VikingCoders.com Affiliate Manager.)
As you can see, this module is both absurdly simple to operate, yet limitless in its applications. A little imagination will go a long way.
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.
Coupon Manager allows you to offer customers various types of coupons which can be redeemed by entering a coupon code during checkout. It features full display options and extensive coupon options which can handle most any type of coupons you wish to offer, such as $20 off any order $100 or over, 15% of any order, buy 4 widgets get $2 off each widget, 20% off your entire order if you order 2 or more of widgets x, y, or z, 10% off orders for the next 10 shoppers that use this coupon - offer not valid with other coupons, spend $20 or more on widgets x, y, and z, and receive free standard shipping plus 10% off your order, limit one/customer, and more!
Coupons may be configured to only be redeemed when used by themselves or redeemable in conjunction with other coupons with an optional maximum total coupons that may be used. Coupons may optionally reduce sales tax depending on your state laws and the type of coupon being used. Coupon Manager's searchable console lets you view the number of times coupons have been redeemed at any time, as well as edit/remove coupons, and can also keep a log of all coupons used which can be imported into database/spreadsheet software.
Features include:
configurable image/button text for redeem coupon button
configurable header and footer for coupon prompt
optional coupon log
coupon expiration date
fixed or percentage discount amounts
extensive coupon options such as taxable, redeemable in conjunction with other coupons (with an optional max coupon cap), one per customer, maximum uses, and a minimum required subtotal
free shipping coupons, with or without an additional discount
configurable qualifying products, including wild card support for product codes beginning with specific characters
qualifying products lists may be set as included or excluded (excluded lists are useful for quickly marking all products except one, or a few, as qualifying)
advanced additional product specific options including minimum quantity, minimum subtotal, whether to calculate the discount based on the quantity ordered (only for fixed amounts), including an optional max quantity cap, and whether to base the discount on the entire subtotal (only for percentage amounts)
option to limit coupons to qualifying zip codes
notes field
searchable console for easy viewing, editing, and deleting of coupons
delete all expired coupons option
Note: This module requires ver. 3.9x or higher of the Miva engine.
The Page Title Manager module allows you to specify titles to be placed on each screen of Miva Merchant. The titles replace the default text between the opening and closing title tags on each page. Tokens are available so that you can include store name, category name, product name, selected customer information, and selected affiliate information. (Some tokens are not available on all screens.
This module provides your store with a more configurable and robust search page. It permits you to offer your customer the option to search categories and attributes and to limit their search to particular fields in the Products database. Searches can be made case sensitive, restricted to searching only the entire phrase, and made to use either AND or OR. In addition, the module provides for the separate configuration of keywords for your products and those keywords can be included in the search. The module supports the Viking Coder's Additional Product Fields Manager module and you can provide your customers with the ability to search the fields that you have configured for your products. All of the configurable options, including the particular fields to search on, can selectively be made default options and hidden from your customers. In this way you can restrict the search to only those fields you want your customers to search in.
The module comes with two distinct admin interfaces. One provides for the simple configuration of a default layout for the search page and display of results. For those familiar with HTML and looking for a specific layout, there is a template based configuration option which provides for complete token and template based control over the layout of the search page and results listing. Support is also provided for Third Party modules in the same manner as my Category Page Templates and Product Page Templates modules.
A sampling of the module's features:
Can be configured to replace the standard Merchant Search link and will use the same search button. So you can have the standard search link instead point to the Search Manager search page
The search page can be linked to from a static link with a link of the form: áááhttp://yoursite.com/Merchant2/merchant.mv?Screen=SRCHM&Store_Code=storecode
Customers can search the categories for their search terms and the results are displayed above the product results (in the standard display format; they can go anywhere you want with the template formatting).
Customers can restrict the search to find only the entire phrase they entered by surrounding the search terms in double quotes. Eg. "Clown nose" will find only those products which contain the exact phrase "Clown nose"
Keywords can be saved for each product and category and those can be used to search in. To search the keywords for the products is an option for the products. The keywords are searched automatically for the categories. In both cases a tab is added to the individual category and product screens so that the keywords can be added.
You can redirect customers who add products from the results listing either back to the search page or to the basket.
All of the buttons (eg. "search", "add to basket", "previous", etc.) are configurable w/ images and alternate text.
When using the Template formatting option, you can use tokens to add drop down select lists with terms your customers might want to search for. They can then search for those with a simple selection from the list.
When using the Template formatting option, you can provide the customer with the option to sort the displayed results ascending or descending by product name, product code, or product id.
When using the Template formatting option, you can use multiple search fields to prompt your customer to search for multiple terms. For example, you could provide a field for "title" and a field for "author" to prompt our customer to narrow their search
Additional Product Fields Manager is an easy to use package for creating an unlimited number of new product fields. It requires no core database modifications or code changes, all additional fields are defined through an admin console. Simply define a code and prompt for each new field, and choose which screens to display it on (product, category, product list, and/or search). These options may be edited later while preserving any new field data you have added. Additionally, you can arbitrarily sort new fields at any time.
Once one or more new fields have been defined, you can start adding product data for the new fields. Product data may be added/updated in the Edit Products Screen, or in bulk using the included Import Module. Field data may contain up to 254 characters and may also include HTML/JavaScript/etc. If you haven't added any data for a new field for a product, that field simply isn't displayed for the product. In this way, different products may contain different new fields. An export module is also included.
Features Include:
Unlimited new fields
No database or code changes required
Configurable display of new fields for all standard screens (you can choose to display a new field on category and product pages, but not on search results, for example)
On-the-fly sorting of new fields
Import module for bulk import of new field data
Export module to export the new field data
Optional bold display of new field data on product and expanded displays
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.
This module extends the capabilities of the Order Status Manager to provide your customers with a way to check on the status of their order with only the order id and/or email address. This is especially useful for those merchants which do not require their customers to create an account with their store when placing an order.
Links to the login page can be placed in up to 13 different positions on the page. The login page itself is entirely configurable using an html template and tokens. Other configurable options include whether or not an email address is required when logging in and which, or either, of the order's email addresses (shipping or billing) can be used. The login page can also include the standard Merchant login fields so it can serve as the login screen for the Order Status Manager for both customers who did purchase with an account and those that didn't.
Additional Screens is a simple to use utility module that allows an unlimited number of new "screens" to be created, such as new pages for contact info, policies, frequently asked questions, etc. You define a screen code, title, and the html you want to be included for each new screen. The category tree may also optionally be displayed for each screen.
Tokens are also available for creating dynamic pages including support for URL Includes (for embedding external html pages, cgi scripts, etc.), secure links including the Session_ID, and any variable available in Merchant.
Note: This module requires version 3.9 or higher of the Miva Engine.
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.
This module gives a store the ability to sell and accept electronic gift certificates. Gift certicates templates are created and can be associated with products for sale in the store (or their attributes). When the associated product is purchased, the module will automatically generate a key for that certificate and send an email (optional) to the purchaser containing the key and an explanation of how to use it. At checkout, on the payment and shipping selection page, the module prompts the customer to enter a gift certificate key and, when a certificate is used, applies the appropriate credit. The remaining balance, if any, is recorded and available on subsequent visits.
Of course there is a little more to it than that and this module provides for a great deal of flexibility:
Certificate types can be associated with individual products or their attributes. In addition, attributes can be added to the product to collect address information, the name of the person the certificate is for, the date to deliver the certificate, and any notes the purchaser wants to include for the recipient. This data is collected and stored in association with the key that is generated for that certificate.
A template can be configured and used to view the certificate in a browser window. This template uses tokens to represent the various information about the certificate such as the key, the store name, expiration date, balance, etc. The data collected when the certificate was purchased (ie. address information, notes, etc.) can also be inserted into the certificate. This certificate can then be printed and mailed or manually distributed.
Keys can be manually generated from within admin. Immediately after the key is generated, a link is availalble to view the certificate so that it can be printed.
There is an administrative interface showing all of the keys that have been generated for each certificate type. The data shown includes the issue date, expiration date (editable), balance (editable), date last used, and the order id in which the certificate was purchased (unless it was manually generated of course). This list can be sorted ascending or descending by the certificate keys and the issue date.
* The orders in which a gift certificate is redeemed are tracked for each key and can be viewed from within admin. The amount for which the certificate was redeemed and the resulting balance is shown.
This module provides your customers with the opportunity to add products to a Wish List. This permits them to later return to your store to view, add, and edit the list. They can send email to their friends prompting them to visit your store and view their wish list. Other customers can search the wish lists for the lists of their friends, hopefully with the intent of buying something for them, and send email to others to recommend that they visit your store and start a list.
The admin interface provides the merchant with the ability to view the current customers with wish lists (searchable by wish list contents and customer data) and to view the contents of each list. The entire wish list can be deleted from within admin as can individual products in the list.
If a product being added to a wish list has attributes, the customer will be prompted to select the attributes (but not required to) before the product is added to the list. If the customer is not logged in when they attempt to add the product to their list, they will first be prompted to log in and will have the opportunity to create a new account.
The module adds new Merchant pages on which the customer can view their your own wish list and search for the wish lists of others. Links to both of these pages can be provided in up to 13 different positions in the navbar and in the category tree. The link by which the customer adds the product to their wish list can appear on up to 11 different positions on the product display page. The link text and/or image used for each of these links is separately configurable.
When a customer searches for wish lists, the wish list "owner's" first name, last name, email address, login, city, state, and zip code are all searched.
The merchant has the option of making the wish list "opt-in only" by providing the customer with a checkbox on the customer account page to enable a wish list (the text of the prompt is configurable). If a customer chooses not to opt-in to the wish list, they will be able to add/edit/view their own list but it will not appear in searches by other customers. They can still email their friends and provide them with a link to their wish list.
An expiration period can be set for the wish lists. If no activity takes place in a configurable time period (ie. no products are added) the lists can be purged from within admin.
The format of all of the pages is completely configurable with tokens. The customer can be permitted to edit the quantity of the items in their wish list, add a note, and delete individual items. The format of the page on which the customer views their own wish list and on which they view the wish list of others are separately configured to provide the customer with the additional ability to edit their list.
From the page on which the customer view their own wish list, they can send an email to their friends to let them know about their list. From the page on which the customer searches for the wish list of others, they can send an email to invite their friends to start a list. The content of both of these emails is completely configurable from within admin and use tokens to represent store and customer data.
The header, footer, background image, title, and background color of each new page added by the module are separately configurable from the module's administration interface.
This module provides an "out of Merchant" interface for creating baskets and entering orders. The interface is completely configurable using "tokens and templates" and combines the product selection, customer information, shipping selection, and payment selection screens of the normal Merchant checkout into a single screen. Products can be added to the basket by selection from a list or from search results. Customer information can be manually added or the customer's account can be searched for and selected to "pre fill" the address information. Customer accounts can be created from the interface with the login and password being manually entered or automatically generated.
The module is intended as an interface to be used by individuals taking phone orders or otherwise needing a more compact check out process than that which is offered by Merchant. As such, it uses Merchant's "basket" and checkout pages and the procedure for it's use is a streamlined version of Merchant's typical procedure. The user will add products to their basket and enter the customer's information (either manually or by selecting the customer's account from search results). The shipping and payment methods are selected. When the order is ready to be completed, the "process" button is clicked and the user is taken into Merchant's checkout pages (which particular page the user is taken to is a configurable option) and the order is completed in the same manner that a normal customer would. This order will then appear in Merchant's order processing exactly like any other order.
This module provides you with the tools you need to let your customers check the status of their past orders. It adds a link (or links, in up to 13 different positions), to the Merchant pages which customers can use to access their order history. The customer is given a display of all of their past orders. They can view the details of any of the orders, and even search them for details. The tracking numbers themselves can be direct links to the shipper's website tracking page, so the customer can check the status of their order with simple click on a link. The merchant, can access a listing of all orders, searchable by customer, date, orderid, shiping status, tracking number, etc., change their status, enter tracking numbers (for orders and even individual products), and have an email sent to the customer notifying them of the change. Shipping labels can be displayed and printed for each order. The format of the shipping label/packing slip is completely configurable using tokens.
The merchant can individually configure many of the features of the module. For example, the status themselves are NOT predefined. The Merchant can configure these to be whatever he wants. Similarly, the "tracking types" can be configured, complete with a URL to use for that type of tracking number. When the tracking number is displayed to the customer, that URL is used to take the customer to the shipper's tracking page. The module comes preconfigured with the URLs for UPS, USPS, and FedEx but adding additional tracking types is simple. The merchant can select to send an email when the status of an order changes. Email can be sent to the customer's billing, shipping, or both, email addresses. Separate text for each type of email can be configured (ie. separate email text can be configured for when the status changes to "shipping", or "back-ordered", or whatever). The email text can include dozens of possible tokens that can be used to represent the customer's details (first name, last name, login, password etc.), tracking status, link to the customer's orders status page (it automatically logs them in), link to the storefront, and many more. The module does not require that the customer be logged in for their order data to be saved. Of course if the customer was not logged in when they placed their order, they won't be able to view the order later.
The module maintains a separate database of the orders which is a duplicate of Merchant's order databases, including the payment and shipping details. So you can delete orders from within Merchant admin, but the customers will still be able to view their past orders. The Order Status orders can be deleted from within the modules admin interface. That interface also provides the ability to search the orders by date, customer, tracking number, tracking type, and status. The order details can be viewed, and tracking status, number, and type, can be set for individual products within the order.
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.
This import/export combo speeds up the process of updating orders maintained by our Order Status Manager. The exported file can be opened in any text editor, spreadsheet or database program for simpler updating of orders. The module will NOT send email updates when an order's status changes. The import will, for example, allow you to change 'Pending' to 'Back Ordered' for any or all orders. It also supports the line item feature of Order Status Manager so you can change the status for individual items within an order, separately from the order itself.
Minimum/Maximum Quantity Manager allows you to set minimum and/or maximum quantities products must be ordered in. Quantity restrictions may be set individually for each product, and/or globally. Global restrictions may be applied to all products, a specific list of products, or products matching a price criteria. For example, you can configure a 2 piece minimum for all products $5 or less. If using a list of products support for * wild cards is included (to include all products starting with specific characters). If both global and product specific restrictions apply to a product, the product restrictions will have priority. For example, you could set a global 2 piece minimum on all products, but have a specific product flagged as 3 piece minimum. Minimum/maximum restrictions apply to all customer by default, but can also be limited to customers assigned to a particular price group.
The basket contents can either be automatically checked and auto-adjusted every time the basket changes, or only checked when the customer attempts to checkout. If auto-adjusting is enabled and a minimum/maximum restriction is not met, a configurable, tokenized message is displayed and the quantity is automatically changed. A message might say, for example, "Quantity for widget adjusted to 4 to meet maximum requirement of 10" (if, say, a customer already had 6 widgets in her basket and tried to add another 5). If auto-adjusting is not enabled, the basket is only checked during checkout. If any restrictions aren't met the customer is redirected to the basket contents page, and a configurable error displays prompting the customer to adjust the basket. The location of the error message is configurable, and can be set to Above Global Header, Below Global Header, Page Top (top of main right cell), or JavaScript Alert.
If products flagged with minimum/maximum quantity restrictions contain attributes, the module also provides a choice between counting each attribute combination as a separate product, or counting them cumulatively. Say a t-shirt is sold in 3 colors, has a minimum quantity of 10, and the customer adds 3 red, 3 blue, and 4 green shirts. If counting attribute combinations cumulatively, the minimum is considered met. If counting individually, the customer must order 10 for each color ordered.
To help the store owner identify needs quickly, an
optional CC email can be sent when an item is wait listed.
