Sales promotion management system

Abstract

To more suitably perform sales promotion planning.SOLUTION: A promotion plan management system that manages a promotion plan that can be repeatedly implemented over a plurality of implementation periods, the promotion plan management system including a setting unit that sets extraction conditions for extracting a promotion target customer and a promotion target product in advance based on an operation, an extraction unit that extracts the promotion target customer and the promotion target product based on the extraction conditions, and a changing unit that changes the extraction conditions based on extraction condition change information for a second and subsequent promotion plans that are repeatedly implemented, the setting unit sets the extraction condition change information in advance on the basis of an operation, and the extraction unit extracts the sales promotion target customer and the sales promotion target product on the basis of the changed extraction condition when the extraction condition is changed by the change unit for the second and subsequent sales promotions which are repeatedly performed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a sales promotion planning management system. [Background technology]

[0002] BACKGROUND ART A coupon issuing system is known that issues coupons taking into consideration the amount of profit (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-235919 Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for improvement in the implementation of sales promotion plans (sales promotion plans) such as issuing coupons.

[0005] The present invention has been made in view of the above circumstances, and aims to provide a technique for more suitably implementing sales promotion plans. [Means for solving the problem]

[0006] One aspect of the present invention for solving the above-mentioned problems is a sales promotion plan management system that manages sales promotion plans that can be implemented repeatedly over multiple implementation periods, and includes a setting unit that sets extraction conditions for extracting sales promotion target customers and sales promotion target products in advance based on operation, an extraction unit that extracts sales promotion target customers and sales promotion target products based on the extraction conditions, and a modification unit that modifies the extraction conditions based on extraction condition modification information for sales promotion plans that are implemented repeatedly from the second time onwards, wherein the setting unit sets the extraction condition modification information in advance based on operation, and when the extraction conditions are changed by the modification unit for sales promotion plans that are implemented repeatedly from the second time onwards, the extraction unit extracts sales promotion target customers and sales promotion target products based on the modified extraction conditions. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 2 is an explanatory diagram illustrating the configuration of a store system S and a headquarters system H. [Figure 2] FIG. 2 is an explanatory diagram illustrating the functions of the sales promotion planning management system 1. [Figure 3] 10 is a display example of the display unit 100. [Figure 4] 10 is a display example of the display unit 100. [Figure 5] 10 is a display example of the display unit 100. [Figure 6] 10 is a display example of the display unit 100. [Figure 7] 10 is a display example of the display unit 100. [Figure 8] 4 is a flowchart showing an example of the operation of the sales promotion plan management system 1. [Figure 9] 4 is a flowchart showing an example of the operation of the sales promotion plan management system 1. DETAILED DESCRIPTION OF THE INVENTION

[0008] FIG. 1 is an explanatory diagram illustrating the configuration of a store system S and a headquarters system H. The store system S and headquarters system H are applicable to various business types (supermarkets, convenience stores, drug stores, home centers, electronics retailers, etc.). As indicated by the arrows in FIG. 1, the store system S (some or all of the devices in the store system S) and the headquarters system H (some or all of the devices in the headquarters system H) can communicate with each other, for example, via the Internet. Although not shown in FIG. 1, a store system S exists for each store.

[0009] (Store System S) The store system S is a system on the store side. The store system S includes a registration and settlement device 20, a registration device 21, a settlement device 22, a transaction status management device 23 (not shown), and a store controller 24 (not shown). The devices within the store system S can communicate with each other via a LAN (which may be wired or wireless).

[0010] The registration and settlement device 20 executes a registration process for registering products and a settlement process for settling the price of the products registered by the registration process. The registration and settlement device 20 may be a device that registers products based on the operation of a store clerk and settles the payment based on the operation of the store clerk. The registration and settlement device 20 may be a device that registers products based on the operation of a customer and settles the payment based on the operation of the customer (a full-self-service device). The registration and settlement device 20 may be a device that registers products based on the operation of a store clerk and settles the payment based on the operation of the customer (a face-to-face semi-self-service device). The registration and settlement device 20 may be a device that has multiple operating modes (full-self-service mode, face-to-face semi-self-service mode). The registration and settlement device 20 can acquire customer identification information from a medium (such as a membership card) brought by the customer.

[0011] The registration device 21 registers products based on the operation of a store clerk. The settlement device 22 settles the payment based on the operation of a customer. The registration device 21 transmits product registration information to the settlement device 22 (directly or via the store controller 24). The settlement device 22 receives the registration information transmitted by the registration device 21 and settles the payment. In other words, the registration device 21 and the settlement device 22 constitute a semi-self-service system. The registration device 21 and the settlement device 22 can acquire customer identification information from a medium brought by the customer.

[0012] The transaction status management device 23 (e.g., a personal computer) is used by a store clerk to manage the devices installed in the store (monitor and control the processing status, operation status, etc.). The store controller 24 (e.g., a server) sends and receives various information.

[0013] The store system S may include a mobile terminal 30 (not shown) that registers products based on customer operations in the product sales area, and a checkout device 23 (not shown) that settles the purchase of the products registered by the mobile terminal 30. The mobile terminal 30 may be a smartphone owned by the customer or a smartphone provided by the store. The mobile terminal 30 may be integrated with a shopping cart. Like the checkout device 22, the checkout device 23 settles the purchase based on customer operations. The checkout device 23 can acquire customer identification information from a medium brought by the customer. If the mobile terminal 30 is a customer's smartphone, the customer can be identified by using the mobile terminal 30, and the checkout device 23 can acquire the customer identification information of the customer. For example, when a user starts shopping using a dedicated registration app on the mobile terminal 30, the customer identification information (e.g., the customer identification information associated with the mobile terminal 30 when the dedicated app is downloaded) is transmitted to the transaction server 13, and then transmitted from the transaction server 13 to the checkout device 23 at the time of settlement. In addition, in the case of a web-based system, when accessing the transaction server 13, customer identification information (for example, customer identification information generated in advance when registering as a member and stored as a cookie) is sent to the transaction server 13, and at the time of settlement, it is sent from the transaction server 13 to the settlement device 23. Therefore, if the mobile terminal 30 is a customer's smartphone, the settlement device 23 does not need to obtain customer identification information from a medium brought by the customer.

[0014] (Headquarters System H) The headquarters system H is a system on the headquarters side. The headquarters system H includes a planning management server 10, a headquarters terminal 11, an analysis and extraction server 12, a trading server 13, a product management server 14, and a customer management server 15. The devices within the headquarters system H can communicate with each other via a LAN (which may be wired or wireless). The dashed lines in FIG. 1 indicate the sales promotion plan management system 1. In other words, the headquarters system H includes the sales promotion plan management system 1. The sales promotion plan management system 1 is a system that manages sales promotion plans that can be implemented repeatedly over multiple implementation periods. The sales promotion plan management system 1 includes the planning management server 10, a headquarters terminal 11, and an analysis and extraction server 12.

[0015] (Trade Server 13) The transaction server 13 manages transactions. Specifically, the transaction server 13 stores a transaction file. The transaction file is a file that stores (saves) transaction information. The transaction information includes, as data items, for example, transaction identification information, transaction date and time, store identification information, product registration information, settlement information, and customer identification information. In the transaction information, the transaction identification information is a key item.

[0016] The transaction server 13 receives transaction information from the registered settlement device 20 or the settlement device 22 (or receives transaction information from the store controller 24) and stores it in a transaction file. In other words, after completing the transaction (after completing the settlement process), the registered settlement device 20 or the settlement device 22 sends the transaction information to the transaction server 13 (directly or via the store controller 24), and the transaction server 13, having received the transaction information, stores the received transaction information in a transaction file. Note that if the registered settlement device 20 or the settlement device 22 has not acquired customer identification information, it sends transaction information that does not include customer identification information to the transaction server 13.

[0017] (Product Management Server 14) The product management server 14 manages products. Specifically, the product management server 14 stores a product master (product file). The product master is a file that stores product information. The product information includes, as data items, product identification information (e.g., JAN code), product name, and price. In the product information, the product identification information is a key item. In response to an inquiry including product identification information from another device (a device in the store system S, another device in the headquarters system H), the product management server 14 may refer to the product master and respond with the price and product name (PLU).

[0018] (Customer management server 15) The customer management server 15 manages customers (customers (members) who have registered as members). Specifically, the customer management server 15 stores a customer master (customer file). The customer master is a file that stores customer information. The customer information includes, as data items, for example, customer identification information, registered name (name, etc.), date of birth, gender, contact information (email address, telephone number, etc.), store identification information of the registered store (main store), and registration date. In the customer information, the customer identification information is a key item. In response to an inquiry including customer identification information from another device (a device within the store system S, another device in the headquarters system H), the customer management server 15 may refer to the customer master and respond with the registered name, etc.

[0019] The customer management server 15 manages customer points (benefits). Specifically, the customer management server 15 stores a point file. The point file is a file that stores point information. The point information includes, as data items, for example, customer identification information and the current number of points (the number of points available). In the point information, the customer identification information is a key item. The customer management server 15 updates the number of points stored in the point file. For example, the customer management server 15 accesses the transaction server 13 (referring to the transaction file) and, for each customer, adds the number of points granted (the number of points according to the purchase amount, for example, 1 point for every 200 yen) to the current number of points and subtracts the number of points used (paid) from the current number of points. The customer management server 15 may obtain and store transaction information (specifically, transaction information including customer identification information) from the transaction server 13 (or may update the number of points by referring to the transaction information stored by the customer management server 15 itself). In response to an inquiry including customer identification information from another device (a device in the store system S, another device in the headquarters system H), the customer management server 15 may refer to the point file and respond with the current number of points.

[0020] (Planning and Management Server 10) The project management server 10 manages sales promotion projects. Specifically, the project management server 10 stores a sales promotion project master (sales promotion project file). The sales promotion project master is a file that stores basic sales promotion project information. The basic sales promotion project information includes, as data items, for example, a project code (sales promotion project identification information), a project name, store identification information of the target store for the sales promotion, an implementation period, an announcement period, and an end flag. In the basic sales promotion project information, the project code is a key item. The basic sales promotion project information is set based on the operation of a store clerk on the basic setting screen GM10 (Figure 3). In other words, the project management server 10 stores basic sales promotion project information that is set based on the operation of a store clerk.

[0021] In addition, promotional plans are basically implemented repeatedly over multiple implementation periods, but if the end flag is set (for example, "1" is stored), the plan will not be implemented, including announcements.

[0022] The project management server 10 manages promotion target customers (target customers of promotion projects). Specifically, the project management server 10 stores a promotion target customer file. The promotion target customer file is a file that stores promotion target customer information. The promotion target customer information includes, as data items, for example, a project code, the number of times the project has been implemented (the number of times it has been implemented) or the implementation period, and the promotion target customer (customer identification information of the promotion target customer). In the promotion target customer information, the project code and the number of times the project has been implemented (or the implementation period) are key items.

[0023] The initial value of the number of times the promotion is performed is 1, and is incremented by 1 each time the promotion is repeated. Promotion target customers are extracted (determined, selected) based on the customer extraction conditions set by the sales clerk's operation on the promotion target customer setting screen GM20 (Fig. 4) (or the customer extraction conditions changed based on the customer extraction condition change information set by the sales clerk's operation on the change setting screen GM50 (Fig. 7)). The analysis and extraction server 12 extracts promotion target customers based on the customer extraction conditions.

