CMS Version 9.0.2 Release Notes

Introduction

CMS 9.0.2 includes the new 2013 UPS rates corresponding to their changes which are effective Dec 31, 2012. FedEx and USPS rate changes will be available in the coming weeks just prior to their effective dates.

When to Install - The shipping rates in CMS will be updated when you install the 9.0.2 update. As such, you should plan the installation of your update to coincide with when you want the new rates to be available in CMS.

Whether or not you have the current rates in CMS you can continue to ship properly with any of your CMS shipping integrations. In every case, the software that prints the shipping label (e.g. WorldShip™ , Ship Manager®, DAZzle®, ShipRush™ , etc.) determines the proper rate for the shipment and is thus how you are billed.

Having the current rates in CMS is often more of a reference. Its greatest impact, though, is for companies who charge their customers a shipping and handling fee based on the actual carrier rate (instead of a spending table or other formulas.) If this is how you charge your customers for shipping and handling, you will want to make sure you have this update installed as soon as you want to start charging your customers based on the new 2013 rates.

9.0.2 ENHANCEMENT DETAILS

2013 UPS Rates - Rates and surcharges updated for the 2013 UPS rate increase, effective December 31, 2012. Details on the UPS rate change can be found on the UPS site HERE.

As expected you'll see increases on both for ground and air services as well as surcharges. These have all been updated in CMS as have the list of zip codes used to determine if an address is subject to a Delivery Area Surcharge (DAS) or Extended Delivery Area Surcharge (EDAS.)

You can review the list of surcharges in CMS under Setup>Shipping>Carriers and Methods>UPS. You're also able to edit surcharges here if you have negotiated rates with UPS. Just fill in the amount and check the box to activate. This override is for surcharges only and not the base rates. Contact us if you'd like to have us integrate your negotiated base rates into CMS.
Bug Fixes and modifications

9.0.2.94

2013 UPS rates, surcharges and DAS/EDAS zips added - 37772

9.0.1.94

Order Imports - If a Product Group component was ordered in addition to the product group, only one instance of the item would appear on the order - 37991

9.0.1.93

Some options in CMS were missing, including Batching for CMS Solo and Standard (regressive to 9.0.1.92) - 37969

Order Imports - Invalid RecipientID when verifying an order - 37988

Order Imports - Importing an order with multiple recipients that have the same name was causing CMS not to uniquely identify them - 37785

Order Entry - When deallocation occurs, as it would when future shipping an item or saving an order as Temp or Proforma, CMS will now also clear back order quantities on items - 37872

Kits - Setup screen for adding components to kits will no longer display other kits (kits cannot be components of kits) - 20745

Order Entry - COD charges were being added to the Shipping and Handling total instead of being placed in the COD charge field - 36943

9.0.1.92

Catalogs - Setting added to Setup>Fulfillment>Import Options to specify default catalog to be used for import order sources - 36336

Catalogs - Print and Export buttons are now enabled by the selection of which catalog to print/export - 35053

Order Review - Corrected issue with too much inventory being returned to stock when removing a forced back ordered item from a saved order where the item was not originally not forced onto back order - 36518

Order Review - Implemented optimizations to improve loading time of saved orders with many recipients - 37784

Customers - Improved how customer flag edits were being handled so that any update problems are better exposed to the user - 36937

Order Entry - Quantity discounts were not being re-evaluated when a product group was added to the order - 34295

Order Entry - Error possible when adding a product group to a non-multiship order - 36784

Order Entry - Enhanced the "1 0 0 trap" (see 9.0.1.84 below) to better handle future ships, proformas, and temp saves - 33856

eCMS - Improved user feedback in situations where a product data upload to CommerceV3 was unsuccessful - 37316

Order Entry - Repaired memory leak when scrolling through orders - 36973

Kits - Kits that pull stock from their components are no longer selectable in Stock Manager - 36793

Kits - When adding components to a kit, you can no longer add the kit parent product to itself - 20745

POS Drawer Session - "Last for this Station" button now functioning properly - 27894

9.0.1.91

Order Entry - Variable kits that contained a mix of inventory and non-inventory items were reporting that the kit must be back ordered - 37839

9.0.1.90

Refunds from Flags and Financials in the Contact Manager were not retrieving the customer's last used credit card number - 37816

Products - When entering an Expected Cost it had become necessary to edit out the $ before the field can be exited. CMS now removes the $ automatically - 37774

9.0.1.89

POS - Workstations configured to operate in POS mode were not always defaulting to the proper POS warehouse - 37436

