Knowledge Post: Five Key Elements of B2B Supply Chain System Design—Easy to Learn

Are the five key elements of B2B system design “the Way” or “the Art”?

01    The Value of B2B Systems

Before diving into the main topic, it is essential to first reflect on the existence and positioning of B‑to‑B systems. Only by clarifying their role can we better understand how to design them effectively.

The success of any business model—whether it operates in a unilateral or bilateral market—depends on both the user side and the platform side. The user side primarily interacts with end users, leveraging consumer-facing systems such as PC websites, mobile apps, and mini-programs, which are responsible for delivering consumer‑oriented services and driving new user acquisition and retention. Platform-side correspondence In B2B operations, the use of B2B systems—such as order management, payment, inventory, and supply chain systems—not only provides backend support for B2C customers but also plays a critical role in driving internal cost reduction and efficiency gains.

▲Value Positioning of the Consumer‑Facing System and the Business‑Facing System

Throughout the course of business operations, B‑to‑B systems encompass all capabilities that lie beyond the C‑to‑C user experience. For instance, in the order‑placement process, pre‑order functions such as search, product listings and details, adding items to the cart, and the checkout flow are part of the C‑to‑C domain. Once an order is placed, however, fulfillment, warehousing, and logistics fall squarely within the B‑to‑B scope. Striking the right balance—maximizing efficiency while minimizing costs without compromising user experience—is the core objective of B‑to‑B operations and the very raison d’être of B‑to‑B systems. The goal of B2B system design is to better support the business in achieving its objectives, and it must be grounded in sound business rationale.

02   B2B Business Development Process

Once we understand the intrinsic value of B‑to‑B systems, we no longer design them in isolation. We recognize that system design must align with business needs—this is precisely where the value of a B‑to‑B product manager lies. Before designing a system, we first map out the business processes and then translate the parts that require system support into concrete requirements. Take creating a purchase order as an example and walk through the process from business analysis to system design: First, the purpose of a purchase order is to procure item X from supplier A. To initiate the procurement process, basic information such as item S and supplier details must be available, so these need to be fully maintained in the system beforehand. Next, different procurement scenarios call for distinct workflows and response strategies. For instance, varying purchase prices may necessitate different approval procedures—for example, orders under 2,000 require no approval, those between 2,000 and 10,000 need departmental approval, and amounts exceeding 10,000 require director-level clearance. Therefore, before starting procurement, it’s essential to predefine approval workflows and tailor approval policies to specific spending thresholds. Only after this foundational information is in place can purchase orders be created within the system. What functionalities are required for order creation? After surveying purchasing staff’s daily workflows, we identified three core capabilities: creating purchase orders, editing (modifying or deleting) existing orders, and approving orders. These are the most critical functions in the purchase‑order‑creation process, frequently performed by users, and must be supported by the system. Accordingly, the system design should include support for creating, editing, and approving purchase orders. Meanwhile, to make the procurement workflow more efficient and seamless, buyers requested features such as batch order creation (enabling multiple orders to be generated at once) and import/export capabilities. While these aren’t core functions, their absence would significantly hamper user productivity. Finally, to assess procurement performance and facilitate day-to-day operations, buyers need regular statistical analysis of purchase orders. Thus, the system should also incorporate order‑analysis and reporting features. In summary, for a complete purchase‑order workflow to operate smoothly, five key system capabilities must align with the business requirements, as illustrated below.

▲ Procurement Order Creation Process

These five system processes follow a specific sequence and are prioritized according to urgency and importance. In terms of order, they must be executed sequentially from ① to ⑤. As for priority, ①, ②, and ③ are more critical and urgent, while ④ and ⑤ are important but not urgent. By further abstracting this workflow, we arrive at a general model that applies to most B2B business processes: 1) Establish foundational data; 2) Configure business strategies; 3) Execute business operations; 4) Add supporting tools; 5) Generate statistical reports.

▲General Model for B2B Business Operations

03    Five Key Elements of B2B System Design

Along Based on the general model for B‑to‑B business operations, we have derived five essential components of B‑to‑B system design: every comprehensive B‑to‑B system must incorporate a foundational data module, a policies and configuration module, a business processing module, auxiliary tools, and reporting capabilities. Just like the foundation, the level ground, the main structure, the doors and windows, and the roof of a house, each component is indispensable. I. Basic Data Module: Static data that is defined prior to the occurrence of a business process and used to identify a specific business or entity, such as product and supplier data in a procurement system, location‑based storage data in a warehouse, or accounting chart of accounts in a financial system; II. Strategy and Configuration Module: Business rules pre‑defined to guide operational execution, encompassing parameters, configuration settings, and system logic—such as procurement approval policies, warehouse receiving procedures, product listing guidelines, and free‑shipping criteria. III. Business Processing Module: Executing and recording the business process is the most fundamental and widely used functionality for completing business operations. It is typically documented in the form of documents, encompassing the sequence of business events and associated data, document status transitions, and relevant operation interfaces. Examples include purchase orders in a procurement system, inbound and outbound inventory management workflows in a warehouse system, accounting processes in a financial system, and work order creation and routing procedures in a work order management system. IV. Auxiliary Tools: To support the achievement of business objectives, software and hardware features are added to reduce costs, improve efficiency, and enhance fault tolerance and error prevention—such as commonly used batch processing and import/export capabilities, as well as various automated devices in logistics. V. Statistical Reports: Kanban boards, reports, and other tools used for statistical analysis and business data querying help to better visualize the overall picture of operations and identify operational issues.