[0024] The project management server 10 manages customer extraction conditions. Specifically, the project management server 10 stores a customer extraction condition file. The customer extraction condition file is a file that stores customer extraction condition information. The customer extraction condition information includes, as data items, for example, a project code, an implementation number (or implementation period), and customer extraction conditions (information indicating the customer extraction conditions). In the customer extraction condition information, the project code and the implementation number (or implementation period) are key items.

[0025] The customer extraction conditions (information indicating the customer extraction conditions) are set based on the operation of the sales clerk on the sales promotion target customer setting screen GM20 (FIG. 4). That is, the planning management server 10 stores the customer extraction conditions set based on the operation of the sales clerk.

[0026] Furthermore, the customer extraction conditions are changed based on customer extraction condition change information set by the store clerk on the change setting screen GM50 (FIG. 7). The planning management server 10 changes the customer extraction conditions based on the customer extraction condition change information.

[0027] In relation to the above, the planning management server 10 stores a customer extraction condition change file. The customer extraction condition change file is a file that stores customer extraction condition change information. The customer extraction condition change information includes, as data items, for example, a plan code, an evaluation result (for example, information indicating one of evaluations A to D), and customer extraction condition change details (information indicating the change details of the customer extraction conditions). In the customer extraction condition change information, the plan code and evaluation result are key items. The change details of the customer extraction conditions are set based on the operation of the store clerk on the change setting screen GM50 (FIG. 7). In other words, the planning management server 10 stores the customer extraction condition change details that are set based on the operation of the store clerk.

[0028] In relation to the above, the planning management server 10 stores an evaluation file. The evaluation file is a file that stores evaluation information. The evaluation information includes, as data items, for example, a planning code, an evaluation period (evaluation range), and evaluation criteria (information indicating the evaluation criteria). In the evaluation information, the planning code is a key item. The evaluation period and evaluation criteria are set based on the operation of a store clerk on the evaluation setting screen GM40 (Figure 6). In other words, the planning management server 10 stores the evaluation period and evaluation criteria that are set based on the operation of a store clerk.

[0029] The project management server 10 manages promotional products (products targeted by a promotional project). Specifically, the project management server 10 stores a promotional product file. The promotional product file is a file that stores promotional product information. The promotional product information includes, as data items, for example, a project code, the number of times the promotion has been implemented (or the implementation period), and the promotional product (product identification information of the promotional product). In the promotional product information, the project code and the number of times the promotion has been implemented (or the implementation period) are key items.

[0030] The promotion target products are extracted based on the product extraction conditions set by the sales clerk on the promotion target product / benefit setting screen GM30 (FIG. 5) (or the product extraction conditions changed based on the product extraction condition change information set by the sales clerk on the change setting screen GM50 (FIG. 7)). The analysis and extraction server 12 extracts the promotion target products based on the product extraction conditions.

[0031] The project management server 10 manages product extraction conditions. Specifically, the project management server 10 stores a product extraction condition file. The product extraction condition file is a file that stores product extraction condition information. The product extraction condition information includes, as data items, for example, a project code, an implementation number (or implementation period), and product extraction conditions (information indicating the product extraction conditions). In the product extraction condition information, the project code and the implementation number (or implementation period) are key items.

[0032] The product extraction conditions (information indicating the product extraction conditions) are set based on the operation of the sales clerk on the sales promotion target product / benefit setting screen GM30 (FIG. 5). That is, the planning management server 10 stores the product extraction conditions set based on the operation of the sales clerk.

[0033] The product extraction conditions are changed based on extraction condition change information set by a store clerk on the change setting screen GM50 (FIG. 7). The planning management server 10 changes the product extraction conditions based on the extraction condition change information.

[0034] In relation to the above, the planning management server 10 stores a product extraction condition change file. The product extraction condition change file is a file that stores product extraction condition change information. The product extraction condition change information includes, as data items, for example, a planning code, evaluation results, and product extraction condition change details (information indicating the change details of the product extraction conditions). In the product extraction condition change information, the planning code and evaluation results are key items. The product extraction condition change details are set based on the operation of a store clerk on the change setting screen GM50 (Figure 7). In other words, the planning management server 10 stores the product extraction condition change details that are set based on the operation of a store clerk.

[0035] The project management server 10 manages the benefits of sales promotion projects (benefits given to customers targeted by the sales promotion). Specifically, the project management server 10 stores a benefit file. The benefit file is a file that stores benefit information. The benefit information includes, as data items, for example, a project code, the number of times the project is implemented (or the implementation period), and benefits (information indicating the content of the benefit). In the benefit information, the project code and the number of times the project is implemented (or the implementation period) are key items.

[0036] The benefits (information indicating the content of the benefits) are set based on the operation of the sales clerk on the sales promotion product / benefit setting screen GM30 (FIG. 5). That is, the planning management server 10 stores the benefits that are set based on the operation of the sales clerk.

[0037] The benefit is changed based on benefit change information set by the store clerk through the change setting screen GM50 (FIG. 7). The project management server 10 changes the benefit based on the benefit change information.

[0038] In relation to the above, the plan management server 10 stores a benefit change file. The benefit change file is a file that stores benefit change information. The benefit change information includes, for example, a plan code, an evaluation result, and benefit change details (information indicating the change details of the benefit) as data items. In the benefit change information, the plan code and evaluation result are key items. The benefit change details are set based on the operation of the store clerk on the change setting screen GM50 (Figure 7). In other words, the plan management server 10 stores the benefit change details that are set based on the operation of the store clerk.

[0039] The project management server 10 also manages the continuation / termination (cancellation) of sales promotion projects. Specifically, the project management server 10 stores a termination determination file. The termination determination file is a file that stores termination determination information. The termination determination information includes, as data items, for example, a project code, an evaluation result, and a continuation / termination determination content (information indicating continuation or termination). In the termination determination information, the project code and evaluation result are key items. The continuation / termination determination content is set based on the operation of a store clerk on the change setting screen GM50 (Figure 7). In other words, the project management server 10 stores the continuation / termination determination content that is set based on the operation of a store clerk.

[0040] The planning and management server 10 stores screen information for the various screens described above (basic setting screen GM10, sales promotion target customer setting screen GM20, sales promotion target product / benefit setting screen GM30, evaluation setting screen GM40, and change setting screen GM50) and transmits the screen information to the headquarters terminal 11. In other words, the headquarters terminal 11 accesses the planning and management server 10 and displays the various screens described above.

[0041] Alternatively, the headquarters terminal 11 may store and display screen information for the various screens described above (basic setting screen GM10, promotion target customer setting screen GM20, promotion target product / benefit setting screen GM30, evaluation setting screen GM40, change setting screen GM50).

[0042] (Headquarters Terminal 11) The main terminal 11 is used by a store clerk. The main terminal 11 is, for example, a personal computer. The main terminal 11 may be provided with a mouse, a keyboard, etc. as operation devices. The display unit of the main terminal 11 may be a touch display.

[0043] The headquarters terminal 11, for example, accesses the planning and management server 10 and displays the various screens described above (basic setting screen GM10 in FIG. 3, sales promotion target customer setting screen GM20 in FIG. 4, sales promotion target product / benefit setting screen GM30 in FIG. 5, evaluation setting screen GM40 in FIG. 6, and change setting screen GM50 in FIG. 7). The headquarters terminal 11 may also access various servers (planning and management server 10, product management server 14, customer management server 15, etc.) and display various information stored in each server (information stored in the various files described above).

[0044] (Analysis and Extraction Server 12) The analysis and extraction server 12 analyzes or aggregates product sales records (sales trends) and customer purchase records (purchase trends). As an example, the analysis and extraction server 12 can execute the following (1) to (10) by referring to the transaction file stored in the transaction server 13, the product master stored in the product management server 14, the customer master stored in the customer management server 15, etc.

[0045] (1) Classification of customers based on the purchase amount during a specified period. For example, classification into excellent, medium, and poor ranks in descending order of the purchase amount during a specified period. The proportion of people in each of the excellent, medium, and poor ranks can be specified arbitrarily. The ranks are not limited to three levels. (2) Classification of customers based on the number of purchases (number of visits) during a specified period. For example, classification into excellent, medium, and poor ranks based on the number of purchases during a specified period. The proportion of people in each of the excellent, medium, and poor ranks can be specified arbitrarily. Ranks are not limited to three levels. (3) Customer classification based on the last purchase date (visit date). For example, classify customers into excellent, medium, and poor ranks in order of the most recent last purchase date. The proportion of people in each of the excellent, medium, and poor ranks can be specified arbitrarily. Ranks are not limited to three levels. (4) Cross-analysis: For example, analyzing customers based on two of the above (1), (2), and (3).

[0046] (5) Purchase history by product per customer for a specified period (sales history for each product per customer). For example, the analysis and extraction server 12 generates a product ranking by purchase quantity for a specified customer (or individual customer). The analysis and extraction server 12 also extracts the top N products by purchase quantity for a specified customer (or individual customer). The analysis and extraction server 12 also generates a product ranking by purchase amount for a specified customer (or individual customer). The analysis and extraction server 12 also extracts the top N products by purchase amount for a specified customer (or individual customer). (6) Purchase history by product for a customer group (for example, multiple customers belonging to one or more segments out of multiple segments classified by cross-analysis) for a predetermined period. (5) above is aggregated for multiple customers belonging to the customer group. For example, the analysis and extraction server 12 generates a product ranking for one customer group based on the number of items purchased or the purchase amount. The analysis and extraction server 12 also extracts the top N products based on the number of items purchased or the purchase amount for one customer group.

[0047] (7) Simultaneous purchase probability of each product per customer (probability of co-selling each product with other products for each customer). This is analyzed based on the purchase history (co-selling history) of multiple customers, including the customer, regardless of whether the customer actually purchased the product. For example, the analysis and extraction server 12 generates a product ranking based on the simultaneous purchase probability for a specified customer (or individual customers). The analysis and extraction server 12 also extracts the top N products with the highest simultaneous purchase probability for the specified customer (or individual customers). (8) Probability of simultaneous purchases by product in a customer group. This is the sum of (7) above for multiple customers belonging to the customer group. For example, the analysis and extraction server 12 generates a product ranking based on the simultaneous purchase probability for one customer group. Also, for example, the analysis and extraction server 12 extracts the top N products with the highest simultaneous purchase probability for one customer group.

[0048] (9) Relevance rate for each product per customer (probability of purchase for each product by other customers with attributes similar to that of the customer). The more purchases there are from other customers with similar attributes, the higher the relevance rate. This may be calculated using an algorithm such as probabilistic latent semantic analysis (PLSA). For example, the analysis and extraction server 12 generates a product ranking based on relevance rate for a specified customer (or individual customers). The analysis and extraction server 12 also extracts the top N products with the highest relevance rate for a specified customer (or individual customers). (10) Relevance rate for each product in a customer group. (9) above is aggregated for multiple customers belonging to the customer group. For example, the analysis and extraction server 12 generates a product ranking based on relevance rate for a customer group. The analysis and extraction server 12 also extracts the top N products in terms of relevance rate for a customer group.

