Cargo EDI
Operational Lufthansa Cargo EDI / air-cargo messaging work for electronic shipment data, eAWB, eHouseManifest, PreCheck, cargo acceptance, status updates, acknowledgements, and error-message handling.
Fullstack / Integration Engineer at Lufthansa Cargo, Dec 2022 - Jan 2024
- eAWB
- shipment data
- FWB/FHL
- cargo messages
- PreCheck
- data validation
Work overview
A quick read on where the work sat, what made it hard, what I owned, and what changed.
Context
This was Lufthansa Cargo operational EDI, not supplier or invoice EDI. It sat next to the cargo booking flow and supported electronic shipment data exchange between forwarder systems, EDI providers, cargo services, eServices, PreCheck/eFreight processes, ground handling context, and internal cargo systems.
What was hard
EDI failures do not always look like normal API failures. A malformed FWB, missing FHL data, rejected acknowledgement, mapping issue, or status-message problem can delay PreCheck, eAWB/eHouseManifest processing, cargo acceptance, tracking, or manual follow-up.
My part
I supported the integration and platform side: Java/Spring service changes, deployment of EDI services, environment and partner configuration, validation and mapping support, CI/CD, monitoring, logs, documentation, troubleshooting, and support around message-processing issues.
What changed
The work helped keep electronic cargo data moving across booking, shipment-data transmission, PreCheck, eAWB/eHM, acceptance, status, acknowledgement, and error-feedback flows.
Constraints that mattered
- This must be described as Lufthansa Cargo operational EDI, not Lufthansa Group supplier/vendor invoice EDI.
- Partner-specific routing and message behavior varied, so support needed clean environment config and traceable processing paths.
- Message processing had to support both legacy and modern air-cargo standards such as Cargo-IMP and Cargo-XML concepts.
- Troubleshooting required enough correlation to understand whether a problem came from syntax, mapping, business validation, partner configuration, or downstream cargo services.
Approach
Treat EDI as cargo operations
The useful framing was not generic data exchange. The messages represented shipment data, AWB/HAWB context, acceptance readiness, status updates, acknowledgements, and rejection feedback.
Make message flows observable
For EDI, a failed process can mean a rejected message, missing acknowledgement, delayed status update, or manual correction path. Logs, correlation, alerts, and dashboards mattered.
Keep mapping and validation explicit
Cargo-IMP/Cargo-XML-style messages need syntax checks, version handling, transformation, canonical shipment data, and business validation before internal services can rely on them.
Key decisions
A few engineering choices that shaped the implementation and delivery path.
Name it air-cargo messaging, not generic EDI
Lufthansa also has supplier/vendor EDI contexts, while this work belongs to operational cargo data exchange.
The portfolio makes the domain clear: eAWB, eHouseManifest, PreCheck, shipment data, status, acknowledgements, and freight acceptance.
Show the process after booking
smartBooking explains offer and booking creation, but EDI explains how shipment and document data move along the transport chain.
The Lufthansa Cargo story becomes easier to understand as one flow: booking, shipment data, PreCheck/eAWB, acceptance, transport, and status updates.
Separate message purpose from implementation detail
EDI support depends on knowing whether the issue is transport, syntax, mapping, validation, or downstream processing.
Troubleshooting became more concrete because each message problem had a clearer place in the processing chain.
What I did
Built
- Java/Spring integration-service changes around EDI message handling, validation, mapping, and partner data flows.
- CI/CD and deployment support for EDI services across environment-specific configuration.
- Documentation and operational support for message-processing, acknowledgement, and error-feedback flows.
Improved
- Operational reliability through logging, monitoring, message-flow diagnostics, and troubleshooting support.
- Data-quality handling around shipment data, eAWB/eHouseManifest, PreCheck, and cargo acceptance processes.
- Clarity around where a message issue belonged: inbound channel, parser, mapping, validation, downstream service, or outbound acknowledgement.
Owned
- Support for FWB/FHL-style shipment-data flows, status updates, acknowledgements, and error-message handling across the processing chain.
- Release and runtime support for integration services connected to Lufthansa Cargo operational processes.
- Documentation and handover notes around message flow boundaries, processing states, and support paths.
Operational air-cargo EDI flow
A sanitized view of how shipment data and status messages moved between cargo partners and internal services.
Forwarders / EDI Providers
Partner systems, TMS, portals, and cargo messaging providers sending shipment and status data.
EDI Messaging Layer
Inbound channels, connectivity, routing, authentication, parsing, and message intake.
Validation & Mapping
Cargo-IMP/Cargo-XML-style syntax, version handling, transformation, and canonical shipment data.
Cargo Services
Booking context, eAWB, eHouseManifest, PreCheck, cargo acceptance, tracking, and operational processing.
Outbound Messaging
Acknowledgements, rejection/error feedback, and FSU/XFSU-style status updates back to customers or partners.
Learnings
- EDI is operational infrastructure: a message problem can become a freight-acceptance or customer-status problem.
- Cargo integrations need both legacy-standard awareness and modern operational discipline around CI/CD, monitoring, and troubleshooting.
- The best documentation explains message purpose and process impact, not only payload shape.