CMS Version 9.0.5 Release Notes

Introduction

CMS 9.0.5 introduces some greatly anticipated enhancements that could have an significant impact on the efficiency of your operation. We're excited to bring these new features to you. If you are already running 9.0.5, you can jump straight to the list of Bug Fixes otherwise read on for all of the details...

IMPORTANT - Updating to CMS 9.0.5 from 8.x or earlier - 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. Please contact us to discuss if you have any questions or concerns.

READ BEFORE INSTALLING 9.0.5

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

Installer Changes:

The installation process for 9.0.5 has been changed slightly as described below. You can also watch the installation video for a review of how the new installation process works.

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

CMS 8.x or earlier updating to 9.0.5 - 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.

CMS 7.x or earlier updating to 9.0.5 - We recommend you update to 8.0.6 before upgrading to 9.x. Please refer to the 8.0 Release Notes for important information and details on upgrading to 8.0 before installing.

Release codes - During the installation of version 9.0.5 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. Once there, just enter your customer number and zip code to log in.

Server updates - The initial server update from 9.x to 9.0.5 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 not required for upgrades from 9.x to 9.0.5. They are recommended for updates from 8.x or earlier.

Prerequisites - If you are not already running CMS version 8.x, we do recommend updating to 8.0.6 before upgrading to 9.0. This is not a requirement but there were a lot of changes and special steps required for version 8 and it would be easier to perform this update separately.

Minimum System Requirements – CMS 9.0.5 did not introduce any new system requirements. Our system requirements can be reviewed on our CMS System Requirements wiki page.

PCI Compliance - CMS 9.0 has been successfully reviewed by Coalfire Systems to also meet the PA-DSS 1.2 standard and our application for listing has been accepted by the PCI Council. You can find CMS 7.0, 8.0, and 9.0 on the PCI Council’s list of Validated Payment Applications HERE

Integrations - No changes to our standard CMS integrations in 9.0.5. All will continue to work as they had including CommerceV3, UPS Worldship, FedEx Ship Manager, Endicia/DaZzle, ShipRush, MPS, TransFirst, and Authorize.net. Comments on Endicia enhancements are below. Integration with Magento has been enhanced and is discussed below.

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

To download 9.0.5 now click HERE

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

