Value chain sales history platform

TWM687305UActive Publication Date: 2026-09-11FORMOSA TECH CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
TW115202081
Authority / Receiving Office
TW · TW
Patent Type
Utility models
Current Assignee / Owner
Filing Date
2026-03-10
Publication Date
2026-09-11
Estimated Expiration
2036-03-09

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

This invention provides a value chain sales history platform, comprising a platform server, a customer data database, and multiple user terminals. The platform server, through a cross-system integration module, obtains front-end order and transaction data and customer interaction data from enterprise resource planning systems, etc., and generates a single customer view after data normalization. The sales history module then generates chronological sales history records. The operational dynamic analysis module calculates revenue trends and target achievement, and the risk detection sub-module identifies potential risks. The recommendation module provides personalized recommendations based on a relevance, frequency, and monetary analysis model, presented on a graphical user interface with notification alerts, to facilitate collaboration among sales, customer service, and operational staff and improve decision-making efficiency.
Need to check novelty before this filing date? Find Prior Art

Claims

1. A value chain sales history platform, comprising: a platform server including at least one processor and at least one non-transitory memory, the non-transitory memory storing instructions; a customer data database coupled to the platform server; and multiple user terminals communicatively connected to the platform server via a network; wherein, When the instruction is executed by the processor, the platform server: obtains customer-related data from multiple enterprise information systems via a cross-system integration module, wherein the enterprise information systems include an enterprise resource planning system, and the customer-related data includes: front-end order and transaction data; and customer interaction data spanning pre-sales, sales, and after-sales events; normalizes the customer-related data into a unified data framework and associates the normalized data with a customer identification code to generate a single customer view for a corresponding customer; generates a sales history record for the corresponding customer based on the single customer view using a sales history module, the sales history record including a chronological representation of at least one portion of the pre-sales, sales, and after-sales events; and calculates at least one operational dynamic output based on the front-end order and transaction data using a campaign dynamic analysis module, the at least one operational dynamic output including a revenue trend indicator and a target achievement indicator for a selected time period. A risk detection submodule determines a potential risk indicator for the corresponding customer based on the change of at least one metric derived from the front-end order and transaction data relative to a benchmark; a recommendation module generates a personalized recommendation for the corresponding customer using an RFM model based on recency, frequency, and monetary value derived from the front-end order and transaction data; and a graphical user interface is presented on at least one of the multiple user terminals, displaying a single customer view, the sales history record, the at least one operational dynamic output, the potential risk indicator, and the personalized recommendation.

2. The value chain sales history platform as described in Request 1, wherein the plurality of enterprise information systems further includes at least one of the following: a customer relationship management system, a customer service ticketing system, a marketing system, and an order entry portal website.

3. The value chain sales history platform as described in Request 1, wherein associating the formalized data with the customer identification code includes: performing customer identity resolution using at least one of the following: a master customer data table; a mapping table; and a comparison rule based on at least one of the following: company name, unified number / tax identification code, account number, and contact information.

4. The value chain sales history platform as described in Request 1, wherein the chronological representation includes a timeline, and the timeline includes multiple event items, and each event item includes at least an event type, an event timestamp, and a related transaction reference.

5. The value chain sales history platform as described in Request 1, wherein the pre-sales, sales and after-sales events include at least one of the following: inquiry events, quotation events, sample request events, order placement events, shipment / fulfillment status events, payment status events, and service / customer complaint events.

6. The value chain sales history platform as described in Request 1, wherein the revenue trend analysis module calculates the revenue trend indicator by summing the transaction amount over the selected time period and comparing the summed transaction amount across multiple sub-periods within the selected time period.

7. The value chain sales history platform as described in claim 1, wherein the target achievement metric is calculated by comparing the total transaction amount for one of the selected time periods with a predetermined target value stored in the customer data repository.

8. The value chain sales history platform as described in claim 1, wherein the potential risk indicator is determined based on at least one of the following: a decrease in order frequency measure relative to one of the benchmarks; an increase in relevance measure relative to one of the benchmarks; and a decrease in amount measure relative to one of the benchmarks.

9. The value chain sales history platform as described in Request 1 further includes a notification module configured to push an alert to at least one of the plurality of user terminals when the potential risk indicator meets a threshold condition.

10. The value chain sales history platform as described in claim 1, wherein the RFM model comprises: relevance defined as a time interval from the most recent order; frequency defined as the number of orders within a predetermined window; and amount defined as the sum of transaction amounts within the predetermined window.

11. The value chain sales history platform as described in Request 1, wherein the personalized recommendations include at least one of the following: product recommendations, cross-selling recommendations, upselling recommendations, and next-best-action recommendations.

12. The value chain sales history platform as described in claim 1 further includes a collaboration module configured to allow multiple roles, including sales, marketing, and customer service, to add annotations and action items to the sales history records through the graphical user interface.

13. The value chain sales history platform as described in claim 12 further includes an access control module configured to perform role-based access control on at least one of the following: viewing, editing, and exporting of the single customer view and the sales history records.

14. The value chain sales history platform as described in claim 12 further includes an audit record module configured to store a change history in the customer data repository, the change history indicating at least: who performed the change, when the change was performed, and what was changed.

15. The value chain sales history platform as described in claim 1, wherein obtaining customer-related information comprises at least one of the following: retrieving the customer-related information near real-time via an application interface; and retrieving the customer-related information synchronously via a batch of programs.