Found 54 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.
Welcome to the future...the first of many "plug-in" themes (or skins) for Miva Merchant and the OpenUI. The themes come in both a Basic and a Professional version.
The themes comes with all graphics and objects used to instantly change the look of your store. In the Profession version, theobjects are editable (using the OpenDesigner™) and blank buttons and master graphic files areincluded so you can extend the theme as your needs dictate.
The Copernicus CustReturn module provides your customers with the ability to request a product
return via your storefront. The return request can be processed in the Miva Merchant admin and
your customers can view the status of the return request.
Key Benefits Include:
“Return Request” web page for
customers to request returns
Optional configuration to allow
customer to explain reason for
return
Merchant admin screen allows
storefront owner to approve or
disapprove request
Auto-approval available based
on reason for return
Results of approval posted in Return
Request web page for customer
to access. Customer must
have an account to be able to access
this information
Approval/disapproval tracked in
Merchant admin
Example Usage:
A storefront that sells cakes and jelly
beans online accepts returns for jelly
beans that arrive stale at the customer’s
doorstep. It does not accept
returns for the cakes that it sells because
the cakes are baked and shipped
on the same day. They are never stale
since they get shipped over night.
(The storefront owner solved this problem
with the Copernicus Shipping SuperMod!)
Well, the storefront owner
purchased a batch of jelly beans from a
discounted wholesaler (whose name
will not be revealed here!) who sold
him 200 pounds of stale jelly beans!
Through his storefront, he wants to
accept requests for returns and he
wants to automatically approve all returns
due to “stale jelly beans.” He
installs the Copernicus CustReturn
module and immediately he is offering
his customers an easy way to handle
the stale jelly bean problem! He has a
standard returns request form for his
customers to fill out on his website. He
can decide whether to approve or decline
all other returns; but since he
knows about the stale jelly bean problem,
he has configured this return reason
for auto-approval. So he’s in complete
control of the process; yet, expediting
the returns for his customers
who have suffered from the stale jelly
bean shipment.
He also wants to offer store credit so
customers can order a new package of
fresh jelly beans. He’s installed the
CustCredit module to integrated the
returns and customer credit process for
his customers. His customers can
come back to his website to find out
about the approval of their return request
and purchase another package of
jelly beans using their customer credit.
SPECIFICATIONS & TECHNICAL NOTES
When using this module alone, that is,
without any other Copernicus products
from the Customer Service Suite, you
can receive return requests through
the return request screen and approve
or decline the requests through the
Merchant admin. When used with the
other Customer Service Suite modules
from Copernicus, it provides a robust
returns tracking system.
When used in conjunction with the
CustRMA module, you can accept returns
through your website, approve or
decline the return, attach an RMA
tracking number to the return and then
track all communication regarding all
aspects of the RMA through the Merchant
admin.
When used in conjunction with the
CustContact module, your customer
can submit a returns request through
your website in the return request
screen and that request is transferred
into the mini-help desk. All related
communication is tracked through the
Merchant admin.
When used in conjunction with the
CustCredit module, the store owner
can accept a request for a return
through the return request screen, approve or decline the request, and issue
a store credit for the items returned.
The Customer Service Suite of modules,
CustCredit, CustReturn, CustRMA
and CustContact can each be used
separately but are best when used together
as a comprehensive customer
service solution.
The Returns Processing module provides an integrated Returns Processing system for your Miva Merchant store. It provides your customers a contact form where the customer can request a return and then track the progress of that return. Within the Miva Merchant admin, the storeowner can approve or decline a return. For approved returns an RMA number is generated, the returned products are tracked, and the type of credit issued to the customer can be recorded. All of this tracking information for returns requests is provided to the customer in a Return History screen that can be viewed while logged into the store.
Key Benefits Customer Benefits:
“Return Request” web page for customers to request returns
Customer chooses from a drop down list the order number for which the return is requested.
Customer selects the products in the order for which the return is requested.
Customer chooses from a drop down list the reason for the return and can also add comments/message for the storeowner
“Return History” web page for customers to track return process
Customer can return to the storefront to review all progress with the return. (Customer must have an account to access this information)
Storeowner Benefits:
Return Request and Return Request History screens are fully customizable with templates when using Dynamic Templates (MMUI-based stores) or the OpenUI SuperMod (OpenUI-based stores)
Store owner receives an email when a new Return Request is initiated by a customer
Store owner can approve or disapprove return requests
Auto-approval available based on reason for return
If return request is approved, RMA ticket is automatically created to track the return of items from the order
Storeowner can set a restocking fee and/or percent of order fee that is automatically subtracted from the refund given to the customer
Storeowner can edit the RMA number so that it matches internal systems
Storeowner can change and edit the items from the order that are included in the RMA ticket. The system tracks the return items from other RMA numbers, ensuring customers do not receive a refund on the same item more than once.
Storeowner checks off items in the RMA as they arrive back at the store
Storeowner can change the dollar amount of refund/credit for the return
RMA automatically closes when all items have been checked off as received
Once the RMA is closed, the storeowner chooses the type of credit used to reimburse the customer for the returned items from a drop down list.
When used with the Copernicus CustCredit module, the drop down list includes CustCredit as an option for reimbursement. When chosen, store credit is automatically applied to the customer’s account for the amount of the closed RMA.
Product Requirements: Miva Merchant: 4.12+
This product may be used with the following user interfaces:
MMUI
MMUI with Dynamic Templates (provides additional functionality to the module)
OpenUI
OpenUI with OpenUI SuperMod (provides additional functionality to the module)
For installation/upgrade services, please contact Copernicus
Try this product out for FREE on Miva Mia -- send a request to sales@cbstech.com for your free product distribution for use on Miva Mia. Be sure to let us know if you need an uncompiled or compiled version of the module. For more information about Miva Mia, available for FREE download from Miva Corporation, please visit: Miva.com
The CustRMA module provides an administrative interface for handling the returns process. Store
administrators can manage product returns, track RMA numbers, and identify the credit method
for a return. When a returned product is received, the store administrator can check-off the items from the RMA list; once the entire return is received the RMA is automatically closed.
Key Benefits Include:
Select items being returned in the
Store Order page in the Miva
admin
Select the credit method for the
return
An RMA Tracking number is assigned
to those items
This number is used in all returns
communication with customer
Grouped items can be assigned
their own tracking number
Check off the returned items as
they arrive; this closes each RMA
ticket as it’s completed
Example Usage: A store that sells cakes and jelly beans
online accepts returns for jelly beans
that arrive stale at the customer’s
doorstep. It does not accept returns for
the cakes that it sells because the
cakes are baked and shipped on the
same day. They are never stale since
they get shipped over night. (The store
owner solved this problem with the
Copernicus Shipping SuperMod!) Well,
the owner purchased a batch of jelly
beans from a discount wholesaler
(whose name will not be revealed
here!) who sold him 200 pounds of
stale jelly beans!
The store owner is upset by this, and
wants to make it easy for his customers
to return the stale jelly beans. He
also wants to make sure that all of the
packages of jelly beans are returned
before he issues store credit to the
customer. The supplier who shipped
the stale jelly beans will replace the
200 pounds of jelly beans with fresh
jelly beans if all of the stale ones are
returned. Therefore, the storeowner
must meticulously track the return of
all of the packages of stale jelly beans.
He installs the Copernicus RMA Tracking
module and instantly he is tracking
every package of jelly beans that are
returned. He can track each package of
each order, assign RMA Tracking numbers
to assure proper accounting of
each package and knows exactly when
a return is completed. Since he also
wants to please his customers, he has
installed the Copernicus CustCredit
module so that instantly upon closure
of the RMA tracking ticket, the customer
receives store credit for the return
and can purchase new packages
of fresh jelly beans.
SPECIFICATIONS & TECHNICAL NOTES
When using this module alone, that
is, without any other products from the
Customer Service Suite, you create the
returns and inform your customers of
the RMA Tracking number and any updates
throughout the return process.
When used with the CustReturn and
CustContact modules, this becomes a
robust returns tracking system.
When used in conjunction with the
CustReturn module, you can accept
returns through your website, approve
or decline the return, attach an RMA
tracking number to the return and then
track all communication regarding all
aspects of the RMA through the Merchant
admin.
When the CustRMA module is used in
conjunction with the CustContact module,
you can track the communication
regarding the RMA Tracking number
through the mini-help desk. This way,
all communication regarding the return
is documented and can be referenced
as necessary throughout the return
process.
When used in conjunction with the
CustCredit module, the store owner
can track the return and automatically
provide a store credit to the customerupon successful closure of the RMA.
The Customer Service Suite of modules,
CustCredit, CustReturn, CustRMA
and CustContact can each be used
separately but are best when used
together as a comprehensive customer
service solution.
For compiled v4.14-4.23.x stores, this product has been replaced by the OpenUI Advanced, and OpenUI Basic, products...
The OpenUI Look & Feel module replaces your MMUI module and provides central 'hooks' through which module developers may easily add features and performance enhancing solutions without having to reinvent the wheel with each Merchant release.
UDPATED VERSION - NEW AND IMPROVED!
We went all out with this latest release of the OpenUI. We have included the following enhancements:
OpenBatches™ - This simplifies order processing in Miva Merchant like never before. You no longer have to go back and forth between the left-hand tree and right-hand main window. From the right hand main window, searchable lists allow you to search, view, edit, or delete batches. This screen also allows you to view orders within a particular batch via OpenOrders™, shows if you have new orders, and even enables you to create a new batch. This all happens from ONE interface.
OpenOrders™ - Using the main window, you now have a searchable order list that allows you to filter by all orders, only unbatched orders, or by orders within an individual batch. You can further filter by order number, product code, order total range, and by date and time range. From this screen, you can also edit and delete individual orders. Once again, this all happens in ONE interface.
An optional statistics interface that works with both the OpenBatches™ and OpenOrders™can be unlocked with the purchase of an OpenUI Pro license key. Find out your top sellers, revenue generators, sales by the hour and day, and much MORE! Read More Detailed Information!
This additional license key is solely for statistics features and will have NO impact on existing or future OpenUI installations. All stores will continue to function with the same capabilities as before and include the great features listed below.
Shorter URLS for Google - It was recently announced in a newsletter geared toward search engines and Miva Merchant that category and product pages without the store code in the url were being readily indexed by the top search engine in the world, Google. If you only have one store, the OpenUI will automatically remove the store code from all urls in the category tree, product list, search results, and basket contents screen. If you have two stores, your store code will remain in the url.
Example:Instead of merchant.mv?Screen=CTGY&Store_Code=CODE&Category_Code=CATEGORY, it will be: merchant.mv?Screen=CTGY&Category_Code=CATEGORY This applies to compiled stores with the mvc extension as well.
Feature added based on recommendations from JMH Web Services (jmhonline.net). *This information has been updated to reflect new findings from JMH. Google now does not have a problem with the store code.
Category and Product Names First in Title Tags- Miva Merchant and previously the OpenUI put your store name before the category and product names in their respective screens title tag (i.e. Store Name: Category or Product Name). Depending on the length of your store name, your category and product titles may not be appearing in your search engine listings title phrase! With the new and improved OpenUI, your category and product titles will be first in the title tag, resulting in better listings within search engines (i.e.Category or Product Title: Store Name).
Feature added based on recommendations from JMH Web Services (jmhonline.net).
A New (Optional) Interface for the Miva Merchant Navigation Bar (navbar)- You now have better (and more) control over which navigation buttons are displayed, as well as many other features including:
Ability to specify cellpadding and cellspacing of navbar.
Optional navbar background image.
Options to align navbar (i.e. Full, Center, Left, Right).
Ability to change navbar buttons including the logo to space, text, etc.
Token replacement in the Cell "links" can be done using the %VAR(varname )% convention. For example, to include the g.sessionurl, just use "%VAR(g.sessionurl)%". To include the store id, use "%VAR(Stores.d.id)%". Most available variables can be used, but they will all be filtered through the encodeentities() function before they are substituted.
Feature added based on recommendations from Rich Chatfield (customMvDesign.com).
Support for New Attribute Types Built-In- New Attribute Types were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Support for module Order Tabs Built-In- module Order Tabs were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Body and Head Tag Options - You don't need additional modules anymore for these two fields if you use the latest version of the OpenUI! Include javascript, cascading style sheets, meta tags, margin height and width, preload images, and much more. For example:
<Select One> Option for Drop-Down Lists - You can now include Select One as the default prompt for attributes, shipping options, and payment option drop-down lists. The default prompt is also customizable for each one. (i.e i.e <Choose Color>, <Select A Shipping Method>, <Select Payment Method>)
The OpenUI Look & Feel Pro License Key unlocks a special feature of the latest OpenUI module. Once you unlock this feature with your license, you will be able to see the total stats for the orders in one batch, all unbatched orders, or all orders regardless of classification. The stats page gives a total sales summary, and then breaks the total sales down by day-of-the-week and time of day (by the hour) the orders were made. The stats page also lists the top selling products and top revenue generators for the specified parameters. The stats are based on the filtering options you currently have set, allowing you to specify exactly what information you would like to generate. For example, if you are in the customer screen on the OpenOrders™ tab and click on the stats button, you will see the stats of that customer's order only. If you have filtered the orders based on the order total and the date range, then the stats will be based on this filter. The stats button gives you immense flexibility because it allows you to view stats using a single filter or any combination of filters. For example, you can see the top 20 products from those that purchased SOMEPRODUCT, or those that have spent over a designated amount....or use both filters. All these resources are available simply by clicking the stats button, which appears on both the OpenOrders™and OpenBatches™ screens.
This additional license key is solely for the new stats features and will have NO impact on existing or future Open UI installation. All stores will continue to function with the same capabilities as before. You can purchase a key by clicking here.
If you don't know which OpenUI product you need, then THIS IS THE ONE!
The OpenUI Advanced (formerly OpenUI Standard) is ULTIMATE enhancement for your Miva Merchant store! Too many features to even begin to list, and all for a VERY LOW PRICE!! It gives you all of the features you are already used to from OpenUI Look & Feel Basic, and the following addons are include:
And the new OpenUI Turbo (double your OpenTokens speed!)
The OpenUI Look & Feel module replaces your MMUI module and provides central 'hooks' through which module developers may easily add features and performance enhancing solutions without having to reinvent the wheel with each Merchant release.
UDPATED VERSION - NEW AND IMPROVED!
We went all out with this latest release of the OpenUI. We have included the following enhancements:
OpenBatches™ - This simplifies order processing in Miva Merchant like never before. You no longer have to go back and forth between the left-hand tree and right-hand main window. From the right hand main window, searchable lists allow you to search, view, edit, or delete batches. This screen also allows you to view orders within a particular batch via OpenOrders™, shows if you have new orders, and even enables you to create a new batch. This all happens from ONE interface.
OpenOrders™ - Using the main window, you now have a searchable order list that allows you to filter by all orders, only unbatched orders, or by orders within an individual batch. You can further filter by order number, product code, order total range, and by date and time range. From this screen, you can also edit and delete individual orders. Once again, this all happens in ONE interface.
An optional statistics interface that works with both the OpenBatches™ and OpenOrders™can be unlocked with the purchase of an OpenUI Pro license key. Find out your top sellers, revenue generators, sales by the hour and day, and much MORE! Read More Detailed Information!
This additional license key is solely for statistics features and will have NO impact on existing or future OpenUI installations. All stores will continue to function with the same capabilities as before and include the great features listed below.
Shorter URLS for Google - It was recently announced in a newsletter geared toward search engines and Miva Merchant that category and product pages without the store code in the url were being readily indexed by the top search engine in the world, Google. If you only have one store, the OpenUI will automatically remove the store code from all urls in the category tree, product list, search results, and basket contents screen. If you have two stores, your store code will remain in the url.
Example:Instead of merchant.mv?Screen=CTGY&Store_Code=CODE&Category_Code=CATEGORY, it will be: merchant.mv?Screen=CTGY&Category_Code=CATEGORY This applies to compiled stores with the mvc extension as well.
Feature added based on recommendations from JMH Web Services (jmhonline.net). *This information has been updated to reflect new findings from JMH. Google now does not have a problem with the store code.
Category and Product Names First in Title Tags- Miva Merchant and previously the OpenUI put your store name before the category and product names in their respective screens title tag (i.e. Store Name: Category or Product Name). Depending on the length of your store name, your category and product titles may not be appearing in your search engine listings title phrase! With the new and improved OpenUI, your category and product titles will be first in the title tag, resulting in better listings within search engines (i.e.Category or Product Title: Store Name).
Feature added based on recommendations from JMH Web Services (jmhonline.net).
A New (Optional) Interface for the Miva Merchant Navigation Bar (navbar)- You now have better (and more) control over which navigation buttons are displayed, as well as many other features including:
Ability to specify cellpadding and cellspacing of navbar.
Optional navbar background image.
Options to align navbar (i.e. Full, Center, Left, Right).
Ability to change navbar buttons including the logo to space, text, etc.
Token replacement in the Cell "links" can be done using the %VAR(varname )% convention. For example, to include the g.sessionurl, just use "%VAR(g.sessionurl)%". To include the store id, use "%VAR(Stores.d.id)%". Most available variables can be used, but they will all be filtered through the encodeentities() function before they are substituted.
Feature added based on recommendations from Rich Chatfield (customMvDesign.com).
Support for New Attribute Types Built-In- New Attribute Types were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Support for module Order Tabs Built-In- module Order Tabs were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Body and Head Tag Options - You don't need additional modules anymore for these two fields if you use the latest version of the OpenUI! Include javascript, cascading style sheets, meta tags, margin height and width, preload images, and much more. For example:
<Select One> Option for Drop-Down Lists - You can now include Select One as the default prompt for attributes, shipping options, and payment option drop-down lists. The default prompt is also customizable for each one. (i.e i.e <Choose Color>, <Select A Shipping Method>, <Select Payment Method>)
The OpenUI Look & Feel Pro License Key unlocks a special feature of the latest OpenUI module. Once you unlock this feature with your license, you will be able to see the total stats for the orders in one batch, all unbatched orders, or all orders regardless of classification. The stats page gives a total sales summary, and then breaks the total sales down by day-of-the-week and time of day (by the hour) the orders were made. The stats page also lists the top selling products and top revenue generators for the specified parameters. The stats are based on the filtering options you currently have set, allowing you to specify exactly what information you would like to generate. For example, if you are in the customer screen on the OpenOrders™ tab and click on the stats button, you will see the stats of that customer's order only. If you have filtered the orders based on the order total and the date range, then the stats will be based on this filter. The stats button gives you immense flexibility because it allows you to view stats using a single filter or any combination of filters. For example, you can see the top 20 products from those that purchased SOMEPRODUCT, or those that have spent over a designated amount....or use both filters. All these resources are available simply by clicking the stats button, which appears on both the OpenOrders™and OpenBatches™ screens.
This additional license key is solely for the new stats features and will have NO impact on existing or future Open UI installation. All stores will continue to function with the same capabilities as before. You can purchase a key by clicking here.
The OpenUI Look & Feel Basic...this is the low-cost, entry-level OpenUI Look & Feel product that is required for running the many 3rd Party Modules currently available. (formerly OpenUI Standard)
It can be enhanced with OpenUI addons, such as the following:
And the new OpenUI Turbo (double your OpenTokens speed!)
The OpenUI Look & Feel module replaces your MMUI module and provides central 'hooks' through which module developers may easily add features and performance enhancing solutions without having to reinvent the wheel with each Merchant release.
UDPATED VERSION - NEW AND IMPROVED!
We went all out with this latest release of the OpenUI. We have included the following enhancements:
OpenBatches™ - This simplifies order processing in Miva Merchant like never before. You no longer have to go back and forth between the left-hand tree and right-hand main window. From the right hand main window, searchable lists allow you to search, view, edit, or delete batches. This screen also allows you to view orders within a particular batch via OpenOrders™, shows if you have new orders, and even enables you to create a new batch. This all happens from ONE interface.
OpenOrders™ - Using the main window, you now have a searchable order list that allows you to filter by all orders, only unbatched orders, or by orders within an individual batch. You can further filter by order number, product code, order total range, and by date and time range. From this screen, you can also edit and delete individual orders. Once again, this all happens in ONE interface.
An optional statistics interface that works with both the OpenBatches™ and OpenOrders™can be unlocked with the purchase of an OpenUI Pro license key. Find out your top sellers, revenue generators, sales by the hour and day, and much MORE! Read More Detailed Information!
This additional license key is solely for statistics features and will have NO impact on existing or future OpenUI installations. All stores will continue to function with the same capabilities as before and include the great features listed below.
Shorter URLS for Google - It was recently announced in a newsletter geared toward search engines and Miva Merchant that category and product pages without the store code in the url were being readily indexed by the top search engine in the world, Google. If you only have one store, the OpenUI will automatically remove the store code from all urls in the category tree, product list, search results, and basket contents screen. If you have two stores, your store code will remain in the url.
Example:Instead of merchant.mv?Screen=CTGY&Store_Code=CODE&Category_Code=CATEGORY, it will be: merchant.mv?Screen=CTGY&Category_Code=CATEGORY This applies to compiled stores with the mvc extension as well.
Feature added based on recommendations from JMH Web Services (jmhonline.net). *This information has been updated to reflect new findings from JMH. Google now does not have a problem with the store code.
Category and Product Names First in Title Tags- Miva Merchant and previously the OpenUI put your store name before the category and product names in their respective screens title tag (i.e. Store Name: Category or Product Name). Depending on the length of your store name, your category and product titles may not be appearing in your search engine listings title phrase! With the new and improved OpenUI, your category and product titles will be first in the title tag, resulting in better listings within search engines (i.e.Category or Product Title: Store Name).
Feature added based on recommendations from JMH Web Services (jmhonline.net).
A New (Optional) Interface for the Miva Merchant Navigation Bar (navbar)- You now have better (and more) control over which navigation buttons are displayed, as well as many other features including:
Ability to specify cellpadding and cellspacing of navbar.
Optional navbar background image.
Options to align navbar (i.e. Full, Center, Left, Right).
Ability to change navbar buttons including the logo to space, text, etc.
Token replacement in the Cell "links" can be done using the %VAR(varname )% convention. For example, to include the g.sessionurl, just use "%VAR(g.sessionurl)%". To include the store id, use "%VAR(Stores.d.id)%". Most available variables can be used, but they will all be filtered through the encodeentities() function before they are substituted.
Feature added based on recommendations from Rich Chatfield (customMvDesign.com).
Support for New Attribute Types Built-In- New Attribute Types were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Support for module Order Tabs Built-In- module Order Tabs were previously only supported in the uncompiled versions of Miva Merchant, but will now be in both the compiled and uncompiled versions, and will not require the Admin Extension installation.
Body and Head Tag Options - You don't need additional modules anymore for these two fields if you use the latest version of the OpenUI! Include javascript, cascading style sheets, meta tags, margin height and width, preload images, and much more. For example:
<Select One> Option for Drop-Down Lists - You can now include Select One as the default prompt for attributes, shipping options, and payment option drop-down lists. The default prompt is also customizable for each one. (i.e i.e <Choose Color>, <Select A Shipping Method>, <Select Payment Method>)
The OpenUI Look & Feel Pro License Key unlocks a special feature of the latest OpenUI module. Once you unlock this feature with your license, you will be able to see the total stats for the orders in one batch, all unbatched orders, or all orders regardless of classification. The stats page gives a total sales summary, and then breaks the total sales down by day-of-the-week and time of day (by the hour) the orders were made. The stats page also lists the top selling products and top revenue generators for the specified parameters. The stats are based on the filtering options you currently have set, allowing you to specify exactly what information you would like to generate. For example, if you are in the customer screen on the OpenOrders™ tab and click on the stats button, you will see the stats of that customer's order only. If you have filtered the orders based on the order total and the date range, then the stats will be based on this filter. The stats button gives you immense flexibility because it allows you to view stats using a single filter or any combination of filters. For example, you can see the top 20 products from those that purchased SOMEPRODUCT, or those that have spent over a designated amount....or use both filters. All these resources are available simply by clicking the stats button, which appears on both the OpenOrders™and OpenBatches™ screens.
This additional license key is solely for the new stats features and will have NO impact on existing or future Open UI installation. All stores will continue to function with the same capabilities as before. You can purchase a key by clicking here.
This module allows you to specify a "return URL" to be able to (for example) add products to your basket from a static page, and then return to that static page.
The StatCat module is both an admin module and a basket interface module. The primary purpose of StatCat is to generate static catalog pages (indexes and sub-pages) directly from your Miva Merchant products and category databases so that search engines will add your pages to their index. Presumably this will allow customers to find your store amongst the millions of web sites on the Internet. As such, the pages generated are basic html pages with links to sub-pages, basket page and individual product pages in your Miva Merchant system. Each page contains your store title, meta description, meta keywords, footers along with the products. Category pages also contain category headers and footers.
Although these are static html pages, they have direct links which allow customers to add the products to their basket which is maintained in your Miva Merchant shopping cart system. If you are using the CIM Inventory Manager or Miva Corp's new Inventory Manager (in Merchant 4.x), it will even check the stock level and return an out of stock message if stock level is depleted
** Caution: If you are using Merchant 4.0 and its Inventory Management system that deducts products from inventory when they are placed in the basket, you should select to NOT use the Add to Basket buttons if you have one-of-a-kind items. The reason for this is that some robots and other indexing software may even follow links which contain the ? and & characters. This could result in the stock level decrementing to zero and out-of-stock emails being sent. The products won't be removed from inventory completely, as they will be re-stocked when you run the Admin:Delete Expired Shopping Baskets. This undesirable situation does not exist in Merchant versions 2.x or 3.x. It is also not a problem in Merchant 4.x if your store does not use the Miva Corp Inventory Management or your product stock levels are not likely to be depleted with one or two passes of the indexing program.
The store owner determines which page the customer will go to when they select to add a product to the basket. They can be taken either to the basket for review or back to the static page they just selected from. Both processes are automatic and do not require Javascript or meta refresh routines. Either click through destination can be used on either of the sort options, store owner choice. In addition to the functionality of this module, it provides an excellent example of how to interface static pages with the Miva Merchant system with return to the correct static page.
Quick links on each sub-page allow the customer to return to the index or go straight to their basket for review and checkout.
Below the sub-pages the store owner can even generate individual product pages. These product pages contain the full sized image and description. If the store uses the Flexible Product Description module and the product record contains a Keyword field, those product specific keywords are added to the store's generic keywords which are already in all of the static pages.
The store owner can decide whether to display the price for each item on the static pages. Since these pages are static and cannot function interactively to determine customer price groups or discounts, the hide price routine has its place. However, if the store has no price groups and discounts are calculated on basket totals or discount coupons, the price listing is useful.
The static pages also have no way to restrict access. So if your store is one which does not allow certain products to be shown to all customers, then this module is not for you, unless you can place all of those restricted products in specific categories. In which case, you could then sort pages by category and simply delete those categories' pages.
This module is for Miva Merchant 2.x, 3.x and 4.x. It works with both the Miva Merchant look and feel (mmui.mv) and the OpenUI look and feel (oui.mv). If using the mmui.mv, there are two edits that need to be made to the mmui.mv file.
StatCat produces pages similar (mirror) to the layout in Miva Merchant with admin control. The following configuration settings are made within the standard Miva Merchant admin interface: Page title, home URL, optional title/store logo, title background color, title foreground color, category title header size, number of product columns on the category sort page, Meta description of the site, Meta keywords on the site, return action after adding a product to the basket, option to hide the prices, category column background color, category column foreground color, category column font, category column size, product background color in the category sorted pages, product foreground color in the category sorted pages, product font and size in the category sorted pages, optional display of thumbnail images in the category sorted pages, store front page welcome screen, search button input, product descriptions on category pages, and page footer.
Once generated, the index pages can be linked to your main home page. The catalog can be left in the directory it is generated in or copied to any web site (or multiple web sites) to increase search engine visibility. The links to images and back to your Merchant.mv store will work across servers. An example of this remote distribution can be seen at my Yahoo/Simplenet web site. The limitation to the remote distribution is that these remote static pages are one way, ie. placing a product in the basket will take the customer to the main Merchant.mv, but not back to the remote static page. They would then continue shopping in Merchant.mv. This limitation exists only if the static pages are not in their original catalog directory. If they are in the catalog directory on the local server with Merchant.mv, then return to the static pages is one of your options in admin.
The StatCat also has the ability to generate static pages which can be placed on a disk and used as a catalog which can be mailed or given out to potential customers. When using this option, links to your web site or the shopping cart are suppressed. An example of this type of catalog can be seen online. It has no links to the cart and the images are virtual to the static html pages.
When generating the catalog, the store owner has the option of restricting the html output to a list of specific categories. This is particularly useful when the store owner wants to place their static pages on remote servers which have specific themes in a mall environment. Some categories may "fit in" and some may not. This also might be useful if you want to create disks with only certain categories of products on them to be given to customers.
Note 1: StatCat uses the first letter of the product name to name the sub-pages. If you use illegal characters for the first letter of product names, you will not be able to generate the by-name catalog. An example would be the left bracket, as some might have put the font tag at the beginning of the product name. If that is the case, use the by-category catalog.
Note 2: If you have an excessively large products database, you will probably not be able to run StatCat on a server without timing out. However, you should be able to run it in MivaMia if you have a mirror of your store on your PC. You would then need to upload the static pages manually. This store of 600 products took about 5 seconds to generate the category pages.
Click through returns to the originating static page after addition (alternatively you can have it remain at the merchant.mv basket)
This example contains StatCat generated individual product pages
Several new features have been added to the compiled version; background image, functional navigation bar, "smart" metatags, extensive implementation of keyword and header and footer usage, product page names can be product code or name ending with html, inclusion of product links at the top or bottom listed as featured products or similar designation, include any fields in the products database on product pages (including modified structure), optionally hide subcategories on category pages as applicable, additional product page links such as "check availability or latest prices", and export to any directory within the store's path (creates directory if it does not exist). Discontinued (inactive) products can continue to have modified static pages generated so that search engine links remain viable, yet do not result in errors when linked to the store. Additionally, affiliate codes can be included with every link so that the static catalog pages can be given to affiliates who wish to mirror your catalog at their site. If you are using the OpenUI, StatCat adds "smart" metatags to your merchant.mv so that when the customers (and search engines) click from your static pages to your actual store, the pages will contain metatags related to category headers, product descriptions and product keywords (if used). It also reverses the title tag with the category and product screens so that the category or product name appear first, then the store name. If your store has our Volume Pricing module version (4.53 or higher) installed, StatCat can optionally include the volume price table on the static pages. When creating the static product pages, a flat file is created in the background which can be used for a data feed file for submission to FroogleTM. It contains the header and data for the basic file format.
This module saves the last static URL that your shopper came from, and adds a "Continue Shopping" button to the Basket Contents page which returns the shopper to that last static page.
Give your customers better control of the basket contents page and improve their shopping experience. This module provides a smart "continue shopping", "empty basket" and "checkout" buttons. Continue shopping button will automatically return the shopper to the last visited product, category, search or product list display screens. All display options are configurable using the menu-driven admin interface and modified basket contents page template, which is automatically installed and configured with this module. Menu driven module configuration allows you to customize your buttons and control which of the merchant pages the customer can return to. This gives you full control over the look and feel of your this new functionality. The module can also be used to add Continue Shopping functionality to other Merchant pages.
The ADS Continue Shopping Module Features:
This module will monitor where the customer came from, prior to visiting the basket page. Then return the customer to that page, even if the customer was on page "X" of the Category, Search or Product List pages. The page tracking is configured using the menu driven selection of "PROD, CTGY, PLST and SRCH" pages. The Empty Basket and Checkout buttons will not display if the basket is empty.
Simple Module Installation and Configuration
Automatic installation and assignment of BASK page required item.
Automatic modification of currently used BASK page template. Previous template versions will be available through version history.
Menu-driven control of new features. No template editing required, but is available for advanced users.
Menu Driven Control of module features
Select Text or Image buttons for Continue Shopping, Empty Basket and Checkout buttons
Upload new Image buttons using the interface. No FTP access required.
Select which of the Merchant pages Continue Shopping button will return the shopper to.
Additional layout modifications can be made using BASK Page template that is pre-installed with this module
Module installation and functionality has the following requirements:
MIVA Merchant Version 5.0
Settings and control this module provides are used in conjunction with BASK Page template that is pre-installed with this module.
The purpose of Power Search is to allow a customer to search one or more fields which are allowed by the store owner. The store owner can choose any fields within the products database and/or the custom product fields (Miva Corp built-in utility module) database to be searchable. This module is for MIVA Merchant 5.x. We also have the corresponding module for an older version of Merchant.
Features: - Implements field specific, keyword searching - Uses store morph technology to build templates with version history - Customer selects the fields to search and the sort order they want the results displayed - Search the whole store or limit to one category - Search by all (AND), any (OR), exact phrase, or begins with - Display total found, number of pages, and links to each page when the results exceed one page - Use the same product list layout as original search or alter for your needs - Can limit search to a specific price range - Use in conjunction with the Emporium Plus Tell A Friend module to send searches to a friend - Product page "return to search" link takes customers back to the same search page - View admin log of searched words/phrases for marketing and keyword identification - Maintain compatibility with 3rd party modules which use the MIVA Corp custom product fields - Create pre-defined select list searches on a single field - License per domain/mall
Feature Details. Easily editable templates. The module has five templates which can be used for each section of the search page. The templates have full versionhistory and use standard Merchant 5 template coding for easy update and rollback of changes. Each template is pulled into the location you want it on the search page using a render token. The templates are field selection, category selection,search scope/type, page counter and links, and product list layout.
Search specific fields and sort results. Allow a customer to search one or more fields which are made selectable by the store owner. The store owner can choose, in the admin screen, any fields within the products database or the MIVA Merchant built in custom product fields database to be available. The Power Search module uses a mirror database of your products, custom fields and categories; much like the big search engines use. By creating a mirror before the search is made, many operations to join multiple databases togethercan be avoided, so the customer gets a much faster search. Customers can also sort the results on fields like name, code, price, cost, when they were added to the store, or the default display order the store owner established for productlists. The build of the mirror database goes quite quickly and is a maintenance procedure you will do periodically. The small amount of time you take to build the mirror will save your customers significant amounts of time in their searches vs searches which don't use an optimized mirror database. Buildingthe mirror is not required just because products are added, deleted, or edited; as those processes update the mirror automatically without needing a rebuild. See the install doc for details.
Category selectable. Customers can use the category selector to select just one category to search. The default is to search the whole store. You can use the built in token which lists all categories with one or more products in them oryou can build your own select list of only certain categories.
Multiple search types. The customer can select how they want to search the database. The default is to search for products where all (boolean AND) of the keywords entered are found in the record. The customer can broaden that search so that any (boolean OR) of the words are found in the record. They can search by exact phrase so that the words must appear in thesame order in the record as was entered in the search input. They can also search the fields where the data in the field begins with the search string. This is useful for things like finding all of the products whose NAME begins with a specific letter and allows you to have a list of A-Z links that implement that specific search.
Advanced pagination. The module can display the total number of products found which match the search condition. Additionally, the pagesare numbered, e.g. Page 3 of 20, when results exceed the configurable number of products per page. You can also display alist of page numbers and links to those pages so the customer can jump to the page they want to look at. This pagination is similar to that used in the Emporium Plus Category Manager module.
Product layout template can be customized. In the 'srch' page template, there is a "search results layout". If you are happy with that layout, you can copy and paste the contents of that template into the Power Search module's product layout template. You can then modify the layout in the Power Search admin screen.
Price range searching. While searching the price field might be useful in some cases, a more popular search is price range. Within the searchable fields section, the customer has the option of entering a low and high price to create a range. If left blank, the search will not be filtered by price range.
Tell a friend module interface. If the store is using the Emporium Plus Tell A Friend module, customers can send the search string from Power Search to friends. The link in the email will go to the same page of products that the customer was on when they clicked the Tell A Friend button.
Return to search page link. After going to the product page from a Power Search rendered search, a convenient "return to search" link on the product page can bring the customer back to the original search page.
Search log with admin report. In admin, you can view the log of search words/phrases which your customers have used. This helps you from a marketing standpoint to determine the most sought after products and possibly the need to carry a new product. Additionally, it helps you identify keywords which might be useful to include in the narrative descriptions or the meta tags for search engine submissions and even local searches in your store. As example, while you might have a product called flip flops, customers might be searching for thong sandals (which is the same thing). But if you had not used those words in your description, you may have lost the sale. The log can be purged in the admin screen to reduce its size as desired.
Optimized search of built-in custom product fields. This module does not require that you use a proprietary 3rd party module for the custom product fields. It uses the built-in custom product fields module from MIVA Corp, thereby ensuring compatibility with other 3rd party modules which use those same custom product fields. No need to go down that proprietary datafield path of no return. As example, the Emporium Plus Template Data Feed module can use the built-in custom product fields to populate feeds to just about any search engine and shopping index with those "special" fields those indexes require.
Live examples. We cannot link to our demo Merchant 5 store from MivaCentral so if you'd like to see a couple of the live pages demonstrating searches, please contact us for the link. You can check out the selected field search in our test store which has about 600 products with multiple custom product fields. Try some searches so you can get an idea of search speed.
Pre-defined selectors. The Power Search function can also be used for pre-defined select pulldowns in your store. An example of genre and decade searches are in the lower left column of our test store's storefront screen. It will search a specific field, with store owner pre-defined selections. This same technique can be used for things like manufacturer searches if you have a manufacturer field in your custom product fields.
Liberal licensing. License is for ONE domain/mall. Within that single mall, it can be used in multiple stores without additional licenses.
This module requires that you are using MIVA Engine v5.03 or newer. When you log into admin, you can see which version of the engine is in use in your store.
The Basket Wizard Pro is a versatile module designed to give you control over the layout of theBasket Display screen and add increased use and functionality to this screen.
Users of the Basket Wizard will find increased functionality in this Pro version.
Key Features include:
Thumbnail Image
Continue Shopping returns to Last Multiple Product Page.
Display New, Special or Discounted Items.
Plus, you can:
Add Thumbnail Image and Link.
Add Category Tree.
Suppress “Remove”, “Product Code” or “Update Quantity”.
Link the Product Name.
Create “Continue Shopping” and “Continue Checkout” links below the basket, choose the screen to terminate “Continue Checkout” and choose one of the following methods for terminating “Continue Shopping” (to return to a specified screen, return to a specified HTML page, or return to the last page viewed that contained multiple products.
You can also add a “Last Chance Specials” dsiplay of products below the Basket Display. Set up your own display of products to offer your customers before they check out using either a multi-column Expanded Layout or Line Layout. Either display is fully configurable in Admin.
Screenshot of admin
The CustCredit module allows you to offer store credit to your customer for returned items. The credit is tracked with the customer’s account and is automatically applied to the next purchase when the customer checks out, simplifying your returns process and minimizing credit card charges for refunds.
Key Benefits Include:
Customer Store Credit page in the
Miva admin
Storefront owner enters store
credit into customer’s account
Optional area to track reason for
credit
Refund credit displayed in Edit
Customer Account screen when
customer logs into storefront
Refund automatically applied to
customer’s basket as he checks
out
Refund amount available to customer
until it is depleted by purchases
Example Usage: A storefront that sells cakes and jelly
beans online accepts returns for jelly
beans that arrive stale at the customer’s
doorstep. It does not accept
returns for the cakes that it sells because
the cakes are baked and shipped
on the same day. They are never stale
since they get shipped over night.
(The storefront owner solved this problem
with the Copernicus Shipping SuperMod!)
Well, the storefront owner purchased a
batch of jelly beans from a discounted
wholesaler (whose name will not be
revealed here!) who sold him 200
pounds of stale jelly beans! The storefront
owner did not know that he was
sold stale jelly beans and now all of his
customers are receiving stale jelly
beans!! This is a storefront owner’s
nightmare!
The storefront owner wants to issue
store credit to his customers rather
than refund the money for the stale
jelly beans. He wants his customers to
be able to come back to his storefront
and place new orders that allow them
to access the store credit they received
as a result of the stale jelly beans.
Therefore, the storefront owner invests
in the Copernicus CustCredit module
and can customize his storefront to
offer store credit for returns.
Thus solving his returns problem.....if
only that wholesaler would take the
stale jelly beans back.......
SPECIFICATIONS & TECHNICAL NOTES
Please note this module requires OpenUI v.4.53 (uncompiled) with the Admin Extensions installed, or OpenUI v.4.71 (compiled).
When used alone, that is, without the Copernicus Returns Processing system, you must manually enter the credit information from your customers. When used in conjunction with our Returns Processing system, you can provide store credit automatically as a method of refunding your customer for a return.
Paypal is a well-established online instant payment service. Paypal allows individuals and small businesses to avoid the expense involved in setting up and maintaining a Merchant account. (Average fees for a Merchant account seem to range around $200 in set up fees, and $15-20/month in gateway fees--with Paypal you'll only pay the transaction fees, which are about the same as most credit card processors charge.) Besides credit card transactions, Paypal is also a convenient way to send money via email, and it is widely used at sites such as eBay where it accounts for 53% of transactions.
This module permits you to use PayPal Web Accept to process payments in your Miva Merchant store. Your customers will be taken to the PayPal site to transfer the money for the purchase to your account. They will then be returned to your store's Invoice page (assuming that the transfer was successfully made. It also provides the ability to verify the transaction with PayPal's records from within admin.
Unlike most off-site payment modules (those payment modules which require your customer to leave Merchant to process the payment), this module takes advantage of advanced features offered by PayPal to assure that a record of the purchase is made in Merchant as soon as the money is transfered! In many other such modules, if something goes wrong and the customer does not return to Merchant no record is made of the order; even though the money was transfered to your account! That won't happen with this module. The customer does not need to return to the invoice screen for Merchant to make a record of the sale.
Gives you the ability to track messages from your customers, handle return requests, process RMA #'s and issue store credits to your customers...and track all of the details in between!
The NetPush Advanced Inventory Module allows Miva Merchant store owners to track inventory within Miva Merchant all the way down to the attribute/option level. The module has numerous configuration settings that should allow the admin to display and tr
Several new features have been added to the compiled version; background image, functional navigation bar, "smart" metatags, extensive implementation of keyword and header and footer usage, product page names can be product code or name ending with html, inclusion of product links at the top or bottom listed as featured products or similar designation, include any fields in the products database on product pages (including modified structure), optionally hide subcategories on category pages as applicable, additional product page links such as "check availability or latest prices", and export to any directory within the store's path (creates directory if it does not exist). Discontinued (inactive) products can continue to have modified static pages generated so that search engine links remain viable, yet do not result in errors when linked to the store. Additionally, affiliate codes can be included with every link so that the static catalog pages can be given to affiliates who wish to mirror your catalog at their site. If you are using the OpenUI, StatCat adds "smart" metatags to your merchant.mv so that when the customers (and search engines) click from your static pages to your actual store, the pages will contain metatags related to category headers, product descriptions and product keywords (if used). It also reverses the title tag with the category and product screens so that the category or product name appear first, then the store name. If your store has our Volume Pricing module version (4.53 or higher) installed, StatCat can optionally include the volume price table on the static pages. When creating the static product pages, a flat file is created in the background which can be used for a data feed file for submission to FroogleTM. It contains the header and data for the basic file format. 