Found 212 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.
Display all open baskets in a table format. This report includes active and expired baskets. As a store owner you are able to see how many people come to your store and abandon baskets, even after placing items in the basket. In some cases, customers get to checkout and then abandon baskets and you can determine that too. You can use it to check basket activity before closing the store for maintenance or deleting baskets in admin. As baskets are converted to orders, they disappear from this listing. Likewise, when expired baskets are deleted in Admin, they also disappear from this listing.
Basket ID - Number assigned when a customer visits your store
Order No. - Incremented number (or retrieved from unused numbers) each time a customer enters their customer information at checkout
Customer - Account info (if available) - Login, Ship To Name, Bill To Name (if different), Ship To Email, Bill To Email (if different)
Product - Product codes in the basket at this time (may be empty or contain one or more)
Expired - "Yes" indicates the basket was last refreshed more than the number of minutes for your basket timeout setting. A number indicates the number of minutes since last activity and the basket is not timed out.
Unattended scheduled tasks , including backups and batch exports . Important up-to-date data, number of visitors shopping, order notifications in real-time . Alerts for oversized files, broken databases , corrupted data, lost orders and emails. Automated cleaning up oversized data and removing temporary files . Statistics . Order history . Bestsellers . Instant shutting down the store, deleting baskets, packing. Instant access to MM Admin.
Displays the number of currently shopping visitors (opened baskets)
Automatically backs up and resets databases and deletes data files that grow over assigned file size quota - significant performance boost!
Automatically deletes temporary files from interrupted packing (i.e. products.dbt00000001)
Automatically deletes temporary upload files
Scheduled ábackups, Batch Exports, etc. (see below in SCHEDULED TASKS)
CHARTS Hourly, daily, weekly, monthly and yearly charts including historical data (unlimited) in following modes. The length of the displayed period is configurable, browsing in the history is of course possible.
Abandoned baskets
Failed payments
Total revenue (sold value)
Total number of orders
Total number of sold products
Total collected tax value
Total collected shipment charges
Number of failed e-mail notifications
STATISTICS Beside the data displayed in the charts and in the mouse-over popup windows over the charts, there are the following data available. The displayed values depend on the selected time mode - it shows either totals over the last hour, day, week, month, or year.
Number of new orders (unbatched orders)
Total number of orders in the given period
Total revenue in the given period
Total number of sold products in the given period
Total value of collected tax in the given period
Total value of collected shipping charges in the given period
Number of abandoned baskets in the given period
Number of failed payments in the given period
Number of failed e-mail notifications in the given period (with MmHTML, MmHTMLc or MmVENDOR)
Number of hits since the last reset (in MM Admin)
Number of visits since the last reset
Total revenue since the last reset
Total number of sold products since the last reset
List of bestsellers. It can contain limited number of bestesellers or list of all products sorted by number of sales. Values since the last reset in MM Admin.
INSTANT ACCESS To MM ADMIN Functions From the MmTICKER window you can access the following often used MM Admin functions with a single click on a button:
Instant access to the standard MM Admin without the necessity to log in
Shutting down the store to the maintenance mode and re-opening it again
Deleting baskets (all or expired only)
Packing store and domain data
Instant access to the batch report of new arrived orders (click on the new order announcement). Works with both Ultra Batch and the built-in MM batch report.
ALERTS AND EMAIL ALERTS MmTICKER watches your store and associated files and in addition to displaying an alert message on the screen it also sends e-mail alert to the store owner. Email alerts work even without the MmTICKER window opened!
File Quotas: MmTICKER warns if pre-defined files grow over the limit assigned to them. Works also with files 3rd party modules!
Database Consistency: MmTICKER verifies all pre-defined databases if they are not corrupted and do not contain duplicate records. Works also with databases 3rd party modules!
Alerts on failed schedule tasks or optionally email reporting of successfully finished scheduled tasks, too.
MmTICKER alerts when the number of failed payments in a day is bigger the given limit (possibly signilizes problems with the payment gateway or fraud attempts)
SCHEDULED TASKS You can set up inlimited number of scheduled taks to be performed daily, monthly or yearly. The defult pre-defined task schedules at 4:00AM the store for at the maintenance mode 15 minutes later, waits till the store is closed, deletes expired baskets, packs store data, packs domain data and re-opens the store. Scheduler may be configured so that it executes the tasks only if nobody is in the store. Currently, the following commands may be used:
Close - scheduling the store for the maintenance mode after a pre-define time (15 minutes by default)
WaitClose - waits till the store shuts down
DelExpBask - deletes expired baskets to increase the performance and reduce the file sizes
DelAllBask - deletes ALL baskets (even those not yet expired)
PackStore - packing store data to reduce store specific files and to rebuild store database indexes.
PackDomain - packing domain data to reduce common Merchant files and to rebuild mall database indexes.
ExportNew - exports new order to a file and sends the new batch by e-mail to the store owner (with Ultra Batch)
DelCC - for security reasons, deletes payment data (incl. CC numbers) of all processed orders (with Ultra Batch).
backup - creating full backup copy of Miva Merchant Data (Unix full shell servers only. Limited support).
mmubat - calls Ultra Batch module and performs tasks defined in passed arguments (with Ultra Batch, for advanced users only).
admin - calls MM Admin and performs tasks defined in passed arguments (for advanced users only).
shell - calls system commands (Unix full shell servers only. For advanced users only).
other commands for the scheduler may be added on request
MmTicker logs unauthorized access attempts with detailed information about the user - logfile is browsable through the MmTICKER admin screen.
Scheduled tasks are also logged and the records may be viewed in the Admin screen.
Time zone setting and user-defined date and time format
Animated "marquee" alerts, messages and statistics with configurable speed and possibilty to change the speed or stop the scrolling with a single mouseclick.
Parts of the MmTICKER window may be hidden to reduce the size
Flashing taskbar button and window popping up on alerts (optional)
Configurable window size - the size of the window may be set to show charts over longer time period.
Zoom - for those with bright eyes or oppositely with sight problems, the winod may be zoomed from 50% to 200%
Mouse-over help and detailed info on items work overall on the MmTICKER window.
MmTICKER window refresh frequency configurable
Frequency for file size and database consistency check configurable
Automated installation, no manual intervention needed
Scheduled tasks may be triggered from the opened MmTICKER window, from a Unix cron table, from a remote server (i.e. truXoft) or directly from Miva Merchant.
Does not require OpenUI. Works with both OUI and MMUI.
No OUI hook conflicts - truXoft modules are 100% conform to the Miva Merchant API, they do not use OUI extensions and therefore never cause hook conflicts with other modules, otherwise common at OUI modules.
Display all open baskets in a table format. This report includes active and expired baskets. As a MIVA Merchant store owner you are able to see how many people come to your store and abandon baskets, even after placing items in thebasket. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
In some cases, customers get to checkout and then abandon baskets and you can determine that too. You can use the module to check basket activity before closing the store for maintenance or deleting baskets in admin. As basketsare converted to orders, they disappear from this listing. Likewise, when expired baskets are deleted in Admin, they also disappear from this listing.
Basket ID - Number assigned when a customer visits your store
Order No. - Incremented number (or retrieved from unused numbers) each time a customer enters their customer information at checkout
Customer - Account info (if available) - Login, Ship To Name, Bill To Name (if different), Ship To Email, Bill To Email (if different)
Product - Product codes in the basket at this time (may be empty or contain one or more)
Expired - "Yes" indicates the basket was last refreshed more than the number of minutes for your basket timeout setting. A number indicates the number of minutes since last activity and the basket is not timed out.
You can delete specific baskets. This feature was requested by a store owner who found his competition was purposely putting large quantities of items in the basket so they would be out of stock. By using this feature he was able to delete the basket and the items were immediately put back in inventory.
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.
As a Miva Merchant storefront licensee, you have discovered that you have a powerful shopping cart system. One of the strengths of Miva Merchant is its ability to plugin 3rd party modules to provide off-the-shelf, additional features at reasonable cost. You may have found that the cost can quickly add up and you are not exactly sure which additional features would be of benefit. We have assembled a bundle of a dozen of our most popular plugin modules. Literally hundreds of stores have found these to be the "must have" modules. As this is a bundle, it's cumulative price is 30% less than the sum of the individual module prices.
The modules in this bundle can be classified as storefront enhancement, discount, checkout, search engine optimization, and administrative back-end modules. The detailed module features and capabilities can be reviewed by clicking on the module names in the components list below. Please review each of the individual product descriptions so you fully understand what is included before selecting this bundle deal.
Non-refundable: Due to the number of popular modules included in this bundle, this
bundle deal is not refundable.
Compiled Merchant only: This bundle is only available for Miva Merchant 4.14 and newer. As it is a starter kit, nobody should be creating new stores with old versions of Miva Merchant anyway.
Baker's Dozen: For a limited time, if you order this bundle, you can get one more Emporium Plus individual module (bundles are not eligible) at no extra charge in a separate order. Email Emporium Plus after paying for the starter kit and tell us which module you would like as a bonus and we will send you a coupon code for a second order to get that module free. A popular free module could be our Customer and Product Administration module which lets customers view their order history among other things (value $40.00).
OpenUI Required: About half of these modules require installation of the OpenUI before they can be installed.
As a Miva Merchant storefront licensee, you have discovered that you have a powerful shopping cartsystem. One of the strengths of Miva Merchant is its ability to plugin 3rd party modules to provideoff-the-shelf, additional features at reasonable cost. You may have found that the cost can quicklyadd up and you are not exactly sure which additional features would be of benefit. We haveassembled a bundle of eleven of our most popular plugin modules. Literally hundreds of storeshave found these to be the "must have" modules. As this is a bundle, it's cumulative price is about 33% less than the sum of the individual module prices.
The modules in this bundle can be classified as storefront enhancement, discount, checkout,search engine optimization, and administrative back-end modules. The detailed modulefeatures and capabilities can be reviewed by clicking on the module names in the componentslist below. Please review each of the individual product descriptions so you fully understandwhat is included before selecting this bundle deal.
Non-refundable: Due to the number of popular modules included in this bundle, thisbundle deal is not refundable.
Compiled MIVA Merchant 5 only: This specific bundle is only available for MIVA Merchant 5 andnewer. As it is a starter kit, nobody should be creating new stores with older versions of MivaMerchant anyway. However, if you are looking for a starter kit for compiled Merchant 4.x, take a look at our other starter kit bundle.
The modules currently fully support the mivasql configuration of MIVA Merchant 5. They also support 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.
Make it easy for your customers to come back again! Does your store sell consumable products that customers are likely to purchase more than once? Or perhaps your customers would like to save their basket and come back to finish their order later? Use our Save Baskets module to implement this feature! Your customers will be able to save one or more baskets with a nickname for future use.
You can configure this module to allow any number of saved baskets--even unlimited--for each customer in your store. Baskets can last forever or they can expire after a given number of days. Your customers can log in, view their saved baskets, check a basket's contents, prices, and subtotal, and then restore the contents of the saved basket to their "live" Miva Merchant basket.
This feature is especially useful for customers who tend to place the same (or similar) orders on a repeated basis.
The module allows extensive customization to the new screens, including headers/footers, custom messages, custom buttons and forms, and many choices of locations for links to the Save Baskets screens. See the slideshow for more details!
The NetPush Advanced Inventory Module allows Miva Merchant store owners to track inventory within Miva Merchant all the way down to the attribute/option level. The module has numerous configuration settings that should allow the admin to display and track any simple or complex inventory configuration. Inventory levels are only adjusted at checkout time so there is no need to worry about old baskets causing inventory problems. The module comes with an import and export module that allows administrators to easily update inventory levels by using csv files.
We suggest using template modules like Viking Coder's Product Templates and
Category Templates if you want better control of the look and feel of your pages with regards to inventory. This will allow you to use tokens for display. Otherwise, you will have to settle for built in hook point displays that are built into the module and are configurable through the administration area.
The Advanced Inventory Module will send email when stock goes below certain configurable low stock level and can disable products when stock goes below the out of stock level. Administrators can also customize every message shown to the user. Fine grain customizations are made easy because the module allows product level configuration settings the ability to override global inventory configuration settings. This allows Miva Merchant Administrators the ability to customize inventory configurations for every product, if he or she wishes.
Notes:
OpenUI Tokens This module can be used with OUI OpenTokens. To use the module with Viking Coders template modules, see the OpenToken instructions and examples in the documentation on the NetPush.com site.
Product Upsell This module does not show stock information on the product upsell screens at this time. Stock is still tracked in the basket and checkout, but no current stock level is shown on the upsell screens during checkout unless you are using alternatives like tokens in templates.
Basket Redirect and Error Message The user is automatically redirected to the basket screen if he or she adds items to the basket that makes the product go out of stock or if the product is already out of stock. The error message is shown above the basket screen using a hook point in the Open UI. The message is configurable in the admin area.
Checkout Screen Error If configuration is setup to do so, the module will block a user from checking out if their basket has an item that is out of stock. This message is shown automatically at the top of the screen. The message is configurable in the admin area.
Pipes ( | ) Product codes, attribute codes, and option codes must not contain the pipe character. NetPush Advanced Inventory uses the pipe to delimit for lookups. Pipes in your codes will cause the module not to work correctly.
Requirements:
Open UI 4.723+ This module requires that you have OpenUI installed in your store. The module uses hook points in the OpenUI. You must have OpenUI version 4.723 or higher if you plan to use the OpenToken functionality available in this module. Please see the OpenUIsite for information about latest versions and bug fixes.
Miva Empressa 3.96+ This module requires that you have Miva Empressa 3.96 or higher. The module uses functionality that is only available in newer versions of the Empressa Engine. Miva regularly releases new versions of Miva Empressa and the Virtual Machine to add new functionality and fix bugs. If you are on an older version, consider contacting your hosting company. You can find the Miva Empressa version at the top left hand of your Store Administrator when you first login. It should show your Miva Merchant version and your Miva Empressa version.
Miva Merchant 2.x, 3.x, and 4.x This module should work with most versions of Miva Merchant. In order to use the deactivate product option, you must be on version 3.0+. All testing and development was done on versions 4.13+.
Global Configuration Screen
All inventory settings will use the global configuration settings found in the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. One may override these settings for products (see product level settings below). Each product must also be manually turned on before tracking starts. See product settings below.
Configuration Settings
Use NetPush Inventory You must set this to "Yes" if you want the module to be turned on. If this is set to "No", the module will not do anything.
Amount considered out of stock Usually this would be 0, but it can be set to any number, including negative numbers. Once the stock level reaches this number, it will be considered out of stock.
Deactivate when product level is out of stock In Miva Merchant versions that support it, the module will turn the Active flag for a product to off, if the product reaches the out of stock level. This only works on the product level, not for the attribute/option level.
Allow purchase even after out of stock Turning this on will allow customers to purchase products even after they go below the out of stock level. This could be a backorder situation.
Automatically remove from basket When a user adds products to the basket, the products will be removed if it makes the inventory go below the out of stock level and the admin is not allowing purchases when products are out of stock. Please take note that this option could cause problems if other modules are installed that also act on the basket.
Send Low Inventory Notices Turn this on to receive email warnings when inventory goes below the low inventory level.
Amount considered low The level that is considered low. Use this setting to trigger emails that will warn you when inventory is hitting a low level.
Low Email To Address Set this to the email address of the person who should be receiving emails when stock is at a low level.
Low Email From Address Set this to the email address that should be set as the from address in low stock emails.
Low Email Subject The subject of the low stock email. This field has token replacement.*
Low Email Body This is the body of the low stock email. This field has token replacement.*
Automatically change stock levels Turn this on if you want the system to subtract stock when a user purchases. If this is set to "No", the system will not update stock levels.
Show out of stock messages Turn this on to show out of stock messages on the product page when stock goes below the out of stock level.
Show in stock messages Turn this on to show how much stock is left on the product page.
Out of Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
In Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
Other Messages*
Out of Stock - Basket Line Marker This helps the user to see which products have gone out of stock when looking at the basket. A red asterisks may be a good indicator for the user.
Out of Stock - Basket This message is shown to the user above the basket when a product has gone out of stock when adding, updating, or looking at the basket. Products can go out of stock at anytime, even after a user adds it to their basket. This is because stock levels only change after checkout.
Out of Stock - Checkout This message is similar to the out of stock basket message. It is shown on the payment screen during checkout. This should be considered one final inventory check before allowing the user to purchase.
* Token Replacement This module has a few built in tokens for messages that allow you to give yourself and the user more detailed information. Some of the tokens below can only be used on certain screens, or in emails.
%%stock%% - Displays the current stock level. (1,2,3) %%basket_quantity%% - Displays the amount in the basket and is unlikely to be used. (1,2) %%available%% - Displays the amount of stock left before hitting the out of stock level. (1,2,3) %%oos_level%% - Displays the out of stock level. (1,2,3) %%line_items%% - Displays a list of line items that are effected. (1,2) %%product_id%% - Displays the product id. (1,2,3) '%%product_code%% - Displays the product code. (1,2,3) %%product_name%% - Displays the product name if available. (3) %%attribute_code%% - Displays the attribute code, or None if the effected product is only being tracked at the product level. (1,2) %%option_code%% - Displays the option code, or None if the affected product is only being tracked at the product level. (1,2)
1. Is used for the low stock email body and subject 2. Is used for the out of stock basket message and out of stock checkout message 3. Is used for the in stock and out of stock messages on the product pages.
Product Configuration Screen
All inventory settings will use the global configuration settings found in
the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. To override these settings at the product level, go to the product in the administration area and click on "NetPush Advanced Inventory". You will see the settings below.
Configuration Settings
Use NP Inventory on this Product You must set this to "Yes" if you want to track inventory on the product. You must manually set this to "Yes" for every product that you want to track. If this is not set to "Yes", no inventory tracking will take place. By default, no product is tracked.
Override Global Settings If this is set to "Yes" the configurations settings will be taken from the individual product screen instead of from the Global configuration settings found under under system extension configuration. If set to "No", the module will use the global settings from above when doing inventory for the product. The default is to use the global settings.
Amount considered out of stock Overrides same setting under Global Configuration.
Deactivate when product level is out of stock Overrides same setting under Global Configuration.
Allow purchase even after out of stock Overrides same setting under Global Configuration.
Automatically remove from basket Overrides same setting under Global Configuration.
Send Low Inventory Notices Overrides same setting under Global Configuration.
Amount considered low Overrides same setting under Global Configuration.
Low Email To Address Overrides same setting under Global Configuration.
Low Email From Address Overrides same setting under Global Configuration.
Low Email Subject Overrides same setting under Global Configuration.
Low Email Body Overrides same setting under Global Configuration.
Automatically change stock levels Overrides same setting under Global Configuration.
Show out of stock messages Overrides same setting under Global Configuration.
Show in stock messages Overrides same setting under Global Configuration.
Out of Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
In Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
Other Messages*
Out of Stock - Basket Line Marker Overrides same setting under Global Configuration.
Out of Stock - Basket Overrides same setting under Global Configuration.
Out of Stock - Checkout Overrides same setting under Global Configuration.
Setting Product Inventory Levels
The administrator can set product inventory levels by going to the product page within the Miva Merchant admin area and clicking on NetPush Advanced Inventory. This is the same screen as the product level configuration. Product inventory levels are shown below the configuration area. To add new inventory, use the yellow add button. To edit inventory, click white add button next to the inventory entry.
The module checks inventory by looking at a unique combination of Product Code, Attribute Code, and Option Code. When entering stock levels, you enter the codes separated by a pipe. For example, shirt1|color|red, where shirt1 is the product code, color is the attribute code, and red is the option code. If you do not set an inventory level for an existing product attribute combination, no tracking is done. Setting a stock level of -9999 has the same effect.
Inventory at a product level You may choose to only track inventory at a product level in combination with or not at an attribute level. To enter a stock level for a product, simply use prodcode||. This tells the system that you are tracking the product code, but not the attributes or options by leaving them blank. Using -9999 for a stock level will temporarily turn inventory tracking off.
Inventory at the attribute level (checkbox, select box, radio buttons) Checkbox - prodcode|attrcode|(the last field should be left blank, as checkboxes have no options) Select Box and Radio Buttons - prodcode|attrcode|optcodeAll 3 are required and must be unique, even if you are using attribute templates. If you are using normal templates in combination with attribute templates, make sure you do not give them duplicate code names.
Using Advanced Inventory with Template Modules and OpenTokens
The Advanced Inventory Module can be used with 3rd party template modules like the ones from Viking Coders by using Open UI tokens on product pages to display current inventory levels. Please note that token support has not been completely tested as of yet.
%module|npinventory|stock_level% Returns the stock level for the product, attribute, option combination. To ensure that this works correctly, you should set g.NPI_Product_Code, g.NPI_Attribute_Code, and g.NPI_Option_Code to the current product code, attribute code, and option code. On a checkbox, make sure to set g.NPI_Option_Code = ''. On a product level, make sure to set the attribute and option variables to ''. After these globals are set, call the token. If the return value is -9999, the item is not being tracked.
%module|npinventory|stock_available% Same as above but shows the amount available.
%module|npinventory|oos_level% Same as above but shows the out of stock level.
%module|npinventory|stock_list% This token will set a global variable that contains an array of structures. You must set g.NPI_Product_Code equal to the current product code before calling the token. This array contains all of the product code, attribute code, and option code combinations for a specific product. It also contains the available stock, out of stock level, and other information shown below. This token makes it easy to create a stock table using OpenUI tokens in Viking Coders templates or in a product header or footer. Code examples are available in the help pages on the NetPush.com site. Array Structure: g.NP_Inventory_StockList[i]:attribute_code - Attribute Code g.NP_Inventory_StockList[i]:option_code - Option Code g.NP_Inventory_StockList[i]:stock_level - Stock Level g.NP_Inventory_StockList[i]:oos_level - Out of stock level g.NP_Inventory_StockList[i]:available - Stock Level minus out of stock level g.NP_Inventory_StockList[i]:allow_pur - Allow purchases even if out of stock from admin settings g.NP_Inventory_StockList[i]:low_amount - Low amount from admin settings g.NP_Inventory_StockListLen - Variable that tells you how many items are in the array (represented by i above)
The Miva Corp inventory management system for Merchant 4.0 has resulted in numerous stores having their shelves temporarily cleared. As customers place products in their baskets, the store inventory level is decremented. If the customer decides not to buy at that time and leaves the store, the products in that abandoned basket remain unavailable. When the store owner manually deletes expired baskets in admin, those basket contents are reclaimed and the products are placed back in the store inventory. Stores which have one-of-a-kind or low inventory levels of products are significantly impacted as the products are not available for purchase by other customers until the store is manually restocked. Stores which have high traffic are similarly impacted when many baskets are abandoned. This module eliminates the need for the store owner to manually restock. At a frequency determined by the store owner, this module will reclaim the expired baskets and restock the shelves. This module may not be required in future versions of Miva Merchant as a similar fix has been requested through the Miva Corp wishlist.
This module is for Merchant 4.0 and is compatible with both the MMUI and OpenUI. Editing of mv files is NOT required.
The need for this module readily became apparent after using the Show Baskets module which identified what customers were leaving in abandoned baskets and how frequently they did that.
Compiled: New in the compiled version is an activity log. It accumulates the numbers of baskets which were not converted to orders and have been reclaimed. It also captures the completed order totals. These numbers can be displayed for any time period. See the screen shots below. The information can be useful when evaluating your success at convincing "visitors" to actually buy something. Another useful usage of this tool is monitoring how often and to what extent search engines spider your merchant.mv pages. You will periodically see a glut of abandoned baskets when the restock module runs. You also have the option of the module sending an email to you each time it restocks the shelves. This is useful in identifying problems with your payment gateway as it identifies baskets which were reclaimed, yet had products in them. This is to be expected within reason, but if you see a significant increase, it may be because your payment gateway is down.
Chat with your customers in a live session online. If you have our Show Baskets module (version 4.59 or newer) you can identify and open a chat session for a specific basket. Then with the Talk Back module, the customer can read and respond in that open chat session. Both the Show Baskets and Talk Back modules are required in order to transmit messages from the store admin to the customer in a chat session.
You can use a module token to display a "Chat" button for the customer to hail store staff. When
they click the button an email is sent to your predetermined email address you use to notify staff that there is someone in the store who wants to chat live.
The store staff can open the session by posting a first message. Once the store begins the dialog, an image or text can be displayed on the storefront (using a token) which invites the customer to chat. If they click the invitation, their chat window will popup. The store and customer can then chat live.
The refresh rate is set by the module's configuration, as is the various buttons and text the customer sees.
Limitations: The module depends on the customer using cookies and that the cookie does not change each time the customer clicks on a new screen. The cookie (session ID) needs to remain with the
customer as they shop in your Merchant store anyway or they would not be able to maintain items in their basket. The customer cannot have popups blocked and they must have javascript enabled.
Required companion modules: 1) You must have Show Baskets version 4.59 or newer in order to use this module. 2) OpenUI must be installed in the store.
Basket Master bundle contains basket tools for both the store owner and customer. It contains four of our most popular basket related modules for Miva Merchant storefronts.
Features: (some features are only in the compiled version as indicated below) o Mini-basket and Recent Visit History Display - Summarize basket contents on most Merchant screens - List product name or code, quantity, and price - Use image to alert new additions made to basket (compiled) - Display a checkout link when order minimum is reached - Use store's assigned shipping modules to preview shipping options and charges - List recently visited product pages with easy add-to-basket button (compiled) - Optionally use OpenUI token to place the mini-basket in many places on the screen (compiled) - Optionally use OpenUI token to place visit history outside of the mini-basket (compiled) - Owner can monitor live activity of customers visiting product pages through admin (compiled) - Customize mini-basket look in admin (color, size, headings) - Built-in link to view main basket - Optionally hide mini-basket if no products are in it (compiled) o Restock Shelves - Eliminate the need for the store owner to manually delete expired baskets - Automatically reclaim expired baskets and restock the inventory - Activity log shows completed orders and abandoned baskets totals for comparison (compiled) - Activity log for any time period and displayed as text and graphics (compiled) o Show Baskets - Display open baskets (active and expired) in table format o Lost and Found Orders - Display contents of baskets before and after the order is finalized - May aid in the recovery of missing order info
- Licensed per domain - OpenUI or MMUI compatible (OpenUI required in compiled Merchant) - Save 15% by buying these licenses as a bundle
The ELM Statistics Package for Miva Merchant will give you even the minute details about what's popular at your store and what isn't. Use the package to track items viewed and purchased and to analyze product placement.
ELM includes Top 100 reports including:
products viewed, added/removed from basket, and ordered
categories viewed
searches
browsers/platforms
states/countries shipped to
Other Features:
Daily, monthly, annual, and customizable date range reports
Detailed sales reports
On-the-fly bar graph generation of screen/action breakdowns across date ranges
Last 100 users report including, date/time, screen, actions, paramaters, browsers/platforms, and IP addresses
Logging block from your own computer(s)/browser(s)
Individual product reports including number of instanced viewed, added/removed from basket, and ordered
Flat file export of complete product statistics for easy import into your favorite
database/spreadsheet application
Convenient hyperlinked integration with your store from product, search, and category reports.
ELM is licensed per store, and all statistics are stored on your server. Simple plugin installation via the Merchant administrative program. No code modifications required. Runs independent of your ui, so ELM will work with mmui, kcui, OpenUI, or any other ui module that accords with the Merchant API.
The StatCat module is both an admin module and a basket interface module. The primary purpose of StatCat is to generate static catalog pages (indexes and sub-pages) directly from your Miva Merchant products and category databases so that search engines will add your pages to their index. Presumably this will allow customers to find your store amongst the millions of web sites on the Internet. As such, the pages generated are basic html pages with links to sub-pages, basket page and individual product pages in your Miva Merchant system. Each page contains your store title, meta description, meta keywords, footers along with the products. Category pages also contain category headers and footers.
Although these are static html pages, they have direct links which allow customers to add the products to their basket which is maintained in your Miva Merchant shopping cart system. If you are using the CIM Inventory Manager or Miva Corp's new Inventory Manager (in Merchant 4.x), it will even check the stock level and return an out of stock message if stock level is depleted
** Caution: If you are using Merchant 4.0 and its Inventory Management system that deducts products from inventory when they are placed in the basket, you should select to NOT use the Add to Basket buttons if you have one-of-a-kind items. The reason for this is that some robots and other indexing software may even follow links which contain the ? and & characters. This could result in the stock level decrementing to zero and out-of-stock emails being sent. The products won't be removed from inventory completely, as they will be re-stocked when you run the Admin:Delete Expired Shopping Baskets. This undesirable situation does not exist in Merchant versions 2.x or 3.x. It is also not a problem in Merchant 4.x if your store does not use the Miva Corp Inventory Management or your product stock levels are not likely to be depleted with one or two passes of the indexing program.
The store owner determines which page the customer will go to when they select to add a product to the basket. They can be taken either to the basket for review or back to the static page they just selected from. Both processes are automatic and do not require Javascript or meta refresh routines. Either click through destination can be used on either of the sort options, store owner choice. In addition to the functionality of this module, it provides an excellent example of how to interface static pages with the Miva Merchant system with return to the correct static page.
Quick links on each sub-page allow the customer to return to the index or go straight to their basket for review and checkout.
Below the sub-pages the store owner can even generate individual product pages. These product pages contain the full sized image and description. If the store uses the Flexible Product Description module and the product record contains a Keyword field, those product specific keywords are added to the store's generic keywords which are already in all of the static pages.
The store owner can decide whether to display the price for each item on the static pages. Since these pages are static and cannot function interactively to determine customer price groups or discounts, the hide price routine has its place. However, if the store has no price groups and discounts are calculated on basket totals or discount coupons, the price listing is useful.
The static pages also have no way to restrict access. So if your store is one which does not allow certain products to be shown to all customers, then this module is not for you, unless you can place all of those restricted products in specific categories. In which case, you could then sort pages by category and simply delete those categories' pages.
This module is for Miva Merchant 2.x, 3.x and 4.x. It works with both the Miva Merchant look and feel (mmui.mv) and the OpenUI look and feel (oui.mv). If using the mmui.mv, there are two edits that need to be made to the mmui.mv file.
StatCat produces pages similar (mirror) to the layout in Miva Merchant with admin control. The following configuration settings are made within the standard Miva Merchant admin interface: Page title, home URL, optional title/store logo, title background color, title foreground color, category title header size, number of product columns on the category sort page, Meta description of the site, Meta keywords on the site, return action after adding a product to the basket, option to hide the prices, category column background color, category column foreground color, category column font, category column size, product background color in the category sorted pages, product foreground color in the category sorted pages, product font and size in the category sorted pages, optional display of thumbnail images in the category sorted pages, store front page welcome screen, search button input, product descriptions on category pages, and page footer.
Once generated, the index pages can be linked to your main home page. The catalog can be left in the directory it is generated in or copied to any web site (or multiple web sites) to increase search engine visibility. The links to images and back to your Merchant.mv store will work across servers. An example of this remote distribution can be seen at my Yahoo/Simplenet web site. The limitation to the remote distribution is that these remote static pages are one way, ie. placing a product in the basket will take the customer to the main Merchant.mv, but not back to the remote static page. They would then continue shopping in Merchant.mv. This limitation exists only if the static pages are not in their original catalog directory. If they are in the catalog directory on the local server with Merchant.mv, then return to the static pages is one of your options in admin.
The StatCat also has the ability to generate static pages which can be placed on a disk and used as a catalog which can be mailed or given out to potential customers. When using this option, links to your web site or the shopping cart are suppressed. An example of this type of catalog can be seen online. It has no links to the cart and the images are virtual to the static html pages.
When generating the catalog, the store owner has the option of restricting the html output to a list of specific categories. This is particularly useful when the store owner wants to place their static pages on remote servers which have specific themes in a mall environment. Some categories may "fit in" and some may not. This also might be useful if you want to create disks with only certain categories of products on them to be given to customers.
Note 1: StatCat uses the first letter of the product name to name the sub-pages. If you use illegal characters for the first letter of product names, you will not be able to generate the by-name catalog. An example would be the left bracket, as some might have put the font tag at the beginning of the product name. If that is the case, use the by-category catalog.
Note 2: If you have an excessively large products database, you will probably not be able to run StatCat on a server without timing out. However, you should be able to run it in MivaMia if you have a mirror of your store on your PC. You would then need to upload the static pages manually. This store of 600 products took about 5 seconds to generate the category pages.
Click through returns to the originating static page after addition (alternatively you can have it remain at the merchant.mv basket)
This example contains StatCat generated individual product pages
Several new features have been added to the compiled version; background image, functional navigation bar, "smart" metatags, extensive implementation of keyword and header and footer usage, product page names can be product code or name ending with html, inclusion of product links at the top or bottom listed as featured products or similar designation, include any fields in the products database on product pages (including modified structure), optionally hide subcategories on category pages as applicable, additional product page links such as "check availability or latest prices", and export to any directory within the store's path (creates directory if it does not exist). Discontinued (inactive) products can continue to have modified static pages generated so that search engine links remain viable, yet do not result in errors when linked to the store. Additionally, affiliate codes can be included with every link so that the static catalog pages can be given to affiliates who wish to mirror your catalog at their site. If you are using the OpenUI, StatCat adds "smart" metatags to your merchant.mv so that when the customers (and search engines) click from your static pages to your actual store, the pages will contain metatags related to category headers, product descriptions and product keywords (if used). It also reverses the title tag with the category and product screens so that the category or product name appear first, then the store name. If your store has our Volume Pricing module version (4.53 or higher) installed, StatCat can optionally include the volume price table on the static pages. When creating the static product pages, a flat file is created in the background which can be used for a data feed file for submission to FroogleTM. It contains the header and data for the basic file format.
The Gift List Registry can be used by couples for wedding registry, by children making their birthday or Christmas list, or that "significant other" who wants to be surprised by not knowing the specific item they are going to receive. This module can also be used for personal wish lists.
Gift List shopping allows a person(s) to select a list of products they would like to have. They place the products into their shopping basket. Then, rather than checkout and pay for the items, they save them to a Gift List Registry. For quick saves, they can also save them from the individual product screens. In Merchant 4.x and if you are also using our Tell A Friend module, a convenient button is placed at the bottom of the Gift List display to forward the URL for the Gift List to friends.
Then, you as the gift giver, can review the list and select the item or items you would like to give them.
Customers can also save items they plan to purchase later by placing them in a wish list. The admin
configuration allows the store owner to change the labels from gift list to wish list.
The admin report allows you to view all active gift lists.
This module allows you to maintain the gift or wish list database on your server. There are no ridiculous monthly/quarterly fees to pay to other companies just to store customer wishes on their server. You control your data.
New in the compiled version is the ability to save attributes of products to the Gift/Wish List, e.g. S, M or L. Also, we've
added the compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the Gift/Wish List save button on the product page so that it better fits your desired look.
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 save to Gift/Wish list button on the Merchant pages so that it better fits your desired look.
Most agree, Yahoo! is the king of commercial and non-commercial directories on the Internet. Their new venture to create a listing of actual items for sale across the Internet, rather than pages with hits on keywords, is a bold attempt to better target customers and buyers in a symbiotic relationship.
This is a giant leap in eCommerce, providing comparison shopping using the Yahoo! Product Search index. If you are a Miva Merchant store owner you CANNOT afford to miss this
opportunity, especially since inclusion in the beta test index is currently free. How much have you invested in getting your store's search engine rankings? If you find you are getting traffic and earning revenue from this venture, you may find it beneficial to stay on after
the beta period has ended. This gives you an opportunity to "test the waters".
Include an affiliate code in the URLs so that you can better track where actual sales are coming from
If your store is a single store in the domain, you
can remove the Store_Code from the URL to aid in search engine spidering
If you are using our Flexible Product Description (recommended) or our Edit More (only for the very experienced) modules, the additional field data can be added to the description for the general products data feed.
Y Feed plugin module creates the datafeed flat file directly from your admin
As this is a new endeavor for Yahoo! Inc., I expect them to change
their format and add new capabilities over time. Licensees of the 4.x version of this module will have free upgrades of the module through the 4.x version.
Limitations: 1) Currently the module can only be used for the general products export for Merchant 4.x uncompiled. With the compiled version (Merchant 4.14 and newer) of the module, you can export book, music, and video type products if you are using one of the additional field methods above.
2) We will be upgrading the Y Feed module for compiled Merchant (4.14 and newer) to include the following product categories in the future: video games, computers, and electronics.
Miva Merchant QuoteTrk System Extension Module allows your customers to save baskets as "Quotes" and to view their previous quotes. They can select a quote and have it transfered to their basket to checkout at a later time. "Save as Quote" shows up as a payment option.
Display the contents of baskets before and after the order is finalized. Once a customer enters their personal data, an order number is assigned to the basket. During the next few minutes a variety of things can happen, one of which is the order will be completed without error. On the other hand, an order may be not completed due to server error, communication between the payment processor and your store fails, the customer decides not to purchase, duplicate ID corruption occurs in your orders database, and any number of other perils.
If you have not packed your store databases, you may still be able to recover most information from lost orders. This module provides the ship to and bill to customer info. It lists the products and their attributes that were ordered. It lists the shipping, tax, coupons, discounts and other miscellaneous entries. It also displays the payment module and data element (not the CC number).
The data will remain in this file until you pack the store databases or the basket number is reclaimed by merchant. The number may be reclaimed if the customer re-visits your store after their earlier, abandoned basket had timed out. If they don't re-visit, the number will remain until you pack the store databases.
This module is also included in the Basket Master bundle. Save when you buy bundled module licenses.
TinyCart and History Helper allows you to create a template-based mini-basket, running subtotal, and/or recently viewed items display. The templates can be be shown above or below the category tree header or footer or above the tree sign-in link, as well as embedded within our Category/Product Page Template modules.
The TinyCart and History Helper are configurable independent of one another. Rather than being stuck with a default layout, the display of either can be entirely customized using a wide range of tokens such as thumbnail, product code, name, price, subtotal, basket/checkout URLs, etc. For advanced users, additional variable tokens are included which allow access to all global, system, and database variables available in Merchant. The recently viewed items can also be embedded as a token within the basket viewer itself.
To illustrate the display control offered, the default template for the recently viewed items displays as a drop-n-go drop down list. The drop down list is nice as it takes up a small amount of screen real estate, but you can change the template to something similar to the mini-cart. Or, use your imagination and come up with an entirely new template.
Both viewers optionally allow alternate text/html to be used if there are no basket/recent items to show. Additional settings for recently viewed items include the maximum number of items to display (1-99) and the number of minutes before recently viewed items expire (1-9999).
You can also give your customers the ability to lookup shipping rates based on their current basket!
*NEW You can now embed the tiny cart within static pages outside of Miva Merchant by using IFRAME like so: Add this product to your basket and then reload this page to see an example. This example has been customized with the easy-to-use admin interface, css, etc.
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 use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processing verified the charge, then forward to the drop shipper. This would save hand entering the order. In addition to the email, an archive flat file 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 address
and products ordered if using real time credit card
authorization. Products section can be torn/folded to
result in a shipping label with your company address included. If not using real time authorization, use the pending mailbox technique similar to the drop shipper scenario above.
Email a
promo coupon code if a customer purchases a specific
product 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 text messaging
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. Those
store owners rent the stores from you for a percentage of
their gross. Use mail manager as an audit tool to track their
sales. 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 spreadsheet
for easy analysis.
With compiled Merchant, the included Mail Manager Report
module can display the contents of that flat file
through admin. It can filter the report by specific time
periods (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 can
be 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 every
product in your store.
However, Mail Manager has a somewhat open architecture so that other events can also trigger an automated response. For example:
Send a
welcome email before the order completes, but after
the customer completes the registration process (for those that
create 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
Essentially any event in the mmui, oui or even another third party module can trigger an email which you write for the
particular event
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. If you don't have an account with us yet, sign up and you'll see how it works.
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:
In the compiled version is 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 formatted emails for better readability. You can change the fonts, colors, layout and even add images to your confirmation and notification emails. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template.
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
Write a different body for each of the email templates you add
Link 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 from a 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 it
to make connections not directly related to sales, yet
linked 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 800 number 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 in hopes 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's
business and decrease the amount of time employees spend on sending out product specific, followup emails.
MMUI and OpenUI compatible. No editing of the mmui.mv is needed and no OpenUI hook points are used. Thus, module conflict does not occur. The pre-formed templates are easy to configure and do not require programming experience. In the compiled version of Merchant (4.14 and newer), 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.
The ultimate Miva Merchant autoresponder module - send specialized emails at the completion of the order. These emails are in addition to or in place of the standard emails which are sent at order completion, e.g. merchant notification, customer confirmation, vendor specific notification, and even cell phone emails. It also can send welcome emails when a new customer account is created. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Autoresponder - specialized emails at the completion of the order - Merchant notification and customer confirmation - Vendor and product specific templates - Can limit sending based on a specific attribute/option code for a product - Include coupons or promo codes when specific products ordered - Optionally require an input to allow the email, e.g. a response from Addendum - Easy to use checkbox configuration of vertical or horizontal layout emails - Highly configurable free form template layout emails with embedded tokens - HTML or text email formatting - Archive flat file is created for each template, easily track sales activity - Mail Manager Report module can display the flat file contents by time period or product - Ship to, bill to and other email addresses for each template - Send emails to your company's internal departments, e.g. shipping - Emails to web enabled cell phones as abbreviated messages - Open architecture so that other events can also trigger an automated response - Can resend emails when the customer knows and enters their order number and email address - Use render token to send an email from any pagein the store - Send a welcome email before the order completes and optionally include a promo code, customer login and password - Include 3rd party data with module tokens, e.g. Addendum responses - Display shipping and payment invoice messages - Create packing slip and label emails - Ship to country address formatted according to the applicable country's postal recommendations - Restrict email to a specified order dollar value range, reward big spending customers with a coupon - Restrict email to a specified list of countries, thus allowing for language specific emails
Feature Details. In admin, you create one or more template emails. Eachtemplate can be different, i.e. what it displays, how the data is oriented on the screen/paper, and what product(s) triggers the autoresponder. Most responses are triggered by the product codes purchased. Some example uses:
Email to any of your drop-ship manufacturers listing the Ship To address and the products to be shipped if using real time creditcard authorization. The module will sort out which drop shippergets which emails, including listing the products to be shipped. Unlike some other vendors' drop ship notification modules, this one only includesthe products belonging to the associated drop shipper. Thus a drop shipper doesnot see the products being supplied to the customer by other drop shippers when the order contains multiple product sources. Youcan still use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processingverified the charge, then forward to the drop shipper. This would savehand entering the order. In addition to the email, an archive flatfile is created which you can use to easily track sales activity related to each of your drop-ship manufacturers.
Email to Ship To or Bill To or both thanking them for a donation to your sponsored charity on your site.
Email to your shipping department listing Ship To addressand products ordered if using real time credit card authorization. Products section can be cut/folded to result in a shipping label with your company address included. If notusing real time authorization, use the pending mailbox technique similarto the drop shipper scenario above.
Email a promo coupon code if a customer purchases a specificproduct or from a list of products
Email service, warranty, shipping and contact information on specific products or product lines
Send an email to your cell phone's inbox when orders are placed in your store (requires a cell phone plan that assigns an email address to your phone).
You own a mall with multiple stores within the mall. Thosestore owners rent the stores from you for a percentage of their gross. Use mail manager as an audit tool to track theirsales. In addition to the autoresponse email, mail manager produces a flat file with order ID, date, product name, product code, quantity, price for each, and price extended. Periodically retrieve that flat file and import into a spreadsheetfor easy analysis.
The included Mail Manager Report module can display the contents of that flat file through admin. It can filter the report by specific timeperiods (daily, weekly, monthly) within reason. The limits of your PC or server may prevent very lengthy reports for excessively long time periods. It can also limit the report to only one product code. Since the templates canbe designed for each vendor, you can create individual vendor flat files with a corresponding report for each vendor.
Literally, you can have a different autoresponder for everyproduct in your store.
However, Mail Manager has a somewhat open architecture sothat other events can also trigger an automated response. For example:
Send a welcome email before the order completes, but afterthe customer completes the registration process (for those thatcreate an account)
Send a thank you for rating a product (using our Rate This system)along with a coupon code for taking the time to do so
You can use the ifvar script or var token in these "other event" emails. For example, generate a unique coupon code with a module token and insert it in the welcome email to give the new customer an incentive to buy now.
Use a render token to send an email from any page in the store. For example, put it on the product page to send a specific email when a specific product's page is viewed by a customer who is logged in. The email goes to their password recovery address (but could be bill to or ship to address). If you want it sent to a hard coded address, e.g. yours to monitor traffic,you would put your email address in the 3rd parameter of the token. The uses of this feature are endless. Send a coupon to entice customers to buy when they visit specific product screens. Tell them about other products related to the one they just viewed.
As you can see, the uses of this Mail Manager are quite diverse. Some of the variable features configured through admin for each template are:
Show or hide any of the data elements
Orient your email either horizontally or vertically
There is also a free form template using an extensive list of tokens and mini-scripts to customize the emails that are sent at the time of order completion. They can vary from mimics of the standard merchant notification and customer confirmation emails to brief order notifications for better acceptance within cell phone emails. The emails can be plain text or HTML formattedemails for better readability. You can change the fonts, colors,layout and even add images to your confirmation and notificationemails. If your shipping and payment modules are configured withinvoice notices, these can be included in the emails with a token. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create packing slip and label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template. In the free form template you canalso set the time so that it can be offset from the server time,thus display for a different time zone in each of your emails.
Customize your email and store's physical address
Designate email recipient, i.e. Ship To and/or Bill To and/or fixed email address
List full or partial Ship To and/or Bill To address
Restrict email to a specified order dollar value range, reward big spending customers with a coupon for their next visit
Restrict email to a specified list of countries, thus allowing for language specific emails
Resend order emails if the customer knows and enters the order number and email which match the actual order. The form for these two data elements can be placed anywhere you can edit the store user interface, e.g. headers, footers, welcome screen.
You can specify the product code and an attribute/option value that must also be met before the email will be sent. This is particularly useful when the emails are used for vendor notification. A certain product might bedrop shipped by two different vendors and the only difference is the selected attribute/option value.
Insert a "require" token that has to be met before the email will be allowed. As example,have a checkbox using Addendum to ask a customer if they want to be added to a list server (mailing list). Then if they check the box, the "yes" response is sent to Mail Manager. The Mail Manager can then generate a specifically formatted email to activate an email address at your list server, if you have one.
Write a different body for each of the email templates you add
List products and prices or just the products without prices
Link the email usage to one or more product codes or entire inventory with wildcard
No need to go to each product to link the email, a copy and paste froma flat text file will add hundreds instantly
I'd be surprised if you find that this capability exists anywhere in any mid-priced shopping cart system. Autoresponders that fill in the blanks are one thing, but this is a store owner, pre-planned autoresponse for a specific product. Within your store, you could have dozens of different responses (individual or grouped) or a wildcard response for all of the products. You can use itto make connections not directly related to sales, yetlinked to a specific sale.
Customer buys a kayak from your store. Tell them about the kayak camp 20 miles from your store and give them the 800number of the guy with the info about a big get together next month.
Customer buys an orchid from you which would lead you to believe he/she may have a specific variety you have been looking for. You autorespond with your want list for your nursery inhopes of finding the needle in a haystack.
As you can see, this list could be endless. Targetted, intelligent autoresponders are designed to increase your store'sbusiness and decrease the amount of time employees spend on sendingout product specific, emails.
The pre-formed templates are easy to configure and do not require programming experience. For the more experienced, you also have the option of using tokens and mini-scripts in free form templates. An example free form template is included with the install documents.
This module 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.
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. 
