INDHOLDSFORTEGNELSE
- Updates
- Purchasing: Purchase Needs now includes vendor lead time in forecast calculations
- Order Release: Fair distribution during automatic order release and improved handling of parked orders
- Production: Order line comments displayed directly in the production flow
- AutoStore: Automatic retries and alarms for pick list errors
- OpenAPI: Pick group and picker available via Open API and webhooks
- Purchasing: Automatic line numbering on purchase orders created in the user interface
- Orders: Anonymization of order history, return orders, and alarms (GDPR)
- Bugfixes
- Consolidation: Consolidation when the carrier refuses to cancel a shipping label
- DanDomain: Correct removal of product integration when a product is deleted in DanDomain
- Shipping: Full compliance with the OpenAPI standard for Generic Forwarder
- AutoStore: Consolidation between AutoStore and manual pick carts
- Picking: Oldest orders prioritised when assigning by area pressure
- Put-away: Correct synchronisation of stock levels to integrations
- Picking: Ability to switch pick cart after picking has started
- Warehouse: Improved warehouse overview and zoom on large warehouses
- Business Central: Updating purchase orders from BC when lines have been received
- Integrations: Manually held orders stay on hold when updated
- Users: Correct creation and editing of users linked to a goods owner
- Purchasing: Correct display of sales figures in Purchase Needs for items with new orders
Updates
Purchasing: Purchase Needs now includes vendor lead time in forecast calculations
When calculating reorder requirements using Forecast under Purchase Needs, the calculation now automatically includes the vendor's lead time:
- Covers lead time plus purchasing period:
The suggested purchase quantity now covers the expected sales during both the vendor's lead time and the selected number of purchasing days, helping ensure that you do not run out of stock while the order is in transit. - Lead time by packaging level or vendor:
The lead time is automatically retrieved from the selected packaging level's Vendor Delivery Time (Days), or alternatively from the vendor's general Lead Time (Days). - Includes growth and seasonal sales:
Any expected growth and historical sales from the previous year are applied across the entire period (lead time + purchasing days).
What does this mean for you?
More accurate purchasing suggestions, helping you avoid stockouts during the period between placing an order and receiving the goods.
Order Release: Fair distribution during automatic order release and improved handling of parked orders
We have optimized Automatic Order Release so that large volumes of held orders for a single product owner no longer prevent other customers' orders from being released and picked:
- Fair distribution per product owner:
Each automatic release run (up to 250 orders at a time) is now distributed evenly among all product owners with active orders. If one product owner has a large backlog of orders on hold (e.g. due to missing stock or customs errors), orders belonging to other product owners will continue to be released automatically as long as their items are in stock. - Retry pauses for failed and held orders:
Orders on hold (e.g. due to missing customs descriptions, country of origin, weight, shipping product, or technical release errors) are no longer retried during every release run. They are automatically assigned a pause (up to 1 hour for data errors and up to 24 hours for missing stock), preventing them from unnecessarily consuming capacity in the release engine. - Targeted reactivation when stock is received:
When new stock is added, replenished, or adjusted for an item number, only the orders actually waiting for that specific item are reactivated from their pause. Orders that are on hold for other reasons remain paused. - Preserved reservations and faster processing:
Stock reservations for older orders remain intact, preventing newer orders from "taking" stock reserved for older orders. At the same time, checks of older orders have been significantly optimized, ensuring stable and fast processing of release runs.
What does this mean for you?
No more order release bottlenecks in 3PL warehouses: One client's missing stock or data errors can no longer block automatic order release for the warehouse's other product owners, minimizing the need for manual order release.
Production: Order line comments displayed directly in the production flow
When a production order is created from a customer order, production employees can now see the customer's specific order line comment directly on the handheld scanner throughout the entire production process:
- Visible at every production step:
The order line comment is clearly displayed below the item information. - Important production details at your fingertips:
Ideal for orders with specific customer requirements (e.g. color codes, custom dimensions, or surface treatments) transferred from the webshop/ERP system via the order line comment field. - Clear display and text wrapping:
Comments retain their original line breaks and adapt to the screen without extending beyond the edge. Longer comments (over 120 characters / 2 lines) are shown in a collapsed view with a "Show more" / "Show less" button, keeping the scanner interface easy to navigate. - Clean display when no comments are available:
If no comment is associated with the relevant order line, no unnecessary fields or empty placeholders are displayed on the screen.
What does this mean for you?
Fewer production errors and no more manual checks: Production floor employees can see the customer's specific requirements and instructions directly on the scanner during production.
AutoStore: Automatic retries and alarms for pick list errors
When orders are released to, modified in, or removed from an automation system (e.g. AutoStore), communication is now handled much more reliably with automatic retries and immediate alarms in case of errors:
- Automatic retries when creating and deleting pick lists:
If a pick list fails when being created in the automation system, or if a pick list cannot be deleted (e.g. when an order is paused or canceled), PeakWMS automatically retries the request. - Clear alarm for persistent errors:
If the automation system still cannot be reached or continues to return an error after the retries, the order is marked with the "Pick list error in automation" alarm, including the exact error message. This allows the issue to be detected immediately rather than only when the order reaches the picking port. - Immediate alarm if picking has already started:
If the automation system rejects a deletion or modification because an operator has already started picking the order at the port, the "Picking started in automation" alarm is created immediately without unnecessary retries. - Follows the warehouse's existing alarm rules:
The alarms are displayed directly in the order details and in the Alarms overview in the administration interface. They include the order number and product owner and automatically trigger email notifications according to your configured alarm rules.
What does this mean for you?
Full visibility into automated orders: You are notified immediately if a pick list encounters an issue in AutoStore, helping you avoid surprises and wasted time.
OpenAPI: Pick group and picker available via Open API and webhooks
Integrations and ERP systems can now retrieve information about a pick order's pick group and picker directly via Open API and event messages (webhooks):
- Pick group on sales order pick orders:
Open API requests for a sales order's pick orders now return the associated pick group's ID and name for both active and archived orders. - Pick group and picker in webhooks:
Event messages (webhooks) for Pick Order Picked, Packed, and Partially Picked/Short Picked now include the pick group's ID and name. In addition, the specific picker is now included directly in the Pick Order Picked webhook.
What does this mean for you?
Your ERP system can now automatically receive and record which pick group and picker handled a delivery, making subsequent follow-up and reporting much easier.
Purchasing: Automatic line numbering on purchase orders created in the user interface
When purchase orders are created manually in the administration interface, order lines are now automatically assigned sequential line numbers (1, 2, 3…):
- Automatic numbering when creating orders:
Orders created via Create Purchase Order, generated via Purchase Needs, or separated using Split Order now automatically have their order lines numbered from the start. - Original numbers retained when editing and creating credit notes:
When an existing order is edited, its existing line numbers remain unchanged. Credit notes created from an invoice order also retain the invoice's original line numbers.
What does this mean for you?
Manually created purchase orders now follow the same consistent line-number structure as orders from ERP and integration systems, ensuring clear line references during receiving and data synchronization.
Orders: Anonymization of order history, return orders, and alarms (GDPR)
When a sales order is anonymized (via the user interface or API), the customer's personal data is now consistently removed across the entire order:
- History panel:
Previous address changes and error messages from shipping providers in the history log are anonymized, and the anonymization itself is recorded as a separate event. - Return orders and comments:
Addresses on completed return orders, return reasons, customer comments, webshop comments, and order line comments are replaced with "Anonymized". - Alarms:
Any error messages and alarm texts associated with the order are automatically anonymized. - API support for completed orders:
Completed orders can now be anonymized directly via the API without validation errors.
What does this mean for you?
Ensures full compliance with GDPR and data protection requirements, as personal data is no longer left behind in order history, alarms, or return data.
Bugfixes
Consolidation: Consolidation when the carrier refuses to cancel a shipping label
When two pick orders are merged via Consolidation with other order, the consolidation now always completes smoothly — even if the carrier refuses to delete the redundant shipping label:
- Consolidation completes without stopping work in the warehouse: If one of the orders being merged has already had a shipping or return label created, PeakWMS automatically attempts to cancel the label with the carrier. If the carrier refuses the cancellation with an error, this no longer stops the consolidation. The pick orders are merged as expected, and the warehouse operator can continue their flow without interruption.
- Automatic alarm for refused labels: If the carrier could not cancel the shipment automatically, an alarm is raised in the administration menu under Alarms (External system update). The alarm specifies the affected parcel number, the order and the carrier's error message, so the office can easily delete or handle the shipment manually in the carrier's own portal.
- Full order history: The order history on the order details records the event precisely, so you always have full traceability of which shipping and return labels were cancelled automatically, and which required manual follow-up.
- Clean handling if the label is already deleted: If the carrier reports that the label has already been removed, the consolidation completes immediately and is recorded in the history as correctly cancelled.
What this means for you Staff experience no blockages on the scanner during consolidation, even if the carrier's system refuses a deletion — and the office is automatically notified via alarms if a label needs to be cancelled manually.
DanDomain: Correct removal of product integration when a product is deleted in DanDomain
When a product or variant is deleted in your DanDomain webshop, the item's integration link is now updated automatically and correctly in PeakWMS:
- Automatic removal of the webshop link: When DanDomain reports that a product has been deleted in the webshop, PeakWMS now removes the integration link from the item immediately.
- The item can be deleted in PeakWMS: Because the link to the webshop is removed correctly, the item is now registered as deletable in PeakWMS (provided the item has no active stock or order lines). Previously, the item remained locked by the old webshop link, even though it had long since been deleted in DanDomain.
- Synchronised product catalogue: Ensures a clean, up-to-date product catalogue in PeakWMS that matches the active range in DanDomain.
What this means for you When you delete items in DanDomain, they are automatically released in PeakWMS, so you can easily delete or clean up discontinued items without manual integration checks.
Shipping: Full compliance with the OpenAPI standard for Generic Forwarder
When you use a Generic Forwarder to send shipment data and retrieve shipping or return labels via your own API services, the data structure from PeakWMS now matches the official OpenAPI documentation (PeakWMS API V1 – Generic Forwarder) 100%:
- Consistent field names (camelCase): All fields in the JSON requests PeakWMS sends to your endpoints (e.g. when creating a shipping label, return label, cancellation and tracking) now follow the standard with a lower-case initial letter (e.g. customerId, existingConsignmentId and shippingComment).
- Correct transfer of country codes and delivery comments: Sender and recipient addresses now always send the country code in the country field, and any delivery instructions/comments for the driver are transferred correctly in shippingComment.
- Parcel shop ID at request level: Pickup points (parcelShopId) are now placed unambiguously at the top-level request, exactly as described in the API contract.
- Flexible parsing of responses: PeakWMS can receive responses from your integration endpoints regardless of whether the field names in your response are returned with an upper- or lower-case initial letter (PascalCase or camelCase), ensuring a stable and trouble-free integration.
What this means for you Developers and technical partners can build and maintain integrations to their own shipping solutions directly from the published OpenAPI specification, with no discrepancies in the data structure.
AutoStore: Consolidation between AutoStore and manual pick carts
When an order contains items from both AutoStore and manual pick areas, PeakWMS now ensures that the items can always be consolidated correctly on the scanner, so the customer receives one combined shipment:
- Pick totes are always linked correctly to the AutoStore cart: When items are picked from AutoStore directly into a load unit belonging to a pick cart, the tote is now automatically registered at its fixed shelf position on the cart. Previously, the tote could remain registered as moved away after an earlier packing, which made the cart appear empty on the scanner during the consolidation step.
- Smooth scanning during consolidation: During the consolidation step on the scanner ("Scan the displayed load unit to consolidate"), the AutoStore cart and the relevant load unit are now always shown correctly, so the picker can complete the consolidation without stops or errors.
- One combined shipment and one shipping label: The order is packed and shipped as one combined parcel with one tracking number, rather than the items being incorrectly split and sent as two separate parcels to the customer.
- New setting: "Keep target when stock is missing": Under Admin > Outbound > Pick consolidation setup, the setting "Keep target when stock is missing" has been added. When enabled, consolidation of the AutoStore items is still offered at the end of the pick tour, even if the manual pick lines have gone into backorder or were zero-picked.
What this means for you No incorrectly split shipments or blocked consolidation steps on the scanner when combining AutoStore and manual picking. The items are always combined into one shipment to the recipient.
Picking: Oldest orders prioritised when assigning by area pressure
When pick orders are assigned automatically to pick carts using the Area Pressure method, the oldest orders are now always prioritised first:
- Oldest orders first (FIFO): If several orders in the same area have the same priority and shipping deadline, the pick cart is now filled with the oldest orders first, rather than in random order.
- Route optimisation unchanged: Area pressure and distance are still respected in order to optimise the pick route.
What this means for you You avoid older orders being overtaken by newer orders in the same pick area when there isn't room for all orders on one cart.
Put-away: Correct synchronisation of stock levels to integrations
When items are moved during put-away, the available stock level is now always updated correctly in connected webshops, POS and ERP systems:
- Automatic stock adjustment on moves: Moving items to/from locations or across warehouses during put-away now automatically sends the necessary stock adjustments to your integrations.
- No more discrepancies in sales channels: Ensures that the webshop's sellable stock matches the warehouse's physical placements, with no need for manual resynchronisation.
What this means for you Your webshop and sales channels are kept automatically up to date with the correct stock level when items are put away in the warehouse.
Picking: Ability to switch pick cart after picking has started
Warehouse staff can now freely switch to another pick cart via Change pick cart, even if items have already been picked on the active cart:
- No more error messages during picking: The action is no longer rejected with the message that the pick cart cannot be reset once picking has started.
- All picked items are preserved: The cart that was started keeps all its picked items and order statuses intact, so the operator (or a colleague) can easily select the cart again and continue the pick tour later.
What this means for you Greater flexibility for pickers in the warehouse, who can quickly switch task or cart without losing work in progress.
Warehouse: Improved warehouse overview and zoom on large warehouses
The warehouse overview on handheld scanners and PCs has been updated so that large warehouse buildings and areas are always shown in full and are easy to navigate:
- The whole warehouse is shown centred: When selecting a location (e.g. when creating/moving load units, during goods receipt, or in location views), the map now always opens centred so that all areas and racks are visible from the start — regardless of the warehouse's physical size.
- Pinch-to-zoom on touch screens: On handheld scanners and tablets you can now zoom in and out with two fingers (pinch-to-zoom), while panning and selecting a location are still done with one finger.
- Better zoom on PC: The mouse wheel can now zoom out far enough to take in the entire layout, even on very large warehouses.
What this means for you Staff in large warehouses get a complete overview of the warehouse map on the scanner and can easily zoom and navigate straight to the location they need.
Business Central: Updating purchase orders from BC when lines have been received
When a purchase order is updated in Business Central after goods receipt has started in PeakWMS, the changes now always take effect on the remaining order lines:
- Other line updates are preserved: If an already received line is deleted or reduced in Business Central, the entire update is no longer rejected. New lines are added, quantity changes on other lines take effect, and unreceived lines are deleted as expected.
- Received data is protected and alarmed: Already received lines and quantities are preserved unchanged on the purchase order in PeakWMS, and a single combined alarm is raised automatically (Cannot delete received purchase order line), so the discrepancy in the ERP system can easily be identified.
What this means for you Purchase orders no longer "freeze" when the ERP changes, and goods receipt can continue unhindered in the warehouse.
Integrations: Manually held orders stay on hold when updated
When an outbound order is put manually on hold with its stock reservation retained (Manually put on hold with reservation), this status is now always preserved on subsequent order updates from webshops and ERP systems:
- No unintended release of the hold: Orders that have been put manually on hold (e.g. on suspicion of fraud, an address error, or at the customer's request) are no longer set back to status Created and released automatically for picking when the webshop sends an ordinary order update.
- The stock reservation is retained: The order stays safely on hold while the items remain reserved for the customer.
What this means for you You no longer risk manually stopped orders being picked and shipped by mistake as a result of automatic background updates from your webshop or ERP.
Users: Correct creation and editing of users linked to a goods owner
When administrators create or edit users with a specific Goods Owner, the link is now always saved correctly:
- No more validation errors on save: Creating or changing a user with a selected goods owner is no longer rejected with error messages about missing address fields or item number postfix ("field is required").
- Secure access control: The user is always linked to the selected goods owner as expected, so the user's access remains correctly restricted to that specific goods owner's data.
What this means for you Administrators can create and maintain goods-owner-specific user accounts without error messages or the risk of incorrect access rights.
Purchasing: Correct display of sales figures in Purchase Needs for items with new orders
In the Purchase Needs wizard on purchase orders, sales figures are now shown correctly for items that have released orders but no historical completed sales yet:
- Sales figures populated for new items: For items with no previous sales history but with released, uncompleted orders, the sales figures (Sold 7/30/60/90/365 days), sold-out calculation and sales index are now populated correctly instead of being left blank.
- Better basis for decisions: Buyers get genuine insight into demand for brand new products when assessing the suggested purchase quantity.
What this means for you New items with current orders show accurate sales figures in the purchasing calculation, giving you a clear data basis for reordering.
Var denne artikel nyttig?
Fantastisk!
Tak for din feedback
Beklager, at vi ikke var nyttige
Tak for din feedback
Feedback sendt
Vi sætter pris på din indsats og vil forsøge at rette artiklen