9.0.5 ENHANCEMENT DETAILS

  1. Hold Until Complete - Have you ever wanted to ship an order complete (instead of shipping some items now and the remainder when the back ordered items become available)? Would you also like to retain stock allocation for your items that were in stock so they'd still be available when the back order was ready to fulfill? Hold Until Complete (HUC) is what you've been waiting for!

    We intentionally call this Hold Until Complete instead of "ship complete" because this solution makes use of the Hold functionality already built into CMS. You end up holding the order as-is, stock allocation and all, until the remaining items are available. When they are, you just fulfill the back order, the items fulfill onto the -1 invoice with the original items (no -2 fulfillment invoice) and your order is released from Hold for further processing (approval, printing, shipping, and capture.)

    Using it couldn't be easier as CMS has automated it all for you. Just turn on the setting in Order Entry Options>Items for HUC and CMS will automatically put any order onto HUC if it contains a mix of in-stock and back ordered items. Employees with the new permission to alter this Hold flag can override it pre or post save (on the View Invoice tab) to allow the in-stock items to ship right away instead. Alternately you can leave the option off so CMS will not automatically set it and just choose the option manually as orders are entered.

    HUC is really a special type of hold that only applies to orders with back ordered items. Like oither fully delayed orders (back orders and future ships) CMS will default the intial payment amount to $0 and CMS will create a payment for the full amount when the order is fulfilled. You can, however, set payment amount to a non-zero amount if you wish to take a deposit on the order. This special type of Hold (HUC) will allow payments to be processed in Batch Approvals and EDC where other Hold types are intentional removed from further processing until the hold is removed.

    HUC does impose a few restrictions on HUC orders. CMS will not set the HUC flag, or let you set it, for orders that have future ship items on it, returns or multiple invoices. You may also not process a return against an unfulfilled HUC order (since CMS was told it needed to ship complete) so the HUC flag would have to be removed by an operator with proper permissions before a return is allowed. Read more about HUC HERE.

  2. Order Locking - We've implemented a powerful new locking mechanism in CMS to prevent multiple edits from occurring to the same order at the same time. This concept extends beyond just manual order edits though. This also covers back order and future ship fulfillment, batch approvals, and batch capture (EDC). All of these processes will now check for an order lock and, if present, will skip processing. Additionally, these processes set locks of their own so, while the order is being processed, it would prevent other users or processes from modifying the order.

    If a lock is encountered, you'll be presented with a message indicating which user/machine has the order locked. This is true both for individual order editing as well as the batch processes. For credit card processing, where it is most critical, we also display a new field called Last Message in the Batch Approvals and EDC screens so you can see that this charge was skipped even after the processing message was closed.

    Locks will clear automatically as edits and updates are completed. If necessary, you can also force all locks from a workstation to be cleared by exiting CMS. When the database service restarts, it will also clear all locks from all connections.

  3. Batch Approvals and EDC windows - These two screens include enhancements resulting from both of the above enhancements.

    • Last Result field - new column in the grid for both screens showing last result, either from the processor or a lock
    • Drag to resize - Both screens can now be resized, just grab a corner and expand to the desired dimensions. This allows for easy viewing of the Last Result field. Some other minor screen changes and button positioning were made to facilitate this.
    • Limit to only X - Normally when processing Batch Approvals, all charges displayed would be processed. This new option lets you set a threshold of the number of charges to process. Normally authorizations are a pre-requisite for printing invoices or pick-tickets so this option can allow you to control how many orders to release into the warehouse. While you could do the same thing with print batching options, this one ensures the customers card is not authorized first and is most useful if you have long shipping back logs and want to ensure the authorization is obtained when you have a reasonable change to ship/capture before that auth expires.

  4. Kit Builder - There are several types of kits that CMS supports, one of which is pre-assembled and has its own inventory (as opposed to pulling from component stock real time like other types of kits.) Pre-assembled kits require a fair amount of extra work when you want to build more. Traditionally you'd have to manually decrement the stock levels from all of the components (a real chore if the kit has a lot of components) and then receive stock into the completed kit...but no more!

    Kit Builder provides a great interface to help you:

    • decide which kits to build
    • see which kits are built from which components
    • see how many you could build
    • see how many you have in stock
    • see how many are on back order
    • streamline the process of building kits

    Kit building can be done in a single or two step process. This starts with the creation of a "batch" of the kit(s) that you want to build. From there you can either build them automatically or reserve stock (decrementing stock from components), print a work-order for the warehouse to pick/build the kits, and then come back to CMS to confirm the actual number built.

    In addition to automating all of the stock decrementing and receiving, Kit Builder will provide a paper trail for your work. Records of inventory adjustment (components) and lots received (kits) will both include a notation that it was done by Kit Builder and via which batch number. The lots for completed kits will also have their cost automatically calculated based on the sum of the component costs.

    Full instructions can be found in our Kit Builder wiki article.

  5. License Update Utility - When logged in as PCI Administrator a new option under Administration can be found called Licensing. Here you can click a button "Update CMS Licensing" to obtain your latest CMS release code without having to exit CMS or install an update. This option is only available if you've installed the CMS Licensing Service, an option available during your 9.0.5 update.

  6. Magento Integration expanded - In 9.0 we announced our Magento shopping cart integration was being released into beta. As we progress with live clients, many enhancements have been added. An overview of the capabilities of this integration can be found on our Wiki.

  7. Shipping Integrations improvements - Your CMS database includes a table called External_Shipping that is provided specifically for use with shipping integrations. This table allows that software to "write-back" to CMS with information like shipping cost, how it actually shipped, tracking number, and shipped date.

    8. This table has been expanded to work better with multi-carrier shipping systems or fulfillment services where before it would only work well with the shipping systems provided by the major carriers. It also now supports USPS shipments which was previously only possible through Endicia integrations.

    New logic was added not only to handle the RDI flag but to make better decisions on if a shipping method in CMS should be replaced with that from the external system (only when there is an exact match) and if multiple matches are made, which of those to use (whichever one is already on the order, if any.)

    New fields include:

    • RDI - Residential Delivery Indicator (residential or commercial) and, if set, CMS can use this to properly indicate UPS Ground Residential or Commercial (all other methods simply have a residential flag)
    • External_ID - Data fields only, reference number from the external system if needed
    • Shipmethod - Carrier agnostic field where the service level used can be specified
    • Carrier - The carrier for the shipmethod (note that these two fields would be used in lieu of the carrier specific fields found earlier in the table)
    • Package_Type - Data field only, could be used for indicating if a package was letter, box, tube, etc.
    • Package_Count - Data field only - how many packages in the shipment
    • Item_Count - Data field only - how many items in the package
    • Rated_Weight - Data field only - applies to dimensionally rated shipments

      The size of the field in the External_Shipping table for UPS_SHIPMETHOD has been increased from 20 to 50 characters (to facilitate the new Expedited Mail Innovations method).

  8. UPS Mail Innovations supported - We've added a new UPS service level called "Expedited Mail Innovations" which is one of the contracted services offered by UPS (CMS already supported the others.)

  9. Support for Adam Scales - Added support for the Adam brand shipping scale model CPWplus. This is an inexpensive alternative to the normally pricey scales that can be used for both letter and package weights (most scales used for package weighing are not sensitive enough to also be used for weighing letters in ounces.)

  10. Shipping and Handling formula improvement for free shipping - The setting to exclude products from S&H calculations in the spending table now also applies to the % Over option. If you use a spending table for your S&H, it is very common to use it in conjunction with the % Over option since this option picks up where the spending table leaves off. Now both of these S&H formula options can recognize when a product should have free shipping.

  11. Email Matching for Imports - There is an option in Setup now for whether or not you'd like CMS to try and match an imported order to an existing customer by their email address (only). If used, CMS will only make this match if there is a single customer in your list with that email address. If there are multiple matches, it is no longer considered a unique match at which point CMS will step back to its traditional matching logic.

  12. Replacing an Order's Customer enhanced - As described just above, CMS employs matching logic to help connect imported orders to existing customers in your list. While this logic is quite good, there are situations where it fails to match to the right customer or perhaps any customer. This is simple enough to resolve by clicking Find Customer when verifying the order but, when that customer was retrieved, it was replacing the order's addresses with the default addresses from the retrieved customer.

    The enhancements in 9.0.5 include giving you the option of which addresses to use, those from the order or from the customer, or cancel the process altogether. These enhancements come into play any time you click Find Customer for an order that already has a customer as well as any imported order.

    In addition to the addresses, CMS will also warn if the salesperson or price category for the order will be altered as a result of replacing the order's customer with Find Customer.

  13. Performance Improvements - Significant enhancements have been added to Order Entry to improve performance for larger orders, those with hundreds of items, packages, and/or recipients. These orders will be faster to load, navigate, and save. These large orders will still have a noticeable lag but will be vastly improved over previous releases.

  14. Tech Info Allows Full Formatting - In the Products window, under the Tech Info tab, you'll see you now have full word processor capabilities for creating text about your products. This text is available to your operators in Order Entry by clicking the Tech button.

    Another tab has been added here as well for "Additional Product Information" which is unformatted plain text. This would be the field to use if you're storing information about your product for use with other systems, like one that produces your printed catalog. This field is plain text where Tech Info is in an RVF format.

  15. Inactive Catalogs - In Setup, if you lift the Active flag on a catalog, CMS will check to see if there are any unfulfilled requests for this catalog. This is useful because outstanding requests for inactive catalogs cannot be fulfilled/completed.

  16. Better Handling of Discontinued - The Setup option for hiding discontinued items in Order Entry has been reworded to reflect the new behavior which is: 'Hide discontinued out of stock items from product selection lists'. In other words, with this option on, you can continue to see and sell discontinued items until they are out of stock. You may have not used this option in the past due to the fact that CMS would have hidden the item even if in stock. You might reconsider using this option now (CMS must be restarted after altering this setting before it will take effect.)

    Other related changes include:

    1. Discontinued items cannot be back ordered or future shipped. This is due to limited availability and that back orders and future ships do not allocate stock so CMS will limit discontinued items to only be allowed for normal allocated sales.
    2. One time items may not use the same product code as a discontinued item.

  17. Order Entry Improvements :

    • Back Order Options (Items tab of Order Entry)
      • When entering the BO/Options for an item, CMS will not always default to fulfilling X (the first radio button)
      • When adding a back ordered item to the order, and the back order options are presented, if you click Cancel the item is removed from the order. If, however, you are editing the B/O Options for an item and hit Cancel, it will simply cancel your changes and the item is not removed.
      • In B/O Options, if you had selected Back Order All and then select a radio button for Fulfill X or Change Amount Ordered To X, the Back Order All Items On Order checkbox will be removed.
    • Multiship Cancel - If you click the Multi-Ship button and do not want to proceed as a multiship, you can click the new Cancel button to revert immediately back to a normal order. (this is also possible by deleting all recipients on the order)
    • Clicking Edit in Order Entry will now leave you on the tab you were viewing (used to jump to View Invoice)
    • When reviewing a -2 or greater invoice and then retrieving another order, CMS was trying to jump to the same invoice number for the retrieved order. Now when retrieving an order from any invoice, it will jump to the -1 invoice of the newly retrieved order.

  18. Order Imports - Payment types in XML are no longer case sensitive. For example - Visa can be VISA, visa, or Visa.

  19. Order Exports - New field for Items Ordered : Product's Vendor SKU - This field provides the primary vendor SKU associated with this product.

  20. Column Sorting - In the Fulfillment Manager, you may now use column sorting in any of the grids by clicking on the column header/name - 34554

  21. Emailing Statements - The option to include a statement as an attachment to a customer email has been restored and is available under the Attachments and Options tab when sending an email from the Contact Manager.

  22. Reports - Physical Inventory - Corrected issue with allocation not including kit components allocations from kits that pull from components. Also added kit components to the optional Detail sub-report. Note that if you have kits that pull from components, this report will now take longer to run.


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

