Skip to main content
This guide describes how declaration data flows through the Eaze Customs platform and the lifecycle states of a customs declaration. The most common way customers integrate with the declaration process is by following the flow below.
Customs Systems
EC
Customer
4. Customs Response
3. Declaration
2. Enrich Data
5. Update Status and Data
1. Shipments
6. Notifications
  1. Shipments: You create a shipment containing the goods, deliveries, and delivery items.
  2. Enrich data: EC validates and enriches the shipment data to automatically generate declarations.
  3. Declaration: EC validates and submits the declaration to the customs authority system.
  4. Customs response: The customs authority processes the declaration and returns status updates, requests, or release messages.
  5. Update status & data: EC updates the declaration status and data based on the customs response.
  6. Notification: You receive updates through webhooks, API polling, or the user interface.

​
Declaration lifecycle

Every declaration goes through several processing stages from creation to final customs clearance and exit confirmation.
Init
New
Valid
Invalid
Submitted
Customs Error
Accepted
Sending/Provider Error
Released
Exit Confirmed
Flow started & splitting done
Deductions & validations
Send to customs
Customs validation failed
Accepted by customs
Customs communication
failed temporarily
Released by customs
Legend
Declaration States
StateStandard processing states (e.g., Init, New, Valid, Submitted, Accepted)
ReleasedSuccessful clearance and confirmation (Released, Exit Confirmed)
ErrorValidation failure or customs rejection (Invalid, Customs Error)
Temp ErrorTemporary network/provider communication failure
Transitions & Actions
ActionActions and validation steps that move declarations between states

​
Lifecycle stages explained

  • Init: The pipeline is initialized, and shipment consignments are automatically split into separate declarations based on country of origin, destination, and other grouping rules.
  • New: The declaration is created in the system.
  • Valid / Invalid: Eaze Customs runs automated data validations and enrichment. If any required fields are missing or invalid, the declaration is marked as Invalid for review. Otherwise, it moves to Valid.
  • Submitted: The declaration is successfully transmitted to the customs authority.
  • CustomsError: The declaration is rejected by customs due to validation errors.
  • Sending/ProviderError: There is a temporary communication failure with the customs server; the system will retry transmission.
  • Accepted: Customs has validated and accepted the declaration filing.
  • Released: Customs has cleared the declaration and released the goods for transit or free circulation.
  • ExitConfirmed: Physical verification that the goods have departed the customs territory.

​
Status descriptions

StatusDescription
NEWDeclaration has been created from shipment data.
READY_TO_DECLAREValidation completed successfully and declaration is ready for submission.
INVALIDValidation errors were found and user action is required.
PRE_LODGEDDeclaration has been pre-lodged with customs.
REGISTEREDCustoms has registered the declaration.
ACKNOWLEDGEDCustoms has accepted receipt of the declaration.
CONTROLCustoms inspection or control process is required.
RELEASEDGoods have been released by customs.
NO_RELEASECustoms rejected release of the goods.
COMPLETEDFinal successful completion of the declaration process.
CANCELLATION_REQCancellation has been requested.
CANCELEDDeclaration has been canceled.