This article lists all known issues related to recent feature developments or enhancements. These cases are first listed in the associated release notes and then added to this compiled list.
At the end of each quarter, resolved tickets are removed from this page.
WMS-6691 – Find Orders: We are aware of an issue that occurs after packing an order using SmartPack, in which the underlying warehouse transaction record is not updating the Total Weight and Total Volume. This is causing the Total Volume, Total Weight, and Total Packages fields to not display correctly in the summary fields.
WMS-9684 – SmartPack: In some cases, the SmartPack page is erroneously stating that there are still items to be packed after all items have been fully packed.
WMS-12565 – SmartParcel: Endicia currently has an issue where attempts to void labels through their APIS generates an error. We are working with them to address this issue as quickly as possible.
(Fixed 1/20) WMS-12756 – SmartScan: We are aware that, when using Zebra MC92 series scanners, multi-part GS1 barcodes may fail to parse completely if they contain any variable-length data elements.
(Fixed 12/16) WMS-15058 – General: We are aware of an issue that occurs when accessing the system using the Safari browser with 1366 x 768 screen resolution, which causes the menus to not work as intended. As a friendly reminder, 3PL Central does not recommend accessing 3PL Warehouse Manager via Safari.
(Fixed 1/6) WMS-15202 – SKU Names: If a SKU name includes a pound sign (#), we are aware that this can cause various actions to fail, such as batch item updates and order imports.
WMS-15676 – Create/Edit Receipt: When creating or editing a receipt, we are aware that the system currently allows you to assign an MU to a null location (No Location) and an additional location. When you attempt to add the MU to the additional location, an error should appear stating that the MU is already in an existing location.
WMS-15732 – SmartScan: We are aware of an issue in the Pick and Pack modules when scanning GS1 barcodes that include variable-length elements, in which the barcode properly parses, but elements in the barcode that occur after a variable-length element are not captured in their appropriate fields. For example, when scanning a GS1 barcode containing SKU (variable) and Lot (variable), the SKU will populate into the SKU field successfully, but the Lot value will not. (Fix ETA: 2/3)
WMS-15741 – WooCommerce Connection: There is currently an issue with retrying orders that fail due to invalid SKUs, which causes invalid data to be appended to the list of failed orders to retry.