Order Imports - Possible for imported orders to show as locked after imported - 37714

9.0.1.88

Best Shipping - On imported orders, if the Best Shipping method was specified in the XML in the Package node, it was causing CMS to create a package for each item. This was originally fixed in 9.0.1.86 but the bug was reintroduced in 9.0.1.87 - 37501

9.0.1.87

Variable kits not back ordering properly - 37268

Overhaul of inventory handling for kits - 37435

CMS not decrementing inventory on back order or future ship fulfillment of kits - 37480

Package error possible when saving an edited order (multiship, multipackage) - 37325

Variable kits set to non-inv will not pull stock from kit components - 37510

Possible for CMS to deallocate too much stock when removing a forced back order item from an order - 37574

When fulfilling a variable kit, the components were retaining their package number from the original invoice. Components are temporarily being forced into the parent kits package which addresses most use cases. Further enhancement coming to address situations where components should have their own package - 37605

Future ship and back order fulfillments were not creating LOT_ITEM records - 37655

Virtual packages were not being deleted after their items were fulfilled - 37628

Order Entry - Display issue where CMS could show all packages for all recipients - 36847

9.0.1.86

Order Imports - For orders using Best Shipping, CMS was assigning a unique package to each item. This was a side effect of a fix introduced in 9.0.1.84 - 37501

9.0.1.85

Order Entry - S&H charges calcluated per package were not working. The fix resulted in a rewriting of how charges are calculated and how they can be configured. Shipping methods may now have both formulas and surcharges defined where they used to be mutually exclusive. If the order's price category has a shipping formula associated with it, that formula takes precedence of shipping method level formulas but either can take into account the surcharges. These surcharges are now always calculated per package. Some interface changed were made in Setup>Carriers and Methods to make the selection of both a formula and a surcharge/replace value both possible and more evident - 37446

POS - Point of Sale orders were not properly defaulting to using the specified POS warehouse after the first order was saved - 37436

Order Entry - CMS was allowing access to the quantity field for variable kit components. Quantities should only be editable at the parent kit item level - 37427

Package Exceptions - A new option has been added to disable the new Package Exceptions window in Order Entry. This new setting is found in Setup>Order Entry Options>General>Shipping - 37477

9.0.1.84

Order Imports - Package level shipping method overrides were being ignored - 36902

Returns - Product selection window would disappear if you clicked outside one of the field - 37204

Order Entry - Error saving order with multiple and user-defined payment types - 37273

Order Imports - All recipients on a multiship were being assigned the same shipping method - 37282

Order Entry - An obscure allocation problem was possible when exiting the Quantity field for a stocked item where CMS would not allocate stock. This resulted in the item showing a quantity ordered (1) but 0 sent and 0 on back order (i.e. 1-0-0). This 1-0-0 scenario should only ever be true for proformas (when not allocated) and future ships. A trap is being implemented to catch this situation and redirect the user back to the affected item so the order quantity can be confirmed and allocated before save. This trap will remain in place until a solution to the underlying problem can be found - 37124

Order Entry - Enhanced behavior for multiships so that when a new recipient is added, it will default to using the fulfill/arrival date of the currently displayed recipient - 36782

Order Entry - If a user defined payment was followed by a credit card in a multi-payment order, CMS may offer the option to update the first payment with the card number from the second - 37360

Order Entry>Proformas - Saving an order with non-inventoried items as a proforma was deallocating and never re-allocating - 37432

9.0.1.83

Payments not properly associated with new customers - 37294

9.0.1.82

Fulfillment Manger - Items set to 'require new package' were being allowed to fulfill into the same package - 37258

Variable kits - In some situations stock was being allocated to only the first component - 37259

9.0.1.81

Non-inventory items were not being assigned a warehouse which affected how items were combining into packages and the availability of those packages in shipping integrations - 37224

Order Imports - CMS was misinterpreting the GMT offset that may be included in the XML for imported orders and, for orders that were future shipped, could reduce their fulfillment date by one day - 37226

Deleting a proforma was converting it to an itemless order and a link to that order was left in the customer's history - 32625

ShipRush - Removed roll-up code that was combining like items in label printing - 37236

9.0.1.80

Address Validation - Commercial flag not removed by the Address Validation module when address is residential - 37201

Drop ship items don't calculate shipping and handling charges - 37214

Editing an order with a linked billing payment would change the payment assocaition from the linked parent to the order's customer - 32900

9.0.1.79

