pixi

pixi 26.01


pixi 26.01 is available from 13 January 2026. It includes several bug fixes, new features, enhancements and optimizations. Reference the numbers in parentheses if you have any questions for support. You can download the latest full installer after the database update on pixi Web under Administration > Downloads. pixi 26.02 is released on 03.02.2026.


API

🟪 Enhancement: We improved the pixiUpdateDeliveryItem API call. Updates now reliably target the correct delivery line. Additionally, the call now requires the delivery item line ID (SdelDkey) when multiple rows exist for the same item; otherwise, it returns an error instructing users to provide this ID. Please note that batch number and best-before date values are no longer overwritten with null when omitted from the request. Existing values are kept unless a new value is provided. (1375537)

🟪 Enhancement: The API call pixiGetDelivery now supports time values in the date parameters. The service previously ignored the provided time and defaulted DateFrom to 00:00 and DateTo to 23:59. It now uses the exact time provided (for example, 10:27) when searching for goods receipt documents. When no time is provided, the API still defaults to 00:00 and 23:59. (1363907)

🟪 Enhancement: With the introduction of the new External Receipt Number in pixi Web, the API now also allows to send this number within the call pxiCreateDelivery. The parameter is @ExternalReceiptNr. (1337952, 1338006)

🟪 Enhancement: pixiUpdateDeliveryItem now supports the @BatchNumber and @BestBeforeDate parameters. (1338046)

🟪 Enhancement: The @ExternalReceiptNr parameter is now also available for pixiUpdateDelivery. You can use this parameter to set a reference for the Goods Receipt document via the @SDelHKey parameter. If ExternalReceiptNr is not provided or is null, the existing value on the Goods Receipt document remains unchanged. (1338017)

🟩 Resolved Issue: We resolved an issue that allowed the pixiDFCreateInvoices API call to run in parallel, which sometimes prevented a procedure from finishing and assigning the correct invoice number. The system now runs invoice creation processes one at a time to ensure proper sequencing. (1271608)

🟩 Resolved Issue: The API calls pixiGetItemStockHistory and pixiGetItemsStockHistory continued to return data from auto exports, even though these entries should be hidden. The API procedures have been adjusted to now also filter out Auto Export movements from the API results. (1318600)

🟩 Resolved Issue: We resolved an issue that caused the pixiGetDeliveryItem API to respond slowly, especially when goods receipt items did not include batch management data, by optimizing the underlying database query. (1349222)

🟩 Resolved Issue: We resolved an issue for call pixiGetInvoiceLinesExtended where using the UpdateDateFrom and UpdateDateTo parameters returned all rows for an invoice instead of only rows with update dates within the specified range. (1291040)


pixi Messaging

🟩 Resolved Issue: The messaging event pixiEXStockMovement continued to return data from auto exports, even though these entries should not be returned. (1318600)


pixi Mobile

Mobile (BETA)

The following release items refer to the new BETA version of pixi Mobile.

🟩 Resolved Issue: Even after passwords expired, users were still able to log in. (1353994)

🟩 Resolved Issue: We resolved an issue that prevented users with usernames longer than 20 characters from performing certain inventory processes, even when their roles had the correct permissions. We updated the system to support usernames up to 30 character. (1365450)


pixi Web

Device Authentication

🟧 New Feature: Device authentication is now available in pixi, strengthening security for pixi Mobile (.NET Maui) and pixi Connector through trusted device policies. This feature provides an alternative to traditional Multi-Factor Authentication (MFA), which is often impractical in warehouse environments where workers may not have business email accounts or access to personal devices. The rollout will occur in three phases: (1346631, 1346634, 1347210, 1347212, 1347214, 1347215, 135330, 1353308, 1373783, 1379281, 1382604, 1379278, 1384391)

  1. During phase one (starting with 26.01), pixi will collect device data in the background and administrators can mark devices as trusted or untrusted on the new User Administration > Devices page already without impacting warehouse workflows.

  2. During phase two (starting with 26.02), from the day the database is updated, the 28 day transition period begins and ends after 28 days (example: When the database update is on 16 January, phase two for the database starts on 13 February).
    Once the defined end date is reached, warehouse workers can continue working without interruption using their trusted devices. In all other cases, workers/users are prompted to send a request for device authentication on first login. After transition is over, devices must be marked as Trusted. If the device status is pending, you will see a notification pixi Mobile (.NET MAUI) and in pixi Connector; however, if the device status is untrusted, login will not work.

  3. In phase three, (starting with 26.02) once the database is updated, the 28 transition period will begin for the database. After 28 days only trusted devices can access pixi Mobile and Connector.


    We recommend visiting the Devices page to mark devices trusted before the 28 day transition period ends. Device authentication will become mandatory 28 days after the update date to 26.02 for any devices that are not marked as trusted.


General

🟪 Enhancement: A loading spinner with the description "Loading" now appears to indicate ongoing processes. During loading, the main menu and the page title area in the top-left corner are grayed out to improve the user experience and prevent unintended interactions. (1364127)

🟪 Enhancement: Product images are now always fetched over HTTPS, even when the image URL uses HTTP. (1048069)


Administration (Shops)

🟪 Enhancement: The field E-mail (SI_Email) is now available in the Shop tables Settings > Shop Information. (1343211)


Administration (User Administration > Devices)

🟪 Enhancement: A new Devices page is now available, allowing you to manage trusted and untrusted device access for pixi Mobile and pixi Connector. Administrators can access this page by default, while all other roles require explicit permission. This page is introduced to support the new Device Authentication.


Controlling (Reporting)

