JP5884541B2 - Program, method, and information processing apparatus - Google Patents

Description

  The present invention relates to processing of information relating to merchandise.

  In a store that sells a product, the product may be newly received and arranged at the store during business hours. For example, products with high freshness, such as fresh food, are the freshest immediately after arrival, so if they are sold to customers in a short period of time immediately after arrival, the customer can use the product in a state where the freshness has not dropped. It can be obtained.

  For example, the direct sales store business is a consignment sale of merchandise brought directly to a store by a product supplier such as a farmer such as a farmer without going through a normal distribution channel such as a wholesale market. This business provides sales services. This allows farmers to reduce distribution costs and consumers to purchase fresher produce. However, compared with general supermarkets and the like, production center direct sales stores often do not have sufficient cold storage facilities, so their freshness tends to deteriorate with the passage of time after the arrival of goods.

  On the other hand, in general supermarkets, even when products with high freshness such as fresh food are arranged on display shelves with cold storage and humidity control functions, the freshness gradually deteriorates with the passage of time after the arrival of products. To do.

  For example, bread and confectionery are products that favor freshness. In a store that manufactures and sells bread and confectionery, bread and confectionery are manufactured and product information such as when and which product is baked may be displayed to the customer.

  In a known sales promotion system, for each individual store, a sold-out product determined to be sold out during the day is set, and sales information of the sold-out product is created and input. The server of the sales promotion system refers to the individual database, automatically selects a plurality of specific individual consumers suitable for the sold-out product, and notifies the sales information of the sold-out product by e-mail or the like. Since the sales promotion system provides sales information targeted to carefully selected individual consumers, the sold-out products can be sold out efficiently. The sales promotion system further feeds back the correlation between the number of stocks or sales by category or the sales amount and attribute data, and the correlation between personal data and sales to sales and purchases, thereby increasing the sell-off rate. Can do.

JP 2005-258620 A

  Known sales promotion systems do not have a mechanism for minimizing the elapsed time from the arrival of goods to the sale.

  The inventors have recognized that if a customer is selected in a form that can shorten the elapsed time from the arrival of the product to the sale and the product information is notified to the customer, the product can be sold in a short elapsed time. Here, the merchandise information includes information on merchandise in a sales state at the store.

  An object of the embodiment is to realize processing for shortening the time from arrival of goods to sales.

According to one aspect of the embodiment, for each customer identification information, by referring to the storage device for storing record information relating to the elapsed time from the transmission of information about products to purchase of the product, the elapsed time for each customer identification information Destination information corresponding to the selected plurality of customer identification information, by selecting a plurality of customer identification information from the performance information according to the priority order that gives higher priority to the customer identification information having a shorter representative value program for executing a process of generating the notification information about including particular item to the information processing apparatus is provided with.

  According to one aspect of the embodiment, it is possible to realize a process for shortening the time from the arrival of goods to the sale.

FIG. 1 shows an example of a schematic configuration of a system including a server device, an inventory management terminal, a charge terminal, an information processing terminal, and a portable information terminal connected to a network according to the embodiment. FIG. 2 shows an example of a schematic configuration of the processor of the server device. 3A to 3G show examples of the data structure of each information record stored in the database. FIG. 4 shows an example of a flowchart of a schematic process for managing the arrival and sale of merchandise executed by the server device or the like according to the embodiment. FIG. 5 shows an example of a flowchart of a schematic process for transmitting a notification message related to commodity arrival executed by the server device to a selected customer according to the embodiment. 6A and 6B show an example of a specific flowchart of step 546 (selection of customer to be notified and notification of product information) in FIG. (Explained in Fig. 6A) FIG. 7 shows an example of a specific flowchart of step 548 (update notification result information) in FIG. FIG. 8 shows an example of a table of product arrival information. FIG. 9 shows an example of a table of product management information. FIG. 10 shows an example of a customer purchase history table. FIG. 11 shows an example of a table of past notification record information in this case. FIG. 12A shows an example of a table of processed past notification result information. FIG. 12B shows an example of a table of sorted past notification record information. 13A and 13B show examples of tables of expected purchase information for each product for each customer for different target sales times. FIG. 14 shows an example of a table of customer registration information used for notification. FIG. 15 shows an example of a table of product information notified to the target customer. FIG. 16 shows an example of a table of notification history information in which notification of product information is recorded. FIG. 17 shows another example of a specific flowchart of step 546 (selection of customer to be notified and notification of product information) in FIG. 18A to 18C show another example of a specific flowchart of step 548 (update notification result information) in FIG. (Explained in Fig. 18A) (Explained in Fig. 18A) 19A to 19D show examples of tables of expected purchase information for target sales times with different time intervals for a certain product. FIG. 20A shows an example of a table of processed past notification result information for a plurality of target sales times. FIG. 20B shows an example of a table of past notification result information sorted by target sales time, product code, and customer ID. FIG. 21 shows another example of the sorted past notification result information table. FIG. 22 shows an example of expected purchase information when the target sales time is the same day or the maximum business time.

