Storefront Basket
Order Fulfillment Import/Export Look & Feel Modules New Modules Payment Modules Shipping Modules Store Features / System Modules Utility Modules Truxoft Modules StoreMan/StoreMan Pro Miva Licenses Truxoft 2.x Modules Truxoft 3.x Modules
| | Order Fulfillment |
DEN_COUPON Coupon Manager 45.00
Coupon Manager allows you to offer customers various types of coupons which can be redeemed by entering a coupon code during checkout. It features full display options and extensive coupon options which can handle most any type of coupons you wish to offer, such as $20 off any order $100 or over, 15% of any order, buy 4 widgets get $2 off each widget, 20% off your entire order if you order 2 or more of widgets x, y, or z, 10% off orders for the next 10 shoppers that use this coupon - offer not valid with other coupons, and more! Coupons may be configured to only be redeemed when used by themselves or redeemable in conjunction with other coupons with an optional maximum total coupons that may be used. Coupons may optionally reduce sales tax depending on your state laws and the type of coupon being used. Coupon Manager's searchable console lets you view the number of times coupons have been redeemed at any time, as well as edit/remove coupons, and can also keep a log of all coupons used which can be imported into database/spreadsheet software. Features include: - configurable image/button text for redeem coupon button
- configurable header and footer for coupon prompt
- optional coupon log
- coupon expiration date
- fixed or percentage discount amounts
- extensive coupon options such as taxable, redeemable in conjunction with other coupons (with an optional max coupon cap), maximum uses, and a minimum required subtotal
- configurable qualifying products, including wild card support for product codes beginning with a specific string
- advanced additional product specific options including the minimum required quantity, whether to calculate the discount based on the quantity ordered (only for fixed amounts), including an optional max quantity cap, and whether to base the discount on the entire subtotal (only for percentage amounts).
- searchable console for easy viewing, editing, and deleting of coupons
- delete all expired coupons option
Note: This module requires ver. 3.9x or higher of the Miva Engine. | MMUI/OUI (OUI required for 4.14 and higher)| 3.x, 4.x| Full featured coupon management| 1

|
BROK_CERTIFICATES Gift Certificate Manager 80.00
| This module gives a store the ability to sell and accept electronic gift certificates. Gift certicates templates are created and can be associated with products for sale in the store (or their attributes). When the associated product is purchased, the module will automatically generate a key for that certificate and send an email (optional) to the purchaser containing the key and an explanation of how to use it. At checkout, on the payment and shipping selection page, the module prompts the customer to enter a gift certificate key and, when a certificate is used, applies the appropriate credit. The remaining balance, if any, is recorded and available on subsequent visits. | Of course there is a little more to it than that and this module provides for a great deal of flexibility: - Certificate types can be associated with individual products or their attributes. In addition, attributes can be added to the product to collect address information, the name of the person the certificate is for, the date to deliver the certificate, and any notes the purchaser wants to include for the recipient. This data is collected and stored in association with the key that is generated for that certificate.
- A template can be configured and used to view the certificate in a browser window. This template uses tokens to represent the various information about the certificate such as the key, the store name, expiration date, balance, etc. The data collected when the certificate was purchased (ie. address information, notes, etc.) can also be inserted into the certificate. This certificate can then be printed and mailed or manually distributed.
- Keys can be manually generated from within admin. Immediately after the key is generated, a link is availalble to view the certificate so that it can be printed.
- There is an administrative interface showing all of the keys that have been generated for each certificate type. The data shown includes the issue date, expiration date (editable), balance (editable), date last used, and the order id in which the certificate was purchased (unless it was manually generated of course). This list can be sorted ascending or descending by the certificate keys and the issue date.
- The orders in which a gift certificate is redeemed are tracked for each key and can be viewed from within admin. The amount for which the certificate was redeemed and the resulting balance is shown.
- A few of the other features:
- Email notification
- The contents of the email is completely configurable with a template which uses tokens to represent various data about the store and the key. The the email message can be separately configured for each certificate type as can the email subject
- Certificate Keys
- The keys can be separately configured for each certificate type and default settings can be configured. The format of the keys can be configured to use any number of numbers, characters, or a mix of both. A template is used to format the key and can include the store name, certificate code, and any other text
- Checkout Prompt
- The checkout prompt that appears on the shipping and payment configuration screen is completely configurable. It uses a template and tokens to represent the location of the text field and the "redeem" button and can inlude any well formed html you want to put into it. All of the buttons can have images configured for them and the size of the text field can be separeately set.
- Other settings
- Among other settings, the module can let you decide whether or not the certificate, when redeemed, can be applied against the shipping and tax, whether or not to permit multiple gift certificates to be used in a single order, and whether or not to bypass the selection of a shipping method and payment method for $0 balances resulting from the redemption of a gift certificate.
|
You can view the module's full documentation (including screen shots) here. | | OUI| 2.22+ 3.x 4.x| Sell and accept gift certificates in your store|

