Support WMS Integration to UPS REST Web Services
For the new integration type, Ship Request is now converted to support UPS for REST Webservices. Now, when the new integration type is chosen for parcel integration with UPS, REST is supported.
- Addition of Shipping with Address1, Address2 and Address3 (also cover Ship to and Ship From)
- Inclusion of Company name in the Ship From name in the email notification.
In the Carrier Facility UI, for Integration Type, the following items have been added:
- New Ship request for REST
- New void de-manifest request for REST
- New auth request for REST
- New entries for celery task and all the related integration steps.
ADD REST SUPPORT FOR UPS PARCEL INTEGRATION
Integration with parcel carriers allows for real-time tracking of shipments, minimizes shipping costs, and maximizes overall operational efficiency.
To add continued support for parcel carriers in WMS, we’ve added REST Webservices support for UPS parcel integration.
NEW FIELDS AND INTEGRATION TYPE IN CARRIER FACILITY UI
To support UPS Integration for REST Webservices, the following additional fields and values are now available in the Carrier Facility UI:
- The drop-down value 'UPS REST Webservices' added to the field Integration Type.
- UPS Webservices is now renamed to 'UPS Legacy Webservices' (which corresponds to the SOAP UI).
UPS Legacy Webservices
NOTE: Records that already exist in the system as UPS Webservices for the Integration Type will now display as UPS Legacy Webservices. This will happen by default for the existing records with this value.
- Two new text fields have been added for configuring the Client_id and the Client_secret key (or code) for UPS REST Webservices.
- A new check box field has been added which allows for requests to switch between the testing sandbox for UPS and for actual live production requests for UPS REST Webservices.
NOTE: By default, the new fields are not visible on the data grid. These fields are not exportable to csv.
CONFIGURATION RECOMMENDATIONS FOR UPS REST
For UPS REST, the new configuration should be set in the Carrier Facility UI, as follows:
- The integration type should be set to "UPS REST Webservices". (and all the other existing fields to be configured as before).
- The existing SOAP UI configurations will now correspond to the 'UPS Legacy Webservices' value for the Integration Type. This value was renamed from UPS Webservices. So, all the existing records having 'UPS Webservices' will now reflect to show 'UPS Legacy Webservices.'
- To proceed further with the pending manifests, the new Ship Via needs to be configured explicitly to link to the Integration Type - UPS REST Webservices and remanifest them.
To configure:
- Setup the new Carrier Facility UPS REST Web services.
- Change the new Ship Via configuration.
- Remanifest the orders in packing status at that time using the new UPS REST webservices
NOTE: At this point, if there are orders in packing/packed orders (or OBLPNs), remanifest should be done manually.
Steps to Enable
You don't need to do anything to enable this feature.