Miva Merchant Modules and Applications Search

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

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

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

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

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

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

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

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

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

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

From: Customer Management Support Modules
Relevance: 31.03%%

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

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

8 QwkPatch 4TheBest.Net / Miva Central

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

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

Current QwkPatch Release: 2.00

Miva Merchant Compatibility: 2.22 - 4.22

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

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

QwkPatch 2.00 Patch List

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

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

From: Store Features Modules
Relevance: 28.74%%

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

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

9 Addendum v5 Emporium Plus / Miva Central

The admin interface allows you to build the form withyour store's questions using standard html syntax. Hence,you can make the response collection table match the restof your store's look and feel. You can have text, radio, select drop down list, text area, and checkbox inputs designed the way you want them. Add css if you like or use typical fonts and table tags.

You can place the questions on one of the three checkout screens. You simply add the tokens to the page templates per the install doc.

You can also specify one or moreof the questions to be required. Customers will not be able to completethe checkout if they do not respond to the required questions.

You can purge old questions from the active file and place them in ahistorical file in order to improve response time during order batchprocessing retrieval. The optional order batch retrieval uses the modified core batch report which is included in the zip distribution file.

You can limit the display of Addendumquestions based on specific product codes. If you list productcodes in the admin input, the questions will only be displayedif one of those products is in the basket at checkout. Youcan also use the wild card product code like 1AA*. If theapplicable products all begin with the same characters, youcan use the asterisk. This can only be used for the beginningcharacters in the product codes.

You can alsolimit the display of questions to specific ship to countries.

You can optionally includethe questions in the emails along with the responses by using the modified email modules which are included in the zip distribution file.If using our Mail Manager (sold separately) module you can have a question (checkbox) which will trigger a specific email, e.g. opt-in mailinglist signup. You can also include the questions and responseson the invoice (last page after payment completes). Theresponses for the batch report are retrieved from an indexeddatabase for faster access.

You can alsoattach a fee to a specific answer to one question if youplace the questions on either the customer information orshipping/payment selection screens.

The included Addendum View report featureallows you to search (within admin) the addendum filefor specific responses. For example, you might have a questionfor a specific requested shipping date. Simply search the filefor orders which have requested the delayed shipping for thatdate. The order numbers can be returned and fed into our EZ Batchreport (sold separately) for a tailored report for a specific shipping date. Another popular use of Addendum is to collect the salesman or representativecode with an order. Not only can you display the code in the batch report,but if you use Addendum View to create a list of orders attributed to thatsalesman, you can make a batch printout for each salesmanwith only their orders on it if you are using our EZ Batch Report (sold separately). You can also include the Addendum responses in the order export file that EZ Batch creates.

Limitation: When used in a store which uses PayFlowlink, PayPal or iTransact payment systems, you will need to placeyour questions on either the customer information screenor the shipping and payment selection screen. Thosepayment systems transport the customer to another domain.Hence, the module needs to save the responses to a filebefore the customer is transported off-site. When thecustomer returns from the off-site payment screens backto your store, the responses will be retrieved for savingto flat file or display in your merchant notification email.

The included modified merchant email and batch reports will display the Addendum resposes. Additionally, the batch report can provide page breaks between each order for better printouts (incoices). Also, the merchant notification email allows you to insert tokens in the subject line so you can include things like the order number, order total, and customer name in the subject of the email.

Compare this module with our competitors' pro or advanced or ultimate versions. Those are just words tacked onto a module name. Don't let our low price fool you - compare features and you will find this module probably contains all of the features found in theirs plus we have several additional features. The Addendum module has been in use since Merchant version 1.x and continually enhanced with each version. Our competitors will try to keep up, but the simple choice is, why get a shadow when you can get the "original".

The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server. This would be the case in most of the server setups. For those that are not, we are in the process of converting the code for that remaining, very small group of MIVA Merchant stores. At this time we have not had a problem. Modules will be moved to the top of the queue as needed.

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

From: Addendum Additional Info Modules
Relevance: 27.97%%

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

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

10 Add Product Redirect to Basket netBlazon / Miva Central

Add Product Redirect to Basket causes the user to automatically be taken to the Basket Contents screen after clicking the "Add to Basket" button. (Standard Miva functionality is such that the user remains on the same screen.)

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

From: Shopping Basket Screen Modules
Relevance: 27.20%%

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

Bookmark Add Product Redirect to Basket <-- Just click this link and then add to your favorites!

11 Display Wizard Pro Luray / Miva Central

Display Wizard Pro contains all the features of the acclaimed Display Wizard OpenUI module, PLUS:

NAVIGATION BAR CONTROL

• Remove any Button in the Navigation Bar.
• Move Checkout Button to the Left next to Basket Button.
• Align Navigation Bar Buttons, left, right or Center.
• Control Navigation Bar Color and Cellpadding.
• Add additional row of Navigation Bar Buttons.
• Place additional row above or below Navigation Bar.
• Align Additional Row Buttons, left, right or Center.
• Control Additional Row Color and Cellpadding.

• Add Additional Left Column.
• Display Category Tree on any or all Screens.
• Keep Category Tree Expanded on Product Display.
• Independent Category Tree Font and/or CSS Font Control.
• Add Bullets, Arrows or other Image to CatTree Text Link.
• Add additional row of Footer buttons.
• Align Footer Buttons, left, right or Center.
• Control Footer Button row Color and Cellpadding.
• Display Category Tree on Any or All Screens.
• Display Right Column on Any or All Screens.
• Display Customer and/or Affiliate Login Right Column.
• Display Mini Basket at top or bottom of Right Column. (requires mini basket to be installed separately)
• Add Category Dependent HTML for Perpetual Header, Left Column, Right Column, Perpetual Body Header, and Perpetual Footer. Set Themes or specific information for each Category

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