[0049] The analysis and extraction server 12 extracts promotion target customers for each promotion plan based on the customer extraction conditions of each promotion plan. That is, the analysis and extraction server 12 references the customer extraction condition file (a file that stores the customer extraction conditions for each promotion plan) stored in the plan management server 10 to extract promotion target customers for each promotion plan. For example, for a promotion plan with plan code "XX", the analysis and extraction server 12 extracts promotion target customers based on the customer extraction condition information (customer extraction conditions) for plan code "XX" stored in the customer extraction condition file. The extraction results (promotion target customers) by the analysis and extraction server 12 are stored in the promotion target customer file of the plan management server 10.

[0050] The customer extraction conditions are conditions related to the cross-analysis described above (see FIG. 4), and the analysis and extraction server 12 extracts, as promotion target customers, multiple customers who belong to one or more of the multiple segments classified by the cross-analysis.

[0051] The analysis and extraction server 12 also extracts promotional products for each promotional plan based on the product extraction conditions for that plan. That is, the analysis and extraction server 12 references the product extraction condition file (a file that stores the product extraction conditions for each promotional plan) stored in the plan management server 10 to extract promotional products for each promotional plan. For example, for a promotional plan with plan code "XX," the analysis and extraction server 12 extracts promotional products based on the product extraction condition information (product extraction conditions) for plan code "XX" stored in the product extraction condition file. The extraction results (promotion target customers) by the analysis and extraction server 12 are stored in the promotional product file of the plan management server 10.

[0052] The product extraction conditions are conditions related to the purchase history, simultaneous purchase probability, and matching rate described above (FIG. 5). Therefore, the analysis and extraction server 12 extracts, for example, products with the highest purchase quantity, simultaneous purchase probability, or matching rate for promotion target customers as promotion target products.

[0053] Fig. 2 is an explanatory diagram illustrating the functions of the sales promotion plan management system 1. As shown by the dashed lines in Fig. 2, the sales promotion plan management system 1 includes a display unit 100, a setting unit 101, an extraction unit 102, an evaluation unit 103, a change unit 104, and a plan information storage unit 109.

[0054] 2, some functions (such as the implementation unit and communication unit) of the sales promotion plan management system 1 are omitted from the illustration. The implementation unit manages the schedule of the sales promotion plan, including the announcement, by referring to period information such as the announcement period and the implementation period. The communication unit (the communication unit of each device) sends and receives information.

[0055] The transaction information storage unit 105 is a function of the transaction server 13. In other words, the storage unit of the transaction server 13 is the transaction information storage unit 105. The transaction information storage unit 105 stores transaction files, etc. The product information storage unit 106 is a function of the product management server 14. In other words, the storage unit of the product management server 14 is the product information storage unit 106. The product information storage unit 106 stores product masters, etc. The customer information storage unit 107 is a function of the customer management server 15. In other words, the storage unit of the customer management server 15 is the customer information storage unit 107. The customer information storage unit 107 stores customer masters, etc.

[0056] The project information storage unit 109 is a function of the project management server 10. In other words, the storage unit of the project management server 10 is the project information storage unit 109. The project information storage unit 109 stores a sales promotion project master, a sales promotion target customer file, a customer extraction condition file, a customer extraction condition change file, an evaluation file, a sales promotion target product file, a product extraction condition file, a product extraction condition change file, a bonus file, a bonus change file, an end determination file, and the like.

[0057] The display unit 100 is a function of the headquarters terminal 11. In other words, the display unit of the headquarters terminal 11 is the display unit 100. The display unit 100 displays, for example, various screens (e.g., a basic setting screen GM10 in FIG. 3, a promotion target customer setting screen GM20 in FIG. 4, a promotion target product / benefit setting screen GM30 in FIG. 5, an evaluation setting screen GM40 in FIG. 6, and a change setting screen GM50 in FIG. 7). The display unit 100 may also display information stored in various files.

[0058] The setting unit 101 is a function of the project management server 10. In other words, the processing unit (CPU) of the project management server 10 realizes the setting unit 101. The setting unit 101 sets (stores) in the project information storage unit 109 the content input via various screens displayed on the display unit 100.

[0059] The extraction unit 102 is a function of the analysis and extraction server 12. In other words, the processing unit (CPU) of the analysis and extraction server 12 realizes the extraction unit 102. The extraction unit 102 refers to the transaction information storage unit 105, the product information storage unit 106, and the customer information storage unit 107, and analyzes or aggregates product sales records (sales trends) and customer purchasing records (purchasing trends).

[0060] The extraction unit 102 also extracts promotion target customers based on the customer extraction conditions. Specifically, the extraction unit 102 extracts promotion target customers based on the customer extraction conditions set by the setting unit 101 (or, if the changing unit 104 changes the customer extraction conditions, the changed customer extraction conditions).

[0061] The extraction unit 102 also extracts promotional products based on the product extraction conditions. Specifically, the extraction unit 102 extracts promotional products based on the product extraction conditions set by the setting unit 101 (or the changed product extraction conditions if the changing unit 104 changes the product extraction conditions).

[0062] The evaluation unit 103 is a function of the project management server 10. That is, the processing unit (CPU) of the project management server 10 realizes the evaluation unit 103. The evaluation unit 103 evaluates the sales project (for example, evaluation A to evaluation D) based on the evaluation information.

[0063] The change unit 104 is a function of the planning management server 10. In other words, the processing unit (CPU) of the planning management server 10 realizes the change unit 104. The change unit 104 changes the customer extraction conditions based on customer extraction condition change information. Specifically, the change unit 104 changes the customer extraction conditions based on the customer extraction condition change details corresponding to the evaluation results by the evaluation unit 103, among the customer extraction condition change details for each evaluation result set by the setting unit 101. The change unit 104 changes the product extraction conditions based on the product extraction condition change information. Specifically, the change unit 104 changes the product extraction conditions based on the product extraction condition change details corresponding to the evaluation results by the evaluation unit 103, among the product extraction condition change details for each evaluation result set by the setting unit 101. The change unit 104 changes the benefit based on the benefit change information. Specifically, the change unit 104 changes the benefit based on the benefit change details (the benefit change details corresponding to the evaluation results by the evaluation unit 103, among the benefit change details for each evaluation result set by the setting unit 101).

[0064] Furthermore, the change unit 104 determines whether to end (cancel) the sales promotion plan. Specifically, the change unit 104 determines whether to end the sales promotion plan based on the continuation / termination determination content corresponding to the evaluation result by the evaluation unit 103, among the continuation / termination determination content for each evaluation result set by the setting unit 101. Note that the part that determines whether to end (cancel) the sales promotion plan may be referred to as an end determination unit (cancellation determination unit).

[0065] (Example of display on display unit 100) 3 to 7 are examples of displays on the display unit 100 (headquarters terminal 11). FIG. 3 is an example of a basic setting screen GM10. FIG. 4 is an example of a promotion target customer setting screen GM20. FIG. 5 is an example of a promotion target product / benefit setting screen GM30. FIG. 6 is an example of an evaluation setting screen GM40. FIG. 7 is an example of a change setting screen GM50.

[0066] The clerk's input operations (setting operations) on the basic setting screen GM10 to the change setting screen GM50 are performed in advance (before the first day of the announcement period for the first implementation of a sales promotion plan that will be implemented repeatedly over multiple implementation periods in the future).

[0067] (Basic setting screen GM10) The headquarters terminal 11 displays a basic setting screen GM10 as shown in FIG. 3 based on a predetermined operation (operation of a sales promotion plan button on the menu screen) from, for example, a menu screen (not shown).

[0068] The basic setting screen GM10 is a screen that accepts input operations (setting operations) related to basic information of a sales promotion plan. The information input on the basic setting screen GM10 is set as sales promotion plan basic information by the setting unit 101 (stored as sales promotion plan basic information in the sales promotion plan master of the plan information storage unit 109).

[0069] 3 has a promotion name input area AR11, a promotion target store input area AR12, a promotion period input area AR13, a notice period input area AR14, a promotion period confirmation area AR15, and a notice period confirmation area AR16. In addition, the basic setting screen GM10 has a back button and a forward button.

[0070] The project name input area AR11 is an input area for the project code and project name. The project code is a key item within each file, so duplication is generally not permitted. The project code may be automatically generated (numbered or issued) when the basic setting screen GM10 is displayed.

[0071] The promotion target store input area AR12 is an input area for the promotion target store. The promotion target store input area AR12 has a store selection button BT101 arranged for selecting the promotion target store, and a promotion target store confirmation area AR102 for confirming the store selected as the promotion target store. When the store selection button BT101 is operated, the headquarters terminal 11 pops up a store selection small screen (not shown). The store selection small screen has buttons for selecting one or more stores (for example, check boxes for each store), a complete button, a cancel button, and the like arranged on it. When the complete button is operated with one or more stores selected on the store selection small screen, the headquarters terminal 11 closes the store selection small screen and displays the store names of the one or more stores selected on the store selection small screen in the promotion target store confirmation area AR102. In addition, if there are only a few stores, the store selection button BT101 may not be placed in the promotion target store input area AR12 (and the promotion target store confirmation area AR102 may not be provided), but buttons that allow the selection of one or more stores may be placed in the promotion target store input area AR12.

[0072] The implementation period input area AR13 is an input area for the implementation period (the implementation period of the sales promotion plan). The implementation period input area AR13 accepts input of the implementation start date (the start date of the sales promotion plan) and the number of implementation days (the number of days the sales promotion plan will be implemented) as the implementation period. The implementation start date is specified by a day of the week or a date. Therefore, first, input (selection using a radio button) of whether to specify a day of the week or a date is accepted. When specifying a day of the week, specification of "0" for "xxth day of the week" (selection using a pull-down button) and specification of "xxth day of the week" (selection using a pull-down button) are accepted. When specifying a date, specification of "xx day" (selection using a pull-down button) is accepted. For the number of implementation days, input of "0" for "xx days" is accepted.

[0073] Although it has been explained that a sales promotion plan can be repeatedly implemented over multiple implementation periods, specifically, a sales promotion plan can be repeatedly implemented every month according to the clerk's input (implementation start date, number of implementation days) in the implementation period input field AR13. For example, if a clerk specifies the start date as "the second Wednesday" by specifying the day of the week and inputs "3" days in the implementation period input field AR13, the implementation period will be three days starting from the second Wednesday of each month. Therefore, the implementation period confirmation field AR15 will display "Implementation period (confirmation) every month:" followed by "3 days starting from the second Wednesday of each month." For example, if a clerk specifies the start date as "the 15th" by specifying the date and inputs "3" days in the implementation period input field AR13, the implementation period will be three days starting from the 15th of each month. Therefore, the implementation period confirmation area AR15 displays "Implementation period (confirmation) every month:" followed by "3 days from the 15th" or "15th, 16th, 17th."

[0074] The announcement period input area AR14 is an input area for the announcement period (announcement period of the sales promotion plan), and accepts input of the announcement start date (announcement start date of the sales promotion plan) and the number of days of announcement (number of days of announcement of the sales promotion plan) as the announcement period. For the announcement start date, input of "〇" for "〇 days before the implementation start date" is accepted. For the number of days of announcement, input of "〇" for "〇 days" is accepted.

