Product providing system, product providing method and product providing program

Abstract

To continuously provide products whose state changes through maturity.SOLUTION: A product providing system for dispatching products that mature over time to destinations on a plurality of delivery dates with different degrees of maturity includes: an information receiving unit for receiving customer request information including the plurality of delivery dates and the destinations; a database registration unit for registering the customer request information in a customer information database; a timing determination unit for determining, for each delivery date, whether a timing has arrived that is before a first period from the delivery date, based on the customer information database; and an information output unit for outputting delivery information for dispatching the product to the destination on the delivery date when the timing has arrived.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a product provision system, a product provision method, and a product provision program, and more particularly to a product provision system, a product provision method, and a product provision program for delivering products that mature over time at multiple delivery dates with different degrees of maturity. [Background technology]

[0002] 2. Description of the Related Art Conventionally, in the field of alcoholic beverages, whiskey, wine, and the like that have been aged for a long time have been traded at high prices, and various systems have been presented for the purpose of providing such products.

[0003] For example, Patent Document 1 describes a wine providing system that holds wine bottles in a predetermined aging environment and stores and manages the wine under conditions according to the customer's preferences and the characteristics of the wine. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2007-269491 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, while conventional systems were able to provide customers with products whose aging period had passed, they did not take into consideration the need to continually provide customers with products in the middle of the aging period, allowing them to experience the aging process.

[0006] The present invention has been made based on the above recognition, and an object of the present invention is to provide a product providing system that is capable of continuously providing products whose state changes due to aging. [Means for solving the problem]

[0007] The product provision system according to the present invention comprises: A product provision system for delivering a product that matures over time to a destination on a plurality of delivery dates with different maturity levels, an information receiving unit that receives customer request information including the plurality of delivery dates and the delivery destination; a database registration unit that registers the customer request information in a customer information database; a timing determination unit that determines, for each of the delivery dates, whether or not a timing that is a first period before the delivery date has arrived based on the customer information database; an information output unit that outputs delivery information for sending the product to the destination on the delivery date when the timing arrives; Equipped with.

[0008] In addition, in the above-mentioned product provision system, The system may further include a customer request information change unit that accepts changes to the customer request information.

[0009] In addition, in the above-mentioned product provision system, The customer request information change unit may be configured to accept a change to the delivery date.

[0010] In addition, in the above-mentioned product provision system, The system may further include a confirmation unit that outputs a confirmation message to confirm the delivery destination and / or the delivery date included in the customer request information before a second period, which is longer than the first period, from the delivery date.

[0011] In addition, in the above-mentioned product provision system, The information output unit may be configured to output shipping information for sending the aged product if the delivery date is the final delivery date among the multiple delivery dates, and to output shipping information for sending the product that is in the process of aging if the delivery date is not the final delivery date among the multiple delivery dates.

[0012] In addition, in the above-mentioned product provision system, The product may be an alcoholic beverage, a non-alcoholic beverage, cheese, pickled plum, pickles, miso, canned fish, ham, sausage or cured meat.

[0013] In addition, in the above-mentioned product provision system, The alcoholic beverage may be whiskey, brandy, wine, sake, Shaoxing wine, shochu, awamori, beer, plum wine, fruit wine, gin or rum.

[0014] The method for providing a product according to the present invention comprises the steps of: A method for providing a product for delivering a product that matures over time to a destination on a plurality of delivery dates with different degrees of maturity, comprising: receiving customer request information including the plurality of delivery dates and the delivery destination; registering the customer request information in a customer information database; determining whether or not a timing before a first period from the delivery date has arrived for each of the delivery dates based on the customer information database; When the timing arrives, outputting delivery information for sending the product to the destination on the delivery date; Equipped with.

[0015] The product provision program according to the present invention includes: A product provision program for delivering a product that matures over time to a destination on multiple delivery dates with different maturity levels, Computer, an information receiving unit that receives customer request information including the plurality of delivery dates and the delivery destination; a database registration unit that registers the customer request information in a customer information database; a timing determination unit that determines, for each of the delivery dates, whether or not a timing that is a first period before the delivery date has arrived based on the customer information database; an information output unit that outputs delivery information for sending the product to the destination on the delivery date when the timing arrives; Run it as: Effect of the Invention

[0016] According to the present invention, it is possible to continuously provide products whose state changes as they age. [Brief description of the drawings]

[0017] [Figure 1] 1 is a schematic configuration diagram of a product provision system according to a first embodiment. [Diagram 2] FIG. 2 is a functional block diagram of a customer terminal according to the first embodiment. [Diagram 3] FIG. 2 is a functional block diagram of a brewing company server according to the first embodiment. [Figure 4] 3 is an example of a customer information database according to the first embodiment. [Diagram 5] FIG. 4 is a sequence diagram illustrating an example of a product provision process according to the first embodiment. [Figure 6] 4 is an example of an input screen for customer request information according to the first embodiment. [Figure 7] FIG. 4 is a diagram showing an example of delivery information according to the first embodiment. [Figure 8] FIG. 11 is a functional block diagram of a brewing company server according to a second embodiment. [Figure 9] FIG. 11 is a sequence diagram illustrating an example of a product provision process according to the second embodiment. [Figure 10] 13 is an example of a customer request information change screen according to the second embodiment. [Figure 11] 13 is another example of the customer request information change screen according to the second embodiment. [Figure 12] FIG. 13 is a functional block diagram of a brewing company server according to a third embodiment. [Figure 13] FIG. 13 is a sequence diagram illustrating an example of a product provision process according to the third embodiment. [Figure 14] 13 is an example of a confirmation message according to the third embodiment. [Figure 15] 13 is an example of a confirmation message according to a modified example of the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In each drawing, components having equivalent functions are denoted by the same reference numerals.

