Found 211 Modules or Applications that might fit the bill
Use caution when considering any modules from modStop. Their support has been reported by umpteen Miva Merchant users as suspect and worse. Some of their modules are simple and shouldn't require support. Please contact us with any questions concerning them or their modules.
Display all open baskets in a table format. This report includes active and expired baskets. As a MIVA Merchant store owner you are able to see how many people come to your store and abandon baskets, even after placing items in thebasket. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
In some cases, customers get to checkout and then abandon baskets and you can determine that too. You can use the module to check basket activity before closing the store for maintenance or deleting baskets in admin. As basketsare converted to orders, they disappear from this listing. Likewise, when expired baskets are deleted in Admin, they also disappear from this listing.
Basket ID - Number assigned when a customer visits your store
Order No. - Incremented number (or retrieved from unused numbers) each time a customer enters their customer information at checkout
Customer - Account info (if available) - Login, Ship To Name, Bill To Name (if different), Ship To Email, Bill To Email (if different)
Product - Product codes in the basket at this time (may be empty or contain one or more)
Expired - "Yes" indicates the basket was last refreshed more than the number of minutes for your basket timeout setting. A number indicates the number of minutes since last activity and the basket is not timed out.
You can delete specific baskets. This feature was requested by a store owner who found his competition was purposely putting large quantities of items in the basket so they would be out of stock. By using this feature he was able to delete the basket and the items were immediately put back in inventory.
The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server. This would be the case in most of the server setups. For those that are not, we are in the process of converting the code for that remaining, very small group of MIVA Merchant stores. At this time we have not had a problem. Modules will be moved to the top of the queue as needed.
Display all open baskets in a table format. This report includes active and expired baskets. As a store owner you are able to see how many people come to your store and abandon baskets, even after placing items in the basket. In some cases, customers get to checkout and then abandon baskets and you can determine that too. You can use it to check basket activity before closing the store for maintenance or deleting baskets in admin. As baskets are converted to orders, they disappear from this listing. Likewise, when expired baskets are deleted in Admin, they also disappear from this listing.
Basket ID - Number assigned when a customer visits your store
Order No. - Incremented number (or retrieved from unused numbers) each time a customer enters their customer information at checkout
Customer - Account info (if available) - Login, Ship To Name, Bill To Name (if different), Ship To Email, Bill To Email (if different)
Product - Product codes in the basket at this time (may be empty or contain one or more)
Expired - "Yes" indicates the basket was last refreshed more than the number of minutes for your basket timeout setting. A number indicates the number of minutes since last activity and the basket is not timed out.
Automatically delete expired baskets and restock the inventory with the products that were sequestered in those expired baskets. Emails with Sale Saver feature can notify store owner with summary restocking results and identify customer and product info in abandoned baskets. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
The Miva Corp inventory management module for Miva Merchant 5.x has resulted in numerous stores having their shelves temporarily cleared. As customers place products in their baskets, the store inventory level is decremented. If the customer decides not to buy at that time and leaves the store, the products in that abandoned basket remain unavailable. When the store owner manually deletes expired baskets in admin, those basket contents are reclaimed and the products are placed back in the store inventory. Stores which have one-of-a-kind or low inventory levels of products are significantly impacted as the products are not available for purchase by other customers until the store is manually restocked. Stores which have high traffic are similarly impacted when many baskets are abandoned. This module eliminates the need for the store owner to manually restock. At a frequency determined by the store owner, this module will reclaim the expired baskets and restock the shelves. When customers visit your store the timer will be checked to determine the last time expired baskets were deleted. If deletion is due, the next customer who clicks to a Miva Merchant PRODUCT screen will launch the shelf restocking routine.
The module includes an activity log. It accumulates the numbers of baskets which were not converted to orders and have been reclaimed. It also captures the completed order totals. These numbers can be displayed for any time period. The information can be useful when evaluatingyour success at convincing "visitors" to actually buy something.
Another useful usage of this tool is monitoring how often and to what extentsearch engines spider your merchant.mvc pages. You will periodically see a glut of abandoned baskets when the restock module runs.
You also have the option of the module sending an email to you each time it restocks the shelves. This is useful in identifying problemswith your payment gateway as it identifies baskets which were reclaimed, yet had products in them. This is to be expected within reason, but if you see a significant increase, it may be because your payment gateway is down.
Included in the email is the Sale Saver feature which displays basket info when the customer info has been filled in AND there are products in the basket. So if the order was not completed, you can see who it was and what they intended on purchasing. It also tells you how far they got into checkout. If they have both the customer info and products, they are considered to have gotten to the OSEL screen. If they also had selected a shipping method, they got to the OPAY screen. In some cases, they may have even gone to pay but the payment failed to update MIVA Merchant. In this case they would also be considered to have reached the OPAY screen.
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.
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)
Unattended scheduled tasks , including backups and batch exports . Important up-to-date data, number of visitors shopping, order notifications in real-time . Alerts for oversized files, broken databases , corrupted data, lost orders and emails. Automated cleaning up oversized data and removing temporary files . Statistics . Order history . Bestsellers . Instant shutting down the store, deleting baskets, packing. Instant access to MM Admin.
Displays the number of currently shopping visitors (opened baskets)
Automatically backs up and resets databases and deletes data files that grow over assigned file size quota - significant performance boost!
Automatically deletes temporary files from interrupted packing (i.e. products.dbt00000001)
Automatically deletes temporary upload files
Scheduled ábackups, Batch Exports, etc. (see below in SCHEDULED TASKS)
CHARTS Hourly, daily, weekly, monthly and yearly charts including historical data (unlimited) in following modes. The length of the displayed period is configurable, browsing in the history is of course possible.
Abandoned baskets
Failed payments
Total revenue (sold value)
Total number of orders
Total number of sold products
Total collected tax value
Total collected shipment charges
Number of failed e-mail notifications
STATISTICS Beside the data displayed in the charts and in the mouse-over popup windows over the charts, there are the following data available. The displayed values depend on the selected time mode - it shows either totals over the last hour, day, week, month, or year.
Number of new orders (unbatched orders)
Total number of orders in the given period
Total revenue in the given period
Total number of sold products in the given period
Total value of collected tax in the given period
Total value of collected shipping charges in the given period
Number of abandoned baskets in the given period
Number of failed payments in the given period
Number of failed e-mail notifications in the given period (with MmHTML, MmHTMLc or MmVENDOR)
Number of hits since the last reset (in MM Admin)
Number of visits since the last reset
Total revenue since the last reset
Total number of sold products since the last reset
List of bestsellers. It can contain limited number of bestesellers or list of all products sorted by number of sales. Values since the last reset in MM Admin.
INSTANT ACCESS To MM ADMIN Functions From the MmTICKER window you can access the following often used MM Admin functions with a single click on a button:
Instant access to the standard MM Admin without the necessity to log in
Shutting down the store to the maintenance mode and re-opening it again
Deleting baskets (all or expired only)
Packing store and domain data
Instant access to the batch report of new arrived orders (click on the new order announcement). Works with both Ultra Batch and the built-in MM batch report.
ALERTS AND EMAIL ALERTS MmTICKER watches your store and associated files and in addition to displaying an alert message on the screen it also sends e-mail alert to the store owner. Email alerts work even without the MmTICKER window opened!
File Quotas: MmTICKER warns if pre-defined files grow over the limit assigned to them. Works also with files 3rd party modules!
Database Consistency: MmTICKER verifies all pre-defined databases if they are not corrupted and do not contain duplicate records. Works also with databases 3rd party modules!
Alerts on failed schedule tasks or optionally email reporting of successfully finished scheduled tasks, too.
MmTICKER alerts when the number of failed payments in a day is bigger the given limit (possibly signilizes problems with the payment gateway or fraud attempts)
SCHEDULED TASKS You can set up inlimited number of scheduled taks to be performed daily, monthly or yearly. The defult pre-defined task schedules at 4:00AM the store for at the maintenance mode 15 minutes later, waits till the store is closed, deletes expired baskets, packs store data, packs domain data and re-opens the store. Scheduler may be configured so that it executes the tasks only if nobody is in the store. Currently, the following commands may be used:
Close - scheduling the store for the maintenance mode after a pre-define time (15 minutes by default)
WaitClose - waits till the store shuts down
DelExpBask - deletes expired baskets to increase the performance and reduce the file sizes
DelAllBask - deletes ALL baskets (even those not yet expired)
PackStore - packing store data to reduce store specific files and to rebuild store database indexes.
PackDomain - packing domain data to reduce common Merchant files and to rebuild mall database indexes.
ExportNew - exports new order to a file and sends the new batch by e-mail to the store owner (with Ultra Batch)
DelCC - for security reasons, deletes payment data (incl. CC numbers) of all processed orders (with Ultra Batch).
backup - creating full backup copy of Miva Merchant Data (Unix full shell servers only. Limited support).
mmubat - calls Ultra Batch module and performs tasks defined in passed arguments (with Ultra Batch, for advanced users only).
admin - calls MM Admin and performs tasks defined in passed arguments (for advanced users only).
shell - calls system commands (Unix full shell servers only. For advanced users only).
other commands for the scheduler may be added on request
MmTicker logs unauthorized access attempts with detailed information about the user - logfile is browsable through the MmTICKER admin screen.
Scheduled tasks are also logged and the records may be viewed in the Admin screen.
Time zone setting and user-defined date and time format
Animated "marquee" alerts, messages and statistics with configurable speed and possibilty to change the speed or stop the scrolling with a single mouseclick.
Parts of the MmTICKER window may be hidden to reduce the size
Flashing taskbar button and window popping up on alerts (optional)
Configurable window size - the size of the window may be set to show charts over longer time period.
Zoom - for those with bright eyes or oppositely with sight problems, the winod may be zoomed from 50% to 200%
Mouse-over help and detailed info on items work overall on the MmTICKER window.
MmTICKER window refresh frequency configurable
Frequency for file size and database consistency check configurable
Automated installation, no manual intervention needed
Scheduled tasks may be triggered from the opened MmTICKER window, from a Unix cron table, from a remote server (i.e. truXoft) or directly from Miva Merchant.
Does not require OpenUI. Works with both OUI and MMUI.
No OUI hook conflicts - truXoft modules are 100% conform to the Miva Merchant API, they do not use OUI extensions and therefore never cause hook conflicts with other modules, otherwise common at OUI modules.
The Miva Corp inventory management system for Merchant 4.0 has resulted in numerous stores having their shelves temporarily cleared. As customers place products in their baskets, the store inventory level is decremented. If the customer decides not to buy at that time and leaves the store, the products in that abandoned basket remain unavailable. When the store owner manually deletes expired baskets in admin, those basket contents are reclaimed and the products are placed back in the store inventory. Stores which have one-of-a-kind or low inventory levels of products are significantly impacted as the products are not available for purchase by other customers until the store is manually restocked. Stores which have high traffic are similarly impacted when many baskets are abandoned. This module eliminates the need for the store owner to manually restock. At a frequency determined by the store owner, this module will reclaim the expired baskets and restock the shelves. This module may not be required in future versions of Miva Merchant as a similar fix has been requested through the Miva Corp wishlist.
This module is for Merchant 4.0 and is compatible with both the MMUI and OpenUI. Editing of mv files is NOT required.
The need for this module readily became apparent after using the Show Baskets module which identified what customers were leaving in abandoned baskets and how frequently they did that.
Compiled: New in the compiled version is an activity log. It accumulates the numbers of baskets which were not converted to orders and have been reclaimed. It also captures the completed order totals. These numbers can be displayed for any time period. See the screen shots below. The information can be useful when evaluating your success at convincing "visitors" to actually buy something. Another useful usage of this tool is monitoring how often and to what extent search engines spider your merchant.mv pages. You will periodically see a glut of abandoned baskets when the restock module runs. You also have the option of the module sending an email to you each time it restocks the shelves. This is useful in identifying problems with your payment gateway as it identifies baskets which were reclaimed, yet had products in them. This is to be expected within reason, but if you see a significant increase, it may be because your payment gateway is down.
Chat with your customers in a live session online. If you have our Show Baskets module (version 4.59 or newer) you can identify and open a chat session for a specific basket. Then with the Talk Back module, the customer can read and respond in that open chat session. Both the Show Baskets and Talk Back modules are required in order to transmit messages from the store admin to the customer in a chat session.
You can use a module token to display a "Chat" button for the customer to hail store staff. When
they click the button an email is sent to your predetermined email address you use to notify staff that there is someone in the store who wants to chat live.
The store staff can open the session by posting a first message. Once the store begins the dialog, an image or text can be displayed on the storefront (using a token) which invites the customer to chat. If they click the invitation, their chat window will popup. The store and customer can then chat live.
The refresh rate is set by the module's configuration, as is the various buttons and text the customer sees.
Limitations: The module depends on the customer using cookies and that the cookie does not change each time the customer clicks on a new screen. The cookie (session ID) needs to remain with the
customer as they shop in your Merchant store anyway or they would not be able to maintain items in their basket. The customer cannot have popups blocked and they must have javascript enabled.
Required companion modules: 1) You must have Show Baskets version 4.59 or newer in order to use this module. 2) OpenUI must be installed in the store.
Display the contents of baskets before and in most cases, after the order is finalized with this MIVA Merchant module. If you are using Merchant 5.x and MySQL, you will not be able to display the contents of completed orders or baskets which have been deleted in this module. With 5.x and MySQL you will be able to see the baskets which did not complete and have not yet been deleted (either by the store admin when deleting baskets or by the customer deleting their own basket). This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Once a customer enters their personal data, an order number is assigned to the basket. During the next few minutes a variety of things can happen, one of which isthe order will be completed without error. On the other hand, an order may not be completed due to server error, communication between the payment processor and your store fails, the customer decides not to purchase, duplicate ID corruption occurs in your orders database, and any number of other perils.
If you have not packed your store databases, you may stillbe able to recover most information from lost orders. This module provides the ship to and bill to customer info. It lists the products and their attributes that were ordered. Itlists the shipping, tax, coupons, discounts and other miscellaneous entries. It also displays the payment moduleand data element (not the CC number) in completed orders (MivaSQL).
With Merchant 5.x (using MivaSQL), the data will remain in this file until you pack thestore databases or the basket number is reclaimed by merchant. The numbermay be reclaimed if the customer re-visits your store aftertheir earlier, abandoned basket had timed out. If they don't re-visit, the number will remain until you pack the store databases. If using 5.x and MySQL, you will still be able to see the data as long as the basket is not deleted and the order had not been completed.
Basket Master bundle contains basket tools for both the store owner and customer. It contains four of our most popular basket related modules for Miva Merchant storefronts.
Features: (some features are only in the compiled version as indicated below) o Mini-basket and Recent Visit History Display - Summarize basket contents on most Merchant screens - List product name or code, quantity, and price - Use image to alert new additions made to basket (compiled) - Display a checkout link when order minimum is reached - Use store's assigned shipping modules to preview shipping options and charges - List recently visited product pages with easy add-to-basket button (compiled) - Optionally use OpenUI token to place the mini-basket in many places on the screen (compiled) - Optionally use OpenUI token to place visit history outside of the mini-basket (compiled) - Owner can monitor live activity of customers visiting product pages through admin (compiled) - Customize mini-basket look in admin (color, size, headings) - Built-in link to view main basket - Optionally hide mini-basket if no products are in it (compiled) o Restock Shelves - Eliminate the need for the store owner to manually delete expired baskets - Automatically reclaim expired baskets and restock the inventory - Activity log shows completed orders and abandoned baskets totals for comparison (compiled) - Activity log for any time period and displayed as text and graphics (compiled) o Show Baskets - Display open baskets (active and expired) in table format o Lost and Found Orders - Display contents of baskets before and after the order is finalized - May aid in the recovery of missing order info
- Licensed per domain - OpenUI or MMUI compatible (OpenUI required in compiled Merchant) - Save 15% by buying these licenses as a bundle
Enhance your shopper experience by providing additional images and information for your store products and categories. This module is packed with features like up to five additional images, for each of your products and categories. Module provides JavaScript functions to handle, image popup windows, mouseover/onclick image swap and slide show options. Each image has an upload feature, an associated width, height, title/description, link and link target fields, controlled through MIVA Merchant admin. Token shortcuts are provided for all of the fields, as well as shortcuts for quick image, image with link, javascript popup, mouseover, onclick image swap and slide show features.
The ADS Image Extra Module Features:
Simple Module Installation and Configuration
Automatic installation and assignment of PROD, CTGY pages with a required item.
Menu-Driven control for Image uploads, width, height, title/description, link and link target fields
Includes JavaScript functions for image popup windows, mouseover/onclick image swap and slide show options.
Built-in Import function to make importing new product fields easy.
List of tokens and token placement suggestions to make installation quick and easy.
Tokens can be used on any product or category associated template screens. This includes individual category and product headers/footers, category and product page headers and footers, category and product pages, etc..
HTML and Merchant 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 Product Page sceenshot with ImageXtra Popup window.
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-imagextra and any Category/Product related templates.
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.
Implement customer product ratings and reviews within Miva Merchant. The 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: - Rate with a numerical/verbal score for each product - Review each product with narrative critique - Customers login prior to rate and review - Configurable message if not logged in - All customers can view ratings/reviews without logging in - Limit customer to one rating/review per product - Customer can edit their prior rating/review of the product if logged in - Ratings are averaged and graphically displayed - Graphics display on product and/or expanded search, category and product list screens - Store owner can replace default heart images with their own - Optional email notification to store when new rating is made - Auto-approve or admin approve before allowing display in the store - Admin reports for easy deletion, analysis, and approval - Admin reports to screen, export to flat file, and optionally email flat file to store - Easily remove malicious customer prank ratings - Easily remove all ratings by a specific customer account login - Easily remove ratings/reviews of a specific product code - List all unapproved ratings/reviews for easy approval of one or more - Summary report for all ratings/reviews on a specific product - Summary report for all ratings/reviews by a specific customer - Admin reports with hot links of the customer logins so you can quickly view rater details - Sort the reviews in the order you want them displayed - Module comes with default layout for both the entry form and display - Easily replace the default layout with customizable template entry form and display - Use render tokens for placement of display and/or prompt in the page template screens - Optionally use tokens in the display template for listing the rater's identity - Allow customer to include identity with their email, name, or location (automatically filled in from their customer account) - Exclude specific product codes from being rated - Integrate with the Emporium Plus Mail Manager module to send a promo email to the ratee, thanking them for the rating - Limit number of reviews on the product page with a "more" link to show all - Licensed by domain without need for multistore license if same domain
Feature Details. The purpose of Rate This module is to allow customers (who have signed in) to provide their rating/review of products offered in the store.The module allows a customer one review on each productthey choose to rate/review. They can go back and change their rating and review as it is controlled by their login and password. The average customer rating is displayed graphically with whole or half images. This graphical display can be on the product screen, the category listscreen or both. The default images are hearts, but the mall owner can substitute any graphics he/she wants. Customers can also leave narrative comments about products they wish to review.
All customers, not just those logged in, are able to view the ratings and reviews made by other customers.
In the event that a malicious customer enters prank ratings, the admin interface allows removal of all ratings by specific customers. Since the module has an email alert feature (if turned onby the store owner), you will know what ratings are being left for your products. There is also a report generator to list all ratings on a specific product code or all ratings by a specific customer.
You can also display and/or delete the ratings of a specific product from the individual product edit screen.
Using a render token, place the Rate This button on the product page so that it better fits your desired look. You canlimit the number of reviews which appear on the product page with a "more"link to show all. You can sort the order of the reviews within the product edit screen so that customers see the reviews in the order you want them seen. You can also require admin approval before the rating/review is displayed to customers visiting your store. Admin reports can be displayed to screen, exported to flat file, and optionally email the flat file to the store. The admin rating reports which display the login have a hot link to the customer login so you can quickly view who the rater is.
Configure through admin, the text and tokens in both the display and prompt for this module as they are customizable templates which can replace the default layouts. You can allow the customer to include their email, name, or location (automatically filled in from their customer account) along with the reviews, depending on the demographicyou choose to allow in the store. As example, a typical rating might be Reviewer: John in Anglikon, Switzerland 05/14/2001 Great tool and simple to install
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.
The Categories in Basket Screen module provides enhanced display of your basket screen with: 1) categories the product is in, 2) thumbnail image of the product, and 3) combined prices of products + attributes into a single price for each product.This module is for MIVA Merchant 5.x.We also have the corresponding module for an older version of Merchant.
This module is licensed to one domain.It may be used in more than one store within the same domain without additional licensee fees.
The tokens are added to the 'bask' and 'invc' page templates to implement the features you want to use in this component module.
You can insert the category name directly below the product name in the Basket (BASK) and Invoice (INVC) screens.When a product is in more than one category, the module displays all of them.Each category name is linked to the corresponding category list screen in the Basket Screen.
In addition to categories in the basket, the module also provides the url for the thumbnail image which can be displayed in the basket.The thumbnail display is not in the built-in basket display so this module provides that extra feature.
Also, the module creates a basket price sum variable which can optionally be displayed in the basket and invoice.This price variable combines the product's basket base price with its attribute prices so that you can show the sum total for the product and hide the individual attribute prices in the basket.If you want to allow customers to see the amounts itemized, you can even make a link to the basket screen and pass a parameter that shows the basket with the product and attribute prices separated by using a conditional display.Creating a sum variable which is different from the original display variable was done to prevent potential conflict with other vendor's 3rd party modules.I could have intercepted the price and changed the variable used for regular price display, but that would likely have led to conflicts as more vendors create modules that effect price display in the basket.So instead, you have both variables and can choose which to display.For those who also want to have combined prices in the merchant and customer emails, you can use the Emporium Plus Mail Manager module which has tokens for this purpose.
Category Template Manager allows merchants to create multiple display templates that can then be assigned to categories. This module is power packed with features like:
The Best Seller Display module interfaces with the internal Miva Merchant 5.0 statistics module to provide your customers with similar best seller information previously only seen by the store owner in the admin interface. It goes a step further by breaking down the best seller information by category. Your customers will not see exact numbers sold, only relative ranking. As they see the best sellers listed, the display provides them with a convenient link to the individual products so that they too can see what all the excitement is about. You can reset the statistics through the existing admin statistics interface so that your best sellers can be kept current as product inventory changes. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Through admin, the store owner can place the token for the display on whichever pages he/she desiires. You can specify the number of best sellers that will display in the box, e.g.top five. The CTGY screen is slightly different from the other screen displays, as it shows the best seller in the category that the customer is viewing at the time. You have the option of excluding specified category screens that you do not want to display the best sellers. You can also vary the color, size and fonts used in the display box. You can even specify that the module will obey the availability group settings. This will limit the linkage if your best sellers are only available to certain customers and those customers have not logged in first. The upside is that it does not show detailed product info for products that are not availableto all customers. If you choose to allow all customers to view all products in the best seller list, the module will ensure that only eligible customers can link to the products.
You can exclude specific products from the display. This is useful if you have products that are special sellers, e.g. upsell products.
The layout optionally allows you to include the thumbnail and price of each best seller item. You can set the height and width for your images, hence you should try to keep all of yourthumbnails at about the same aspect ratio. You can vary the layout at each of the screen type so that some can be vertical while others are horizontal or no display at all. Using the render tokens, you can insert the Best Seller Display just about anywhere and on any screen.
The default display is easily configured in the module's admin screen and will display the best sellers either vertical or horizontal. For those with more experience in using the Miva page templates, you can use the custom render token and make all of the table layout configurable by processing the array that the module creates.
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.
The sorter module gives you the ability to sort your Miva Merchant categories and products very quickly from an easy to use, admin interface. The typical sort time for700+ products is 1-2 seconds. In the latest version of the module, you can also capture the number of products in each category for quick lookup at runtime for use in the category tree or other Merchant pages. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Sort categories by name, code or entry date - Sort products by name, code, price or entry date (ascending or descending) - Sort entire store or sort one category at a time - Sort products within categories by name, code, price or entry date (ascending or descending) - Categories do not all have to be sorted the same way - Move specific products to the top of the product list, search and category pages with a quick mass input - Display an image before the product name for products with a sort order number lower than the trigger number established by the store owner - Count products in each category for later display at runtime to reduce server load and page view time
Feature Details. You can sort the categories by name, code, or entry date. Many stores find that their categories are best sorted by category code rather thancategory name. This way they can create codes which will put their categoriesin the order they want. While most may actually coincide with category namesbeing alphabetical, stores can rearrange the categories to put things like "Specials"or "Close Out" at the top of bottom of the list. The customer does not see the category code, they only see the results of the sorted list.
The products can be sorted by name, code, price, or entry date. The product sorting can be done either as either ascending or descending. Moststores will sort the products by name. The very quick sort is done storewide with a couple button clicks. The storewide sort results in the products being sorted in all of the category screens, the product list screen, and the search screen.
You can sort the products within individual categories differently than the sorting in the store at large. So while the product list and most categories might be sorted alphabetically, you could have others sorted by price as ascending or descending. You can sort theproducts by a specific category and then on the next screen, make minor changes to re-arranged that sorting. This gives you the ability to move certain products to thetop for more customer visibility.
You can also move to the top of the list up to 999 product codes in the orderyou want them. They can appear before any other products on the product list, search and each category screen. This ability to assign a sort order number also makes it possible to display an image, e.g. new or hot, to all products with a sort order number less than the trigger you assign using a token.
You can also elect to count the products in each category. If you do, the counts willbe available at runtime in Merchant. By having the data in a quick lookup table, Merchant does not have to count the products in each category as it displays the category list in a 3rd party module's category tree. It simply shows the previously stored totals. This option cannot be used in stores which use availability groups to hide products fromsome customers because the totals would show the amounts for all products in eachcategory. The sorter module uses a token to display the products-in-category total after the category name if you are using a 3rd party category tree template module.
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.
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.
Export your Miva Merchant product data in the basic file format required for FroogleTM (� 2002 Google) data feed submissions for inclusion in their ecommerce search engine. Fields included: product_url, name, description (html removed), price, image_url, category, offer_id (code). This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Most agree, Google is the mother of all search engines onthe Internet. Their feature to create a listing of actual items for sale across the Internet, rather thanpages with hits on keywords, is a bold attempt to better target customers and buyers in a symbiotic relationship. This is a giant leap in eCommerce, providing comparison shopping using the Google search engine. If you are a MivaMerchant store owner you CANNOT afford to miss this opportunity, especially since inclusion in the FroogleTMindex is free. How much have youinvested in getting your store's search engine rankings?
A big side benefit to getting listed in FroogleTM is that the Google company is spidering your site, thus it may increase the number of your pages listed in Google. Coincidentally, my site went from 1220 to 1350 pages in Google within a week after submitting the first data feed to FroogleTM. I had an additional 130 which had been previously overlooked. There is no direct indication that listing in Froogle will effect your listing in Google, only time will tell.
A module designed for the specific purpose of creatinga data feed for FroogleTM (rather than a generic data export)can include features which make it the best solution for the task:
Include an affiliate code in the URLs so that youcan better track where actual sales are coming from
If your store is a single store in the domain, you can remove the Store_Code from the URL to aid in search engine spidering
Fast Data Feed plugin module creates the datafeed flat file directly from your admin
Frequent, no hassle submissions keep your data currentin FroogleTM
Eliminates the need to copy product and category databases from the server to your PC to produce a flat file export with software such as MS Excel
Uses your data as it exists within admin at the moment it is run
Control over category insertion
Limit export to specific categories
Automatically builds the category hierarchy from each product's category up to top level category
Optionally modify category placement, overriding actual category hierarchy
Removes html from your product descriptions; convertingthe brackets to escaped characters or even hiding html using the !-- technique did not satisfy FroogleTM support staff - it must be completely removed
Included in the module are features to eliminate timeouts when generating the data feed export of large numbers of products
Exports to your documents directory rather than yourdata directory for ease of capture and transmittal
Don't delay. The FroogleTM index is a great way to list your products in a major search engine.
Steps
Submit request to FroogleTM for acceptance into the program
Install this module and run it
Once accepted, FTP resulting (username).txt flat file to FroogleTM
Check your pages in FroogleTM when they show up
If you are going to submit to indexes in addition to Froogle, you might want to take a look at our Template Data Feed. It can create data feeds in just about any order the specification requires.
Create your orders batch file based on the date of theorder. You specify the beginning and ending date andname the batch, this module will do the rest. It finds orders which have not already been batched and that fallwithin the date range you specified. Many people fillorders from the merchant notification email and infrequentlylook in the order processing section to review a detailabout the order. Hence, they do not bother to batch daily. This module allows you to maintain your batches in alogical, historical manner (e.g. by month), much like thefile cabinet in your office without having to run thebatch at a specific time or date. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
The module includes a feature that lets you re-batch previously batched orders if their batch has not been deleted. For example, you may batch orders daily. But then at the end of the month, instead of having 30 batches in your order processing tab, you can re-batch all the orders for that month into a single batch. This makes archiving orders convenient.
The build action of this module is run within Admin,under the Store Utilities. Once the batch is created, theRun Report screen pops up. You can run a report then oryou can find the batch and run a report later from theorder processing section. The batches show up in thestandard list of batches under Order Processing.
Communication of order status with your customers is a critical element in the overall success of your store. Provide order status change emails to customers, keep track of order changes with backend administrative notes, and provide customers with an easy login view of their order status and invoice. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Order status updated in admin including tracking numbers and admin notes - Bulk update several orders' status with a single click - Status change emails with tracking links can optionally be sent to customers - Unlimited number of templates for the status change emails - Quick inventory adjustment when orders are cancelled - End of day (EOD) productivity report for all dates, a range of dates, or specific date - EOD display all records or just the records with a specific status - EOD contains links to the order edit screen for easy viewing of an individual order - EOD display of products sold summary reports - Run a Stock Level Report (SLR) to determine which items are nearing depletion - Editable interface to change the inventory levels of all/any products in the SLR - Export the SLR for mass editing/importing or to interface with your office backend - Annotate progress updates from multiple departments within the order record - Progress is visibile to other admin entities within your store at all times - Customers can view their order status history including tracking links and product lists - Order status history can use default or store built template - Customers can view their invoice within current orders from the order status history or the link in the confirmation email - Customers can view their order status and shipping tracking by entering their order number and email - Customers can have one click re-order from invoices in the current orders - Auto-assign customer membership to price groups based on their order total history
Feature Details. Provide order status change emails to customers, keep track of order changes with backend administrative notes, and provide customers with an easy login view of their order status and invoice. Easily manage customer communication with this module and the related modules below.
The membership system allows you to automatically include customers into price groups when they log into your store and is based on their prior purchase history. You set up your price groups as you would any price groups and assign the applicable products to those groups. Then you specify a trigger level required for the customer to be a member of each group. You can insert tokens into the applicable screens, e.g. customer edit, welcome back returning and new customers. Then when they log in, the token runs the order history for the status codes you specify (e.g. F for filled), sums the totals, and checks to see if they meet a membership level. If they do, they are inserted into the highest qualified price group.
In addition to enhanced communication with your customers, you may want to manage product levels associated with orders and cancelled orders. Miva Merchant allows you to track stock levels of your products online. As products are placed in the basket, the level is decremented. If the order is not completed, the products are returned to the shelf when you delete expired baskets. If the order is cancelled, the products are not automatically returned to stock in the core Miva Merchant. The customer and product management modules interface with the built in internal inventory management (IM) system to improve the overall IM usability.
In the administrative interface:
Shipping tracking numbers, entered through admin, display in the customer account and the status update email (can be linked directly to the shipper tracking page)
Change the order status and optionally send the customer an order status email which can vary based on the style of the status email chosen. Email styles are created using templates with tokens for insertion of specific variables. Can update several orders at once with the bulk status update feature.
Run an end of day-productivity report for all dates, a range of dates, or a specific date displaying all records or just the records with a specific status. A convenient link to the order edit screen makes viewing an individual order quick and easy.
Re-establish inventory levels for a product when an order has been cancelled (auto-restock) or new quantities are put in your inventory.
Run a Stock Level Report to determine which items are nearing depletion or all products being managed for inventory. The module admin console includes an easily editable interface to change the inventory levels of all/any products in the report.
Export a flat file of product codes, quantity, and product name for easy mass editing/importing or to interface with your office backend systems or for re-import into Merchant itself.
Additional order related data can be added in the admin screen; employee code making the status change, date of the change, narrative notes about the order, numeric value (e.g. for adjustments). Multiple admin updates can be made to each order's record by any department within your store (packing, shipping, accounting, returns, etc).
From the customer account record:
Customers can view the status of all of their orders, including update information (e.g. tracking numbers) which is entered by the store owner through admin. The order status history display can be modified by the store owner with a template and tokens. You can even include hot links to carriers' tracking systems with the number filled in. You'll need to enter your carrier tracking URLs into the module's admin configuration screen. The number of carrier URLs you include in admin is not limited.
Customers can view their previous invoices as long as they are in online batches or still in the unbatched orders.
Even after orders and batches are deleted (you may delete processed orders to save disk space) the customer can still review the basic products listed in their order along with the shipping and payment info.
Customers can re-order/duplicate a previous order with a single click from the invoice (order details page) which are still in online batches (i.e. not deleted) or as yet unbatched orders.
Be sure to take a look at our other related modules which can enhance store - customer - vendor communication even further. They include:
Contact Manager - provide a support interface without needlessly including your email on your store's pages for spam harvesters to capture
Event Reminder - customers and store admin can schedule reminders to themselves or others for specific events/tasks at specific times
Follow-on Contact - generate after sales communication at pre-determined points of time in the future
Mail Manager - generate template emails (with tokens) as HTML or text as an auto-response, e.g. as customer order confirmation or even welcome emails
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.
Wow Wow Widgets are blocks of customizable compiled template code that are dynamically displayed on any MIVA Merchant 5 page. A widget can contain text, html, or MIVA Merchant's template scripting code. Widgets are flexible and reusable, can be easily edited and duplicated, and can be used to display dynamic content, including products, categories, and baskets, anywhere.
Widgets can be used to display: a mini-basket in the sidebar of any page; one or more category listings on the storefront and on any other page; mini-category listings anywhere, with links to the category page; products on any page; multiple headers and footers; blocks of dynamic content that are reused in specific place through out the store; and just about anything else, anywhere.
By adding a content management layer, the Wow Wow Widgets module makes it easier to include, edit and manage content within MIVA Merchant 5.