|
BROK_ORDERSTATUS Order Status 80.00 This module provides you with the tools you need to let your customers check the status of their past orders. It adds a link (or links, in up to 13 different positions), to the Merchant pages which customers can use to access their order history. The customer is given a display of all of their past orders. They can view the details of any of the orders, and even search them for details. The tracking numbers themselves can be direct links to the shipper's website tracking page, so the customer can check the status of their order with simple click on a link. The merchant, can access a listing of all orders, searchable by customer, date, orderid, shiping status, tracking number, etc., change their status, enter tracking numbers (for orders and even individual products), and have an email sent to the customer notifying them of the change. Shipping labels can be displayed and printed for each order. The format of the shipping label/packing slip is completely configurable using tokens. The merchant can individually configure many of the features of the module. For example, the status themselves are NOT predefined. The Merchant can configure these to be whatever he wants. Similarly, the "tracking types" can be configured, complete with a URL to use for that type of tracking number. When the tracking number is displayed to the customer, that URL is used to take the customer to the shipper's tracking page. The module comes preconfigured with the URLs for UPS, USPS, and FedEx but adding additional tracking types is simple. The merchant can select to send an email when the status of an order changes. Email can be sent to the customer's billing, shipping, or both, email addresses. Separate text for each type of email can be configured (ie. separate email text can be configured for when the status changes to "shipping", or "back-ordered", or whatever). The email text can include dozens of possible tokens that can be used to represent the customer's details (first name, last name, login, password etc.), tracking status, link to the customer's orders status page (it automatically logs them in), link to the storefront, and many more. The module does not require that the customer be logged in for their order data to be saved. Of course if the customer was not logged in when they placed their order, they won't be able to view the order later. The module maintains a separate database of the orders which is a duplicate of Merchant's order databases, including the payment and shipping details. So you can delete orders from within Merchant admin, but the customers will still be able to view their past orders. The Order Status orders can be deleted from within the modules admin interface. That interface also provides the ability to search the orders by date, customer, tracking number, tracking type, and status. The order details can be viewed, and tracking status, number, and type, can be set for individual products within the order.
The module's documentation can be read here| OUI| 2.x 3.x 4.x| Comprehensive order history and tracking|

