OMS · TMS · WMS · EPOD
Understanding the operational workflow behind each system.
Scope of my contribution
Alongside my primary KL Club responsibilities, I provided architecture, system-design and business-use-case support across logistics applications. Each system had dedicated project managers, business analysts and developers.
My contribution focused on understanding operational requirements, reviewing technical approaches and supporting integration decisions across the broader application landscape.
Distinct operational responsibilities
Order intake & distributionWMS
Warehouse execution
Delivery planning & executionEPOD
Delivery-completion evidence
Responsibility map. No specific integration sequence is implied.
OMS — order intake
Client order intake and distribution to downstream logistics applications.
WMS — warehouse operations
Inbound and outbound workflows, inventory, stock allocation, transfers, picking and packing, and batch handling.
TMS — transportation
Last-mile planning, courier and driver assignment, scheduling and route execution.
EPOD — completion evidence
Electronic proof-of-delivery workflows and delivery-completion evidence.
How I approached the work
Start with the business use case
Order intake, warehouse handling, transport planning and delivery confirmation describe different stages of operational work. System design discussions needed to connect these workflows with the teams responsible for them.
Review integration in context
I worked with the dedicated teams to analyze workflows, review implementation approaches and support cross-system technical decisions. My role complemented their delivery ownership.
What this experience added
The work broadened my logistics domain knowledge beyond commerce into warehouse, transportation and delivery operations. It also developed my ability to support architecture decisions across teams while keeping responsibility clear.