Generating Shipping and Return labels for FedEx
Content was last updated in 06.23.01-00
Revision History
Version No. | Reference No. | Changes |
06.23.01-00 | R2-19991 | Integrating Shipping/Return labels for logistics purpose |
Sharing Package information with the Transportation and Logistics Team (usually some 3rd party vendor) for Shipping and Return of the Container / Package can be a taxing process if both the systems aren't integrated properly.
Logically thinking at a very basic level, the Transportation and Logistics Team must know the Size of the package/ container (Dimensions, Weight, No. of items, Nature of item [Fragile, Not to be stacked, Package/ Container to be stored up-right etc.]). And the same information must be shared with the intended 3rd party vendor for their internal consumption.
The easiest way to share this information is to prepare a label in a pre-specified proforma template (probably a Barcode/ QR Code) that can be printed and attached to the package itself or the documentation accompanying the package.
To facilitate this, the Warehouse App creates and prints shipping labels for FedEx, both for shipping items out and for the customer to ship them back.
The functionality can be invoked by taping the print icon on the Prep/Dispatch screens of the Warehouse App.
The API that helps generating the FedEx labels, is an external vendor's proprietary, build by them for FedEx.
As shown in the screenshots below, once the icon is tapped, the system generates a PDF document that contains the necessary information.
The document thereby can be printed and/or downloaded or shared as per the additional features configured on the mobile device.
Once you click on the print icon in the above screen, the API that generates these Shipping and Return labels needs to be pre-configured in the R2 Mobile App Server.
As a UX safeguard the 'Print Icon' is visible only when the above-mentioned API is configured on R2 Mobile App Server.
R2Wcf Application Settings in IIS
Certain Application Settings for the R2Wcf application must be added in IIS. Follow the steps below.
Open IIS, expand the tree on the left panel to locate the R2Wcf application and select it.
On the center panel, double-click on Application Settings.
In the Application Settings screen for R2Wcf, add the name and value pairs listed in the table below by clicking on the Add… button on the right panel under Actions. Or if the setting already exists, double-click on it or select it and click on the Edit… button to edit the existing value.
Field Name | Value |
YardShipLabelServiceProvider | Grosh |
YardShipLabelServiceUrl | |
YardShipLabelServiceApiTokenHeaderName | Fedex-Access-Token |
YardShipLabelServiceApiToken | 27ap6dpw#Q2c77uRxqR%HfUCUqsKj4 |
The values below are for the Grosh test/dev environment. Adjust according to the Production or Live environment being configured.
To get more help on Configuring the API on your R2 Mobile App Server deployment, please contact UBS Tech Support through your respective PM.