JP6767254B2 - Automatic ordering system, automatic ordering method, and automatic ordering program - Google Patents

Description

The present invention relates to an automatic ordering system, an automatic ordering method, and an automatic ordering program.

Conventionally, a service of purchasing products on a regular basis using an online shopping system has been known. In connection with this, a technique for displaying a product purchased a certain number of times or more as a pre-purchased product candidate is known (see Patent Document 1). Further, there is known a technique for confirming a purchase intention online at the timing of regular purchase when there is a possibility of purchasing the product on a regular basis (see Patent Document 2). Further, there is known a technique for automatically performing order processing of products by registering order schedule information of products to be purchased on a regular basis in an order server (see Patent Document 3).

JP-A-7-296075 Japanese Unexamined Patent Publication No. 2003-22388 Japanese Unexamined Patent Publication No. 2003-157378

However, the above-mentioned conventional technology may not be convenient because it does not consider the benefits that can be obtained by purchasing the product and the benefits that can be used when purchasing the product.

The present invention has been made in consideration of such circumstances, and one of the objects of the present invention is to improve the convenience of service by placing an order for a product in consideration of benefits related to product purchase.

One aspect of the present invention is a generation unit that generates a purchase plan for the product based on a condition that the privilege can be acquired or used by purchasing the product when a request for purchasing the product is received, and the generation unit. An automatic ordering system comprising a providing unit that provides the purchase plan generated by.

According to one aspect of the present invention, the convenience of the service can be improved by placing an order for the product in consideration of the privilege related to the purchase of the product.

It is a block diagram of the automatic ordering system 1 of embodiment. It is a block diagram of the shopping server 500. It is a figure which shows an example of a store database 610. It is a figure which shows an example of the product database 620. It is a figure which shows an example of a privilege database 630. It is a figure which shows an example of the purchase history database 640. It is a figure which shows an example of the content 1000 which makes you choose whether to purchase newly or from the order history when purchasing a product. It is a figure which shows an example of purchase condition content 1010. It is a figure which shows an example of purchase condition content 1020. It is a figure which shows an example of the purchase plan content 1030. It is a figure which shows an example of the purchase plan content 1040. It is a figure which shows an example of the privilege list content 1050. It is a figure which shows an example of the edit content 1060. It is a flowchart which shows the flow of process which provides purchase plan content. It is a figure which shows the simulation result of the purchase plan. It is a figure which shows the simulation result of the purchase plan. It is a figure which shows the state of editing a purchase plan. It is a figure which shows an example of the updated purchase plan content 1030 #. It is a flowchart which shows an example of the flow of entry processing. It is a figure which shows an example of the content for entry. It is a flowchart which shows an example of the flow of a notification process. It is a flowchart which shows the flow of process which generates a purchase plan based on a privilege use condition. It is a figure which shows an example of the hardware composition of the terminal apparatus 100, and the shopping server 500.

Hereinafter, embodiments of the automatic ordering system, the automatic ordering method, and the automatic ordering program of the present invention will be described with reference to the drawings.

<1. Overview>
The automated ordering system of the embodiment, when receiving a request to purchase a product, generates a purchase plan for the product based on the conditions for using or acquiring benefits by purchasing the product, and provides the generated purchase plan for shopping. It provides services. The request for purchasing a product is, for example, information requesting that a product continuously used by the user be ordered a plurality of times within a product purchase period, which is a period specified by the user. The conditions related to the award include the condition that the award can be acquired by purchasing the product (hereinafter, the award acquisition condition) and the condition that the award can be used when the product is purchased (hereinafter, the award use condition). When the automatic ordering system accepts the request, it generates purchase plan data capable of acquiring or using more benefits based on at least one of the benefit acquisition conditions or the benefit usage conditions. The purchase plan data is a simulation result including the product purchase date, the product delivery date, the presence / absence of privilege acquisition, etc. during the product purchase period. By providing the content based on the purchase plan data, the automatic ordering system of the embodiment can make the user recognize the privilege acquired by the product purchase and the privilege used at the time of product purchase. As a result, the automatic ordering system of the embodiment can enhance the convenience of the shopping service.

<2. Configuration of automatic ordering system>
FIG. 1 is a configuration diagram of the automatic ordering system 1 of the embodiment. The automatic ordering system 1 includes, for example, a terminal device 100, a store terminal 200, a login server 300, a user database server 400, a shopping server 500, a database server 600, and a payment server 700. In the automatic ordering system 1, the terminal device 100, the store terminal 200, the login server 300, the user database server 400, the shopping server 500, the database server 600, and the payment server 700 are connected to the network NW. Each device connected to the network NW has a communication interface such as a NIC (Network Interface Card) or a wireless communication module (not shown in FIG. 1). The network NW includes, for example, a radio base station, a Wi-Fi access point, a communication line, a provider, the Internet, and the like.

It should be noted that not all combinations of these components need to be able to communicate with each other, and the network NW may include a local network in part. The login server 300, the user database server 400, the shopping server 500, and the database server 600 may be partially or wholly integrated into one device.

