Release note 3.33 - English

Ændret den Thu, 28 Maj kl. 8:20 AM

INDHOLDSFORTEGNELSE

Features and updates
Bug fixes

Planned release date: Thursday evening, May 28, 2026

This release includes an AutoStore integration. This release also includes some issues in order release, ERP integration, and webshop stock adjustments have been fixed, and a number of useful OpenAPI extensions have been added.

Features and updates

AutoStore

This release includes an AutoStore integration. PeakWMS now supports the most essential warehouse operations towards AutoStore systems, including:

Handling of pick list lifecycle in AutoStore. PeakWMS can now create, update, and delete pick lists directly in AutoStore, ensuring synchronization between WMS and AutoStore throughout the entire order lifecycle.
AutoStore stock counting. It is now possible to perform stock counts on AutoStore locations as part of the standard stocktaking flow in PeakWMS.
Inventory adjustments in AutoStore. Adjustments made in PeakWMS are now correctly sent to AutoStore, ensuring synchronized stock items between systems.
Batch product synchronization to AutoStore. Product synchronization sends the entire batch of materials in a single import call instead of one per product. This significantly improves performance during full product synchronization.

Admin – Allowed areas per product

Ability to view allowed areas for a product in an admin dialog. A new admin dialog has been added, providing an overview of which products are allowed in which warehouse areas. This makes it significantly easier to troubleshoot orders that fail due to area restrictions.

The dialog can be found under Admin > Inventory > Product allowed areas. It displays the product, the assigned area, and the area type.

All product fields are available in the dialog, allowing you to tailor the view to your specific needs.

Shopify – use of actual tax amounts

New feature flag UseActualTaxAmounts on ClientHost. You can now configure your Shopify integration to use the actual tax amounts on orders.

For example, when a Shopify order is created from a US state without sales tax (e.g., Oregon), Shopify may return a taxLine with a rate (e.g., 0.08) but with an actual tax amount of $0.00.

Previously, PeakWMS used the rate to calculate tax, incorrectly applying tax to tax-exempt orders. With the new feature flag UseActualTaxAmounts (default: false), you can switch to using Shopify’s actual tax amounts per line instead of rate-based calculations. The feature must be enabled to take effect—existing integrations are not impacted until activated.

Note that Shopify tax amounts are calculated after discounts, and the logic supports multi-element tax lines (e.g., state + county in the U.S., GST + PST in Canada).

Important: The feature must be enabled on your Shopify integration in PeakWMS. It can be found under Settings > Integrations > Webshop integration.

OpenAPI extensions

Brand included on stock endpoints

External inventory applications (e.g., third-party tools) will now receive the product’s Brand as part of stock responses. This is a purely additive change and removes the need for a separate product lookup when categorizing or displaying stock by brand.

New OpenAPI endpoint for deleting return orders

New endpoint:
DELETE /api/integration/v1/salesOrder/{orderId}/return/{returnOrderId}

The endpoint validates that the return order belongs to the specified outbound order. RETURN_HANDLED and REFUNDED return orders are rejected (existing validation), while ARCHIVED orders can still be deleted for manual cleanup.

Inbound order state can now be updated via OpenAPI

Previously, the State field was explicitly ignored for PUT PurchaseOrder. This has been corrected, allowing status updates via OpenAPI.

Other updates

Fallback to shipping locations in other areas within the same warehouse

Previously, packing required the shipping location to be in the same area as the packing station. In warehouses with multiple areas, orders packed in Area A could not be linked to shipping locations in Area B, even within the same warehouse.

This has been changed. PeakWMS can now link orders to shipping locations in other areas within the same warehouse. The system still prioritizes locations within the packing area but falls back to searching the entire warehouse if no suitable location is found.

Postal code rules (ShippingLocationSettings.IsPostalCodeAllowed) are still enforced during fallback.

If a valid location exists within the same area, the existing behavior remains unchanged.

Expected delivery date without time

When creating/editing purchase orders, specifying a time is no longer required for expected delivery— only the date is required.

Updated text in ReturnComment

Return comments now clearly indicate whether the return is processed “without refund” or with a refund.

You will no longer see comments such as “Refunded via PeakWMS” on returns that were handled without refund.

It is now possible to update the purchase order status directly from the purchase order dialog without opening the full edit view.

For example, if an order is in “Draft”, you can change its status directly via the three-dot menu. The feature is also available in bulk edit.

Bug fixes

ReservedForOlder was deducted twice. Pseudo reservations from older orders were subtracted from a filtered subset instead of the total per product, causing rules to appear as having insufficient stock. This has been corrected across OrderReleaseService and ConfigurableOrderSplitStrategy.

Order lines were not split across rules. Lines with quantity 2 requiring one rule per area/location incorrectly resulted in “no stock” despite PartialStockSplitOrderReleaseMaterial being enabled. Splitting logic has been fixed.

ERP overwrote closed purchase orders. Late ERP updates reset ClosedDateTime and modified/deleted lines. This is now blocked and logged.

Duplicate stock adjustments to webshop. Adjustments were sent regardless of IncludeInStockAdjustForWebshop, causing duplicate stock reporting. Messages are now only created for relevant locations.

Invalid adjustment types (value 0). Missing validation allowed incorrect setup of adjustment reasons. Validation has now been added both generically and via OpenAPI.

Manual Uniconta retrieval now respects integration scripts (RUN_BEFORE_MAPPING), preventing unintended order creation/update.

Uniconta production reporting no longer throws PermissionException when creating PackagingUnit.

LogiSnap return labels are now correctly booked, allowing label generation.

Stock items were not merged during automatic purchase order selection. Merge logic has been corrected.

Print button disabled in packing after shipping method change. Button state now updates correctly.

Long order numbers failed barcode generation. Generator now handles long values.

StockAdjust messages missing status now include both original and new status.

Best before date can now be selected via date picker (not only manual entry).

Homerunner country selection now supports both country names and codes (e.g. Holland and NL).

Sorting on “Empty” column in the load unit dialog is now supported.

Delivery note and customs documents now regenerate correctly after merging with parked orders.

Cancelled Shopify single-item orders are no longer shipped in packing (this error was only seen on a few orders).

Refund calculations for partial returns with discounts are now correct.

Quick search now returns all matching products (wildcard behavior fixed).

Incorrect date format in purchase needs wizard has been corrected (YYYY-MM-DD).