CMS TEN Release Notes


CMS TEN includes important changes to help you meet PCI requirements for the next several years. We've done this by having CMS validated against the PA-DSS 3.0 specification. In fact CMS was one of the first applications in the country to be so validated. The related changes are, in some cases, significant and should be carefully reviewed to understand their impact on your operation and how to best address your PCI compliance efforts. A new PA-DSS Implementation Guide is included to help you with compliant CMS configuration and use. This doc is included with the install of CMS and can be downloaded from our Support Downloads site.

Of course CMS TEN also includes a long list of other, perhaps more interesting, enhancements and bug fixes. See below for details.

Release Notes from all previous versions can be found on our Release Notes page.


Important information to prepare you for the transition to your new version of CMS. Please see our CMS TEN Upgrade Plan article for additional guidance.

For All Updates from 9.x or earlier -

Encryption - The Encryption option in PCI Administration must be enabled before installing CMS TEN. Please log into CMS as PC Administrator and verify yours is turned on before proceeding. To do this, log into CMS as PCI Administrator and go PCI Administration>PCI. Your button for encryption should read 'Re-Encrypt' as seen in this screenshot AND say "no further action is necessary". If so, you're set and there's nothing more you need to do (no need to re-encrypt).

If you install CMS TEN and encryption has not been run or is up to date, the install will warn you and abort. If encryption/re-encryption is necessary. we recommend you run encryption overnight while everyone is out of CMS.

CMS 9.x to TEN Updates - If updating from version 9.x to TEN, the update will run quickly and is only necessary on the server.

CMS 8.x or earlier updating to TEN - Please refer to the 9.0 Release Notes and 9.0 Upgrade Plan for important information and details on upgrading to 9.0 before installing. While you are able to jump straight from v8 to TEN, you must familiarize yourself with the changes from v9 as well. Database changes occurred in v9 that could affect custom Crystal reports or forms (invoices, pick tickets, etc.) Contact us for more information on how to test these and make the necessary changes so they will work properly with the newer versions of CMS.

CMS 7.x or earlier updating to TEN - You must update to 9.0.5 before upgrading to CMS TEN. Please refer to the above links on import 9.x information before updating.

MINIMUM SYSTEM REQUIREMENTS – CMS TEN did not introduce any new system requirements although we can now support CMS running on Windows 8.1. Our system requirements can be reviewed on our CMS System Requirements wiki page.

Release codes - CMS TEN uses the same release codes as CMS 9.x. If you're on CMS 8.x, you'll need to use v9 codes obtained from your account manager.

Server updates - The initial server update from 9.x to TEN will take up to 50% longer than a standard update. Updating from version 8.x will take quite a bit longer.

Note - We are now deploying Java and Mapforce files with server installs to facilitate our forthcoming Amazon integration. This results in two new directories under \NewHaven Software for \jre and \MapForce.

Workstation updates - Workstation updates are required for any Windows 8.x machines after your server update to CMS TEN. This update is necessary to install the new Sybase database drivers which are needed to properly support these operating systems.

End of Life Announcement - WinXP and Server 2003
Microsoft has announced they will no longer provide support and updates for Windows XP. Windows Server 2003 is also slated for End of Life on July 14th, 2015.

This is a fairly critical situation. XP and Server 2003 will no longer receive security patches which, aside from the obvious security threats, also means that you cannot be PCI compliant.

For a complete list of operating systems we support for use with CMS, see our System Requirements wiki article.