The terminal device 100 is a device used by a user (general user). The terminal device 100 is, for example, a computer device (communication device) such as a mobile phone such as a smartphone, a tablet terminal, or a personal computer. The terminal device 100 transmits an HTTP (Hypertext Transfer Protocol) request to the shopping server 500 when a UA (User Agent) such as a web browser is activated and a predetermined operation is performed by the user. Then, the terminal device 100 generates a web screen based on the web page returned from the shopping server 500 and displays it on the display unit. A web page is content including, for example, text data described in a markup language such as HTML (Hyper Text Markup Language), style sheets, still image data, moving image data, audio data, and the like. An arbitrary application program may be used instead of the web browser as a means for acquiring the content.

The store terminal 200 is, for example, a computer used by a store manager who sells products. The store terminal 200 transmits store information including product information, inventory information, delivery period, and the like to the database server 600.

The login server 300 is a server device that manages user logins. The login server 300 receives a login request when the terminal device 100 accesses the shopping server 500. The login server 300 authenticates the user based on the user ID or the like included in the login request. The login server 300 makes the shopping service available when the user authentication is successful.

The user database server 400 is, for example, an HDD (Hard Disc Drive), a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), a ROM (Read Only Memory), or a RAM (Random Access Memory), or a hybrid using a plurality of these. It is realized by the type storage device. The user database server 400 may be realized by an external storage device that can be accessed via various networks. An example of an external storage device is a NAS (Network Attached Storage) device. The user database managed by the user database server 400 includes information necessary for login such as a user ID and password, user attribute information, privilege information that can be used by the user, and the like.

The shopping server 500 is a server device that provides a shopping service. FIG. 2 is a configuration diagram of the shopping server 500. The shopping server 500 includes, for example, a content providing unit 510, a purchase plan generation unit 520, an order processing unit 530, and a notification unit 540. These functional units are realized by, for example, a processor such as a CPU (Central Processing Unit) executing a program stored in a program memory. In addition, some or all of these functional units may be realized by hardware such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), or FPGA (Field-Programmable Gate Array). It may be realized by the cooperation of software and hardware.

The content providing unit 510 provides various contents to the terminal device 100. The content providing unit 510 provides various contents such as contents introducing products and purchase planning contents. The purchase plan generation unit 520 generates purchase plan data that is the basis of the purchase plan content based on the request acquired from the terminal device 100. The purchase plan data is information including the order date of the product, the delivery date of the product, the number of products, the privilege information, and the like. The order processing unit 530 performs a process of ordering a product based on the purchase plan data. The order processing unit 530 transmits an order request to the store terminal 200 when the order timing has arrived. The notification unit 540 notifies the terminal device 100 of various information.

The database server 600 is realized by, for example, an HDD, a flash memory, an EEPROM, a ROM, or a RAM, or a hybrid storage device using a plurality of these. The database server 600 may be realized by an external storage device accessible via various networks. An example of an external storage device is a NAS device. The database server 600 stores, for example, a store database, a product database, a privilege database, and a purchase history database.

FIG. 3 is a diagram showing an example of the store database 610. The store database 610 is information in which a product ID, inventory information, and delivery period information are associated with a store ID. FIG. 4 is a diagram showing an example of the product database 620. The product database 620 is information in which a product name, an expiration date, a set / quantity, and a number of uses are associated with a product ID. FIG. 5 is a diagram showing an example of the privilege database 630. The privilege database 630 is information in which the acquisition condition and the privilege content are associated with the privilege name. FIG. 6 is a diagram showing an example of the purchase history database 640. The purchase history database is information in which a product ID, a store ID, a purchase period, an entry privilege, and a frequency of use are associated with a user ID.

The payment server 700 is a server device that performs payment processing based on information such as purchase amounts and usage points acquired from the shopping server 500.

<3. Purchase plan content>
The purchase plan contents will be described below. FIG. 7 is a diagram showing an example of content 1000 that allows a user to select whether to purchase a new product or to purchase from an order history when purchasing a product. The shopping server 500 provides the terminal device 100 with content 1000 including a new purchase button 1001 and an order history purchase button 1002 for purchasing from the order history in response to a purchase request acquired from the terminal device 100. The shopping server 500 provides the purchase condition content 1010 when the new purchase button 1001 is selected and a request is acquired. When the shopping server 500 acquires a request based on the selection of the order history purchase button 1002, the shopping server 500 provides the purchase condition content 1020 to the terminal device 100.

FIG. 8 is a diagram showing an example of the purchase condition content 1010. The purchase condition content 1010 includes purchase condition information 1011 and a simulation viewing button 1012. The purchase condition information 1011 includes the product name, the store from which the product was purchased, the delivery period, the number of orders, the order date, the first arrival date, the number of uses, the frequency of use, the purchase period, and benefits. The product name, store to purchase, number of orders, first arrival date, number of uses, frequency of use, and product purchase period are set based on the purchase request obtained based on the user's operation. The delivery period is automatically set based on the information registered in the store database 610. Today's date is automatically set as the ordering date. The product purchase period is set to a period selected based on the user's operation. The product name, the store of purchase, the order date, the first arrival date, and the frequency of use may be automatically set based on the purchase history database 640. Further, the frequency of use may specify a time zone of the day based on the operation of the user.