To download 9.0.5 now click HERE

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

Bug fixes and modifications

9.0.5.156

Order Entry - If CMS was configured to capitalize all names/addresses as they were entered, orders imported in mixed case could create customer records that had a first name in all caps and a mixed case last name - 38434

Fulfillment - When fulfilling orders it was possible for incorrect packages to be created, either too many packages or packages would have the incorrect weight which would case Best Shipping rules to assign the wrong method - 42278

HUC - Fulfilling an HUC order with the virtual packages option disabled would cause the package to drop from the order - 42272

POS - Setting for default shipping method for POS was not saving - 41438

Multi-ships - Recipient phone numbers were disappearing on save - 42254

9.0.5.155 - Internal Only

9.0.5.154

Order Entry - When editing an order you will no longer be able to delete a line item that has been fulfilled on another invoice (e.g. back order or future ship fulfillment.) Such items must instead be returned. Items fulfilled onto the same invoice, as in the case with Hold Until Complete (HUC), can be deleted and this delete will remove both the ordered and fulfilled records for that line item - 42124

Order Entry - Standardized use of Alloc_qty, Cur_sent, and Fulfill_dt in table ITEMSORD to ensure alloc_qty is sent consistent with sent_qty while cur_sent is only maintained on the parent (usually invoice 001) item. This will correct some reporting issues (Physical Inventory report, allocated qty) - 42145

9.0.5.153

Scheduled Emails - Scheduled emails (previously known as Survey Emails) were being created for customers without email addresses. Having an email address is now a prerequisite, as it has been for order and shipment confirmations emails - 40591

Find Customer - Searching for a customer by phone number would display the same customer multiple times if that phone number had been used multiple time (e.g. billing, mailing, and shipping address). Results on phone searches are now unique by customer number - 24361

Kit Builder - Removing a reserved kit from a batch places the reserved inventory back into stock. This process was also increasing the received qty of the lot it was restocking - 42099

Order Entry - Setup option added to allow order level discounts to be applied to items that also have line item discounts. This setting is found in Setup>Order Entry Options>Money - 33469

Order Entry - Back order confirmation window was coming up multiple times when changing warehouse for a back ordered item - 41445

Order Locking - The Options button on View Invoice in Order Entry will now look for and set order locks, preventing edits from other users while performing the operations in this section - 41520

Exactor - Added configuration for "Nexus States" in CMS Setup>Company. This is used only with tax api integrations (e.g. Exactor). CMS will only submit tax calculation requests for nexus states to the tax service. For non-nexus states, CMS will not require that the Get Tax button be clicked as a condition of order saving - 41517 and 41727

Returns - Added Discount Reversal field to the Order Summary column and added safeguards to ensure proper calculations on complex orders with multiple returns/exchanges - 42033

Unshipped - Orders on any type of Hold are now filtered from the unshipped orders list - 32827

Bad Debt - Can now be set in or out of edit mode and does not require saving after setting when set outside of edit mode - 26196

Bad Debt - Improved display on View Invoice to prevent conflict with other side bar messages - 41521 and 41604

9.0.5.152

eCMS - For kits that have their own stock (i.e. do not pull from component inventory real time), CMS was uploading the available stock level as if it pulled from components - 35972