|
DEN_SOFTGOODS Soft Goods 135.00
Soft Goods is a complete and secure solution for selling downloadable products with Miva Merchant. Files are stored in your Miva data directory (by default, you may also serve downloads from other locations, even a remote server), never in a public accessible directory. When an order is placed, if the order contains products which have been setup as soft goods, a unique download URL is generated for each product. This URL may be displayed above/below the invoice, and/or be sent in a separate configurable email. The URL is only valid for the maximum download attempts and/or maximum minutes you specify in admin. Download URLs can be issued automatically or manually. You can also configure which payment modules should trigger automatic URLs, and downloads for manually approved payment methods can be approved in admin via a searchable console. Features include: - maximum download attempts
- maximum minutes download is available
- selective payment modules to be used for auto vs manually approved downloads
- configurable display of download URLs on invoice
- configurable download emails
- attribute-based downloads (the file to download may optionally vary depending on the selected option of a radio or drop-down list attribute)
- product specific messages included in emails
- console with advanced search filters for manually approving downloads
- manually generated download URLs from the edit products screen
- failed attempts log which can be viewed and purged in admin
Note: This module works in conjunction with a PHP script, so your server must have PHP installed (most hosting providers do, but be sure to check with your host before purchasing if you aren't sure). Also, though this module is backwards compatible for 3.x versions of Merchant, it requires ver. 3.9 or higher of the Miva Engine. | MMUI/OUI (OUI required for 4.14 and higher)| 2.x, 3.x, 4.x| Electronic software download| 1

|
BROK_VENDORS Vendor Manager 80.00
| This module gives a merchant the ability to track the purchase of products assigned to vendors. The module logs all purchases and sends notification emails to the vendor assigned to the products. In addition, the module is capable of tracking payouts due to vendors and provides for a convenient interface to process payouts and generate "invoices". Use of the payout feature is optional. | Of course there is a little more to it than that and this module provides for a great deal of flexibility: - The format of the email sent to the vendors is completely configurable with the use of tokens to specify the vendor and order information. A default template can be configured for the email and individual vendors can also have a template specifically configured for them.
- Similarly, the invoice showing the payout being made to the vendor can be configured with a default template or with a template specific to the particular vendor. Like the email, the invoice template uses tokens to represent information about the vendor (name, code, payout due, total payout paid, date paid, etc.) and the products purchased.
- Payouts can be calculated and tracked as a percentage or flat rate (eg. $5/product sold). The percentage can be based on the product's cost, price paid (eg. prices affected by sales), or list price. In addition, the payout calculation can be configured "globally" for the vendor (applies by default to all assigned products) and individual products can also have a specific payout method associated with them (i.e. a vendor can be provided a different payout calculation method for a specific product).
- The module's admin interface provides for a simple listing of all payouts due with a link to each vendor's specific payout screen. Payout periods can be specified for each vendor and can be configured in just about time span you would want and can be set to be paid on any particular day of the week, month, year, etc.
|
You can view the module's full documentation (including screen shots) here. | | OUI, MMUI| 2.x 3.x 4.x| Notify and Track Payouts to your Vendors|

|
BROK_WISHLIST List Manager 80.00
This module provides your customers with the opportunity to add products to a List. This permits them to later return to your store to view, add, and edit the list as well as order things from it.0 They can send email to their friends prompting them to visit your store and view and purchase things from the list. Other customers can search the wish lists for the lists of their friends, hopefully with the intent of buying something for them, and send email to others to recommend that they visit your store and start a list. The module is very configurable and can be used equally well as a Wish List or a My Favorites type of feature for your store. You can view the module's full documentation (including screen shots) here. | Of course there is a little more to it than that and this module provides for a great deal of flexibility: - The admin interface provides the merchant with the ability to view the current customers with lists (searchable by list contents and customer data) and to view the contents of each list. The entire wish list can be deleted from within admin as can individual products in the list.
- If a product being added to a list has attributes, the customer will be prompted to select the attributes (but not required to) before the product is added to the list. If the customer is not logged in when they attempt to add the product to their list, they will first be prompted to log in and will have the opportunity to create a new account.
- The module adds new Merchant pages on which the customer can view their your own list and search for the lists of others. Links to both of these pages can be provided in up to 13 different positions in the navbar and in the category tree. The link by which the customer adds the product to their list can appear on up to 11 different positions on the product display page. The link text and/or image used for each of these links is separately configurable.
- When a customer searches for lists, the list "owner's" first name, last name, email address, login, city, state, and zip code are all searched.
- The merchant has the option of making the list "opt-in only" by providing the customer with a checkbox on the customer account page to enable a list (the text of the prompt is configurable). If a customer chooses not to opt-in to the list, they will be able to add/edit/view their own list but it will not appear in searches by other customers. They can still email their friends and provide them with a link to their list.
- An expiration period can be set for the lists. If no activity takes place in a configurable time period (ie. no products are added) the lists can be purged from within admin.
- The format of all of the pages is completely configurable with tokens. The customer can be permitted to edit the quantity of the items in their list, add a note, and delete individual items. The format of the page on which the customer views their own list and on which they view the list of others are separately configured to provide the customer with the additional ability to edit their list.
- From the page on which the customer view their own list, they can send an email to their friends to let them know about their list. From the page on which the customer searches for the wish of others, they can send an email to invite their friends to start a list. The content of both of these emails is completely configurable from within admin and use tokens to represent store and customer data.
- The header, footer, background image, title, and background color of each new page added by the module are separately configurable from the module's administration interface.
| | OUI| 2.x 3.x 4.x| Provide your customers with a Wish List or My Favorites list|

|
DEN_PIN PIN Fulfillment 80.00
PIN Fulfillment allows you to automatically issue PIN Numbers to customers when qualifying products are purchased. This module was developed for stores selling calling cards, but can be used for issuing any type of unique code for products, such as license keys, passwords, etc. The only requirement is that each "PIN" number is unique. Optionally, a second configurable field may be used to go along with PIN numbers. It might be used for a phone number, if selling calling cards, or for a password if selling logins/passwords, etc. The labels for both fields are configurable. PIN numbers may be sent in a separate email and/or displayed in the invoice. Note: displaying on the invoice requires Merchant 4.0 or higher and the OpenUI, MMUI installation instructions for enabling this feature will be provided upon request. The admin settings allow you to customize the email from address, cc, subject, header, and footer. You can also optionally be auto-notified when PIN numbers are running low for a product. PIN Fulfillment may also be configured so that PIN numbers are only auto-issued to customers assigned to a particular availability group (by default all orders are auto-approved). If the customer isn't assigned, the orders can be manually approved from an order history console. You can auto-assign customers to the availability group when manually approving orders as well. You can also setup the module to allow customers to view their PIN order history from the account edit screen. Note: this feature requires Merchant 4.0 or higher and the OpenUI, MMUI installation instructions for enabling this feature will be provided upon request. Additionally, you can set a customer order counter and receive notifications when customers' PIN orders have reached multiples of that counter (for rewarding frequent shoppers with coupons, etc.). PIN Numbers can be manually added for products via a simple to use console in the edit products screen, or in bulk using the included import module. An order history database is maintained, and easily viewed with a searchable console (for looking up lost PIN numbers for customers, etc.). The console also features optional search filters for searching by order number, customer name, customer email, product code, and PIN number. Note: This module requires ver. 3.9x or higher of the Miva Engine. |MMUI/OUI |2.x, 3.x, 4.x |Issue unique codes when qualifying products are purchased |1

|
DEN_CLIXGALORE clixGalore Affiliate Tracking 20.00
clixGalore Affiliate Tracking is a simple to use plug-in allowing Merchant to work with the clixGalore affiliate program. You must be a clixGalore member before using this module. Click here to sign up now. clixGalore is the recommended affiliate program by mivahelp.com, offering an affordable service. This module can work with all levels of clixGalore membership, from Bronze to Corporate Platinum. Admin Screenshot Compatibility Notes This module is compatible with MMUI and OpenUI for Miva Merchant 4.12 or higher. However, for versions prior to 4.12, it requires the OpenUI. Version 3.9 or higher of the Miva Engine is also required. | See Below| 3.x, 4.x| Drive traffic to your site using the clixGalore affiliate program| 1

|
DEN_AFFILIATE Generic Affiliate Integration 25.00
Generic Affiliate Integration allows you to integrate Merchant with an unlimited number of 3rd party affiliate programs such as My Affiliate Program, clickXchange.com, FineClicks.com, clixGalore, etc. Typically affiliate networks provide cut/paste HTML to insert on the invoice with placeholders for variables such as order number that should be replaced with the actual order number. This module allows you to replace these placeholders with their respective dynamic variables by using "tokens". The following tokens are available: - %order_number% - order number
- %order_total% - order total
- %order_subtotal% - order total before any order charges/discounts (tax, shipping, coupons, etc.)
- %order_subtotal_adjusted% - the order total before any order charges (tax, shipping, etc.) but after any discounts (any negative order charges, such as coupons)
When an order is placed, any HTML that has been added will be inserted into the bottom of the invoice, and any tokens will be converted into their respective values. In other words, the HTML code given to you by your affiliate program will automatically be calculated and sent without you having to make any code changes to your invoice page. Compatibility Notes This module is compatible with MMUI and OpenUI for Miva Merchant 4.12 or higher. However, for versions prior to 4.12, it requires the OpenUI. Version 3.9 or higher of the Miva Engine is also required. | See Below| 3.x, 4.x| Drive traffic to your site using the clixGalore affiliate program| 1

|
|
|