The benefits are, for example, a discount on the purchase price of the product, points that can be used in place of the purchase price of the product, and free shipping of the product. Benefits can be earned if at least one of the user's attributes, merchandise, store, or merchandise purchase period is met. When the product purchase period is set from October 1st to November 30th, it is assumed that the benefits that can be obtained are the day campaign with "5" and the birthday campaign. In this case, the purchase condition information 1011 includes a day campaign with "5", the characters "birthday campaign", and a check box for selecting each campaign.

FIG. 9 is a diagram showing an example of the purchase condition content 1020. The purchase condition content 1020 includes purchase condition information 1021 and a simulation viewing button 1022. The purchase condition information 1021 includes the product name, the store from which the product was purchased, the delivery period, the number of orders, the remaining number, the number of uses, the frequency of use, the product purchase period, and benefits. In the purchase condition information 1021, the order date and the first arrival date are omitted. The remaining number is information acquired based on the user's operation, but is not limited to this, and is a number automatically calculated based on the product purchase period and usage frequency registered in the purchase history database 640. Good.

It is desirable that the notification unit 540 of the shopping server 500 notifies the privilege when there is a privilege that can be acquired and is not provided by the purchase condition content. Benefits that can be obtained but are not provided by the purchase condition content are related to, for example, the benefits that can be obtained when the purchase conditions are edited, or the campaign newly established after the product purchase period starts. It is a privilege. For example, when the shopping server 500 specifies a product purchase period from December 1st to December 31st, the shopping server 500 notifies the Christmas campaign as an additional privilege during the specified period. Further, the privilege may be set based on the total period of the product purchase period specified at the time of product purchase and the product purchase period registered in the purchase history database 640. When the product purchase period exceeds the predetermined period, the shopping server 500 determines that, for example, the privilege acquisition condition of the subscription campaign having a higher privilege rate than the privilege of the day campaign with "5" is satisfied, and the purchase condition information. Include the word subscription campaign and checkbox in 1021. As a result, the shopping server 500 notifies the added privilege.

FIG. 10 is a diagram showing an example of the purchase plan content 1030. The purchase plan content 1030 is information representing the purchase plan data for one month (October) in the product purchase period in a calendar format. The purchase plan content 1030 includes calendar information 1031, remaining quantity information 1032, purchase quantity information 1033, delivery quantity information 1034, campaign information 1035a and 1035b, privilege information 1036, purchase confirmation button 1037, purchase plan edit button 1038, and privilege list. Button 1039 is included. The calendar information 1031 is information in which the date and the day of the week are associated with each month. The remaining number information 1032 is information indicating the remaining number of products corresponding to the date. The purchase number information 1033 is information indicating the number of products to be ordered on the product ordering date. The delivery number information 1034 is information indicating the number of products arriving on the product arrival date. The campaign information 1035 is information representing a campaign that satisfies the acquisition conditions. The privilege information 1036 is information representing the privilege when the product is purchased according to the purchase plan provided in the purchase plan content 1030. The campaign information 1035 and the privilege information 1036 correspond to information representing the contents of the privilege.

FIG. 11 is a diagram showing an example of the purchase plan content 1040. The purchase plan content 1040 is information representing the purchase plan data for one month (November) in the product purchase period in a calendar format. The purchase plan content 1040 includes calendar information 1041, remaining quantity information 1042, order quantity information 1043, delivery quantity information 1044, campaign information 1045a, privilege information 1046, purchase confirmation button 1047, purchase plan edit button 1048, and privilege list button 1049. It is included.

The purchase plan content 1030 includes a switching button 1030A for switching the display from the purchase plan content 1030 to the purchase plan content 1040. The purchase plan content 1040 includes a switching button 1040A for switching the display from the purchase plan content 1040 to the purchase plan content 1030.

FIG. 12 is a diagram showing an example of the privilege list content 1050. The privilege list content 1050 is provided to the terminal device 100 when an operation for the privilege list button 1039 or 1049 is accepted. The shopping server 500 creates a content listing the privilege name, acquisition condition, and privilege content of the privilege included in the purchase plan in response to receiving the operation for the privilege list button 1039 or 1049. Each privilege may be provided by the privilege list content 1050, but is not limited to this, and may be displayed in the calendar information 1031.

FIG. 13 is a diagram showing an example of the edited content 1060. The edited content 1060 is information in which the delivery date, the number of purchases, the privilege name, and the privilege content are associated with the purchase date included in the purchase plan. A triangle mark indicating that each of the edit content 1060 can be changed is added to the purchase date, delivery date, number of purchases, and privilege name. The shopping server 500 displays the options in a pull-down list format in response to the acceptance of the operation of selecting the triangle mark. The information provided as an option may be included in the edited content 1060, and may be provided from the shopping server 500 to the terminal device 100 depending on the acceptance of the operation of selecting the triangle mark. When the shopping server 500 detects that the purchase plan has been changed, the shopping server 500 resimulates the privilege information 1036 and the like based on the changed purchase plan. The shopping server 500 provides the terminal device 100 with the purchase plan content as a result of the re-simulation.