[0075] As an example, if the implementation period is entered as three days from the 15th (15th, 16th, 17th) in the implementation period input area AR13, and the notification start date is entered as "3" days before the implementation start date and the number of notification days is entered as "5" days in the notice period input area AR14, the notice period will be five days from the 12th every month. Therefore, the notice period confirmation area AR16 will display "Notice period (confirm) every month:" followed by "5 days from the 12th" or "12th, 13th, 14th, 15th, 16th."

[0076] The back button at the bottom of the basic setting screen GM10 is a button that is operated when returning to the previous screen (menu screen). The forward button is a button that is operated when the input operation on the basic setting screen GM10 is completed and the user proceeds to the next screen (sales promotion target customer setting screen GM20). The forward button may be made operable after the input operation on the basic setting screen GM10 is completed.

[0077] (Promotion target customer setting screen GM20) The headquarters terminal 11 displays a sales promotion target customer setting screen GM20 as shown in FIG. 4 based on the operation of the forward button on the basic setting screen GM10.

[0078] The promotion target customer setting screen GM20 is a screen that accepts input operations (setting operations) related to customer extraction conditions. The information input on the promotion target customer setting screen GM20 is set as customer extraction condition information by the setting unit 101 (stored as customer extraction condition information in a customer extraction condition file in the project information storage unit 109).

[0079] 4 includes a customer extraction condition input area AR21, an extraction unit input area AR22, and an extraction period input area AR23. The promotion target customer setting screen GM20 also includes a back button and a forward button.

[0080] The customer extraction condition input area AR21 is an input area for customer extraction conditions. Specifically, in the customer extraction condition input area AR21, parameters (horizontal axis, vertical axis, composition ratio) related to customer cross analysis are specified and customers to be targeted for sales promotion (selection of one or more segments from multiple segments classified by cross analysis) are selected.

[0081] The customer extraction condition input area AR21 is provided with a horizontal axis specification area AR201, a horizontal axis composition ratio input area AR202, a vertical axis specification area AR203, a vertical axis composition ratio input area AR204, and a segment selection area AR205.

[0082] The horizontal axis specification area AR201 is an area for specifying the horizontal axis (one side of the analysis axis) of the cross analysis. In the example of FIG. 4, the purchase amount is specified (selected using a pull-down button). The horizontal axis composition ratio input area AR202 is an area for inputting the composition ratio (proportion of the number of people) of each of the horizontal axes of the cross analysis. In the example of FIG. 4, "20"% is input as A rank (superior rank), "40"% as B rank (medium rank), and "40"% as C rank (poor rank). The vertical axis specification area AR203 is an area for specifying the vertical axis (the other side of the analysis axis) of the cross analysis. In the example of FIG. 4, the number of purchases is specified (selected using a pull-down button). The vertical axis composition ratio input area AR204 is an area for inputting the composition ratio (proportion of the number of people) of each of the vertical axes of the cross analysis. In the example of FIG. 4, "20"% is input as A rank (superior rank), "30"% as B rank (medium rank), and "50"% as C rank (poor rank).

[0083] The segment selection area AR205 is an area for selecting one or more segments from among a plurality of segments (Aa rank, Ab rank, Ac rank, Ba rank, Bb rank, Bc rank, Ca rank, Cb rank, and Cc rank) classified by cross analysis. The segment selection area AR205 has a plurality of buttons (Aa rank button, Ab rank button, Ac rank button, Ba rank button, Bb rank button, Bc rank button, Ca rank button, Cb rank button, and Cc rank button) corresponding to each segment. Each button corresponding to a segment switches between selected and unselected with each operation. In the example of FIG. 4, two segments (Bb rank and Cb rank) are selected.

[0084] In the example of Figure 4, the selected Bb rank customers are customers whose purchase amount is B rank and whose number of purchases is b rank (customers who belong to the top 40% between the top 20% and top 60% in order of purchase amount, and who belong to the top 30% between the top 20% and top 50% in order of purchase frequency). Cb rank customers are customers whose purchase amount is C rank and whose number of purchases is b rank (customers who belong to the bottom 40% in order of purchase amount, and who belong to the top 30% between the top 20% and top 50% in order of purchase frequency).

[0085] In other words, in the example of Figure 4, the customer extraction conditions entered are to extract customers who belong to the 80% other than the top 20% in terms of purchase amount, and who belong to the 30% between the top 20% and the above 50% in terms of purchase frequency (customers with Bb or Cb rank).

[0086] Therefore, in the example of Figure 4, the extraction unit 102 extracts, based on the above-mentioned customer extraction conditions, customers who belong to the 80% other than the top 20% in order of purchase amount and who belong to the 30% between the top 20% and the above 50% in order of purchase frequency as promotion target customers.

[0087] The extraction unit input area AR22 is an input area for the extraction unit (extraction method). Specifically, the extraction unit input area AR22 accepts input (selection using a radio button) of whether to use the extraction unit common to all promotion target stores or per promotion target store. The common promotion target store method is a method of performing a single cross-analysis overall based on the overall transaction information of multiple promotion target stores when multiple promotion target stores are entered (selected) on the basic setting screen GM10 (Figure 3). For example, if store X, store X, and store △ are promotion target stores, the cross-analysis is performed based on the overall transaction information combining the transaction information of store X, store X, and store △. The per promotion target store method is a method of performing an individual cross-analysis based on the individual transaction information of each promotion target store when multiple promotion target stores are entered (selected) on the basic setting screen GM10 (Figure 3). For example, if store X, store X, and store △ are the target stores for the sales promotion, a cross-analysis is performed based on the transaction information of store X, a cross-analysis is performed based on the transaction information of store X, and a cross-analysis is performed based on the transaction information of store △.

[0088] The extraction period input field AR23 is an input field for the extraction period (extraction range). The extraction period (extraction range) is the extraction period for transaction information (i.e., the range of transaction information for which cross analysis is performed). In the example of FIG. 4, the extraction period (extraction range) is the period from "60" days ago to the previous business day.

[0089] The back button at the bottom of the promotion target customer setting screen GM20 is a button that is operated when returning to the previous screen (basic setting screen GM10). The forward button is a button that is operated when completing the input operation on the promotion target customer setting screen GM20 and proceeding to the next screen (promotion target product / benefit setting screen GM30). The forward button may be operable after completing the input operation on the promotion target customer setting screen GM20.

[0090] (Promotional Products / Bonus Settings Screen GM30) The headquarters terminal 11 displays a promotion target product / benefit setting screen GM30 as shown in FIG. 5 based on the operation of the forward button on the promotion target customer setting screen GM20.

[0091] The promotional product / benefit setting screen GM30 is a screen that accepts input operations (setting operations) related to product extraction conditions and input operations (setting operations) related to benefits. Information related to the product extraction conditions input on the promotional product / benefit setting screen GM30 is set as product extraction condition information by the setting unit 101 (stored as product extraction condition information in the product extraction condition file of the project information storage unit 109). Information related to benefits input on the promotional product / benefit setting screen GM30 is set as benefit information by the setting unit 101 (stored as benefit information in the benefit file of the project information storage unit 109).

[0092] 5, a product extraction condition input area AR31 and a benefit input area AR32 are provided on the promotional product / benefit setting screen GM30. In addition, a back button and a forward button are provided on the promotional product / benefit setting screen GM30.

[0093] The product extraction condition input area AR31 is an input area for product extraction conditions. The product extraction condition input area AR31 is provided with a purchase history-based extraction product number specification area AR301, a simultaneous purchase probability-based extraction product number specification area AR302, and a relevance rate-based extraction product number specification area AR303. The product extraction condition input area AR31 also has an add product specification button BT304 and an exclude product specification button BT305.

[0094] The purchase history-based product number specification area AR301 is an area for inputting the number of products to be extracted (the number of products to be extracted based on purchase history) when extracting promotional products based on purchase history. Specifically, for purchase history, input of "0" is accepted for "up to the top 0 products."

[0095] When N items are entered in the purchase history-based extraction product number specification area AR301 (i.e., when N promotion target products are entered to be extracted based on purchase history), the extraction unit 102 extracts the top N products in terms of purchase quantity among promotion target customers (promotion target customers extracted based on the customer extraction conditions entered on the promotion target customer setting screen GM20 (Figure 4)) as promotion target products.

[0096] The simultaneous purchase probability-based product number selection field AR302 is an area for inputting the number of promotional products to be selected (the number of products to be selected based on the simultaneous purchase probability) when selecting products based on the simultaneous purchase probability. Specifically, the simultaneous purchase probability field accepts input of "0" for "up to the top 0 products."

[0097] When N items are entered in the simultaneous purchase probability based extraction product number specification area AR302 (i.e., when N promotion target products are entered to be extracted based on the simultaneous purchase probability), the extraction unit 102 extracts the N products with the highest simultaneous purchase probabilities as promotion target products among promotion target customers (promotion target customers extracted based on the customer extraction conditions entered on the promotion target customer setting screen GM20 (Figure 4)).

[0098] The area AR303 for specifying the number of products to be extracted based on the matching rate is an area for inputting the number of products to be extracted (the number of products to be extracted based on the matching rate). Specifically, for the matching rate, an input of "0" is accepted for "up to the top 0 products."

[0099] When N items are entered in the area AR303 for specifying the number of items to be extracted based on the matching rate (i.e., when N promotional items are to be extracted based on the matching rate), the extraction unit 102 extracts the top N items with the highest matching rate among promotional target customers (promotional target customers extracted based on the customer extraction conditions entered on the promotional target customer setting screen GM20 (Figure 4)) as promotional target products.

[0100] There is a limit to the total of the input values ​​in the purchase history-based extraction product number specification area AR301 (the number of promotional products to be extracted based on purchase history), the input values ​​in the simultaneous purchase probability-based extraction product number specification area AR302 (the number of promotional products to be extracted based on the simultaneous purchase probability), and the input values ​​in the relevance rate-based extraction product number specification area AR303 (the number of promotional products to be extracted based on the relevance rate). In this example, the total is limited to a maximum of 20.

[0101] The Specify Additional Product button BT304 is a button that is operated when specifying a product to be added to the promotion target products unconditionally (regardless of extraction based on purchase history, simultaneous purchase probability, or relevance rate). When the Specify Additional Product button BT304 is operated, the headquarters terminal 11 pops up an Additional Product Specification small screen (not shown). On the Additional Product Specification small screen, it is possible to specify one or more products per product unit. On the Additional Product Specification small screen, it may also be possible to specify one or more product classifications, one or more manufacturers, and one or more price ranges per product classification unit.

[0102] When a product to be added to the promotional products is specified, the specified product is excluded and products are extracted (extracted based on purchase history, simultaneous purchase probability, or matching rate), and then the specified product is added after extraction. Note that when a product to be added to the promotional products is specified, instead of the above, products may be extracted without excluding the specified product, and if the specified product is not extracted, the specified product may be added.

[0103] The Exclude Product Designation button BT305 is a button that is operated when designating products to be excluded from promotional products unconditionally (regardless of whether they are extracted based on purchase history, simultaneous purchase probability, or relevance rate). When the Exclude Product Designation button BT305 is operated, the headquarters terminal 11 pops up an Exclude Product Designation small screen (not shown). On the Exclude Product Designation small screen, it is possible to designate one or more products per product unit. On the Exclude Product Designation small screen, it may also be possible to designate one or more product classifications per product classification unit, one or more manufacturers, or one or more price ranges.