eCMS - Kits that pull their stock from components are now being properly flagged for updated stock level uploads when the stock level of any of the components change - 39258

Kits - Products set as "Kit Component Only" were being displayed in Order Entry. Normally this setting should suppress these items from being selectable in Order Entry - 41655

Authorize.net - New option added in PCI Administrator to allow emailed charge receipts for POS orders. For non-POS orders there is a setting in your Authorize.net admin to indicate if you want charge receipts emailed but there is no such option for charges processed through a POS account. The default in CMS is to not send emails but, if you wish to continue to send them, as has been occurring, you can enable this option - 39830

Best Shipping - In instances where CMS recreates the packages for an order (possible after edits or fulfillments) the logic for Best Shipping and the assigning of shipping methods by weight was not being triggered. It will now take place immediately after any repackaging - 42000

Scales - If you were using a scale with the CMS Manifest and then opened the Products screen, where weighing is also an option, an error would be raised since both forms were trying to access the scale at the same time. The Manifest now has priority and the scale will be unavailable in the Products section while the Manifest window is open - 41769

PCI - The routine that runs nightly to enforce your selected data retention policy logic has been enhanced so that a credit card number will only be cleared from the database if it is captured (and matches other criteria such as number of days and if the order is not fully fulfilled.) While unlikely, it was possible for an order to be fulfilled after the data retention policy time period and, if that card was not captured the same day it was fulfilled, it could have been deleted before it was captured - 38808

9.0.5.151

Variable Kits - When future shipping a variable kit, the date was not being assigned to the kit header or component - 42024

Order Entry - Unable to select the Multi-Ship button on a new order following the save of a multiship order - 41845

9.0.5.150

Kits - Possible for errors to be raised when attempting to deallocate a kit that pulls its stock from components. Scenarios include returns with the Restock option and saving as Temp or Proforma without allocation - 39337

9.0.5.149

MPS - Authorization reversals and the voids of captured transactions were failing due to a change at MPS where they no longer can accept non-alphanumeric characters (CMS has long used a hyphenated order-customer number for invoice and reference numbers.) Removed all non-alphanumeric characters from the invoice/refno fields - 41580

9.0.5.148

Proformas - Shipping formula calculations based on weight or number of packages was not properly accounting for the order's packages. This also had ramifications on shipping charge calculations for orders that were a mix of stocked and delayed items - 40613

Mail List Exports - CMS was not recognizing edits to the destination file name after the first export in a session - 25203

Exactor - Unable to save a return with no items - 39470

Scheduled Payments - Business days were always being factored, regardless of user setting. Additionally when the scheduler code adjusted for business days, it didn't re-adjust for the next cycle so date-creep could result - 40086

9.0.5.147

MPS - Increased the size of the ACQREFDATA field in the CHARGEINFO table from 50 to 150 - 41580

Returns - If returning an item to a warehouse other than the one it was sold from, the item was not being properly restocked in the alternate warehouse and was possible for the Sent Qty on the item to be 0 - 40596

Proformas - A proforma that consisted of only dropship or non-inventory items was not prompting for allocation when saving as a completed order causing the Sent Qty to remain at 0 - 41389

Proformas - Addressed problem where packages were not being retained for saved proformas and in some cases were not created when the proforma was saved as a completed order - 40572

9.0.5.146

Vendors - Added fields for Vendor Notes and Minimum Order Amount - 41378

Staging - Added multi-select capabilities to the shipping method combo box - 40770

eCMS (all) Plug-ins

Magento Plug-in - Added support for gift message (requiring use of the v1 API data) - 41427

9.0.5.145

Batch Approvals - Added Order Date column to the grid and the ability to column sort. The sort order in this grid controls the sequence in which the charges are processed. Particularly useful when used in combination with the feature in Batch Approvals to limit the number of transactions to process, giving you control over which charges to process and thus release into the next phase of the fulfillment flow. When sorting by order number, charges without an order number (e.g. payments not applied to an order) will always be at the top of the list to ensure they are processed - 41179

9.0.5.144

Kits - Packages were not being assigned to kits in Order Entry (adding to solution in 9.0.5.131 under ticket 40488) - 41400

9.0.5.143

POS - IMPORTANT - Point of Sale orders placed using the free POS feature of CMS were not getting set as shipped automatically on save. The solution to this required moving the setting of Default POS Shipmethod from the POS Module tab in Setup to the Point of Sale tab in Order Entry Options. This option must be configured before placing POS orders with or without the POS Module. You must have one or more shipping choices configured to use the service level "Customer Carryout" for the carrier "Other". The Default POS Shipmethod selection box is filtered to only allow customer carryout methods - 40414

Proformas - Proforma orders that consisted exclusively of dropship or non-inventory items would not prompt for allocation on edit and would not set Sent quantities or packages on save. Note: You should answer Yes to this allocation prompt, even if all items are dropship or non-inventory, if your intent is to save the order as Complete in this session - 40613

Order Review - Added a safeguard in Order Entry to disable the Options menu when in Edit mode to ensure that any edits made via Options are not lost - 35087

9.0.5.142

Order Imports - CMS was not importing an order if it did not have a shipping address - 41314

9.0.5.141

NCOA - Reverted change implemented in 9.0.5.136 (RT 40781). We were able to get Peachtree to commit to supporting the 589 length return file to ensure compatibily with all versions of CMS. Proper record length should be 589 (587 in their layout report.pdf plus CRLF) and a notes/info field of 22 bytes - 41269

Order Imports>Yahoo - Corrected a file processing problem when importing orders from Yahoo stores - 41278

Help - The updated v9 Help file was not being installed and the v8 Help file was being installed instead - 41186

9.0.5.140

HUC Payments - CMS will now default payment amounts to $0 for Hold Until Complete orders. This is done by default now since the fulfillment of the HUC order will result in the creation of a single full payment for the entire order. You may still override this and enter any desired amount if you wish to take a downpayment on the HUC order. This $0 default applies to all hand entered HUC orders and, for imports, CMS will also automatically reduce the payment amount to $0 for any uncaptured charge card or echeck payment - 40412