<4. Providing purchase plan content>
FIG. 14 is a flowchart showing a flow of processing for providing the purchase plan content. The purchase plan generation unit 520 first determines whether or not a purchase request has been received from the terminal device 100 (S100). If the purchase plan generation unit 520 has not received the purchase request, the purchase plan generation unit 520 ends the process of this flowchart. When the purchase plan generation unit 520 receives the purchase request, it determines whether or not the privilege acquisition condition is satisfied (S102). The purchase plan generation unit 520 determines whether or not the privilege acquisition condition is satisfied based on the product purchase period specified by the purchase request, but is not limited to this, and in addition to the product purchase period or the product purchase period. Alternatively, it may be determined whether or not the privilege acquisition condition is satisfied based on the attributes of the user, the attributes of the product, and the like. If the purchase plan generation unit 520 does not satisfy the privilege acquisition condition, the purchase plan generation unit 520 provides the purchase plan content based on the remaining number of products and the frequency of use (S118).

Next, the purchase plan generation unit 520 selects one of the latest privilege acquisition dates (S104). The award acquisition date is a date that satisfies the award acquisition condition. Next, the purchase plan generation unit 520 determines whether or not there is a privilege acquisition date next to the selected privilege acquisition date in the product purchase period (S106). If there is no next privilege acquisition date, the purchase plan generation unit 520 determines whether or not the remaining number becomes 0 by the end of the product purchase period (S114). If the remaining number becomes 0 by the end of the product purchase period, the purchase plan generation unit 520 determines to order the product on the selected privilege acquisition date (S112). If the remaining number does not reach 0 by the end of the product purchase period, the purchase plan generation unit 520 generates the purchase plan content based on the privilege acquisition date, the remaining number of products, and the frequency of use, and uses the generated purchase plan content as a terminal. Provided to device 100 (S116).

If there is a next privilege acquisition date, the purchase plan generation unit 520 calculates a delivery candidate date when the product is ordered on the next privilege acquisition date (S108). The purchase plan generation unit 520 determines whether or not the remaining number of products becomes 0 by the calculated delivery candidate date based on the remaining number of products on the selected privilege acquisition date and the frequency of use of the products (S110). ). The purchase plan generation unit 520 determines that if the remaining number of products becomes 0 by the calculated delivery candidate date, the product is ordered on the selected privilege acquisition date (S112). Then, the purchase plan generation unit 520 returns the process to S104. As a result, the purchase plan generation unit 520 can determine whether or not to order the product for each privilege acquisition date included in the product purchase period.

(Selection of benefits based on benefit rate)
It is desirable that the purchase plan generation unit 520 preferentially selects a privilege having a high privilege rate when the privilege acquisition conditions of a plurality of privileges are satisfied. For example, in the case where the day campaign with "5" and the birthday campaign overlap, if the birthday campaign can obtain more benefits, the purchase plan generation unit 520 will perform the birthday campaign in S104. Is preferentially selected.

(4.1 Specific example of purchase plan content provision processing)
15A and 15B are diagrams showing the simulation results of the purchase plan. Hereinafter, the transition of the remaining number of products will be described together with the process of providing the purchase plan content described with reference to FIG. As shown in FIG. 15, on October 1, 14 products were ordered based on the purchase request, 14 products were delivered on October 3, and the products were used once a day. It shall be. In addition, the purchase plan generation unit 520 selects the day campaign with "5" in the purchase condition content, so that October 5, October 15, October 25, and November 5 during the product purchase period. , It is determined that the privilege acquisition condition is satisfied by ordering the product on November 15th and November 25th (S102).

The purchase plan generation unit 520 first selects October 5 as the privilege acquisition date (S104). The purchase plan generation unit 520 determines that October 15th is the next privilege acquisition date on October 5th (S106). The purchase plan generation unit 520 calculates October 17 as a delivery candidate date when the order is placed on October 15 (S108). On October 17, the purchase plan generation unit 520 determines that the remaining number of products will be exhausted unless an order is placed on October 5 (S110), and determines that the product will be ordered on October 5 (S112).

Next, the purchase plan generation unit 520 selects October 15 as the privilege acquisition date (S104). The purchase plan generation unit 520 determines that October 25 is the next privilege acquisition date on October 15 (S106). The purchase plan generation unit 520 calculates October 27 as a delivery candidate date when an order is placed on October 25 (S108). On October 27, the purchase plan generation unit 520 determines that the remaining number of products will not be exhausted even if the order is not placed on October 15 (S110), and determines that the product will not be ordered on October 15 (S110). S112).

Next, the purchase plan generation unit 520 selects October 25 as the privilege acquisition date (S104). The purchase plan generation unit 520 determines that November 5th is the next privilege acquisition date on October 25th (S106). The purchase plan generation unit 520 calculates November 7 as a delivery candidate date when the order is placed on November 5 (S108). On November 7, the purchase plan generation unit 520 determines that the remaining number of products will be exhausted unless an order is placed on October 25 (S110), and determines that the product will be ordered on October 25 (S112).

Next, the purchase plan generation unit 520 selects November 5 as the privilege acquisition date (S104). The purchase plan generation unit 520 determines that November 15th is the next privilege acquisition date on November 5th (S106). The purchase plan generation unit 520 calculates November 17 as a delivery candidate date when the order is placed on November 15 (S108). On November 17, the purchase plan generation unit 520 determines that the remaining number of products will be exhausted unless the order is placed on November 5 (S110), and determines that the product will be ordered on November 5 (S112).

