CMS Version 10.0 Pre-Release Notes
(subject to change, more may be added)

Introduction

CMS version 10.0 (specifically 10.0.1) includes important changes to help you meet PCI requirements for the next several years. We've done this by having CMS validated against the recently introduced 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 10.0 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.

READ BEFORE INSTALLING 10.0.1

- Important information to prepare you for the transition to your new version of CMS.

For All Updates from 9.x or earlier -

Encryption - The Encryption option in PCI Administration must be enabled before installing CMS 10.0. 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. If so, you're set and there's nothing more you need to do (no need to re-encrypt).

If instead the button says "Encrypt," this means you have never encrypted your card data (and need to). We recommend you run encryption overnight while everyone is out of the system.

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

CMS 8.x or earlier updating to 10.0.1 - 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 v10, you must familiarize yourself with the changes from v9 as well. Database changes occured 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 on CMS 9/10.

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

MINIMUM SYSTEM REQUIREMENTS – CMS 10.0.1 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 - During the installation of version 10.0.1 you will be asked to enter your 9.0 release code. You can access your 9.0 release code by logging into the Support Downloads section of our web site. Just enter your customer number and zip code to log in.

Server updates - The initial server update from 9.x to 10.0.1 will run as quickly as most other updates. If, however, you are updating from version 8.x or earlier, this update can take quite a bit longer than normal.

Workstation updates - Workstation updates are required for any Windows 8.x machines after your server update to CMS 10.0. 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
Microsoft has announced they will no longer provide support and updates for Windows XP. This is a fairly critical situation. XP will no longer receive security patches which, aside from the obvious security threats, also means that you cannot be PCI compliant.

Our recommendation is to move to Windows 7 Professional or 8.1 Pro. The Pro versions of these operating systems is required for joining a network domain, which is needed for running CMS on a network. For a complete list of operating systems we support for use with CMS, see our System Requirements wiki article.

PCI Compliance - CMS 10.0 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. 9.0.6.159, 10.0.1.123). You can read more about our versioning methodology HERE.

You can find CMS versions 7.0 through 9.0 on the PCI Council’s list of Validated Payment Applications HERE We are currently submitting CMS 10.0's 3.0 validation to the PCI Council and expect its listing to be available on their site summer 2014.

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

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 Authorize.net.

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 10.0. 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.

10.0.1 ENHANCEMENT DETAILS

  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 10.0 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 10.0 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 - https://www.pcisecuritystandards.org/pdfs/PCIDSS.pdf

    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

    • Threshold in account setup to establish how much of a gift card balance can be returned to cash in POS

    • 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 but, instead of being stored on your server, it is being stored on MPS's server 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 learning more.

    Tokenization is currently not offered by TransFirst or Authorize.net although Authorize.net does have a solution (CIM) which accomplishes much of the same thing that we expect to evaluate in 2015.

  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 schedule 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 10.0 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 encounted.

    • 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 imact all order imports, from file or eCMS integraton.

    • Override Prices - The setting that allows you to choose between using the imported file's product prices vs CMS's internal pricing had been a global option that applied to all import order sources. As one of the many changes we've made and been making to CMS to make it better suited to working with multiple websites and sources of orders, we've moved this setting to the order source level. 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.)

  6. CommerceV3 (CV3) New Web Service

    We have completed our migration to the public CV3 web service. For ~10 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(s) 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.

  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 10.0, we have modified our eCMS Magento plug-in to accept credit card dataThis 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.
    • Future ships supported via custom fields feature
    • Improved order status uploads
    • 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
    • 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.

      Noting here that 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.

    • 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. Product 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
      999

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

    • Kits withing 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.)

  12. 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 10.0 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.

    • Improved component filtering

  13. 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)

  14. 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

  15. 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.

  16. 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 anyhere 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.

  17. 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 10.0 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.

  18. 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 http://screencast.com/t/5q2i0uPGIh

    • Keyed imports
      • Integrations have been completely redesigned to dramatically improve performance. No need to do anything, it will just run faster in 10.0. 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.

  19. 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 screenshot 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 pring shipping lables 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 10.0.

    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 explicitely 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.

  20. 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.

  21. Refund Enhancements

    22. 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.

  22. More 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 HTML means of making Help available. http://help.newhavensoftware.com

    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.

  23. Windows 8.1 and Server 2012

    24. 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.

  24. Reports

    25. Physical Inventory - This has been overhauled to enhance allocation reporting, specifically to improve performance and better account for allocations for 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. This report is possible due to strides made in our shipping integrations over the last several versions that help facilitate getting the actual shipping costs from the carrier back into CMS (and making sure that CMS does not replace those costs on any order edit).

  25. Bug Fixes and modifications