What’s New in Release 25.3
In our next major release—25.3—we’re delivering a leap forward in warehouse automation, external integration, and system control. These enhancements are not just incremental; they open the door for deeper integration with third-party systems, faster execution of core workflows, and better governance in day-to-day operations.
Below, I walk you through the headline features, grouped by new business objects, enhancements to existing objects, and key new capabilities.
New Business Objects: Automating bulk tasks and systems integration
One of the highlights of 25.3 is the addition of nine new Business Objects (BOs). These BOs greatly expand what external applications, scripts, or middleware can do with DATASCOPE WMS — giving your integration teams far more control and reducing manual overhead. Here are the main ones:
- Bulk posting / pick automation
- PickPost (JobPickToPickSlip) & PickToTrackID (JobPickToTrackID)
These two BOs empower you to post many Job-type pick items in one shot, driving stock from one TrackID to another automatically. This reduces repeated manual posting of individual picks, accelerates throughput, and tightens accuracy in stock movement. - PickToTrackID (Replenishment / DirectedReplenishment)
Similar logic—but for replenishment picks. This lets integrators handle multiple replenishment-type picks in one call, simplifying external systems that orchestrate replenishment logic.
- PickPost (JobPickToPickSlip) & PickToTrackID (JobPickToTrackID)
- Smarter reservation and stock allocation
- ReserveLine
You can now programmatically reserve stock for specific lines in a Replenishment Order. This gives your integration layer fine-grained control over which quantities to reserve and from which TrackIDs. - AutoReserve
This BO automates the reservation process at scale. Clients can filter by stock code, zones, demand dates, urgency, and more — and have WMS auto-reserve stock accordingly. No more manual reservation runs.
- ReserveLine
- Enhanced shipping & waybill integration
- Full Load Update
Accepts a full waybill data set from external systems and compares it against the existing WMS state. The BO will add, update, or remove lines accordingly, dynamically renumber stops, enforce seal number logic, and reconcile the differences. This is powerful for logistics partners who resend full manifests mid-route. - ConvertToShippingTrackIds
Allows conversion of Picking Track IDs to Shipping Track IDs outside of the usual shipping flow. You can “pre-allocate” shipping identifiers early, even before actual dispatch, which is helpful in scenarios where Track IDs must be aligned with carrier or logistics planning early.
- Full Load Update
- MaintainPickfaces
Now your external apps can add or remove stock assignments on Pickface bins programmatically, managing min/max thresholds, source warehouses, and pickface rules without manual user intervention. - Pick to TrackID with custom IDs
Third-party systems can now generate their own picking Track IDs (e.g. with specialized naming conventions) and hand them over to WMS. WMS will accept the custom naming while still tracking the pick in its internal logic.
For an online version of the Business Objects documentation, refer to DATASCOPE Business Objects Reference Library
Enhancements to existing Business Objects: Smarter behavior, fewer calls
We also improved several existing BOs to reduce round-trip times, simplify logic, and align with modern automation patterns.
- Assign by MSN (Master Shipment Number)
The PickAssign BOs in OrderRelease, WIP, and Replen have been enhanced to support pMasterShipmentNumber. Pass an MSN, and the system will automatically assign all pick slips linked to that shipment. This saves you from having to iterate through pick slips one at a time. - Print + assign in one go
We added a new optional parameter pPickAssign to the Pick Slip Print BOs. Now you can optionally assign the pick slip to a picker right after printing, in the same call. No need for a second API call. - Accept SSCC in Shipping Dispatch Put Away
Previously, the Shipping Dispatch Put Away BO required a Shipping TrackID. Now you can supply an SSCC (Serial Shipping Container Code) instead. WMS will resolve the SSCC to the corresponding Shipping TrackID and proceed. This helps with integration with logistics partners that operate in accordance with SSCC standards.
Key new features: Operational control & tighter integration
Beyond the BO layer, 25.3 introduces several notable enhancements to WMS itself:
- EDI Out XML on Dispatch / Invoice
With this release, whenever a dispatch or invoice is posted in WMS, an EDI-compliant XML document is generated automatically. It includes bill of lading numbers, weights, SSCCs, line item details, and more. The XML file lands in a configurable warehouse folder (e.g., EDI_XML_OUT). No more externally built middleware to pull dispatch data — it’s native, real-time, and accurate.
- Logout Operators Admin Screen
Admins now get visibility into all currently logged-in operators (PC or HTML5) and can log out users directly from the system. This helps with license control, session hygiene, and governance across web and desktop contexts.
- Job Returns — Multi Line (HTML5)
For high-volume job return operations (for example, when lots or pallets are over-issued), operators can now return multiple component lines in one screen session — without reloading the job each time. This significantly speeds up kitting or assembly returns.
- Cycle Count — Validation for inspectable stock
We tightened cycle counting logic: you can only count stock that has officially cleared inspection in SYSPRO. The HTML5 cycle count screen now checks SYSPRO’s inspection status (depending on TWO_STAGE_RECEIVING rules). This prevents “phantom” counts of stock that should remain on hold.
- Replenishment Pick to Bin (HTML5)
A new mobile screen to support full-pallet moves (entire TrackIDs) directly to a destination bin — ideal for large DCs. No partial scanning or re-labelling — you scan the pallet, and the system moves the whole thing. The existing “Replenishment Pick to TrackID” screen is also renamed to align with naming conventions.
- HTML5 Auto Timeout / Inactivity logoff
Improving security: after a configurable idle period (default 15 mins), users are prompted to stay logged in; if no response within 2 mins, they’re auto-logged out (which also logs out the PC client if linked). This helps prevent unauthorized use of unattended devices.
Why this matters — the value to you
Why this matters — the value to you
- Greater integration flexibility: The new BOs give your middleware, WMS integrator, or RPA tools fine-grained control over core tasks like picking, replenishment, and shipping.
- Fewer calls, simpler flows: Combined BO enhancements reduce the “chatty” overhead of multiple API calls for print, assign, pick, etc.
- Tighter logistics alignment: Support for SSCC and full-load updates enables deeper connectivity with third-party carriers and logistics partners.
- Operational control & security: Session control, auto logout, operator visibility — all help you govern the system more tightly.
- Faster, smarter UI workflows: The new HTML5 screens (job returns, replenishment to bin) reduce operator friction and streamline physical tasks.
- EDI output built-in: No more custom scripting; your dispatch data is now exportable in standard format out of the box.
This release reflects our continued commitment to delivering a more intelligent, agile, and connected WMS experience. To activate these enhancements, contact your DATASCOPE Solutions Partner (DSP) or reach out to our team directly.
Let’s keep moving your warehouse forward—together.