The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not intended to limit the invention.

  Non-limiting embodiments of the present invention will be described with reference to the drawings. In the drawings, similar components and elements have the same reference numerals.

  The inventors recognize that if a customer is selected in a form that can shorten the elapsed time from the arrival of the product to the sale and the product information is notified to the customer, the product that is preferred to freshness can be sold with high freshness. did.

  The purpose of the embodiment is to realize a process for selecting a customer in a form that can shorten the elapsed time from the arrival of the product to the sale and notifying the selected customer of the arrival information of the product That is.

  1 is a schematic configuration of a system including a server device 10, an inventory management terminal 20, a charge terminal 30, information processing terminals 40 and 60, and a portable information terminal 64 connected to a network 5 according to an embodiment. ) Example. The system may further include an electronic mail server device 12. For example, the server device 10 may be disposed in a facility of a store operator or an external data center.

  1, the server apparatus 10 is an information processing apparatus, and may be a computer including a processor 102, a memory 104, an internal bus, a network interface (NW I / F) 108, and the like. The server device 10 further includes a storage device 16 such as a hard disk drive (HDD) including a drive 106 for reading a recording medium and a database 162 coupled to an internal bus. The drive 106 is provided for reading a recording medium 164 such as an optical disc in which software is recorded. The software may include, for example, an OS, a database management system (DBMS), an application program, and the like.

  The processor 102 may be a CPU (Central Processing Unit) for a computer. The memory 104 includes, for example, a main storage device and a semiconductor memory.

  The processor 102 may operate according to its software stored in the memory 104 and / or the storage device 16. The software may be stored in the recording medium 164, read from the recording medium 164 by the drive 106, and installed in the server device 10. Further, as an alternative, the processor 102 may be a dedicated processor that is implemented as an integrated circuit, for example, including at least a part of the software functions described above. The server apparatus 10 can be connected to the inventory management terminal 20, the charge terminal 30, the information processing terminals 40 and 60, and the portable information terminal 64 via the network interface 108 and further via an external or local network or line 5. . The server device 10 may be further connected to the electronic mail server device 12 via the network interface 108 via an external or local network or line 5.

  The inventory management terminal 20 may be, for example, a dedicated information processing terminal for inventory management or a general-purpose information processing apparatus (for example, a personal computer) in which inventory management software is installed. The label issuing machine 22 and the reader / writer (R / W) 24 is coupled. The inventory management terminal 20 manages product management information, and stores and manages information on delivery or arrival of each product and stock in the database 162. The inventory management terminal 20 is disposed in a store and can be operated by a product supplier such as a farmer or a user such as a store clerk.

  The reader / writer (R / W) 24 reads information such as the supplier ID (identification information) of the IC card of the merchandise supplier in accordance with the operation of the user under the control of the inventory management terminal 20, or to the IC card. Write information. The inventory management terminal 20 authenticates the supplier with information such as the supplier ID and password, and enables subsequent operations.

  The merchandise supplier or the store clerk inputs and determines the merchandise and price information such as the merchandise name, the price per unit weight, the unit number, the weight, the selling price, etc. on the inventory management terminal 20 and so on. Issue labels that contain product and price information. The label issuing machine 22 is under the control of the inventory management terminal 20 according to the operation of the supplier, the date and time of issue, the text (characters, symbols) representing the product and price information, and the one-dimensional code (barcode) or two-dimensional Print out a label containing code, etc. on paper. The label issuing machine 22 may include a weighing printer that weighs out a product and prints out a label including a character representing a price and a one-dimensional or two-dimensional code. The supplier attaches the label to the corresponding product, and arranges the product at the position of the product arrangement shelf designated by the store.

  When the label is issued, the inventory management terminal 20 records the date and time, the supplier ID, the product code (identification information) of the delivered product, the number of deliveries or the number of deliveries, etc. in the product arrival information of the database 162. To do. The product arrival information may be referred to as product delivery information from the viewpoint of the supplier. The server device 10 may update and manage the product management information of each product in the database 162 every time the product arrival information is stored or updated. The update and management of the product management information may be performed by the inventory management terminal 20 every time the product delivery information is recorded.

  The fee terminal 30 may be, for example, a cash register terminal (cash register machine terminal), a POS terminal, or the like, and a reader / writer (R / W) 34 may be combined therewith. The charge terminal 30 is arranged in a store and can be operated by a user such as a store clerk. The reader / writer 34 may include a function or device for scanning and reading product label information, and a function or device for writing and reading information on an IC card or electronic money.

  The charge terminal 30 stores product sales information such as the date and time, the product code of the sold product, and the number of products sold in the database 162. The merchandise sales information may be information relating to a receipt or a receipt including transaction details. The server device 10 may update and manage customer purchase history information and product management information of each product in the database 162 every time product management information is updated. The server device 10 may update and manage customer purchase history information and product management information for each product in the database 162 each time product sales information is recorded or updated. In addition, updating and management of the customer purchase history information and the merchandise inventory information may be performed by the fee terminal 30 every time merchandise sales information is recorded.

  The information processing terminal 40 may be an information processing apparatus such as a personal computer disposed in a store, and may be coupled with a reader / writer (R / W) 44. The reader / writer 44 may write and read an input amount and / or the number of points with respect to an IC card, a magnetic card, electronic money, or the like. The information processing terminal 40 may be operated by a user such as a store clerk, a supplier, or a customer. The information processing terminal 40 may read the balance amount and / or the number of points recorded in the database 162 or the IC card, magnetic card or electronic money and display them on the display.

  On the display of the information processing terminal 40, a user such as a store clerk, a product supplier, or a customer can view information including information on the store and information on actual and scheduled product arrival. A user such as a store clerk, a merchandise supplier, or a customer can operate the information processing terminal 40 to register and store customer registration information and supplier registration information regarding the customer and the supplier in the database 162.

  The information processing terminal 60 may be an information processing apparatus such as a personal computer, which is arranged in a customer's house or facility and has a browser application installed. A user such as a customer can browse a web page including information on a store, product information for the customer, and the like on the display by the browser of the information processing terminal 60. Here, the product information or the information on the product includes information on the product in a sales state in the store, and may further include information on the received product or information indicating that the product has arrived.

  The portable information terminal 64 may be, for example, a tablet terminal, a smartphone, another portable terminal, or a cellular phone in which a browser application and a mailer application are installed. The portable information terminal 64 may be connected to the network 5 via the mobile communication network 7 via the radio base station or the access point 72. For example, the portable information terminal 64 can receive an e-mail or a short message from the server device 10 or other mail server device 12 and display it on the display. For example, a user such as a customer can browse a web page including store information, product information, and the like on the display by the browser of the portable information terminal 64.

  FIG. 2 shows an example of a schematic configuration of the processor 102 of the server device 10.

  The processor 102 includes a control unit 1220, and further includes or includes a product management unit 1224, a target product selection unit 1226, a target customer selection unit 1228, a notification result update unit 1230, and other processing units 1240. May be. The processing unit 1240 may include an e-mail server function. The control unit 1220 may supply control signals to the product management unit 1224, the target product selection unit 1226, the target customer selection unit 1228, the notification result update unit 1230, and the processing unit 1240 to control the operation of these elements. Good.

  3A to 3G show examples of the data structure of each information record stored in the database 162. FIG. Each information in FIGS. 3A to 3G may take the form of a table.

  FIG. 3A shows an example of the data structure of a record of notification history information generated by the server device 10 and stored in the database 162. The notification history information includes, for example, fields of customer ID (identification information), transmission date, transmission time, and target product code. The customer ID may include a number or may be a unique number. The target product represents the product that is the target of the sales promotion or the target of notification of information related to the arrival of the product.

  FIG. 3B shows an example of the data structure of a record of customer purchase history information generated by the server device 10 or the like and stored in the database 162. The customer purchase history information includes, for example, fields of customer ID, purchase date, purchase time, purchased product code, and purchase quantity.

  FIG. 3C shows an example of the data structure of a record of notification result information generated by the server device 10 and stored in the database 162. The notification result information includes, for example, fields of customer ID, purchase date, reaction time, purchased product code, quantity purchased, purchase category, and target sales time. The purchase category indicates whether or not there is a purchase. The reaction time represents an elapsed time from when information about a product is transmitted to the customer until the customer purchases the product.

  FIG. 3D shows an example of the data structure of the record of expected purchase information of each product for each customer generated by the server device 10 and stored in the database 162. The expected purchase information of each product for each customer includes, for example, fields of customer ID, purchased product code, expected number, average reaction time, purchase rate (%), average number, and target sales time.

  The expected number represents an expected value of the number that the customer purchases the product for one notification or once per notification when the customer is notified of information related to the arrival of the product. The purchase rate represents the ratio of the number of times the customer has purchased the product to the number of notifications when the customer is notified of information related to the product. The average number represents the average value of the number of purchases per purchase of the customer when the customer purchases the product after notifying the customer of information related to the product.

  FIG. 3E shows an example of the data structure of a record of product management information generated by the server device 10 or the like and stored in the database 162. The merchandise management information includes, for example, fields for a merchandise code, the number of goods received, the number of sales, and the quantity of stock.

  FIG. 3F shows an example of the data structure of a record of commodity arrival information generated by the inventory management terminal 20 or the server device 10 and stored in the database 162. The merchandise arrival information includes, for example, fields of a merchandise code, a merchandise name, the number of arrivals, an arrival date, and an arrival time.

  FIG. 3G shows an example of the data structure of a record of customer registration information generated by the information processing terminal 40 or the server device 10 and stored in the database 162. The customer registration information includes, for example, customer ID, name, number of points, and notification destination fields. The notification destination may be an e-mail address or a telephone number that can be used as a short message destination.

  FIG. 4 shows an example of a flowchart of a schematic process (for sales management) for managing the arrival and sale of merchandise executed by the server device 10 or the like according to the embodiment.