▲Five Key Elements of B2B System Design

Developing B‑to‑B business is like building a house: the foundational data module serves as the bedrock of the business, much like the foundation of a structure—without it, no towering edifice can rise from the ground. Moreover, if the foundation is unstable, the entire structure will be precarious. The strategy and configuration module provides essential preconditions for business operations, akin to the level surface on which the house stands; whether you eventually build a single‑story home, an apartment building, or a villa depends on the design and quality of that base. The business processing module constitutes the core functionality, comparable to the main structural framework of a house—it is the most critical component for delivering the final product and the part users interact with most frequently. Auxiliary tools enhance operational efficiency, much like doors and windows, making the space more ventilated and bright; while their absence does not necessarily prevent habitation, the overall experience would be significantly diminished. Finally, statistical reports offer a macro‑level view of the business process and its quality from a data perspective, serving as the roof that supports the entire structure—its purpose is to shield the building from the elements. The figure below illustrates several functional menus within a particular ERP system, each of which can be mapped one‑to‑one with the five key components described above.

①Product Management → Master Data

② System Settings → Policy Configuration

③ Purchase Order Management → Business Processing

④Home Dashboard → Statistical Reports

⑤ Import, Export, and Batch Operations → Utilities

04   Application of the Five Elements of B2B Design

Some friends may ask, “We already know the five elements—so what’s the point of them?” The five elements are a design methodology distilled from B‑to‑B systems after stripping away business-specific details. No longer tied to any particular business context, they simplify system design. In everyday work, we can leverage these five elements to generalize and apply their principles more broadly: I. Based on Five elements for designing a system from zero to one. The Five Elements constitute an excellent system framework. When designing a system from scratch, they enable rapid functional grouping; in fact, the menu structures of many systems are organized according to these five elements. II. Based on Five key elements for switching careers and learning. When transitioning to a new B2B business domain, we can leverage the five key elements to accelerate learning and address knowledge gaps. For example, moving from the supply chain space to the SaaS sector—though the business and industry have changed—the underlying principles of B2B system design remain consistent. By applying these five elements, we can quickly master foundational data, strategy configuration, and business‑process modules, grasp the core essentials, and achieve twice the results with half the effort. III. Based on The five elements allow for a clear understanding of the positioning and value of each system function. If it’s core business processing, the value is certainly high; but if it’s an auxiliary tool, you’ll need to assess its business value. IV. May be based on Five factors for rapidly prioritizing projects. If the implementation involves core data, policy configuration, and business‑processing requirements, these are undoubtedly critical and urgent and should be prioritized. By contrast, auxiliary tools and statistical analysis are relatively less time‑sensitive. In our day‑to‑day work, each of us can leverage the five key elements to design systems, pursue cross‑functional learning, and make swift, informed decisions about project priorities. Moreover, by applying these same five elements, we can clearly articulate the role and value of each system feature, enabling more effective assessment of its business impact.

05   Conclusion

We are currently in In the VUCA era—characterized by volatility, uncertainty, complexity, and ambiguity—high salaries are a thing of the past, and the safety net of big corporations has vanished. Change is happening so rapidly that even our best efforts can’t keep up, leaving us exhausted and barely able to catch our breath. We want to give up, yet we lack the resources to simply “lie flat”; all we can do is endure in silence, carrying our sorrows privately. If the outcome seems predetermined to be unfavorable, might we adjust our mindset, slow down, and seek out something more certain? I believe that, just as with B‑to‑B system design, the functioning of society itself operates as an intricate system—one in which certain constants remain unchanged. These constants constitute the underlying logic of our world. Only by mastering them do we truly grasp the “way” of application, rather than merely acquiring superficial “techniques.” For example, reading classic books and watching timeless films; maintaining a healthy lifestyle with regular exercise and sound sleep; studying foundational principles; understanding the patterns governing how things evolve; and learning to think with greater long-term perspective. These truths are familiar to us from childhood, passed down from one generation to the next—timeless guidelines for navigating life that have endured through shifting eras. They are worth deeply reflecting upon for each of us, whether we’ve felt anxious in the past or continue to do so today. So, in your view, are the five key elements of B‑to‑B system design “the way” or merely “the technique”?