9.0.5.139

HUC Packaging - When fulfilling a Hold Until Complete (HUC) order, if it was fulfilled on a date later than the date entered, it would place the fulfilled items into a new package when the desired behavior is to allow the items to fulfill into existing packages (provided all other packaging rules are met.) An exception for HUC has been added to the packaging logic which will allow items with different fulfillment dates to add to the same package. In other words, you should have the same packages after an HUC fulfillment as you would have had if all the items had all been available during the initial order creation - 40413

HUC EDC - Payments applied to Hold Until Complete orders are allowed to process in both Batch Approvals and Batch Capture (EDC) sections. HUC orders should normally have a $0 payment (see 9.0.5.140) on the initial save and a full payment is created on fulfillment. You may, however, take a down payment on the HUC order to allow it to be partially or fully paid in advance of the fulfillment. This change will now allow that down payment to fully process - 40412

HUC - Added a safeguard to ensure that the Hold Until Complete flag can only be manually selected on orders with at least one back ordered item - 40053

Packaging - CMS was allowing back ordered items and in-stock items to be placed in the same package for imported orders - 37856

Order Entry - Editing a saved order and changing the size/color for an item was not properly restocking the original SKU or allocate the new SKU. This works as expected pre-save but not for editing a saved order. The ... button which is used to open the Size/Color selection window is now disabled after the order is saved. Edits to SKU's will require removing the original product and adding then adding the new product/SKU to the order to preserve proper inventory control - 40905

Products - Added field to the Inventory tab of Products for Minimum Order (quantity) which will also be displayed in Purchasing on the Items tab - 40383

Purchasing - Added display fields for In Multiples Of and also the new Min Qty field (see above) - 40383

Purchasing - Fixed an error message loop that would occur if you re-selected the same item (on the same line) where it would warn you that the item already existed on the PO (a PO can only have one instance of each SKU) - 40383

Contact Manager>Credits - When attempting to refund a customer credit from the Contact Manager, the Issue Refund button was not enabled for credit card payments unless you entered the refund amount first - 34107

Products - When scrolling in the product list and there was a kit and a product group adjacent to each other it would raise an error "Cannot perform this operation on a closed dataset: - 40765

eChecks - eChecks are only processed as a single step transaction (essentially authorized and captured at the same time) so we've made changes to Batch Approvals to all these payments to auth/capture in a single transactions even if the credit card payments are only authorizing - 40992

9.0.5.138

USPS Priority Mail Express - The US Postal Service has re-branded Express Mail and it is now known as Priority Mail Express. All references in CMS to Express Mail have been renamed to match the new naming convention. This change will not impact the integration with Dazzle but CMS is compatible with the new version of Dazzle should you decide to update it (Endicia calls the new Dazzle version an optional update) - 40670

Order Entry - The Multiship button was disabled for customers that had no first and last name. CMS requires a customer be selected before allowing the order to be converted to a multiship. CMS is now employing the same logic used elsewhere to determine if the basic element of a customer are present which includes contact name or company name and a city - 40953

9.0.5.137

Scales - Adam brand scales were not returning a weight after the first weight had been received by CMS. We've also added logging of serial scale communications to help troubleshoot future issues. This logging (file name - ScaleDebugLog.txt) can be enabled in Setup>General>Workstation Specific>Scales and Scanners - 40826

eChecks - Added option to unlock merchant account info which is otherwise locked after initial configuration - 40880

POS - Users of the free POS options in CMS (not the POS Module) were unable to edit POS orders after they were saved. They can now be edited the same as non-POS orders. The POS Module will continue to enforce editing controls on POS orders so that they can only be edited the same day they were created - 40438

9.0.5.136

NCOA - CMS now accepts Peachtree's layout of 590 bytes (up from 589) - 40781

9.0.5.135

Order Entry - Unable to select Multiship for an order with a new customer - 40750

Order Exports - Extra items ordered lines were being exported for invoices with fulfillments - 40598

9.0.5.134

Scales - Serial scale taking too long to respond or not responding - 40209

Batch Approvals - The credit card processing option in PCI Admin>Electronic Payments>Options for "Process Only Shipped by Default", which was designed to only default the setting in Batch Captures (EDC), was also defaulting the setting for Batch Approvals - 40724

9.0.5.133

Batch Approvals - Error opening Batch Approvals if you were only configured for eChecks and not credit card processing - 39631

Order Entry - If you discarded an unsaved order by clicking Retrieve, any items allocated on the order were not restocked - 32541

Gift Notes - Print task for printing gift notes on CMS invoices (not Crystal) was not functioning - 39377

Shipping Charges - Shipping formula element Y (% of products purchased) was not calculating any charge - 40534

Order Entry - Multiship button was disabled if you clicked Edit while on the Items tab - 40505

Order Entry - Multiship button was enabled while not in Edit mode - 40569

Order Entry - Ad code for an order was disappearing if clicking Edit while on the Tracking tab of an order (data was not lost even if resaved) - 40633

Returns - After returning an item, CMS will now highlight the previous item in the list instead of returning to the top of the list of unreturned items - 40424

Kit Builder - Error when deleting a batch that is not yet applied - 40621

9.0.5.132

Fulfillment Manager - Column Sorting added to the grids - 34554

Proformas - Packages were not being created when converting proformas to completed orders unless you clicked into the Shipping tab of Order Entry - 39454

Order Imports - CMS is now setting the order level default fulfill (future ship) date based on the item with the earliest fulfillment date. If the order is subsequently edited to add new items, these items will use that order level fulfill date and thus default to fulfilling with one or more of the other items on the order - 38321