8 to 10 show examples of tables used in the flowchart of FIG.
FIG. 8 shows an example of a table of product arrival information. FIG. 9 shows an example of a table of product management information. FIG. 10 shows an example of a table of customer purchase history information.

  Referring to FIG. 4, in step 502, the processor 102 (or its product management unit 1224) or the inventory management terminal 20 is generated or updated according to the operation of the inventory management terminal 20 by a user such as a store clerk or a product supplier. Based on the product arrival information of the received product, the arrival information such as the number of arrivals of each product on the day in the product management information is updated.

  For example, the arrival number 500 of the product name “daikon” of the product code “001001” in the product arrival information of FIG. 8 is added to the arrival number of 0 of the product code “001001” in the product management information of FIG. The number is 500. For example, the arrival number 1000 of the product name “tomato” of the product code “001002” in the product arrival information of FIG. 8 is added to the arrival number of 0 of the product code “001002” in the product management information of FIG. The number becomes 1000.

  In step 504, the processor 102 (product management unit 1224) generates customer purchase history information of each customer based on the product sales information generated or updated by the fee terminal 30 according to the operation of a user such as a store clerk. Or update.

  For example, in the customer purchase history information of FIG. 10, for the customer with the customer ID “M0001”, the purchase date “October 16, 2011”, the purchase time “13:40”, the purchase product code “001001” (radish), A record of 8 purchase quantities is stored. For example, in the customer purchase history information of FIG. 10, for the customer with the customer ID “M0002”, the purchase date “October 24, 2011”, the purchase time “13:50”, the purchase product code “001002” (tomato), And a record of 5 purchase quantities is stored.

  In step 506, the processor 102 (product management unit 1224) updates sales information such as the number of sales of each product on the current day in the product management information based on the customer purchase history information. For example, each sales quantity on the day of the product code “001001” (radish) in the customer purchase history information of FIG. 10 is sequentially added to the number of sales of the product code “001001” in the product management information of FIG. 200.

  In step 508, the processor 102 (product management unit 1224) subtracts the number of sales from the number of arrivals of each product on the current day based on the number of arrivals and sales of each product on the current day of the product management information, and product management information Update the number of items in stock, etc.

  For example, in the product management information of FIG. 9, the number of sales 200 is subtracted from the number of products 500 received with the product code “001001” (radish), and the number of stocks 300 is recorded. For example, in the merchandise management information in FIG. 9, the sales quantity of 700 is subtracted from the quantity of merchandise received with the merchandise code “001002” (tomato), and the inventory quantity of 300 is recorded.

  FIG. 5 shows an example of a flowchart of a schematic process (for transmitting product information) for transmitting a notification message about a product executed by the server device 10 to a selected customer according to the embodiment.

  FIG. 11 shows an example of a table of notification result information used in the flowchart of FIG.

  Referring to FIG. 5, in step 542, the processor 102 (or its target product selection unit 1226), for example, a product targeted for information notification regarding sales promotion or arrival according to an operation of the information processing terminal 40 by a user such as a store clerk Select or determine the product code for. The store clerk displays the number of arrivals, arrival time, number of stocks, etc. in the product arrival information of FIG. 8 and / or the product management information of FIG. 9 in the database 162 on the display of the information processing terminal 40 to examine sales. Alternatively, select a product for which notification of information regarding arrival is made. One or more target products may be selected.

  In step 544, the processor 102 (target product selection unit 1226) determines the target sales time of the selected sales promotion target product in accordance with an input operation of the information processing terminal 40 by a user such as a store clerk. For example, the store clerk sets the target sales time of the selected target product to, for example, a time between the current time and the business end time or one hour before that, for example, 2 hours. In step 544, the processor 102 (target product selection unit 1226) may further determine the target number of sales of the selected sales promotion target product according to an input operation of the information processing terminal 40 by a user such as a store clerk. Alternatively, the target number of sales may be determined by a user, such as a store clerk, or automatically at step 546 as well.

  In step 546, the processor 102 (or its target customer selection unit 1228) selects a target customer to be notified of information on a target product for promotion based on past notification result information or expected purchase information of each product for each customer. . The expected purchase information may be generated from the past notification result information for the set target sales time, or may be selected from a plurality of expected purchase information generated in advance. The expected purchase information can be generated with a small processing load if it is generated at that time with respect to the set target sales time. On the other hand, if the expected purchase information is selected from a plurality of expected purchase information generated in advance, the product information can be notified to the target customer in a short time. Next, the processor 102 (target customer selection unit 1228) generates a message for notifying the product information and transmits the message to the customer. The message may be, for example, an e-mail or a short message. For this purpose, for example, the target product is later determined based on the customer ID, purchase date, reaction time, purchase product code, purchase quantity and purchase category, and target sales time in the past notification result information of FIG. Customer IDs are sequentially extracted according to a certain priority order as described.

  The processor 102 (or its target customer selection unit 1228) may generate e-mail information including a message for notifying the product information and the customer e-mail address, and pass it to the e-mail server device 12 for transmission. . Alternatively, the processor 102 (or its target customer selector 1228) may send a short message containing the notification information to the phone number of the portable information terminal instead of the email.

  In step 548, the processor 102 (or the notification result update unit 1230) responds from the notification of the product information to the purchase of the customer based on the notification history information of the product information to the customer and the purchase history information of the customer. The time is calculated, the notification result information of the day is generated and stored in the database 162. The notification result information on that day includes, for example, the customer ID, purchase date (current day), reaction time, purchase product code, purchase quantity, and purchase category of each customer. The notification result information is used to generate next expected purchase information. Even if the expected purchase information used in step 546 after the next day is generated in advance for a plurality of possible target sales times in step 548, one target sales time is determined in step 546 after the next day. May be generated.

  6A and 6B show an example of a specific flowchart of step 546 (selection of customer to be notified and notification of product information) in FIG.

  FIGS. 11-16 show examples of tables used in the flowcharts of FIGS. 6A and 6B.

  FIG. 11 shows an example of a table of past notification record information in this case. 12A and 12B show examples of the notification result information. FIG. 12A shows an example of a table of processed past notification result information. FIG. 12B shows an example of a table of sorted past notification record information. 13A and 13B show examples of tables of expected purchase information for each product for each customer for different target sales times. FIG. 14 shows an example of a table of customer registration information used for notification. FIG. 15 shows an example of the product information of the received product notified to the target customer. FIG. 16 shows an example of a table of notification history information in which notification of product information is recorded.

  Referring to FIG. 6A, in step 604, the processor 102 (target customer selection unit 1228), from the database 162, notifies the past about the target product of the sales promotion or arrival product information notification selected in step 542 of FIG. 5. Extract performance information. For the notification performance information, a past period of a certain length before the previous day, such as one month, three months, six months, or twelve months, may be extracted.

  For example, in the past notification result information table of FIG. 11, information for six lines from the purchase product code “001001” (radish) of the target product is extracted. Information on other purchased product code lines that are not the target product is not extracted.

  In step 606, the processor 102 (target customer selection unit 1228) determines whether each reaction time is equal to or shorter than the target sales time as a threshold for each record of the notification result information. If it is determined that the reaction time is less than or equal to the target sales time, the procedure proceeds to step 608. If it is determined that the reaction time is not less than the target sales time, the procedure proceeds to step 610. If the target sales time is set to the longest business time, that is, the maximum length from the business start time to the end time, the reaction time is the target for all the records of notification result information whose purchase category is purchase. It may be determined that it is less than the sales time.

  For example, when the target sales time is 2 hours, the reaction time 40 minutes on the purchase date October 16, 2011 of the customer ID “M0001” in the notification result information table of FIG. 11 is within the target sales time. For example, when the target sales time is 2 hours, the reaction time 180 minutes on the purchase date October 16, 2011 of the customer ID “M0002” in the notification result information table of FIG. 11 is not within the target sales time. For example, in the notification result information table of FIG. 11, the reaction time of purchase date October 16, 2011 for customer ID “M0003” is blank, the purchase category is not purchased, and the reaction time is 2 as the target sales time. Not within hours.

  In step 608, the processor 102 (target customer selection unit 1228) sets the purchase quantity in the notification result information as the purchase quantity subjected to threshold processing at the target sale time for each record of the notification result information whose reaction time is within the target sale time. Set “Purchase” as the purchase category that has been thresholded at the target sales time. Therefore, a record of past notification results information is stored in the database 162 as it is as a record of notification results information subjected to threshold processing at the target sales time.

  For example, in the notification result information table of FIG. 12A, the notification result information of the purchase date October 16, 2011 for the customer ID “M0001” is copied and saved as the purchase quantity and the purchase classification, taking over those of FIG. It has been done. For example, in the notification result information table of FIG. 12A, the notification result information of the purchase date October 24, 2011 of the customer ID “M0001” is copied and saved as the purchase quantity and purchase classification, taking over those of FIG. It has been done.

  In step 610, the processor 102 (target customer selection unit 1228) sets 0 (zero) as the number of purchases subjected to threshold processing at the target sales time for each record of notification result information whose reaction time is longer than the target sales time, “Non-purchased” is set as the purchase category subjected to threshold processing at the target sales time. Therefore, a record of past notification results information in which the number of purchases is changed to 0 (zero) and the sales classification is changed to “not purchased” is stored in the database 162 as a record of notification results information that is threshold-processed at the target sales time. Is done. Thereby, in the case where the reaction time from the notification of the product information to the customer ID to the purchase of the product exceeds the target sales time, it is possible to generate performance information processed as having no purchase of the product. Thereby, it is possible to prevent the performance information whose reaction time exceeds the target sales time from being used for customer selection.

  For example, in the notification result information table of FIG. 12A, the row of the purchase date October 16, 2011 of the customer ID “M0002” includes the reaction time 180 minutes of the notification result information of FIG. The row of the purchase date of October 16, 2011 for the customer ID “M0002” is further set to 0 (zero) as the number of purchases and the purchase category changed from those in the notification result information of FIG. And includes "not purchased".

  In step 612, the processor 102 (target customer selection unit 1228) records each record of the notification result information thresholded at the target sales time, including the processed purchase quantity and purchase classification, for example, as in the table of FIG. 12A. Is generated and stored in the database 162. The table of FIG. 12A includes, for example, the past notification result information of the purchased product code “001001” of FIG. 11, and the purchase quantity and the purchase classification in the notification result information of the reaction time that is not within the target sales time of 2 hours are “0”, respectively. And “not purchased”.

  In step 614, the processor 102 (target customer selection unit 1228) determines whether or not all the records of the extracted past notification result information have been processed. If it is determined that all records have been processed, the procedure proceeds to step 616. If it is determined that all records have not yet been processed, the procedure returns to step 606.

  In step 616, the processor 102 (target customer selection unit 1228) sorts the records of the notification result information subjected to the threshold processing with the target sales time in the order of the customer ID. For example, the notification performance information in FIG. 12B is obtained by sorting the notification performance information in FIG. 12A in the order of customer ID numbers. In the table of FIG. 12B, the records of the notification result information are sorted in the order of customer IDs “M0001” to “M0003”.

  In step 618, the processor 102 (target customer selection unit 1228) sets the expected number of purchases, the average reaction time, the purchase rate, and the average number of purchases for each customer based on the notification result information as shown in FIG. 12B, for example. calculate. Next, the processor 102 (target customer selection unit 1228) includes the calculated expected number of purchases for each product and each customer, the average reaction time, the purchase rate, and the average number of purchases, for example, as shown in FIG. 13A. Expected purchase information for each product is generated and stored in the database 162.

  The expected number is an average value of the number of purchases of the product of the customer with respect to the number of times the product information is notified to the customer. The average reaction time is an average value of reaction times from notification of product information to purchase when a customer purchases a product. The purchase rate is an average value of the number of times the customer has purchased the product with respect to the number of times the customer is notified of certain product information. The average number of purchases is an average value of the number of purchases with respect to the number of purchases of the customer when the customer purchases the product after notifying the customer of certain product information.

  The table in FIG. 13A is based on the information records in the first to second rows in FIG. 12B, and the expected number of customers with the customer ID “M0001” of the purchased product code “001001” (radish) is 6.5, and the average response It includes 45 minutes of time, 100% purchase rate, and an average number of purchases per purchase of 6.5. In this case, the customer purchases the merchandise within 2 hours of the target sales time for all the records for each notification, and the purchase rate is 100%.

  The table in FIG. 13A is based on the information records in the 3rd to 4th rows in FIG. 12B, the expected number of customers with the customer ID “M0002” of the purchased product code “001001” (radish), and the average reaction time blank. , The purchase rate is 0%, and the average number of purchases per time is 0. In this case, since the customer has not purchased a product within 2 hours of the target sales time for all the records for each notification, the purchase rate is 0%.

  The table in FIG. 13A is based on the information records in the 5th to 6th rows in FIG. 12B, the expected number of customers with the customer ID “M0003” of the purchase product code “001001” (radish), the average reaction time 30 Minute, purchase rate 50%, and the average number of purchases per transaction is 6. In this case, for each notification, the customer purchases the product within 2 hours of the target sales time for one record and does not purchase the product within 2 hours of the target sales time for one record. The purchase rate is 50%.

  FIG. 13B shows a case where the target sales time is the same day or the maximum business time. In this case, for example, the record (1st to 6th lines) of the notification result information of the product code “001001” in the table of FIG. 11 is used as the notification result information subjected to threshold processing with the target sales time as it is. In this case, in FIG. 13B, based on the information records in the third to fourth rows in FIG. 12B, the expected number of customers with the customer ID “M0002” of the purchased product code “001001” (radish) is 1.5, average It includes a reaction time of 180 minutes, a purchase rate of 50%, and an average number of purchases per purchase of three. Since each customer purchases a product for one record and does not purchase a product for one record, the purchase rate is 50%.

  As an alternative form, in step 604, the past notification record information of all products is extracted regardless of the target product for sales promotion, and in step 606, the process of step 606 is executed for the past notification record information of all products. Also good. In this case, processed notification performance information for each notification regarding all products is generated in step 612, and expected purchase information regarding all products for each customer is generated in step 618.

  Referring to FIG. 6B, in step 620, the processor 102 (target customer selection unit 1228) determines, based on the expected purchase information as shown in FIG. 13A or 13 B, the target product of the day in the customer purchase history information as shown in FIG. Delete the record of the customer who purchased the product and exclude it from the customer to be notified. Accordingly, it is possible to prevent undesired information from being transmitted to a customer who has already purchased the target product on the day.

  In step 622, the processor 102 (target customer selection unit 1228) sets the target sales number of the target product according to the operation of the information processing terminal 40 by a user such as a store clerk, or automatically. Even if the target sales number is an input value of a user such as a store clerk or the current stock quantity of the target product in the table of FIG. It may be a quantity obtained by subtracting the predicted number of purchases from the current inventory quantity, or it may be the number of unsold sales on the current day. The target sales number may be set by a user such as a store clerk in step 544 of FIG.

  In step 624, the processor 102 (target customer selection unit 1228) sequentially selects customers to be notified in the expected purchase information according to a given priority. For this purpose, the processor 102 (target customer selection unit 1228) may sort the expected purchase information as shown in FIG. 13A or 13B in accordance with the priority order. The priority order may be a combination of a plurality of priority orders.

  The priority order is, for example, at least one of a rank with a short average reaction time, a rank with a large average number of purchases, and a rank with a high purchase rate for each customer ID within the target selling time. It may be based on one rank. Short average response times, high average purchases, and high purchase rates indicate high appetite for the target product or high likelihood of purchase behavior as a customer response. There will be. The processor 102 (target customer selection unit 1228) sorts the expected purchase information by the first priority among the plurality of priorities, and sets the customer IDs of the same rank within the same or allowable error range among the second priorities. And customer IDs of the same rank within the same or allowable error range may be sorted by the third priority.

  For example, the priority order may give a higher priority to a customer ID having a shorter average reaction time from notification of target product information for each customer ID to purchase. The priority is more than the average purchase quantity or expected quantity of the target product after the notification among two or more customer IDs of the same average reaction time within the same or tolerance (for example, ± 5 minutes) A higher priority may be given to the customer ID. The priority is further determined by the purchase rate among two or more customer IDs of the same average reaction time and / or average purchase quantity or expected quantity within the same or tolerance (eg, ± 5 minutes, ± 1 piece). May give higher priority to higher customer IDs. Alternatively, the priority may be further determined after the notification within two or more customer IDs of the same average reaction time and / or purchase rate within the same or tolerance (eg, ± 5 minutes, ± 2%). A higher priority may be given to a customer ID having a larger average purchase quantity or expected quantity of the target product. In this way, by giving different priorities to customer IDs having the same rank within the same or tolerance range in one or more priorities, there is a possibility that the target number of products can be sold in a shorter time. Will be higher.

  For example, the priority order may be such that among a plurality of customer IDs whose average reaction time is within the target sales time, a higher priority is given to a customer ID having a larger average purchase quantity or expected quantity of the target product. .

  The priority may be given, for example, to a customer ID having a higher purchase rate of the target product among a plurality of customer IDs whose average reaction time is within the target sales time.

  For example, in the table of FIG. 13A, customer IDs “M0003” and “M0001” are selected in this order in ascending order of average reaction time. For example, in the table of FIG. 13A, customer IDs “M0001” and “M0003” are selected in this order in descending order of purchase rate. For example, in the table of FIG. 13A, customer IDs “M0001” and “M0003” are selected in this order in descending order of the average purchase quantity.

  When notification result information for only the notification target product is extracted in step 604, the priority order is determined based on the average reaction time of only the specific notification target product, and purchase behavior based on the customer's product preference is expected. The tendency to be reflected in purchasing information will be high. On the other hand, when the notification result information of all the products is extracted in step 604, the priority order is determined based on the average reaction time of all the more notification target products, and the overall purchase behavior of the individual customer is determined. The tendency to be reflected in expected purchase information will be high.

  In step 626, the processor 102 (target customer selecting unit 1228) subtracts the predicted purchase number E of the target product purchased by the customer from the remaining sales target number G to obtain a new remaining sales target number (G = GE). The predicted purchase number E may be the expected number of purchases of the target product of the customer ID. As an alternative, the predicted purchase number E is, for example, the average number of purchases of the target product of the customer ID, or the purchase number “0” for the purchase category “Purchase” and the purchase number “0” for the purchase category “0”. May be an expected number obtained by weighted averaging with respective weights α and β. For example, the weights α = 2 and β = 1 may be used. In this case, the predicted purchase number E will be a value between the expected number and the average number.

  For example, by subtracting the expected number 6.5 of the customer ID “M0003” in FIG. 13A from the initial sales target number = 300 inventory numbers of the target product code “001001” (radish), a new remaining sales target number 293 is obtained. .5 are required. Thereafter, by subtracting the expected number 3 of the customer ID “M0003” in FIG. 13A from the remaining sales target number 293.5 of the target product code “001001”, a new remaining sales target number 292.5 is obtained.

  In step 628, the processor 102 (target customer selection unit 1228) determines whether or not the remaining sales target number is less than 0 (zero). If it is determined that the remaining sales target number is less than 0 (zero), ie, negative, the procedure proceeds to step 632. If it is determined that the remaining sales target number is 0 (zero) or more, the procedure proceeds to step 630. In this way, by sequentially selecting the target customers until the remaining sales target number G becomes negative, it is possible to more reliably achieve the sales of the products with the target sales number within the target sales time.

  In step 630, the processor 102 (target customer selection unit 1228) determines whether all customers have been selected. If it is determined that all customers have been selected, the procedure proceeds to step 632. If it is determined that not all customers have been selected, the procedure returns to step 624. Steps 628 and 630 are repeated until the remaining target sales number G is less than 0 (zero) or all customer records have been selected.

  In step 632, the processor 102 (target customer selection unit 1228) refers to the customer registration information as shown in FIG. 14, for example, and sends an e-mail or a short message to notify the selected notification target customer in order of target product information. Execute the process to send. For this purpose, the processor 102 (the target customer selection unit 1228 and the processing unit 1240) generates an e-mail or short message addressed to the customer including the product information and transmits it to the information processing terminal 60 or the portable information terminal 64 of the target customer. May be. As an alternative, the processor 102 (the notification information generation unit of the target customer selection unit 1228) sends the target customer's destination e-mail address and notification information about the product information to the e-mail server device 12 on the network 5. Also good. In this case, the e-mail server apparatus 12 transmits the notification information as an e-mail to the information processing terminal 60 or the portable information terminal 64 of the customer. The e-mail may be transmitted in order of priority of the expected purchase information in FIG. 13A or 13B.

  The e-mail may include product information such as the display content of FIG. In FIG. 15, the product information includes information such as customer ID, customer name, store name S, and target product name.

  In step 634, the processor 102 (target customer selection unit 1228) generates notification history information including the customer ID of the email transmitted to the target customer, the date and time of transmission, and the target product ID, and stores the notification history information in the database 162. For example, the notification history information in FIG. 16 includes a customer ID “M0001”, a transmission date “October 16, 2011”, a transmission time “13:00”, and a target product code “001001” (radish).

  In this way, a customer with a shorter average reaction time from notification of product information to purchase of the product can be selected as a notification target customer with higher priority. Accordingly, the time from the arrival of the product to the purchase can be shortened with a small processing load for notifying only the selected customer of the product information. Also, by limiting the customers to be notified by the customer reaction time and the total number of predicted purchases or expected numbers, the processing load for notifying product information is less than sending product information to all customers, and the product It is possible to suppress transmission of undesired information to a customer who is unlikely to purchase the product quickly. In addition, it is possible to reduce the occurrence of a situation in which a customer who has received notification of product information comes to the store to purchase and cannot be purchased because it is sold out, and the reliability of notification of product information can be increased.

  FIG. 7 shows an example of a specific flowchart of step 548 (update notification result information) in FIG. Step 548 in FIG. 5 or the flowchart in FIG. 7 in this case is from, for example, the business end time after step 546 in FIG. 5 to the business start time before steps 542 to 546 in FIG. It only has to be executed.

  Tables such as FIGS. 16, 10 and 11 are used in the flowchart of FIG.

  Referring to FIG. 7, in step 652, the processor 102 (notification result update unit 1230) extracts past notification history information as shown in FIG. 16 from the database 162, for example.

  In step 654, the processor 102 (notification result update unit 1230) extracts the customer purchase history information of all customers as shown in FIG.

  In step 656, the processor 102 (notification result update unit 1230) extracts from the customer purchase history information that there is a purchase record of the target product after notification in the past notification history information on the same day. The extracted date may be only a certain length of time in the past before the previous day, for example, one month, three months, six months, or twelve months.

  For example, in the customer purchase history information of FIG. 10, the customer ID “M0001”, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001” of the past notification history information of FIG. Corresponding customer ID, purchase date, and subsequent purchase time 13:40, a purchased product code is recorded. Therefore, the record of this customer purchase history information in FIG. 10 is extracted.

  For example, in the customer purchase history information of FIG. 10, the customer ID “M0002” of the past notification history information of FIG. 16, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001” The corresponding customer ID, purchase date, and subsequent purchase time of 16:00 are recorded with the purchased product code. Therefore, the record of this customer purchase history information in FIG. 10 is extracted.

  For example, in the customer purchase history information of FIG. 10, the customer ID “M0003” of the past notification history information of FIG. 16, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001”. The corresponding customer ID, purchase date, subsequent purchase time, and purchased product code are not recorded. Accordingly, the corresponding customer purchase history information does not exist and is not extracted.

  Steps 658 to 666 are executed for each record of the notification history information as shown in FIG.

  In step 658, the processor 102 (notification result update unit 1230) determines whether or not corresponding extracted customer purchase history information exists for each record of the notification history information. If it is determined that customer purchase history information exists, the procedure proceeds to step 660. If it is determined that the customer purchase history information does not exist, the procedure proceeds to step 662.

  In step 660, the processor 102 (notification result update unit 1230) sets “purchase” as the purchase category used for the notification result information for each customer and each product for the record of the notification history information. The processor 102 (notification result update unit 1230) further transmits an e-mail or a message in the notification history information from the purchase time in the purchase history information as a reaction time used for the notification result information for each customer and each product. Set the difference time after subtracting the time. Further, the processor 102 (notification record update unit 1230) sets the purchase quantity in the corresponding purchase history information as the purchase quantity used for the notification record information for each customer and each product.

  For example, the customer ID “M0001” in the past notification history information in FIG. 16, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001” in the customer purchase history information in FIG. Reference is made to the purchase time 13:40 and the purchase quantity 8 in the corresponding customer and purchase date information. As a result, “purchase”, reaction time 40 minutes, purchased product code “001001”, and 8 purchased items are set as the purchase category for the notification history information.

  For example, the customer ID “M0002” in the past notification history information in FIG. 16, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001” in the customer purchase history information in FIG. Reference is made to the purchase time 16:00 and the purchase quantity 3 in the corresponding customer and purchase date information. Accordingly, “purchase”, a reaction time of 180 minutes, a purchase product code “001001”, and a purchase quantity of 3 are set as the purchase category for the notification history information.

  In step 662, the processor 102 (notification result update unit 1230) sets “not purchased” as a purchase category used for the notification result information for each customer and each product for the record of the notification history information. The processor 102 (notification result update unit 1230) further sets a blank as the reaction time used for the notification result information for each customer and each product, and sets 0 (zero) as the number of purchases used for the notification result information. Set. As a result, in the case where there is no purchase of the product as a response to the notification of the product information with respect to the customer ID, it is possible to generate performance information indicating that the product has not been purchased.

  For example, the customer ID “M0003” in the past notification history information in FIG. 16, the transmission date October 16, 2011, the transmission time 13:00, and the target product code “001001” in the customer purchase history information in FIG. There is no corresponding customer and purchase date information. Accordingly, “not purchased”, blank reaction time, purchased product code “001001”, and 0 purchase quantity are set as the purchase category for the notification history information.

  In step 664, the processor 102 (notification result update unit 1230), for each record of the notification history information, includes the set purchase category, reaction time, and number of purchases, for example, as shown in the table of FIG. Each record of information is generated and stored in the database 162.

  For example, in the notification result information table of FIG. 11, customer ID “M0001”, purchase date October 16, 2011, reaction time 40 minutes, purchase product code “001001”, purchase quantity 8 pieces, purchase category “purchase”. A containing record is generated.

  For example, in the notification result information table of FIG. 11, customer ID “M0002”, purchase date October 16, 2011, reaction time 180 minutes, purchase product code “001001”, purchase quantity 3 pieces, purchase classification “purchase”. A containing record is generated.

  For example, in the notification result information table of FIG. 11, customer ID “M0003”, purchase date October 16, 2011, blank reaction time, purchase product code “001001”, purchase quantity 0, purchase category “not purchased”. A record containing is generated.

  In step 666, the processor 102 (notification result update unit 1230) determines whether all records of past customer purchase history information have been processed. If it is determined that all records have been processed, the procedure exits the routine of FIG. If it is determined that not all records have been processed yet, the procedure returns to step 658.

  However, the notification result information generates the notification result information for the current day based on the notification history information for the day and the customer purchase history information for the day, and further converts the notification result information to the past notification result information up to the previous day. It may be generated by merging or merging. Thereby, it is possible to reduce the processing load for generating the notification result information.

  In this way, for example, the notification result information table of FIG. 11 is generated. The notification result information of FIG. 11 is used in the subsequent day in step 546 of FIG. 5 or the flowcharts of FIGS. 6A and 6B.

  FIG. 17 shows another example of a specific flowchart of step 546 (selection of customer to be notified and notification of product information) in FIG.

  19A to 19D and 22 show examples of tables of expected purchase information of each product for each customer for a plurality of target sales times used in the flowchart of FIG. 19A to 19D show examples of tables of expected purchase information for target sales times with different intervals of 30 minutes for a certain product. However, the tables of expected purchase information for each customer similar to FIGS. 19A to 19D are also prepared for other products.

  14 and 15 are also used in the flowchart of FIG. In this case, expected purchase information for a plurality of target sales times is generated in advance, for example, in the form as shown in FIGS. 19A to 19D and 22 and stored in the database 162. Expected purchase information of each product for each customer for each target sales time may be generated in advance, for example, by nighttime batch processing on the previous day.

  Referring to FIG. 17, in step 602, the processor 102 (target customer selection unit 1228), for example, the expected purchase information of each product for each customer corresponding to the notification target product and the target sales time determined by a user such as a store clerk. Select.

  For example, the table of expected purchase information of each product for each customer in FIG. 19D corresponding to the notification target product code “001001” and the target sales time of 2 hours is selected from the tables of FIGS. 19A to 19D and 22. FIG. 19D corresponds to the table of expected purchase information of each product for each customer in FIG. 13A.

  Steps 620 to 634 in FIG. 17 are the same as those in FIG. 6B. Accordingly, in step 632, for example, referring to the customer registration information as shown in FIG. 14, an e-mail or a message for notifying the selected notification target customer of the product information of the target product in order is transmitted. In step 634, notification history information including the customer ID of the email transmitted to the target customer, the date and time of transmission, and the target product ID is generated and stored in the database 162.

  18A to 18C show another example of a specific flowchart of step 548 (update notification result information) in FIG. The flowcharts of FIGS. 18A to 18C are used in combination with the flowchart of FIG.

  20A, 20B, 21 and 22 show the tables used in the flowcharts of FIGS. 19A-19D and 11 are also used in the flowcharts of FIGS. 18A-18C.

