Found 29 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.
Add OpenTokens™ support to your non-Miva Merchant MivaScript application. Make your screens, emails, reports, etc., completely configurable by your clients thru an easy to use API...with no royalties or per-client costs!
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
Display a customizable, interactive agreement page during checkout. Design your own agreement page with accept/decline buttons to continue or abort checkout. Ideal for customer acceptance of storefront payment, order, policy, etc terms.
Show/hide category tree and right column
Page title
Disagree/decline button redirection to storefrontwelcome page or your own desired URL
Option to exclude or include specific products to display agreement page
Choice to display agreement page after customer info or shipping/payment selection page
Agreement page content with available tokens for agree/decline buttons. Supports OpenTokens for parsing OUI tokens.
Option to display unformatted agreeement text on invoice page and customer/merchant order confirmation emails. Supports OpenTokens for parsing OUI tokens.
Accept/decline buttons configurable with desired text or image
Notes: 1) This module requires Miva Engine v3.9 or higher. 2) Supports OpenTokens
Version 4.23
Access to the store can be restricted, requiring customers to login to a standard account or an approved account. 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.
Four Optional Levels of Access Restriction:
Login Required at Storefront
Login Required to View Products
Login & Approved Account Required at Storefront
Login & Approved Account Required to View Products
Features:
Required 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
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.
Ultimate Feed Generator is a tool for generating product feeds, sitemaps, and more. It can be used to create feeds for:
Shopping Portals: Shopzilla, NexTag, Shopping.com, PriceGrabber, and more
Search engine sitemaps: Google XML Sitemaps, Yahoo Search Submit, etc
HTML Store Maps: page(s) on your own site that link to every (or selected) product and category
Ultimate Feed Generator comes with 5 pre-defined feeds: Google Sitemaps, Froogle, PriceGrabber, Yahoo Site Submit, and an HTML site map. You can create as many new feeds, for as many purposes as you like, through the simply yet powerful interface. In addition, we'll be providing new feed templates on our website in the near future, free for licensed users.
The module provides tokens to display dynamic product and category data, such as name, price, description, weight, and other database fields. It also fully supports OpenTokens for users of OpenUI (although OpenUI is not required to use Ultimate Feed Generator). Feeds can be generated individually, or you can select multiple feeds and run them at once. (Check them all off and go to lunch while it processes, for instance.)
Fully supports OpenTokens, and special link styles (such as Search Friendly Links and others) can be built using tokens.
"If you haven't had a chance to use this yet I think you'll be blown away. It's truly the Swiss Army Knife of feed/export modules." -Marvin Sanders, WineBuys.com
Note: A version of Ultimate Feed Generator for Miva Merchant 5 should be available in February 2006.
The NetPush Advanced Inventory Module allows Miva Merchant store owners to track inventory within Miva Merchant all the way down to the attribute/option level. The module has numerous configuration settings that should allow the admin to display and track any simple or complex inventory configuration. Inventory levels are only adjusted at checkout time so there is no need to worry about old baskets causing inventory problems. The module comes with an import and export module that allows administrators to easily update inventory levels by using csv files.
We suggest using template modules like Viking Coder's Product Templates and
Category Templates if you want better control of the look and feel of your pages with regards to inventory. This will allow you to use tokens for display. Otherwise, you will have to settle for built in hook point displays that are built into the module and are configurable through the administration area.
The Advanced Inventory Module will send email when stock goes below certain configurable low stock level and can disable products when stock goes below the out of stock level. Administrators can also customize every message shown to the user. Fine grain customizations are made easy because the module allows product level configuration settings the ability to override global inventory configuration settings. This allows Miva Merchant Administrators the ability to customize inventory configurations for every product, if he or she wishes.
Notes:
OpenUI Tokens This module can be used with OUI OpenTokens. To use the module with Viking Coders template modules, see the OpenToken instructions and examples in the documentation on the NetPush.com site.
Product Upsell This module does not show stock information on the product upsell screens at this time. Stock is still tracked in the basket and checkout, but no current stock level is shown on the upsell screens during checkout unless you are using alternatives like tokens in templates.
Basket Redirect and Error Message The user is automatically redirected to the basket screen if he or she adds items to the basket that makes the product go out of stock or if the product is already out of stock. The error message is shown above the basket screen using a hook point in the Open UI. The message is configurable in the admin area.
Checkout Screen Error If configuration is setup to do so, the module will block a user from checking out if their basket has an item that is out of stock. This message is shown automatically at the top of the screen. The message is configurable in the admin area.
Pipes ( | ) Product codes, attribute codes, and option codes must not contain the pipe character. NetPush Advanced Inventory uses the pipe to delimit for lookups. Pipes in your codes will cause the module not to work correctly.
Requirements:
Open UI 4.723+ This module requires that you have OpenUI installed in your store. The module uses hook points in the OpenUI. You must have OpenUI version 4.723 or higher if you plan to use the OpenToken functionality available in this module. Please see the OpenUIsite for information about latest versions and bug fixes.
Miva Empressa 3.96+ This module requires that you have Miva Empressa 3.96 or higher. The module uses functionality that is only available in newer versions of the Empressa Engine. Miva regularly releases new versions of Miva Empressa and the Virtual Machine to add new functionality and fix bugs. If you are on an older version, consider contacting your hosting company. You can find the Miva Empressa version at the top left hand of your Store Administrator when you first login. It should show your Miva Merchant version and your Miva Empressa version.
Miva Merchant 2.x, 3.x, and 4.x This module should work with most versions of Miva Merchant. In order to use the deactivate product option, you must be on version 3.0+. All testing and development was done on versions 4.13+.
Global Configuration Screen
All inventory settings will use the global configuration settings found in the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. One may override these settings for products (see product level settings below). Each product must also be manually turned on before tracking starts. See product settings below.
Configuration Settings
Use NetPush Inventory You must set this to "Yes" if you want the module to be turned on. If this is set to "No", the module will not do anything.
Amount considered out of stock Usually this would be 0, but it can be set to any number, including negative numbers. Once the stock level reaches this number, it will be considered out of stock.
Deactivate when product level is out of stock In Miva Merchant versions that support it, the module will turn the Active flag for a product to off, if the product reaches the out of stock level. This only works on the product level, not for the attribute/option level.
Allow purchase even after out of stock Turning this on will allow customers to purchase products even after they go below the out of stock level. This could be a backorder situation.
Automatically remove from basket When a user adds products to the basket, the products will be removed if it makes the inventory go below the out of stock level and the admin is not allowing purchases when products are out of stock. Please take note that this option could cause problems if other modules are installed that also act on the basket.
Send Low Inventory Notices Turn this on to receive email warnings when inventory goes below the low inventory level.
Amount considered low The level that is considered low. Use this setting to trigger emails that will warn you when inventory is hitting a low level.
Low Email To Address Set this to the email address of the person who should be receiving emails when stock is at a low level.
Low Email From Address Set this to the email address that should be set as the from address in low stock emails.
Low Email Subject The subject of the low stock email. This field has token replacement.*
Low Email Body This is the body of the low stock email. This field has token replacement.*
Automatically change stock levels Turn this on if you want the system to subtract stock when a user purchases. If this is set to "No", the system will not update stock levels.
Show out of stock messages Turn this on to show out of stock messages on the product page when stock goes below the out of stock level.
Show in stock messages Turn this on to show how much stock is left on the product page.
Out of Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
In Stock Messages*
Product Level This message is shown to the user on the product page below the shipping weight.
Attribute Level - Checkbox This message is shown to the user on the product page next to a checkbox option.
Attribute Level - Radio Buttons This message is shown to the user on the product page next to each radio button option.
Attribute Level - Select Box This message is shown inside of the drop down on a select box. HTML should not be used here.
Other Messages*
Out of Stock - Basket Line Marker This helps the user to see which products have gone out of stock when looking at the basket. A red asterisks may be a good indicator for the user.
Out of Stock - Basket This message is shown to the user above the basket when a product has gone out of stock when adding, updating, or looking at the basket. Products can go out of stock at anytime, even after a user adds it to their basket. This is because stock levels only change after checkout.
Out of Stock - Checkout This message is similar to the out of stock basket message. It is shown on the payment screen during checkout. This should be considered one final inventory check before allowing the user to purchase.
* Token Replacement This module has a few built in tokens for messages that allow you to give yourself and the user more detailed information. Some of the tokens below can only be used on certain screens, or in emails.
%%stock%% - Displays the current stock level. (1,2,3) %%basket_quantity%% - Displays the amount in the basket and is unlikely to be used. (1,2) %%available%% - Displays the amount of stock left before hitting the out of stock level. (1,2,3) %%oos_level%% - Displays the out of stock level. (1,2,3) %%line_items%% - Displays a list of line items that are effected. (1,2) %%product_id%% - Displays the product id. (1,2,3) '%%product_code%% - Displays the product code. (1,2,3) %%product_name%% - Displays the product name if available. (3) %%attribute_code%% - Displays the attribute code, or None if the effected product is only being tracked at the product level. (1,2) %%option_code%% - Displays the option code, or None if the affected product is only being tracked at the product level. (1,2)
1. Is used for the low stock email body and subject 2. Is used for the out of stock basket message and out of stock checkout message 3. Is used for the in stock and out of stock messages on the product pages.
Product Configuration Screen
All inventory settings will use the global configuration settings found in
the Miva Merchant Administration area under Stores > Your Store > System Extension Configuration > NetPush Advanced Inventory. To override these settings at the product level, go to the product in the administration area and click on "NetPush Advanced Inventory". You will see the settings below.
Configuration Settings
Use NP Inventory on this Product You must set this to "Yes" if you want to track inventory on the product. You must manually set this to "Yes" for every product that you want to track. If this is not set to "Yes", no inventory tracking will take place. By default, no product is tracked.
Override Global Settings If this is set to "Yes" the configurations settings will be taken from the individual product screen instead of from the Global configuration settings found under under system extension configuration. If set to "No", the module will use the global settings from above when doing inventory for the product. The default is to use the global settings.
Amount considered out of stock Overrides same setting under Global Configuration.
Deactivate when product level is out of stock Overrides same setting under Global Configuration.
Allow purchase even after out of stock Overrides same setting under Global Configuration.
Automatically remove from basket Overrides same setting under Global Configuration.
Send Low Inventory Notices Overrides same setting under Global Configuration.
Amount considered low Overrides same setting under Global Configuration.
Low Email To Address Overrides same setting under Global Configuration.
Low Email From Address Overrides same setting under Global Configuration.
Low Email Subject Overrides same setting under Global Configuration.
Low Email Body Overrides same setting under Global Configuration.
Automatically change stock levels Overrides same setting under Global Configuration.
Show out of stock messages Overrides same setting under Global Configuration.
Show in stock messages Overrides same setting under Global Configuration.
Out of Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
In Stock Messages*
Product Level Overrides same setting under Global Configuration.
Attribute Level - Checkbox Overrides same setting under Global Configuration.
Attribute Level - Radio Buttons Overrides same setting under Global Configuration.
Attribute Level - Select Box Overrides same setting under Global Configuration.
Other Messages*
Out of Stock - Basket Line Marker Overrides same setting under Global Configuration.
Out of Stock - Basket Overrides same setting under Global Configuration.
Out of Stock - Checkout Overrides same setting under Global Configuration.
Setting Product Inventory Levels
The administrator can set product inventory levels by going to the product page within the Miva Merchant admin area and clicking on NetPush Advanced Inventory. This is the same screen as the product level configuration. Product inventory levels are shown below the configuration area. To add new inventory, use the yellow add button. To edit inventory, click white add button next to the inventory entry.
The module checks inventory by looking at a unique combination of Product Code, Attribute Code, and Option Code. When entering stock levels, you enter the codes separated by a pipe. For example, shirt1|color|red, where shirt1 is the product code, color is the attribute code, and red is the option code. If you do not set an inventory level for an existing product attribute combination, no tracking is done. Setting a stock level of -9999 has the same effect.
Inventory at a product level You may choose to only track inventory at a product level in combination with or not at an attribute level. To enter a stock level for a product, simply use prodcode||. This tells the system that you are tracking the product code, but not the attributes or options by leaving them blank. Using -9999 for a stock level will temporarily turn inventory tracking off.
Inventory at the attribute level (checkbox, select box, radio buttons) Checkbox - prodcode|attrcode|(the last field should be left blank, as checkboxes have no options) Select Box and Radio Buttons - prodcode|attrcode|optcodeAll 3 are required and must be unique, even if you are using attribute templates. If you are using normal templates in combination with attribute templates, make sure you do not give them duplicate code names.
Using Advanced Inventory with Template Modules and OpenTokens
The Advanced Inventory Module can be used with 3rd party template modules like the ones from Viking Coders by using Open UI tokens on product pages to display current inventory levels. Please note that token support has not been completely tested as of yet.
%module|npinventory|stock_level% Returns the stock level for the product, attribute, option combination. To ensure that this works correctly, you should set g.NPI_Product_Code, g.NPI_Attribute_Code, and g.NPI_Option_Code to the current product code, attribute code, and option code. On a checkbox, make sure to set g.NPI_Option_Code = ''. On a product level, make sure to set the attribute and option variables to ''. After these globals are set, call the token. If the return value is -9999, the item is not being tracked.
%module|npinventory|stock_available% Same as above but shows the amount available.
%module|npinventory|oos_level% Same as above but shows the out of stock level.
%module|npinventory|stock_list% This token will set a global variable that contains an array of structures. You must set g.NPI_Product_Code equal to the current product code before calling the token. This array contains all of the product code, attribute code, and option code combinations for a specific product. It also contains the available stock, out of stock level, and other information shown below. This token makes it easy to create a stock table using OpenUI tokens in Viking Coders templates or in a product header or footer. Code examples are available in the help pages on the NetPush.com site. Array Structure: g.NP_Inventory_StockList[i]:attribute_code - Attribute Code g.NP_Inventory_StockList[i]:option_code - Option Code g.NP_Inventory_StockList[i]:stock_level - Stock Level g.NP_Inventory_StockList[i]:oos_level - Out of stock level g.NP_Inventory_StockList[i]:available - Stock Level minus out of stock level g.NP_Inventory_StockList[i]:allow_pur - Allow purchases even if out of stock from admin settings g.NP_Inventory_StockList[i]:low_amount - Low amount from admin settings g.NP_Inventory_StockListLen - Variable that tells you how many items are in the array (represented by i above)
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.
Dynamically control what payment methods are displayed to your shoppers, based on almost any criteria. It uses the powerful OpenTokens strings to allow everything from simple to complex configurations. You are not LIMITED to use only criteria that we coded in...you can use almost ANY CRITERIA you can imagine.
Using the same OpenTokens strings, you can also rename each Payment Method (even supporting OpenLanguages).
Supports all current Payment Modules (including 3rd party Payment Modules).
Dynamically control what shipping methods are displayed to your shoppers, based on almost any criteria. It uses the powerful OpenTokens strings to allow everything from simple to complex configurations. You are not LIMITED to use only criteria that we coded in...you can use almost ANY CRITERIA you can imagine.
Using the same OpenTokens strings, you can also rename each Shipping Method (even supporting OpenLanguages).
You can also group products into different "classifications" and allow the shopper to select a different shipping methods for each. Will also help with providing free shipping. Support all current Shipping Modules (including 3rd party Shipping Modules).
Easily add Extra Product Fields to your store. Extra Fields can be of any type (character, number, boolean/logical, or memo), and each field can be displayed on the Product Display screen and the expanded format of the Product List, Categories & Search screens. Fully-customizable, template-based display of Extra Product Fields. Batch-oriented import utility handles very large data sets.
Summary of Features:
No limit on number of custom fields;
Custom fields can be character, number, Boolean/logical, or memo field;
Field lengths can be specified for character & number fields; memo fields have unlimited length;
Custom screen prompts can be specified for extra fields and for standard Miva Merchant fields;
Each Extra Field can be displayed on the Product Display screen and the expanded format of the Product List, Categories & Search screens;
Determine the order in which extra fields are displayed;
Display of extra fields can be hidden if value is empty or zero;
Extra fields added directly to Products field database, providing greater compatibility with other modules
Create and add as many of your own storefront pages as you like. Add static HTML content pages/screens within your storefront to display information, such as policies, contact us, FAQ's, shipping info, etc. Each page created can individually control the screen code, title, content, show/hide category tree, and show/hide right column inside the module configuration. OpenTokens is fully supported to parse/display OUI tokens for the page and provide easy insertion/placement of additional storefront page links inside the storefront.
The Buy X Items - Get 1 Free module gives the shopper a discount based on a predetermined qualifying number of items. In Merchant admin, the store owner sets the number of items it requires in order for the lowest priced item to be free. For every increment of that trigger number, an item's value reduces the total sale. For example, if the number is 5 and the customer buys 5, the lowest priced item is free. If the customer buys 10, the lowest two items are free.
When the customer views their basket, the free item discount appears as a separate line item. If they view the basket prior to reaching the trigger level by one, there is a message telling the customer to add one more and the lowest priced item will be free.
In the compiled version you can change the percentage discount from 100% (free) to a lesser discount of the lowest priced items. You also can change the message in the basket from the admin configuration panel. You can specify a list of products which are not figured in the quantity calculation nor are they eligible for the discounting.
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.