INDHOLDSFORTEGNELSE

• Overview of features
• New feature
  • User communication
  • Stock: Moving reserved stock to non-pick locations prompts to return orders for re-release
  • Address: New phone number input with country code selector across the system
• Other updates
  • Highrunner: Prevent endless release loops and repeated shipping labels for high-runner orders
  • Search: Add records to "In" / "Not in" criteria without overwriting existing selections
  • Order release: Manual order release checks for required delivery dates
  • Integration messages: Re-queue multiple failed incoming webhook messages at once
• Bugfixes
  • Bundles: Accurate re-picking of missing bundle components on resend orders
  • Freight: Carrier label is cancelled and tracking details cleared when the label document is deleted
  • OpenAPI: Orders created on hold via API are no longer released prematurely
  • Purchase need: Optimized purchase need calculation prevents blocking product deletions
  • Purchase need: Purchase need calculation no longer fails for sales in less common currencies
  • Colli pack: Accurate total quantities on sale stock actions when packing multiple parcels or pick orders
  • OpenAPI: API release blocks orders missing a required delivery date
  • Rackbeat: Rackbeat no longer rejects stock adjustments and warehouse moves sent just after midnight
  • Pallet Lite: Real rejection reasons displayed for Pallets Lite pallet failures

Overview of features

New feature

User communication

Client administrators now have full control over user access to support and feature requests, as well as which topics Peak Systems may contact each user about:

• "Super User" replaces support access: Previous support access is replaced by the Super User flag, which client administrators can now assign directly. Super Users receive access to support and feature requests.
• Four communication subscriptions: Roles and individual users can now be subscribed to receiving communication about: Critical operations information, Release and product updates, PeakWMS Inspiration, and Open API.
• Mandatory phone number: Super Users and client administrators must have a valid phone number with country code when created or edited, ensuring Peak can reach the right key contacts during operational incidents. If you are editing a user after the release, make sure to check, that a phone number is added.
• Goods owner restriction: Goods owner users cannot be assigned Super User status or client-admin roles, as goods owners does not have direct access to PeakWMS support.

What this means for you:
You can designate Super Users directly without contacting Peak support, ensuring operational alerts and relevant product updates are routed to the right team members.

You will receive another email with more information about user communication.

Stock: Moving reserved stock to non-pick locations prompts to return orders for re-release

When moving an entire stock line or load unit with active pick reservations to a location not intended for picking (such as a replenishment or bulk location):

• Confirmation prompt: The system now opens a confirmation dialog (Reserved stock) stating how much is reserved, asking whether unstarted pick orders should be returned for re-release.
• Automatic re-release from pick stock: Selecting Yes clears the reservations, moves the stock, and returns the order to created status so it can be re-released from an eligible pick location. Selecting No carries the reservations over to the new location.

What this means for you:
Pickers are no longer directed to bulk or replenishment locations to pick items that were moved out of the picking area.

Address: New phone number input with country code selector across the system

When entering phone numbers in the web interface (including addresses, user creation, packing, return portal, and wizard dialogs):

• Searchable country selector: The input now includes a dropdown with country flags, names, and dial codes (e.g., ?? Denmark +45), searchable by country, ISO code, or dial code.
• Standardized format and validation: Phone numbers are automatically validated and stored in standardized international E.164 format (e.g., +4512345678).

What this means for you:
Ensures phone numbers consistently include valid country codes, preventing carrier booking and SMS notification failures.

Other updates

Highrunner: Prevent endless release loops and repeated shipping labels for high-runner orders

When using configurable order release rules alongside high-runner pack tables, orders are now only assigned to a high-runner pack table if the reserved stock is physically located at that table's high-runner pick locations:

• No endless release loop: If an order's reserved stock is located in standard warehouse locations, it is now released as a regular pick order rather than routing to a high-runner pack table where it cannot be picked.
• Prevents duplicate shipping labels: Eliminates the loop where orders were repeatedly rejected, deleted, and re-released, preventing unnecessary shipping label and tracking number generation with the carrier.

What this means for you:
Orders requiring non-high-runner stock are seamlessly processed through the standard picking flow, preventing wasted carrier labels and stalled orders.

Search: Add records to "In" / "Not in" criteria without overwriting existing selections

When adding values to criteria using the In or Not in operator in picking groups or order release rules:

• New "Add" button: The selection pop-up now includes an Add button alongside Select, appending newly ticked records to those already in the field.
• Preserves existing selections: You no longer need to re-find and re-tick all previously selected records (such as shipping products, carriers, integrations, or goods owners) just to add an additional one.

What this means for you:
Faster and safer configuration of rules and picking groups without the risk of accidentally overwriting previously selected criteria.

Order release: Manual order release checks for required delivery dates

When an operator manually releases sales orders from the Orders administration dialog (Release order / Release orders), and the chosen forwarder product requires a delivery date:

• Validates delivery date: Orders lacking a mandatory delivery date can no longer be released to picking, regardless of their current on-hold reason.
• Prevents premature dispatch: Ensures orders are not picked and booked with the carrier without the delivery date required by the shipping method.

What this means for you:
Eliminates booking and delivery errors by ensuring orders released manually always have the required delivery date.

Integration messages: Re-queue multiple failed incoming webhook messages at once

In the administration under Integration Messages → Incoming Webhook Messages:

• Bulk re-queueing of failed messages: You can now select multiple failed messages and re-queue them all in a single action instead of confirming each message individually.
• Faster recovery from integration failures: Makes it quick to resubmit large batches of messages following temporary webshop or ERP outages.

What this means for you:
Saves time when handling integration errors by allowing you to re-queue all affected messages at once rather than one by one.

Bugfixes

Bundles: Accurate re-picking of missing bundle components on resend orders

When packing a bundle product on a resend (send-again) order and selecting "Send what is in stock" after short-packing, only the missing components are now re-picked:

• No duplicate picking of packed parts: The system now only generates pick lines for the missing bundle components instead of re-picking the entire bundle. Already packed components are excluded.
• Consistent behavior: Resend orders now follow the exact same logic as standard sales orders.

What this means for you:
Prevents unnecessary re-picking and accidental over-shipping when dispatching remaining bundle items on resend orders.

Freight: Carrier label is cancelled and tracking details cleared when the label document is deleted

When a shipping or return label document is deleted from a pick order, either in the UI or through the integration API:

• Cancelled with the carrier: The label is cancelled once with the carrier, where the carrier supports cancellation. This means you are not billed for it.
• All tracking data cleared: The tracking number, package number, consignment number, tracking link and parcel-shop code are removed from the pick order.

Important for integrators: If you delete a label through the API, it is now cancelled with the carrier, so you will need to request a new one.

What this means for you:
You no longer pay for unused labels, and pick orders no longer show outdated tracking numbers.

OpenAPI: Orders created on hold via API are no longer released prematurely

When an integration creates a sales order via the API with state On hold and a valid on-hold reason (e.g., On hold in webshop or Manual):

• Created directly on hold: The order is now placed on hold immediately with the specified reason, preventing automatic release to picking.
• Overrides internal hold reasons: The integration's hold reason takes precedence over internal PeakWMS on hold reasons (such as a missing delivery date).

What this means for you:
Orders placed on hold by your webshop or ERP stay safely on hold and are not accidentally picked or shipped.

Purchase need: Optimized purchase need calculation prevents blocking product deletions

When calculating reorder requirements via Purchase Needs for large product assortments:

• No deadlocks on product deletions: Saving calculation results no longer blocks or deadlocks background product deletions from webshop integrations.
• Faster calculation: The calculation and result storage have been optimized, significantly reducing waiting time in the wizard.

What this means for you:
Webshop sync jobs no longer fail or time out during purchase calculations, and buyers receive their reorder suggestions much faster.

Purchase need: Purchase need calculation no longer fails for sales in less common currencies

When calculating reorder recommendations in Purchase Needs for products sold in less common currencies:

• Full currency coverage in calculations: Exchange rates are now properly cached and handled for all supported sales currencies rather than only a limited subset.
• No more calculation errors: Prevents purchase forecast calculations from failing with a "Divide by zero" error when sales history includes currencies previously missing from the rate cache.

What this means for you:
Purchase forecasts calculate reliably regardless of which currencies your sales orders were placed in.

Colli pack: Accurate total quantities on sale stock actions when packing multiple parcels or pick orders

When an order is packed into multiple parcels (colli), or multiple pick orders are completed together without packing:

• Accurate running totals: Each Sale stock action now immediately accounts for stock deducted on preceding parcels or pick orders within the same confirmation, keeping the Total Quantity accurate.
• Accurate inventory valuation: Prevents inventory levels and values in the financial stock report (Generate Financial Report) from being overstated for multi-parcel orders.

What this means for you:
Stock action ledgers and financial reports reflect accurate warehouse inventory immediately upon shipping, without waiting for the nightly sync job.

OpenAPI: API release blocks orders missing a required delivery date

When attempting to release a sales order via the integration API (release sales order) where the forwarder product requires a delivery date:

• No release without delivery date: The order is no longer released to picking without a delivery date—even when force release is requested.
• Placed on hold automatically: The order is placed on hold with the reason Missing Delivery Date instead, allowing the date to be supplied first.

What this means for you:
Prevents orders with delivery date requirements from being picked prematurely or shipped without a valid date.

Rackbeat: Rackbeat no longer rejects stock adjustments and warehouse moves sent just after midnight

Rackbeat rejected stock adjustments and moves between two warehouses when PeakWMS sent them just after midnight Danish time, while the UTC date was still the previous day. This happened between 00:00 and 02:00 in summer and between 00:00 and 01:00 in winter.

• Now booked correctly: Stock changes in that window were not booked in Rackbeat and failed permanently. This no longer happens.
• No failure alarms: You no longer get alarms for these stock changes.

Note: Stock messages that have already failed are not resent automatically. Contact support and we will resend them.

What this means for you:
Stock movements around midnight now sync to Rackbeat just like the rest of the day.

Pallet Lite: Real rejection reasons displayed for Pallets Lite pallet failures

When Homerunner Pallets Lite rejects pallet creation for a packed parcel (e.g., due to carrier, destination, or country code):

• No more "response: null": The integration message and customer alarm now display Pallets Lite's actual error message and the rejected field instead of generic »null«.
• Shows submitted carrier and country: The error text specifies the carrier and country code PeakWMS passed in the request, making issues easy to identify.

What this means for you:
Support and warehouse managers can immediately see why Pallets Lite rejected a pallet and resolve the underlying issue quickly.