FIG. 20A shows an example of a table of processed past notification performance information for a plurality of target sales times T _j . FIG. 20B shows an example of a table of past notification result information sorted by target sales time T _j , product code, and customer ID.

  Referring to FIG. 18A, steps 652 to 666 are similar to those of FIG.

Referring to FIG. 18B, in step 670 after step 666, processor 102 (notification result update unit 1230) sets a plurality of target sales times _Tj and maximum target sales time Te and stores them in memory 104 or the like. The target sales time T _j is, for example, 30 minutes, 30 minutes, 60 minutes,..., And 480 minutes, or 20 minutes, 20 minutes, 40 minutes,. . . , And 480 minutes, etc. The maximum target sales time Te may be, for example, 60 minutes, 120 minutes,..., Or 480 minutes within the length of the business hours of the day. Maximum target Sales time Te, the time interval between minimum target sales time T ₁ and a plurality of target sales time T _j, may be a value entered by the user by operating the information processing terminal 40 such as the clerk .

In step 672, the processor 102 (notification result update unit 1230) selects the smallest value among the plurality of target sales times T _j , for example, T ₁ = 30 minutes.

For each target sold selected time T _j, the step 606 to 614 is performed for and potential product code of every product. Steps 606-614 are similar to those of FIG. 6A.

