Ship-T for Dynamics RMS (Release June 2008) addresses the issues of a specific sales tax legislation (Destination-Based Sales Tax) in some states. The legislation requires that if a purchased item is shipped from the store by mail, the destination tax needs to be charged. However, when the same customer walks in the store and purchases the item in person, the store's local tax applies. Dynamics RMS provides no such flexibility as it allows to set default taxes on per-customer basis or treat everyone as a walk-away customer - without consideration of whether shipping is included or not.

Ship-T for Dynamics RMS overcomes this annoying issue. First, it imports the file off the Government web site which contains all destination-based taxes, and automatically creates or updates corresponding sales and item taxes. This process may be repeated every time the taxes change.

Read more about the program at: http://www.retailhero.com/destination_tax_dynamics_rms.aspx

Team Commission (Release June 2008) overcomes the limitations of RMS in the area of handling sales commissions. Quite often in the apparel boutiques and other high-ticket retail outlets commission is assigned to a sales team rather than an individual sales person. The team members may have different commission rates and "weights" within the team according to their experience and seniority and participate in different teams because of the work shifts.

The sales transactions are processed as usual with a sales team assigned to each transaction. However, as different team members may have different commission rates and weights within the team, each of them may get a different commision amount.

A built-in custom report in RMS Manager automatically calculates  each individualo member commissions for a period of time.

Read more about the program at http://www.retailhero.com/team_commission_dynamics_rms.aspx

New: Version 2.0 (new name: Physical Inventory Count - Made Easy, or PIC-ME for short)  also works with Windows Vista and RMS 2.0

This tool helps to overcome some shortcomings in Microsoft Dynamics RMS related to physical inventory count. It is designed primarily for importing count files produced by simple data collectors or data terminals, such as ScanPal 2.

The biggest deficiency in RMS, when it comes to importing from the data collector, is that RMS expects to see only Item Lookup Codes in the file. In reality, the codes that are scanned from items during physical count may be recorded in RMS as the item's Alias (e.g. a UPC code), be part of the Description, sometimes one of the SubDescriptions (1,2, or 3), or contain additional prefixes or postfixes (because of some business rules or oher peculiarities).

PIC-ME, when importing the file, looks up all those fileds in order to match the record to an item in RMS. It also keeps track of all "unknown" items by giving the operator an option to create new items "on-fly" or just display the list of such items for future manual fixing. Another nice feature is that the program also allows to consolidate multiple count sheets into one final count that will be used to commit and update the RMS database after the count is over.  

TOP Import (Transfer Order - Purchase Order Import) for Dynamics RMS

Version 2.1 - June 2008

The “Physical Count” functionality in RMS allows importing data file from a data collector (a standard text file: comma- or tab- delimited). However, a similar functionality is missing from RMS when it comes to TOs (RMS Transfer Orders) or POs (RMS Purchase Orders). But in some cases such functionality is required.

For example if one of the RMS Stores in a chain is used as a warehouse, a Transfer Order from the warehouse to a store may need to be populated from a data collector. Also, the Purchase Orders sometimes are not created prior to receiving but ordering is done manually and the Purchase Order is created “on fly” while receiving shipment from the supplier.

The Retail Hero’s Order Import utility helps to resolve these issues.

Features:

Retail Hero’s Order Import Utility has the following features:

• Operates as a standalone application or may be configured to run from the Tools menu in RMS SO Manager
• Lists all orders currently available in RMS: Purchase Orders and Transfer Orders with types and statuses
• Imports into RMS a data collector file (comma- delimited) which contains two columns per line item lookup codes (SKUs) and quantity.
• Adds items from the data collector file to the RMS Purchase Order or RMS Transfer Order if they do not exist in the order's content 
• Adjusts the item quantities in the order according to the data collector's file
• Verifies each imported item against the item’s supplier in RMS database (how it is setup in RMS) and alerts the operator if no match is found, If the SKU being imported is not found in RMS, allows the operator to create the item "on the fly".

Future enhancement will include the following functionality:

• Converting Purchase Orders into Transfer Orders and vice versa 
• Generating Purchase Orders and Transfer Orders based or restock/reorder levels
• Consolidating multiple Purhcase Orders and Transfer Orders at the warehouse

Contact Retail Hero for demo or purchase.

Q-Rewards for Microsoft RMS

'Frequent Buyer' Program - Buy X Get Y For Z - "Over Time" (Current version/build 2.5.2-Refresh - released 02/11/2007) Retail Hero's Q-Rewards (Formerly known as AQRMS) for Microsoft Dynamics is designed to implement a retail industry's requirement to track customer purchases for groups of similar items (product families) over time and reward the customer with a discount when they reach certain quantity levels - thus rewarding the customer's loyalty. Originally designed as the answer to the specific requirements of the Pet Food Retailers (to implement the common program supported by many pet food manufacturers known as "Buy 10 Bags Get 1 Free"), Q-Rewards for Microsoft RMS can be successfully applied to any other retail industry that deals with quantity purchases and rewards for loyal customers. Flexible settings allow for various reward scenarios for different prodcut families. Works well equally in single store installation or over RMS HQ for a store chain. Read more at: http://www.retailhero.com/dynamics_rms_frequent_buyer.aspx