Found 448 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.
Provides tokens and templates formatting for some of the "other" pages of Merchant. You can create templates and assign them to some of the pages of Merchant (currently the module supports template assignment to BASK (basket page), PLST (product listing), LOGN (customer login), and Missing Attributes), Upsell, Search, etc. In addition, you can create a template for you own page, create a "screen" variable for it and link to it directly.
The category and product pages are still best handled by the Category Page Templates and Product Page Templates module, the storefront by the Storefront Template Module, and the search page by the Search Manager)
The templates are created and modified exactly like the templates in the other template modules. However since they are assigned to screens rather than products or categories, that part is a bit different.
The way Merchant works is that most of the pages are assigned "identifiers" which Merchant uses to determine what page is to be generated. For example, if the variable Screen is set to BASK, Merchant knows that it needs to display the basket screen. The module intercepts that process to use templates to display the screen instead of Merchant's default screen. This is done by assigning templates to the identifier. The module comes pre-configured with a number of different templates which you can assign to the screens of Merchant. For example, the "Basket Page" template can be assigned to the "BASK" screen to display the basket screen using that template.
NOTE REGARDING COMPATIBILITY: This module has the same compatibility issues with other modules as the original template modules. This module totally replaces the portion of the OpenUI (or MMUI if you are using it) that displays the pages it intercepts and is not compatible with any other module which needs to hook into that page unless the developer of that module has specifically made their module compatible. And given that this module is so new, very few modules are completely compatible with it. This module provides for an easy-to-use manner for developers to provide tokens that can be used to insert their module's HTML into the pages. And these tokens can be registered in the module's admin interface.
NOTE/WARNING: although there are a number of people successfully using this module, given the large number of tokens and attempts to handle many pages of Merchant you can expect bugs to arise and for the module to be missing functionality. I'll work diligently to fix them but please don't purchase this module if you can't accept the possibility of some issue with the module keeping you from accomplishing what you're after.
Similarly, given the current state of the documentation (there is no documentation on the available tokens but most of them are present in the pre-configured templates) if you're not familiar with the other template modules and the use of tokens in templates, you might want to wait until the documentation is completed.
Another note about compatibility: This module is compatible with the OpenUI right out of the box. However, for it to be compatible with the MMUI requires a minor modification to the MMUI file (ie. mmui.mv).
The Category Manager module allows you to have multiple category templates in a single store. You can have a different template for every category in your store if you want. The templates use the standard store morph technology template editor in MIVA Merchant 5. While basic knowledge of how to edit MIVA Merchant 5 templates is required, there are two example templates provided in addition to the built in ctgy page template. Getting started is not that difficult. Don't miss our introductory price of this versatile module.
Features: - Multiple category templates in a single store - One or more categories can be assigned to use a specific template - Default template is used for categories which do not have a custom template assigned - Custom pagination in addition to the default Previous and Next buttons - Can limit products displayed per page to a specific number for each template or can list all on one page - Customer can sort products within the category in real time dynamically - Breadcrumb navigation included - Sub-category navigation included
Feature Details. Multiple page templates. Using the built-in store morph technology, you can edit the page templates just like the built-in page templates, including recall, notes, and indexing of previous versions. Include typical render tokens on the custom category pages from other 3rd party modules (sold separately) which you have in your store, e.g. rate this, wait list, best seller, and others.
Easy assignment of categories to templates. Once you create the template you can assign one or more categories to it. This can be done from the Category Edit screen or if you are using the Emporium Plus Category Import module (sold separately), you can import the template assignment right along with importing new categories into the store. No need to import the categories with one module and then use a separate module to assign them to templates.
Default page for unassigned categories. The default ctgy page template is used for all categories which have not been assigned to a specific custom template. This makes processing more efficient as the Category Manager runs a quick lookup to determine if it needs to run certain more complex processing routines, like advanced pagination.
Advanced page navigation. Several pagination variables are available to write detailed page navigation links. You can have the typical 1 2 3 4 etc. Or you can break up long lines with arrows, dots, dashes, etc to fill in a gap. You can also display the page number of the total number of pages. This pagination is similar to that used in the Emporium Plus Power Search module for Merchant 5. As a point of reference for the customer, you can even include how many products are listed in the category.
Flexible pagination. Each category template can have a different setting for the number of products to display on a page. Initially, the customer will see the number you set. However, customers using broadband may want to see all the product in a category on a single page, so there is an option to list all.
On-the-fly sorting. The products are initially displayed in the sort order which the store owner has previously setup in the normal admin sorting. The customer can then change the sort order based on their desires. Available sort fields are name, code, price, date items were added to the store, or the default store setup. They can be sorted ascending or descending.
Breadcrunb navigation. The module includes optional breadcrumb navigation. An array is created which holds the current category name and its parents up to the top level category. With standard MIVA Merchant template code, you can create a quick link to higher categories like Home > Software > Developer Bundles
Sub-category navigation. You can display the sub-categories of a parent category on the category page, e.g. below the parent category's name. The array can be displayed like you want it using standard MIVA Merchant template code.
We cannot link to our demo stores from MivaCentral so if you'd like to see a couple of the live pages demonstrating single or multiple column layout of products, please contact us for links. Those pages demonstrate the variable layout of products, breadcrumb navigation, on-the-fly sorting, and sub-category navigation.
The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server. This would be the case in most of the server setups. For those that are not, we are in the process of converting the code for that remaining, very small group of MIVA Merchant stores. At this time we have not had a problem. Modules will be moved to the top of the queue as needed.
Search Engine Optimization (SEO) is a key to the success of your On-Line business. This module provides a multi-level control of your store meta tags. You can specify meta tags on a global, page, category and product levels. Module provides a template field for each of its levels, along with an Advanced META Tag Generator Tool which will quickly generate common meta tags, based on provided information. METAMaster Module is designed for easy intallation and is automatically configured for SFNT Storefront, CTGY Category Display and PROD Product Display pages. You can easily add this functionality to any other page used by MIVA Merchant system. This gives you master control over your store meta tag settings.
The ADS META Master Module Features:
Simple Module Installation and Configuration
Automatic installation, configuration and item assignment for SFNT, CTGY and PROD pages.
Automatic installation and assignment of revised Storfront, Product Display and Category Display templates. Current version history templates are used to generate revised templates. Previous template versions will be available through version history.
Multi-Level control of store meta tags. Global, Page, Category and Product Level controls are available.
Advanced META Tag Generator Tool which will quickly generate common meta tags, based on provided information. You can also quickly check the character count for META Description and Keywords. This tool will be available on all METAMaster controlled fields.
Module is fully compatible with Merchant Template language. Tokens can be used to dynamically populate information in your meta tags, which can be a great time saver.
No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
Global Level Control:
Global META Tag settings are used if no other meta tags are available
Global Level Control can be used on any of MIVA Merchant pages
Advanced META Tag Generator Tool make creating meta tags simple
Tokens can be used to automatically insert content
Page Level Control:
Page META Tag settings are used if no Product or Category meta tags are available
Page Level META Tags take priority over the Global Level settings
Page Level Control can be assigned to any of MIVA Merchant pages
Advanced META Tag Generator Tool make creating meta tags simple
Tokens can be used to automatically insert content
Category Level Control:
Category Level META Tags take priority over the Global and Page Level settings
Advanced META Tag Generator Tool make creating meta tags simple
Tokens can be used to automatically insert content
Product Level Control:
Product Level META Tags take priority over the Global and Page Level settings
Advanced META Tag Generator Tool make creating meta tags simple
Tokens can be used to automatically insert content
Additional Module Uses:
Easily add module functionality to any other page used by MIVA Merchant system.
Use this module to provide additional content to the page HEAD area, specific to individual page templates, categories and products. The content may be javascript, stylesheets or any other page, category or product specific information that belongs in the HEAD section of the page.
Sample META Master Category configuration screen with Advanced META Tag Generator Tool
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with Item "ads-metamaster", PROD Product Display, CTGY Category Display and SFNT Strorefront page templates that are pre-installed and configured with this module.
Original templates and/or Merchant "Original" templates will not be modified by this module and can be restored, using the new Version history features, at any time.
No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
The purpose of Power Search is to allow a customer to search one or more fields which are allowed by the store owner. The store owner can choose any fields within the products database and/or the custom product fields (Miva Corp built-in utility module) database to be searchable. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Implements field specific, keyword searching - Uses store morph technology to build templates with version history - Customer selects the fields to search and the sort order they want the results displayed - Search the whole store or limit to one category - Search by all (AND), any (OR), exact phrase, or begins with - Display total found, number of pages, and links to each page when the results exceed one page - Use the same product list layout as original search or alter for your needs - Can limit search to a specific price range - Use in conjunction with the Emporium Plus Tell A Friend module to send searches to a friend - Product page "return to search" link takes customers back to the same search page - View admin log of searched words/phrases for marketing and keyword identification - Maintain compatibility with 3rd party modules which use the MIVA Corp custom product fields - Create pre-defined select list searches on a single field - License per domain/mall
Feature Details. Easily editable templates. The module has five templates which can be used for each section of the search page. The templates have full versionhistory and use standard Merchant 5 template coding for easy update and rollback of changes. Each template is pulled into the location you want it on the search page using a render token. The templates are field selection, category selection,search scope/type, page counter and links, and product list layout.
Search specific fields and sort results. Allow a customer to search one or more fields which are made selectable by the store owner. The store owner can choose, in the admin screen, any fields within the products database or the MIVA Merchant built in custom product fields database to be available. The Power Search module uses a mirror database of your products, custom fields and categories; much like the big search engines use. By creating a mirror before the search is made, many operations to join multiple databases togethercan be avoided, so the customer gets a much faster search. Customers can also sort the results on fields like name, code, price, cost, when they were added to the store, or the default display order the store owner established for productlists. The build of the mirror database goes quite quickly and is a maintenance procedure you will do periodically. The small amount of time you take to build the mirror will save your customers significant amounts of time in their searches vs searches which don't use an optimized mirror database. Buildingthe mirror is not required just because products are added, deleted, or edited; as those processes update the mirror automatically without needing a rebuild. See the install doc for details.
Category selectable. Customers can use the category selector to select just one category to search. The default is to search the whole store. You can use the built in token which lists all categories with one or more products in them oryou can build your own select list of only certain categories.
Multiple search types. The customer can select how they want to search the database. The default is to search for products where all (boolean AND) of the keywords entered are found in the record. The customer can broaden that search so that any (boolean OR) of the words are found in the record. They can search by exact phrase so that the words must appear in thesame order in the record as was entered in the search input. They can also search the fields where the data in the field begins with the search string. This is useful for things like finding all of the products whose NAME begins with a specific letter and allows you to have a list of A-Z links that implement that specific search.
Advanced pagination. The module can display the total number of products found which match the search condition. Additionally, the pagesare numbered, e.g. Page 3 of 20, when results exceed the configurable number of products per page. You can also display alist of page numbers and links to those pages so the customer can jump to the page they want to look at. This pagination is similar to that used in the Emporium Plus Category Manager module.
Product layout template can be customized. In the 'srch' page template, there is a "search results layout". If you are happy with that layout, you can copy and paste the contents of that template into the Power Search module's product layout template. You can then modify the layout in the Power Search admin screen.
Price range searching. While searching the price field might be useful in some cases, a more popular search is price range. Within the searchable fields section, the customer has the option of entering a low and high price to create a range. If left blank, the search will not be filtered by price range.
Tell a friend module interface. If the store is using the Emporium Plus Tell A Friend module, customers can send the search string from Power Search to friends. The link in the email will go to the same page of products that the customer was on when they clicked the Tell A Friend button.
Return to search page link. After going to the product page from a Power Search rendered search, a convenient "return to search" link on the product page can bring the customer back to the original search page.
Search log with admin report. In admin, you can view the log of search words/phrases which your customers have used. This helps you from a marketing standpoint to determine the most sought after products and possibly the need to carry a new product. Additionally, it helps you identify keywords which might be useful to include in the narrative descriptions or the meta tags for search engine submissions and even local searches in your store. As example, while you might have a product called flip flops, customers might be searching for thong sandals (which is the same thing). But if you had not used those words in your description, you may have lost the sale. The log can be purged in the admin screen to reduce its size as desired.
Optimized search of built-in custom product fields. This module does not require that you use a proprietary 3rd party module for the custom product fields. It uses the built-in custom product fields module from MIVA Corp, thereby ensuring compatibility with other 3rd party modules which use those same custom product fields. No need to go down that proprietary datafield path of no return. As example, the Emporium Plus Template Data Feed module can use the built-in custom product fields to populate feeds to just about any search engine and shopping index with those "special" fields those indexes require.
Live examples. We cannot link to our demo Merchant 5 store from MivaCentral so if you'd like to see a couple of the live pages demonstrating searches, please contact us for the link. You can check out the selected field search in our test store which has about 600 products with multiple custom product fields. Try some searches so you can get an idea of search speed.
Pre-defined selectors. The Power Search function can also be used for pre-defined select pulldowns in your store. An example of genre and decade searches are in the lower left column of our test store's storefront screen. It will search a specific field, with store owner pre-defined selections. This same technique can be used for things like manufacturer searches if you have a manufacturer field in your custom product fields.
Liberal licensing. License is for ONE domain/mall. Within that single mall, it can be used in multiple stores without additional licenses.
This module requires that you are using MIVA Engine v5.03 or newer. When you log into admin, you can see which version of the engine is in use in your store.
The module lets you configure the category page html to your liking. It provides an interface for you to enter the specific HTML that you want to use to display the product listing for the category. You create templates which you can then assign to selected categories. The module comes with 4 preinstalled templates but you can add as many as you want. One of the preinstalled template provides for a category display that lets you add all of the listed products to your basket with the click of a single button. Another provides for the display of multiple products in rows across the page instead of vertically. In your templates, you can use tokens to represent the normal Merchant product and category fields. For example, you can use the token %prodname% to represent where you want the product's name to be displayed. Making changes like removing the "buy one now" button is as simple as tweaking the HTML used to display the page. One of the preinstalled templates is identical to the standard Merchant category display and serves as a good starting point for those little tweaks you have always been wanting to make. The module also permits you to copy existing templates when you are creating a new template.
You can use strike-thru pricing with this module too!
Note about compatibility with other modules: This module totally replaces the portion of the OpenUI (or MMUI if you are using it) that displays the Category page and is not compatible with any other module which modifies the category page unless the developer of that module has specifically made their module compatible. This module provides for an easy-to-use manner for developers to provide tokens that can be used to insert their module's HTML into the pages. And these tokens can be registered in the module's admin interface. All VikingCoders.com's modules are compatible with this module (ie. there are tokens that can be used to display their information on the category page) or soon will be.
Another note about compatibility: This module is compatible with the OpenUI right out of the box. However, for it to be compatible with the MMUI requires a minor modification to the MMUI file (ie. mmui.mv).
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 module lets you configure the product page html to your liking. It provides an interface for you to enter the specific HTML that you want to use to display the products in your store. You create templates which you can then assign to selected products. In your templates, you can use tokens to represent the normal Merchant product fields. For example, you can use the token %prodname% to represent where you want the product's name to be displayed. Making changes like moving the attributes or removing the "product weight" are as simple as tweaking the HTML used to display the page. A template is preinstalled which is identical to the standard Merchant product display and serves as a good starting point for those little tweaks you have always been wanting to make. The module also permits you to copy existing templates when you are creating a new template.
Note about compatibility with other modules: This module totally replaces the portion of the OpenUI (or MMUI if you are using it) that displays the Product page and is not compatible with any other module which modifies the product page unless the developer of that module has specifically made their module compatible. This module provides for an easy-to-use manner for developers to provide tokens that can be used to insert their module's HTML into the pages. And these tokens can be registered in the module's admin interface. All VikingCoders.com's modules are compatible with this module (ie. there are tokens that can be used to display their information on the product page) or soon will be.
Another note about compatibility: This module is compatible with the OpenUI right out of the box. However, for it to be compatible with the MMUI requires a minor modification to the MMUI file (ie. mmui.mv). Go here for instructions on making that modification.
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.
You've got your store spidered by the search engines, you're showing up in the search engine results, but you just can't seem to improve your rankings...Search Engine Tweak Pro (SETPro) is here to help!
Search engines take into account many factors when ranking web results, and one of the most important is proper page content optimization. Miva Merchant's dynamic page creation is not designed to be search engine friendly with how it creates and displays the page content. This is where SETPro comes in to play with a number of optimizations and enhancements for product and category screens. These optimizations are primarily done with the Google search engine in mind, but are also relevant to most other popular search engines.
PRODUCT SCREENS:
Product Name Tags:
Allows you to set the product names on the product screens to a preferred heading tag, bold, or none (
,
,
,
, ).
The keywords to focus on for an individual product page are typically contained within the product name. Making the product name a larger font size using the heading tags, compared to most of the other page content, adds extra weight to those keywords when rankings are determined.
Remove Store Name In Product Title Bar:
Optionally strips out the store name in the product screen title bars.
Page titles are extremely important to search engines. Miva Merchant adds the store name in the browser window's title bar along with the product name. This is a good thing, but it may also make it undesireable by diluting the product name keywords with an unnecessary store name, thus giving less weight to your keyword focus.
Product Description at Top of HTML Body:
Optionally placed at the very top of the page, just after the
tag in the page code, this displays the product name followed by the first 200 characters of the product description. Any HTML used in the description is stripped out before being displayed at the page top.
Stock Miva Merchant nests a considerable amount of hidden tables within one another. It makes for an adequate display but search engines don't see page content as the viewer does. That creates a large amount of page code that pushes the product descriptions far down the page, even possibly tripping up some older search engines. It's best to have your real keyword content as far up the page code as possible, creating more keyword weight and improving relevancy for the product pages. It's recommended to use either this option or the commented out feature described below, but not both.
Commented Out Product Description at Top of HTML Body:
Optionally placed at the very top of the page, just after the
tag in the page code. This option adds the product name followed by the first 200 characters of the product description text, commented out (hidden from view). Any HTML used in the description is stripped out before it's added to the top of the page code.
This is the same as the product description display above, except that the description and title are commented out, essentially invisible, at the top of the page. Most search engines will ignore comment tags but some may take them into account. This is an elegant alternative to actually displaying the product name with description at the top of the page, leaving the page as it's meant to be displayed. It's recommended to use either this option or the displayed product description feature described above, but not both.
CATEGORY SCREENS:
Category Name Tags:
Allows you to set the category names on the category screen, to a preferred heading tag, bold, or none (
,
,
,
, ).
The keywords to focus on for an individual category page are typically contained within the category name. Making the category name a larger font size using the heading tags, compared to most of the other page content, adds extra weight to those keywords when rankings are determined.
Remove Store Name In Category Title Bar:
Optionally strips out the store name in the category screen title bars.
Page titles are extremely important to search engines. Miva Merchant adds the store name in the browser window's title bar along with the category name. This is a good thing, but it may also make it undesireable by diluting the category name keywords with an unnecessary store name, thus giving less weight to your keyword focus.
Product Links in Line-Item Listings:
Optionally replaces the product name with a linked product name, when a line-tem listing is used. This is mainly for category screens, but also applies to related products, search results, and product list screens.
Search Engines add additional keyword weight to pages using those keywords contained in incoming anchor text (links) from other pages.
Product Short Description in Line-Item Listings:
Optionally adds a short product description under the product name when a line-item listing is used. Mostly used for category screens, but also applies to related products, search results, and product list screens when line-item formatting is used. Choices are:
None
Product Description (First 200 characters with stripped out HTML code)
Product Short Description (Displays from the OpenUI Short Description Field)
Particularly helpful with non-descriptive category screens or related product areas, by adding more useful content for search engines to index. Also useful for adding varied keyphrases by use of the product's Short Description field.
The OpenUI SuperMod provides you with advanced display and formatting capabilities for any Miva Merchant store using OpenUI. By inserting Virtual Modules into the OpenUI SuperMod and using templates and tokens throughout the store, you can control the look and feel of Miva Merchant in a whole new way. The OpenUI SuperMod allows you to harness the power and flexibility of OpenUI!
Key Benefits Include:
New Directly edit and modify the templates that control the screen output of your store! All of the templates can be fully customized to your needs, and are fully compatible with any OpenUI Token-enabled modules.
New Create New Screens for your store using Templates! Create forms and surveys, have the contents of the form emailed to you after submission!
Page Template capabilities without module conflicts
Nearly unlimited possibilities for store layout enhancements
Create OpenUI Virtual Modules with a few mouse clicks instead of paying a programmer to develop a fully custom module
Display any text, HTML or variable at any OpenUI Hook Point
Dozens of free plug-in Virtual Modules can be downloaded from the Copernicus Website
All Virtual Modules are supported on both uncompiled and compiled Miva Merchant
Simple GUI based Virtual Module development interface, allows:
Value Assignments
Variable-value Assignments
Text/HTML screen output
Variable screen output
Tokenized screen output
Conditional execution
Simple arithmetic assignments
OpenUI Return-hook overrides for selectively hiding or displaying screen sections
NEW! DynamicTemplates Scripting Engine
NEW! Direct SQL Queries for OpenDBv2/MvSQL-QUERY
Templates are available for the following screens!
Standard Shopping Screens:
SFNT/LOGN/ACNT/SRCH/PLST/BASK: Store front screen, login screen, customer account screen, store search screen, product list screen, basket contents screen
CTGY: Category screen(s)
Generic store wide category screen template
Category specific screen templates
Category screen templates applied to categories with similar category codes
PROD: Product screen(s)
Generic store wide product screen template
Product specific screen template
Product screen templates applied to products with similar product codes
Standard Checkout Screens
OINF: Order Information screen
OSEL: Order Shipping and Payment Selection Screen
OPAY: Order Payment Information
INVC: Invoice Screen
Free Virtual Modules:
Add Contact Us Button
Body Tag Insert
Change All Prices To "FREE"
Change CTGY Next/Prev Table Width
Change 'Login' to 'Sign In'
Custom Shipping Messages
Head Tag Insert
Hide All Prices
Hide Create New Account
Hide Order w/out Account
Move Continue Button (to center)
Move Continue Button (to left)
No Category Tree
No Weight
Prohibit Shoppers from Altering the Quantity in the Basket
Remove BASE HREF tag
Remove PROD Screen Links
Remove Product Code Links in Basket
Store Front URL
Remove Global Header from Invoice Screens
Remove Other State / Province from Address Screens
Third-party module compatible
Product Page Templates
NEW! No Purchase Links if Zero Price
NEW! No Weight if Zero
NEW! Third-party module compatible
NEW! Best Sellers Display Template
NEW! Category Path?Breadcrumbs Template
NEW! Category Storefront Template
NEW! Mini-Basket Template
NEW! Expanded Category Tree
OpenUI Token Support: The OpenUI SuperMod supports OpenUI and third-party tokens through the OpenUI provided token functions. OpenUI token
support is available in:
Uncompiled: OpenUI v4.56+
Compiled: OpenUI v4.74+
NEW! Copernicus Template Library: The Copernicus Template Library includes over 15 special purpose tokens for OpenUI, and is include FREE with the OpenUI SuperMod!
NEW! OpenUI Enumerator Included! The OpenUI Enumerator is now included FREE with the OpenUI SuperMod!
Third-party Module Compatible Templates: The OpenUI SuperMod allows you to include template files anywhere in your Miva Merchant store, optionally not skipping any other output or hook points. Thus, you can include a template on any screen without compromising existing module compatibility.
NEW! DynamicTemplates Engine:
Now featuring the very first ever lightweight template scripting engine for OpenUI and Miva Merchant(tm), DynamicTemplates allow you to create scripted templates! Includes control structures, variable assignments and conditional displays!
NEW! Direct SQL Queries for OpenDBv2 & MvSQL-QUERY:
Users of OpenDBv2 now have direct SQL query capabilities for Miva Merchant! Never before avialable, this feature is a must for advanced display capabilities using OpenUI and OpenDB!
Product Capabilities:
The OpenUI SuperMod can be used for most display
modifications and tweaks, even those that are conditional. With the advent of OpenUI Expression evaluation, almost any Miva Merchant API function can be called from within a template or a VMod. This provides the ultimate in display and execution control within your Miva Merchant store.
*Note: While many API functions are available, general database creation and writing routines are not provided by the OpenUI SuperMod or OpenUI
unless you are using MvSQL-QUERY and OpenDBv2 Therefore custom programming that requires new databases is not possible.
Miva Merchant: v4.00 - v4.13 OpenUI Required: Any Version Miva Merchant: v4.14+ OpenUI Required: Any Version, latest version requierd for token and API function calls.
Please note: The OpenUI Enumerator is included free of charge with this distribution.
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.
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.
Take master control of your Product Attributes. This module is packed with features like menu-driven control of MIVA Merchant product attributes. You can control field attributes, prompt/image locations and options, multi-column radio attribute options, and much more. Module features are configurable using the menu-driven admin interface, Product Display Layout, Missing Attributes PATR Page, OUS1 Checkout: Upsell Product (Single) Page and UATR Upsell: Missing Product Attributes (Single) Page templates. These templates are automatically created using your current template versions, when the module is initially installed. Attributes can also be displayed on other product related pages. This gives you master control over the look and feel of your product attributes.
The ADS Attribute Master Module Features:
Simple Module Installation and Configuration
Automatic installation and assignment of PROD, PATR, OUS1 and UATR pages with required item.
Automatic installation and assignment of revised Product Display Layout, Missing Product Attributes, Checkout: Upsell Product (Single) and Upsell: Missing Product Attributes (Single) templates. Current version history templates are used to generate revised templates. Previous template versions will be available through version history.
Menu-driven control of new features. No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
Radio Button Control Features:
Extra Tag Attributes
Attribute Image/Prompt Location
Attribute Image/Prompt Style Wrapper using provided token
Options Image/Label Location
Option Image/Label Style Wrapper using provided tokens
Display Option Price Adder when applicable
Table/Style Attributes
Number of Option Columns
Drop-Down List Control Features
Adds <Select One> at the top of the list
Extra Tag Attributes
Image/Prompt Location
Display Option Price Adder when applicable
Image/Prompt Style Wrapper using provided token
Checkbox Control Features
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided tokens
Display Attribute Price Adder when applicable
Text Field Control Features
Size Attribute
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided token
Display Attribute Price Adder when applicable
Text Area Field Control Features
Cols Attribute
Rows Attribute
Extra Tag Attributes
Image/Prompt Location
Image/Prompt Style Wrapper using provided token
Display Attribute Price Adder when applicable
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with Item "ads-attrmaster", Product Display Layout, Missing Attributes PATR Page, OUS1 Checkout: Upsell Product (Single) Page and UATR Upsell: Missing Product Attributes (Single) Page templates that are pre-installed and configuredwith this module.
Original templates and/or Merchant "Original" templates will not be modified by this module and can be restored, using the new Version history features, at any time.
No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
Hide Prices Pending Customer Approval module Tremendously useful for wholesalers and other store owners who want to limit access to a known, and approved, customer base. Product prices can be hidden until a customer's account has been approved by the store's owner. Access to the site can also be restricted, requiring customers to login. Includes an administrative utility for review & approval of customer accounts and assigning of price & availability groups. Fully compatible with OpenUI OpenTokens and third-party template-based modules.
Professional Version Features:
Price & Availability Groups support integrated into utility module - easily select a price & availability group while approving a customer
Require Customers to login - customers can be required to login (or create an account) before being granted access to anywhere in the store or to the product-related pages
OpenUI OpenTokens fully supported
Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Display Attribute-Option prices on Product Display screen
Plus all the features of the Standard Version
Summary of of Standard Version Features:
Multiple modes for hiding prices - prices can be hidden until a account approved or until a customer creates/logs-in to an account.
"Add To Cart" and the "Buy One Now" buttons are also hidden.
Prices & buttons hidden on the Product List, Categories, Search Results, and Product Display screens
Optional, fully-customizable message can be displayed in place of the hidden prices, on the customer accounts screen & on all screens for accounts that are pending approval
Two modules in one - includes a feature-rich administrative utility module for approving and managing customers
"Quick approval" feature for approving new customer accounts
Compatible with compiled Miva Merchant version 4.14 thru 4.2.
OpenUI OpenTokens OpenUI OpenTokens are fully supported.
Template-Based Modules Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Requires OpenUI.
Details
The "Hide Prices Pending Customer Approval" module contains a wealth of functionality and customizable options. It's tremendously useful for wholesalers and other store owners that want to limit access to a known, and approved, customer base.
Product Prices Hidden Product prices can be hidden until a customer's account has been approved by the store's owner. Optionally, prices can be hidden until a customer creates or logs-in to an account (without requiring approval of the account).
Buttons Too The product prices - and the "Add To Cart" and the "Buy One Now" buttons - can be hidden on the Product List, Categories, Search Results, and Product Display screens. An optional, fully-customizable message can be displayed in place of the hidden prices.
Require Customer Login Customers can be required to login (or create a new account) before being granted access to the entire store or to the product-related pages (Product Listing, Categories, Search, Product Display & Basket screens).
For instance - The module can be configured to "Hide Prices Pending Approval of Customer Account" and to "Require Login to View Products".
With this configuration:
Customers could access the storefront but would be prevented from accessing the Product Listing, Categories, Search, Product Display & Basket screens. They could of course also access the Login & Create New Accounts screens.
Once the customer logged in or created a new account, they would then be able to view the Product Listing, Categories, Search & Product Display screens, but the prices would be hidden.
Once the account was approved by the store's administrator, the customer would be able to login and view product prices.
Multiple Levels of Price Display & Access Restriction
Display of Prices:
Hide Prices Pending Approval of Customer Account
Hide Price Unless Customer Has Account
Show Prices - (Disables Module)
Access to Store:
No Login Required to Access Store
Login Required at Storefront
Login Required to View Products
Customer Messages An optional & customizable "Customer Account Pending Approval" message can be displayed just below the Miva Merchant header. An optional & customizable message can also be displayed on the Customer Account & Customer Information screens. This can be used to inform the customer of the store's policy for accessing the product prices.
For example: "Approval of customer account is required. Please complete the customer account form. You will be notified by email when your account is approved."
Two Modules In One It's actually two modules - a OpenUI system module and an administrative utility Module. The system module customizes the store's look and feel and limits access to prices. The administrative utility module provides the store owner with the ability of reviewing and approving customer accounts.
It's also a feature-rich, admin-friendly customer management utility.
Choose the way you approve customer accounts - accounts can now be approved using either the standard Customer admin or the administrative utility module.
Quick Approval of Customer Accounts The Approve Customers administrative utility module also has a "quick approval" feature. A store's administrator can quickly search for a new customer by login, email address, or other keyword - then approve the customer with one click.
Admin-Friendly navigation - Sort Customers by newest, by id, or by login. Search by login, name or other keyword. Easily scroll through customer records, choose how many are displayed per page, go to first or last record, approve, edit or delete records.
Integrated Price & Availability Groups Support The store administrator can also assign customers to a price and/or availability group at the same time that accounts are being approved.
Template-based Merchant Notification of New Accounts An optional email notification can be sent to a specified address whenever a new account is created by a customer. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Template-based Customer Notification of Approved Accounts An optional email notification can be sent to the customer whenever their account is approved. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Display Attribute-Option Prices Attribute & option prices on the product display screen.
Fully customizable attribute-option prompt template gives you complete control over their display
Works with all types of attributes, drop-down menus, radio button, checkboxes, text fields & memo fields
Modifies both the Product Display & Missing Attributes screens
Completely compatible with Miva Merchant price groups
Give your customers an alternative way of reaching you while keeping your email address safe from the email harvesters. The information you get from the customers is validated and organized in an email which is automatically sent. This module automatically installs and configures a default Contact Page which can be further customized to meet your needs. You can create an unlimited number of contact pages, each specific to your requirements. The module is capable of sending both TEXT and HTML emails and comes pre installed with an Email template for each. You can use template Headers/Footers to provide additional content information for your contact page(s) or edit the page and email templates to suit your needs.
The ADS Contact Form Pro Module Features:
Possible Contact Form Uses
Questions about products and services. Automatically populate the subject line or other fields with Category, Product or other information.
Customer Requests for information, literature, specifications, etc...
Request Contact Information for dealer opportunities, wholesale accounts, etc...
Create Customer Surveys with emailed responses.
Many other information gatherings uses.
Simple Module Installation, Configuration and Controls
Automatic installation and assignment of a new Contact Page template, TEXT and HTML Email templates, and the required item.
Easily create additional Contact Pages, specific to your requirements.
Control which email address the contact email is sent from and to.
Validate Customer provided information by requiring information for certain fields.
Customize the Email sent by organizing how the information appears in the email.
Insert the links to your new contact pages anywhere by using MIVA Merchant navigation bar, category tree, static pages, etc...
Menu and Template based control of new features. No template editing required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
Sample snap shot of a Contact Page:
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with a New Contact Page and Templates that are pre-installed with this module.
No template editing is required, but is available for advanced users. HTML and template scripting knowledge is required to make template modifications. If you do not have these skills it is recommended you contact ADS representative to get assistance with template design and customization.
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.
Take master control of your Category(CTGY) Page. This module is packed with features like menu-driven global and individual category level control of Category Product List Layout, Multi-Column Category Product layout with image positioning, Category Product Pagination with Totals, Subcategory Listing, and Category Breadcrumbs. No need for separate modules to control your category screen globally or individually for each category. All display options are configurable using the menu-driven admin interface, CTGY page templates and Product List Layout templates that are automatically installed and configured with this module. This gives you full control over the look and feel of your category screen.
The ADS Category Master Features:
Simple Module Installation and Configuration
Automatic installation and assignment of CTGY page required item.
Automatic installation and assignment of new CTGY page template. Previous template versions will be available through version history.
Automatic installation and assignment of new Category Product List Layout template. Previous template versions will be available through version history.
Menu-driven control of new features. No template editing required, but is available for advanced users.
Global and Individual Category Control of Category Product List Layout
Merchant basic Category Product Layout Control
Category Title Display option
Number of Columns for Product Display in expanded view
Image Positioning and Spacing
Additional layout modifications can be made using CTGY Page and Category Product List Layout templates that are pre-installed with this module
Global and Individual Category Control of Category Paging
Gives your customers the ability to move within the category using page numbers and/or previous next buttons
Display Total Product Count for selected category
Menu-driven control of pagination menu, no Template editing necessary
Additional layout modifications can be made using CTGY Page and Category Product List Layout templates that are pre-installed with this module
Global and Individual Category Control of Subcategory Listing
Display a Subcategory Listing for selected category for easy navigation
Menu-driven control for:
Page position for Subcategory Listing
Subcategory title header and footer
Display number of products for each subcategory
Number of columns in subcategory table
Subcategory footer
Additional layout modifications can be made using CTGY Page and Category Product List Layout templates that are pre-installed with this module
Global and Individual Category Control of Category Breadcrumb Navigation
Display Breadcrumb style navigation for current category
Menu-driven control for:
Page position for Breadcrumb Navigation
Home URL location and label
Breadcrumb separator
Selected and Unselected breadcrumb formatting
Additional layout modifications can be made using CTGY Page and Category Product List Layout templates that are pre-installed with this module
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with CTGY Page and Category Product List Layout templates that are pre-installed with this module. These settings will override the Merchant default settings.
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.
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. 