In step 612, the processor 102 (notification result updating unit 1230) performs notification result information subjected to threshold processing at each target sales time T _j including the processed purchase quantity and purchase classification as shown in the table of FIG. 20A, for example. Are generated and stored in the database 162.

The table in FIG. 20A includes the past notification result information of the purchased product code “001001” in FIG. 11, and the purchase quantity and the purchase classification in the notification result information of the reaction time not within the target sales time T _j are 0 (zero), respectively. And “not purchased”. In this case, each target sales time T _j is 30 minutes, 60 minutes _,. . . , 120 minutes,. . . , And 480 minutes. The notification result information table as shown in FIG. 20A is generated for the product codes of all possible products.

  For example, in the first two lines of the notification result information in FIG. 20A, the information on the purchase date October 16, 2011 of the customer IDs “M0001” and “M0002” is the response time taken over in the notification result information in FIG. 40 minutes and 180 minutes, the changed purchase quantity “0” and the changed purchase category “not purchased” are included.

  For example, in the fifth line of the notification result information in FIG. 20A, the information on the purchase date October 24, 2011 of the customer ID “M0001” is changed by the inherited reaction time 50 minutes in the notification result information in FIG. The purchase quantity “0” and the changed purchase category “not purchased” are included.

  For example, in the twelfth line of the notification result information of FIG. 20A, the information on the purchase date October 16, 2011 of the customer ID “M0002” is changed by the inherited reaction time of 180 minutes in the notification result information of FIG. The purchase quantity “0” and the changed purchase category “not purchased” are included.

  If it is determined in step 614 that all records have been processed, the procedure proceeds to step 684.