🟪 Enhancement: Proforma-Invoice reports now feature the E-Mail field from Shop tables > Settings > Shop Information. The variable in the footer on the standard Proforma-Invoice report can now be set accordingly. (1343211)

🟪 Enhancement: Reports in pixi Web now support configurable numeric formatting based on the format value defined in the Report Layout file. To display more than two decimal places in the grid, download the report layout, open it as a text file, update "format": "{0:n2}" to "format": "{0:n4}" for your desired column and then reupload the layout. This formatting applies to both the preview grid and the Excel export. (1356665)

🟪 Enhancement: After you generate a report and select a system layout, pixi now loads 90 rows at a time instead of 30. As you scroll, pixi continues loading additional batches of 90 rows, up to a total of 10,000 rows displayed on the web. (1353243)

🟩 Resolved Issue: The report Unshippable Orders falsely returned not locked orders, although the parameter Include Locked Orders was set to "1". (1329243)


Customer Service (Invoices and Credits)

🟩 Resolved Issue: An issue was resolved where duplicate invoice numbers could be assigned due to an ambiguously defined index. (1258881)


Customer Service (Returns)

🟩 Resolved Issue: We resolved an issue where the setting Return Costs - Default Value behaved inconsistently in the web refund workflow. The setting itself indicates that it applies only to the desktop return wizard, but it was also applied when refunding a single return in pixi Web. However, when refunding multiple returns at once, the value was not used. The behavior is now consistent throughout Desktop and Web. (1342539)


Items (Item Labels)

🟩 Resolved Issue: Item labels printed in ZPL were missing numeric values with two decimal places. (1338101)


Logistics (Goods Receipt)

🟪 Enhancement: A new Ext. Receipt Nr. field is now available for goods receipt documents in pixi Web. The field allows storing a reference to an external document (up to 50 characters) and can be added via API and the Edit option on the receipt's detail page. The value is visible in the goods receipt list, where it is also searchable through the Ext. Receipt Nr. search field and displayed in the document header. (1338103, 1337910, 1337954, 1338150, 1338163, 1363299)


🟪 Enhancement: The Goods Receipt details page now includes the Best Before Date and Batch Number columns in the grid. Here, the batch management data can now also be added or edited. Please note that, when a goods receipt document is closed and the option to put items into a bin is enabled, the system now validates that all items with batch management tags have batch management data entered before the document can be closed. (1341832)



🟪 Enhancement: In the Goods Receipt overview grid (details page), the column ABC was renamed to System Tags, where also BM icons will be displayed. (1341832)

🟩 Resolved Issue: When items with batch management data were added to stock by closing the goods receipt document, the provided BM data was not saved to the database. (1338085)

🟩 Resolved Issue: We resolved an issue where the External Receipt Number search on the Goods Receipt overview did not behave as a partial (“like”) search to return documents that only partially matched the entered value. The search now returns results only when part of the External Receipt Number matches. The External Receipt Nr variable is now also available for printing on the Goods Receipt document. It has to be added manually to the existing goods receipt template in the Template Editor. (1362608)


Logistics (Picklists)

🟪 Enhancement: The picklist creation for not reserved orders was optimized in the part where it checks if there is sufficient stock available for the items. (1363927)


Logistics (Ship-Out)

🟩 Resolved Issue: We resolved an issue on the Multi-package ship out page that caused two shipping-label requests to be sent when a different shipping vendor was selected from the drop-down list. The page was refactored to ensure only a single request is submitted. (1353140)


Logistics (Stock)

🟩 Resolved Issue: We resolved an issue that prevented performed stock movements from appearing immediately in the Item History tab; the list now updates without requiring a manual refresh. (1350233)

🟩 Resolved Issue: The Show Location Stock In Item Search - Summary Quantity setting now consistently controls how Summary Quantity and Location Quantity appear in Advanced Search. When enabled, both fields show quantities for the user’s or document’s location. When disabled, Summary Quantity shows quantities across all locations, while Location Quantity continues to reflect the user’s or document’s location. (1354778)

🟩 Resolved Issue: We resolved an issue where scanning or entering a barcode in the Put to Stock tab did not display bin locations and caused a browser error if the item was stored in only one bin. The correct bin is now displayed immediately without errors, even when only a single bin exists. (1358784)


Purchasing

🟩 Resolved Issue: Invalid characters that are inserted into the Notes field via copy and paste operations are now ignored. (1333540)

🟩 Resolved Issue: Supplier order suggestions now evaluate all potential suppliers for items using the Stock turnover order method. The system considers every supplier in the calculation, even when the immediate required quantity is 0. This ensures the most cost-effective supplier is selected based on complete evaluation criteria, including delivery time and cost. (1352205)


pixi Desktop

Control Center

🟩 Resolved Issue: In Control Center Tables > Messaging Events, the Last Execution Date was not updated. (1335578)


ShipRush Integration

🟪 Enhancement: Enhancement: Shipping via ShipRush now supports recalculating invoice amounts from the order currency to the home currency before sending the shipping request. You can enable this behavior by modifying the shipping request template. Ensure the carrier currency defined in ShipRush is set to the home currency. (1101052)



Release Podcast

The AI-generated Descartes pixi Release Notes Podcast gives you a concise overview of the latest product updates, enhancements, and bug fixes. It's the perfect way to stay informed about all the latest changes: whether you're on the go or just taking a moment in between.


Updates

Contact our support team for an update appointment

  • Via email: Click the following link, fill out the email template and send it to servicedsk@descartes.com.

  • Via the portal: Log in to the Portal and open a Ticket.

Updates can either be done from Monday to Friday between 7:00 am and 5:00 pm or overnight. Ask the pixi Support team for an appointment.

Back to top