Message mapping
EDIFACT segments are mapped field by field to your ERP, depot and operations data, with partner-specific rules kept in configuration rather than code.
EDI Integration
EDI integration that speaks your partners’ language
We connect the electronic data you exchange with shipping lines, customers and suppliers to your own systems—through message mapping, validation, secure delivery and monitoring.
Trading partners
Shipping line
Customer
Supplier
Pars Medya EDI
- 01Receive
- 02Validate
- 03Map
- 04Deliver
CODECODESTIMAPERAK
Your systems
ERP
Depot / yard
Accounting
Overview
What is EDI and why does it matter?
EDI (Electronic Data Interchange) is the automated exchange of business documents—orders, bookings, gate movements, repair estimates or invoices—between companies in a standard format, without manual re-entry. In logistics, the most common standard is UN/EDIFACT.
EDI messages follow rules agreed bilaterally with each trading partner. A successful integration is therefore more than sending files: every segment must be mapped correctly, validated against the rules, acknowledged and monitored so that errors are visible.
Pars Medya has built an EDI platform with an EDIFACT parser and serializer core, message-specific rules, SFTP transport adapters and a background processing queue. We adapt the same architecture to your trading partners and internal systems.
EDIFACT
Message families we work with
We work with the EDIFACT messages used between container depots and shipping lines. Each message is mapped according to the partner’s message implementation guide (MIG).
CODECO
Container gate-in/gate-out and yard movement reports
DESTIM
Maintenance & repair (M&R) estimates, repair orders and revisions
COPARN
Container pre-announcement and release instructions
IFTMBC
Booking confirmations and version tracking
APERAK
Technical and application-level acknowledgements
CEDEX
Damage and repair code validation against the standard dataset
Formats and delivery channels
Standards
- UN/EDIFACT (directories such as D96B, D00B, D06B)
- XML and JSON transformations
- CSV / fixed-length files
Delivery
- SFTP (automated pickup and delivery)
- REST API and webhooks
- AS2 where the partner requires it
Assurance
- Message rule and code list validation
- Acknowledgement (APERAK) matching
- Audit trail and sensitive data masking
Capabilities
What our EDI integration covers
Validation engine
Mandatory fields, code lists and business rules are checked before sending, so faulty messages are caught before they reach a partner.
Secure delivery
Automated pickup and delivery over SFTP and APIs, with retries and a file lifecycle log.
Processing queue
Messages are queued in a worker process that runs independently of the web interface, so nothing is lost under load.
Acknowledgement tracking
The acknowledgement status of every message is tracked; rejections and errors reach your team as clear alerts.
Monitoring dashboard
See which message went to which partner and when, what is pending and what failed—on one screen.
Process
How an EDI project runs
- 01
Partner & message analysis
We clarify which messages are exchanged with which partners, in which direction and how often.
- 02
MIG & mapping design
We derive segment and field mappings from each partner’s message implementation guide.
- 03
Build & validation
Parsing, generation and validation rules are developed and tested against golden sample messages.
- 04
Partner testing
Connectivity, file naming and acknowledgement flows are verified with the partner in a test environment.
- 05
Go-live & monitoring
After a controlled cut-over we monitor traffic and onboard new partners onto the same platform.
Industries
Who is it for?
EDI reduces manual data entry for any business that exchanges documents with partners regularly and at volume.
- Container depots
- Port & terminal operations
- Logistics & transport
- Foreign trade
- Manufacturing supply chains
- Retail & distribution
EDI integration FAQ
What is the difference between EDI and API integration?
APIs work in real time between two systems through defined endpoints. EDI uses industry-wide message standards, usually file-based and governed by rules agreed with each partner. Projects often combine both: we receive the EDI message and pass it to internal systems through APIs.
Can it connect to our existing ERP or depot software?
Yes. We review the APIs, database access or file transfer options your systems provide and build a secure middle layer that moves EDI data into them.
Do we need our partner’s message guide (MIG)?
Yes. Because EDI messages follow rules agreed with each partner, accurate mapping needs the partner’s message implementation guide and sample messages. We help you manage that process.
How are failed or rejected messages handled?
Messages are validated before sending; rejections and error responses from partners are matched to the original message, raised to your team as alerts and can be resent after correction.
Contact
Let’s turn your next idea into a reliable digital product
Tell us about your goals. We will review the opportunity and return with a practical next step.