How “Endpoint Applications” Enable Multi‑Mini‑Program Flexibility in Weimob WOS

Preface

With the rollout of Weimob’s large‑customer strategy, merchant scenarios have become increasingly complex. A single store may use multiple mini‑programs, each offering different business functions.

To support this, the concept of an “endpoint application” is introduced. An endpoint application packages product functions, allowing a store to create multiple endpoint applications, each bundling different products and binding to a specific mini‑program, thus achieving differentiated functionality across mini‑programs.

Requirement Analysis

Merchants want distinct business functions to be carried by different mini‑programs because the boundaries between these functions are clear. This also helps convey clearer usage scenarios to users and improves experience.

Another scenario is merchants creating multiple mini‑programs with identical functionality for promotion across different channels.

In Weimob WOS, the smallest unit of business functionality is defined as a “product” (e.g., Mall, CRM, Guide). By combining and packaging different products, a “solution” can be built to meet various industry scenarios.

We found that the dimension used by merchants to divide mini‑program functions aligns with WOS’s product dimension, so the solution‑packaging concept can be analogously applied to user‑side functions, packaging them by product.

The answer is yes – this packaging is called an “endpoint application”.

Furthermore, endpoint applications can package the same product, satisfying the second scenario of identical functionality across multiple mini‑programs.

Core Concept

An endpoint application is a combination of product functions owned by a merchant’s C‑side. Its ID field is called CID.

Default endpoint applications: each BosID has a unique default endpoint application, generated when the first product purchase instance message is detected. The default endpoint application includes all product instances under that BosID that are in an active state.

Custom endpoint applications: endpoint applications created by merchants that package custom product instances.

Product Instance and Endpoint Application Relationship

1. When packaging an endpoint application, the included product instances must be explicitly defined.

2. A product instance can be included in multiple endpoint applications.

3. The relationship between product instances and endpoint applications is n:m.

Channel and Endpoint Application Relationship

1. An endpoint application can contain multiple channels (WeChat mini‑program, Official Account, H5, Douyin mini‑program, Alipay mini‑program, etc.). All channels within the same endpoint application share the same endpoint application ID.

2. Within the same endpoint application, user data should be unified; across multiple endpoint applications under the same merchant, user unification can be optional.

Upstream/Downstream and Endpoint Application Relationship

Endpoint applications listen to product fulfillment messages (purchase and unsubscribe) to create and initialize default endpoint applications, adding or removing product instances as they are subscribed or unsubscribed.

Endpoint applications expose query interfaces for external use.

When an endpoint application changes, it emits change events to notify downstream services.

Change process:

(1) Maintain non‑unsubscribed product instances; if an instance is unsubscribed, it is removed from the endpoint application.

(2) The default endpoint application monitors the status of all product instances under the store.

(3) Custom endpoint applications monitor the status of product instances manually associated by the user.

Product Functions

The use of endpoint applications is closely tied to channel authorization scenarios. To ensure a smooth merchant experience, endpoint application management is integrated into the channel authorization flow, linking channel authorization, endpoint application creation, and binding into a single process. The main flow for a WeChat mini‑program authorization is illustrated in the diagram.

Business Application

Weimob Value‑Customer Promotion (值客推) is a D2C e‑commerce marketing solution built on Weimob WOS. It uses multiple mini‑programs across different channels to reach users, addressing challenges such as low organic traffic, poor conversion, and difficulty in repeat purchases.

In this solution, multiple endpoint applications are created, each packaging the relevant products of the Value‑Customer Promotion solution and binding to a specific WeChat mini‑program, enabling multiple mini‑programs under the same store.

Future Planning

Products and organizational nodes have an activation relationship. Since endpoint applications package products, they can theoretically access all organizational nodes opened by those products. The future plan focuses on managing the relationship between organizational nodes and endpoint applications, allowing configurable constraints on which nodes an endpoint application can use.

Key points of the future plan:

Each BosID can have multiple endpoint applications, each belonging to a single BosID (1:n relationship).

An endpoint application can be assigned to multiple VIDs, and a VID can have multiple endpoint applications (n:m relationship).

VIDs are associated with product instances; endpoint applications are linked to VIDs based on this association.

Conclusion

Within the Weimob WOS ecosystem, endpoint applications leverage underlying product and organizational capabilities to provide flexibility and extensibility. They effectively support the launch of the Value‑Customer Promotion solution, and future roadmap will gradually implement advanced management of endpoint‑application and organizational‑node relationships to meet evolving merchant needs.