Found 737 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.
Discount your product base prices based on the number of items ordered of identical products, eg 1-3 = standard price, 4-6 = lower, etc. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Discount product prices based on quantity ordered - Easy from - to price breaks in a single input - Unlimited price break ranges - Fixed price or percentage off regular price - Optional automatic start and stop dates for volume pricing - Use our time zone offset to adjust the time that the date changes - Each product can have different price breaks and dates - Can use price groups with percentage discounts - Optionally apply price group discount "on top of" volume price breaks - Can exclude price groups from volume pricing - Can exclude all except specific price groups - Hide or display table which depicts price breaks - Include a quantity input in the table on category pages - Volume price can be applied on identical products or can amalgamate - Can amalgamate discounts of different attributes in the same product - Optional "as low as" to replace regular price - Optional strike thru of regular price followed by volume price - Can put all or some of your store products on sale within seconds - Can remove all volume pricing in the store within seconds - Flat file import for quick update - Optional wild card can apply same volume pricing to all products - Export volume pricing settings to flat file - Use render tokens to place "as low as" and table on applicable screens - Licensed by domain, unlimited stores under one MIVA Merchant mall pay no additional license fee
Feature Details: This module's admin interface provides an easy to enter "from - to cost" format. You can literally have as many ranges as you want to type in. See the image below for example syntax. You can either use actual values to replace the base price or percent of price to be subtracted from the product base price. These price differentials are added directly in the admin interface under the product edit screen. You only apply these price differentials in the products that you want to use them.
This module applies the price in your low,high, cost groupings. If you do not include a grouping at the single item level, it will use the method for pricing in your store. It onlyactivates if you include a low, high, cost grouping. For example: 6|10|12% 11|20|14% 21|999|16%
The module only uses price groups when using the percentoff discount calculation. If you enter fixed prices for the quantity ranges, then price groups are ignored. Keep in mindthat the percent discounts could be over and above the discountalready given if you are using price groups.
You can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volumepricing and hide the table from them completely. Conversely,you can exclude everybody from volume pricing except specific price group members. Customers must be logged in to identify the price group they are in before the volume pricing module can qualify or disqualify them from volume pricing if you are using the price group restrictions.
The percentage discounting method subtracts the percent discount from the base price. Base price does not include attribute prices. To apply the percentage, simply include the percent symbol (%) in the line. If you are using cost method for your store (other than price groups), you will not be able to use the percentage discounting method. Instead, use the actual value method.
If you are using another third party module which overrides prices in the basket and recomputes them using the price in the product record, youmay not be able to use this module. Other third party modules may notrecognize that it needs to apply the calculations in this module.
The module recognizes identical products. Hence different product codes will change the product enough that the discountwon't apply. For example 3 red shirts and 6 blue shirts willnot give the discount of 9 shirts. Rather, they'll get the discount rate of 3 for one of the line items and 6 for the other.
You can amalgamate quantities so in the example above, as long as the product code is the same and the color variation is done with attributes, all 9 items would get the volume discount for 9 items. You have the option for each product code to amalgamate quantities or treat varied attributes as different products.
You can optionally include a table on the product (PROD) andcategory (CTGY) screens displaying the rates as generatedfrom the products' volume discount record. You can optionallyhave a quantity input in that table display on the category screen. These options areconfigured through admin.
If you want to have a sale on one or moreitems. Simply set the volume to 1 or more with a specific discount percentage and you have a sale with as low as display. You can use the token %product_price_f% to further highlight that witha strike thru. To make this feature even more useful, youcan enter a starting and ending date for the sale so that itwill start and end automatically.
For ease of entry, a flat file import module is included. You can put all product codes in the flat file or use an asterisk (*) and one lineof "rules" to apply the volume price to all products in thestore. Create a storewide sale, e.g. 10% off in seconds with a specific start and stop date. Then just as quickly removeall settings at your leisure after the sale. There is also a volume price export so you can quickly build your flat file, then edit or add to it. This is useful when you want to have a storewide sale on all products butretain volume prices on your regularly discounted items. Export the volume prices. Import your sale settings. Importyour volume discounts on the few you want to maintain at pre-sale prices.
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.
Recalculate the basket prices based on the price group a customer is in when they log in. Normally, if a customer is not logged in when they place items in the basket, the basket price will be a non-price group price, even after they log in at check out.
Features: - Automatically recalculate basket prices when logging in - Exclude specific product codes from the recalculation - Safety check price change to ensure it does not raise it - Token available to force recalculation in addition to the automatic log in recalculation (Merchant 5.x only)
Feature Details. Automatically recalculate. When the customer logs in, the module will determine the price group status of the customer. If they are in a price group, it will recalculate the prices in the basket to reflect the price group prices of the items.
Product exclusion. In some cases, you may not want to recalculate the basket price for specific products. As example, there are 3rd party modules which adjust the basket price based on other factors set by those modules. The External Product Purchase (sold separately), Size Pricing, Dimension Pricing, Override Pricing modules allow the customer to enter values in the products' attributes which ultimately effect the basket prices of the products. This product exclusion feature lets you exclude those products from the recalculation process. The basket price will remain as it was calculated by the 3rd party module that originally controlled the addition of the product into the basket.
Safety check. The module will verify that the price group recalculation will actually lower the price. Some 3rd party modules discount item prices at the time they are added to the basket, based on a variety of factors. An example of this is Volume Pricing (sold separately). If the customer orders in quantity and you have set the threshold so they will get a price break for multiples of the item, the item will be added to the basket at a price lower than its individual item price. In some cases, that value could even be lower than price group prices. The recalculation module will compare the two prices and use the lower of the two for the basket price.
Additional token. The additional token feature is in the Merchant 5.x version of the module only. This module will make the recalculation at the time the customer logs in. In some cases, you might want to force the process again. For example, the Emporium Plus Customer and Product Administration module (sold separately) has an automatic price group promotion feature. If you set that to occur when they log in, it actually happens when the screen displays at the point you place the token to do that. As the recalculation module does its automatic feature before the screen displays, the customer would not get the full advantage of a promotion to a new price group. Hence, if you are using a price group promotion feature in another 3rd party module, you can follow that process with a forced basket price group recalculation.
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.
Discount your product prices based on the number
of items ordered of identical products, eg 1-3 =
standard price, 4-6 = lower, etc.
The admin interface provides an easy to enter "from - to cost" format. You can literally have as many ranges as you want to type in. See the image below for example syntax. You can either use actual values or percent of price to be subtracted from the product price. These price differentials are added directly in the admin interface under the product edit screen. You only apply these price differentials in the products that you want to use them.
This module applies the price in your low, high, cost groupings. If you do not include a grouping at the single item level, it will use the method for pricing in your store. It only activates if you include a low, high, cost grouping.
For example: 6|10|12% 11|20|14% 21|999|16%
The module only uses price groups when using the percent off discount calculation. If you enter fixed prices for the quantity ranges, then price groups are ignored. Keep in mind that the percent discounts will be over and above the discount already given if you are using price groups.
In the compiled version you can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volume
pricing and hide the table from them completely. Customers
must be logged in to identify the price group they are in before
the volume pricing module can disqualify them from volume pricing.
The percentage discounting method subtracts the percent discount from the base price. Base price does
not include attribute prices. To apply the percentage,
simply include the percent symbol (%) in the line. If
you are using cost method for your store (other than
price groups), you will not be able to use the percentage
discounting method. Instead, use the actual value method.
If you are using another third party module which overrides prices in the basket and recomputes them using the price in the product record, you will not be able to use this module. Other third party modules will not
recognize that it needs to apply the calculations in this module.
The module recognizes identical products. Hence different attributes will change the product enough that the discount won't apply. For example 3 red shirts and 6 blue shirts will not give the discount of 9 shirts. Rather, they'll get the discount rate of 3 for one of the line items and 6 for the other.
The module for the compiled version of merchant DOES have the ability to amalgamate quantities so in the example above as long as the product code is the same, all 9 items would get the volume discount for 9 items. You have the option for each product code to amalgamate quantities or treat varied attributes as different products.
You can optionally include a table on the product (PROD) and category (CTGY) screens displaying the rates as generated from the products' volume discount record. You can see an example of that with our best seller products. You can optionally have a quantity input in that table display. These options are configured through admin.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the table display on the product page so that it better fits your desired look. New configuration options added for the table display. Also, the ability to display the lowest price in place of the standard price when volume pricing effects the product, the store is using the OpenUI, the store is version 4.14 or higher, and there are no other 3rd party modules effecting the price display. This feature is useful if you want to have a sale on one or more items. Simply set the volume to 1 or more with a specific discount percentage and you have a sale with as low as display. You can use the token %product_price_f% to further highlight that with a strike thru. To make this feature even more useful, you can enter a starting and ending date for the sale so that it will start and end automatically. For ease of entry, a flat file import module is included. You can put all product codes in the flat file or use an asterisk (*) and one line of "rules" to apply the volume price to all products in the store. Create a storewide sale, e.g. 10% off in seconds with a specific start and stop date. Then just as quickly remove all settings at your leisure after the sale. There is also a volume price export so you can
quickly build your flat file, then edit or add to it. This
is useful when you want to have a storewide sale on all products but retain volume prices on your regularly discounted items. Export the volume prices. Import your sale settings. Import your volume discounts on the few you want to maintain at
pre-sale prices. The volume price can also be used in our compiled
Fast Data Feed module for
froogle submissions and our
Static Catalog Generator which creates static html pages for better search engine indexing.
Manage coupon addition and redemption functions within a Miva Merchant 5.x storefront with this plugin module. License is for ONE mall. Within that single mall, it can be used in multiple stores without additional license. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features:- Configurable prompt - Configurable action - Configurable redemption - Configurable coupon rejection messages - Uses tokens to place input on pages - Searchable coupon database with pagination - Easy view admin for coupon content and historical usage - Coupon codes can be individually assigned - Import coupon codes from flat file in bulk - Autogenerate unique coupon codes with token - Assign coupon code as a series for affiliate purposes - Global scope or for specific products - Checkout coupons one per order - Instant coupons on product pages, multiple per order - Fixed amount or percentage of eligible products discounting - Specific product eligibility can be scoped to the attribute level - Minimum order level for redemption of checkout coupons - Establish expiration dates - Line item display in basket after redemption - Single use coupons - One per customer coupons - Multiuse coupons (can be limited) - Free shipping coupons - Limit the country, state or zip a coupon can be used for - Combination of free shipping and order discount (% or fixed) coupon - Easy deletion of expired coupons - Coupon report identifies coupon usage
Feature Details. You can add coupons through the standard Miva Merchant admin interface and include usage criteria.
An unlimited number of coupons can be assigned to the store and eachidentified with a coupon code. Once you have added the module to the store, you can add coupons in the Order Fulfillment section of the admininterface. When you select the Add icon, you will have several input fields to fill in. You must enter a unique code for your coupon. Thisis the code that you will give to customers so they can shop and redeemthe coupon. It can be any combination of letters and/or numbers.
You canembed a token in your welcome email or notification emails generated with our Mail Manager (Emporium Plus - Weiland) module. A unique coupon code will be created and is based on the coupon template you designate. You can have an unlimited number of templates and an unlimited number of coupons copied from them. If you are not using our Mail Manager, you can still activate the generator by placing the token in the invoice header. If you are using our Tell A Friend (Emporium Plus - Weiland) module, you can embed the unique coupon code in the emails that customers send when referring their friends to your store. The coupon generation is also useful when it is embedded into the follow on contact emails that our Follow On Contact (Emporium Plus - Weiland) module sends out.
If you have a lot of coupons you want to load into the system quickly,there is a coupon import from flat file module
An optional expiration date can be included which will prevent its useif the date has passed. Enter it in the year, month, day format, eg. 20000724 would be July 24, 2000. If you leave this field blank the coupon will never expire. However, you can still delete it manually through the admin interface.
A fixed value OR percentage discount off the order total is assigned to each coupon. The default is fixed value/price, e.g. $5.00 off the order total. If you put the % sign in the next input field AFTER the value field, it will calculate the coupon value based on the assigned percent of the order total. The %, if used, is entered in the separate field to the right for that purpose. If left blank, the calculation will be based on the fixed value of the coupon. See the note below about restricting discount calculations to specific products instead of the order total. A maximum redemptionvalue can be assigned to each coupon.
Free shipping coupon option. If you enter the letter S in the field to the right of the value field, the coupon will be used to allow free shipping for the entire order. Other criteria for the coupon must be met, e.g. minimum order amount, eligible products, etc.
Optionally, a coupon can be allowed only when an order total reaches a specific amount. For example, you can give a 10% discount when the order total reaches $200 as an incentive or promo. In all cases where a raw value is used, you must make this value equal to or greater than the value of the coupon. If you usethe percent calculation, this value can be any value, including zero.
Based on your state's tax requirements, the coupon can be designated toreduce the sales tax or not reduce it. The coupon's tax effect is onthe order total, not on individual products. For example, in some states, a store coupon reduces the cumulative value of products purchased before the sales tax is applied, hence you would want it to reduce tax. The exception to doingthis is if your products are likely to be non-taxable, making a coupon reduce tax could result in a negative tax calculation. Another type coupon might be the manufacturer coupon. In some states, manufacturer coupons do not decrease the tax liability. You should determine your state's tax requirements before adding coupons to your store.
Coupons can either be used:
multiple times - The coupon can be used at every visit by any customer who shops at your store. This is usually used as a promo to customers,user lists, clubs, etc. They often have a short expiration date to limittheir use. A typical usage might be a special holiday sale, eg 10% offeverything in the store if used by a specified date. This would eliminatethe need for special price groups if the intent is that everybody who hasthe coupon code can use it. In the compiled version you can limit the number of times a multiple coupon is redeemed.
only one time for each customer - The coupon can only be used for one visit per customer. When the same customer shops at your store a secondtime, if he/she uses the same coupon code, it will be rejected. This isprobably the most common coupon and is usually used in print ads or as a promo, eg. "$5.00 off on your next visit".
only one time for a unique coupon code - The coupon can only be used once. Once any customer has used this code, it becomes unavailable for any other purchase. This is often used as a customer relations tool, e.g. "sorry for the inconvenience, please accept this coupon.....".
Global or product related. You can restrict usage of a coupon in your store so that it can be used only if a specific product is ordered. You can list several product codes,any of which in the basket would make the coupon valid if the other requirements are met. Leaving the product code blank means that customers do not have to order a specific product as long as they meet the other requirements the store owner has specified. If you check the box to the left of the product code list, and are using the percentage discount, only those products in the code list will be used in the calculation using the qualifying products subtotal. If you do not check the box, the percentage discount will be applied against the order total. Youcan use a wildcard for the product list, e.g. 1AA* would make all productsbeginning with 1AA eligible for the coupon discount.
Use instant coupons on the individual product pages and for specific products. These coupons are redeemed at the product page and instantly appear in the basket as a line item discount related to a specific product. Unlike the global checkout coupons, customers can redeem multiple instant coupons in a single order. From a marketing standpoint this gives the merchant the opportunity to offer a promo code atthe product level which gives an impending event (expiration of the promo)to encourage sales while not lowering the value of the product with an overtprice discount.
You can restrict the coupon usage down to the attribute level. For example, you can limit the coupon to product codes beginning with 1AA and the attribute "Version" with the specific option value of "4.5". The format for the input would be 1AA*~Version~4.5|
If you precede the product list with a - (minus) character,the coupon will be excluded from use with those products.
You can limit the coupon to be used only if the customer is in a specific zone. You can use ONE of six possible zone limitations for each coupon (ship to: country, state or zip; bill to: country, state or zip).
Appropriate error messages are displayed when coupons don't meet theusage criteria established by the store owner. When the shopper entersa coupon code that is not valid based on the criteria you establish, he/she will see an error message just below the coupon codeinput when the page is re-displayed.
In admin, the coupons can be easily displayed and edited. The couponsare displayed in a table format with configurable number of coupons per page displayed. The entire coupon database is searchable by coupon code or beginning portion of the coupon code.
Expired coupons can be removed from the database (to cut down on disk usage) one at a time or in mass. In admin, you can either put a checkin the remove column and select update or select purge expired coupons, then select update.
A historical database, which can be imported and analyzed in database orspreadsheet software, is maintained on all coupons used. The couponuz.dbfcan be FTPd to your PC for further analysis in MS Access, MS Excel, or other data management software. This could be useful in determining which coupons bring you the most activity. The number of uses for each coupon is also displayed in the admin table.
The coupon usage report module can provide historical data within your admin. You can summarize or list each coupon used for a specific time period. You can also restrict the output to a specific coupon code or a string of characters in a coupon code. This latter is useful when you have assigneda series of coupons to an affiliate or advertising campaign. You can determine how much business was brought in with the coupons from various sources.
The module currently fully supports the mivasql configuration of MIVA Merchant 5. It also supports MySQL as long as load balancing has the data stored on the single MySQL server. This would be the case in most of the server setups. For those that are not, we are in the process of converting the code for that remaining, very small group of MIVA Merchant stores. At this time we have not had a problem. Modules will be moved to the top of the queue as needed.
With Kitmaker, you can combine several related products into a kit and offer them as a group price. You can also combine unrelated products to establish a bundle offering. This product contains both the Kit Maker module and the Strike Thru module.
You simply enter a percentage discount in your admin and Miva Merchant will sum the prices of the individual items, then apply that discount to calculate the new kit price. If you change the price of a kit component, the kit price will be re-calculated when you update the kit assembly in admin AND when the kit product is displayed on the screen=PROD in merchant.
The kit component list can be displayed in the narrative description area on the product screen. You can display it at the beginning or end of the description or leave it off altogether. Each of the kit components is listed as a link to the individual product's screen so that customers can review the full description of each component. Each kit has the option to show or hide the percent savings.
If you want to show the full price as a strike thru you can select in admin to automatically calculate the product cost equal to the original prices of all of the components. Then install the striker.mv module (included with Kit Maker) and it will display a strike thru for all products where the cost exceeds the price, not just those products which are kits.
If using the OpenUI, the code is inserted automatically. If using the MMUI look and feel, two edits are required in the mmui.mv file for Kit Maker and one edit is required if you want to add the Strike Thru capability to your store.
New in the compiled version is compatibility interface with the OpenUI Tokens and Viking Coders product template module. Place the list of kit components on the product page so that it better fits your desired look. The kit component display can either use the default display (store owner does not need to know html) or the template which allows the store owner to rearrange the kit component display with or without thumbnail images.
Limitation: This module does not have inventory management oversight of the individual components for display or decrementing. If your components are such that they may likely be depleted, then you will need to scrutinize sales to
determine when to remove the kit from the shelf.
An example of a product assembled using Kit Maker is at
1AA00102.
The ultimate Miva Merchant autoresponder module - send specialized emails at the completion of the order. These emails are in addition to or in place of the standard emails which are sent at order completion, e.g. merchant notification, customer confirmation, vendor specific notification, and even cell phone emails. It also can send welcome emails when a new customer account is created. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Autoresponder - specialized emails at the completion of the order - Merchant notification and customer confirmation - Vendor and product specific templates - Can limit sending based on a specific attribute/option code for a product - Include coupons or promo codes when specific products ordered - Optionally require an input to allow the email, e.g. a response from Addendum - Easy to use checkbox configuration of vertical or horizontal layout emails - Highly configurable free form template layout emails with embedded tokens - HTML or text email formatting - Archive flat file is created for each template, easily track sales activity - Mail Manager Report module can display the flat file contents by time period or product - Ship to, bill to and other email addresses for each template - Send emails to your company's internal departments, e.g. shipping - Emails to web enabled cell phones as abbreviated messages - Open architecture so that other events can also trigger an automated response - Can resend emails when the customer knows and enters their order number and email address - Use render token to send an email from any pagein the store - Send a welcome email before the order completes and optionally include a promo code, customer login and password - Include 3rd party data with module tokens, e.g. Addendum responses - Display shipping and payment invoice messages - Create packing slip and label emails - Ship to country address formatted according to the applicable country's postal recommendations - Restrict email to a specified order dollar value range, reward big spending customers with a coupon - Restrict email to a specified list of countries, thus allowing for language specific emails
Feature Details. In admin, you create one or more template emails. Eachtemplate can be different, i.e. what it displays, how the data is oriented on the screen/paper, and what product(s) triggers the autoresponder. Most responses are triggered by the product codes purchased. Some example uses:
Email to any of your drop-ship manufacturers listing the Ship To address and the products to be shipped if using real time creditcard authorization. The module will sort out which drop shippergets which emails, including listing the products to be shipped. Unlike some other vendors' drop ship notification modules, this one only includesthe products belonging to the associated drop shipper. Thus a drop shipper doesnot see the products being supplied to the customer by other drop shippers when the order contains multiple product sources. Youcan still use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processingverified the charge, then forward to the drop shipper. This would savehand entering the order. In addition to the email, an archive flatfile is created which you can use to easily track sales activity related to each of your drop-ship manufacturers.
Email to Ship To or Bill To or both thanking them for a donation to your sponsored charity on your site.
Email to your shipping department listing Ship To addressand products ordered if using real time credit card authorization. Products section can be cut/folded to result in a shipping label with your company address included. If notusing real time authorization, use the pending mailbox technique similarto the drop shipper scenario above.
Email a promo coupon code if a customer purchases a specificproduct or from a list of products
Email service, warranty, shipping and contact information on specific products or product lines
Send an email to your cell phone's inbox when orders are placed in your store (requires a cell phone plan that assigns an email address to your phone).
You own a mall with multiple stores within the mall. Thosestore owners rent the stores from you for a percentage of their gross. Use mail manager as an audit tool to track theirsales. In addition to the autoresponse email, mail manager produces a flat file with order ID, date, product name, product code, quantity, price for each, and price extended. Periodically retrieve that flat file and import into a spreadsheetfor easy analysis.
The included Mail Manager Report module can display the contents of that flat file through admin. It can filter the report by specific timeperiods (daily, weekly, monthly) within reason. The limits of your PC or server may prevent very lengthy reports for excessively long time periods. It can also limit the report to only one product code. Since the templates canbe designed for each vendor, you can create individual vendor flat files with a corresponding report for each vendor.
Literally, you can have a different autoresponder for everyproduct in your store.
However, Mail Manager has a somewhat open architecture sothat other events can also trigger an automated response. For example:
Send a welcome email before the order completes, but afterthe customer completes the registration process (for those thatcreate an account)
Send a thank you for rating a product (using our Rate This system)along with a coupon code for taking the time to do so
You can use the ifvar script or var token in these "other event" emails. For example, generate a unique coupon code with a module token and insert it in the welcome email to give the new customer an incentive to buy now.
Use a render token to send an email from any page in the store. For example, put it on the product page to send a specific email when a specific product's page is viewed by a customer who is logged in. The email goes to their password recovery address (but could be bill to or ship to address). If you want it sent to a hard coded address, e.g. yours to monitor traffic,you would put your email address in the 3rd parameter of the token. The uses of this feature are endless. Send a coupon to entice customers to buy when they visit specific product screens. Tell them about other products related to the one they just viewed.
As you can see, the uses of this Mail Manager are quite diverse. Some of the variable features configured through admin for each template are:
Show or hide any of the data elements
Orient your email either horizontally or vertically
There is also a free form template using an extensive list of tokens and mini-scripts to customize the emails that are sent at the time of order completion. They can vary from mimics of the standard merchant notification and customer confirmation emails to brief order notifications for better acceptance within cell phone emails. The emails can be plain text or HTML formattedemails for better readability. You can change the fonts, colors,layout and even add images to your confirmation and notificationemails. If your shipping and payment modules are configured withinvoice notices, these can be included in the emails with a token. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create packing slip and label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template. In the free form template you canalso set the time so that it can be offset from the server time,thus display for a different time zone in each of your emails.
Customize your email and store's physical address
Designate email recipient, i.e. Ship To and/or Bill To and/or fixed email address
List full or partial Ship To and/or Bill To address
Restrict email to a specified order dollar value range, reward big spending customers with a coupon for their next visit
Restrict email to a specified list of countries, thus allowing for language specific emails
Resend order emails if the customer knows and enters the order number and email which match the actual order. The form for these two data elements can be placed anywhere you can edit the store user interface, e.g. headers, footers, welcome screen.
You can specify the product code and an attribute/option value that must also be met before the email will be sent. This is particularly useful when the emails are used for vendor notification. A certain product might bedrop shipped by two different vendors and the only difference is the selected attribute/option value.
Insert a "require" token that has to be met before the email will be allowed. As example,have a checkbox using Addendum to ask a customer if they want to be added to a list server (mailing list). Then if they check the box, the "yes" response is sent to Mail Manager. The Mail Manager can then generate a specifically formatted email to activate an email address at your list server, if you have one.
Write a different body for each of the email templates you add
List products and prices or just the products without prices
Link the email usage to one or more product codes or entire inventory with wildcard
No need to go to each product to link the email, a copy and paste froma flat text file will add hundreds instantly
I'd be surprised if you find that this capability exists anywhere in any mid-priced shopping cart system. Autoresponders that fill in the blanks are one thing, but this is a store owner, pre-planned autoresponse for a specific product. Within your store, you could have dozens of different responses (individual or grouped) or a wildcard response for all of the products. You can use itto make connections not directly related to sales, yetlinked to a specific sale.
Customer buys a kayak from your store. Tell them about the kayak camp 20 miles from your store and give them the 800number of the guy with the info about a big get together next month.
Customer buys an orchid from you which would lead you to believe he/she may have a specific variety you have been looking for. You autorespond with your want list for your nursery inhopes of finding the needle in a haystack.
As you can see, this list could be endless. Targetted, intelligent autoresponders are designed to increase your store'sbusiness and decrease the amount of time employees spend on sendingout product specific, emails.
The pre-formed templates are easy to configure and do not require programming experience. For the more experienced, you also have the option of using tokens and mini-scripts in free form templates. An example free form template is included with the install documents.
The 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.
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.
Membership SuperMod for Discounts Sales and Membership Rewards
The Membership SuperMod allows you to create Membership Groups in Miva Merchant giving the store owner ways to reward customers through Customer Appreciation Discounts, Sales and Points that can be redeemed for a discount. The storeowner can make various Membership Groups allowing the owner to offer different levels of Membership (and its benefits) depending on the “level of loyalty” of the customer. Customers can be automatically moved from one Membership Group to the next as their purchasing increases. The Membership SuperMod also provides facilities to create special time-based sales for all shoppers in the store.
Key Benefits:
User Interface Independent: Utilizes standard features of Miva Merchant for setting discounts and availability. Can be used with MMUI and OpenUI.
Full automatic control of all Price and Availability Group customer assignments. Membership Groups define a set of price and availability groups that are automatically applied to all members of the Membership Group.
Membership Groups can have a set beginning date, expiration date or specific duration
Configurable to display discounts as a price reduction in the basket and checkout screens so customer is aware of their savings
Basket price adjustments are performed when a user logs in; thus allowing the customer to take advantage of their membership even if they log in after shopping.
Membership and Sales Features:
Time-duration based sales: The store administrator can configure special “Automatic” membership groups that apply to every customer immediately upon login. This is useful for creating special sales periods where all shoppers receive a discount on any or all products in the store
Membership Rewards Program: Provide multiple levels of discounts to customers based on their purchase history. Memberships into discount (price) groups can occur by point accumulation, purchase accumulation, or points spent.
Points Redemption Program: Provide a points redemption program where customers accumulate points based on purchase history, then can receive discounts in the store by redeeming points for discounts.
Exclusive Membership Groups: The storeowner can create membership groups that remove the customer from all other groups as they enter an exclusive group.
Automatic entry into membership groups based on:
Purchase of a specific product
Prior Price or Availability Group membership
Entering Membership Code into the customer account
Automatic removal from membership groups based on:
Allowed duration of a membership
Expiration date of a membership
Entry into an exclusive group
Manual expiration by administrator
Customer benefits:
Receive pre-established discounts at checkout when part of a Membership Group
Accumulate points when making purchases
Redeem accumulated points when making purchases
Receive pre-established discounts and earn/use points even if login to Membership Group during a shopping session
Pay with dollars (in addition to points) if there are not enough points accumulated to cover the cost of the entire order
Storeowner has complete control when creating Membership Groups
Optionally create a “Signup Fee” for the Membership Group
Limit the duration of a Membership Group (in days) – great for running sales!
Manually adjust the number of points in a customer record
Allow or disallow points to be used to pay for tax or shipping
Include Price and Availability Groups in the Membership Group
Track total purchases, discounts, points earned and points spent by customer
Add customers to a group and individually specify their end date within the Membership Group
Determine thresholds for automatic inclusion of a customer in a Membership Group
Product Requirements: The major features of the Membership SuperMod are provided through the standard Miva Merchant API. Thus, this module can be used in any Miva Merchant 4.x store. However, in order to redeem points at checkout and fully customize the module display and layout features, you must be using a UI module that provides templates or tokens- either OpenUI or MMUI with the Copernicus DynamicTemplate Engine. OpenUI users who also have the OpenUI SuperMod can perform additional customizations that are not available when just using OpenUI.
Uncompiled Miva Merchant 4.00-4.13:
OpenUI 4.9+ based stores
MMUI based stores
Miva Merchant 4.14+
OpenUI 4.9+ based stores
MMUI based stores
When the Membership SuperMod is used with Dynamic Templates for MMUI-based stores or with the OpenUI SuperMod for OpenUI-based stores, the storeowner can take advantage of the templates and tokens available in these modules thus allowing the storeowner to tailor the module output to his specific needs.
Sort your payment methods, with your preferred method at the top of the list. You can also restrict payment methods by price group, country ship to or bill to, subtotal range of the products in the order, and categories of products that are in the basket. The payment methods can be displayed as either a select list or radio button grouping. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
>Features: - Sort payment methods in the order you want them - Template with tokens to layout methods as select list or radio button group - Default layout for those who do not have skills with HTML and tokens - Restrict methods by price group - Restrict methods by ship to or bill to country - Restrict methods by subtotal range of the order - Restrict methods based on categories of products that are in the basket - Can have a different configurable message on the order payment and invoice screens. - Can have a configurable message in the notification emails for each payment method using tokens if the email module is compatible with tokens using the syntax %module|payment|html_message%
Feature Details. This module's admin screen auto-lists payment methods which are assigned as payment modules for use by the store. In the case of a payment module which configures payment methods at runtime, e.g. available based on login or assigned availability/price group, the store owner can manually add that method to the ordered list.
In addition to the ability to sort the methods, you can restrict any of the methods to specific price group(s). Each method can have its own list of acceptable or unacceptable price groups. The default displays the methods without regard to price groups.
You can restrict the payment methods to specific countries. You decide whether you will tie it to the ship to or bill to address. Then you can create a list of acceptable or unacceptable countries. The default displays the methods without regard to countries.
You can further restrict payment methods to a specific subtotal range of products. For example, if you did not want to accept checks for product subtotal over $50, you would setup the range for check payments as 0.00 to 50.00. The default displays the methods without regard to order subtotal.
You can also restrict payment methods based on categories of products that are in the basket. Thus, if you have certain categories of products that you do not want to allow a specific payment method, you would enter the category codes into the input. If any of those categories of products were in the basket, the method would be hidden.
Each method can have a different configurable message (text or html) which is displayed using render tokens. This message can be displayed on the order payment screen (the screen after payment method is selected) and on the invoice screen. It can also be in the customer and merchant notification emails if they can implement module tokens in the format %module|paygroup|html_message%. This eliminates the need to install a separate, custom module for checkout messages or rely on the payment module to have the message capability (many do not have it).
The store owner can use the default select list layout or use a template for the layout of the payment options. The template can use either select inputs or radio inputs.
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.
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
Volume pricing at the category level. Easily offer a fixed discount (not percentage) based on the number of items in the basket and the categories those items are in. We also have the corresponding module for an older version of Merchant.
Features: - Discount based on number of items ordered - Set up to 4 tiers of discounts per category group - Can have 8 groups (each containing one or more categories), each with 4 different discount tiers - Category wide, multi-category or store wide discounts - Optionally apply discount after other discounts have lowered the subtotal - Discount shows at checkout as separate line item - Optionally display updated discount in basket prior to checkout - Can use wildcard instead of entering category codes for the group - Can either include or exclude a single price group, e.g. Wholesale, to be able to use the discount
Feature Details: In admin, the store owner configures the trigger levels (number of items needed to activate the discount) and thecorresponding fixed amount off. The store owner can designate 1 - 4 trigger levels so that he/she can vary thediscount based on the number bought. Reward the customer; the more the customer buys, the higher the discount.
The storeowner then includes a list of category codes that willbe used in the calculation. Use this module for category-wide or store-wide fixed discounts. If using store-wide, make sure the discount doesn't exceed the priceof the potentially summed products. If using category-wide,make sure the discount does not exceed the price of the lowestpriced product in the category.
The discount amount will appear during checkout on the screen after the customer has entered their shipping method. You can optionally display the discount in the basket prior to checkout.
In admin you can setup eight separate groups withtheir own four-tiered discount and categories. Hence, if you want to discountone category of products with one set of rules (levels) and another category with a different set of rules, you can now do this. Multiple categories can be assigned to each group. As the basket is scanned, the discount is applied based on each group's rules, then summed together at checkout. You can optionally display the updated discounts prior to checkout in the regular basket screen, recalculating and updating discounts based on changing basket contents.
You can choose one price group, e.g. Wholesale, which is not eligible for the discount since they presumably already benefit from significantly lower prices. Or if you don't want to exclude, you can include the one group. This would be useful if you want to apply a fixed amount off for that price group rather than use Merchant's percent off price group calculations. This would allow you to discount different fixed amounts from different groupings (categories) of products.
You can use the asterisk (*) to replace the category codes. When the module encounters the asterisk instead of category codes, it considers all further products eligible. As example, the asterisk in the first group would make all products in the store eligible for the discount. On the other hand, category codes in the first group would apply the first group rules to those categories. Then if there is an asterisk in the second group, all other products in the store woulduse those discount rules.
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.
1. Use the Cost field to set MSRP and display savings as difference or Percentage. 2. Use a Percent markup over Price to extablish MSRPand display savings as difference or Percentage. 3. Use Price Groups to set discount and display normal price as MSRP and savings the difference between Price and Adjusted Price. * 4. Use both Group Method and Price Methods simultaneously.
* Display MSRP with or without strike through. * Create your own labels for "MSRP", "Savings" and "Your Price". * Font size, color and bold control. * Select screens to display the above information.
Independent and simultaneous control over Flagged Products
Supress Price on Flagged Products
* Designate specific products not to display price. * Replace Price with your message on flagged products. * Replace Price for Flagged Products with HTML link. * Replace Price with Email link (adds Product Code and Name to Subject line.) * Select screens to display the above information. * Supress "Add" and "Buy"Buttons.
Independent and simultaneous control over products with a Price of Zero
* Create your own message to replace "Price". * Email link includes Product Code and Name in Subj Line. * Replace 0.00 Price with an HTML link to another page. * Select screens to display the above information. * Remvoe "Add" and "Buy" buttons.
Forced Login controlled by two methods:
* No Access without Login at all. * Suppress Price, Add to Basket and Buy Buttons. * Place Order without Account suppression optional * Create New Account suppression optional.
The ultimate Miva Merchant autoresponder module - send specialized emails at the completion of the order. These emails are in addition to or in place of the standard emails which are sent at order completion, e.g. merchant notification, customer confirmation and even vendor specific notification.
Features: (some features are only in the compiled version)
- Autoresponder - specialized emails at the completion of the order
- Merchant notification and customer confirmation
- Vendor and product specific templates
- Include coupons or promo codes when specific products ordered
- Easy to use checkbox configuration of vertical or horizontal layout emails
- Highly configurable free form template layout emails with embedded tokens
- HTML or text email formatting
- Archive flat file is created for each template, easily track sales activity
- Mail Manager Report module can display the flat file contents by time period or product
- Ship to, bill to and other email addresses for each template
- Send emails to your company's internal departments, e.g. shipping
- Emails to web enabled cell phones
- Open architecture so that other events can also trigger an automated response
- Send a welcome email before the order completes and include a promo code
- Include 3rd party data with tokens, e.g. Addendum responses
- Display shipping and payment invoice messages
- Create packing slip and label emails
- Ship to country address formatted according to the applicable country's postal recommendations
- Restrict email to a specified order dollar value range, reward big spending customers with a coupon
- Restrict email to a specified list of countries, thus allowing for language specific emails
- MMUI and OpenUI compatible. No editing of the mmui.mv is needed and no OpenUI hook points are used
In admin, you create one or more template emails. Each
template can be different, i.e. what it displays, how the
data is oriented on the screen/paper, and what product(s)
triggers the autoresponder. Most responses are triggered
by the product codes purchased. Some example uses:
Email to any of your
drop-ship manufacturers listing the Ship To
address and the products to be shipped if using real time credit
card authorization. The module will sort out which drop shipper gets which emails, including listing the products to be shipped. You can still use the module if you are not using real time authorization, but you would send the email to your pending mailbox until manual processing verified the charge, then forward to the drop shipper. This would save hand entering the order. In addition to the email, an archive flat file is created which you can use to easily track sales activity related to each of your drop-ship manufacturers.
Email to Ship To or Bill To or both thanking them for
a
donation to your sponsored charity on your site.
Email to
your shipping department listing Ship To address
and products ordered if using real time credit card
authorization. Products section can be torn/folded to
result in a shipping label with your company address included. If not using real time authorization, use the pending mailbox technique similar to the drop shipper scenario above.
Email a
promo coupon code if a customer purchases a specific
product or from a list of products
Email service, warranty, shipping and contact information on
specific products or
product lines
Send an email to your cell phone's text messaging
when orders are placed in your store (requires a cell phone
plan that assigns an email address to your phone)
You own a mall with multiple stores within the mall. Those
store owners rent the stores from you for a percentage of
their gross. Use mail manager as an audit tool to track their
sales. In addition to the autoresponse email, mail manager
produces a flat file with order ID, date, product name,
product code, quantity, price for each, and price extended.
Periodically retrieve that flat file and import into a spreadsheet
for easy analysis.
With compiled Merchant, the included Mail Manager Report
module can display the contents of that flat file
through admin. It can filter the report by specific time
periods (daily, weekly, monthly) within reason. The limits
of your PC or server may prevent very lengthy reports for
excessively long time periods. It can also limit the
report to only one product code. Since the templates can
be designed for each vendor, you can create individual
vendor flat files with a corresponding report for each
vendor.
Literally, you can have a different autoresponder for every
product in your store.
However, Mail Manager has a somewhat open architecture so that other events can also trigger an automated response. For example:
Send a
welcome email before the order completes, but after
the customer completes the registration process (for those that
create an account)
Send a thank you for
rating a product (using our Rate This system)
along with a coupon code for taking the time to do so
Essentially any event in the mmui, oui or even another third party module can trigger an email which you write for the
particular event
You can use the
ifvar script or var token in these "other event" emails. For example, generate a unique
coupon code with a module token and insert it in the welcome email to give the new customer an incentive to buy now. If you don't have an account with us yet, sign up and you'll see how it works.
As you can see, the uses of this Mail Manager are quite
diverse. Some of the variable features configured through
admin for each template are:
In the compiled version is a free form template using an
extensive list of
tokens and mini-scripts to customize the emails that
are sent at the time of order completion. They can vary
from mimics of the standard
merchant notification and customer confirmation emails to brief order notifications for better acceptance within cell
phone emails. The emails can be plain text or HTML formatted emails for better readability. You can change the fonts, colors, layout and even add images to your confirmation and notification emails. You can include data from other 3rd party modules, like Addendum, by using tokens. You can also create label emails with the "ship to" country address formatted according to the applicable country's postal recommendations when using the HTML template.
Customize your email and store's physical address
Designate email recipient, i.e. Ship To and/or Bill To and/or fixed email address
List full or partial Ship To and/or Bill To address
Restrict email to a specified order dollar value range, reward big spending customers with a coupon for their next visit
Restrict email to a specified list of countries, thus allowing for language specific emails
Write a different body for each of the email templates you add
Link to one or more product codes or entire inventory with wildcard
No need to go to each product to link the email, a copy and paste from a flat text file will add hundreds instantly
I'd be surprised if you find that this capability
exists anywhere in any mid-priced shopping cart system.
Autoresponders that fill in the blanks are one thing, but
this is a store owner, pre-planned autoresponse for a
specific product. Within your store, you could have dozens
of different responses (individual or grouped) or a
wildcard response for all of the products. You can use it
to make connections not directly related to sales, yet
linked to a specific sale.
Customer buys a kayak from your store. Tell them about
the kayak camp 20 miles from your store and give them the 800 number of the guy with the info about a big get together next month.
Customer buys an orchid from you which would lead you to believe he/she may have a specific variety you have been looking for. You autorespond with your want list for your nursery in hopes of finding the needle in a haystack.
As you can see, this list could be endless. Targetted,
intelligent autoresponders are designed to increase your store's
business and decrease the amount of time employees spend on sending out product specific, followup emails.
MMUI and OpenUI compatible. No editing of the mmui.mv is needed and no OpenUI hook points are used. Thus, module conflict does not occur. The pre-formed templates are easy to configure and do not require programming experience. In the compiled version of Merchant (4.14 and newer), you
also have the option of using tokens and mini-scripts in free form templates. An example free form template is included with the install documents.
The 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 for 700+ 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.
Features:(some features are only in the compiled version) - 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 (openui hook point or token) 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 (openui token) 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 than category name. This way they can create codes which will put their categories in the order they want. While most may actually coincide with category names being 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. Most stores will sort the products by name. The very quick sort is done storewide with one button click. The storewide sort results in the products being sorted in all of the category screens, the product list screen, and the search screen.
Compiled version additional features: New in the compiled version for Merchant 4.14 and newer, 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 the products 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 the top for more customer visibility. You can also list up to 999 product codes in the order you want them and 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 OpenUI hook points or tokens. You can also elect to count the products in each category. If you do, the counts will be 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 the category tree. It simply shows the previously stored totals. This option cannot be used in stores which use availability groups to hide products from some customers because the totals would show the amounts for all products in each category. The sorter module provides OpenUI hook points to display the products in category total after the category name. To use that option, your store needs to have the OpenUI installed. Alternatively, the module has a token which can be run by other 3rd party modules to report the products in category totals. That method may or may not require the OpenUI, depending on the module which is going to use the token. If you have OpenUI version 4.935 or newer, the Sort Categories and Products link appears in the upper admin menu under the Categories and Products headings.
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.
Allow your customers to enter an offer price for a product that is in your products database. You can also use it for auction high bidder purchases. This module is similar to our External Product Purchase module. The difference is that Override Pricing is best suited for products that are actually in your inventory so the customer sees the product image, description, etc that they are offering/bidding on. With External Product Purchase, the customer is seeing a generic
product page where they enter the product name, ID, offer/bid price, and weight.
The offer or high bid is entered into the text attribute on the product page. The price in the basket reflects that customer entered offer/bid price. The order will then continue as normal. However, you can create a disclaimer that if the offer/bid is not accepted, the order will be cancelled and payment refunded. Consult with an attorney on the best wording for your disclaimer as you would not want to be required to sell at their entered price.
The attribute for the override pricing input can also be modified in admin if you are using the OpenUI. You can select to shorten the input to 10 characters (size) or you can even make it a hidden input. You can also have regular product attributes on the same product page. For example, you may want to have an optional auction ID in case the item is going to be sold in store and/or through auction. The link from the auction win could include the auction ID and it would also pre-filled when clicked.
There are also some examples of links and .htaccess re-write rules for making short url links for typical uses of this module in its online install/usage doc.
Limitation: There are some 3rd party modules which change the price in the basket AFTER the item has already been added to the basket. Most notable are those which re-do all of the prices if a customer is in a price group but forgot to login at the beginning of shopping. If you are going to get one of those modules, make sure it 1) only changes the
price if the basket price and actual product price are the same (which means no special actions had been taken on the price when it was put in the basket initially), 2) it does not make the basket price higher than the current basket price as the Override Price module which controlled the actual addition of the item to the basket should be the module to determine the offer/bid price. If you already have a module which makes those sweeping basket price changes without regard for the module that put the product in the basket, you may want to contact that module's developer to see if they could add the two simple rules above to their logic to reduce module conflict.
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.
Volume pricing at the category level. Easily offer a discount based on the number of items inthe basket and the categories those items are in. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Discount based on number of items ordered - Set up to 4 tiers of discounts per category group - Can have 8 groups (each containing one or more categories), each with 4 different discount tiers - Category wide, multi-category or store wide discounts - Optionally apply discount after other discounts have lowered the subtotal - Discount shows at checkout as separate line item - Optionally display updated discount in basket prior to checkout using render token - Can use wildcard instead of entering category codes for the group - Can exclude a single price group, e.g. Wholesale, from receiving the discount
Feature Details: Thedefault is to calculate product charges in the specifiedcategory(ies) (including attribute charges) to determinethe subtotal to discount. You canoptionally include non-product charges in the calculation.
In admin, the store owner configures the triggerlevels (number of items needed to activate the discount) and thecorresponding percentage off. The store owner candesignate 1 - 4 trigger levels so that he/she can vary thepercentage discount based on the number bought. Reward thecustomer; the more the customer buys, the higher thediscount percentage.
The storeowner then includes a list of category codes that willbe used in the calculation. Use this module forcategory-wide or store-wide discounts.
The discount amount willappear during checkout on the screen after the customer hasentered their shipping method. This allows Merchant toinclude (optionally) any miscellaneous fees or coupons redeemedon the Shipping - Payment selection screen so the subtotal willbe adjusted before the discount.
In admin you can setup eight separate groups withtheir own four-tiered discount and categories. Hence, if you want to discountone category of products with one set of rules (levels) and another categorywith a different set of rules, you can do this. Multiple categories can beassigned to each group. As the basket is scanned, the quantities are subtotaledfor each group. The discount is applied based on each group's rules, then summedtogether at checkout. You can optionally display the updated discounts prior to checkout in the regular basket screen, recalculatingand updating discounts based on changing basket contents.
In admin, you can chooseone price group, e.g. Wholesale, which is not eligible for the discount since theypresumably already benefit from significantly lower prices.
You can use the asterisk(*) to replace the category codes. When the module encounters the asterisk instead ofcategory codes, it considers all further products eligible. As example, the asterisk inthe first group would make all products in the store eligible for the discount. On the other hand,category codes in the first group would apply the first group rules to those categories.Then if there is an asterisk in the second group, all other products in the store woulduse those discount rules.
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 purpose of Power Search is to allow a customer to search one or more fields which are allowed by the store owner. The store owner can choose any fields within the products database and/or the custom product fields (Miva Corp built-in utility module) database to be searchable. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Implements field specific, keyword searching - Uses store morph technology to build templates with version history - Customer selects the fields to search and the sort order they want the results displayed - Search the whole store or limit to one category - Search by all (AND), any (OR), exact phrase, or begins with - Display total found, number of pages, and links to each page when the results exceed one page - Use the same product list layout as original search or alter for your needs - Can limit search to a specific price range - Use in conjunction with the Emporium Plus Tell A Friend module to send searches to a friend - Product page "return to search" link takes customers back to the same search page - View admin log of searched words/phrases for marketing and keyword identification - Maintain compatibility with 3rd party modules which use the MIVA Corp custom product fields - Create pre-defined select list searches on a single field - License per domain/mall
Feature Details. Easily editable templates. The module has five templates which can be used for each section of the search page. The templates have full versionhistory and use standard Merchant 5 template coding for easy update and rollback of changes. Each template is pulled into the location you want it on the search page using a render token. The templates are field selection, category selection,search scope/type, page counter and links, and product list layout.
Search specific fields and sort results. Allow a customer to search one or more fields which are made selectable by the store owner. The store owner can choose, in the admin screen, any fields within the products database or the MIVA Merchant built in custom product fields database to be available. The Power Search module uses a mirror database of your products, custom fields and categories; much like the big search engines use. By creating a mirror before the search is made, many operations to join multiple databases togethercan be avoided, so the customer gets a much faster search. Customers can also sort the results on fields like name, code, price, cost, when they were added to the store, or the default display order the store owner established for productlists. The build of the mirror database goes quite quickly and is a maintenance procedure you will do periodically. The small amount of time you take to build the mirror will save your customers significant amounts of time in their searches vs searches which don't use an optimized mirror database. Buildingthe mirror is not required just because products are added, deleted, or edited; as those processes update the mirror automatically without needing a rebuild. See the install doc for details.
Category selectable. Customers can use the category selector to select just one category to search. The default is to search the whole store. You can use the built in token which lists all categories with one or more products in them oryou can build your own select list of only certain categories.
Multiple search types. The customer can select how they want to search the database. The default is to search for products where all (boolean AND) of the keywords entered are found in the record. The customer can broaden that search so that any (boolean OR) of the words are found in the record. They can search by exact phrase so that the words must appear in thesame order in the record as was entered in the search input. They can also search the fields where the data in the field begins with the search string. This is useful for things like finding all of the products whose NAME begins with a specific letter and allows you to have a list of A-Z links that implement that specific search.
Advanced pagination. The module can display the total number of products found which match the search condition. Additionally, the pagesare numbered, e.g. Page 3 of 20, when results exceed the configurable number of products per page. You can also display alist of page numbers and links to those pages so the customer can jump to the page they want to look at. This pagination is similar to that used in the Emporium Plus Category Manager module.
Product layout template can be customized. In the 'srch' page template, there is a "search results layout". If you are happy with that layout, you can copy and paste the contents of that template into the Power Search module's product layout template. You can then modify the layout in the Power Search admin screen.
Price range searching. While searching the price field might be useful in some cases, a more popular search is price range. Within the searchable fields section, the customer has the option of entering a low and high price to create a range. If left blank, the search will not be filtered by price range.
Tell a friend module interface. If the store is using the Emporium Plus Tell A Friend module, customers can send the search string from Power Search to friends. The link in the email will go to the same page of products that the customer was on when they clicked the Tell A Friend button.
Return to search page link. After going to the product page from a Power Search rendered search, a convenient "return to search" link on the product page can bring the customer back to the original search page.
Search log with admin report. In admin, you can view the log of search words/phrases which your customers have used. This helps you from a marketing standpoint to determine the most sought after products and possibly the need to carry a new product. Additionally, it helps you identify keywords which might be useful to include in the narrative descriptions or the meta tags for search engine submissions and even local searches in your store. As example, while you might have a product called flip flops, customers might be searching for thong sandals (which is the same thing). But if you had not used those words in your description, you may have lost the sale. The log can be purged in the admin screen to reduce its size as desired.
Optimized search of built-in custom product fields. This module does not require that you use a proprietary 3rd party module for the custom product fields. It uses the built-in custom product fields module from MIVA Corp, thereby ensuring compatibility with other 3rd party modules which use those same custom product fields. No need to go down that proprietary datafield path of no return. As example, the Emporium Plus Template Data Feed module can use the built-in custom product fields to populate feeds to just about any search engine and shopping index with those "special" fields those indexes require.
Live examples. We cannot link to our demo Merchant 5 store from MivaCentral so if you'd like to see a couple of the live pages demonstrating searches, please contact us for the link. You can check out the selected field search in our test store which has about 600 products with multiple custom product fields. Try some searches so you can get an idea of search speed.
Pre-defined selectors. The Power Search function can also be used for pre-defined select pulldowns in your store. An example of genre and decade searches are in the lower left column of our test store's storefront screen. It will search a specific field, with store owner pre-defined selections. This same technique can be used for things like manufacturer searches if you have a manufacturer field in your custom product fields.
Liberal licensing. License is for ONE domain/mall. Within that single mall, it can be used in multiple stores without additional licenses.
This module requires that you are using MIVA Engine v5.03 or newer. When you log into admin, you can see which version of the engine is in use in your store.
In the compiled version you can opt to not give the price group an additional discount above the volume pricing. You can even make all or some price groups not eligible for volume
pricing and hide the table from them completely. Customers
must be logged in to identify the price group they are in before
the volume pricing module can disqualify them from volume pricing.