In step 684, the processor 102 (notification result update unit 1230) selects the next smaller value T _j = T _{j + 1} among the plurality of target sales times T _j , for example, T _{j + 1} = 60 minutes.

In step 686, the processor 102 (notification result update unit 1230) determines whether or not the target sales time T _{j + 1} is greater than the maximum target sales time Te. If it is determined that the target sales time T _{j + 1} is not greater than or less than the maximum target sales time Te, the procedure returns to step 606. By repeatedly executing step 684, a plurality of target sales times T _j from the second shortest target sales time T ₂ to the maximum target sales time T _j = T _n (j = n) within the maximum target sales time Te. Are selected sequentially. If it is determined that the target sales time T _{j + 1} is greater than the maximum target sales time Te, the procedure proceeds to step 690 in FIG. 18C. This prevents notification result information from being generated for a target sales time T _{n + 1} that is greater than the maximum target sales time Te.

  However, the notification result information generates the notification result information for the current day based on the notification history information for the day and the customer purchase history information for the day, and further generates the processed notification result information for each sales target time. However, it may be generated by merging or integrating with the processed notification result information for each sales target time up to the previous day. Thereby, it is possible to reduce the processing load for generating the notification result information.

Referring to FIG. 18C, in step 690, processor 102 (notification result update unit 1230) sequentially sorts the processed notification result information as shown in the table of FIG. 20A with respect to target sales time T _j , product code, and customer ID. Then, notification result information like the table of FIG. 20B is generated.

  In step 692, the processor 102 (notification result update unit 1230), for each target sales time, for each customer, for example, based on the notification result information as shown in FIG. Calculate the rate and average number of purchases. Next, the processor 102 (target customer selection unit 1228) includes the expected number of purchases calculated for each product and each customer, the average reaction time, the purchase rate, and the average number of purchases, for example, as shown in FIGS. 19A to 19D. The expected purchase information of each product for each target sales time and each customer is generated and stored in the database 162.

  The table of FIG. 19A shows the expected number of customers with the customer ID “M0001” of the purchased product code “001001” (radish) based on the information records in the first and second rows of FIG. Includes 0, blank average reaction time, 0% purchase rate, and 0 average number of purchases per transaction. In this case, since the customer has not purchased the product within 30 minutes for all the records for each notification, the purchase rate is 0%.

  The table in FIG. 19A is based on the information records in the 3rd to 4th rows in FIG. 20B, the expected number of customers with the customer ID “M0002” of the purchased product code “001001” (radish), and the blank average response Includes time, purchase rate 0%, and average number of purchases per transaction. In this case, since the customer has not purchased the product within 30 minutes for all the records for each notification, the purchase rate is 0%.

  The table in FIG. 19A is based on the information records in the 5th to 6th rows in FIG. 20B, and the expected number of customers with the customer ID “M0003” of the purchase product code “001001” (radish) is 3 and the average reaction time 30 Minute, purchase rate 50%, and the average number of purchases per transaction is 6. In this case, the customer purchases a product within 30 minutes for one record and does not purchase a product within 30 minutes for one record, so the purchase rate is 50%.

  The table of FIG. 19B shows the expected number of customers with the customer ID “M0001” of the purchased product code “001001” (radish) based on the information records in the first and second rows of FIG. It includes 6.5 items, an average reaction time of 45 minutes, a purchase rate of 100%, and an average number of purchases per purchase of 6.5 items. In this case, the customer purchases the merchandise within one hour for all the records for each notification, and the purchase rate is 100%.

  The table in FIG. 19B includes the same information as FIG. 19A for the customers with the customer IDs “M0002” and “M0003” of the purchased product code “001001” (radish).

  The tables of FIGS. 19C and 19D include the same information as FIG. 19B for customers with customer IDs “M0001” to “M0003” of purchased product code “001001” (radish) for a target sales time of 90 minutes and 2 hours, respectively. It is out.

  FIG. 21 shows another example of the sorted past notification result information table.

  In step 694, the processor 102 (notification record update unit 1230) sorts the original notification record information as shown in the table of FIG. 11 for the product code and the customer ID without setting the target sales time. Notification result information as shown in the table below is generated.

  FIG. 22 shows an example of expected purchase information when the target sales time is the same day or the maximum business time.

  In step 696, the processor 102 (notification result update unit 1230) determines the expected number of purchases, the average reaction time, the purchase rate, and the average number of purchases based on the notification result information as shown in FIG. Is calculated. Next, the processor 102 (target customer selection unit 1228) includes the expected number of purchases calculated for each product and each customer, the average reaction time, the purchase rate, and the average number of purchases, for example, the same day as shown in FIG. Expected purchase information of each product for each customer is generated and stored in the database 162.

  For example, in the expected purchase information shown in FIG. 22, the record (1st to 6th lines) of the notification result information of the product code “001001” in the table of FIG. 11 is used as it is. In this case, in FIG. 22, the product code “001001” includes the expected purchase information similar to FIG. 13B. The expected purchase information in FIG. 22 includes expected purchase information of other product codes.

In this manner, a table of expected purchase information of each product for each customer for a plurality of target sales times T _j as shown in FIGS. 19A to 19D and 22 can be generated in advance by the flowcharts of FIGS. 18A to 18C. Selected at step 602 of FIG. 17 when the table of expected purchase information for each product for each customer for one target sales time T _j of the plurality of target sales time T _j is the flow chart of FIG. 17 is executed later Is done. As a result, the product information can be notified to the target customer in a short time.

  According to the above-described embodiment, specific merchandise information can be selectively notified only to customers selected according to priority, and merchandise can be sold to customers in a short time before the freshness is reduced.

  In the above-described embodiment, processing of information related to a product delivered at a local production store has been described. However, the embodiment can be applied to other sales business, store business, distribution business, and the like. The embodiment also provides notification of product information to customers in a retail store such as a supermarket that manufactures and sells products such as bread and Western confectionery, fresh confectionery, and prepared dishes that are preferred for freshness or have a short shelf life. Applicable. The embodiment can also be applied to, for example, notification of product information such as a fashionable sold-out product, or notification of product information such as a ticket with a sales deadline.

  All examples and conditional expressions given here are intended to help the reader understand the inventions and concepts that have contributed to the promotion of technology, such examples and It is understood that the present invention is not limited to the conditions, and that the organization of such examples in the specification is not related to the superiority or inferiority of the present invention. Although embodiments of the present invention have been described in detail, it will be understood that various changes, substitutions and variations can be made thereto without departing from the spirit and scope of the invention.

Regarding the embodiment including the above examples, the following additional notes are further disclosed.
(Supplementary note 1) In the storage device, for each piece of customer identification information, record information on the elapsed time from transmission of information about the product to purchase of the product, and specific product information,
According to a priority order that gives higher priority to customer identification information with a shorter average elapsed time than the average elapsed time for each customer identification information, a plurality of customer identification information is selected from the performance information,
A program for causing an information processing apparatus to execute a process of generating notification information regarding the specific product including destination information corresponding to the plurality of selected customer identification information.
(Supplementary note 2) The program according to supplementary note 1, wherein the information relating to the product is past notification information relating to the specific product.
(Supplementary Note 3) The performance information includes the number of purchases of the product for each customer identification information,
The priority is further given higher priority to customer identification information having a larger average value of the number of purchases of the specific product among two or more customer identification information of the same average elapsed time within the same or tolerance. The program according to appendix 1 or 2, characterized by providing a degree.
(Supplementary Note 4) The performance information includes the number of purchases of the product for each customer identification information,
The priority is given to the customer identification information having a larger average value of the number of purchases of the specific product among the plurality of customer identification information whose average elapsed time is within a threshold time. The program according to appendix 1 or 2, characterized in that it exists.
(Supplementary Note 5) The performance information includes the number of purchases of the product for each customer identification information,
The process of selecting the plurality of customer identification information is performed when the total number of predicted purchases or expected purchases based on the number of purchases of the plurality of customer identification information is greater than the target number of the specific product. The program according to any one of appendices 1 to 4, wherein the program ends the selection of customer identification information.
(Supplementary Note 6) The program according to Supplementary Note 5, wherein the target number is a stock number of product information in the storage device.
(Additional remark 7) The process which produces | generates the notification information regarding the said specific goods includes producing | generating the notification information regarding the said specific goods according to the said priority, Any one of Additional remark 1 thru | or 6 characterized by the above-mentioned. Program.
(Additional remark 8) The said performance information contains the information showing the presence or absence of the purchase of the said goods for every customer identification information,
Further, the priority is a customer having a larger ratio of the number of purchases to the number of transmissions of each customer identification information among two or more customer identification information of the same average elapsed time within the same or tolerance. The program according to any one of appendices 1 to 9, wherein the program gives higher priority to identification information.
(Supplementary Note 9) Further, the information processing apparatus further includes a process of calculating the elapsed time based on customer identification information and information related to transmission related to merchandise and purchase information stored in the storage device and generating the record information in advance. The program according to any one of appendices 1 to 8, wherein the program is executed.
(Supplementary note 10) Further, the information processing includes processing for deleting the elapsed time in the performance information exceeding the threshold time and setting the number of purchases in the performance information corresponding to the deleted elapsed time to 0 (zero). The program according to any one of appendices 1 to 8, wherein the program is executed by an apparatus.
(Additional remark 11) Information processing apparatus,
In the storage device, for each customer identification information, store actual information on the elapsed time from the transmission of information about the product to the purchase of the product, and specific product information,
According to a priority order that gives higher priority to customer identification information with a shorter average elapsed time than the average elapsed time for each customer identification information, a plurality of customer identification information is selected from the performance information,
A method of executing a process of generating notification information regarding the specific product including destination information corresponding to the plurality of selected customer identification information.
(Supplementary Note 12) A storage device that stores performance information on the elapsed time from transmission of information about a product to purchase of the product and specific product information for each customer identification information;
A selection unit that selects a plurality of customer identification information from among the performance information according to a priority order that gives higher priority to customer identification information having a shorter average elapsed time than the average elapsed time for each customer identification information;
An information generating unit that generates notification information about the specific product including destination information corresponding to the plurality of selected customer identification information;
Including information processing apparatus.

5 Network 10 Server Device 16 Storage Device 102 Processor 104 Memory 12 E-Mail Server Device 20 Inventory Management Terminal 30 Charge Terminal 40, 60 Information Processing Terminal 64 Portable Information Terminal

Claims (9)

For each customer identification information, by referring to the storage device for storing record information relating to the elapsed time from the transmission of information about products to purchase the product, shorter customer identification information is a representative value of the elapsed time for each customer identification information in accordance with the priority to give higher priority to select a plurality of customer identification information from among the record information,
Program for executing a process of generating the notification information of the destination information corresponding to a plurality of customer identification information said selected regarding including specific item to the information processing apparatus.   The program according to claim 1, wherein the information on the product is past notification information on the specific product. The track record information includes the number of purchases of the product for each customer identification information,
Further, the priority order gives a higher priority to customer identification information having a larger average value of the number of purchases of the specific product among a plurality of customer identification information whose representative value is within a threshold time. The program according to claim 1 or 2, characterized by the above. The track record information includes the number of purchases of the product for each customer identification information,
The priority is higher than the customer identification information having a larger average value of the number of purchases of the specific product among the two or more customer identification information of the same representative value within the same or tolerance. The program according to claim 1, wherein the program is provided. The track record information includes the number of purchases of the product for each customer identification information,
The process of selecting the plurality of customer identification information is performed when the total number of predicted purchases or expected purchases based on the number of purchases of the plurality of customer identification information is greater than the target number of the specific product. The program according to any one of claims 1 to 4, wherein the selection of customer identification information is terminated.   6. The program according to claim 1, wherein the process of generating the notification information related to the specific product includes generating the notification information related to the specific product according to the priority order. Accepting the specification of a specific product and the input of the sales period of the specific product,
For each of the plurality of customers, referring to the storage unit that stores the actual information about the elapsed time from the transmission of information about the product to the purchase, among the plurality of customers, the representative time that is a representative value of the elapsed time is the sales Generate a set containing customers that are within the period,
Generating notification information regarding a specific product destined for at least one of the customers included in the generated set;
A program for causing an information processing apparatus to execute processing. Information processing device
For each customer identification information, by referring to the storage device for storing record information relating to the elapsed time from the transmission of information about products to purchase the product, shorter customer identification information is a representative value of the elapsed time for each customer identification information in accordance with the priority to give higher priority to select a plurality of customer identification information from among the record information,
How to perform the process of generating the notification information of the destination information corresponding to a plurality of customer identification information said selected regarding including specific product. A storage device that stores performance information on the elapsed time from the transmission of information about the product to the purchase of the product for each customer identification information;
A selection unit that selects a plurality of customer identification information from the performance information according to a priority order that gives higher priority to customer identification information having a shorter representative value of the elapsed time for each customer identification information;
An information generation unit address information corresponding to a plurality of customer identification information the selected generating the notification information about including particular product,
Including information processing apparatus.

Images