From: Store Look and Feel Modules
Relevance: 27.20%%

Rating: (10.00) Votes: (1) Hits: (2447) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Display Wizard Pro <-- Just click this link and then add to your favorites!

12 Wish List Manager Viking Coders / Miva Central

This module provides your customers with the opportunity to add products to a Wish List. This permits them to later return to your store to view, add, and edit the list. They can send email to their friends prompting them to visit your store and view their wish list. Other customers can search the wish lists for the lists of their friends, hopefully with the intent of buying something for them, and send email to others to recommend that they visit your store and start a list.

The admin interface provides the merchant with the ability to view the current customers with wish lists (searchable by wish list contents and customer data) and to view the contents of each list. The entire wish list can be deleted from within admin as can individual products in the list.

If a product being added to a wish list has attributes, the customer will be prompted to select the attributes (but not required to) before the product is added to the list. If the customer is not logged in when they attempt to add the product to their list, they will first be prompted to log in and will have the opportunity to create a new account.

The module adds new Merchant pages on which the customer can view their your own wish list and search for the wish lists of others. Links to both of these pages can be provided in up to 13 different positions in the navbar and in the category tree. The link by which the customer adds the product to their wish list can appear on up to 11 different positions on the product display page. The link text and/or image used for each of these links is separately configurable.

When a customer searches for wish lists, the wish list "owner's" first name, last name, email address, login, city, state, and zip code are all searched.

The merchant has the option of making the wish list "opt-in only" by providing the customer with a checkbox on the customer account page to enable a wish list (the text of the prompt is configurable). If a customer chooses not to opt-in to the wish list, they will be able to add/edit/view their own list but it will not appear in searches by other customers. They can still email their friends and provide them with a link to their wish list.

An expiration period can be set for the wish lists. If no activity takes place in a configurable time period (ie. no products are added) the lists can be purged from within admin.

The format of all of the pages is completely configurable with tokens. The customer can be permitted to edit the quantity of the items in their wish list, add a note, and delete individual items. The format of the page on which the customer views their own wish list and on which they view the wish list of others are separately configured to provide the customer with the additional ability to edit their list.

From the page on which the customer view their own wish list, they can send an email to their friends to let them know about their list. From the page on which the customer searches for the wish list of others, they can send an email to invite their friends to start a list. The content of both of these emails is completely configurable from within admin and use tokens to represent store and customer data.

The header, footer, background image, title, and background color of each new page added by the module are separately configurable from the module's administration interface.

Versions 2.x, 3.x Available!

Price: $80 Upgrade Cost: $48 Upgrade Terms (If Any): Upgrade Pre-Sept 15 $48 Post $0
Compatibility: OpenUI Versions: 2.x, 3.x, 4.x, 4.14-4.24x (Available Compiled)
Other Module Compatibility: N/A

From: Gift Wish Favorites List Modules
Relevance: 25.67%%

Rating: (8.00) Votes: (2) Hits: (2268) Reviews:
Rate It - Review It - Modify It - Report It

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

13 Static Catalog Generator Weiland / Emporium Plus

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.

Example static catalog pages

• Sort by name
  • This example has the add to basket button disabled
  • This example contains StatCat generated individual product pages
• Sort by category
  • 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 Froogle^TM. It contains the header and data for the basic file format.

Price: $35 Upgrade Cost: $10 Upgrade Terms (If Any): Upgrade Now
Compatibility: MMUI/OpenUI Versions: 2.x, 3.x, 4.x, 4.14-4.16x (Available Compiled)
Other Module Compatibility: N/A

From: Search Engine Optimization Modules
Relevance: 25.67%%

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

Bookmark Static Catalog Generator <-- Just click this link and then add to your favorites!

14 Add External Products CrosstownTraffic.Net /

Uses MMUI for main functionality.
Need to take orders with custom configurable products? This is an extremely useful module that will help you acomplish it! Add external product ordering to your store. Simply install this module to allow adding external items to your baskets. Add a dummy product, and use the link system provided with install, or use a form to send the data to the store.

Admin Screen Shot
This module allows you to create products in the store that are not easily definable in Miva Merchant - such as auction items, or Dynamic Items (when the customer needs to enter his price.) The items Name, Product Code, Weight, and Price are all customizable. A set of Attributes can be used to Define particular attributes such as Size, Color, and Pattern/Style. More options upon customization.

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

From: Store Features Modules
Relevance: 24.90%%

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

Bookmark Add External Products <-- Just click this link and then add to your favorites!

15 Upload File Attribute Copernicus / Miva Central

The Upload File Attribute module allows you to collect file attachments from your customers. With this module, you can add an upload file attribute to individual products so the product can accept attachments from the customer. Your customers can then add attachments to their order when they select that product for purchase, and the store administrator can easily access the attachment in the Miva admin.

Key Benefits

• Allow your customers to add attachments to products in their order
  • Customers can add multiple attachments to the same product in the order
• Store Administrator controls the file type and file size permitted for upload
• Store Administrator can easily access the attached files through the Miva admin

• OpenUI: v4.9*
• Customized MMUI**

• MMUI+DynamicTemplates: 4.53
• OpenUI: v4.9+

Price: $149.95 Upgrade Cost: $74.95 Upgrade Terms (If Any): N/A
Compatibility: MMUI/OpenUI Versions: 4.x, 4.14-4.23x (Available Compiled All 4.x Versions)
Other Module Compatibility: N/A

From: Attributes Modules
Relevance: 24.14%%

Rating: (10.00) Votes: (1) Hits: (1387) Reviews:
Rate It - Review It - Modify It - Report It

Bookmark Upload File Attribute <-- Just click this link and then add to your favorites!

16 NetPush Advanced Inventory NetPush / MvCool

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)

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

From: