Canofy Process Standardization & Refactoring

User Story
As a Canofy user, I want a common cargo and shipment verification framework so that shipment information from different ULIP cargo services can be searched, retrieved and presented consistently within the application.

Description
Develop a reusable cargo and shipment verification framework for integrating multiple ULIP cargo-related services into Canofy.
The framework provides a common structure for handling cargo searches based on different reference types such as AWB, HAWB and MAWB, while supporting both import and export shipments.
The framework was designed to accommodate the different response structures and business information returned by cargo services, including shipment status, origin, destination, flight information, airline, cargo location and customs status.
The current implementation uses simulated ULIP responses to validate the application workflow. The framework is structured so that individual ULIP cargo services can be connected through their respective service methods without requiring the entire UI or application workflow to be redesigned.

Configuration / Prerequisites
Common ULIP client/service layer available.
Cargo search workflow and UI framework available.
Support for import/export selection.
Support for relevant shipment reference types:
AWB
HAWB
MAWB
Standard response/error handling implemented.
Mock cargo shipment responses available for development and testing.
Cargo service methods available for ACMES, ACCS and AIICLAS integrations.

Acceptance Criteria
The application provides a consistent workflow for cargo/shipment verification.
Users can select the applicable cargo type, such as import or export.
Supported shipment reference types can be passed to the appropriate cargo service.
Cargo service responses are mapped into a consistent application-level structure.
Shipment information can include:
AWB/MAWB number
HAWB number
Shipment status
Origin
Destination
Flight number
Airline
Cargo/terminal location
Customs status
Last updated timestamp
Successful, failed and service-error responses are handled consistently.
Different cargo service implementations can be integrated without duplicating the overall verification workflow.
The framework can accommodate different response fields returned by individual ULIP cargo APIs.
Mock implementations can be replaced with approved ULIP API calls once production access is provided.