Order Entry - With the option for using quanty in the size/color matrix you would receive an error "List index out of bounds" - 37159

Order Entry - With the option for using quanty in the size/color matrix it was possible to have a SKU repeat on the order if the size/color matrix was revisited and some of the items were on back order - 37182

POS - Default warehouse for items was changing back to main warehouse after first item was added - 37166

Order Entry - Shipping charges were not being fully removed for orders when their shipping method was changed to Hand Delivered or Customer Carryout - 37176

9.0.1.78

Internal only

9.0.1.77

Returns - Lot error when returning kits that pull from components - 37089

eCMS - Inventory upload was not properly accounting for quantity on back order - 36530

Order Entry - Assertion Failure error possible if exiting Order Entry after scrolling through the product list - 37097

Order Imports - Back Order All checkbox in Order Entry>Items is now checked for imported orders that were forced onto back order as a result of the corresponding Fulfillment Option - 36952

Order Entry - In unusual circumstances it is possible for a stocked item to be added to an order without stock allocating. This appears on the View Invoice screen as 1 ordered, 0 sent, and 0 back ordered (i.e. 1-0-0). This should only be true for future shipped items and a catch has been implemented to identify this scenario and, if found, will return you to the Items page to confirm allocation for the item in question. This temprorary measure will be used to ensure the anomoly can be addressed by the operator pre-save until we can find the source of the issue and deliver a fix - 37124

9.0.1.76

ShipRush - Further custom label modifications - 37069

9.0.1.75

Endicia International - Items sharing the same harmonization code will now have their customs data combined . This can reduce the number of lines needed on the customs forms - 28429

Returns - Added recipient combo to Returns screen. This combo, like in Order Entry, acts as a filter to display only that recipient's items - 27568

Returns - Error when attempting to return an item on a multiship order - 36791

9.0.1.74

Access Violation when issuing a refund of customer credit to a credit card - 37047

9.0.1.73

Virtual packages not deleting when all of its items have been fulfilled - 36970

Error when attempting to paste rich text (RTF) into customer history - 36933

ShipRush integration - Custom label modifications - 36708

9.0.1.72

Fulfillment Manager - Partial Back Orders are fulfilling without the option being selected to allow partials (regressive to 9.0.1.70) - 37007

9.0.1.71

Products - New product level option called "Requires New Package" which forces such items into a new package when added to an order - 36264

9.0.1.70

Fulfillment Manager - corrected memory leak which could affect larger fulfillment sessions - 36940

Fulfillment Manager - Window that shows all packages that could not be fulfilled was unable to display large lists and was running off the screen and could hide the OK button - 36405

Fulfillment Manager - Error possible when attempting to send an email with no body (e.g. only an attached invoice) - 36939

POS - Possible to get an error when switching in and out of POS mode in Order Entry - 36925

Order Entry - New Back Order All option was not resetting after the save of a new order or clicking the Clear button - 36803

Manifest - Error " is not a valid integer value was possible after dropping a package - 35831

Proforma Orders - Deleting a proforma was causing CMS to save it as a completed order first - 36830

9.0.1.69

Installer - 8 to 9 upgrade - In some databases it was possible that the population of the new Recipients table would have duplicate primary keys - 36891

9.0.1.68

Order Entry - Converting a Multiship to a Normal Order - Removing a recipient will now remove all of that recipient's items as well unless it is the last recipient on the order. When it is the last recipient, the order will be converted to a normal order (non-multiship) and the items from the last recipient are retained now as the buyer's items. If the buyer had no default shipping address, CMS will use the mailing address as the shipping address - 36479

Order Importing - Error message "XML data too large" - 36539

Installer - Database Update -Corrected problem updating Shippers table - 36837

Installer - Database Update - Changelog was failing to convert recipients with invalid address_ids in the ITEMSORD table - 36519

Order Review - Multiships - The Recipient_Order table's shipping charge was not being updated when editing a saved order - 36850

Order Review - Possible to receive a "List index out of bounds" message when editing the shipping address of a saved multiship order - 36719

Order Entry - Adding a sized item to a multiship recipient could result in an error - 36731

Updated Report - InvoiceTemplate-Email - 36197

Updated Report - InvoiceTemplate-SummaryByInv - 36205

Updated Report - Product Sales Detail - 36517

Updated Report - Product Sales Demand - 36756

Updated Report - Lots Received - Now includes "return lot" information - 36686

Order Entry - Items set as "does not ship" were not getting a fulfillment date - 36631