Next, the purchase plan generation unit 520 selects November 15 as the privilege acquisition date (S104). The purchase plan generation unit 520 determines that November 25th is the next privilege acquisition date on November 15th (S106). The purchase plan generation unit 520 calculates November 27 as a delivery candidate date when the order is placed on November 25 (S108). On November 27, the purchase plan generation unit 520 determines that the remaining number of products will not be exhausted even if the order is not placed on November 15 (S110), and determines that the product will not be ordered on November 15 (S110). S112).

Next, the purchase plan generation unit 520 selects November 25 as the privilege acquisition date (S104). Since there is no next privilege acquisition date on November 25, the purchase plan generation unit 520 determines whether or not the remaining number becomes 0 by the end of the product purchase period (S116). The purchase plan generation unit 520 determines that the product will be ordered on November 25, since the remaining number will be 0 by the end of the product purchase period (S112).

As described above, the purchase plan generation unit 520 can generate the purchase plan content for ordering the product on the privilege acquisition date.

(4.2 Editing of purchase plan contents)
The process of editing the purchase plan content will be described below. FIG. 16 is a diagram showing how the purchase plan is edited. In the state where the shopping server 500 is providing the edited content 1060, the day campaign with "5" that can acquire the privilege on November 5 based on the user's operation is privileged on November 3rd. You have accepted a request to change to a birthday campaign where you can earn. The purchase plan generation unit 520 may change the campaign based on the operation of editing the privilege name, but the campaign is not limited to this, and the campaign may be changed based on the operation of editing the purchase date.

When the purchase plan generation unit 520 receives the request to change the campaign, the purchase plan content 1030 is updated by executing the re-simulation of the purchase plan. FIG. 17 is a diagram showing an example of the updated purchase plan content 1030 #. The purchase plan generation unit 520 purchases 14 pieces of one set on November 3, and updates the calendar information 1031 # so as to deliver 14 pieces of one set on November 5. In addition, the purchase plan generation unit 520 changes the privilege information 1036 # so as to update the purchase amount and the profit total. As described above, the purchase plan generation unit 520 can resimulate the purchase plan in response to the change in the purchase conditions and provide the edited purchase plan content.

<5. Entry processing>
The entry process executed for the user to acquire the privilege will be described below. The entry process is a process for confirming the intention of the user to acquire the privilege by purchasing the product. FIG. 18 is a flowchart showing an example of the flow of entry processing. First, the shopping server 500 determines whether or not the product purchase request has been accepted (S200). The product purchase request is provided from the terminal device 100 to the shopping server 500 when the terminal device 100 receives an operation on the purchase confirmation button 1037 in the purchase plan content 1030.

Next, the shopping server 500 refers to the purchase plan data and determines whether or not the purchase plan satisfies the privilege acquisition condition (S202). If the purchase plan does not satisfy the privilege acquisition condition, the shopping server 500 ends the process of this flowchart. The shopping server 500 provides entry content when the purchase plan satisfies the privilege acquisition condition (S204). FIG. 19 is a diagram showing an example of entry content. The entry content 1070 includes a message 1071 inquiring about the intention to acquire the privilege and a request button 1072 for requesting the entry.

Next, the shopping server 500 determines whether or not the entry request has been accepted by receiving the information based on the operation of selecting the request button 1072 (S206). If the shopping server 500 does not receive the entry request, the shopping server 500 ends the process of this flowchart.

When the shopping server 500 receives the entry request, the shopping server 500 accepts an operation based on the intention to acquire the privilege based on the operation for providing the entry content 1070. Next, the shopping server 500 determines whether or not to acquire the same privilege a plurality of times (S208). When the shopping server 500 acquires the same privilege a plurality of times, the shopping server 500 registers an entry for all of the privilege acquired a plurality of times (S210). Registering an entry means storing the entered privilege information in the purchase history database 640. If the shopping server 500 does not acquire the same privilege a plurality of times, the shopping server 500 registers an entry for one privilege (S212).

Next, the shopping server 500 determines whether or not the entry registration is completed for all the benefits included in the purchase plan (S214). If the entry registration for all the benefits is not completed, the shopping server 500 returns the process to S204. For example, when the shopping server 500 generates a purchase plan that satisfies the privilege acquisition conditions of the day campaign with "5" and the birthday campaign, the shopping server 500 also performs the birthday campaign in addition to the day campaign with "5". The processes from S204 to S212 are executed.

<6. Notification processing>
The notification process for notifying the privilege will be described below. FIG. 20 is a flowchart showing an example of the flow of notification processing. The shopping server 500 determines whether or not the product purchase request has been accepted (S300). The shopping server 500 executes the purchase plan in response to receiving the product purchase request (S302). Executing the purchase plan means that the order processing unit 530 performs the order processing of the product and the delivery work from the store to the user on the condition that the payment processing by the payment server 700 is completed.