Product Groups - Components that were out of stock were not being placed on back order. Also improved how product group parent items interact with their components allowing you to alter the quantity on the parent and it will update the component quantities or deleting the parent can optionally remove the components - 39861, 33234

Order Review - Corrected poor wording in the dialog message that comes up warning you that this order should have a confirmation created but currently does not - 40540

Order Review - Package ID error when saving after converting to a backorder - 40570

9.0.5.131

Order Entry - Packages were not being assigned to kits - 40488

9.0.5.130

Order Locking - Batch Approvals and EDC were seeing orders as locked that had payments that were applied to more than one invoice on the order (common in 0.00 payments on -1 and then later applied to the -2 on fulfillment) - 40483

CV3 Plug-in - Reversed a previous work-around implemented to deal with authorization data the CommerceV3 was passing to CMS in the wrong field. This was causing some online authorizations to import without their Transaction ID and would treated as a forced sale when captured - 40428

Order Entry - Error when adding items with size/colors if you did not have the option selected to suppress the display of discontinued items - 40499

Order Entry - Error when attempting to find an item with the description search if you did not have the option selected to suppress the display of discontinued items - 40494

Setup - Removed an extraneous field label in Workstation Specific>Location - 40481

9.0.5.129

CMS Licensing Service - Corrected issue with workstations not being able to access the licensing service and thus could not launch CMS - 40454

9.0.5.128

CMS Forms - Added print tasks (aka merge fields for letters) for USERCODE5 and USERCODE6, which represent User Field 3 and User Field 4 in Contact Manager - 40085

Catalog Requests - Fixed sort order in catalog request combo in Todos and Contact Manager to show active catalogs from newest to oldest - 38546

Batch Approvals/Captures - If a processing error is encountered during batch processing of approvals/captures, the order that was locked when the error occurred does not get unlocked - 40429

9.0.5.127

Purchasing - Error printing CMS PO forms (not Crystal) - 40326

Installer - Modify EULA and added CMS Licensing Service install - 40208

Installer - Error if Licensing service was installed but not running when update was installed - 40405

Installer - Now properly cleaning out mia and programdata (both current and for previous installs) - 37516

Order Entry - Products combo was not sorting items in the expected sequence - 40425

Order Entry - Access Violation would occur when clicking View Invoice in a new order if you had clicked Clear while viewing the -1 invoice of the previously saved order - 40275

9.0.5.126

Order Entry - When replacing an order's customer, add options for the user to select which address to use (customer's or order's) and warn if the customer retrieved will alter the order's current salesperson or price category - 40261

Order Entry - Using address validation in some cases could have caused the underlying address_id to not get updated properly affecting the shipping address printing on some Crystal forms - 39692

9.0.5.125

Add support for UPS Mail Innovations shipping method - 39840

External Shipping - Increased size of UPS_SHIPMETHOD field to 50 characters and can now accept write-backs for the new UPS Mail Innovations method - 40245

Batch Approvals - Option to limit number of authorizations was not working - 40214

9.0.5.124

Order Imports - Payment amount incorrectly adjusted on orders with all delayed items - 40211

Kit Builder - Implemented all related controls and settings - 36087, 40016, 40018, 40106, 40231

9.0.5.123

Order Entry - Scrolling the products combo box with arrow keys may cause jump to beginning - 37067

9.0.5.122

Order Imports - Imports were failing to allocate stock - 40204

9.0.5.121

Order Entry - Improved the efficiency of tax lookups - 39228

Order Entry - Back Order Options - Clear the Back Order All flag automatically when a user selects Fulfill X or Change Amount to X - 37654

Order Entry - Even with arrival date support turned off, CMS was still running the arrival date estimation code - 38311

Installer - CMS v9 update error for converting LineID - 38159

Installer - Zonedays update errors referencing CUSTHIST.NOTES process - 38586

Installer - Correct a condition that could cause a failed line_id to integer update - 38897

Order Entry - Items' status is now properly reverted to PD (pending) when deallocated - 37985

eCommerce API - Plug-In Option duplicate name allowed in db but restricted in gui - 38252

Setup>Catalogs - Warning added when setting a catalog as inactive

9.0.5.120

Order Entry - Taxes on return/exchange incorrect when an order level discount is present - 38084

S&H - Implemented S&H formula change for % over to take into account products with their option set as "Exclude from Spending Tables" - 38915

Hold Until Complete (HUC) implemented - 28947, 39955, 39957, 39962, 40056, 40058, 40112

Product Groups - Product Groups on imports were dropping the second instance of a component - 38592

External Shipping - If a shipping integration wrote back a shipping method CMS did not have a match for, CMS was clearing the ship method from the package. Now an update will only take place when a match is made - 39648

External Shipping - Flag needed for residential delivery indicator (RDI) with corresponding logic to act on it - 27633

Batch Approval/Capture screens redesigned to allow for resizing - 40114

Order Entry - Resolved an Access Violation stemming from retrieving a new order while currently viewing a non-001 invoice - 39117

Order Entry - CMS was performing an old-style recipient load from ITEMSORD data prior to doing the newer load from the RECIPIENT_ORDER data - 39742

Order Entry - Optimizations for loading large orders - 39744

Order Entry - Clicking Edit should not change the page/tab - 38955

Order Entry - For editions of CMS that do not support future fulfillment the item level fulfill date has been disabled - 39904, 39905

Order Entry - Implemented Cancel option when going into Multiship mode - 39577

Order Entry - Assorted enhancements to Back Order Options - 39923

Batch Approvals - Regardless of eCheck module existence, the eCheck filter was enabled - 40127

Windows Management - Improve control over nested locking of windows (i.e. a form, button, grid, etc.) to reduce flicker during an internal, multi-step operation - 38887

Magento - Order download db cleanup causing old orders to be downloaded again after 60 days - 40055

Order Imports - Increase robustness of Importing payments by making Payment Import type case-insensitive - 39560

9.0.5.119

