IMPORTANT Actions and Considerations

The following are important actions and considerations to review for 26A:

TRANSITION FROM LEGACY SOAP TO REST API INTEGRATIONS FOR FedEx and UPS SHIPPING SERVICES

To ensure ongoing support, we want to inform you that FedEx and UPS have officially transitioned their shipping integrations from legacy SOAP web services to modern REST APIs. SOAP will be deprecated by these carriers in the near future.

To support your transition, we are making the following changes effective with release 26A:

  1. New Configurations

The system will not allow you to create a Carrier Facility for FedEx or UPS Legacy services or for ConnectShip. The system will display the message: "The Legacy SOAP web service is no longer supported. Please migrate to REST API."

  1. Existing Configurations

If you currently have an existing Legacy SOAP configuration, you can continue to use and update your existing setup temporarily. The following warning message will appear on the configuration screen:

For FedEx/UPS: "This integration uses legacy SOAP web services. FedEx and UPS now support REST APIs. Please migrate to REST as SOAP will be deprecated."
For Connectship: "This integration method will no longer be supported. Please migrate to REST API."

NOTE: Begin planning your migration to the new REST API integrations as soon as possible to maintain carrier support and avoid service interruptions.

COMPANY REPORT TYPE - BILL OF LADING .xls FORMAT

  • Company Report Type - Bill of lading. xls format is no longer supported and will throw a message (NOT_SUPPORTED) when Company Report Type - Bill of Lading (BOL) is configured with .xls format. 
  • New Company Report Type configurations or existing configurations or report sub-type values (with .xls) will NOT be visible. Prior Company Report Type - Bill of Lading containing .xls format will display an error.

NOTE: Input Interfaces still currently support .xls files. However, this will be deprecated in an upcoming release, likely 26B. 

INTRODUCE HYPERLINK IN WAVE SEARCH AND DYNAMIC WAVE SEARCH FIELDS

We have enhanced the Wave Template UI to update the “Wave Search” and “Dynamic Wave Search” fields to clickable hyperlinks. This allows you to quickly navigate to the respective configuration or details pages. When you click the hyperlinks, the system filters and displays the associated wave search or dynamic wave search configured in the wave template.

RESTRICT CONFIGURATION OF “TREAT AS ATTRIBUTE” ON INVENTORY LOCK CODES

The system allows you to enter an inventory attribute (a to f) as a value in the “Treat as Attribute” field on the Inventory Lock Codes (InventoryLockCodeView) UI. When you apply a lock code (configured with “Treat as Attribute”) to inventory, the system overrides the corresponding inventory attribute value at the inventory level. This behavior can affect replenishment because in-transit inventory and the inventory to be replenished can change.
To prevent these unintended inventory attribute changes, we are now restricting new adoption of “Treat as Attribute” on inventory lock codes.
With this restriction, 

  • New users and existing users who have not previously used “Treat as Attribute” (created at least one lock code at the parent company level) are not allowed to create a lock code with “Treat as Attribute”. If you save a lock code populated with “Treat as Attribute”, the system displays an error message.
  • Existing users who already have at least one lock code with “Treat as Attribute” at the parent company level can continue to configure “Treat as Attribute” for inventory lock codes.

NOTE: In the future, we may deprecate “Treat as Attribute”. For now, we have blocked new adoption and alternatives will be provided with sufficient notice before removal. If you already use “Treat as Attribute,” you may continue current usage and configurations for now. If you do not use “Treat as Attribute” (including new customers), you cannot configure it on any lock code.

DEPRECATION OF SSH-BASED RF

Starting in January 2026, new customers will not be offered SSH-based RF. Redwood Mobile WMS is the replacement. Even now, all new customers are being encouraged to use Redwood Mobile WMS from the beginning.

Existing customers can continue to use SSH based RF for a further year. It will be retired starting January 2027 per the following schedule:

  • January 2027 – Cohort 1 customers
  • April 2027 – Cohort 2 customers 
  • July 2027 – Cohort 3 customers

INTRODUCED “UPLOADED TIMESTAMP” AND “UPLOADED USER” COLUMNS TO THE NBR ATTACHMENTS SCREEN

We have added “Uploaded Timestamp” and “Uploaded User” columns to the data grid on the Nbr Attachments screen, which is accessible from the following UI screens:

  • IB Shipments (IBShipmentView)
  • IBLPNs (IbContainerView)
  • OBLPNs (ObContainerView)
  • Pallet (PalletView)
  • OB Load (ObLoadView)
  • IB Loads (IbLoadView)
  • Cycle Count Adjustment (CCAdjustmentHdrView)
  • OBLPN Type (ObLpnTypeView)

Also, we have added “Uploaded User” column to the data grid on the Attachments (AttachmentsView) UI.