Descartes® is pleased to announce the latest release of Peoplevox. This is the final scheduled update for 2025, and includes a range of performance improvements to both action creation and put away, a new web app management screen to help you keep track of mobile devices, and a couple of small bug fixes. Below, you'll find a summary of the changes implemented in this version. For any questions about specific items, please reference the associated number (if provided) when contacting Descartes Customer Support.
Tip: Use our Ideas Portal to submit your enhancement ideas for Descartes Peoplevox. Click here for additional information and instructions on how to request access.
Highlights
🟨 New mobile device management screen (1226836)
The new Mobile devices (Beta) page of the web application allows you to view and manage all of the mobile devices that are registered to your Peoplevox account.
From here, you can see a list of all of the devices that have been registered, along with some key information like the serial number, model, and when it was last seen in the warehouse.
This list view also allows you to unregister a device if you need to revoke access to it for any reason.
You can also drill into each device here to see more detail:
As you can see above, the detail page will provide you with the same summary information as the grid view, but from here you can also update the description of the device, see a list of recent logins (both successful and unsuccessful), and also view the location barcode that was most recently scanned by that device, to help you locate missing devices.
Each device can also optionally be assigned to one or more sites from here, which will then allow you to filter down the list on the previous page to exclude devices that may not be relevant to you.
This site assignment does not restrict the usage of the device. A device assigned to a given site can still be used in other sites as long as the user has sufficient permissions to do so.
IMPORTANT: At the moment, all mobile devices are automatically registered with the system when a user successfully logs in on the device. Starting in January 2026, devices will need to be manually registered through this screen before they can be used in the warehouse. This manual registration is a form of two-factor authentication. Any existing devices already in the system will remain registered.
🟨 Support for multiple action deletion through the web application (364094)
With this release, it is now possible to select and delete multiple actions at once through the web application actions screen:
Each row of the actions grid now supports a checkbox to select the action, and the bin icon in the top-right of the grid can be used to delete each selected action at once.
You will be prompted to confirm before the item is deleted:
If you try to delete an action that cannot be deleted, you will be shown a list of those, along with a reason for each. You will also be asked to confirm whether you want to proceed with deleting the valid actions anyway:
You can use this new feature to quickly remove and recreate actions, which you may find useful for example if you need to clear and regenerate replenishment tasks.
🟨 Put away performance improvements (1286326)
The overall performance of the new put away rules has been significantly improved. The app now keeps track of several things that it previously had to calculate on-the-fly for each rule, such as the most recently used location for each product, and whether or not a given location is currently empty.
The result of this should be that existing rules will work much more quickly, and the mobile device should now support putting away larger quantities of items at once.
We will likely continue to work on the rule performance in the future as well, but this release should be a significant step forward.
New Features and Enhancements
🟪 We have continued to apply a number of performance improvements to the system. These have largely been focused around the processes related to action creation. (588091)
Resolved Issues
🟩 We fixed an issue that could incorrectly split picks into the wrong sequence when multiple orders require the same item from the same location. (1299565)
🟩 We fixed an issue with the new PVX+ Register workflow that could prevent some products from being scanned if the scanned text included characters like plusses or slashes. (1336901)
🟩 We fixed an issue with some despatch workflows that could prevent the package weight from being calculated correctly if certain steps in the workflow were hidden. (1251346)
🟩 We fixed a rare bug in the action creation process that could occasionally cause the process to look at fewer items than are actually needed for the selected orders. This could manifest in several ways, including items being apparently skipped from an action, items appearing to be added to orders after the pick was completed, and orders being prematurely released to pick while still waiting on some inventory from bulk. The fix ensures that the process gathers all of the necessary items correctly before it checks for their locations in the warehouse, and this results in a generally more robust workflow. (1337503)
Preview of Changes Coming Soon
Cycle Count Improvements
We’re working on several improvements to the cycle count process. We would love to hear your feedback on these topics.
🟦 We are working on an auto-approval mechanism that will allow you to define thresholds for auto-approval based on the total item variance, or a percentage variance, or a total value variance (or any combination of the above). These thresholds will be set at the Site level and are entirely optional. You will be able to enable auto-approval with a variance threshold of zero if you only want to auto-approve variances with no discrepancies.
🟦 We plan to improve the way cycle count actions are displayed on the web application. The current actions pages are geared around pick actions, making many of the fields and columns not applicable to cycle counting. The goal is to introduce screens that are relevant to the specific action type.
Changes to Multi-factor Authentication and Mobile Device Registration
Coming in January 2026, multi-factor authentication (MFA) will be required for the majority of web app users. MFA is already enforced for users with permission to manage roles or users; this requirement will then be extended to other web app user roles.
The exception to this requirement will be for web app users that only have permissions related to Returns and/or Despatch. This is intended to ensure that returns and pack bench workstations can continue to operate seamlessly.
Multi-factor authentication codes will not be required for mobile operators, but from January 2026, any new mobile devices accessing the system will first need to be registered via a new web app page coming soon. The intent behind this change is to ensure that only authorized devices are permitted to connect to the system, and to provide administrators with greater control over onboarding and offboarding mobile operators.
This device registration page will also support a number of other functional enhancements, such as assistance to find lost devices, and login audit history.
We will be communicating these changes separately in an upcoming announcement as well.
Descartes ShipRush
You can also find the latest release notes for ShipRush here: