Overview / Context
The logistics system used FedEx shipping functionality that involved legacy WSDL-based integrations. The work involved moving shipping functionality toward FedEx REST APIs while continuing to support the shipping workflows required by the application.
Problem
The integration needed to keep supporting multiple shipment workflows while moving from legacy WSDL-based services to REST APIs.
The complexity was in preserving different shipment scenarios and their data requirements, not only changing one endpoint style to another.
Approach / Implementation
- Worked on the transition from legacy WSDL-based FedEx integrations to FedEx REST APIs.
- Supported domestic, international, and multi-package shipment workflows.
- Handled shipment, package, and customs-related data required by each workflow.
- Worked through production issues tied to shipment data requirements across different shipping scenarios.
Important Engineering Details
International shipping required customs-related information in addition to shipment and package details.
Multi-package shipments introduced additional package-level handling requirements compared with single-package flows.
My Contribution
I worked directly on integration updates and production fixes as these workflows were exercised, including shipment scenarios with customs and multi-package requirements.
Result
The service supported modern REST-based shipping workflows for several shipment types.