PCI Compliance - CMS TEN has been successfully validated against the PA-DSS 3.0 specification by Coalfire Systems. Software changes that could affect your compliance are only included in major CMS versions (e.g. 9.0, 10.0) or minor versions (e.g. 9.2, 10.2) and never in releases (e.g. 9.0.5, 10.0.2) or builds (e.g., You can read more about our versioning methodology HERE.

You can find CMS versions 7.0 through 10.0 listed on the PCI Council’s directory of Validated Payment Applications.

Database Changes - The following database changes were made in CMS TEN. This information is provided for users that may have custom integrations or reports that could be affected by changes made in TEN.

XML Spec Changes - Changes to our specification (CMSxml.xsd) that governs how XML data is imported and exported

Integrations - With the noted exception below and needing to ensure all integrations are connecting to your database with the CMSUser credentials as described above, all integrations will continue to work as they had including CommerceV3, UPS Worldship, FedEx Ship Manager, Endicia/DaZzle, ShipRush, MPS, TransFirst, and

Manifest - The way shipping methods are selected in the Manifest has been changed to more closely resemble how selections are done in Order Entry. This was done to facilitate the use of hotkeys and can be done without using the mouse. A full list of Manifest changes is described in more detail below.

The Date Advance field that was used for our Dazzle integration has been changed to a field called Pickup Date to merge the advanced label processing concept with the one supported by UPS. CMS will now display the actual date of pickup instead of how many days in advance you're preparing the label.

UPS Worldship - Keyed Imports
- We've revamped how keyed imports work with Worldship to dramatically increase the speed of the imports. (no impact on XML integration) This was in beta previously and is now in full release in CMS TEN. No change in configuration is needed, it will now just run faster. Also worth noting is that CMS now supports passing package dimensions to Worldship and Dazzle which is described in more detail below.

1Shopping Cart - We have removed support for 1Shopping Cart from CMS. Please contact us if you are still using their eCommerce solution and desire to import orders from your site into CMS.


CMS Downloads Site



  1. PA-DSS 3.0 (PCI)

    The PCI Council released a new PCI DSS specification in 2014, version 3.0. Once it was announced we took the leading edge and have had CMS TEN validated against the new 3.0 spec by Coalfire Systems. In fact CMS was one of the first applications in the country to be successfully validated against this new standard.

    The term "PA-DSS" translates to Payment Application Data Security Standard. It is the subset of PCI requirements that specifically apply to applications, like CMS, that handle payment data. We submit CMS to a security assessor certified by the PCI Council to validate CMS has met or exceeded the requirements in the PA-DSS specification, which in turns ensures that CMS will allow you to be PCI compliant.

    CMS TEN and its adherence to the new 3.0 standards will facilitate your PCI compliance for many years to come in addition to providing you with added levels of security immediately.

    You can read a high level overview of the 3.0 changes (vs 2.0) in a PDF published on the PCI Council's site -

    The PA-DSS 3.0 requirements that we've had to satisfy not only apply to CMS as software but also to NewHaven Software as a developer to ensure that we develop and deploy CMS securely, employ secure coding techniques, receive regular security and PA-DSS training, monitor and assess security vulnerabilities, etc.

    Most of the changes in CMS for PA-DSS 3.0 will not have much of an impact on your day to day use of CMS. Nevertheless, there are several changes that your administrators must become familiar with which are detailed here:

    • New PA-DSS Implementation Guide (IG) - We provide a document called the CMS PA-DSS Implementation Guide (a Word doc) that provides you with specific information on how CMS addresses or helps you satisfy all of the aspects of your PCI compliance pertaining to your use of CMS. PCI compliance goes well beyond just your software but, for the areas CMS can affect, you can rest assured you have the compliant solution you need.

      Please refer to this IG for guidance on how you need to configure and use CMS. This document will be especially useful as you're completing your self assessment questionnaire (SAQ) so you can see which areas are impacted by CMS and how potential vulnerabilities are addressed.

      You must follow the instructions in the CMS PA-DSS Implementation Guide in order to be PCI compliant.

      After installation this document can be found in your \docs folder in the \NewHaven Software shared directory (where you run CMS.exe from) or can be downloaded from Support Downloads.

    • Masking - The Masking option in PCI Administration has been removed and now is always enforced. Credit card numbers will always be masked throughout CMS once they have either been processed or saved.

    • DBO - The database user 'DBO' can no longer be accessed by users. It is exclusively for use by CMS and CMS will manage its password in a PCI compliant manner.

      If you have any custom integrations or connections to your CMS database, make sure they are done with the CMSUSER account. Also, the CMSUSER account no longer has access to the tables or fields that fall under the scope of PCI (administration settings, employee, and credit card data)

      If you've created your own tables in CMS, you will still have access to read/write to them but no longer have access to modify database structures. This means you cannot create new tables or modify existing tables.

    • Username - CMS will no longer display the user's name on the right side of the login screen after initials/username have been entered. Only the combination of username and password can be confirmed (see next bullet)

    • Password - CMS will no longer tell you that the password you entered is invalid. Instead it will only indicate that the combination of your username and password is invalid.

    • New Admin Password - When creating a new PCI Administrator user, you will be forced to immediately set a password.

    • Secure Deletes - CMS now employs 'secure deletes' so that sensitive data is overwritten several times before being deleted.

    • Secure Connections - When downloading orders from a website/service or FTP location, CMS will require that the connections to these servers be secure (e.g. https or ftps)

    • New Logging - A new log has been added to record any changes to your database structure. See the CMS PA-DSS Implementation Guide for details on how to export this log data.

    • Improved Audit Log - The PCI Audit log has been expanded to record every change made by anyone logged in with an administrative account including, but not limited to, changes to employee permissions.
  2. Gift Cards

    Gift Cards are physical branded rechargeable cards (think Starbucks) that you can issue to your customer that they can use to pay for purchases on your site, in your store, or by phone. CMS is now able to sell, issue, redeem, and reload gift card via the gift card solutions offered by Mercury Payment Systems (MPS). You do not have to do your credit cards with MPS to take advantage of their gift card program either.

    Here is a summary of related enhancements:

    • New Product Type - (checkbox above gift certificate) for selling gift cards. This enables a new Gift Card button in OE>Items that you’d click on to issue the new card. There are no other Product settings.

    • Gift Card account setup is done in PCI Administration. There you can define your bin ranges and card number lengths for accepted cards so CMS can validate gift card input.

    • Order Entry - Selling a gift card product enables a new Gift Card button where the card can be issued (card number scanned or entered, amount set, and submit.) Existing cards can be reloaded in this same screen.

    • CMS does not enforce a relationship between the amount of the gift card loading and the sale price. As such you could sell a $100 gift card for $90 as a promotion.

    • Gift card reporting will come from the card processor (issue, redeemed, activity) since the gift cards could be used at different channels, potentially those not handled by CMS, and cards may be preloaded by MPS. Activity from CMS will include the station and user ID combined as an operator ID.

    • There is a Gift Card Manager interface available under the Accounting menu where cards and balances can be reviewed either for all customers or a selected customer. Reloading and issuing is only available in Order Entry, however.

    • Gift cards are all processed as a sale, a single transaction. There is no approval capture. Deleting a captured gift card sale will reverse it, the same as voiding a captured credit card.

    • Modifications were made to the 'last payment used' lookup that CMS does to find last gift card, separate of credit cards. Card number for retrieved gift cards and credit cards is now locked and may not be edited.

    • Gift card use is currently only available in Order Entry. Not available in Apply Payments or for Customer Credit Ledger

    • No AVS is used but CVC is optional

    • You can set a threshold in account setup to establish how much of a gift card balance can be returned to cash

    • Gift card transactions write to our cmsedc.log when enabled. No storage otherwise of specific transactions from CMS (just the sale of gift card products.) That reporting comes from MPS.

      Contact your NHS account rep if you're interested in learning more.

  3. Tokenization

    Tokenization is a solution to reduce the complexity of your PCI compliance by removing cardholder data (CHD) storage from CMS. If you don't store CHD, the size of the self-assessment questionnaire (SAQ) you have to complete could be reduced by about 50% (SAQ-C instead of SAQ-D). The effort and corresponding cost savings could be very significant so is worth serious consideration.

    Previously the choices available to you were either store the credit card data, and deal with the involved compliance associated with it (SAQ-D), or not store the card data at all and live without the convenience of having card data on file for future purchases, returns, etc. Tokenization represents the best of both. It allows you to keep a card on file for future use (up to six months since last use) but, instead of being stored on your server, it is being stored by MPS who provides CMS with a token to use next time that card is needed. The experience is almost entirely transparent to you as you'll continue to see the last 4 digits of the card for reference.

    This service requires credit card processing via Mercury Payment Systems (MPS) using their MToken solution and doesn't require your website also be tokenizing (CMS will tokenize when the payment is processed.) Contact your NHS account rep if you're interested in moving your payment processing to MPS.

  4. eCMS Enhancements

    eCMS is the module that manages the integrations between CMS and your website(s).

    • Process Locking - The types of communications possible include order downloads, order status uploads, and product data uploads. These communications can be scheduled or run manually so in a previous version we added locks to ensure that you couldn't manually start an upload/download while another was running on another machine, complete with a message indicating who had the process locked.

      In CMS TEN this locking mechanism becomes more granular so one person could be downloading orders while another is uploading product data, even for the same site. This should be particularly useful for companies running multiple stores or import order sources, allowing multiple non-conflicting upload/download sessions to run concurrently. If there are no processes currently locked, you'll be able to proceed as normal. If any requested process is locked, however, a new dialog window will pop-up informing you of which processes are locked (and on which machine/operator). You can then decide to continue with the remaining unlocked operations or cancel and wait until those locks are cleared. Be aware though that any requested processes will be locked by you until you respond to the dialog to continue or cancel.

    • Admin Email - A new field has been added to the Global Options in Import Source and Plug-ins for eCMS Admin Email. Global Options is where you would go to setup one of your CMS workstations to automatically connect to your web site(s). If any automatic connection fails more than three times due to the processes being locked by someone else (see above bullet), CMS will then send an email to this email address informing you which process locks were encountered.

    • Order Import Cycling - An option has been added called 'Order Imports are limited and must be cycled to completions'. This new option allows you to control whether or not you'd like CMS to continue requesting new orders for download until there are no more remaining. This is particularly useful for sites like CommerceV3 that have limited the maximum number of orders allowed to be downloaded in a single request.
  5. Import Improvements

    Changes that impact all order imports, from file or eCMS integration.

    • Override Prices - The option used to override the prices on imported orders had been a global option that applied to all import order sources. This has been moved to the order source level to better facilitate importing orders from multiple sources. With this, you can have some sites or sources of orders that provide product pricing and others that CMS will assign on import.

    • Country Matching - We've improved the logic used for matching countries on imported orders. This, in addition to updated country table data, will help ensure that CMS properly recognized the country (solving the common issue with Spain vs Canary Islands, as one example.)

    • Background Processing - Order import processing window can now be minimized to run in the background allowing you to perform other work in CMS while the imports/uploads are running.

    • Automated Imports Module
      • Users of this module will now find that the grid of validation checks consists only of columns representing failed checks. Previously this grid displayed all columns/checks regardless of whether or not you were configured to use them or if there were any orders which failed that check. This new filtered display limits the columns displayed to only the validation checks pertinent to orders in the Verify Imports queue.
      • New validation check has been added to see if the order's customer has a non-zero balance. You'd use this if you didn't want an order to automatically process if the customer owes you money from other orders.

    • Verify Imports
      • Column added for Fulfill Date so you can identify future ship orders which can be useful if you want to prioritize the verification of orders shipping today
      • Window can now be maximized
      • Order Date converted from a date:time to just a date. Downloaded column still includes a time stamp
  6. CommerceV3 (CV3) New Web Service

    We have completed our migration to the public CV3 web service. For over ten years we've worked with a web service CV3 hosted specifically for CMS and, while it has worked well, they have since implemented a new web service used by all other integrators.

    That "public" web service (not really public but not dedicated to CMS) has been enhanced more quickly than the one they host exclusively for CMS and thus has more capabilities. Our migration onto the public web service opens the door for improving and expanding our integration with CV3 for such things as quantity discounts, product URL's, categories, additional product fields, etc. More to come in future CMS versions...

    To use the new public web service, you'll need to change your configuration in CMS for your CV3 order source to use the plug-in called "CV3 (Public)" instead of "CV3 (CMS Only)". We will continue to support both for the time being but all ongoing development of the integration will now take place in the CV3 (Public) plug-in.

    • With the new web service we are now able to map item-level customization data into the customization fields within CMS where on the old web service that customization info was just placed into the invoice notes.

    • New plug-in options have been added allowing you to select what product data you want uploaded. There are controls for Text, Pricing, and Inventory.

    • Another plug-in option has been added specifically for Attribute Names. If you are using attribute names on CV3 other than Size and Color as they are in CMS, this plug-in option will keep CMS from overwriting them during a product upload. CMS can now also poll CV3's product list to see if an item is new or not to determine if the attribute labels should be uploaded (always needed for a new product).

  7. Magento Integration Improvements

    • Passing Credit Card Data - Magento, by default, does not store credit card data which means all processing of those payments must be done on their site. This requires a elaborate synchronization between CMS and Magento to ensure accurate invoices and packages are created to facilitate proper payment. While this is possible, the integration is more complex and in many cases a more traditional style of integration may be desirable, where all charge processing is handled in CMS.

      With CMS Ten, we have modified our eCMS Magento plug-in to accept credit card data. This option is only available to users running Magento Community or Professional editions (other editions are hosted by Magento and do not allow the credit card storage option to be enabled.)

      If you choose to enable this option in Magento, their storage of credit card data adds significant PCI responsibilities. You'll need to work with your service provider to ensure those requirements are being met.
    • Improved order status uploads - Speed of uploads has been dramatically enhanced by CMS processing updates against multiple orders at a time
    • Future ship dates supported via custom fields feature
    • Improved product uploads
      • Improved support for size/color (SKU defining) attributes
      • The CMS product code can now be included in the product listing in addition to the SKU_ID
    • Invoice Notes - Imports now allow for multiple lines of invoice notes
  8. Active/Inactive Flags

    Using CMS for years often results in a huge list of ad codes and shipping methods, many of which are no longer active or pertinent. Deleting these old codes generally isn't a good alternative as it will result in some loss of data/history. To address this, and make it easier on your operators to make valid/current selections in Order Entry, we've added an Active flag to the following lists in CMS:

    • Ad Codes - A checkbox option was added in Order Entry under the ad code selection so you can choose to see inactive codes when needed.

    • Order Sources - This would be used primarily for import orders sources that you no longer receive orders from (old Yahoo store, call center you no longer work with, etc.)

    • Shipping Methods - Older methods can still be shipped in the manifest (say you're fulfilling an old order) but only active methods can be selected in Order Entry and the Manifest otherwise

    • Price Categories - In some scenarios price categories may be created frequently and for temporary use. You may now set a price category as inactive which will prevent it from being an option to select in Order Entry and product setup. The price category remains in the database though to facilitate proper reporting and can be viewed in Order Entry for saved orders (just not selected for new orders.)

      The selection combo (dropdown) boxes have all been refined to allow the display and selection of historical inactive codes when they were previously used but not display them for new orders/transactions.

      Note: Active flags are also used for product SKU's and Catalogs as implemented in earlier versions of CMS.
  9. Email Confirmations to Ship-to and Bill-to

    A top request from User Voice! All confirmation emails sent by CMS in the past have just been to the customer's primary email address, which is the email address found on their Mailing address tab (not the bill-to or ship-to.) There was logic in place to use the billing or shipping email address (in that order) but only if no mailing email address was present.

    You can now configure CMS to send email confirmations to the mail, bill, and/or ship-to email address. Note that CMS will still use its logic to find the next best email address if the preferred email address is not available. For example, if you wanted to confirmations to only be sent to billing address email, CMS would do so when one was present and would default to the mailing email address when there was no billing email. CMS will never use the ship-to email, however, unless you have CMS configured to use it.

    The current implementation of this feature can send confirmations to the customer's billing or shipping email but will not send confirmations to recipients of multiship orders. This is currently being explored in a way that would facilitate recipient specific order information being sent to each ship-to as opposed to information about the entire order, as confirmations emails work currently.

    There are unusual but possible circumstances where an email confirmation gets created but cannot be sent (e.g. bad email address data.) When you release email confirmations from Fulfillment Manager, you will now be warned when such emails exist and they will be left in the list for review, editing, or deletion.

  10. Contact Manager Improvements

    • CMS will now prompt you to save if you've made changes to a customer record and attempt to close or leave the record without saving. If you scroll off the customer record to the next/previous and answer No to the Save Changes question, your changes will be discarded. This only applies if you are operating without the workstation specific setting for Autosave (noting we generally do not recommend using the Autosave option, which saves changes automatically as soon as you exit any field in the Contact Manager.)

    • You may now also choose the Alternate ID as the field for prominent display in Contact Manager. This is the data displayed just below the customer's name at the top of the Contact Manager, next to Primary Notes. You can alter what is displayed here in Setup>Customers>Customer Fields>Field for Prominent Display

  11. Grid Improvements

    In many of the grids in CMS you can not only sort the results by clicking on the column's label, that label will now also display an arrow showing if you are sorting ascending or descending. Examples of where this is employed is Verify Imports, Find Customer, Quick Counts, and Fulfillment Manager. (see video)

  12. Batching and Edit Batches combined

    The Batching window and the Edit Existing Batches windows have been combined into a single tabbed interface. Each will automatically refresh as you switch between them. Both support the column sorting described immediately above and both now allow double-clicking on an invoice to retrieve it.

  13. Products/Purchasing Improvements

    • In the past we found it was too easy to inadvertently click and remove the 'Has Sizes', 'Has Colors', or 'Is a Kit' checkboxes in the Products window. Un-checking these boxes can have significant effects and is difficult to correct. CMS now employs protections to prevent these checkboxes from being unchecked until all of the SKUs have been removed (for Sizes and Colors) or all of the kit components have been removed (for Kits.)

    • The size of the UPC field has been increase to 40 characters

    • Price Categories - The number of price categories has been expanded from 99 to

    • Stock Manager - Hotkey added for saving new lots (Alt-O triggers the OK button)

    • Kits within Kits! - CMS now allows you to have assembled kits as components of other kits. To be clear, an assembled kit is on that has its own stock (i.e. not pulling from components' inventory in real time.)

    • CMS will now prompt you to save if you've made changes to a purchase order and attempt to close or leave the record without saving.
  14. Kit Builder Improvements

    The Kit Builder feature, introduced in CMS 9.0.5, is a useful tool for automating the assembly of stocked kits, reducing inventory from their components as you build them. In CMS TEN we've incorporated a number of requested improvements including:

    • Product filter - A new 'Kits' field added to the top left of the Kit Builder screen allows you to filter the list of displayed kits to be built just by typing in a portion of the kit's product code OR description.

    • Column sorting in the top grid so you can sort the grid by 'Can Build', 'Cur built', etc.

    • Column added for "Reserved" quantity

    • Columns added for Restock To and Resupply At

    • Improved component filtering

    • When costs of built kits change after the kit is built, CMS can now find and correspondingly update the kits lot cost (as well as any orders that allocated from that lot)
  15. Apply Payments Improved

    Several enhancements to make Apply Payments faster and easier to use:

    • Field added for PO Number - Useful when applying a single payment to multiple open invoices that are referenced by PO Number (note: The grid in Apply Payments allows for column sorting by any field, including PO Number, so you can quickly find the open invoices/PO

    • Running total added when multiple invoices are selected - Useful when using a credit card to pay off selected invoices and you want CMS to tell you the total amount owed (vs the customer sending in a fixed payment amount)
  16. Linked Billing Enhancements

    When viewing the parent customer record for a linked billing account in the Contact Manager, under the History tab you'll see a new option to toggle between viewing just this customer's history or the history of any one of its linked children. This will make it quick and easy to identify contacts or orders for any of the children accounts.

    You may now also choose the Linked Billing customer number as the field for prominent display in Contact Manager. This is the data displayed just below the customer's name at the top of the Contact Manager, next to Primary Notes. You can alter what is displayed here in Setup>Customers>Customer Fields>Field for Prominent Display

  17. Editing Notes for Any Invoices

    The Invoice Notes text box available for editing during the entry or editing of an order has traditionally only been for the order's first invoice. You may now scroll to select other invoices for the order to see and edit notes specifically for that invoice.
  18. Order Entry Changes

    • PO Number search - You may now search for an order by PO number with a wildcard search. As is the case with customer searches, you can use the % sign before or order the known search criteria to search for a PO number beginning or ending with that value. For example %1234 would find any orders whose PO number ended in 1234. 1234%, on the other hand, would find any order whose PO number started with 1234. You can even use the wildcard on both sides to find any PO that has 1234 anywhere in it (e.g. %1234%).

    • Last Card Confirmation - In previous versions CMS would automatically load the last credit card used for the customer if that payment type was selected. You'll now be presented an option of loading that saved card or continuing with the entry of a new card number.
  19. Shipping Formula Precedence

    The shipping formulas you defined in CMS are used to calculate the shipping and handling fee you charge to your customers. Typically these formulas are either applied to an order based on the order's price category (e.g. Retail, Wholesale, etc.) or based on the order's shipping method. In most situations applying these formulas to just one or the other is fine. In other cases though you may wish to have a base formula to use for the price category but if the customer selects an expedited shipping method, then use a different formula.

    In CMS TEN there is a new checkbox in the shipping method setup for 'Take Precedence over Price Category' which allows the shipping method's formula to apply instead of the price category's formula. With this box unchecked, the price category's formula will be used.
  20. Shipping integrations

    • UPS Worldship (XML) - CMS can now support international shipping with UPS via our XML integration with Worldship (processing packages from the CMS Manifest screen, not keyed imports from Worldship.) To make use of this you'll need to have the customs data added to your products (same as is used with Endicia international), at minimum the country of origin. This integration will trigger the printing of the appropriate shipping label and UPS customs invoice. Individual items that are valued at $2500 or more require additional documentation (SED - shippers export document) which is not created as part of this integration. If you have a lot of these let us know and we'll pursue it further.

    • USPS International (Dazzle)
      • Logic has been added so CMS can choose the customs form based on method, weight, and value (noting that CMS must make this determination, not Dazzle as you might think) See
      • The number of customs line-items you can have in a package has increased from 30 to 1000

    • Keyed imports
      • Integrations have been completely redesigned to dramatically improve performance. No need to do anything, it will just run faster in CMS Ten. This is true for both UPS and FedEx
      • We've added a new Unshipped Packages view in the database to facilitate keyed imports from third party multi-carrier shipping systems and/or alternate USPS shipping solutions (previously there was no way to do keyed imports with USPS shipments from outside CMS.) These options can be quite attractive if you're interested in automating rate shopping between services/carriers.
      • A new database view has also been added for item-level customs data. This will be used for keyed imports of international shipments to obtain the customs data for each item in the package being shipped.
  21. Manifest Enhancements

    A number of changes have been made to the Manifest screen to improve the efficiency of your package processing and to provide some new capabilities. You can view a screen shot of the new Manifest screen HERE and read about the details below.

    Hotkey Selection - The Manifest now allows you to select shipping methods by hotkey (same as used in Order Entry) which should speed up the process of changing a shipping method for a package when needed. You can click into the field to make your choice or press the F2 button to tell CMS you want to alter the shipping method and then just type in the hotkey.

    Function Key Scans - If you have your scanner configured to operate in HID POS mode (see below), you can use your scanner to scan in function keys to trigger various functions in the Manifest including:

    • Change Ship Method (F2)
    • Bring in Weight from Scale (F4)
    • Add Package (F6)
    • Print Label (F7)
    • Validate Address (F8)

    Print out our list of Manifest Hotkey Bar Codes and just tape it to the monitor on your shipping station or you can download this document from Support Downloads. The document has the bar codes aligned both horizontally and vertically so just cut out the alignment that best works for your monitor.

    The goal, of course, is improvements in the speed of processing packages. This is done by minimizing how often you'd need to reach for the keyboard or mouse. For most shipments you can just place the package on the scale, scan a bar code or two, and your label is printing. See our wiki article on Shipping Station Best Practices for other tips.

    Pickup Dates - You can now print shipping labels for packages you want to be picked up by the carrier on a future date. This can be helpful to balance out your workload when approaching a high volume shipping period, like the week before Christmas if you're retail, by releasing your future shipments early and preparing those packages today.

    UPS supports pickup dates up to 30 days in advance and USPS (Endicia/Dazzle) supports up to 7 days in advance. Our integrations for label processing from the Manifest with UPS Worldship and Endicia's Dazzle software for USPS both support future pickup dates in CMS Ten.

    By default the pickup date for all packages will be today and is displayed as a Default Pickup Date for all packages. Viewing the pickup date for a specific package, you'll see that same date displayed in italics to indicate it is a slave to the Manifest's default pickup date. You can override this manually, or with an option to preserve the future ship date as the pickup date during future ship fulfillment, in which case it will be displayed non-italic.

    You can read more about the setup and use in this document or watch a quick run through in this video.

    Note: Pickup dates explicitly set by the user or by a fulfillment override are not affected by the carrier default date advance setting.

    Multi-user - The manifest now can work more effectively when running multiple shipping stations simultaneously. CMS will flag the package to indicate which shipping station has added it to the manifest to facilitate limiting the packages displayed in the manifest to only that stations packages. This will ensure that there is no cross shipping or confusion between stations. We've added a new option in the Manifest screen to let you toggle between viewing all manifested packages vs only those manifested on this workstation.
  22. Scanner Support Expanded

    CMS has traditionally supported USB bar code scanners configured to work in a serial emulation mode. CMS can now also work with scanners configured in a USB HID POS mode. This method should both allow for faster reads, wider support for other scanners, and simplified setup. While this mode has 'POS' in its name, it is not limited to POS use and will work equally as well for the the warehouse and shipping.

    We've added support for the model Honeywell 1300g scanner which has replaced the widely used 3800g. This scanner operates in both serial emulated and USB POS mode so is a good choice for any version of CMS. Programming instructions for this scanner can be downloaded from our Support Downloads.

    We've made strides in our understanding how to best support scanners and other USB peripherals over remote connections (e.g. Remote Desktop). Please see our wiki article for additional information if you would like to use CMS remotely with scanners and/or card readers.

    New Places to Scan - You can now scan product bar codes to lookup a product in both the Products search window as well as Stock Manager.

  23. Refund Enhancements

  24. Refunds may now be canceled from Payment Maintenance. If this refund was a result of refunding customer credit, the customer's credit will be adjusted back to the pre-refund amount by a new entry in the customer's credit ledger. If the refund was a result of a return, you'll be advised to edit the order and delete the payment there, allowing Order Entry to properly handle the financial adjustments necessary.

  25. Help!

    We have fully converted our Help files to the web allowing us to provide content updates year 'round without you ever having to install an update. When you open Help, either by the Help menu or hitting F1 for context-sensitive Help, CMS will pop open your favorite web browser and launch the CMS Help portal. Help is now available to anyone, anywhere, on any device, even if CMS isn't installed. Of course an internet connection is required for this, which probably isn't too much to ask these days, but if a connection cannot be found CMS will instead use the local Help file from CMS v9.0 (which will only receive limited updates.) The PDF manual has also gone away in favor of this new more interactive and accessible version.

    Also, a link has been added under Help>Online Resources for 'Request a Feature' which will take you to our User Voice site. At User Voice you can review and vote on feature requests submitted by other users or, of course, your own.

  26. Windows 8.1 and Server 2012

  27. Windows 8.1 Pro (not 8.0 or RT) and Server 2012 are now officially supported for use with CMS. This required upgrading to a newer version of the Sybase database which includes new drivers. Workstation installs will be required to update the Sybase database access drivers on each CMS workstation running Windows 8.x.
  28. Reports

  29. Hide Zero/Discontinued - The Physical Inventory, Inventory Analysis, and Items To Reorder report have all been modified to include a new parameter for Hide Zero Stock. Options include No (default), Yes, or Discontinued only.

    Physical Inventory - This report has been overhauled to enhance allocation reporting, specifically to improve performance and better account for the allocations of kit components.

    Dropship Invoices (new!) - This report is found under the Fulfillment category of reports and, for a range of dates, will tell you all of the invoices you have with dropship items along with corresponding dropship purchase order info/status. See example.

    Shipping Cost Analysis (new!) - A report we've had in beta for some time has made it into release. This report looks at the shipping charges on an order and compares it to the shipping costs from the carrier to help you assess if you're making or losing money on your shipping charges (example).

    While the first page of the report provides a high level review per shipping method, further down the report it also provides details on what you're shipping to each zone by weight.

  30. Bug Fixes and modifications


CMS Downloads Site


CV3 (public) - Backorder dates (CV3 term) were not being included in product uploads at the SKU/attribute level (only at the product level) - Dev-335

CV3 (public) - Expired CV3 passwords would cause order downloads to fail without an error message to indicate that the expired password was the problem (such a message has been added) - Dev-255

NCOA - CMS will now filter out non-U.S. address when performing a NCOA export when no filter is selected (it automatically has done this if any filter was used) - Dev-350

Product Images - Bulk image imports from CMS Setup were not responding - Dev-330

Column Sorting - Error possible when column sorting in a grid, such as the customer look-up - Dev-345

CMS Invoices - The print task for billing address on CMS invoices (not Crystal forms) could in some cases print the wrong billing address when linked billing was used - Dev-217

ShipRush Integration - Communication with ShipRush would fail if there was a percentage sign in the ship-to address - Dev-332

Shipping Rates - Shipping rates not calculating properly for shipments coming from Hawaii - Dev-349

Installer - Link to the release notes was pointing to the wrong version of Whatsnew.htm - Dev-322 (internal only)

CMS Licensing Service - The service used to automatically update CMS license codes was failing to install. The side effect of this was for customers on payment plans to not automatically receive their updated codes upon payment - Dev-305

Reports - Error running the Physical Inventory report - Dev-306

Reports - Error running the Inventory Analysis report when grouping by Vendor - Dev-316

Order Review - Error when attempting to use column sorting in the email confirmations grid - Dev-108

Order Entry - New warning added when editing a saved order that has associated dropship purchase orders already created - Dev-280

Order Imports - Imported orders with delayed items and the order not set to Bill Delayed will place the shipping charge on the -1 invoice when no items have been fulfilled - Dev-290

Order Imports - Unable to save an order containting a credit card payment whose expiration date is this month - Dev-289

Order Imports - Possible for an Access Violation error to be raised during the automated processing of order imports (during save) - Dev-295

Endicia - Expanded support for the number of customs line items from 30 to 1000 - Dev-266

Installation - Error possible during database update when a scheduled trigger was firing at the same time the update was running - Dev-291

Installation - Possible for permissions to not be properly set for new files resulting in assorted errors when running CMS from the workstation - Dev-270

Reports - Physical Inventory report could fail to run after a CMS update was installed - Dev-286

PCI Admin - Tokenization option now will only be displayed for the processor MPS - Dev-265

Kit Builder - Removed 'Restock at' column and added columns for ' Resupply At' and 'Restock To' - Dev-264

Contact Manager - Errant warning to save customer information when retrieving a candidate from the list - Dev-278

Contact Manager - Added columns for address lines to the candidates grid that shows up when typing a name into the Contact Manager - Dev-279

Order Entry - Recipient Imports - Duplicate recipient names were not being uniquely named also causing the replication of items to all recipients to skip some recips - Dev-269

Returns - Error when trying to return a kit that was sold via exchange - Dev-267

Setup>Payments - Added option to enable/disable Gift Card payments - Dev-273

Setup>Payments - Converted selected grid to checkboxes to accomodate more payment types - Dev-273

Reports - Added Shipping Cost Analysis report under the Reports>Fulfillment menu - Dev-156

Contact Manager - When a customer had multiple orders on the same day, the most recent was not at the top of the list in Order History - Dev-250

Order Entry - Error opening the one-time item dialog - Dev-262 - Converted to's new processing URL in prep for their 2016 switchover. They are currently running in parallel but will remove support for the older URL's in 2016 - Dev-231

Payments - When being prompted if you'd like to use the last credit card used, the dialog now includes the last four digits of the card number to facilitate the decision - Dev-55

Installer - Installation will now warn and abort if the database does not have credit card encryption enabled (PCI and CMS TEN requirement) - Dev-58

Order Review - CMS was unnecessarily prompting for permission to update shipping charges when editing an order. The prompt should only come if certain aspects of the order have changed like items, price, or shipping address - Dev-253

Order Entry - Address Editor was not skipping Honorific if configured to do so in Order Entry Options>Field Navigation - Dev-249

Order Entry - Using Enter or Tab to advance through the fields on the Tracking tab will no longer stop on the Show Inactive Adcodes checkbox - Dev-244

Order Entry - Using Enter or Tab to advance through the fields on the Money tab will no longer stop on the Apply Date field - Dev-246

CV3 - Improved handling of errors due to expired login password - Dev-241

Scheduled Payments - Unable to re-save an order that had an expired credit card in its payment schedule - Dev-257

Contact Manager - CMS was prompting for a customer save if the customer's total spending changed or when scrolling between customers with different total spending levels - Dev-256

Order Entry - Order Source data could be lost if tabbing through the field after initially set - Dev-245

Automated Imports - No order history added to a new customer record created for an order's recipient - Dev-252

Kit Builder - Possible to return too much component inventory to stock if canceling after both stock was reserved and Qty To Build was subsequently reduced - Dev-243

Installer - Included additional Java components for server installs, finalizing the deployment issues related to Dev-226 below

CV3 (public) - Order level Default Ship Method was not being assigned - Dev-239

Order Imports - Removed the fix for Dev-230 ( to have it re-assessed for better handling of product descriptions for one-time items

Multi-ship Orders - Possible for CMS to drop a recipient and for their items to appear on the wrong recipient - Dev-242

Plug-ins - Prepping plug-ins to use a dictionary of plug-in options - Dev-248

Kit Builder - Unable to reduce Qty to Build after stock had been reserved - Dev-238

CV3 (public) - Attribute names were being overwritten by product uploads from CMS. New plug-in option added to suppress CMS from uploading attribute names for existing products (now also checking to see if a product is new) - Dev-218

CV3 (public) - When using automated imports CMS could misidentify a product with attributes as being on backorder - Dev-237

Find Customer - Width of the State column in the search results was defaulting to 50 characters (max field size) which was taking up too much space in the grid - Dev-233

Package grid highlight color for a selected record was too dark to see text - Dev-174

Manifest - Changing the ship method with the arrow key was not properly setting the new method - Dev-181

Verify Imports - Error was raised if doing a customer search by Company while verifying an imported order - Dev-225

Automated Imports - CMS was not using the Order Entry default shipping method setting when an imported order had an unrecognized shipping method - Dev-232

Order Imports - Products that imported with attributes that matched to a product in CMS that was not configured to have attributes was dropping the attribute data (now being treated as a one-time item) - Dev-230

eCMS - Plug-in Options not recognized if there is a capital B (e.g. failing on WEBSERVICEID) - Dev-234

Address Editor - Unable to scroll to the end of a long email address - Dev-212

Database - Email field in tables ADDRESS, CONTACTS, IMPTEMP, VEND have been expanded to 100 char - Dev-213

Database - Changed table name PRODCAT to PRODTAXCAT - Dev-229

Contact Manager - Altering customer credit amount was prompting the user to save (the change is saved automatically) - Dev-216

Contact Manager - Unable to process a credit card for a refund of customer credit - Dev-224

Returns - Switching payment types will now clear the credit card number - Dev-223

TransFirst ePay - Voids responses from TransFirst were not being recognized or logged and CMS reported an error or unsuccessful attempt to void. They were actually successfully processed but CMS was not interpreting the new response format properly - Dev-219

Installer - We are now deploying Java and MapForce files with server installs to facilitate our forthcoming Amazon integration. This results in two new directories under \NewHaven Software for JRE and MapForce - Dev-226

TransFirst ePay - Credits (refunds) were failing to process - Dev-220

CV3 (public) - Order level discounts were not importing - Dev-214

Magento - Converted to multi-threaded order status uploads to speed up processing time - Dev-103

Order Entry - Advanced Product Search was failing to find results based on products' Tech Info and Additional Information (unicode issue). Matching text on the search term will also now display italicized and colored magenta - Dev-198

Inventory Tracking report - Updated to work with database change, IPADJUST table field name changed from ITEM to SKU_ID - Dev-206

Installer - Updated to InstallAware v18 to address rare "insufficient resources" error. It also will be the foundation of our support for Windows10 installs - Dev-207

Kits - Error when partially reducing the quantity ordered of a kit that pulls stock from components - Dev-195

Order Entry - Tech Info and Additional Info product fields were not displaying - Dev-197

Order Entry - Possible to return too much stock to inventory if item was forced onto backorder repeatedly - Dev-188

Order Entry - Access Violation error if Order Entry was closed while the product selection combo was open - Dev-151

Contact Manager - New option to warn of unsaved edits was not recognizing edits to some of the fields under the Profile tab - Dev-182

Automated Imports - New validation check for customer non-zero balance - Dev-142

Product Uploads - Automatic product uploads were not taking place unless the option for order status uploads was also selected - Dev-204

Dazzle - Modified integration to pass Canadian postal codes without spaces or dashed per new spec - Dev-133

Order Importing - Import window can now be minimized to allow for processing in the background - Dev-71

Kits - Error when using a kit that pulled fractional quantities for a component - Dev-195

Batching - Batching window now combined with the Edit Existing Batches window using tabs to separate them. Now supports double clicking to open the corresponding order - Dev-141

CV3 - Product attribute duplicated when importing orders with a sized item (caused item to go onto backorder)- Dev-189

USPS Rates - Updated First Class, Standard Post, Media Mail, and Parcel Select rates in prep for the May 31st USPS rate change - Dev-132

Endicia - Canadian postal codes are now standardized before passing to Dazzle to meet new requirements - Dev-133

Magento - Discontinued items were still uploading - Dev-177

Endicia (international) - CMS was not passing the province data which is now being placed into an expanded State field - Dev-139

Endicia (international) - Now using ISO3166 country codes to specify 'country of origin' for international orders which should result in a more definitive match

Magento - Multi-threading employed for order status uploads to increase speed of processing - Dev-103

Manifest - Unable to click the Close button when there were no packages in the list - Dev-172

CV3 plug-in (public) - Single-attribute products were importing with that attribute showing as both the size and color - Dev-179

CV3 plug-in (public) - Item-level customization data is now mapped into the item's customization field (previously just went to invoice notes) - Dev-163

Invoice Batching - The grid now supports double-clicking to open the corresponding order - Dev-178

MPS - Tokens now managed by the PCI data retention policy or the MPS recommendation of 180 days, whichever comes first - Dev-131

Returns - Dropship items added to a return as an exchanged item defaulted to a quantity of zero - Dev-136

Installer - Removed option to automatically run CMS on completion of update. There is a bug in the new version of the installer software that is causing this option to throw errors so it has been removed for now - Dev-171

Products - Altering the Discount radio button will not save unless other pricing changes are made - Dev-159

Grids - Grid sorting with directional arrows has been added in most CMS grids - Dev-158

Kit Builder - When a kit is built and a component's cost later change, CMS can now find and correspondingly update the lot costs of all kits built from that component - Dev-130

XML - CMS now supports the ability to specify a tax category for items imported that do not match a product in your list - Dev-118

Confirmations - When viewing confirmation emails created for an order, the date was being cut - Dev-109

Order Entry - Payment amount field was locked after authorization. Field will now only be disabled after capture - Dev-161

Order Entry - Credit cards that have been cleared from the database due to the data retention policy will now display the last4 of the card number in place of the card number (last4 is not considered sensitive cardholder data) - Dev-164

Payments - If a payment created a customer credit and that payment was later edited, the corresponding credit was not being updated - Dev-165

Reports - Added "Exclude Zero Stock" parameter (with options for yes, no, or discontinued) to the Physical Inventory, Inventory Analysis, and Items To Reorder reports - Dev-145

Manifest - Duplicated packages were filtered from being displayed - Dev-154

Verify Imports - Columns for failed validation checks will now only display if one or more orders in the Verify Imports queue has failed that check and window will dynamically resize. This window may now also be maximized - Dev-155

Magento - Product uploads could cause the 'Do Not Show' flag to be set - Dev-148

CommerceV3 - The new plug-in for the CV3 public web service was assigning the last SKU's price to the product. It will now use the lowest price of the product's SKUs - Dev-153

CommerceV3 - The new plug-in for the CV3 public web service was not uploading special (sale) prices or their corresponding effective dates - Dev-152

MPS - eCom charges were not defaulting to using the MOTO merchant account - Dev-146

Verify Imports - Column added for Fulfill Date, column for order date altered from date:time to date - Dev-121

Installer - Enforcing choices are selected before allowing Next button to be clicked - Dev-150

Order Entry - Possible for CMS to create Return Lots when deallocating a kit that pulls fractional quantities of a component - Dev-97

Installer - Install Aware software updated to current version - Dev-110/124/143

Order Entry - Possible for an invoice with multiple payments to allow editing of the credit card field (albeit still masked) when editing should have been prevented - Dev-144


CMS Downloads Site