We make continual improvements to the API & integrations, so keep an eye on this page for important news on any of those changes that might affect you.
The changes described below will typically fall into one of two releases, in either September or April of each year.
For these releases, we start by communicating the change well in advance, followed by a release to QAC so that you can observe and test the change. Next, we perform a short brownout on production to identify any remaining users that would be impacted and are unaware. One month after the brownout, we release the change to production. For example, the schedule for September typically looks like this:
June: Email confirming the planned changes
July: Release changes to QAC environments
August: A short "brownout" window in which these changes will be applied to production for 1-2 hours
September: Release changes to production environments
Not all changes will follow this pattern, but our intent is to provide you with plenty of warning about upcoming changes so that you can comfortably prepare for them.
Recently released in 2026
Changes to Multi-factor Authentication and Mobile Device Registration
From January, multi-factor authentication (MFA) is required for the majority of web app users. MFA is already enforced for users with permission to manage roles or users; this requirement now extends to other web app user roles.
The exception to this requirement is for web app users that only have permissions related to Returns and/or Despatch. This exception is intended to ensure that returns and pack bench workstations can continue to operate seamlessly.
Multi-factor authentication codes are not required for mobile operators, but from the January release onwards, 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.
Questions and Answers
What exact permissions are permitted for an Android user to maintain the MFA exception for web app logins?
The following permissions either affect the mobile device or are specifically excluded from impacting a user's eligibility to skip MFA setup for web logins. If a user has no other permissions other than those listed below, then MFA is not mandatory for that user to access the web application:
-
All permissions under the following modules
Despatch
Returns
Search
Move Items
Move Containers
Remove Items
Remove Containers
Receive By Purchase Orders
Receive By Items
Stock Control
Reconcile
Variance Report
Failed Actions
Simple Register
Register With Reason
Receive Without Scan
Stock Take Items
Stock Take Containers Only
Stock Take Clear Locations/Containers
Unpick
Adjustment (Android)
Repack
Replenishment
Global permissions
Stock Take Cycle Count
Put Away 2.0
Stock Take (Android) (Beta)
Put Away
Return (Android)
Return (Android) 2.0
Register
Move
Remove
Stock Take (Android)
Pick
Receive
PICK: One Order
PICK: Multiple Sales Orders (Orders)
PICK: Single Item Batch Picking
PICK: Multiple Sales Orders (Items)
PICK: Pick and sort to trolley
Despatch (Android)
Despatch by container
PICK: Pick by zone
Quick Despatch by Order
Sort
Despatch by Item
Despatch by Load
Scan
-
The following specific permissions:
Put Away Rules 2.0: Preview Beta
Dashboards: Read, Preview Beta
Mobile Devices: Preview Beta
Return Authorizations: Preview Beta
-
How can I register a new device and why was the automatic registration process changed?
You can register a device using the new management page on the web application, available under Users -> Mobile Devices. This manual registration process ensures that all new devices that attempt to access the application undergo a manual review process by an administrator, ensuring that you have full control over who can access your data. To register a new device, you can either provide the serial number (visible from the login page of the mobile application), or you can wait for a mobile user to attempt to connect via the device, at which point it will appear in the list of unregistered devices and you will be able to approve the registration from there.
How can I reset my Two-Factor Authentication (2FA)?
To reset an authentication key, please reach out to the support team via the helpdesk link in the application, or by emailing servicedesk@descartes.com.
Will these changes affect my current devices?
No, any devices that you are currently using today will remain registered. You will only need to register new devices that have not been used previously.
Is there any deadline for making these changes?
The mobile device registration process is being rolled out in January. The web MFA enforcement is coming very shortly thereafter, so please review your permissions as soon as possible to ensure that access is not interrupted.
What should I do if I encounter issues during device registration?
Please reach out to the support team by using the helpdesk link in the application or by emailing servicedesk@descartes.com.
Will my data or settings be affected by this update?
No, this update will not modify your data or any configuration.
How can I remove a device from accessing Peoplevox?
Using the new Mobile Devices management page, you can view a list of devices that are currently approved to access the system, as well as revoke that access to prevent them from logging in.
Removal of Legacy Screens Following Migration to the New Web UI
As we continue to migrate web app screens to the new UI, we will be starting to decommission the legacy screens that they replace. The following screens are scheduled to be decommissioned in 2026:
Locations
Location groups
Actions
Stock take variance approval
Our intent is for the new screens to fully replace the legacy screens without any loss in functionality or ease-of-use. If you have any concerns that you are unable to use the new screens or the new screens do not support the workflow(s) you need, please raise a ticket on the support portal as soon as possible.
Coming soon
These changes are planned for the future, but do not yet have a specific delivery date. Please keep these in mind when building or updating your integrations.
Consolidation of Multiple Return Items to a Single Return Code
With the release of the updated returns and RMA workflow in early 2024, users now have the ability to return multiple products in a single workflow, without exiting the returns process. However, behind the scenes, each of those products is assigned to a unique return record (with a unique return code to identify it), which means that each of those items is communicated to integrations separately.
We expect this behaviour to change in the future, such that items processed together on a single returns workflow are also grouped on a single return code.
Note: The schema of the returns event subscription already supports this, so no structural changes are required to endpoints that consume this data. However, those endpoints must be prepared for the situation that different items on the return will have different return reasons / states. Most marketplace / ERP systems track the reason and state at the item-level, but others track it at the return-level, so please speak to your integration partner if you have any concerns over how this change may impact you and your reporting.
New UI for the web app
We're modernizing the web app, one screen at a time. This UI update will give us an opportunity to improve a number of workflows, make the app easier to use, and allow us to implement many of the changes often voted for on the ideas portal. Stay tuned for some previews soon.
Changes to the API
The maximum duration of a single reporting request will be reduced from 10 minutes to 5 minutes. Callers should ensure that suitable filters are provided against the report so that they complete execution before that timeout.
We are looking to standardise the page size limits on API requests for reporting data. After the change, API callers will be able to ask for a maximum of 50,000 records per page of a report. We will be carefully reviewing existing reports to ensure that it is possible to provide appropriate paging options on the request.