Found 298 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.
Customers can identify products that they would like to purchase but are currently out of stock. Once you place the product in stock, you can run the Send Email routine from the admin interface. It sends an unlimited number of notifications as one process, using Miva Engine
functions to prevent timeout. Each waiting customer will receive an email telling them that the product is back in stock.
If you are using my Inventory Management (IM) module (version 2.x or 3.x) or Miva's Inventory Management (version 4.x), the wait list manager will automatically insert the Wait List link on the product page when the
quantity is zero or less (version 2.x or 3.x) or out of stock (version 4.x configurable on a product by product basis). If you have modified your IM (version 2.x or 3.x) to allow ordering at less than zero to a specified lower
amount, you can modify the Wait List Manager to account
for that. In 4.x, this is determined by the global default or individual product's "out" setting. You can even block the
automatic link insertion by including the product code in the blocking list through the admin interface. If you
are not using an Inventory Management module, you can
still use the Wait List Manager by manually inserting the link into the product description of products you want to
"Wait List". In the case of "other" inventory management systems, you can insert the link into the code that those systems generate for out-of-stock messages.
When the customer clicks the Wait List link they are taken to a form to verify/enter their email address. If they are logged in, it inserts their email address for them. If not, they just type it in. The form also lists the number of other customers waiting for the item if
that number is 5 or above (just to the right of the
product name). This will give customers a sense
of urgency when they receive the in-stock notification. When they add themselves to the list, you have the option (in admin) of sending them a thank you (for their interest) email. If you employ this option, it will also tell them their position on the Wait List. When products are in short supply, that may be something your customers would like to know. Also, if they are already on the Wait List, and sign up again, it will not
duplicate their record, rather it will email them that they are already on the list and what their current position is on the list.
The admin configuration screen allows you to vary the name and/or image associated with this program so you aren't locked into the term "Wait List". You can also change the colors and fonts in the form along with the verbage in the form and notification email. You may even want to pass on a coupon code in the notification email for customers who have been waiting for a product.
When editing an individual product in admin, you can also display all of the Wait List records associated with that
product. They can be deleted manually in this screen if you don't plan to restock the item. There is also a handy link for mailing them to verify their continued interest in the item. For those not using an Inventory Management, this is also the screen that allows you to use Wait List to notify customers when an item is re-stocked. The Inventory Override works with either no online inventory system or inventory systems from other 3rd party module providers. Naturally, it also works with mine (version 2.x and 3.x) and Miva's (version 4.x) inventory systems. You can even limit the
notification in this screen to just some of the waiting customers. This is useful when you only receive a small number of the out-of-stock item and there are many more waiting for it. Since the entries are arranged in order, it is easy to give those on the waiting list the longest, the first shot at the newly re-stocked item.
You can quickly get a summary of all of the items on "Wait List" to provide you with a re-order, based on demand, tool.
When you Send Email, the module searches all products with a stock level (if using mine or Miva's Inventory Management systems) above zero and checks the product code against the Wait List database. Pending Wait List customers are notified of the re-stock of the product and their Wait List record is then deleted.
This module works with both the Miva Merchant and OpenUI look and feel user interfaces. Minor editing is required if you are not using the OpenUI.
To help the store owner identify needs quickly, an
optional CC email can be sent when an item is wait listed.
In the compiled version, you can use this module with
the standard MMUI, as mmui.mv edits are not required in
Merchant versions 4.14 and newer.
New in the compiled version is an alternate template form for
the customer to enter their name and email address. This template can
be HTML customized to suit your look and feel. If you are
not skilled at coding HTML, you can still use the default
(built in) form which is customized with colors, fonts,
etc with easy inputs in admin.
The compiled version of this module can use OpenTokens
instead of hook points within OpenObjects. The
OpenDesigner screen lists the OpenObjects which can
replace all or some screens within the OpenUI user
interface. The OpenObjects provide a template screen
which contains the existing hook points (backward
compatibility), OpenToken capability, and the ability to
move output around within the OpenObject screen. Since
the tokens in this module conform to OpenToken
functionality, they may be used in other template type
screens like those provided by Viking Coders. Place the
wait list button on the Merchant pages so that it
better fits your desired look.
Manage coupon addition and redemption functions within a Miva Merchant 2.2x, 3.x or 4.x storefront with this plugin module. License is for ONE mall. Within that single mall, it can be
used in multiple stores without additional license.
Features: (some features are only in the compiled version)
- Configurable prompt
- Configurable action
- Configurable redemption
- Configurable coupon rejection messages
- OpenTokens for use in OpenObjects
- Searchable coupon database with pagination
- Easy view admin for coupon content and historical usage
- Coupon codes can be individually assigned
- Import coupon codes from flat file in bulk
- Autogenerate coupon codes with token
- Assign coupon code as a series for affiliate purposes
- Global scope or for specific products
- Checkout coupons one per order
- Instant coupons on product pages, multiple per order
- Fixed amount or percentage of eligible products discounting
- Specific product eligibility can be scoped to the attribute level
- Minimum order level for redemption
- Establish expiration dates
- Line item display in basket after redemption
- Single use coupons
- One per customer coupons
- Multiuse coupons (can be limited)
- Free shipping coupons
- Limit the country, state or zip a coupon can be used for
- Combination of free shipping and order discount (% or fixed) coupon
- Easy deletion of expired coupons
- Coupon report identifies coupon usage
Feature Details. You can add coupons through the standard Miva Merchant admin interface and include usage criteria.
An unlimited number of coupons can be assigned to the store and each identified with a coupon code. Once you have added the module to the store, you can add coupons in the Order Fulfillment section of the admin interface. When you select the Add icon, you will have several input fields to fill in. You must enter a unique code for your coupon. This is the code that you will give to customers so they can shop and redeem the coupon (one per order). It can be any combination of letters and/or numbers.
The compiled version has a coupon generation function. You can embed a token in your welcome email or notification emails generated with our
Mail Manager module. A unique coupon code will be created and is based on the coupon template you designate. You can have an unlimited number of templates and an unlimited number of coupons copied from them. If you are not using our Mail Manager, you can still activate the generator by placing the token in the invoice header if you are using the OpenUI.
If you have a lot of coupons you want to load into the system quickly, the compiled version has a coupon import from flat file module
An optional expiration date can be included which will prevent its use if the date has passed. Enter it in the year, month, day format, eg. 20000724 would be July 24, 2000. If you leave this field blank the coupon will never expire. However, you can still delete it manually through the admin interface.
A fixed value OR percentage discount off the order total is assigned to each coupon. The default is fixed value/price,
eg $5.00 off the order total. If you put the % sign in the next input field AFTER the value field, it will calculate the coupon value based on the assigned percent of the order total. The %, if used, is entered in the separate field to the right for that purpose. If left blank, the calculation will be based on the fixed value of the coupon. See the note below about restricting discount calculations to specific products instead of the order total. A maximum redemption value can be assigned to each coupon in Merchant 4.x.
If you enter the letter S in the field to the right, the
coupon will be used to allow free shipping (compiled version only) for the entire order. Other criteria for the coupon must be met, e.g. minimum order amount, eligible products, etc.
Optionally, a coupon can be allowed only when an order total reaches a specific amount. For example, you can give a 10% discount when the order total reaches $200 as an incentive or promo. In all cases where a raw value is used, you must make this value equal to or greater than the value of the coupon. If you use the percent calculation, this value can be any value, including zero.
Based on your state's tax requirements, the coupon can be designated to reduce the sales tax or not reduce it. The coupon's tax effect is on the order total, not on individual products. For example, in some states, a store coupon reduces the cumulative value of products purchased before the sales tax is applied, hence you would want it to reduce tax. The exception to doing this is if your products are likely to be non-taxable, making a coupon reduce tax could result in a negative tax calculation. Another type coupon might be the manufacturer coupon. In some states, manufacturer coupons do not decrease the tax liability. You should determine your state's tax requirements before adding coupons to your store.
Coupons can either be used:
multiple times - The coupon can be used at every visit by any customer who shops at your store. This is usually used as a promo to customers, user lists, clubs, etc. They often have a short expiration date to limit their use. A typical usage might be a special holiday sale, eg 10% off everything in the store if used by a specified date. This would eliminate the need for special price groups if the intent is that everybody who has the coupon code can use it.
only one time for each customer - The coupon can only be used for one visit per customer. When the same customer shops at your store a second time, if he/she uses the same coupon code, it will be rejected. This is probably the most common coupon and is usually used in print ads or as a promo, eg. "$5.00 off on your next visit".
only one time for a unique coupon code - The coupon can only be used once. Once any customer has used this code, it becomes unavailable for any other purchase. This is often used as a customer relations tool, eg "sorry for the inconvenience, please accept this coupon.....".
You can restrict usage of a coupon in your store so that it can be used only if a specific product code is ordered. You can list several product codes, any of which in the basket would make the coupon valid if the other requirements are met. Leaving the product code blank means that customers do not have to order a specific product as long as they meet the other requirements the store owner has specified. If you check the box to the left of the product code list AND are using the percentage discount, only those products in the code list will be used in the calculation using the qualifying products subtotal. If you do not check the box, the percentage discount will be applied against the order total. In Merchant 4.0, you can use a wildcard for the product list, e.g. 1AA* would make all products beginning with 1AA eligible for the coupon discount.
New in the compiled version of the coupon module is the ability to restrict the coupon usage down to the attribute level. For example, you can limit the coupon to product codes beginning with 1AA and the attribute "Version" with the option of "4.5". The
format for the input would be 1AA*~Version~4.5|
Alternatively, if you precede the product list with a - (minus) character, the coupon will be excluded from use with those product codes. You canNOT specify it to the attribute level like the include above. (compiled version only)
Appropriate error messages are displayed when coupons don't meet the usage criteria established by the store owner. When the shopper enters a coupon code at checkout that is not valid based on the criteria you establish, he/she will see an error message just below the coupon code input when the checkout form is re-displayed. One coupon can be redeemed per order on the checkout page.
In admin, the coupons can be easily displayed and edited. The coupons are displayed in a table format with configurable number of coupons per page displayed. The entire coupon database is searchable by coupon code or portion of the coupon code.
Expired coupons can be removed from the database (to cut down on disk usage) one at a time or in mass. In admin, you can either put a check in the remove column and select update or select purge expired coupons, then select update.
A historical database, which can be imported and analyzed in database or spreadsheet software, is maintained on all coupons used. The couponuz.dbf can be FTPd to your PC for further analysis in MS Access, MS Excel, or other data management software. This could be useful in determining which coupons bring you the most activity. The number of uses for each coupon is displayed in the admin table in Merchant 4.0
New in the compiled version is the coupon usage report. You can summarize or list each coupon used for a specific time period. You can also restrict the output to a specific coupon code or a string of characters in a coupon code. This latter is useful when you have assigned a series of coupons to an affiliate or advertising campaign. You can determine how much business was brought in with the coupons from various sources.
The compiled version of this module can use OpenTokens instead of hook points within OpenObjects. The OpenDesigner screen lists the OpenObjects which can replace all or some screens within the OpenUI user interface. The OpenObjects provide a template screen which contains the existing hook points (backward compatibility), OpenToken capability, and the ability to move output around within the OpenObject screen. Since the tokens in this module conform to OpenToken functionality, they may be used in other template type screens.
MMUI and OpenUI compatible. If you are using MMUI, there are two required edits in the mmui.mv. If using MMUI in
a compiled version of Merchant (4.14 and newer), you will need to edit and recompile the mmui.mv (expensive proposition). Thus, with compiled Merchant, we recommend using OpenUI instead of the MMUI user interface.
The OpenUI Extension Module Kit features 32 extensions. LICENSE IS PER DOMAIN.
The Plug N Play Pack #5 includes the abilities to:
Begin_Screen & General
multinavbars.mv - Alternate Navigation Bar Menus. Will display a different Alternate HTML Menu for each screen. Displays normal Navbar for any missing HTML file files.
newframe.mv - Basket Contents Required Before Checkout. Checkout is called in NEW SCREEN. Useful to break out of frames.
bodyheader.mv - Adds a Perpetual Header to the Body of ALL screens.addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
Store Front Screen
nocattreesfnt.mv - Removes Category Tree from Store Front Screen.
Category Screen
adddesccatexp.mv - Places Description below quantity in basket on Category Screen Expanded Display.
addmorecatexp.mv - Add More Info Button to Category Screen Expanded. Displays either gif or grey button. Displays above "Add to Basket" and "Buy One Now" buttons.
addmorecatline.mv - Add More Info Button to Category Product Line Display Screen. Displays either gif or grey button. Displays left of "Add to Basket" and "Buy One Now" buttons.
addquancat.mv - Add Quantity and Box to Category Screen.
addthumbcatline.mv - Add thumbnail image on the Left End of the Category Screen Product Line Display
nocodelinknamectgy.mv - Remove "Code" and add a link to "Name" in the Category Screen Product Line Display.
autodefaultimg2X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 2.X ONLY.
autodefaultimg3X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 3.X ONLY.
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
Product Display Screen
autodefaultimg2X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 2.X ONLY.
autodefaultimg3X.mv - Automatically displays a default image named notavails.jpg for Thumbnails and notavail.jpg for Images. Version 3.X ONLY.
autoimggifjpgprod.mv - Automatically displays either GIF or JPG images. No need to set path in admin. Displays a default image named notavail.jpg for Images not found. Version 2.X and 3.X.
autoimgjpgprod.mv - Automatically displays JPG images. No need to set path in admin. Displays a default image named notavail.jpg for Images not found. Only searches for JPG images. Version 2.X and 3.X.
autoimggifprod.mv - Automatically displays GIF images. No need to set path in admin. Displays a default image named notavail.gif for Images not found. Only searches for GIF images. Version 2.X and 3.X.
noattribqtyprod.mv - Remove Quantity and Attributes in Product Display Screen.
Product List Screen
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
addthumbplst.mv - Adds Thumbnail Image on the Left End of the Product Line Display on the Product List Screen.
nocodelinknameplst.mv - Removes "Code" and adds a link to "Name" on Product Line Display on the Product List Screen.
addmoreplstline.mv - Adds More Info Button on the Product Line Display on the Product List Screen.
Search Screen
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
addthumbsrch.mv - Adds Thumbnail Image on the Left End of the Product Line Display on the Search Screen.
nocodelinknamesrch.mv - Removes "Code" and adds a link to "Name" on Product Line Display on the Search Screen.
addmoresrchline.mv - Adds More Info Button to Related Products on the Search Screen.
Related Products
addthumball.mv - Adds Thumbnail Image on Left End of Line on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknameall.mv - Removes "Code" and adds a link to "Name" on all Product Line Display Screens. (Category, Search, Product List and Related Products.
nocodelinknamerel.mv - Removes "Code" and adds a link to "Name" to Related Products on the Product Display Screen.
addmorerelated.mv - Adds More Info Button to Related Products on the Product Display Screen.
addthumbrelatedprod.mv - Adds Thumbnail Image on Left End of Line to the Related Products on the Product Display Screen.
noaddrelatedprod.mv - Removes Add to Basket from Related Products on the Product Display Screen.
nonamerelatedprod.mv - Removes Name from Related Products on the Product Display Screen.
nopricerelatedprod.mv - Removes Price from Related Products on the Product Display Screen.
nocoderelatedprod.mv - Removes Code from Related Products on the Product Display Screen.
Upsell Screens
dispthumbupsell.mv - Displays Thumbnail instead of Full Sized Image on the Upsell Screen.
nocodeupsell.mv - Removes "Code" from the Upsell Screen.
nowtupsell.mv - Removes "Weight" from the Upsell Screen.
Almost all of these Extension Modules are completely "Plug-N-Play". Designed/Written by Luray Williams.
If you are not using OUI version 3.11 or above you must upgrade to at least version or these modules may not run correctly. The latest version of Open UI can be downloaded at http://www.openui.org
Customers receive access to a private support forum at the DesignExtend Miva Merchant Discusson Boards. Full instructions on installation included.
Provide an easy interface for visitors to refer your site URL to their friends. It uses the Miva SMTP capability. The subject and body of the Tell a Friend email message is
configurable through the Merchant admin interface. The form colors and fonts that the customer sees is also configurable in admin. You can choose to have a blind CC sent to the store email address and a log entry (date, from, to, product code - if applicable) maintained in a
flat file when referrals are sent. If the customer sends
the referral email when they are on a specific product
screen, a second link to the product is included in the
email. In Merchant 4.x and if you are using our Gift - Wish List module, there is a convenient button on the bottom of the Gift List display that sends the Gift List URL to your friends.
The module is MMUI and OpenUI compatible. If using the MMUI, two edits are required in the mmui.mv. With MMUI, you can place the button just about anywhere on the screen that you want it, the most common location being at the bottom of the category column. With the OpenUI, you can select through admin among the eight possible locations.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the Tell-a-Friend button
on the product page so that it better fits your desired look. Also, new in the compiled version is the ability to send the search string to a friend if your store is also using our Power Search module. Clicking the link will reproduce the search the original friend had created with Power Search prior to sending the Tell-a-Friend email.
In the compiled version, you can use this module with
the standard MMUI, as mmui.mv edits are not required in
Merchant versions 4.14 and newer.
New in the compiled version is an alternate template form for
the customer to enter friend names and email addresses, plus
an option to allow them to include a note. This template can
be HTML customized to suit your look and feel. If you are
not skilled at coding HTML, you can still use the default
(built in) form which is customized with colors, fonts,
etc with easy inputs in admin.
New in the compiled version is the ability to embed
certain tokens in the tell a friend email. For example,
if you are using our Coupon Redemption module with its
unique coupon code generation feature you can insert a
token like %module|couponrd|1~TELL-% in the body of the
email. If you are on a product page when you send the
email, the email can also contain the product name,
image or thumbnail, and price by using tokens. Also,
new in the compiled version is the ability to send the
email as HTML formatted instead of plain text.
New in the compiled version is the ability to send the
search string to a friend if your store is also using our Power Search module. Clicking the link will reproduce the search the original friend had created with Power Search prior to sending the Tell-a-Friend email. This is similar to the link you can send for
the Gift/Wish list if you are using our Gift List module.
The compiled version of this module can use OpenTokens
instead of hook points within OpenObjects. The
OpenDesigner screen lists the OpenObjects which can
replace all or some screens within the OpenUI user
interface. The OpenObjects provide a template screen
which contains the existing hook points (backward
compatibility), OpenToken capability, and the ability to
move output around within the OpenObject screen. Since
the tokens in this module conform to OpenToken
functionality, they may be used in other template type
screens like those provided by Viking Coders. Place the
Tell-a-Friend button on the Merchant pages so that it
better fits your desired look.
This license key allows you to upgrade from any previous version of Miva Merchant to version 4.x (non-compiled or compiled).
NOTE: Before upgrading you should verify that any third party modules you have are also ready to be used with version 4.x.
We can install 4.x for you! Upgrading to version 4.x can be tricky. Leave the worrying and fixing to us. We'll backup your data, and install the upgrade in a separate directory on your server so you can test the new version while your existing store is still live to customers. This process gives you plenty of time to test your newly upgraded store before opening it to the public.
Hide Prices Pending Customer Approval module Tremendously useful for wholesalers and other store owners who want to limit access to a known, and approved, customer base. Product prices can be hidden until a customer's account has been approved by the store's owner. Access to the site can also be restricted, requiring customers to login. Includes an administrative utility for review & approval of customer accounts and assigning of price & availability groups. Fully compatible with OpenUI OpenTokens and third-party template-based modules.
Professional Version Features:
Price & Availability Groups support integrated into utility module - easily select a price & availability group while approving a customer
Require Customers to login - customers can be required to login (or create an account) before being granted access to anywhere in the store or to the product-related pages
OpenUI OpenTokens fully supported
Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Display Attribute-Option prices on Product Display screen
Plus all the features of the Standard Version
Summary of of Standard Version Features:
Multiple modes for hiding prices - prices can be hidden until a account approved or until a customer creates/logs-in to an account.
"Add To Cart" and the "Buy One Now" buttons are also hidden.
Prices & buttons hidden on the Product List, Categories, Search Results, and Product Display screens
Optional, fully-customizable message can be displayed in place of the hidden prices, on the customer accounts screen & on all screens for accounts that are pending approval
Two modules in one - includes a feature-rich administrative utility module for approving and managing customers
"Quick approval" feature for approving new customer accounts
Compatible with compiled Miva Merchant version 4.14 thru 4.2.
OpenUI OpenTokens OpenUI OpenTokens are fully supported.
Template-Based Modules Compatible with template-based modules, including Viking Coders Category Page Templates & Product Page Templates
Requires OpenUI.
Details
The "Hide Prices Pending Customer Approval" module contains a wealth of functionality and customizable options. It's tremendously useful for wholesalers and other store owners that want to limit access to a known, and approved, customer base.
Product Prices Hidden Product prices can be hidden until a customer's account has been approved by the store's owner. Optionally, prices can be hidden until a customer creates or logs-in to an account (without requiring approval of the account).
Buttons Too The product prices - and the "Add To Cart" and the "Buy One Now" buttons - can be hidden on the Product List, Categories, Search Results, and Product Display screens. An optional, fully-customizable message can be displayed in place of the hidden prices.
Require Customer Login Customers can be required to login (or create a new account) before being granted access to the entire store or to the product-related pages (Product Listing, Categories, Search, Product Display & Basket screens).
For instance - The module can be configured to "Hide Prices Pending Approval of Customer Account" and to "Require Login to View Products".
With this configuration:
Customers could access the storefront but would be prevented from accessing the Product Listing, Categories, Search, Product Display & Basket screens. They could of course also access the Login & Create New Accounts screens.
Once the customer logged in or created a new account, they would then be able to view the Product Listing, Categories, Search & Product Display screens, but the prices would be hidden.
Once the account was approved by the store's administrator, the customer would be able to login and view product prices.
Multiple Levels of Price Display & Access Restriction
Display of Prices:
Hide Prices Pending Approval of Customer Account
Hide Price Unless Customer Has Account
Show Prices - (Disables Module)
Access to Store:
No Login Required to Access Store
Login Required at Storefront
Login Required to View Products
Customer Messages An optional & customizable "Customer Account Pending Approval" message can be displayed just below the Miva Merchant header. An optional & customizable message can also be displayed on the Customer Account & Customer Information screens. This can be used to inform the customer of the store's policy for accessing the product prices.
For example: "Approval of customer account is required. Please complete the customer account form. You will be notified by email when your account is approved."
Two Modules In One It's actually two modules - a OpenUI system module and an administrative utility Module. The system module customizes the store's look and feel and limits access to prices. The administrative utility module provides the store owner with the ability of reviewing and approving customer accounts.
It's also a feature-rich, admin-friendly customer management utility.
Choose the way you approve customer accounts - accounts can now be approved using either the standard Customer admin or the administrative utility module.
Quick Approval of Customer Accounts The Approve Customers administrative utility module also has a "quick approval" feature. A store's administrator can quickly search for a new customer by login, email address, or other keyword - then approve the customer with one click.
Admin-Friendly navigation - Sort Customers by newest, by id, or by login. Search by login, name or other keyword. Easily scroll through customer records, choose how many are displayed per page, go to first or last record, approve, edit or delete records.
Integrated Price & Availability Groups Support The store administrator can also assign customers to a price and/or availability group at the same time that accounts are being approved.
Template-based Merchant Notification of New Accounts An optional email notification can be sent to a specified address whenever a new account is created by a customer. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Template-based Customer Notification of Approved Accounts An optional email notification can be sent to the customer whenever their account is approved. The subject, header & message body are fully customizable. The message template has tokens for all customer fields - login, password, shipping info & billing info.
Display Attribute-Option Prices Attribute & option prices on the product display screen.
Fully customizable attribute-option prompt template gives you complete control over their display
Works with all types of attributes, drop-down menus, radio button, checkboxes, text fields & memo fields
Modifies both the Product Display & Missing Attributes screens
Completely compatible with Miva Merchant price groups
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)
MmDbDOC - truXoft Data Doctor and Miva Database Editor
MmDbDOC is a tool for testing and repairing corrupted databases and database indexes. It allows you to remove duplicate records from any Merchant or non-Merchant database quickly and without downloading or importing them, directly through the Miva Merchant Admin web interface. There are three different ways of the duplicate records repair:
manual selection - you can select which of the duplicate records you keep, and remove the remaining one(s)
manual editing - you can edit the duplicates so that you keep several or all of them in the database but change the unique identifier field(s) so that the duplicate key in the index is avoided
fully automated - MmDbDOC will automatically remove all duplicate records from the selected database, keeping always the first found record in the duplicate set
MmDbDOC can be also used for viewing databases. This feature is invaluable for quick database verification, for retrieving data not accessible through Miva Merchant Admin (i.e. customer passwords, module settings, basket data, affiliate data, ...). Please note: We recommend viewing the raw databases containing sensitive data (passwords, email addresses, payment data) in secure mode only (SSL / https).
The PRO version includes a full featured database editor for modifying any Miva Merchant or 3rd party database tables. Fields may be quickly modified without downloading or exporting any data. New records may be added or old ones deleted. You can duplicate whole blocks of records with a simple click and edit them afterwards.
Main Features
version
DEMO
Standard
PRO
Merchant databases
yes
yes
yes
3rd party databases
yes
yes
yes
database list
limited
yes
yes
database information
yes
yes
yes
index expression retrieval
yes
yes
yes
dupe locator
yes
yes
yes
database browser
limited
yes
yes
database viewer
limited
yes
yes
manual duplicates repair
no
yes
yes
editing duplicate records
no
yes
yes
automated repair
no
yes
yes
index error parser
no
yes
yes
editing records
no
no
yes
deleting records
no
no
yes
adding/cloning records
no
no
yes
database packing
no
no
yes
Please note: truXoft Ultra Batch is required for the full functionality of the standard or PRO versions. The free version of Ultra Batch that comes with MmDbDOC, allows you to see maximally up to three records at a time.
Support
truXoft offers limited free support within 30 days after the purchase of the module. Issues not included in the free support:
Information about the structure of Miva Merchant databases
Information about individual database tables or the database fields
Information about relations between individual Miva Merchant database tables
Help with repairing or editing of databases
Any other issues not directly related to MmDbDOC
Important note: The database editor in the PRO version was designed for advanced users who understand the basic structure of Miva Merchant databases. MmDbDOC allows you to edit the raw data, but makes no verification of the data you added, modified or removed. If multiple tables are in a relation, it is the user who has to insure to edit all related tables appropriately to avoid breaking the cross table links. Unqualified editing of the databases may corrupt the store. We highly recommend backing up the entire domain and store data before removing duplicate records (repair) or before editing the databases. truXoft bears absolutely no liability in case of loss of data, corrupted databases or a broken Miva Merchant store. If any such case should occur, please restore the original data from the backup.
After repairing or editing any database, you have to pack both domain and store data in Admin!
Instructions
Installation instrucitons may be found in the readme.txt included in the distribution package. After registering your license key, in Ultra Batch (Xadmin) screen in the main frame of Miva Merchant Admin, click on the tab "databases", select the mode "database list" and click the OK button. Ultra Batch will show you the list of all pre-defined databases.
If a corrupted database with duplicate records is detected, the "Repair" button appears right in the line of the concerned database. By clicking it, you access the repair interface and see the first found set of duplicate records.
You can either:
select the record you want to keep (click "KEEP Selected"),
or edit the records to avoid the duplicate key (edit the fields with light blue background so that the resulting key is different at each record) and click the button "Keep multiple"
or let MmDbDOC repair the database unattended (click "Automated Repair")
In case of manual repair, as described above in 1) and 2), you have to repeat the operation with each duplicate set individually. Normally, you should use the default mode of Ultra Batch hiding deleted records - select "standard" in the first small dropdown box in the right part of the Ultra Batch control panel. In case you use the mode "all", you'll have to navigate through the duplicate sets with the help of the navigation buttons right below the Ultra Batch control panel.
The navigation buttons can be used also when you want to preview all duplicate sets before starting to repair them. Please note that the filter expression (top left) and pagination (top right) of Ultra Batch have influence on the MmDbDOC output. When low numbers are selected in the pagination in sake of faster page loads, use the navigation buttons to proceed to the next page. It applies also for the database list, not only for the repair and edit interface of MmDbDOC.
Before starting to repair or edit databases with MmDbDOC, it is recommended to put the store into maintenance mode. Use the first button (the lock) in the Ultra Batch panel to close and re-open the store. We also highly recommend to back up the entire Miva Data directory containing the databases, before performing any operation on the data with MmDbDOC.
If you experience a runtime error in the store front or Admin, where the message speaks about a database index, copy the message, and after opening the mode "parse error" in the "databases" tab of Ultra Batch, paste the error into the displayed field. MmDbDOC will look up the databases and launch the repair interface.
In case you need to repair a database not listed, you can select the "3rd party dB" mode and enter the database and index paths manually to start the repair function.
Database viewer (demo and standard versions), or the database editor (PRO version) can be launched by clicking the requested database alias in the database list.
IMPORTANT: after repairing or editing any database, you have to pack both domain and store data in Admin!
Compatibility
Any UI (MMUI, OUI, KCUI,...)
Miva Merchant v4.14 or higher
Miva Empresa v4.07 or higher
MSIE 6 recommended for the Administration interface of truXoft modules
Compatibility with OpenXB stores was not yet tested
Price: $39.95 Pro Version $99.95 Upgrade Cost: $0
Upgrade Terms (If Any): N/A Compatibility: MMUI/OpenUI Versions:
4.14-4.23x (Available Compiled All 4.x Versions) Other Module Compatibility: N/A
NetPush Order works with all versions of Miva Merchant except for version 1.x. Included with the product are two modules for each version of Miva Merchant--one for uploads and one for downloads. NetPush Order runs on computers using Windows 98 or later and does not require Access or any other applications to be installed. Version 2 of NetPush Order is the first public release.
NetPush Order 2.00 is an advanced order and product management system that makes keeping track of your online store easy and efficient. NetPush Order runs on any computer that has Windows 98 or later. With its simple, intuitive screens and controls, you have the full ability to add or modify your store's orders, products, customers, and much more. Simple imports and exports allow you to write changes you make back to your online store, and download new information that your store has collected. Other features include integration with QuickBooks, reporting, pick lists, invoicing, and more.
NetPush Order is a perfect choice for Miva Merchant users. Special Miva Merchant modules allow you to seamlessly import and export data, at the click of a few buttons. Nearly every native Miva Merchant database object for every version since 2.x is supported within the NetPush Order application. Recent features such as inventory are covered, as are the built-in payment modules. If you are a Miva Merchant store owner, and you're looking to streamline and simplify your order processing and content management, NetPush Order may be the perfect choice for you.
Complete CSV import and export for integration with shopping cart systems.
QuickBooks and general ledger import/export
Complete order management system
Customer management interface
Complete product and category management for Miva Merchant
Direct order entry
Pick lists and labels
Invoices
Multiple Site/Store support
Access, SQL Server, or MySQL back end
NetPush Order Professional Edition is meant for any business that has more than one store or multiple users. The professional version can connect to databases like SQL Server and MySQL. The Professional Version is perfect for fulfillment companies that manage multiple stores for multiple organizations.
Purchasing and Registering NetPush Order. When you purchase NetPush Order you will receive a License Registration Key in your email confirmation, along with a link to download the program if you have not already installed the free trial. You must use this License Registration Key to register your copy of NetPush Order within 30 days of the original installation. Registering your copy with us is required for the program to function, and it qualifies you to receive support services from NetPush. Upon registering you will be emailed an Unlock Code, which you enter into NetPush Order to ensure it continues to function. There absolutely no additional charges to register your copy with us or to receive support services.
This module allows a Merchant store owner to import attributes (text, textarea, checkbox, radio, and select) and options from an easily edited/managed flat file. The module also allows the type "template" to be specified if you have previously added the corresponding template through admin. It will not create the templates and its internal attributes/options. The module will also delete product attributes which the store owner identifies for deletion. For those sites with time-out problems, multiple flat files can be used to break up the number of attributes and options being imported at one time. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Normally, additions are made based on the product code. A typical version 5.x entry inthe flat file for a radio button attribute for a specific product would be: A|1AA00004|version|radio|Merchant Version:|0|0|1|graphics/en-US/mmui/blades.gif||| O|1AA00004|version|5X|5.xx|0|0|1||1|0 O|1AA00004|version|4X|4.xx (add $1.00)|1|1|0||2|0
The key for the field values is: A|product_code|code|type|prompt|price|cost|required|image|template code|display order|weight O|product_code|attribute_code|option_code|prompt|price|cost|default|image|display order|weight
This module also allows you to import the same attributes/options by category code. That way you can fill all of the products in a category withthe same attributes. This saves considerable typing in the flat file.
If for some reason you want to delete attributes, you can easily delete all attributes related to a product code.
The attribute and option EXPORT module is distributed with the IMPORT module. It creates a flat file in the format described above so that the data can bere-imported after off-line editing.It does not export the templates.
Most agree, Google is the mother of all search engines on the Internet. Their new venture to create a listing of actual items for sale across the Internet, rather than pages with hits on keywords, is a bold attempt to better target customers and buyers in a symbiotic relationship. This is a giant leap in eCommerce, providing comparison shopping using the Google search engine. If you are a Miva Merchant store owner you CANNOT afford to miss this opportunity, especially since inclusion in the FroogleTM index is free. How much have you invested 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. Granted, I use Static Catalog Generator to create static html pages of all of my products so there were already a lot of pages in Google. Now I have an additional 130 which had been overlooked. If you don't have a good representation of your product catalog already in Google or other search indexes, you may want to use the Static Catalog Generator to optimize site visibility. Search engine optimization requires a multi-pronged approach (static html pages, shorter links, specific paid or unpaid submissions to directories). I have found that use of static html pages consistently gets my site into search indexes better than the dynamically produced Miva Merchant pages. 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 creating a 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 you can better track where actual sales are coming from
If your store is a single store in the domain, you can remove the Store_Code from the URL to aid in search engine spidering
If you are using our Volume Pricing module (version 4.53 or newer), you have the option to submit the lowest (bulk) prices as your product prices, thus making your listings more attractive when compared with competitors in the FroogleTM listing. However, the Google Feeds Support said the quantity option is not yet supported so it would be "best if you just give the price for ordering a single item". Eventually they plan to list the minimum break points to obtain the volume prices.
Fast Data Feed plugin module creates the datafeed flat file directly from your admin
Frequent, no hassle submissions keep your data current in 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; converting the 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 your data directory for ease of capture and transmittal
Don't delay. The FroogleTM index is still in beta. As such, knowledge about it is not yet widespread due to limited promotion. The FroogleTM support team has been reviewing requests for inclusion and currently have reasonable turn around time. Your store may or may not be accepted and I would expect it to take longer and have more stipulations for acceptance and continued inclusion as this service becomes more popular. You should request acceptance into FroogleTM as soon as possible. Once accepted, whether you use our module for building the datafeed or some other software, you should do it now while time is on your side.
As this is a new endeavor for FroogleTM, I expect them to change their format and add new capabilities over time. Licensees of the 4.x version of this module will have free upgrades of the module through the 4.x version. We do not yet have a 2.x version available but will be exploring that option next week. Please ensure you select the correct module version for the version of Merchant you have.
Collect supplemental, required or non-required responses fromcustomers at checkout. You can add as many additional checkoutquestions to your form as you want, within reason. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Collect supplemental, required or non-required responses from customers at checkout - Export responses to a delimited flat file - View responses in the file with a searchable admin report - Display responses in the include modified invoice emails and batch reports and invoice screen - Include response data in the order export file created by our inexpensive EZ Batch Report module (sold separately) - Configure text label for each question to preceed the responses in the emails and reports - Special instructions for the order, e.g. shipping needs - Collect responses from survey or poll questions - Customer entered gift card messages - Questions displayed in a table which the store owner designs with standard HTML - Limit the display of questions based on specific product codes - Limit the display of questions based on the ship to country of the order - Used in conjunction with our Mail Manager module, activate sending of specific emails - Assign a fee to one response, for example gift wrapping fee, donation, or rush handling - Insert a negative fee (vs positive fee) for impromptu sales, etc - One or more responses can be required before customer can proceed - Highlighted error message when required response(s) are omitted - Tokens can be used to refill the responses if the page is redisplayed due to missing info - Our standard version contains the features you'd expect in competitors' pro version
Feature Details. The responses are exported to a delimited text file which can beimported into most database management systems for further analysis. Youcan also have those responses appear in the Miva Merchant Email notification and batchprocessing (modified email and batch modules included in the zip file). Use the module for the customer to add specialinstructions for the order, collect responses from survey or pollquestions, allow the customer to fill out gift card messages, include salesman orrepresentative code, etc.
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.
This module allows a Merchant store owner to import attributes (text, textarea, checkbox, radio, and select) and options from an easily edited/managed flat file. The module also allows the type "template" to be specified if you have previously added the corresponding template through admin. The module will also delete product attributes which the store owner identifies for deletion. For those sites with time-out problems, multiple flat files can be used to break up the number of attributes and options being imported at one time.
Normally, additions are made based on the product code. A