How Our Platform Products Empower Business: User Center & Order Management Blueprint

In the 2024 company‑level product strategy, we divide the product line into platform products and commercialized goods. Platform products serve as the company’s infrastructure and a collection of general capabilities that empower commercial products by providing basic services and core abilities for common scenarios.

Historically, our platform capabilities and product construction have been scattered across various product lines and projects, lacking unified planning and investment, which has led to gaps in foundational abilities and duplicated efforts, such as fragmented user systems and inconsistent order models.

After the platform product received GR approval in the first half of this year, we conducted detailed research and discussions on the current platform architecture, basic design, and general capabilities, proposing product solutions and achieving preliminary results. We hope this initial exploration offers insights and invites further discussion to continuously improve the platform products.

1. What Are Our Platform Products?

Platform products focus on foundational and generic capabilities, covering IoT data collection, data processing and algorithm services, logistics capacity, order models, and user systems. Design principles are driven by business needs, abstraction, scalability, reusability, and stability, establishing service standards. Their core task is to determine product line positioning, functional boundaries, and interaction interfaces from a company‑wide perspective, guiding resource allocation and priority.

2. What Problems Do Platform Products Solve?

The discussion centers on the Platform User Center and the Platform Order/Waybill Center .

User Center

Creating a unified, secure, and convenient user management platform to solve existing issues, improve user experience, enable cross‑system functionality sharing, and meet diverse customer needs.

Resolve existing user system problems: Consolidate fragmented user systems, improve planning, increase feature reuse, reduce integration costs, and enhance authentication security.

Provide a unified user experience: Centralized authentication enables single sign‑on across systems, improving convenience.

Support multi‑tenant architecture: Allows data isolation, resource sharing, and permission management for different business systems.

Ensure user security: Centralized identity management strengthens password and account protection with auditing and monitoring.

Facilitate cross‑system feature sharing: Offers foundational services for coordinated system collaboration, boosting overall efficiency.

Data shows many customers use multiple systems (e.g., E6, G7S, 财运通), leading to account integration challenges. Industry solutions fall into three categories: strong binding, weak binding, and silent binding.

We analyzed similarities (no large‑scale account restructuring) and differences (various binding techniques) among existing solutions. Because G7S, 财运通, and 易流云 have completely independent account systems, we adopted a phone‑number‑based login approach that allows natural persons to access multiple business systems while maintaining a standardized, unified, and secure entry point for the platform and flexible customization for individual services.

Order/Waybill Center

By unifying the order model, optimizing collaboration, enhancing adaptability, reducing costs, improving information sharing, supporting business expansion, and adhering to design principles, the center addresses current challenges.

Unified integration: Solves inconsistent order models across systems, lowering integration costs and increasing efficiency.

Optimized collaboration: Promotes coordinated work among systems, improving information flow.

Enhanced adaptability: Meets diverse customer and scenario requirements, supporting product growth.

Cost reduction: Avoids duplicate development and resource waste.

Improved information sharing: Enables end‑to‑end data exchange across the chain.

Business expansion support: Provides a scalable foundation for new market opportunities.

Optimized basic services: Offers stable, flexible data models and services for multi‑system assembly.

Design principle compliance: Follows high abstraction and minimalism for performance and maintainability.

For our company, the “order” is the upstream request from shippers to carriers, describing transport needs and can be split into sub‑orders. The “waybill” records the carrier’s execution details, serving as a transport proof and internal workflow document.

To achieve end‑to‑end fulfillment, we must associate and share information about people, goods, and vehicles at loading/unloading sites, supporting various transport scenarios such as single‑load/single‑unload, multi‑load/multi‑unload, and multimodal transport.

We experimented with multiple scenarios, illustrating how shippers and carriers can split, merge, and delegate orders across nodes.

In summary, the evolution of platform products must be driven by business needs, emphasizing scalability, reusability, and stability. The user center and order/waybill center should provide unified, secure, and convenient services, while account integration should adopt appropriate solutions to gradually achieve seamless user identity across systems, enhancing service experience and enabling extensive data utilization.