The shopping server 500 determines whether or not a new privilege capable of satisfying the privilege acquisition condition has been added (S304). The new privilege that can satisfy the privilege acquisition condition is, for example, a privilege that satisfies the privilege acquisition condition by editing the purchase date of the product, the number of purchases of the product, and the like. The shopping server 500 notifies the added privilege when a new privilege that can satisfy the privilege acquisition condition is added based on the change of the user attribute, the editing of the purchase plan, the addition of the new campaign, or the like (S306). ). When the terminal device 100 is a web browser, the shopping server 500 transmits an e-mail containing the added privilege in the text. When the terminal device 100 is an application, the shopping server 500 notifies the privilege added by the push notification.

Next, the shopping server 500 determines whether or not the purchase plan has been edited in response to the notification of the added privilege (S308). When the purchase plan is edited, the shopping server 500 executes a re-simulation of the purchase plan (S310).

<7. Other embodiments>
Hereinafter, other embodiments will be described. In the above-described embodiment, the purchase plan is generated based on the privilege acquisition condition, but the purchase plan may be generated based on the privilege usage condition instead of the privilege acquisition condition. For example, when a product is purchased and a discount ticket that can be used at the next opportunity to purchase the product is acquired, information on the discount ticket is stored in the purchase history database 640. When purchasing a product, the purchase plan generation unit 520 refers to the purchase history database 640 and determines whether or not there is a discount ticket as a privilege usage condition. If there is a discount ticket, the purchase plan generation unit 520 generates a purchase plan for purchasing the product using the discount ticket. The privilege used when purchasing the product may be points already held by the user.

FIG. 21 is a flowchart showing a flow of processing for generating a purchase plan based on the privilege usage conditions. The purchase plan generation unit 520 first determines whether or not a purchase request has been received from the terminal device 100 (S400). If the purchase plan generation unit 520 has not received the purchase request, the purchase plan generation unit 520 ends the process of this flowchart. When the purchase plan generation unit 520 receives the purchase request, it determines whether or not the privilege usage condition is satisfied (S402). If the purchase plan generation unit 520 does not satisfy the privilege usage conditions, the purchase plan generation unit 520 provides the purchase plan content based on the remaining number of products and the frequency of use (S418).

Next, the purchase plan generation unit 520 selects one of the latest privilege usage dates (S404). The award usage date is a date that meets the award usage conditions. Next, the purchase plan generation unit 520 determines whether or not there is a privilege use date next to the selected privilege use date in the product purchase period (S406). If there is no next privilege use date, the purchase plan generation unit 520 determines whether or not the remaining number becomes 0 by the end of the product purchase period (S414). The purchase plan generation unit 520 determines that if the remaining number becomes 0 by the end of the product purchase period, the product is ordered on the selected privilege usage date (S412). If the remaining number does not reach 0 by the end of the product purchase period, the purchase plan generation unit 520 generates the purchase plan content based on the privilege usage date, the remaining number of products, and the frequency of use, and uses the generated purchase plan content as a terminal. Provided to device 100 (S416).

If there is a next privilege use date, the purchase plan generation unit 520 calculates a delivery candidate date when the product is ordered on the next privilege use date (S408). The purchase plan generation unit 520 determines whether or not the remaining number of products becomes 0 by the calculated delivery candidate date based on the remaining number of products on the selected privilege usage date and the frequency of use of the products (S410). ). The purchase plan generation unit 520 determines that if the remaining number of products becomes 0 by the calculated delivery candidate date, the product is ordered on the selected privilege usage date (S412). Then, the purchase plan generation unit 520 returns the process to S404. As a result, the purchase plan generation unit 520 can determine whether or not to order the product for each privilege use date included in the product purchase period.

Although the purchase plan generation unit 520 generates the purchase plan based on the privilege usage conditions, the purchase plan may be generated based on both the privilege acquisition conditions and the privilege usage conditions. In this case, the purchase plan generation unit 520 generates a purchase plan for ordering the product on the privilege acquisition date or the privilege usage date. Further, when both the privilege acquisition condition and the privilege usage condition are satisfied, the purchase plan generation unit 520 selects the one with the higher privilege rate and generates a purchase plan for ordering the product on the day when the selected condition is satisfied.

<8. Effect of embodiment>
As described above, according to the automatic ordering system 1 of the embodiment, when a request for purchasing a product is received, a product purchase plan is made based on a privilege acquisition condition that allows the privilege to be acquired by purchasing the product. It can be generated and content can be provided based on the generated purchase plan. As a result, according to the automatic ordering system 1, the convenience of the shopping service can be improved by placing an order for the product in consideration of the privilege related to the purchase of the product.

In addition, according to the automatic ordering system 1, if the privilege acquisition condition is satisfied by purchasing the product during the predetermined period included in the product purchase period, a purchase plan for purchasing the product within the predetermined period is generated, so that the privilege is maximized. It is possible to generate a purchase plan that can be acquired in a limited amount.

Further, according to the automatic ordering system 1, if a product is insufficient during the period when the privilege acquisition condition is satisfied, a purchase plan for purchasing the product during the period when the privilege acquisition condition is satisfied is generated. It is possible to suppress the situation where the remaining number of products is insufficient.