[0019] (First embodiment) <Product provision system> A product providing system 1 according to a first embodiment will be described with reference to Figs. 1 to 4. Fig. 1 is a schematic configuration diagram of the product providing system 1 according to the present embodiment. Fig. 2 is a functional block diagram of a customer terminal 10 according to the present embodiment. Fig. 3 is a functional block diagram of a brewing company server 20 according to the present embodiment. Fig. 4 is an example of a customer information database DB according to the present embodiment.

[0020] The product provision system 1 is a system for delivering products that age over time to a delivery destination on multiple delivery dates with different degrees of maturity. In this embodiment, a case will be described in which whiskey, which is an alcoholic beverage, is delivered to a customer's designated address on a delivery date designated by the customer.

[0021] In this application, the product will be referred to as a "matured product" or a "matured product" depending on the degree of maturity. When there is no need to distinguish between the two, they will be collectively referred to as a "product."

[0022] A partially aged product is a product (a product in the process of aging) that is at an intermediate stage of a targeted aging period (for example, 20 years). It is desirable that a partially aged product is at least aged enough to be sent to the customer (to the extent that it is suitable for eating or drinking, in the case of a food product). However, products sent on the "initial delivery date" described below are included in the partially aged product, even though they are hardly aged (or not aged at all). Aged products are products that have passed the targeted aging period (products that have already aged).

[0023] In this embodiment, the in-process aging product is a product that is sent on a delivery date that is not the last of the multiple delivery dates, and is also called a "sample." In this embodiment, the aged product is a product that is sent on a delivery date that is the last of the multiple delivery dates, and is also called a "final product." For example, a sample is sent in a smaller volume than the final product.

[0024] As shown in Fig. 1, product provision system 1 includes one or more customer terminals 10, a brewing company server 20, and a delivery company server 30. Customer terminal 10, brewing company server 20, and delivery company server 30 are communicatively connected to each other via a communication network NW such as the Internet. The protocol of the communication network NW is not particularly limited. Customer terminal 10, brewing company server 20, and delivery company server 30 are connected to the communication network NW by wire or wirelessly.

[0025] The customer terminal 10 is a terminal used by a customer. As will be described in detail later, the customer terminal 10 accepts customer request information, which may include, for example, multiple pieces of delivery date information and delivery address information, and transmits the information to the brewing company server 20. The type of the customer terminal 10 is not particularly limited, and may be, for example, a notebook computer, a tablet terminal, a smartphone, or a desktop computer.

[0026] The brewing company server 20 is a server device located in the office or data center of the brewing company that brews whiskey. As will be described in detail later, the brewing company server 20 is configured to, for example, acquire and store customer request information transmitted from the customer terminal 10, generate delivery information for transmitting the product to the delivery destination on the delivery date, and transmit the information to the delivery company server 30.

[0027] The brewing company server 20 is configured, for example, by a general server device, but may also be configured by a desktop computer, a notebook computer, etc. The brewing company server 20 may also be a cloud server.

[0028] The delivery company server 30 is a server device owned by a delivery company. The delivery company server 30 acquires delivery information received from the brewing company server 20, for example, and performs delivery processing to deliver the product to the delivery destination on the delivery date.

[0029] The delivery company server 30 is configured, for example, by a general server device, but may also be configured by a desktop computer, a notebook computer, etc. Also, the delivery company server 30 may be a cloud server.

[0030] In this embodiment, the delivery company server 30 is linked to a warehouse management system (WMS). By using the warehouse management system, it is possible to easily manage the delivery of products and send the products on the specified delivery date.

[0031] In this embodiment, the brewing company server 20 outputs production information for producing (bottling) samples or the product, for example, at the end of the previous year to which each delivery date belongs. This production information is sent to, for example, a server device of a brewery, and the brewery takes out a portion of whiskey from a barrel B stored at the brewery based on the production information and starts producing bottles b. Bottles b are sent to a warehouse or the like of a delivery company by the beginning of the year to which each delivery date belongs. When the delivery company receives a delivery instruction from the brewing company, it performs a delivery process so that bottles b stored in a warehouse or the like are sent on the delivery date specified by the brewing company. This allows bottles b to be sent to customers regardless of whether the specified delivery date is any day between January 1st and December 31st.

[0032] <Customer terminal> Next, the detailed configuration of the customer terminal 10 will be described.

[0033] As shown in FIG. 2, the customer terminal 10 includes a communication unit 11, a storage unit 12, an input interface 13, an output interface 14, and a control unit 15.

[0034] The communication unit 11 is an interface that enables the customer terminal 10 to transmit and receive information to and from external devices such as the brewing company server 20. There are no particular limitations on the communication method and standard used by the communication unit 11.

[0035] Memory unit 12 is a storage device that stores various information. For example, memory unit 12 stores programs executed by control unit 15 and information received from brewing company server 20. Memory unit 12 is composed of semiconductor memory, a hard disk drive, an optical disk, etc.

[0036] The input interface 13 is an interface that accepts input operations from a customer, converts the accepted input operations into electrical signals, and outputs the electrical signals to the control unit 15. The input interface 13 is, for example, composed of a touch panel, a mouse, a keyboard, a trackball, and buttons. Note that, when the input interface 13 is a touch panel, the input interface 13 may also serve as the output interface 14.

[0037] The output interface 14 is an interface for presenting various information to the customer, and outputs a screen generated by the display control unit 153, a GUI (Graphical User Interface) for receiving input operations from the customer, etc. The output interface 14 is formed, for example, of a liquid crystal display, an organic EL display, a CRT (Cathode Ray Tube) display, or a plasma display.

[0038] The control unit 15 is a processor that controls the overall operation of the customer terminal 10. As shown in FIG.

