Project

General

Profile

Actions

Task #85

open
SG

Task #1: Product Improvement

Task #3: ULIP application/Integration

12. ICEGATE Customs Verification Module

Task #85: 12. ICEGATE Customs Verification Module

Added by Srishti Ghosh 18 days ago. Updated 17 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
08/01/2026
Due date:
08/15/2026 (14 days late)
% Done:

100%

Estimated time:
6:00 h

Description

User Story
As a Canofy user, I want to verify import and export customs declarations through the ICEGATE service, so that I can retrieve customs clearance and cargo declaration information using the relevant declaration reference.

Description
Implement the ICEGATE cargo verification module within the Canofy ULIP integration framework.
The module supports both Import and Export declarations and allows users to search using the applicable declaration type — Bill of Entry for imports and Shipping Bill for exports.
The current implementation uses simulated ICEGATE responses to validate the complete verification workflow before connecting to the actual ULIP/ICEGATE API.
The module also handles successful searches, unsuccessful searches and simulated ICEGATE service failures.

Configuration / Prerequisites
Common Cargo Verification Framework completed.
ULIP client/service layer configured.
ICEGATE verification method implemented.
Import/Export declaration selection available.
Bill of Entry / Shipping Bill search type supported.
Port location input available.
Mock ICEGATE responses configured for success, failure and server-error scenarios.

Acceptance Criteria
User can select Import or Export declaration type.
Import verification supports Bill of Entry search.
Export verification supports Shipping Bill search.
User can provide the relevant declaration number and port location.
Successful ICEGATE responses are processed and displayed correctly.
Results display relevant customs information, including:
Declaration Number
Importer/Exporter
Declaration Status
Port
Cargo Description
Duty Status
Last Updated
Invalid declaration numbers result in a clear "No customs declaration found" response.
ICEGATE service exceptions are handled gracefully without crashing the application.
The module follows the common cargo verification workflow.
The mock implementation can be replaced with the actual ULIP/ICEGATE API after government approval and API access are provided.

Test Cases
TC01 – Import Bill of Entry Verification
Select Import → Bill of Entry and enter:
IMP-2026-001
Use any required port location.
Expected: Successful verification showing Customs Cleared, with cargo description Electronic Components and duty status Duty Paid.

TC02 – Export Shipping Bill Verification
Select Export → Shipping Bill and enter:
EXP-2026-001
Expected: Successful verification showing Let Export Order Issued, with cargo description Industrial Machinery and duty status Export Cleared.

TC03 – Second Import Declaration
Select Import → Bill of Entry and enter:
IMP-2026-002
Expected: Successful verification showing Under Assessment, with cargo description Computer Hardware and duty status Duty Assessment Pending.

TC04 – Invalid Declaration Number
Enter:
000-000000
Expected: Application displays a clear No customs declaration found for the provided reference message.

TC05 – ICEGATE Service Error
Enter:
ERROR500
Expected: Simulated ICEGATE service exception is handled gracefully and an appropriate service-unavailable/error message is displayed.

Actions

Also available in: PDF Atom