Further, according to the automatic ordering system 1, according to the date included in the calendar, the purchase plan content including the period satisfying the privilege acquisition condition, the purchase date and the number of purchases of the product, the delivery date and the number of deliveries of the product Since it is provided, it is possible to visualize that benefits can be obtained by purchasing the product, and it is possible to improve the satisfaction level of the shopping service.

Further, according to the automatic ordering system 1, the contents of the benefits associated with the period satisfying the privilege acquisition condition, the list of benefits that can be acquired during the product purchase period, and the total of the benefits acquired during the product purchase period are provided. Therefore, the convenience and satisfaction of the shopping service can be further improved.

Further, according to the automatic ordering system 1, when it is possible to satisfy a plurality of privilege acquisition conditions, one of the privilege acquisition conditions is selected based on the privilege rate, and a purchase plan satisfying the selected privilege acquisition conditions. Is generated, so it is possible to generate a purchase plan that maximizes the benefits.

Further, according to the automatic ordering system 1, the purchase plan can be edited based on the operation of the user, so that the convenience of the shopping service can be further improved.

Furthermore, according to the automatic ordering system 1, when a purchase plan that satisfies the same privilege acquisition condition is generated multiple times by purchasing the product multiple times, the entry content is provided once and the privilege is to be acquired. When the operation based on is accepted once, the purchase plan to purchase the product multiple times is executed, so even if the privilege is acquired multiple times, the shopping service is further performed without forcing the operation for multiple entry. The convenience of the system can be improved.

Further, according to the automatic ordering system 1, when there is a new privilege that can acquire the privilege during the product purchase period, the new privilege is notified, so that the convenience of the shopping service can be further improved. Further, according to the automatic ordering system 1, the convenience and satisfaction of the shopping service can be further improved by editing the purchase plan in order to acquire the new privilege notified.

<9. Hardware configuration>
FIG. 22 is a diagram showing an example of the hardware configuration of the terminal device 100 and the shopping server 500. This figure shows an example in which the terminal device 100 is a personal computer or the like. In the terminal device 100, for example, a CPU 101, a RAM 102, a ROM 103, a secondary storage device 104 such as a flash memory, an interface 105 for operation and display, and a wireless communication module 106 are connected to each other by an internal bus or a dedicated communication line. It has a configured structure.

The shopping server 500 has a configuration in which, for example, NIC501, CPU502, RAM503, ROM504, a secondary storage device 505 such as a flash memory or an HDD, and a drive device 506 are connected to each other by an internal bus or a dedicated communication line. .. A portable storage medium such as an optical disk is mounted on the drive device 506. The program stored in the portable storage medium mounted on the secondary storage device 505 or the drive device 506 is expanded in the RAM 503 by a DMA controller (not shown) or the like, and executed by the CPU 502 to function the shopping server 500. The part is realized.

Although the embodiments for carrying out the present invention have been described above using the embodiments, the present invention is not limited to these embodiments, and various modifications and substitutions are made without departing from the gist of the present invention. Can be added.

1 ... Automatic ordering system 100 ... Terminal device 300 ... Login server 400 ... User database server 500 ... Shopping server 510 ... Content providing unit 520 ... Purchase plan generation unit 530 ... Order processing unit 540 ... Notification unit 600 ... Database server 610 ... Store database 620 ... Product database 630 ... Bonus database 640 ... Purchase history database 1010 ... Purchase condition content 1011 ... Purchase condition information 1020 ... Purchase condition content 1021 ... Purchase condition information 1030 ... Purchase plan content 1032 ... Remaining number information 1033 ... Purchase number information 1033 ... Order quantity information 1034 ... Delivery quantity information 1035 ... Campaign information 1040 ... Purchase plan content 1050 ... Bonus list content 1060 ... Editing content 1070 ... Entry content

Claims (19)