Order Locking - Completed changes needed to support locking in Order Entry - 38347

Products - Error with non_inv item "Could not convert variant of type (String) into type (Boolean) - 40061

Order Exports - Added "Item Ordered: Product Vendor SKU" to available Item Ordered export fields. This field represents the data found in the "Vndr SKU" edit box in Product Setup - 40036

Order Exports - Within the Export Layout window, one of the field radio buttons was called "Calculated". This radio button has been removed - 40021

COGS - itemsord t_cost not being updated consistently when a dropship po is confirmed - 40029

EDC - Restored Pay Name to the EDC grid. It was inadvertently dropped when the EDC was reworked for 38457 - 40073

9.0.5.118

Order Locking - Backorder and Future ship fulfillments now check for order locks before processing and then set a lock for the duration of the fulfillment - 38410

Product Groups - Unable to delete components from a product group in Setup - 39049

Installation - When a CMS update is applied to an existing installation, the fCOGSForOrder database function gets deleted - 39894

Statements - Option for attaching statements to emails was missing - 39901

Kits - Kits that pull from their own stock were not decrementing inventory - 39797

Order Entry - Removing the purchaser recipient from a multiship order was failing to remove their items - 39696

9.0.5.117

Order Imports - Now using new internal recipient structure (recipient_id instead of sequence) - 37995

Order Locking - Batch Approvals - 38413

Order Locking - Batch Captures - 38457

Automated Imports Module - Corrected issues with access control - 38671

Windows Management - Included remaining fixes related to nested window locking related to ticket 38815 - 39208

Scales - Added support for Adam brand scale model CPWplus - 38423

Order Review - Item Total on View Invoice was incorrectly based on order quantity and has been reset to use sent quantity - 39645

Order Review - Order Summary was missing the Discount Reversal values which could affect the balance on the Order Summary page - 35203

Order Edits - CMS will refresh the order data when clicking Edit and then set the order lock - 38690

Magento - Custom Magento fields were being cleared before processing - 39651

9.0.4.116

Fulfillment - Added optimizations to improve the speed in which back orders and future ships are fulfilled from Fulfillment Manager. This will be particularly noticeable on orders with hundreds of items and/or recipients - 39583

9.0.4.115

Fulfillment - For companies not configured to use Bill Delayed by default in Order Entry, the fulfillment of back orders or future ships could cause the Bill Delayed flag to be enabled on such orders which moved some or all financials to the -1 invoice - 39642

Order Entry - Changing the warehouse using the arrow key (without opening the Warehouse combo box) was not properly registering the change in selected warehouse - 38257

9.0.4.114

Order Imports - Optimizations added to improve performance during order verify and save for orders that have hundreds of items and/or recipients - 39478

Order Imports - For orders that were partially on back order, CMS was not always altering the credit card payment amount to match the new invoice total, not taking into account shipping charges - 39540

Order Imports - In stock items forced onto back order during imports did not have their fulfill date cleared which could cause them to fulfill into separate packages - 36954

Order Imports - New option to match order imports to customers by email address (default is on). Also modified the logic used on customer matching by email address so that if more than one customer record is found with the same email address, it is not considered unique and no match will be made by email address. Standard name/address matching logic will be used instead - 37263

Order Entry - Bill Delayed, if used by default, was not always being properly set for future ships - 39091

TransFirst - Added support for new responses that are possible when processing reversals or voids on charge card transactions - 38666

Mail List Exports - Optimized the export process and changed the progress bar to increase export performance - 38288

9.0.4.113

Order Entry - Unable to jump to Warehouse combo on Order Entry>Items screen using keyboard - 38815

Order Entry - When converting a future ship order to one that will fulfill today, CMS will no properly allocate maximum qty available to each item ordered and back order the remainder - 39242

Magento - Significant updates to the plug-in to improve integration - 39310

Order Imports - When verifying imports the tax lookup was being skipped - 39336

9.0.4.112

UPS Worldship - Additional packages that were created in Worldship were not displaying a shipping method in CMS - 38593

Purchasing - PO's that were created for drop ship items were not being assigned the shipping method from the corresponding order - 38231

Purchasing - Editing the addresses on a PO were updating the warehouse's address - 24213

Verify Imports - When scrolling through the grid of imported orders in the Verify Imports window, the highlight used to indicate which record you are currently reviewing was disappearing - 38923

Order Review - If a future ship was fulfilled before the scheduled date, the invoice Fulfill Date was not getting updated to the new date of fulfillment - 37619

Order Entry - Optimized arrival date calculations to improve the performance on orders with hundreds of items - 38516

Products - The new Additional Product Information was not displaying a scrollbar when the text entered exceeded the display area - 38659

Products - If a product was converted from being a kit to a standard inventoried item, Stock Manager was not allowing stock to be received (still thinking the product was a kit) - 38725

Kits - Safeguard to disallow a kit item from being added to itself as a component - 20745

Order Entry - A package containing an item set as "Ship In Own Box" will display an item count of "1" on the package contents, regardless of how many were ordered and/or placed into the package - 38715

Installer - On the completion of an install, and once all of the selected databases have been updated, the installer will now initiate a database service restart before reporting that the installation is complete - 38345

9.0.4.111

Order Entry - When configured to use Bill Delayed by default for orders with delayed item, CMS was not setting the Bill Delayed checkbox when delayed items were added to the order via a product group - 38983

XML - Added a new element ItemID to the ItemType definition. CMS will fill in this field with the itemsord.itemid in order status uploads that support item-level synchronization (presently only Magento) -39039

9.0.4.110

Order Entry - Error when deleting the only recipient on an order - 38948

9.0.4.109

Order Entry - If a product or kit component had its quantity edited in an order entry session so it was pulling from multiple lots and then the product was removed form the order, CMS would return all of the stock to the last lot instead of splitting it between the lots originally pulled from - 37634 and 37668