[0104] When a product to be excluded from the promotion target products is designated, the designated product is excluded from the extraction of products. Alternatively, when a product to be excluded from the promotion target products is designated, the product may be extracted without excluding the designated product, and when the designated product is extracted, the designated product may be excluded.

[0105] The reward input area AR32 is an area for inputting rewards. As shown in the figure, the reward input area AR32 accepts the specification of the reward type (selection using a pull-down button), input of the reward amount (value), specification of rounding (less than 1 yen) (selection using a pull-down button), input of whether or not there is a limit (selection using a radio button), and input of the limit details (transaction amount, number of times rewards are given) if there is a limit.

[0106] For example, if product A (usual price 270 yen) and product B (usual price 245 yen) are extracted as promotional products, the bonus type is "discount," the bonus amount is "5 (%)," and the rounding is "round down," then the discounted price for product A and product B for promotional customers during the promotional plan implementation period will be 256 yen and 232 yen, respectively. The discount is based on the price excluding tax (the price excluding tax is discounted and consumption tax is added to the discounted price). It is also possible to base the discount on the price including tax (the price including tax is discounted and the consumption tax is calculated).

[0107] Note that the example shown in the figure is a 5% discount on the promotional item, but other benefits are also possible, such as a discount of XX yen on the promotional item, a discount of XX yen on the subtotal, a discount of XX% on the subtotal, issuance of a coupon worth XX yen, or awarding XX points (or XX times the points).

[0108] It is also possible to set an upper limit for the amount of benefits such as discounts (including discounts using coupons) and discounts (including discounts using coupons or points). Specifically, the upper limit may be set based on the cost price (purchase price, etc.).

[0109] For example, if a promotional item has a promotion price below its cost price (or cost price + α) according to the set bonus amount, the bonus amount may be automatically adjusted (decreased) so that the promotional price of the promotional item becomes the cost price (or cost price + α). Alternatively, if a promotional item has a promotion price below its cost price (or cost price + α) according to the set bonus amount, instead of automatically adjusting the promotional price of the promotional item, a warning (alert) may be displayed and a hold screen may be displayed that accepts a store clerk's operation (whether to adjust the bonus amount), and the bonus amount may be adjusted based on the operation on the hold screen (or may not be adjusted; in other words, the promotional item may be allowed to have a promotion price below its cost price (or cost price + α)). Alternatively, if a promotional item has a promotion price below its cost price (or cost price + α) according to the set bonus amount, the promotional item may be automatically canceled (removed from the promotional items), or the hold screen described above may be displayed and the promotion may be canceled based on a store clerk's operation (or may not be canceled). The hold screen may not accept any operation and may prompt the user to operate the Exclude Product Designation button BT305. Also, for example, if there is a promotional product whose promotion price falls below the cost price (or cost price + α) according to the set bonus amount, the set bonus amount (or bonus type and bonus amount) may be automatically canceled (settings may be cleared), or the hold screen as described above may be displayed and the cancellation may be performed based on the operation of the store clerk (or it may not be canceled).

[0110] Furthermore, as a limit on the set bonus amount, an upper limit may be set based on a fixed value common to all products, instead of the cost price of each product. In other words, for example, it may be possible to set a discount of up to XX% and up to XX yen. The same applies to points, etc. For example, it may be possible to set a maximum of XX points or a maximum of XX times as a condition to be met simultaneously with other setting items.

[0111] The back button at the bottom of the promotional product / benefit setting screen GM30 is a button that is operated when returning to the previous screen (promotional target customer setting screen GM20). The forward button is a button that is operated when completing the input operation on the promotional product / benefit setting screen GM30 and proceeding to the next screen (evaluation setting screen GM40). The forward button may be operable after completing the input operation on the promotional product / benefit setting screen GM30.

[0112] (Evaluation setting screen GM40) The headquarters terminal 11 displays an evaluation setting screen GM40 as shown in FIG. 6 based on the operation of the forward button on the sales promotion target product / benefit setting screen GM30.

[0113] The evaluation setting screen GM40 is a screen that accepts input operations (setting operations) related to the evaluation of a sales promotion plan. The information input on the evaluation setting screen GM40 is set as evaluation information by the setting unit 101 (stored as evaluation information in an evaluation file in the plan information storage unit 109).

[0114] 6, an evaluation period input area AR41 and an evaluation criteria input area AR42 are provided on the evaluation setting screen GM40. In addition, a back button and a forward button are arranged on the evaluation setting screen GM40.

[0115] The evaluation period input field AR41 is an input field for the evaluation period (evaluation range). Specifically, the evaluation period input field AR41 accepts input (selection using a radio button) of whether to use the previous (current) period or all periods. If the previous period is input (selected), the most recent implementation period becomes the evaluation period (the most recent promotional plan becomes the evaluation range). If all periods are input, the entire implementation period from the first to the previous period becomes the evaluation period (the evaluation range is all promotional plans from the first to the previous period).

[0116] In the example shown in Figure 6, since the previous time has been entered (selected), the evaluation period for the second implementation of the sales promotion plan is the period during which the first implementation of the sales promotion plan is carried out, the evaluation period for the third implementation of the sales promotion plan is the period during which the second implementation of the sales promotion plan is carried out, and the evaluation period for the fourth implementation of the sales promotion plan is the period during which the third implementation of the sales promotion plan is carried out (same below).If all of the information is entered, the evaluation period for the second implementation of the sales promotion plan is the period during which the first implementation of the sales promotion plan is carried out, the evaluation period for the third implementation of the sales promotion plan is the period during which the first and second implementations of the sales promotion plan are carried out, and the evaluation period for the fourth implementation of the sales promotion plan is the period during which the first to third implementations of the sales promotion plan are carried out (same below).

[0117] The evaluation criteria input area AR42 is an input area for the evaluation criteria. Specifically, the evaluation period input area AR41 first accepts input (selection by radio button) of whether to specify the average purchase amount or the average number of purchases (average number of store visits).

[0118] If you specify the average purchase amount, input the average purchase amount for each rating (rating A to D) while referring to the reference value (average purchase amount). If you specify the average number of purchases, input the average number of purchases for each rating (rating A to D) while referring to the reference value (average number of purchases).

[0119] In the example shown in Figure 6, the average purchase amount is input (selected), and an A rating is 1,857 yen or more, a B rating is 1,570 yen or more but less than 1,857 yen, a C rating is 1,400 yen or more but less than 1,570 yen, and a D rating is less than 1,400 yen. Therefore, if the average purchase amount during the evaluation period is 1,857 yen or more, it is rated A; if it is 1,570 yen or more but less than 1,857 yen, it is rated B; if it is 1,400 yen or more but less than 1,570 yen, it is rated C; and if it is less than 1,400 yen, it is rated D. The same applies when an average number of purchases is input.

[0120] In Figure 6, as an example of settings, an A rating is more than 30% higher than the reference value of "1,428 yen", a B rating is more than 10% higher than the reference value of "1,428 yen", and a D rating is more than a slight decrease (28 yen decrease) from the reference value of "1,428 yen" (a C rating is between D and B ratings).

[0121] The average purchase amount and average number of purchases to be evaluated are the average number of purchases by customers targeted by the sales promotion. Similarly, the reference values ​​use figures for customers targeted by the sales promotion. The reference values ​​are the averages before the implementation of the sales promotion plan (for example, the last month or the month before). The average purchase amount and average number of purchases for all customers, including customers targeted by the sales promotion, including the reference values, may also be used as the evaluation targets.

[0122] The back button at the bottom of the evaluation setting screen GM40 is a button that is operated when returning to the previous screen (promotional product / benefit setting screen GM30). The forward button is a button that is operated when completing the input operation on the evaluation setting screen GM40 and proceeding to the next screen (change setting screen GM50). The forward button may be operable after completing the input operation on the evaluation setting screen GM40.

[0123] (Change setting screen GM50) The headquarters terminal 11 displays a change setting screen GM50 as shown in FIG. 7 based on the operation of the forward button on the evaluation setting screen GM40.

[0124] The change setting screen GM50 is a screen that accepts input operations (setting operations) related to the continuation / termination (cancellation) of a sales promotion plan, changes to customer extraction conditions, changes to product extraction conditions, and changes to benefits. Information related to the continuation / termination of a sales promotion plan that is input on the change setting screen GM50 is set as termination determination information by the setting unit 101 (stored as termination determination information in the termination determination file of the plan information storage unit 109). Information related to changes to customer extraction conditions that is input on the change setting screen GM50 is set as customer extraction condition change information by the setting unit 101 (stored as customer extraction condition change information in the customer extraction condition change file of the plan information storage unit 109). Information related to changes to product extraction conditions that is input on the change setting screen GM50 is set as product extraction condition change information by the setting unit 101 (stored as product extraction condition change information in the product extraction condition change file of the plan information storage unit 109). The information regarding the change of the privilege input on the change setting screen GM50 is set as privilege change information by the setting unit 101 (stored as privilege change information in the privilege change file of the plan information storage unit 109).

[0125] 7 has an A rating input area AR51, a B rating input area AR52, a C rating input area AR53, and a D rating input area AR54. In addition, a back button and a complete button are arranged on the change setting screen GM50.

[0126] The A rating input area AR51 is an input area corresponding to the judgment result "Rating A." The B rating input area AR52 is an input area corresponding to the judgment result "Rating B." The C rating input area AR53 is an input area corresponding to the judgment result "Rating C." The D rating input area AR54 is an input area corresponding to the judgment result "Rating D."

[0127] The A rating input area AR51 accepts inputs for specifying whether to continue or end the sales promotion plan (selection using radio buttons), changing (or maintaining) the customer extraction conditions, changing (or maintaining) the product extraction conditions, and changing (or maintaining) the product extraction conditions. The same applies to the B rating input area AR52, the C rating input area AR53, and the D rating input area AR54.

[0128] In the example shown in Figure 7, in the A evaluation input area AR51, "Continue" is specified for the continuation / termination of the sales promotion plan, "Maintain (no change)" is entered for the change of customer extraction conditions, "Maintain (no change)" is entered for the change of product extraction conditions, and "Maintain (no change)" is entered for the change of benefits.

[0129] When the setting button BT511 for changing the customer extraction conditions for an A-rated customer is operated, the headquarters terminal 11 pops up a small screen (not shown) for changing the customer extraction conditions. The small screen for changing the customer extraction conditions can accept whether or not to change the customer extraction conditions, and if so, the details of the changes. When the store clerk inputs no changes regarding whether or not to change the customer extraction conditions and operates the complete button on the small screen, the headquarters terminal 11 closes the small screen and displays "Maintain (No Changes)" in the display area AR512 for confirming the input details, as shown in the figure.

[0130] When the setting button BT513 for changing the product extraction conditions for an A rating is operated, the headquarters terminal 11 pops up a small screen (not shown) for changing product extraction conditions. The small screen for changing product extraction conditions can accept whether or not to change the product extraction conditions, and if so, the details of the changes. When the store clerk inputs no changes regarding whether or not to change the product extraction conditions and operates the complete button on the small screen, the headquarters terminal 11 closes the small screen and displays "Maintain (no changes)" in the display area AR514 for confirming the input details, as shown in the figure.

[0131] When the setting button BT515 for changing the A-rated benefit is operated, the headquarters terminal 11 pops up a small benefit change screen (not shown). The small benefit change screen can accept whether or not to change the benefit, and if so, the details of the changes (for example, the percentage increase / decrease in the benefit amount, restrictions, etc.). When the store clerk inputs no changes regarding whether or not to change the benefit and operates the complete button on the small screen, the headquarters terminal 11 closes the small screen and displays "Maintain (No Changes)" in the display area AR516 for confirming the input details, as shown in the figure.

[0132] In the example shown in Figure 7, in the B evaluation input area AR52, "Continue" is specified for the continuation / termination of the sales promotion plan, "Number of purchases: 3% increase for rank b, 3% decrease for rank c" is entered for the change of customer extraction conditions, "Maintain (no change)" is entered for the change of product extraction conditions, and "Maintain (no change)" is entered for the change of benefits.

[0133] When the setting button BT521 for changing the customer extraction conditions for a B rating is pressed, the headquarters terminal 11 pops up the small screen for changing the customer extraction conditions (not shown). If the salesperson inputs "Yes" for the question about whether or not to change the customer extraction conditions, inputs a 3% increase in the number of people with rank b in the number of purchases and a 3% decrease in the number of people with rank c as the change details, and then presses the "Complete" button on the small screen, the headquarters terminal 11 clears the small screen and displays "Number of purchases: rank b 3% increase, rank c 3% decrease" in the display area AR522 for confirming the input details, as shown in the figure. Note that "Number of purchases: rank b 3% increase, rank c 3% decrease" means that the number of purchases for rank b is increased by 3% and the number of purchases for rank c is decreased by 3%. In the example of FIG. 4, the rank b is 30% and the rank c is 50%, but this means that the rank b is changed to 33% and the rank c is changed to 47%. In the example of FIG. 4, customers in ranks Bb and Cb are extracted as promotion target customers, so the number of promotion target customers increases.

[0134] The change in product extraction conditions for a B rating is the same as the change in product extraction conditions for an A rating, so a description thereof will be omitted. The change in benefits for a B rating (and the same for a C rating) is the same as the change in benefits for an A rating, so a description thereof will be omitted.

[0135] In the example shown in Figure 7, in the C evaluation input area AR53, "Continue" is specified for the continuation / termination of the sales promotion plan, "Number of purchases: 5% increase for rank B, 5% decrease for rank C" is entered for the change of customer extraction conditions, "Purchase history: 2 more units" is entered for the change of product extraction conditions, and "Maintain (no change)" is entered for the change of benefits.

[0136] Changing the customer extraction conditions for a C rating is the same as changing the customer extraction conditions for a B rating, so an explanation will be omitted. Note that "Number of purchases: increase rank b by 5%, decrease rank c by 5%" means a change to increase the number of purchases for rank b by 5% and decrease the number of purchases for rank c by 5%. In the example of Figure 4, rank b is 30% and rank c is 50%, but this means changing rank b to 35% and rank c to 45%.

[0137] When the setting button BT533 for changing the product extraction conditions for C ratings is operated, the headquarters terminal 11 pops up the above-mentioned small product extraction condition change screen (not shown). When the store clerk inputs "Yes" as the question about whether or not to change the product extraction conditions, inputs an increase of two items in the purchase history as the change content, and operates the completion button on the small screen, the headquarters terminal 11 clears the small screen and displays "Purchase history: Increased by 2" in the display area AR534 for confirming the input content, as shown in the figure. Note that "Purchase history: Increased by 2" means a change to increase the number of promotion target products extracted based on the purchase history by two. For example, if "1" was input in the purchase history-based extraction product number designation area AR301 in FIG. 5, this change changes "1" to "3."

[0138] 7, in the D evaluation input area AR54, "end" is specified as the continuation / end of the sales promotion plan. When "end" is specified, the headquarters terminal 11 disables the operation of the setting button.

[0139] 7 shows an example in which the program is terminated without continuing if the evaluation is unfavorable (e.g., a D rating), but it may also be terminated if the evaluation is favorable (e.g., an A rating). In other words, the program may be terminated if the targeted effect is not achieved, or if the target is achieved.

[0140] 8 and 9 are flowcharts showing an example of the operation of the sales promotion plan management system 1. Specifically, the flowchart in FIG. 8(A) shows the operation of the sales promotion plan management system 1 when a certain sales plan is newly set up. The flowchart in FIG. 8(B) shows the operation of the sales promotion plan management system 1 before the start of the Nth (N is 1 or more) implementation of a certain sales plan. The flowchart in FIG. 9 shows the operation of the sales promotion plan management system 1 after the Nth (N is 1 or more) implementation of a certain sales plan but before the start of the N+1th implementation. In other words, the operation of the sales promotion plan management system 1 for a certain sales plan is performed in the order of the flowchart in FIG. 8(A) → the flowchart in FIG. 8(B) → the flowchart in FIG. 9 → the flowchart in FIG. 8(B) → the flowchart in FIG. 9. Thereafter, the operation of the sales promotion plan management system 1 for a certain sales plan is performed only once. Thereafter, the operation of the flowchart in FIG. 8(B) and the operation of the flowchart in FIG. 9 are repeated except when the continuation / end determination in the flowchart in FIG. 9 determines that the plan is to be ended.

[0141] (Flowchart of Figure 8(A)) Step S1: The setting unit 101 (plan management server 10) sets basic information for the sales promotion plan. Specifically, the setting unit 101 sets the sales promotion plan basic information based on the store clerk's operation on the basic setting screen GM10 (FIG. 3) (the sales promotion plan basic information is stored in the sales promotion plan master in the plan information storage unit 109). Then, the process proceeds to step S2.

[0142] Step S2: The setting unit 101 sets the customer extraction conditions. Specifically, the setting unit 101 sets the customer extraction condition information based on the operation of the sales clerk on the promotion target customer setting screen GM20 (FIG. 4) (the setting unit 101 stores the customer extraction condition information in the customer extraction condition file in the project information storage unit 109). Then, the process proceeds to step S3.

[0143] Step S3: The setting unit 101 sets product extraction conditions. Specifically, the setting unit 101 sets product extraction condition information based on the store clerk's operation on the promotion product / benefit setting screen GM30 (FIG. 5) (the product extraction condition information is stored in the product extraction condition file in the project information storage unit 109). Then, the process proceeds to step S4.

[0144] Step S4: The setting unit 101 sets a benefit. Specifically, the setting unit 101 sets benefit information based on the store clerk's operation on the sales promotion product / benefit setting screen GM30 (FIG. 5) (the benefit information is stored in a benefit file in the project information storage unit 109). Then, the process proceeds to step S5.

[0145] Step S5: The setting unit 101 sets the evaluation. Specifically, the setting unit 101 sets the evaluation information based on the operation of the store clerk on the evaluation setting screen GM40 (FIG. 6) (the evaluation information is stored in the evaluation file of the project information storage unit 109). Then, the process proceeds to step S6.

[0146] Step S6: The setting unit 101 sets the continuation / end of the sales promotion plan, the change of the customer extraction conditions, the change of the product extraction conditions, and the change of the benefit. Specifically, based on the store clerk's operation on the change setting screen GM50 (FIG. 7), the setting unit 101 sets end determination information (storing the end determination information in the end determination file of the plan information storage unit 109), sets customer extraction condition change information (storing the customer extraction condition change information in the customer extraction condition change file of the plan information storage unit 109), sets product extraction condition change information (storing the product extraction condition change information in the product extraction condition change file of the plan information storage unit 109), and sets benefit change information (storing the benefit change information in the benefit change file of the plan information storage unit 109). This flowchart then ends.

[0147] (Flowchart in Figure 8(B)) At the start of the flowchart of FIG. 8(B), it is assumed that the setting information of the sales promotion plan (various information set by the flowchart of FIG. 8(A)) is stored.

[0148] Step S11: The implementation unit (planning management server 10) controls the implementation of the promotional plan announcement. For example, the implementation unit references the setting information and, before the announcement period (for example, by the day before), transmits information necessary for announcing the promotional plan (for example, announcement period, promotional store, promotional product, special offer, etc.) to the promotional store (store controller 24) so ​​that the announcement information (promotion period, promotional store, promotional product, special offer, etc.) is printed on the receipts of the promotional target customers during the announcement period (the announcement period for the current implementation). Note that the information necessary for announcing the promotional plan may be transmitted to another server (for example, transaction server 13) and then transmitted from the other server to the promotional target store. Note that the transaction server 13 may store the information necessary for announcing the promotional plan, and the announcement information may be printed on the receipts of the promotional target customers through communication with the promotional store until the transaction is completed. Next, proceed to step S12.

[0149] Step S12: The implementation unit controls the implementation of the sales promotion plan. For example, the implementation unit refers to the setting information and transmits, via the transmission unit, information necessary for the implementation of the sales promotion plan (for example, the implementation period, the sales promotion target store, the sales promotion target customer, the sales promotion target product, the special offer, etc.) before the implementation period (for example, by the day before) so that the sales promotion plan (in the example of FIG. 5, a 5% discount on the sales price of the sales promotion target product to the sales promotion target customer) is implemented during the implementation period (the announcement period for the relevant implementation number). Note that the information necessary for the implementation of the sales promotion plan may be transmitted to another server (for example, the transaction server 13) and then transmitted from the other server to the sales promotion target store. Note that the transaction server 13 may store the information necessary for the implementation of the sales promotion plan and provide the special offer in response to an inquiry (PLU) from the sales promotion target store. Next, proceed to step S13.

[0150] Step S13: The implementation unit (or evaluation unit) collects transaction information for the evaluation period. For example, the implementation unit (or evaluation unit) refers to the setting information, and at a predetermined timing that takes into account the preparation time for the next implementation after the end of the implementation period, the implementation unit (or evaluation unit) acquires the transaction information for the evaluation period from the transaction server 13 via the transmission unit (plan management server 10) and stores it in the plan information storage unit 109. Then, this flowchart ends.

[0151] The preparation time for the next promotion is mainly the time required to extract the target customers and products for the next promotion (the time required for steps S29 and S30 in the flowchart in Figure 9). Because customer ranks fluctuate depending on daily purchasing behavior, the target customers for the promotion will always be extracted even if the customer extraction conditions are maintained. Furthermore, if there is a change in the extracted target customers for the promotion, the target products for the promotion may also change, so the target customers for the products will always be extracted even if the product extraction conditions are maintained (Figure 9).

[0152] (Flowchart in Figure 9) At the start of the flowchart in FIG. 9, it is assumed that the transaction information for the evaluation period has already been stored in the plan information storage unit 109 (that is, it is assumed that the transaction information has already been collected so that it can be evaluated).

[0153] Step S21: The evaluation unit 103 (project management server 10) evaluates the sales promotion project based on the transaction information for the evaluation period and the evaluation information stored in the evaluation file. For example, if the evaluation information (evaluation criteria) for the sales promotion project is the content shown in Figure 6 (evaluation A is 1,857 yen or more, rating B is 1,570 yen or more but less than 1,857 yen, rating C is 1,400 yen or more but less than 1,570 yen, and rating D is less than 1,400 yen), the evaluation unit 103 will assign an A rating if the average purchase amount obtained from the transaction information for the evaluation period is 1,857 yen or more, a B rating if it is 1,570 yen or more but less than 1,857 yen, a C rating if it is 1,400 yen or more but less than 1,570 yen, and a D rating if it is less than 1,400 yen. Next, the process proceeds to step S22.

[0154] Step S22: The change unit 104 (project management server 10) determines whether to continue the sales promotion project based on the evaluation result of step S21 and the termination determination information stored in the termination determination file. For example, if the termination determination information (continuation / termination determination content) for the sales promotion project is the content shown in FIG. 7 (ratings A to C: continue, rating D: terminate), the change unit 104 determines to continue the sales promotion project if the rating is A to C, and determines not to continue (terminate) the sales promotion project if the rating is D. If it is determined to continue the sales promotion project (step S22: YES), the process proceeds to step S23. If it is determined not to continue the sales promotion project (step S22: NO), the change unit 104 sets the sales promotion project to terminate (for example, sets the termination flag), and this flowchart ends.

[0155] Step S23: The change unit 104 determines whether to change the customer extraction conditions based on the evaluation result of step S21 and the customer extraction condition change information stored in the customer extraction condition change file. For example, if the customer extraction condition change information (customer extraction condition change content) for the sales promotion plan is the content shown in FIG. 7 (rating A: maintain, rating B: "number of purchases: rank b 3% increase, rank c 3% decrease," and rating C: "number of purchases: rank b 5% increase, rank c 5% decrease"), the change unit 104 determines not to change (maintain) the customer extraction conditions if the rating is A, and determines to change the customer extraction conditions if the rating is B or C. If it is determined that the customer extraction conditions should be changed (step S23: YES), the process proceeds to step S24. If it is determined that the customer extraction conditions should not be changed (step S23: NO), the process proceeds to step S25.

[0156] Step S24: The change unit 104 changes the customer extraction conditions based on the evaluation result of step S21 and the customer extraction condition change information stored in the customer extraction condition change file, and then the process proceeds to step S25.

[0157] Step S25: The change unit 104 determines whether to change the product extraction conditions based on the evaluation result of step S21 and the product extraction condition change information stored in the product extraction condition change file. For example, if the product extraction condition change information (product extraction condition change content) for the sales promotion plan is the content shown in FIG. 7 (rating A or B: maintain, rating C: "Purchase record: increase by 2"), the change unit 104 determines not to change (maintain) the product extraction conditions if the rating is A or B, and determines to change the product extraction conditions if the rating is C. If it is determined that the product extraction conditions should be changed (step S25: YES), the change unit 104 proceeds to step S26. If it is determined that the product extraction conditions should not be changed (step S25: NO), the change unit 104 proceeds to step S27.

[0158] Step S26: The change unit 104 changes the product extraction conditions based on the evaluation result of step S21 and the product extraction condition change information stored in the product extraction condition change file, and then the process proceeds to step S27.

[0159] Step S27: The change unit 104 determines whether to change the benefit based on the evaluation result of step S21 and the benefit change information stored in the benefit change file. For example, if the benefit change information (benefit change content) for the promotional plan is the content shown in FIG. 7 (ratings A to C are maintained), the change unit 104 determines not to change (maintain) the benefit regardless of whether the rating is A, B, or C. If it is determined that the benefit should be changed (step S27: YES), the process proceeds to step S28. If it is determined that the benefit should not be changed (step S27: NO), the process proceeds to step S29.

[0160] Step S28: The change unit 104 changes the privilege based on the evaluation result of step S21 and the privilege change information stored in the privilege change file. The changed privilege is set (stored in the privilege file) as the next privilege. Then, the process proceeds to step S29.

[0161] Step S29: The extraction unit 102 (analysis and extraction server 12) extracts promotion target customers based on the customer extraction conditions, etc. The extracted promotion target customers are set (stored in the promotion target customer file) as promotion target customers for the next promotion. Then, proceed to step S30.

[0162] As mentioned in the flowchart of Figure 8(B), customer ranks fluctuate depending on daily purchasing behavior, so even if the customer extraction conditions are maintained (proceeding from step S23 to step S25 and skipping step S24), promotion target customers will always be extracted.

[0163] Step S30: The extraction unit 102 (analysis and extraction server 12) extracts promotional products based on the product extraction conditions. The extracted promotional products are set (stored in the promotional product file) as promotional products for the next round. This flowchart then ends.

[0164] As mentioned in the flowchart of Figure 8(B), customer ranks fluctuate depending on daily purchasing behavior, so even if the customer extraction conditions are maintained (step S24 is skipped), promotion target customers will always be extracted, and if there is a change in the extracted promotion target customers, the promotion target products may also change, so product target customers will always be extracted even if the product extraction conditions are maintained (step S25 → step S27 is proceeded to, and step S26 is skipped).

[0165] The sales promotion plan management system 1 starts the flowchart of FIG. 8(B) after the flowchart of FIG. 9, except when it is determined in step S22 that the sales promotion plan will not be continued.

[0166] The above describes the embodiments, but according to the embodiments, it is possible to more appropriately implement a sales promotion plan (for example, to easily implement a more advanced sales promotion plan). For example, a sales promotion plan that has been narrowed down to a specific target in accordance with tactics can be repeatedly implemented while automatically adjusting the content (target customers for the sales promotion, products for the sales promotion, and benefits) according to the implementation results (post-implementation evaluation). Furthermore, in the embodiments, if a setting operation is performed before the first implementation, the content for the second and subsequent implementations is automatically adjusted (because the setting operation is performed only once at the beginning), which reduces the burden compared to repeatedly performing the setting operation each time.

[0167] (Variations, etc.) Although the embodiments have been described above, the device configuration, data configuration, processing flow, display and output modes, etc. can be appropriately changed as shown in the following (1) to (12). In addition, the following (1) to (12) can be appropriately combined with each other.

[0168] (1) In the above embodiment, the evaluation is in four stages (A to D) as shown in the evaluation setting screen GM40 of Fig. 6, but it may be in two stages, three stages, five stages or more. The number of evaluation stages may be input (specified) on the screen (for example, the evaluation setting screen GM40 of Fig. 6).

[0169] (2) In the above embodiment, the customer extraction conditions are described as conditions related to cross analysis (cross tabulation) (i.e., two-axis conditions), but they may also be conditions on one axis. For example, they may be conditions related to purchase amount (ABC analysis, decile analysis, etc.). As an example, customer extraction conditions may be set through on-screen operations to extract one or more groups (e.g., the middle three groups ranked fourth through sixth out of a total of 10 groups) as promotion target customers based on the results of decile analysis. One axis may be the number of purchases, the last purchase date, age, gender, etc. Note that since the customer extraction condition change information is information corresponding to the customer extraction conditions, if the customer extraction conditions are one-axis, the customer extraction condition change information will naturally also be information corresponding to the one axis. For example, the customer extraction condition change information (customer extraction condition change content) may change the middle three groups ranked fourth through sixth in the above-mentioned decile analysis to two or four groups. Furthermore, if the customer extraction conditions are one-axis ABC analysis, the customer extraction condition change information (customer extraction condition change content) may change the composition ratio.

[0170] Although the cross analysis in the above embodiment was based on two axes, it may be based on three or more axes (multiple cross tabulation). In other words, the customer extraction conditions may be based on three or more axes. For example, axes such as age and gender may be added. In the case of three or more axes, multiple two-dimensional analysis results may be displayed, and the setting operation for the customer extraction conditions may be accepted.

