Release note 3.43 - English

Ændret den Wed, 4 Nov kl. 1:31 PM

INDHOLDSFORTEGNELSE

                                                       


PeakWMS 3.43 is expected to release on 4 November 2026. This release lets you manage product comments directly in PeakWMS and issue a new API key for an Open API integration yourself. It also includes a long list of fixes, especially in the handling of delivery dates, orders shipped together, and integrations with multiple goods owners.


Overview of new features

Type

Title

Subtitle

Source

Value

Task (WMS-9001)

Products: Create, edit and delete product comments directly in PeakWMS

Product comments can now be managed in the Product Comments dialog instead of only through an integration

Strategic/Roadmap

Full control over the messages the warehouse sees when picking, packing, receiving and replenishing. One comment can be given to many products at once, and comments can finally be deleted

Task (WMS-9754)

​Open API: Generate a new API key for an integration

A lost or leaked API key can be replaced directly on the Open API Integrations page

Improvement/Onboarding/Internal

The integration no longer has to be deleted and recreated, so links to products and orders are kept. The old key stops working immediately

Task (WMS-9955)

Warehouse: Automatic clean-up of empty temporary load units

Empty, unused load units of the Temporary type are deleted automatically every hour

Sales/Project/Open Point

The Load Units overview stays clear without manual clean-up



New features

Products: Create, edit and delete product comments directly in PeakWMS

Product comments are the messages warehouse staff see when an item is picked, packed, received, replenished or put away. Until now, they could only be created and changed through an integration, and they could never be deleted.


Comments can now be managed directly in the Product Comments dialog under Products. A wizard makes it possible to attach one comment to many products at once and choose in which workflows it is shown, and whether it is shown as a pop-up. Individual products can be added to or removed from an existing comment, and you can also select products in the product overview and give them a comment from there. This gives full control over the messages the warehouse sees, without going through an integration.


Open API: Generate a new API key for an integration

An Open API integration's API key is only shown once, when the integration is created. If the key was lost or had leaked, the only solution was to delete the integration and create it again, which removed all links to products and orders.


A user with access to the Open API Integrations page can now generate a new key and copy it, while everything else on the integration is kept. The old key stops working immediately, so every system that uses it must be updated with the new one. Deactivating and deleting an integration now also takes effect immediately.


Warehouse: Automatic clean-up of empty temporary load units

Load units of a type marked as Temporary are only used for one job, for example picking or packing, but were never removed again. As a result, the Load Units overview filled up with units nobody would use again.


PeakWMS now automatically deletes empty, unused temporary load units every hour. This keeps the overview clearer. Note that temporary load units should not be created in advance, as they are deleted if they are empty and unused at the next run.



Updates to existing features

Reports: "Average per employee" has moved to the Count view

On the Total performance tab under Reports > Employee Performance, you could select Average per employee together with Average per work hour. This divided a figure that was already per employee hour by the number of employees once more, so the pace looked far too low.


The option is now found under Count instead, where it divides each period's total by the employees who were active in that period. Average per work hour now always shows the actual pace per work hour. Charts previously saved with the option switched on may show values per employee when set to Count. The option can be switched off again.



Bugfixes

Orders: One common rule for a new requested delivery date

A new requested delivery date was handled differently depending on where it came from. An order could therefore be released even though it was still on hold, or be packed without the lines PeakWMS had removed. For example, an unpaid Shopify order was picked after a user had set its delivery date.


A new date now follows one common rule, both through the Set delivery date action in the order overview and through the Open API. The rule takes into account the Set planned release date from requested delivery date setting and how far picking and packing have progressed. This gives predictable planning, and orders on hold stay on hold.


Orders: A new delivery date from editing, e-conomic and WooCommerce reschedules the order

When the delivery date was changed on the Edit Outbound Order page, on the e-conomic order page, or through an order update from WooCommerce or e-conomic, the date was saved, but the order was not rescheduled. The order was therefore picked and shipped according to the old plan. At the same time, the Excel import in the order overview cleared the delivery date on all orders if the file had no date column.


These routes now follow the same rule as above, so the order is planned according to the new date. The Excel import keeps the delivery date when the file has no date column.



Orders/Combined shipping: Picked items are no longer written off when an order is removed from "Send with other order"

When an integration removed an order from the order it was to be shipped with, for example because it became unpaid, was put on hold or was cancelled, the lines were removed even though the items had already been picked or packed. Picked items were written off while they were still in the picker's load unit, and packed items could be shipped twice.