Order Entry - Package assignments were incorrect for variable kit components on a multi-recipient order if the 'Replicate to all recipients' option was used on the variable kit - 37728

Order Entry - Possible for a recipient to not have a package if their future ship or arrival date was set while on a blank item - 37613

Fulfillment Manager was slow if there were a lot of orders with kits (back orders or future ships), now optimized - 38472

Products - Added full word processor formatting capabilities to Tech Info product notes and added a new unformatted Additional Info section for other notes. The Tech Info notes (products.info in the tables) is now stored as RVF so we have provided the Additional Info field for companies needing to store unformatted product information for use with outside integrations. Both are available for view in Order Entry - 37298

Products - Shipping and Customs related settings, which were previously found under the Tech Info tab, have been moved to their own tab labeled Shipping (as part of the above Tech Info modifications) - 37298

PA-DSS - The CMS PA-DSS Implementation Guide.doc has been updated to version 1.7 with minor changes (detailed at the beginning of the doc) resulting from our recent CMS 9.0 PA-DSS assessment by Coalfire Systems (an authorized QSA for the PCI Council) - 37946

Multiship Orders - Expanded the field used to store the combined first+last name to 100 characters - 37786

Temp and Proforma Management - Under Orders>Manage Temp and Pro Forma Orders the grid results have been expanded to include columns for first name, last name, and company - 38016

Worldship - Corrected identification of South Korea to Korea, South so it is recognized by Worldship - 38043

9.0.4.108

Variable kits that contained non-inventoried components were going onto back order - 38907

Standard kits the pulled stock from components, some or all of which were non-inventory, were going onto back order - 38920

9.0.4.107

Proformas - Tax was being calculated on proforma orders for tax exempt customers - 38175

Order Review - If CMS was configured to use Bill Delayed by default and the bill delayed checkbox was unchecked on an order, a subsequent edit to that order would recheck the bill delayed box - 38030

Mail List Imports - During a mail list import, if you elected to delete some bad records, CMS was not adjusting its "nextnum" value used for new customer records - 38645

CommerceV3 uploads - CMS was including variable kit definitions in product uploads for products that were no longer configured as kits which caused an error during the product upload process - 38674

9.0.4.106

Manifest - Add Range of Packages (by ship date) was excluding orders created in CMS 9.x - 38727

9.0.4.105

Returns - Orders with multiple returns processed against them would display as if one of the refund payments had not been applied to its return invoice - 37045

9.0.4.104

Exactor - Get Tax requests for international multi-recipient orders were getting an error response about invalid ship_id - 38661

9.0.4.103

Order Entry - In rare cases it was possible for multi-recipient orders to share the same package.dest_id - 37877

9.0.4.102

Order Review - If a single recipient gift order had its recipient deleted, the new address_id was not properly updated on the itemsord records leading to some Crystal invoices printing without a shipping address - 38262

Catalogs - The combo box used to select a catalog for a catalog request is now sorted in a date descending order so the most recent active catalog is listed first. Also, in the Catalogs section, the list of catalogs to choose from in the combo box there is limited to only those you have open catalog requests for - 38546

Purchasing - Access Violation error when clicking on the Vendors button while in a purchase order - 36923

9.0.4.101

USPS rate updates - 37933

Order Entry - future ship and arrival dates are now disabled at the item level until a product has been entered - 35721

Order Entry - The option to display Quantity in the Size Grid for products with SKUs was in some cases displaying the wrong available quantity if edits were made in the grid to back ordered items - 37183

Order Review - On the View Invoice page, the Zone field was not displaying any value - 38212

9.0.3.99

Exactor - Invalid Ship_ID Error during Get Tax call - 38427

Purchasing - Qty per Unit for vendor skus was not being recognized when placing or receiving purchase orders (allowing for the ordering of case/bulk quantity, or really any multiple other than what you sell) - 32622

Order Review - On the Order Summary, the Fulfill Date was incorrectly displaying the same as the Order Date on the Order Summary if the order contained items that are set as 'does not ship' - 36810

eCMS - Removed the Admin button from the eCMS toolbar (now accessible from Setup>Import Sources and Plug-ins - 38255

9.0.3.98

Kits - In Products when configuring your kit, it was possible for some products to not display as components or candidates to be components - 38386

Invoice Printing - Printing CMS invoices (non-Crystal forms) was including items from all of the order's invoices - 38242

Linked Billing - Customers with Linked Billing will now display the customer number of the "parent" above the Linked Billing button - 36611

Payment Maintenance - If you were to close Payment Maintenance, CMS would not allow you to pull it up again until CMS was restarted - 38318

Lots Received report - This report now includes breakout detail for return lots - 36686

Variable Kits - CMS was displaying a fractional quantity available (based on component availability) when the kit was not configured to allow decimal quantities - 37652

eCMS - Can now override the CommerceV3 web service URL to redirect to another address if needed. This is done with the Plug-in value for ALTERNATEURL- 37434

9.0.3.97

Variable Kits - If an imported variable kit was on back order, the back order quantity was only being set on the kit parent and not on the components - 38230

Variable Kits - Sent quantity was not being properly set on variable kit components that were non-inventory and could also cause issues with back order fulfillments of these variable kits - 38025

9.0.3.96

Exactor - Added support for the Exactor tax integration module for expanded beta testing - 36173

Magento - The Magento Plug-in is now available for CMS Standard (previously only available for Pro)

9.0.3.95

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

Returns - CMS was warning that the customer's tax status had changed for all tax exempt orders/customers - 37466

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

Order Imports - Components of variable kits were not getting their Sent Qty set properly - 38025

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, multi-package) - 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 calculated 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 item-less 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 association from the linked parent to the order's customer - 32900

9.0.1.79

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

Order Entry - With the option for using quaintly 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 temporary measure will be used to ensure the anomaly 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 - Altered 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.5 now click HERE

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