This notification reminds impacted customers that, with the NetSuite 2026.1 upgrade, support for the 2019.2 SOAP endpoint will end and the WMS Printer Driver and Carrier Integrator application will migrate to the 2025.2 SOAP endpoint. It also outlines the required steps to migrate and notes that the updated endpoint will be available in sandbox and Release Preview.
This notice applies to customers who you use the WMS Printer Driver and Carrier Integrator application for your NetSuite WMS Advanced solution. In NetSuite 2026.1, the following changes will affect the services provided by this application:
- End of Support for 2019.2 SOAP Endpoint – After your account is upgraded to NetSuite 2026.1, the 2019.2 SOAP endpoint will no longer be supported for this application.
For more information, see Support for Existing WSDL Versions, SuiteAnswers ID 10817 - Migration to 2025.2 SOAP Endpoint - Oracle NetSuite WMS 2026.1 will update the application to use the 2025.2 SOAP endpoint.
The 2025.2 SOAP endpoint for the updated WMS Printer Driver and Carrier Integrator application will also be available in NetSuite sandbox and Release Preview.
What is Changing?
The 2025.2 SOAP endpoint update for the WMS Printer Driver and Carrier Integrator application will include the following changes:
- Updated web reference URL and configuration file
- Switch to token-based authentication, which includes the following required permissions for roles that need to access or manage the updated application:
Note: The default WMS Web Services Admin role is already preconfigured with the required permissions.- SOAP Web Services – Full access level
- User Access Tokens – Full access level
- Updated NetSuiteCarrierIntegrator.exe build
- Updated NetSuite WMS Advanced Shipping Integration Guide
These changes will apply to upgraded NetSuite 2026.1 accounts that have an existing NetSuite WMS Advanced solution.
Required Actions
Before your scheduled NetSuite 2026.1 account upgrade, update your application configurations on NetSuite sandbox or Release Preview to test the WSDL changes. You must generate a unique Application ID for each test environment that you want to use. See Steps A to C.
Important: After NetSuite 2026.1 disables the 2019.2 SOAP endpoint, you’ll lose access to warehouse printers and shipping integration services provided by the application, until you install the updated application and change your configurations. Make sure that you complete your configurations immediately after your scheduled NetSuite 2026.1 account upgrade.
Whether you use either or both the application’s Carrier Integrator or Printer Driver, you must update your configurations to support the 2025.2 SOAP endpoint. On your NetSuite 2026.1 account, you must complete the following steps:
Step A. On your NetSuite 2026.1 account, verify that you have the latest version of the SuiteApps. - Using the Administrator role, go to Customization > SuiteBundler > Search & Install Bundles > List.
- On the Installed Bundles page, verify the details of the following SuiteApps:
- SCM Mobile – Bundle ID: 590761 and Version: 2026.1
- Oracle NetSuite WMS – Bundle ID: 590660 and Version 2026.1
- In the Version column for each SuiteApp, click the Info icon beside the version number to check if it requires an update.
- If a SuiteApp requires an update, call Oracle NetSuite Support .
- On each shipping station, print server, or combination of both on which the WMS Printer Driver and Carrier Integrator is configured, complete Steps B to E.
|
|---|
Step B. Uninstall the current WMS Printer Driver and Carrier Integrator application, and then install the upgraded application that uses 2025.2 SOAP endpoint. - After your NetSuite 2026.1 account upgrade, uninstall or remove the current WMS Printer Driver and Carrier Integrator application from the computer.
- To download and install the upgraded application, log in to your NetSuite 2026.1 account using the WMS Administrator role. Then, go to Reports > Configuration > NSWMS Print Driver.
For detailed instructions, see Installing the WMS Printer Driver and Carrier Integration .
|
Step C. Generate the Application ID. - Go to Setup > Integration > Manage Integrations > New.
- On the Integration page, in the Name field, enter NSWMS Carrier Integration ID.
- On the Authentication subtab, check the following boxes:
- Token-Based Authentication
- TBA: IssueToken Endpoint
- To save the integration record and generate your key, click Save.
- From the saved integration record, copy the generated data in the following columns: Consumer Key (Client ID) and Consumer Secret (Client Secret). Then, paste them in Notepad or in another secure file or document.
Note: You can’t view the values in the Consumer Key and Consumer Secret fields when you access the record again. - After you copy the generated data, proceed to Step D.
|
Step D. Create a user access token. - Using the WMS Web Services Admin role or a custom role based on it, go to Setup > Users/Roles > Access Tokens > New.
Make sure that the role you use has the following permissions, which can be accessed on the Setup subtab of the Role page:- SOAP Web Services – Full access level
- User Access Tokens – Full access level
For more information, see Setting Permissions. - On the Access Token page, set the following fields:
- Application Name – Select NSWMS Carrier Integration.
- User – Select the name of the person designated to manage your application.
- Role – Select the role of the person you specify in the User field and who has the required permissions listed in Step D.1.
- Token Name – Enter a unique name for the token to be generated.
- Click Save.
- From the saved user access token record, copy the generated data in the Token ID and Token Secret fields. Then, paste them in Notepad or in another secure file or document.
|
Step E. Add the required data to your application’s configuration file. - TBAConsumerKey
- TBAConsumerSecret
- TBATokenID
- TBATokenSecret
For example: <add key="TBAConsumerKey" value="A0E1F648-004C-441B-8132-0B2774FB985Y"/> - Search for the setting tag for the NetSuite SOAP web services endpoint, NetsuiteCarrierIntegrator_com_netsuite_webservices_NetSuiteService, and then for its value, do the following:
- Replace the placeholder value, XXXXXXX, for the domain string in the URL with your SuiteTalk account-specific domain.
To view your account-specific domains in NetSuite, go to Setup > Company > Company Information, and then click the Company URLs subtab.
For more information, see URLs for Account-Specific Domains, SuiteAnswers ID: 65679. - Verify that the port is set to NetSuitePort_2025_2 *.
- Save the configuration file.
*For example: <setting name=”
NetsuiteCarrierIntegrator_com_netsuite_webservices_NetSuiteService
” serializeAs=”String”> <value> https://99999.suitetalk.api.netsuite.com/services/NetSuitePort_2025_2
</value>
</setting> |
After you complete all the steps in the procedure, try to log in to the application. Note that your initial login doesn’t require entry of credentials.