When a request to purchase a product based on a user's operation is received, the first condition regarding the timing of product purchase at which the first privilege can be acquired or used and the timing at which the second privilege can be acquired or used. Acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing different from or overlapping with, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A generator that generates a purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition so that the index based on the privilege that can be performed becomes larger.
A provider that provides the purchase plan generated by the generator and
Automatic ordering system with. The first condition and the second condition are to purchase the product within a predetermined period.
The generation unit generates a purchase plan for purchasing the product in the predetermined period.
The automatic ordering system according to claim 1. When a request to purchase a product is received by designating the product purchase period, the first condition and the second privilege of purchasing the product during a predetermined period during which the first privilege can be acquired or used are acquired. or a second condition and use the predetermined period that may be is to purchase the item into predetermined periods different or overlapping, and information about the remaining degree of the product in the transmission source of the request, the frequency of use of the product Based on the above, one or both of the first condition and the second condition so that the index based on the privilege that can be acquired or used by the sender of the request becomes larger during the product purchase period. A generator that generates a purchase plan including the purchase date of the product that satisfies the conditions of
A provider that provides the purchase plan generated by the generator and
Automatic ordering system with. The providing unit, in response to the date included in the calendar, the predetermined period, date of purchase and cart of the product, provides the contents of the purchase plan that contains delivery date and delivery speed of the products,
The automatic ordering system according to claim 3 . The providing unit, in association with the predetermined period, providing the content of the purchase plan that includes information indicating the content of benefits,
The automatic ordering system according to claim 4. When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A generator that generates a purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition so that the index based on is larger.
A provider that provides content that includes the purchase plan generated by the generator and information showing a list of benefits that can be earned or used during the specified product purchase period .
Automatic ordering system with. When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A generator that generates a purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition so that the index based on is larger.
A provider that provides content that includes information indicating the purchase plan generated by the generator and the total benefits earned or available during the specified merchandise purchase period .
Automatic ordering system with. When it is possible to satisfy the condition that a plurality of benefits can be acquired or used, the generation unit preferentially selects the condition having a high privilege rate and generates a purchase plan satisfying the selected condition.
The automatic ordering system according to any one of claims 1 to 7 . The generation unit edits the purchase plan based on the user's operation.
The automatic ordering system according to any one of claims 1 to 8 . An execution unit that executes the purchase plan generated by the generation unit is further provided.
When the execution unit receives an operation based on the intention to acquire the privilege, the execution unit executes the purchase plan.
The automatic ordering system according to any one of claims 1 to 9. When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A generator that generates a purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition so that the index based on is larger.
An entry that confirms the intention to acquire benefits by purchasing a product when the purchase plan generated by the generation unit is provided and the operation of purchasing the product is accepted according to the purchase plan generated by the generation unit. With a provider that provides content for
An execution unit that executes the purchase plan generated by the generation unit when an operation based on the intention to acquire the privilege is accepted based on the operation for providing the entry content.
Automatic ordering system with. When the generation unit generates a purchase plan that satisfies the same conditions multiple times by purchasing the product multiple times.
The providing unit provides the entry content once,
The execution unit executes a purchase plan for purchasing a product a plurality of times when the operation based on the intention to acquire the privilege is received once.
The automatic ordering system according to claim 11. When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A generator that generates a purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition so that the index based on is larger.
A provider that provides the purchase plan generated by the generator and
In the case of executing the purchase plan generated by the generation unit, if there is a new privilege that can acquire the privilege, a notification unit for notifying the new privilege and a notification unit.
Automatic ordering system with. The computer
When a request to purchase a product based on a user's operation is received, the first condition regarding the timing of product purchase at which the first privilege can be acquired or used and the timing at which the second privilege can be acquired or used. Acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing different from or overlapping with, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition is generated so that the index based on the privilege that can be performed becomes larger.
Provide said said purchased plan generated.
Automatic ordering method. On the computer
When a request to purchase a product based on a user's operation is received, the first condition regarding the timing of product purchase at which the first privilege can be acquired or used and the timing at which the second privilege can be acquired or used. Acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing different from or overlapping with, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition is generated so that the index based on the privilege that can be performed becomes larger.
To provide the generated said purchase plan,
Automatic ordering program. The computer
When a request to purchase a product is received by specifying the product purchase period, the first condition and the second privilege of purchasing the product during a predetermined period during which the first privilege can be acquired or used are acquired. or a second condition and use the predetermined period that may be is to purchase the item into predetermined periods different or overlapping, and information about the remaining degree of the product in the transmission source of the request, the frequency of use of the product Based on the above, one or both of the first condition and the second condition so that the index based on the privilege that can be acquired or used by the sender of the request becomes larger during the product purchase period. Generate a purchase plan that includes the purchase date of the product that meets the conditions of
Provide said said purchased plan generated.
Automatic ordering method. On the computer
When a request to purchase a product is received by designating the product purchase period, the first condition and the second privilege of purchasing the product during a predetermined period during which the first privilege can be acquired or used are acquired. or a second condition and use the predetermined period that may be is to purchase the item into predetermined periods different or overlapping, and information about the remaining degree of the product in the transmission source of the request, the frequency of use of the product Based on the above, one or both of the first condition and the second condition so that the index based on the privilege that can be acquired or used by the sender of the request becomes larger during the product purchase period. Generate a purchase plan that includes the purchase date of the product that meets the conditions of
To provide the generated said purchase plan,
Automatic ordering program. The computer
When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition is generated so that the index based on is larger.
Provides the generated the purchase plan,
When the operation of purchasing the product is accepted according to the generated purchase plan, the entry content for confirming the intention to acquire the privilege by purchasing the product is provided.
When the operation based on the intention to acquire the privilege is accepted based on the operation for providing the entry content, the generated purchase plan is executed.
Automatic ordering method. On the computer
When a request to purchase a product is received, the first condition regarding the timing of product purchase in which the first benefit can be acquired or used differs from or overlaps with the timing in which the second benefit can be acquired or used. A privilege that can be acquired or used by the sender of the request in a predetermined period based on the second condition regarding the timing of the request, the information on the residual degree of the product at the sender of the request, and the frequency of use of the product. A purchase plan including the purchase date of the product that satisfies one or both of the first condition and the second condition is generated so that the index based on is larger.
To provide the generated the purchase plan,
When the operation of purchasing the product is accepted according to the generated purchase plan, the entry content for confirming the intention to acquire the privilege by purchasing the product is provided.
When the operation based on the intention to acquire the privilege is accepted based on the operation for providing the entry content, the generated purchase plan is executed.
Automatic ordering program.

Images