[0039] Each part of the control unit 15 is stored in the storage unit 12 in the form of a program executable by a computer. In other words, the control unit 15 realizes the functions of the information receiving unit 151, the information output unit 152, and the display control unit 153 by reading and executing the program from the storage unit 12.

[0040] In addition, the control unit 15 in this embodiment realizes the functions of the information receiving unit 151, the information output unit 152, and the display control unit 153 using a single processor, but is not limited to this, and the control unit 15 may be configured to realize these functions using a combination of multiple independent processors.

[0041] Each part of the control unit 15 will be described in detail below.

[0042] The information receiving unit 151 receives information input by a customer via the input interface 13. Specifically, the information receiving unit 151 receives customer request information from the customer. The customer request information received from the customer includes multiple delivery dates, delivery destinations (delivery addresses), and the like.

[0043] The information output unit 152 outputs the customer request information accepted by the information accepting unit 151 to the brewing company server 20 via the communication unit 11.

[0044] The display control unit 153 controls the output interface 14 so that various information is displayed on the output interface 14. For example, the display control unit 153 generates an input screen for customer request information and displays it on the output interface 14.

[0045] <Brewing company server> Next, the brewing company server 20 will be described.

[0046] As shown in FIG. 3, the brewing company server 20 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0047] The communication unit 21 is an interface through which the brewing company server 20 transmits and receives information to and from external devices such as the customer terminal 10 and the delivery company server 30. There are no particular limitations on the communication method and standard used by the communication unit 21.

[0048] The storage unit 22 is a storage device that stores various information. For example, the storage unit 22 stores a program executed by the control unit 23 and information received from the customer terminal 10. The storage unit 22 is composed of a semiconductor memory, a hard disk drive, an optical disk, etc.

[0049] The storage unit 22 also stores a customer information database DB. FIG. 4 shows an example of the customer information database DB. As shown in FIG. 4, a plurality of pieces of customer request information are registered in the customer information database DB. In the example shown in FIG. 4, for each customer ID, a customer name, purchased raw liquor information (such as the type of raw liquor and the year brewing began), purchase date, a plurality of delivery dates, and a delivery address are registered. In this embodiment, the plurality of delivery dates are the first delivery date, the delivery dates of the first to fifth samples, and the delivery date of the actual product. Note that the customer request information stored in the customer information database DB may further include purchasing information such as the customer's contact information (telephone number, email address, etc.), the product name (brand name) of the purchased product, and the purchase price, as well as information regarding payment methods such as credit card information (card number, expiration date, etc.) and account transfer information (information on the debit account).

[0050] Note that, if information such as customer name, delivery address, contact details, etc. can be obtained from another database, this information does not need to be included in the customer information database DB. For example, if a database is created in which customer names, delivery addresses, contact details, etc. are registered when a customer creates an account to log in to a product application site, the customer information database DB does not need to include this information, and this information may be obtained via a customer ID, etc.

[0051] Control unit 23 is a processor that controls the overall operation of brewing company server 20. As shown in Fig. 3, control unit 23 includes an information acquisition unit 231, a database registration unit 232, a timing determination unit 233, and an information output unit 234.

[0052] Each part of control unit 23 is stored in storage unit 22 in the form of a program executable by a computer. In other words, control unit 23 realizes the functions of information acquisition unit 231, database registration unit 232, timing determination unit 233, and information output unit 234 by reading and executing the program from storage unit 22.

[0053] In addition, the control unit 23 in this embodiment realizes the functions of the information acquisition unit 231, the database registration unit 232, the timing determination unit 233 and the information output unit 234 using a single processor, but is not limited to this, and the control unit 23 may be configured to realize these functions using a combination of multiple independent processors.

[0054] Each part of the control unit 23 will be described in detail below.

[0055] The information acquisition unit 231 acquires information via the communication unit 21. Specifically, the information acquisition unit 231 acquires, via the communication unit 21, customer request information output by the information output unit 152 of the customer terminal 10.

[0056] The database registration unit 232 registers the customer request information acquired by the information acquisition unit 231 in the customer information database DB of the storage unit 22 .

[0057] The timing determination unit 233 determines whether or not the timing to perform processing related to the delivery of the product has arrived. Specifically, the timing determination unit 233 determines whether or not the timing has arrived before the delivery preparation period (first period) from each delivery date based on the customer information database DB. The first period is, for example, a period required for the delivery company to complete delivery of the product to the customer after delivery information is sent to the delivery company server 30, and is, specifically, for example, 10 days. In the case where the first period is 10 days, when the current date is 10 days before the delivery date, the timing determination unit 233 determines that the timing has arrived. Note that the first period may be, for example, the number of days from the first day of the month preceding the month to which the delivery date belongs to until the delivery date. In this case, when the current date is the first day of the month preceding the month to which the delivery date belongs, the timing determination unit 233 determines that the timing has arrived. As another example, the timing determination unit 233 may determine that the timing has arrived based on the year and month (year and month) to which the delivery date belongs and the current year and month, instead of the date (year, month, and day) of the delivery date.

[0058] When the above-mentioned timing arrives, the information output unit 234 outputs delivery information for sending the product on the delivery date. In detail, when the timing determination unit 233 determines that the timing has arrived, the information output unit 234 generates delivery information based on the customer request information contained in the customer information database DB, and outputs it to the delivery company server 30. The delivery information is information necessary for the delivery company to deliver the product, and includes at least the purchased raw liquor information, the delivery date, and the name and address of the delivery destination among the customer request information. Note that the delivery information may include information for identifying the bottle b to be sent from the bottles b stored in the delivery company's warehouse or the like, instead of the purchased raw liquor information.

[0059] In this embodiment, the information output unit 234 outputs delivery information for sending a matured product (full product) if the delivery date is the final delivery date, and outputs delivery information for sending a product in the middle of maturation (sample) if the delivery date is not the final delivery date. Specifically, the delivery information in this embodiment includes information indicating whether it is a sample or a full product (product type).

