How to Design a Scalable Procurement System Architecture for Rapid Business Changes

1. Introduction

Yanxuan continuously faces changes in the commercial environment, such as traffic models, competitive landscapes, and sudden public health events like pandemics. The procurement system, a core component of Yanxuan's supply side, must have a solid top‑down design and ongoing evolution to cope with rapid business shifts and serve end users effectively.

2. Define Macro: Capturing the Underlying Stable Logic

Understanding the business positioning, supply‑chain characteristics, and technical architecture is essential for identifying the key points of the procurement system’s underlying architecture.

Business positioning determines long‑term direction. Once established, it remains relatively stable, guiding user perception and shaping all subsequent business activities. For example, an e‑commerce platform may adopt a platform model (e.g., Tmall) or a brand model (e.g., Yanxuan).

Business Characteristics

Architecture Characteristics

Platform model: massive merchant‑consumer matching, focus on transaction volume and GMV, little concern for manufacturing.

Fast‑growing scale, need for extensible table sharding and machine expansion, flexible front‑end design and solid back‑end capabilities.

Brand model: focus on loyal users and profit margin, end‑to‑end control from design/manufacturing to delivery and after‑sale.

Complex multi‑channel distribution, long product lifecycle, need for channel inventory and order abstractions.

2.2 Full‑Link Characteristics: Deep Collaboration & Bidirectional Drive

Long commercial chain : selection, sourcing, planning, contract signing, material coordination, production, quality control, logistics, warehousing, returns, finance, etc.

Many collaborative roles : product development, procurement, planning, quality, customs, finance, and others work closely together.

Complex layers : physical flow, information flow, capital flow, and increasingly, commercial flow intersect.

The supply‑chain business and technology act as interlocking gears. Early stages are business‑driven, requiring extensive online scenario implementation and data accumulation. As the system matures, technology‑driven scenarios emerge, showcasing intelligent features such as sales forecasting, smart replenishment, and inventory‑balanced procurement distribution. The architecture must balance current needs with future opportunities, avoiding over‑design while embracing intelligent possibilities.

2.3 Identifying Evolution Key Features: Accuracy and Availability

Availability : The system must provide uninterrupted service for daily operations across multiple roles.

Accuracy : Long, multi‑step procurement processes demand precise data to ensure cost control and reliable settlement.

Quantifiable metrics—online rate, failure rate for availability; SLA/SLO/SLI platforms for quality—should be integrated into the architecture monitoring dashboard rather than rebuilt from scratch.

3. Design Blueprint: Defining Stage‑wise Target Architecture

After clarifying the underlying logic, a stage‑wise blueprint can be created using views such as the bounded context diagram and business architecture diagram.

3.1 Bounded Context Diagram – The Basis for Division and Shielding

Dividing the large procurement system into smaller, manageable subsystems clarifies internal and external boundaries, enabling clear responsibility allocation and service granularity.

3.2 Business Architecture Diagram – Aligning Scenarios with System Capabilities

The diagram should express both horizontal (business process flow, stakeholder groups) and vertical (layered capabilities: scenario, product function, system ability, business model) dimensions.

4. Implementation: Building the System in Layers and Rhythm

4.1 First Floor – Horizontal Expansion

Construct a domain‑centric system map that covers business domains and delivers services at the system level.

4.2 Second Floor – Vertical Deepening

Validate scenario completeness, then iteratively enrich system capabilities (e.g., urgent approval, mobile approval) to meet deeper cost‑control, efficiency, and experience demands.

4.3 Third Floor – Automation & Intelligence

Automation and intelligence represent the ultimate stage, requiring long‑term exploration. Personalized procurement flows can skip risk‑heavy nodes for trusted users, dramatically improving efficiency.

5. Continuous Evolution: Dynamic Balance

Target architecture reflects an ideal state at a point in time; when key factors change, the architecture must be adjusted. For example, the 2020 Double‑11 promotion introduced a split sales peak (11‑1 to 11‑3 and 11‑11), demanding additional system capacity, rapid post‑event analysis, and supplemental replenishment tools.

Market change : Two sales peaks require capacity re‑evaluation.

Business change : Need for rapid post‑event review and a second replenishment cycle.

System change : Redesign for dual peaks, decision‑support tools, and urgent replenishment mechanisms.

6. Conclusion

Supply‑chain B‑side systems have high entry barriers, demanding both deep business insight and technical expertise from architects. Combining business sensitivity with architectural methodology and a dynamic growth perspective reveals true technical and business value.