ShipRush Integration - Added options to Setup screen allowing the user to define font width and height as well as the position on the label for the carrier's label - 36708

Internal - Cached master-detail autoinc inserts only save correct link detail data for the current master - 36553

9.0.1.67

Order Review - Package information not available on the Shipping tab unless in Edit mode - 36798

Order Entry - Error adding a product group to a multiship order - 36788

9.0.1.66

Verify Imports - Access Violation error possible when verifying imported multiship orders - 36763

9.0.1.65

Verify Imports - Error adding or editing variable kit components when verifying an imported order - 36544

Order Entry - Back Order All option added to Items tab and Back Order Options window. Selecting will force all items on the order onto back order and will release allocation. Deselecting will allocate to all items on the order as is possible. 36592

Multiships - Improved handling of deleted recipients on multiship orders - 36707

Printing - Access Violation possible when printing Crystal forms set to print only based on certain payment types - 35085

Order Review - Scrolling from a multiship order to a non-multiship would show the recipient scrolling or selection combo boxes on the non-multship order. Subsequent editing and saving could result in errors - 36258

CommerceV3 - Corrected statuses on order status uploads to CV3 so they are Processing or Shipped - 36427

Order Entry - Larger multiship orders could result in slower response times when adding new items - 36582

Order Entry - Shipping tab was not displaying package data unless you were in Edit mode - 36692

Order Entry - CMS was prompting empty Package Exception windows under certain conditions - 36693

Order Entry - Deleting a saved package could cause an error - 36713

Setup - Added option for Scheduled Emails to Auto Todo configuration screen - 35151

Order Entry - When a product is changed to a non-Product Group Header status, its Product_Group_ID field must be cleared, else problems can result in Order Entry - 36332

Payments - Loading previous charge card info into Order Entry/Apply Payments that had the corporate flag set fails to set the corporate flag as "checked", and so subsequent saves set the flag to "false" - 36485

Order Review - Package Exceptions now disabled when editing shipped orders - 36620

Order Imports (not using Automated Imports) were in some cases creating two customer history entries - 36641

9.0.1.64

MPS - CommerceV3 was incorrectly placing the ProcessData in the RefID field which was causing authorization reversals to fail. CMS is now ignoring this bad data when processing a reversal - 36315

9.0.1.63

Invoice Printing - CMS invoices (not Crystal) were not printing the Items section of the form - 36362

Confirmation Emails - The merge task 477 representing the items ordered list was not functioning (related to the above fix) - 36610

9.0.1.62

Order Imports via Automated Imports were in some cases creating two customer history entries - 36453

Order Entry - A non-shipping product will cause an "is not an integer" error when changing either the fulfill or arrival date at the item level - 36472

9.0.1.61

Fulfillment Manager - Forced back orders were not fulfilling into the same package as non-forced back orders - 36413

Automated Imports module - The exception column for AVM would disappear after verifying your first order - 36314

Order Review - Editing an older multiship order could cause recipient_id errors - 36379

Order Entry - If you had an overpayment that would create credit but then resolved that overpayment before save, CMS was still warning you that a credit would be generated - 36421

9.0.1.60

CommerceV3 Plug-in - Modified the CV3 Plug-in to no longer map the AcqRefData to to Chargeinfo.TransID field in the database - 36363

eCMS - For a workstation configured to automatically connect to your stores to download orders, CMS will now raise a new Automatic Download window so you can choose to let it run or postpone - 35333

9.0.1.59

Order Entry - No zones or warehouse displaying in the package grid on the Shipping tab - 36342

Order Entry - Invalid Recipient ID error possible when editing or verifying a multiship order - 36321

MPS - Added AcqRefData and ProcessData nodes to CMSXML.xsd and altered the CommerceV3 import of MPS data so it is no longer placing the AcqRefData into the CMS TransactionID field - 36363

Downloads site - Altertered how CMS connects to Support Downloads so it can always pull the latest WhatsNew.htm corresponding to the version of CMS running - 35653

9.0.1.58

New print task: Invoice Tracking Numbers (All) - 36172

New Crystal invoice template: InvoiceTemplate-MS-BC - 36195

Customer Letters - URL merge capabilities added - 36206

Order Entry - Fulfillment Date fields now restricted to only allow date input - 35740

Order Entry - Replacing a recipient by using Find Customer will now ask if you want to update the Recipient Display field - 30955

Order Entry - Date change confirmation window - removed option for 'existing items' in cases where the recipient has no items - 36001

=============================================================

To download 9.0.2 now click HERE

=============================================================