Express-Link / KL Club
Reusable commerce on shared customer capabilities.
Context & my contribution
KL Club was a reusable commerce module within KLN’s Express-Link / K-Idea customer platform. I led its technical design and major development, from business requirements and backend design to implementation and coordination with stakeholders and developers.
I also contributed to the shared user and payment modules. The wider platform and logistics applications involved other dedicated teams.
Commerce within a shared platform
Conceptual capability and fulfillment map.
Design decisions & trade-offs
Reuse genuinely shared capabilities
Identity/SSO, loyalty, payments and notifications were shared across customer applications. KL Club integrated with these services rather than maintaining its own isolated versions. This enabled reuse while introducing dependencies on shared interfaces and availability.
Build commerce for multiple storefronts
Product variants and versioning, promotions, merchant-managed listings, and organization-specific visibility and pricing supported different storefront needs within the commerce module. The added flexibility required more explicit eligibility and pricing rules.
Decompose orders around merchant fulfillment
Customer orders were decomposed into merchant-level orders. Fulfillment could follow direct merchant delivery or KLN consolidation, including partial shipment requirements. Customer-facing orders and operational fulfillment therefore needed distinct responsibilities.
Centralize payment integration
The shared payment module managed application-specific provider configuration and integrations including Visa, Mastercard, PayMe, WeChat Pay and Alipay. My contribution supported this shared module; I did not independently own the entire platform.
What the work delivered
KL Club provided reusable multi-storefront commerce integrated with shared customer capabilities and two fulfillment models. My role combined domain analysis, system design, major development and continuing technical leadership.
This experience shaped how I approach platform reuse: shared modules need clear ownership and interfaces, while application-specific business rules remain explicit.