[0060] <Product provision processing> Next, an example of the product provision process according to the first embodiment will be specifically described with reference to the sequence diagram of FIG. 5, and FIGS.

[0061] In this embodiment, as an example, a case will be described in which a customer purchases whiskey in the year of the birth of his / her child, and receives the products (samples and the actual product) in accordance with various events that mark turning points in the child's development.

[0062] It should be noted that the sequence diagram of FIG. 5 starts on the assumption that the customer has already accessed the brewing company server 20 by operating the customer terminal 10 (eg, has logged in to the customer page).

[0063] First, the customer terminal 10 displays a screen for inputting customer request information (step S11). In detail, the display control unit 153 of the customer terminal 10 acquires information from the brewing company server 20 via the communication unit 11, generates a screen for inputting customer request information, and displays it on the output interface 14.

[0064] Fig. 6 is a diagram showing an example of a customer request information input screen according to this embodiment. As shown in Fig. 6, the customer request information input screen displays the following items: purchased raw liquor, purchase date, first delivery date, first sample delivery date, second sample delivery date, ..., fifth sample delivery date, product delivery date, and shipping address. The customer request information input screen also displays fields Y, M, and D, a field NM, a button B1, and the like for displaying or inputting information in each item.

[0065] Each item is explained in detail below.

[0066] "Purchased raw liquor" indicates information about the purchased raw liquor of the product purchased by the customer. In the example of FIG. 6, the field NM displays "2023 raw liquor," indicating that the product purchased by the customer is whiskey that will begin brewing (or will begin brewing) in 2023. The field NM may further display the type of raw liquor, the product name (brand name), etc.

[0067] "Purchase date" indicates the date on which the customer purchases the product. In the example of Figure 6, "2023" is displayed in purchase date field Y, "3" in field M, and "3" in field D, indicating that the date on which the customer will purchase the whiskey is March 3, 2023.