The order is now removed without writing off picked items. If the items are already packed, the order stays linked and an alert is created so someone can decide what to do. This keeps stock figures correct and prevents duplicate shipments.



Orders/Combined shipping: Deleting or cancelling a main order no longer leaves orders stuck

When the main order in a "Send with" group was deleted, the linked orders were left in the Send with other order status and were never released. If the main order was cancelled by an integration, the orders were instead shipped separately, even though they belonged to the same shipment.


The oldest waiting order in the group now becomes the new main order, and the rest are linked to it. The Unlink from send with main order action can also release orders that are already stuck.



Orders: Orders on hold are no longer released when lines are added

An order on hold in the webshop was released as soon as the same customer placed a new order, if the held order had already been picked or packed. The same happened when a line was added to an order on hold or in error. For example, a replacement item could be shipped before the return had been received.


The order now keeps its status when lines are added, and a new order is not linked to an order the webshop is holding back.



Bundles: Available quantity is updated when orders change

A bundle's available quantity and the stock value sent to the webshop were not updated when an order line for one of the bundle's components was deleted, or when an order was created, edited, deleted or cancelled through the Open API. The bundle could therefore show the wrong figure, so it either could not be sold or was oversold.


Bundles are now recalculated shortly after the change is saved, and the new stock value is sent to the webshop. Bundles that already show the wrong figure are corrected by saving the bundle again or by a full stock synchronisation.



Integrations: Order download continues past an order that fails

When one order failed during an integration's order download, the download stopped and the following orders were skipped. For Magento and PrestaShop, where the download is the only way in, one failing order could block all orders behind it.


The download now continues with the remaining orders, so one error does not hold back the rest.



e-conomic: Clear error message for products without a product group

Products without a product group cannot be created in e-conomic, but the alert said neither which product failed nor why. Neither the customer nor support could therefore see what needed to be fixed.


The alert now names the product and explains that it is missing a product group. The product group is set in the Product dialog, and the product is sent again when it is saved.



HostedShop: Cost price is updated in the webshop

When PeakWMS sent a product's average cost price to HostedShop, the cost price on the product or variant was never updated. Customers had to correct it manually, and the margin figures in the shop were wrong.

The cost price in HostedShop is now updated automatically for both products and variants.



Shopify: Stock for new variants becomes sellable again

Since release 3.37, stock sent to a variant that was not yet linked to the warehouse's Shopify location was not made sellable, even with Activate tracking in Shopify switched on. Items could therefore show as sold out online even though the warehouse had them.


The variant is now activated at the location again when the setting is switched on. Variants affected since 3.37 are corrected with the Sync stock action.



Open API: Alerts are created for the right integration

When an integration created an alert through the Open API and another integration already had a similar alert, the other integration's alert was overwritten instead of a new one being created.

Each integration now gets its own alert, and no messages are lost.



Products: The supplier on a packaging unit must belong to the product's goods owner

The Packaging Unit dialog accepted a supplier from a different goods owner than the product's. The other goods owner could therefore see and change the packaging unit.


Only suppliers from the product's own goods owner can now be selected. Suppliers without a goods owner can no longer be used on a goods owner's products.



Invoicing/3PL: Storage data for goods owners counts shelves correctly

The nightly calculation of goods owners' storage usage, which is used for storage invoicing, counted one shelf per partly used shelving rack instead of one per shelf level. A shelving rack without locations was also counted as a full rack for every goods owner.


Shelves are now counted per shelf level, and shelving racks without locations are not counted. The fix applies from the first night after the release, and earlier days keep their figures. For goods owners who use several shelves in racks they do not fill, storage invoicing may therefore increase.



Forwarders: Saving a forwarder no longer hangs

Saving a forwarder under Settings > Forwarders could take many hours and fail if you removed a forwarder product that still had open orders.

The forwarder is now saved without the long wait in that situation.



Stock count: The count starts at the beginning of the route

When an employee selected a stock count order in Count warehouse, the count could start in the middle of the route if a location was remembered from an earlier count. Open locations before it were skipped.

The count now always starts at the beginning of the route, so all locations are included in order.








Var denne artikel nyttig?

Fantastisk!

Tak for din feedback

Beklager, at vi ikke var nyttige

Tak for din feedback

Fortæl os, hvordan vi kan forbedre denne artikel!

Vælg mindst én af grundene
Captcha-bekræftelse er påkrævet.

Feedback sendt

Vi sætter pris på din indsats og vil forsøge at rette artiklen