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)