[0068] "First delivery date" indicates the delivery date of the first sample. In the example of Fig. 6, "2023" is entered in the first delivery date field Y, "5" in the field M, and "5" in the field D, indicating that the first sample delivery date is May 5, 2023 (Children's Day).

[0069] "1st sample delivery date" to "5th sample delivery date" represent the delivery dates of the 1st to 5th samples, respectively. Regarding the 1st sample delivery date, "2026" is entered in field Y, "11" is entered in field M, and "15" is entered in field D, which indicates that the delivery date of the 1st sample is November 15, 2026 (Shichi-Go-San).

[0070] Similarly, the delivery dates for the second to fifth samples are April 8, 2030 (elementary school entrance ceremony), January 15, 2033 (half coming of age ceremony), April 8, 2036 (junior high school entrance ceremony), and April 8, 2039 (high school entrance ceremony), respectively.

[0071] "Product delivery date" indicates the delivery date of the product. In this embodiment, the product delivery date is the final delivery date. In the example of FIG. 6, "2043" is entered in field Y of the product delivery date, "1" is entered in field M, and "15" is entered in field D, indicating that the product delivery date is January 15, 2043 (Coming of Age Day).

[0072] In this way, customers can receive products (samples and the actual product) in time for various events that mark milestones in their children's development. In the example of Figure 6, the first sample is received on Children's Day in the year the child was born, the first to fifth samples are received on the dates of the child's Shichigosan festival, elementary school entrance ceremony, half coming of age ceremony, junior high school entrance ceremony, and high school entrance ceremony, respectively, and the actual product is received on the date of the child's coming of age ceremony.

[0073] The customer can arbitrarily specify the value of field M and the value of field D for each delivery date. For example, the customer can receive the sample and the product on a specific anniversary (for example, a family member or friend's birthday, a wedding anniversary, the date of purchase of a home, or the anniversary of the founding of a company) by specifying the same month and day for all delivery dates.

[0074] "Shipping address" indicates the address to which the customer wishes the samples and the product to be sent. The shipping address may be the customer's own address, or in the case of gifts, an address other than the customer's address may be entered.

[0075] In addition, the customer request information input screen may further display items other than those mentioned above, such as customer ID, customer name, delivery address, contact information (customer email address, phone number, etc.), purchase information, and payment information.

[0076] Next, as shown in Fig. 5, the customer terminal 10 determines whether or not the registration button has been pressed (step S12). More specifically, the information output unit 152 of the customer terminal 10 determines whether or not the customer has pressed (tapped, clicked, etc.) the button B1 in Fig. 6 via the input interface 13.

[0077] If it is determined that the registration button has been pressed (step S12: Yes), the customer terminal 10 transmits the customer request information to the server (step S13). More specifically, the information output unit 152 of the customer terminal 10 generates customer request information based on the information entered on the input screen, and transmits it to the brewing company server 20 via the communication unit 11.

[0078] On the other hand, if it is not determined that the registration button has been pressed (step S12: No), the customer terminal 10 waits until the registration button is pressed.

[0079] Next, the brewing company server 20 acquires the customer request information from the customer terminal 10 and registers it in the database (step S21). More specifically, first, the information acquisition unit 231 of the brewing company server 20 acquires the customer request information from the customer terminal 10 via the communication unit 21. Thereafter, the database registration unit 232 of the brewing company server 20 registers the customer request information in the customer information database DB of the storage unit 22.

[0080] Next, brewing company server 20 determines whether the timing for performing processing related to product delivery has arrived (step S22). More specifically, timing determination unit 233 of brewing company server 20 determines whether the timing has arrived a first period before the delivery date included in the customer request information registered in customer information database DB. For example, timing determination unit 233 determines whether the timing has arrived or passed a first period before the first delivery date based on the current date and the first delivery date.

[0081] If it is determined that the timing has arrived (step S22: Yes), the brewing company server 20 generates delivery information and transmits it to the delivery company server 30 (step S23). More specifically, first, the information output unit 234 of the brewing company server 20 generates delivery information based on the customer request information of the customer registered in the customer information database DB. FIG. 7 is a diagram showing an example of delivery information. As shown in FIG. 7, the delivery information includes the product type (here, the first sample of 2023 raw sake), delivery date, delivery destination name (here, the customer name), and delivery address. The delivery information may also include the customer's telephone number. Based on this delivery information, the delivery company delivers the first sample of the 2023 raw sake to the specified delivery address on the specified delivery date, with the delivery destination name as the addressee.

[0082] On the other hand, if it is not determined that the timing has arrived (step S22: No), the brewing company server 20 waits until the timing arrives.

[0083] 5, the delivery company server 30 acquires delivery information and performs delivery processing (step S31). In this embodiment, as described above, the sample or the bottle b of the product is sent to the warehouse of the delivery company, and each time the delivery company acquires delivery information, the delivery processing of the sample or the product is performed, and the sample or the bottle b of the product is sent to the customer.

[0084] The above-mentioned steps S22 to S31 are repeated for the number of delivery dates. In this embodiment, the initial delivery date, first sample delivery date, second sample delivery date, third sample delivery date, fourth sample delivery date, fifth sample delivery date, and product delivery date are set as the delivery dates, so steps S22 to S31 are repeated for each of these delivery dates.

[0085] By following the above steps, products that mature over time can be delivered to customers on multiple delivery dates with different degrees of maturity.

[0086] In this embodiment, the value of the field Y for each delivery date on the input screen of FIG. 6 is automatically input based on the purchased raw liquor and the purchase date, and the customer cannot specify a value different from the automatically input value. This allows the brewing company to easily manage the production (bottling) of the first sample and the first to fifth samples. In the case of the delivery date set on the screen of FIG. 6, for example, the first sample is produced (bottled) at the end of 2025, the second sample is produced at the end of 2029, ..., the fifth sample is produced at the end of 2038. Note that the value of the field Y that is automatically input is not limited to the above-mentioned value and is arbitrary.

[0087] In addition, in the input screen of FIG. 6, the value of the field Y for each delivery date may be specified by the customer. For example, if the amount of raw liquor is sufficient, by producing sufficient samples including surpluses, the customer can receive samples at any time. In such a case, the customer can also place an additional order for samples and the product.

[0088] 6, the time interval between the first sample delivery date (first delivery date) and the product delivery date (last delivery date) is 20 years, but the time interval between the first delivery date and the last delivery date may be other than 20 years. If the product is whiskey, the time interval between the first delivery date and the last delivery date may be, for example, 10 years or more and 25 years or less.

[0089] In the example of Fig. 6, a total of six sample delivery dates are set, including the first sample delivery date and the first to fifth sample delivery dates, but the number of sample delivery dates is not limited to this and may be any number. Also, the first sample delivery date does not have to be set.

[0090] In addition, the number of delivery dates for the Product is not limited to one, but may be multiple.

[0091] As described above, the product provision system 1 according to this embodiment includes an information receiving unit 151 that receives customer request information including multiple delivery dates and delivery destinations from customers, a database registration unit 232 that registers the customer request information in the customer information database DB, a timing determination unit 233 that determines whether the timing before the delivery preparation period (first period) from the delivery date has arrived based on the customer information database DB, and an information output unit 234 that outputs delivery information for sending the product to the delivery destination on the delivery date when the timing has arrived. This makes it possible to continuously provide customers with products whose state changes due to aging.

[0092] As a result, for example, it is possible to provide a special product that has grown with the customer's life with a high level of satisfaction. That is, as in the above embodiment, by specifying multiple delivery dates on the dates of various events that are turning points in a child's growth, the customer can experience the growth of the child and be provided with a memorable experience. This allows the customer to enjoy the growth of the child and the maturation (aging) of the product (whisky) even more.

[0093] The amount of whiskey bottled in the sample may be less than the amount bottled in the actual product, which increases customer anticipation of the arrival of the actual product and improves customer satisfaction with the arrival of the sample.

[0094] Second embodiment A product provision system according to the second embodiment will be described with reference to Fig. 8. Fig. 8 is a functional block diagram of a brewing company server 20A according to the present embodiment. The customer terminal 10 and the delivery company server 30 are the same as those in the first embodiment.

[0095] One of the differences between this embodiment and the first embodiment described above is that changes to customer request information are accepted before the product is sent on the delivery date. In the following, the present embodiment will be described focusing on the differences with the first embodiment, and descriptions of common parts will be omitted as appropriate.

[0096] As shown in Fig. 8, the control unit 23A of the brewing company server 20A according to this embodiment includes the components related to the control unit 23 of the brewing company server 20 according to the first embodiment, and further includes a customer request information change unit 235. The customer request information change unit 235 accepts changes to the customer request information from the customer. For example, the customer request information change unit 235 accepts changes to the shipping address and / or delivery date included in the customer request information.

[0097] <Product provision processing> The product provision process according to the second embodiment will be described with reference to the sequence diagram of FIG. 9 and the screen examples of FIG. 10 and FIG.

[0098] 9 starts on the assumption that the customer has already accessed the brewing company server 20A (e.g., logged in to the customer page) by operating the customer terminal 10. This customer terminal 10 may be the same device as the customer terminal into which the customer inputs the customer request information, or it may be a different device.

[0099] First, the customer terminal 10 displays a change screen (step S11A). In detail, the display control unit 153 of the customer terminal 10 acquires information from the brewing company server 20A via the communication unit 11, generates a change screen for changing the customer request information, and displays it on the output interface 14.

[0100] Fig. 10 is a diagram showing an example of a screen for changing customer request information according to this embodiment. As shown in Fig. 10, the screen for changing customer request information displays items including purchased raw liquor, purchase date, first delivery date, first sample delivery date, second sample delivery date, ..., fifth sample delivery date, product delivery date, and shipping address, as well as fields Y, M, D, and AD for each item.

[0101] Furthermore, the screen for changing customer request information displays buttons B2 and B3 for changing the contents of each item. In detail, button B2 is a button for changing the first delivery date, first sample delivery date, second sample delivery date, ..., fifth sample delivery date, and product delivery date, and button B2 is a button for changing the shipping address.

[0102] The following describes an example where a customer changes the delivery date of the first sample.

[0103] When the customer presses button B2 corresponding to "First sample delivery date" via input interface 13 on the change screen shown in Fig. 10, a change screen for customer request information shown in Fig. 11 is displayed. On the screen shown in Fig. 11, a new button B4 is displayed next to button B2 for first sample delivery date, and fields M and D for first sample delivery date are left blank. The customer inputs new values ​​(dates) into fields M and D for first sample delivery date, which are now blank.

[0104] Next, as shown in Fig. 9, the customer terminal 10 judges whether or not the registration button has been pressed (step S12A). More specifically, the information output unit 152 of the customer terminal 10 judges whether or not the customer has pressed the button B4 for the first sample delivery date on the screen shown in Fig. 11.

[0105] If it is determined that the registration button has been pressed (step S12A: Yes), the customer terminal 10 transmits the change information to the brewing company server 20A (step S13A). More specifically, the information output unit 152 of the customer terminal 10 transmits the change information to the brewing company server 20A via the communication unit 11. The change information transmitted to the brewing company server 20A may be the entire changed customer request information, or only the changed part of the customer request information.

[0106] On the other hand, if it is not determined that the registration button has been pressed (step S12A: No), the customer terminal 10 waits until the registration button is pressed.

[0107] Next, the brewing company server 20A acquires the change information from the customer terminal 10 and updates the database (step S21A). More specifically, first, the information acquisition unit 231 of the brewing company server 20A acquires the change information from the customer terminal 10 via the communication unit 21. Thereafter, the customer request information change unit 235 of the brewing company server 20A updates the customer information database DB in the storage unit 22 based on the change information.

[0108] Next, brewing company server 20A determines whether the changed timing has arrived (step S22A). More specifically, timing determination unit 233 of brewing company server 20A determines whether the timing has arrived before the delivery preparation period (first period) from the delivery date included in the customer request information registered in the updated customer information database DB.

[0109] If it is determined that the changed timing has arrived (step S22A: Yes), brewing company server 20A generates delivery information and transmits it to delivery company server 30 (step S23). The process after step S23 is the same as in the first embodiment described above, and therefore the description will be omitted.

[0110] On the other hand, if it is not determined that the changed timing has arrived (step S22A: No), the brewing company server 20A waits until the timing arrives.

[0111] The above explanation has been about changing the delivery date of the first sample, but the same applies to changing other delivery dates. Note that the period during which each delivery date can be changed may be limited to before the delivery process of the sample or the Product begins (for example, from the delivery date to before the first period).

[0112] As described above, the brewing company server 20A of the product provision system according to the second embodiment further includes a customer request information change unit 235 that accepts changes to customer request information. This allows a customer to change their delivery address when their delivery address has changed due to moving, etc., or to change the delivery date when the month and / or day of an event has changed.

[0113] The customer request information change unit 235 may be able to change other items. For example, the customer request information change unit 235 may be able to change the aging period, that is, the year to which the delivery date of the product belongs.

[0114] As another example, the customer request information change unit 235 may be able to change the amount of each sample or the number of times the samples are sent. In addition, when the total amount of whiskey contained in the sample and the product is fixed, the customer request information change unit 235 may be able to change the amount of each sample and / or the number of samples within the total fixed amount.

[0115] (Third embodiment) A product provision system according to the third embodiment will be described with reference to Fig. 12. Fig. 12 is a functional block diagram of a brewing company server 20B according to this embodiment. The customer terminal 10 and the delivery company server 30 are the same as those in the first embodiment.

[0116] One of the differences between this embodiment and the first embodiment described above is that the delivery date and delivery address are notified to the customer before the product is delivered. The following describes this embodiment, focusing on the differences with the first embodiment, and omitting descriptions of the common parts as appropriate.

[0117] As shown in FIG. 12, the control unit 23B of the brewing company server 20B according to this embodiment further includes a confirmation unit 236 in addition to the configuration related to the control unit 23 of the brewing company server 20 according to the first embodiment. The confirmation unit 236 outputs a confirmation message to the customer to notify them of the delivery date and delivery address included in the customer request information a confirmation period (second period) before the delivery date. The second period is a period longer than the delivery preparation period (first period) and is a period for setting a reference date for reminding the customer. The confirmation message is specifically an email, a chat, or the like.

[0118] <Product provision processing> A product provision process according to the third embodiment will be described with reference to the sequence diagram of FIG. 13 and FIG.

[0119] Steps S11 to S21 are similar to those in the first embodiment described above, and therefore the description thereof will be omitted.

[0120] Next, the brewing company server 20B judges whether the reminder reference date has arrived (step S24). More specifically, the confirmation unit 236 of the brewing company server 20B outputs a confirmation message to notify the customer of the delivery date and delivery address included in the customer request information before a confirmation period (second period) longer than the delivery preparation period (first period) from the delivery date (i.e., the reminder reference date). The output confirmation message is transmitted to the customer terminal 10 by the communication unit 21.

[0121] The customer terminal 10 then receives and displays the confirmation message from the brewing company server 20B (step S14). More specifically, the display control unit 153 of the customer terminal 10 receives the confirmation message via the communication unit 11 and displays it on the output interface 14.

[0122] FIG. 14 shows an example of a confirmation message according to this embodiment. The example in FIG. 14 is a confirmation message that is output before the confirmation period from the delivery date of the first sample. As shown in FIG. 14, the confirmation message MS1 includes the customer name (AA), a message indicating that the first sample is scheduled to be delivered, the delivery date, and the delivery address. This allows the customer to know that the first sample is scheduled to be delivered to the address listed in the confirmation message MS1 on November 5, 2026, which is the delivery date.

[0123] As shown in FIG. 14, the confirmation message MS1 may include a contact means (here, a URL) for contacting the brewing company server 20B when there is a change in the delivery address included in the customer request information. In the example of FIG. 14, the text "If you wish to change the delivery date or delivery address, please change it from My Page" and a URL are described. When this URL is clicked, the change process of the second embodiment described above may be performed. That is, the control unit 23B of the brewing company server 20B may further include a customer request information change unit 235, and the process of steps S11A to S21A in FIG. 9 may be performed. Note that the contact means is not limited to a URL, and may be an email address, a telephone number, or the like. Also, when the customer's payment method is a credit card and the expiration date has passed, a description to that effect and a request to update the credit card information may be added to the confirmation message MS1.

[0124] Next, the brewing company server 20B determines whether or not it is time to perform a process related to the delivery of the product (step S22). The process after step S22 is the same as that of the first embodiment described above, and therefore the description will be omitted.

[0125] In this embodiment, it is determined that the timing has arrived after a predetermined period of time (the period obtained by subtracting the delivery preparation period from the confirmation message MS1) has elapsed since the confirmation message MS1 was sent. Therefore, for example, it is desirable that the predetermined period of time be a period that allows the customer to confirm the confirmation message MS1 and, if there are any changes, to transmit such changes to the brewing company server 20B. As a specific example, the period from the delivery date to the confirmation period is the 10th of the month preceding the month to which the delivery date belongs.

[0126] As described above, the product provision system according to the third embodiment includes a confirmation unit 236 that outputs a confirmation message to the customer terminal 10 to notify the customer of the delivery date and delivery address included in the customer request information before the delivery date and before the confirmation period (second period) that is longer than the delivery preparation period (first period) (i.e., the reminder reference date). This allows the customer to check whether the delivery date and delivery address are appropriate before the product is delivered. As a result, even if the delivery address changes due to moving or the customer forgets about the service itself, it is possible to reduce the risk that the product cannot be delivered to the delivery address.

[0127] Furthermore, if the customer's telephone number is registered in the customer information database DB, even if the delivery address has changed and delivery is undeliverable, a call can be made to inquire about the current address and this can be reflected in the customer request information, allowing for redelivery.

[0128] (Modification 1 of the third embodiment) A product provision system according to a first modified example of the third embodiment will be described with reference to FIG.

[0129] In the third embodiment described above, when a predetermined period of time (the second period minus the first period) has elapsed since the sending of the confirmation message MS1, it is determined that the time has come, and the customer sends a notification to the brewing company server 20B only if there is a change in the delivery date and / or delivery address.

[0130] In this modification, the timing determination unit 253 determines that the timing has arrived only when the customer terminal 10 transmits a response to the confirmation message to the brewing company server 20B. To achieve this, the confirmation message according to this modification includes a contact means (here, a URL) for transmitting the destination confirmation information.

[0131] Fig. 15 is a diagram showing an example of a confirmation message MS2 according to this modified example. As shown in Fig. 15, the confirmation message MS2 contains the customer name, a message indicating that the first sample is to be delivered, the delivery date, and the delivery address, as well as the sentences "(1) If there are no changes in the delivery date or delivery address, please access the URL below" and "(2) If there are changes in the delivery date or delivery address, please access the URL below," along with URL1 and URL2 associated with each sentence.

[0132] If there is no change in the delivery date or delivery address, the customer accesses URL1 to send the delivery destination confirmed information to the brewing company server 20B. The timing determination unit 253 determines whether the delivery destination confirmed information has been sent, and determines that the timing has arrived only when it is determined that the delivery destination confirmed information has been sent. On the other hand, if there is a change, the customer accesses URL2 to send to the brewing company server 20B a notice that there is a change in the customer request information and the delivery destination confirmed information. Note that when URL2 is clicked, the change process of the second embodiment described above may be performed, as in the case of the confirmation message MS1. That is, the control unit 23B of the brewing company server 20B may further include a customer request information change unit 235, and the processes of steps S11A to S21A in FIG. 9 may be performed.

[0133] According to the product provision system 1 of this modified example, the customer's intention can be grasped more reliably, and delivery to an incorrect delivery address can be prevented.

[0134] (Modification 2 of the third embodiment) A product provision system according to a second modification of the third embodiment will be described below.

[0135] In this modification, information that allows the customer to grasp the state of the product is presented to the customer together with the confirmation message MS1 in the third embodiment described above. For example, a barrel B filled with the purchased whiskey, a bottle b sent to a delivery company, or a photograph of samples from each year poured into glasses and arranged side by side, a graph showing the transition of ingredients, etc. are sent to the customer terminal 10 together with the confirmation message MS1. This allows the change in the state of the product to be shared with the customer, increasing the customer's expectations for the product.

[0136] The timing of presenting the customer with information that allows the customer to understand the product status is not limited to the timing of sending confirmation message MS1, and is arbitrary. The manner in which the information is presented to the customer is also arbitrary. For example, a postcard or the like may be sent to the delivery address at the beginning of each year from the year following the year in which the customer purchases the product until the year in which the product is delivered. In this case, brewing company server 20B may output delivery information for sending the postcard or the like to delivery company server 30 or a post office server, etc.

[0137] In each of the above-mentioned embodiments, the product is not limited to whiskey, and may be an alcoholic beverage such as brandy, wine, sake, Shaoxing wine, shochu, awamori, beer, plum wine, fruit wine, gin, or rum. As another example, the product may be a non-alcoholic beverage such as non-alcoholic beer. As yet another example, the product may be a fermented food such as cheese, pickled plum, pickles, miso, or canned fish, or a processed food such as ham, sausage, or aged meat. The product is preferably one that adds value by aging, and is not limited to a specific food or beverage.

[0138] In addition, in the case of products such as whiskey that do not age while bottled, multiple initial samples may be bottled for one customer, and the initial samples may be sent together with the samples of the corresponding batch on each sample delivery date other than the delivery date of the initial sample. This allows the customer to directly compare the initial sample (before aging) with the sample of the corresponding batch, allowing the customer to easily recognize the degree of maturation of the product they ordered, and increasing the satisfaction that comes with aging (for example, the satisfaction of seeing a child grow up) and the customer's expectations for the product.

[0139] In addition, products may be made available for ordering going back a certain period of time (for example, three years). For example, it may be possible to purchase 2023 vintage malt spirits in 2025.

[0140] Furthermore, the configuration of the product provision system is not limited to that shown in Fig. 1. For example, the brewing company server 20 and the delivery company server 30 may belong to the same company. In this case, a single server device may realize the functions of both the brewing company server 20 and the delivery company server 30.

[0141] Based on the above description, a person skilled in the art may be able to conceive additional effects and various modifications of the present invention, but the aspects of the present invention are not limited to the individual embodiments described above. Elements of different embodiments may be appropriately combined. Various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and intent of the present invention derived from the contents defined in the claims and their equivalents.

[0142] 2 and 3 are merely examples, and at least some of the components of brewing company server 20 may be located within customer terminal 10. For example, at least a portion of memory unit 22 and at least a portion of control unit 23 in brewing company server 20 may be provided within customer terminal 10.

[0143] At least a part of the product providing system 1 described in the above embodiment may be configured with hardware or software. When configured with software, a program that realizes at least a part of the functions of the product providing system 1 may be stored in a recording medium such as a flexible disk or a CD-ROM, and may be read and executed by a computer. The recording medium is not limited to removable ones such as a magnetic disk or an optical disk, and may be a fixed recording medium such as a hard disk device or a memory.

[0144] In addition, a program that realizes at least a part of the functions of the product providing system 1 may be distributed via a communication line (including wireless communication) such as the Internet. Furthermore, the program may be encrypted, modulated, or compressed and distributed via a wired line or wireless line such as the Internet, or stored in a recording medium. [Explanation of symbols]

[0145] 1 Product provision system 10 Customer terminal 11 Communications Department 12 Storage section 13 Input Interface 14 Output Interface 15 Control section 151 Information Reception Department 152 Information output section 153 Display control section 20, 20A, 20B Brewery Server 21 Communications Department 22 Memory section 23, 23A, 23B Control section 231 Information Acquisition Department 232 Database Registration Department 233 Timing Judgment Unit 234 Information Output Section 235 Customer Request Information Change Department 236 Verification Department 30 Delivery company server DB Customer information database DI Shipping Information MS1, MS2 confirmation message NM,Y,M,D,AD Fields NW Communication network

Claims

1. A product provision system for delivering a product that matures over time to a destination on a plurality of delivery dates with different maturity levels, an information receiving unit that receives customer request information including the plurality of delivery dates and the delivery destination; a database registration unit that registers the customer request information in a customer information database; a timing determination unit that determines, for each of the delivery dates, whether or not a timing that is a first period before the delivery date has arrived based on the customer information database; an information output unit that outputs delivery information for sending the product to the destination on the delivery date when the timing arrives; A product provision system comprising:

2. The product providing system according to claim 1 , further comprising a customer request information changing unit that accepts changes to the customer request information.

3. The product providing system according to claim 2 , wherein the customer request information changing unit accepts changes to the delivery date.

4. The product delivery system according to claim 1, further comprising a confirmation unit that outputs a confirmation message for confirming the shipping destination and / or the delivery date included in the customer request information before a second period from the delivery date that is longer than the first period.

5. The product delivery system of claim 1, wherein the information output unit outputs delivery information for sending the aged product if the delivery date is the final delivery date among the multiple delivery dates, and outputs delivery information for sending the product that is in the process of aging if the delivery date is not the final delivery date among the multiple delivery dates.

6. 6. The product provision system according to claim 1, wherein the product is an alcoholic beverage, a non-alcoholic beverage, cheese, pickled plum, pickles, miso, canned fish, ham, sausage or aged meat.

7. The product provision system according to claim 6 , wherein the alcoholic beverage is whiskey, brandy, wine, sake, Shaoxing wine, shochu, awamori, beer, plum wine, fruit wine, gin or rum.

8. A method for providing a product for delivering a product that matures over time to a destination on a plurality of delivery dates with different degrees of maturity, comprising: receiving customer request information including the plurality of delivery dates and the delivery destination; registering the customer request information in a customer information database; determining whether or not a timing before a first period from the delivery date has arrived for each of the delivery dates based on the customer information database; When the timing arrives, outputting delivery information for sending the product to the destination on the delivery date; The method for providing a product includes the steps of:

9. A product provision program for delivering a product that matures over time to a destination on multiple delivery dates with different maturity levels, Computer, an information receiving unit that receives customer request information including the plurality of delivery dates and the delivery destination; a database registration unit that registers the customer request information in a customer information database; a timing determination unit that determines, for each of the delivery dates, whether or not a timing that is a first period before the delivery date has arrived based on the customer information database; and an information output unit that outputs delivery information for sending the product to the destination on the delivery date when the timing arrives; A product provision program executed as a

Images