[0171] (3) In the above embodiment, an example was described in which notification information was printed on a receipt during a notification period to announce a sales promotion plan, but the manner in which a sales promotion plan is announced is not limited to this. For example, instead of or in addition to printing the notification information on a receipt, the announcement may be made on the display of the registration and settlement device 20 (registration device 21, settlement device 22, settlement device 23), or via the Internet (email, SNS, etc.). The announcement may also be made via a store clerk (for example, the information may be displayed on a store clerk's display and communicated verbally by the store clerk).

[0172] (4) In the above embodiment, an example was described in which a sales promotion plan is continuously implemented indefinitely unless it is stopped. However, the plan may be terminated when it reaches a predetermined number of implementations (or may be terminated by being stopped before it reaches the predetermined number of implementations). In other words, a sales promotion plan may be repeatedly implemented with an upper limit (limit number of times). The upper limit number of times may be input (specified) on a screen (for example, the basic setting screen GM10 in FIG. 3).

[0173] (5) In the above embodiment, an example was described in which the continuation / termination (cancellation) of a promotional plan was determined based on evaluation. However, the continuation / termination may be determined based on factors other than evaluation instead of or in addition to evaluation. For example, the promotional plan may be terminated when the benefits (discount amount, points awarded as benefits (including points added based on a multiplier)) reach their budget. In other words, the promotional plan may be terminated based on a cancellation condition other than evaluation (e.g., a cancellation condition related to the budget of the promotional plan) instead of or in addition to a cancellation condition related to the evaluation of the promotional plan. Cancellation conditions other than evaluation may also be input (specified) on a screen (e.g., the change setting screen GM50 in FIG. 7).

[0174] (6) In the above embodiment, an example was described in which promotional products were set (extracted) for all promotional target customers (customer group) (for example, an example in which a common promotional product was set for 1,000 promotional target customers), but promotional products may also be set for individual promotional target customers (that is, a promotional product may be set for each of the 1,000 promotional target customers). Note that even when promotional products are set for individual promotional target customers, the product extraction condition information and / or product extraction condition change information are common. Because the extracted promotional products must be managed for each customer, the promotional product information includes customer identification information as well as the project code and the number of times the promotion was implemented (or the implementation period).

[0175] (7) In the above embodiment, an example was described in which the target customers for the second and subsequent sales promotions are automatically adjusted if the setting operation is performed before the first implementation (an example in which the setting operation is performed only once at the beginning). However, the setting operation (operation of the evaluation setting screen GM40 or operation of the change setting screen GM50) may be performed each time before the second and subsequent implementations. In other words, the setting operation may be performed each time in advance so that it is ready for the next implementation. However, as mentioned above, the burden is less if the setting operation is performed only once at the beginning.

[0176] (8) In the above embodiment, it was explained that the headquarters terminal 11 (display unit 100) displays the basic setting screen GM10, the promotion target customer setting screen GM20, the promotion target product / benefit setting screen GM30, the evaluation setting screen GM40, and the change setting screen GM50. However, one screen may be divided into two or more screens, or one screen may be combined with one or more other screens to form a single screen (for example, a scrolling display, etc.).

[0177] (9) In the above embodiment, it was explained that the planning management server 10 (planning information storage unit 109) manages (stores) the sales promotion planning master, the sales promotion target customer file, the customer extraction condition file, the customer extraction condition change file, the evaluation file, the sales promotion target product file, the product extraction condition file, the product extraction condition change file, the bonus file, the bonus change file, and the termination determination file. However, one file may be divided into two or more files, or one file may be combined with one or more other files to form one file.

[0178] (10) In the above embodiment, the analysis and extraction server 12 is described as being included in the headquarters system H, but the location where the analysis and extraction server 12 is installed is not particularly limited. For example, the analysis and extraction server 12 may be a cloud server installed in an IDC or the like. The same applies to the planning and management server 10. The planning and management server 10 and the analysis and extraction server 12 may be installed in different locations. Furthermore, the headquarters terminal 11 may display the above-mentioned screen using a browsing function. The headquarters terminal 11 may also be a so-called thin client.

[0179] (11) In the above embodiment, the setting unit 101, evaluation unit 103, change unit 104, and project information storage unit 109 were described as functions of the same device (specifically, the project management server 10), but they may be distributed across two or more devices.

[0180] (12) In the above embodiment, an example was described in which the sales promotion planning management system 1 is configured with the planning management server 10, the headquarters terminal 11, and the analysis and extraction server 12, but these devices do not have to be separate. For example, the planning management server 10 and the headquarters terminal 11 may be a single device. Also, for example, the planning management server 10 and the analysis and extraction server 12 may be a single device. Also, for example, the planning management server 10, the headquarters terminal 11, and the analysis and extraction server 12 may be a single device.

[0181] <Summary of the embodiment> [Technical field] The present invention relates to a sales promotion planning management system. [Background technology] BACKGROUND ART A coupon issuing system is known that issues coupons taking into consideration the amount of profit (see, for example, Patent Document 1). [Prior art document] [Patent documents] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-235919 [Summary of the Invention] [Problem to be solved by the invention] However, there is room for improvement in the implementation of sales promotion plans (sales promotion plans) such as issuing coupons. The present invention has been made in consideration of such circumstances, and aims to provide a technology for more appropriately implementing sales promotion plans. [Means for solving the problem]

[0182] (1) One aspect for solving the above-mentioned problem is a sales promotion plan management system (e.g., sales promotion plan management system 1) that manages sales promotion plans that can be repeatedly implemented over multiple implementation periods, and includes a setting unit (e.g., setting unit 101) that sets extraction conditions (e.g., customer extraction conditions, product extraction conditions) for extracting promotion target customers and promotion target products in advance based on an operation (e.g., see the sales promotion target customer setting screen GM20 in FIG. 4 and the sales promotion target product / benefit setting screen GM30 in FIG. 5), an extraction unit (e.g., extraction unit 102) that extracts promotion target customers and promotion target products based on the extraction conditions, and a setting unit (e.g., setting unit 103) that sets extraction conditions (e.g., customer extraction conditions, product extraction conditions) for extracting promotion target customers and promotion target products in advance based on an operation (e.g., see the sales promotion target customer setting screen GM20 in FIG. 4 and the sales promotion target product / benefit setting screen GM30 in FIG. 5). This sales promotion plan management system is characterized by comprising a change unit (e.g., change unit 104) that changes the extraction conditions based on extraction condition change information (e.g., customer extraction condition change information, product extraction condition change information) for the second or subsequent sales promotion plan to be implemented, the setting unit sets the extraction condition change information in advance based on an operation (e.g., see change setting screen GM50 in Figure 7), and the extraction unit extracts promotion target customers and promotion target products based on the changed extraction conditions when the extraction conditions are changed by the change unit for the second or subsequent sales promotion plan to be implemented repeatedly. According to the configuration (1), it is possible to more suitably implement a sales promotion plan (for example, to simply implement a more sophisticated sales promotion plan).

[0183] (2) The sales promotion planning management system described in (1) is characterized in that the setting unit sets the extraction condition change information in advance based on an operation for each evaluation when a sales promotion planning is implemented (for example, see the change setting screen GM50 in Figure 7). According to the configuration (2), for example, a sales promotion plan can be repeatedly implemented while automatically adjusting the content (customers targeted for the sales promotion, products targeted for the sales promotion) according to the evaluation after the implementation.

[0184] (3) The sales promotion planning management system described in (2) is characterized in that the setting unit pre-sets, based on operation, as the extraction conditions for promotion target customers, the proportion of customers belonging to each rank of purchase amount ranks, which rank customers according to purchase amount, the proportion of customers belonging to each rank of purchase frequency ranks, which rank customers according to the number of purchases, and one or more segments out of multiple segments by purchase amount and purchase frequency identified from the purchase amount ranks and the purchase frequency ranks (see, for example, the sales promotion target customer setting screen GM20 in Figure 4), and the extraction unit extracts customers belonging to one or more segments set by the setting unit as promotion target customers, and the setting unit pre-sets, based on operation, at least one of the proportion of customers belonging to each rank of the purchase amount ranks and the proportion of customers belonging to each rank of the purchase frequency ranks as changes to the extraction conditions for promotion target customers (see, for example, the change setting screen GM50 in Figure 7). According to the configuration (3), for example, the target of a sales promotion plan (customers targeted for the sales promotion) can be appropriately set (narrowed down) in accordance with tactics, and the sales promotion plan can be repeatedly implemented while automatically adjusting the target based on the evaluation after implementation.

[0185] (4) The extraction unit extracts one or more products with a high matching rate or a high purchase probability for all customers extracted as promotion target customers as promotion target products, and the setting unit sets the number of products to be extracted as promotion target products by the extraction unit as the extraction condition for the promotion target products based on an operation (see, for example, the promotion target product / benefit setting screen GM30 in FIG. 5), and pre-sets, based on an operation, a change in the number of products to be extracted as promotion target products by the extraction unit as a change in the extraction condition for the promotion target products (see, for example, the change setting screen GM50 in FIG. 7). The sales promotion planning management system according to (2) is characterized in that: According to the configuration (4), for example, promotional products suitable for promotional target customers can be extracted, and promotional plans can be repeatedly implemented while automatically adjusting the promotional products according to the evaluations after the implementation.

[0186] (5) In the sales promotion plan management system described in (1) to (4), the setting unit sets in advance a termination condition (cancellation condition) for the sales promotion plan based on an operation. According to the configuration (5), the end conditions of the sales promotion plan can also be easily set.

[0187] (6) The promotion planning management system described in (1) to (4) is characterized in that the setting unit sets in advance the benefits to be granted to the promotion target customers extracted by the extraction unit based on an operation (for example, see the promotion target product / benefit setting screen GM30 in Figure 5). According to the configuration (6), the benefits to be given to customers who are the target of the sales promotion can be easily set.

[0188] (7) A sales promotion plan management system as described in (6), characterized in that the change unit changes the benefits for the second and subsequent sales promotion plans that are repeatedly implemented based on benefit change information, and the setting unit sets the benefit change information in advance based on an operation (for example, see the change setting screen GM50 in Figure 7). According to the configuration (7), the benefit change information can be easily set in advance, and the benefits to be granted in the second and subsequent sales promotion plans can be automatically adjusted in accordance with the setting.

[0189] (8) A sales promotion planning management system as described in (1) to (4), characterized in that it includes a notification unit that notifies the promotion target customers extracted by the extraction unit of at least the promotion period and the promotion target products (for example, by printing the notification information on a receipt, displaying it on a display unit, or notifying via the Internet). According to the configuration (8), the contents of the sales promotion plan can be communicated to the target customers of the sales promotion plan.

[0190] Note that programs for implementing the functions of each of the above-described devices (such as the planning and management server 10, headquarters terminal 11, analysis and extraction server 12, trading server 13, product management server 14, and customer management server 15) may be recorded on a computer-readable recording medium, and the programs may be loaded into a computer system and executed to perform processing on each of the above devices. Here, "loading a program recorded on a recording medium into a computer system and executing it" includes installing the program on a computer system. The term "computer system" here includes hardware such as an operating system and peripheral devices. The term "computer system" may also include multiple computer devices connected via a network, including the Internet, a WAN, a LAN, or a dedicated line. The term "computer-readable recording medium" refers to portable media such as floppy disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. The term "recording medium" also includes internal or external recording media accessible from a distribution server for distributing the program. The program code stored on the recording medium of the distribution server may be different from the program code in a format executable by the terminal device. In other words, the format in which the program is stored on the distribution server is not important as long as it can be downloaded from the distribution server and installed in a format executable by the terminal device. The program may be divided into multiple parts, each downloaded at a different time and then combined on the terminal device, or each part may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" also includes a storage medium that stores a program for a certain period of time, such as volatile memory (RAM) within a computer system that serves as a server or client when a program is transmitted over a network. The program may also be for implementing part of the functions described above.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0191] 1...Sales promotion planning management system, 10...Planning management server, 11...Headquarters terminal, 12...Analysis and extraction server, 13...Transaction server, 14...Product management server, 15...Customer management server, 100...Display unit, 101...Setting unit, 102...Extraction unit, 103...Evaluation unit, 104...Change unit, 105...Transaction information storage unit, 106...Product information storage unit, 107...Customer information storage unit, 109...Planning information storage unit

Claims

1. A sales promotion plan management system that manages sales promotion plans that can be repeatedly implemented over multiple implementation periods, a setting unit that sets extraction conditions for extracting promotion target customers and promotion target products in advance based on an operation; an extraction unit that extracts promotion target customers and promotion target products based on the extraction conditions; a change unit that changes the extraction conditions based on extraction condition change information for the second and subsequent sales promotion plans that are repeatedly implemented; Equipped with The setting unit The extraction condition change information is set in advance based on an operation; The extraction unit For the second or subsequent promotional plan that is repeatedly implemented, if the extraction conditions are changed by the change unit, the promotion target customers and promotion target products are extracted based on the changed extraction conditions. A sales promotion planning management system characterized by:

2. The setting unit As the extraction condition change information, the change content of the extraction condition is set in advance based on the operation for each evaluation when the sales promotion plan is implemented.

2. The sales promotion planning management system according to claim 1.

3. The setting unit The extraction conditions for target customers for the sales promotion are set in advance based on an operation, including the proportion of customers belonging to each rank of purchase amount ranks, which rank customers according to purchase amount; the proportion of customers belonging to each rank of purchase frequency ranks, which rank customers according to purchase frequency; and one or more segments from a plurality of segments by purchase amount and purchase frequency identified from the purchase amount ranks and the purchase frequency ranks; The extraction unit extracting customers who belong to one or more segments set by the setting unit as promotion target customers; The setting unit As a change in the extraction conditions for promotion target customers, at least one of the ratio of the number of customers belonging to each rank in the purchase amount ranking and the ratio of the number of customers belonging to each rank in the purchase frequency ranking is set in advance based on an operation.

3. The sales promotion planning management system according to claim 2.

4. The extraction unit extracting, as promotion target products, one or more products with a high matching rate or purchase probability from all customers extracted as promotion target customers; The setting unit setting, based on an operation, the number of products to be extracted as promotion target products by the extraction unit as the extraction condition for the promotion target products; As a change in the extraction conditions for the promotion target products, a change in the number of products to be extracted as promotion target products by the extraction unit is set in advance based on an operation.

3. The sales promotion planning management system according to claim 2.

5. The setting unit Pre-set the end conditions for a promotion based on operations 5. The sales promotion planning management system according to claim 1, wherein:

6. The setting unit A benefit to be given to the promotion target customers extracted by the extraction unit is set in advance based on an operation.

5. The sales promotion planning management system according to claim 1, wherein:

7. The change unit For the second or subsequent promotional plan that is repeatedly implemented, change the benefit based on benefit change information; The setting unit The benefit change information is set in advance based on an operation.

7. The sales promotion planning management system according to claim 6.

8. a notification unit that notifies at least the promotion period and the promotion target product to the promotion target customers extracted by the extraction unit; Equipped with 5. The sales promotion planning management system according to claim 1, wherein:

Images