🎯 cargoLogix | EDI Engine Certification Requirement
Under RMIG Model 1: Commercial Consolidator to Postal Network Integration
📌 EDI API Endpoint: https://ediapi.api.post/
Authentication: Token-based with EDI mailbox and application ID
Key APIs: /EventMappingConfiguration, /MailItems, /CustomsDeclaration, /CargoConsignments
Operator: cargoLogix - Commercial Consolidator operating under RMIG Model 1 (Commercial-to-Postal framework)
🎯 UPU EDI Engine Certification Scope - cargoLogix Implementation
Objective: Certifying cargoLogix as a commercial consolidator to integrate with the postal network using RMIG Model 1 framework
Required Implementation: Generate mandatory EDI events and messages from item collection through handover to Destination postal customs
Certification Focus: Events marked with ★ REQUIRED are mandatory for successful certification
📋 Required Events for EDI Engine Certification
cargoLogix Must Generate:
- EMA - Item collection
- ITMATT - Customs declaration
- EMB - Consolidation
- EMC - Departure (triggers Carrier Docs)
Destination Post Generates:
- CUSITM - Customs pre-advice
- EDB - Customs presentation
- EMD - Arrival confirmation
Supporting Messages (Optional):
- PREDES - Dispatch pre-advice
- CARDIT - Carrier document
- RESDIT - Transport status
- CUSRSP - Customs response
Items successfully handed to postal customs
Disclaimer: S10 Barcodes, Desination Post Names and EDI Messages used are for referrence purpose only.