Delivery management system, delivery management method, and program

Abstract

To provide a delivery management system capable of improving the convenience of a customer using periodical delivery of an article.SOLUTION: According to the present disclosure, a delivery management system includes a customer identification unit for identifying a customer on the basis of customer identification information presented by a store in the case where a customer using periodical delivery of articles purchases the article in the store, and a delivery management unit for managing the periodical delivery to the customer by considering a store purchase amount showing the amount of the articles purchased in the store.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a delivery management system, a delivery management method, and a program. [Background technology]

[0002] A regular delivery service that delivers products such as kerosene to customers' homes on a regular basis is known. As a related technique, Patent Document 1 discloses an oil delivery instruction system that predicts inventory by calculating consumption amounts associated with each oil storage container and enables planned oil delivery. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 11-208794 Summary of the Invention [Problem to be solved by the invention]

[0004] One of the conditions for using regular delivery services is a minimum purchase amount of a product. For example, in the case of a service that delivers kerosene to a customer's home tank on a regular basis, the customer must fill up with more than the minimum amount of fuel stipulated in the contract with the kerosene supplier.

[0005] In many cases, the price of kerosene at stores such as gas stations is cheaper than the price of kerosene in regular deliveries. However, if a customer who uses regular deliveries purchases kerosene at a store, the amount purchased at the store is not counted as a purchase in the regular delivery. Therefore, even if the price of kerosene at a store is cheaper, customers should consider the minimum amount of fuel required for regular deliveries and consider purchasing kerosene at the store.

[0006] In view of the above-mentioned problems, the object of the present disclosure is to provide a delivery management system, a delivery management method, and a program that can improve the convenience of customers who use regular product deliveries. [Means for solving the problem]

[0007] The delivery management system according to the present disclosure includes: a customer identification unit that identifies a customer who uses regular product delivery and purchases a product at a store based on customer identification information presented at the store; and a delivery management unit that manages regular deliveries to the customer, taking into account a store purchase amount that indicates the amount of merchandise purchased at the store.

[0008] The delivery management method according to the present disclosure includes: The computer a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; and a delivery management step of managing regular deliveries to the customer, taking into account a store purchase amount indicating the amount of merchandise purchased at the store.

[0009] The program according to the present disclosure is a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; and a delivery management step of managing regular deliveries to the customer, taking into account a store purchase amount indicating the amount of merchandise purchased at the store. [Effects of the Invention]

[0010] The delivery management system, delivery management method, and program according to the present disclosure can improve convenience for customers who use regular delivery of goods. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating the configuration of a delivery management system according to the present disclosure. [Figure 2]1 is a flowchart illustrating processing performed by a delivery management system according to the present disclosure. [Figure 3] FIG. 1 is a block diagram illustrating the configuration of a delivery management system according to the present disclosure. [Figure 4] FIG. 2 is a diagram illustrating an example of customer information stored in a customer information DB according to the present disclosure. [Figure 5] FIG. 10 is a diagram showing an example of delivery schedule information according to the present disclosure, the delivery schedule information being displayed on the display unit of a customer terminal. [Figure 6] FIG. 10 is a diagram showing an example of a change request display according to the present disclosure, which is displayed together with delivery schedule information. [Figure 7] FIG. 10 is a diagram showing a My Page displayed on the display unit of a customer terminal as an example of a usage status page according to the present disclosure. [Figure 8] FIG. 10 is a sequence diagram showing the processing performed by the delivery management system according to the present disclosure. [Figure 9] FIG. 1 is a block diagram illustrating an example of the hardware configuration of a computer that realizes a delivery management system according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals. For clarity of explanation, duplicated explanations will be omitted as necessary.

[0013] <Embodiment 1> The delivery management system 100 according to the present disclosure will now be described. FIG. 1 is a block diagram showing the configuration of the delivery management system 100.

[0014] (Configuration of delivery management system 100) The delivery management system 100 includes a customer identification unit 101 and a delivery management unit 102. When a customer who uses regular product delivery purchases a product at a store, the customer identification unit 101 identifies the customer based on customer identification information presented at the store.

[0015] A store is a place where a seller of a product sells the product to customers. A store may be a physical store set up in a predetermined location, or may be, for example, a predetermined sales space set up temporarily.

[0016] Customer identification information is information for identifying a customer. For example, customer identification information is a customer's credit card number, membership card number, etc. For example, when a customer makes a payment by credit card at a store, the customer presents the customer identification information by having the credit card information read by a card reader.

[0017] The delivery management unit 102 manages regular deliveries to customers, taking into account the store purchase amount, which indicates the amount of product purchased at the store. For example, if the product is kerosene, the delivery management unit 102 manages the scheduled delivery amount of the product based on the amount of oil obtained by subtracting the amount of kerosene purchased at the store from the preset minimum amount of fuel.

[0018] The delivery management system 100 includes a processor, memory, and storage device (not shown). The storage device stores a computer program that implements the processes described herein. The processor can load the computer program from the storage device into the memory and execute the computer program. This allows the processor to realize the functions of the customer identification unit 101 and the delivery management unit 102.

[0019] The customer identification unit 101 and the delivery management unit 102 may each be realized by dedicated hardware. Some or all of the components may be realized by general-purpose or dedicated circuits, processors, etc., or a combination of these. These may be configured by a single chip, or by multiple chips connected via a bus. Some or all of the components may be realized by a combination of the above-mentioned circuits, etc., and programs.

[0020] (Processing of delivery management system 100) 2 is a flowchart showing the processing performed by the delivery management system 100. Here, it is assumed that a customer purchases a product at a store and submits customer identification information by making a credit card payment.

[0021] First, the customer identification unit 101 acquires the customer identification information and the store purchase amount of the product presented at the store (S1). Next, the customer identification unit 101 identifies the customer based on the acquired customer identification information (S2). Next, the delivery management unit 102 manages regular deliveries to the customer taking into account the store purchase amount (S3).

[0022] As described above, the delivery management system 100 according to the present disclosure manages regular deliveries to customers by taking into account the purchase quantity of products that the customer has purchased at the store. This allows customers to purchase products at the store without considering the minimum purchase quantity set by the regular delivery service. In this way, the delivery management system 100 can improve the convenience of customers who use regular product deliveries.

[0023] <Embodiment 2> Next, a description will be given of embodiment 2. Embodiment 2 is a specific example of embodiment 1 described above.

[0024] (Configuration of delivery management system 10) 3 is a block diagram showing the configuration of a delivery management system 10 according to the present disclosure. The delivery management system 10 includes a weighing machine 1, a POS (Point Of Sales) terminal 2, a DB (DataBase) server 3, a Web server 4, a customer terminal 5, and a management terminal 6. The weighing machine 1 and the POS terminal 2 are installed in a store.

[0025] The weighing machine 1, POS terminal 2, DB server 3, Web server 4, customer terminal 5, and management terminal 6 communicate with each other via a network N. The network N is a wired or wireless communication line. For example, a wireless LAN or an internet line may be used as the network N. The type of communication is not limited.

[0026] The number of components included in the delivery management system 10 is not limited to those shown in the figure. The delivery management system 10 may include multiple weighing machines 1, POS terminals 2, DB servers 3, Web servers 4, customer terminals 5, and management terminals 6.

[0027] First, an overview of the delivery management system 10 will be described. The delivery management system 10 is a system that manages information related to product delivery in a regular product delivery service. Products that are subject to regular delivery include, but are not limited to, fuels such as kerosene, diesel, heavy oil, or gasoline. Products may be various items that can be delivered on a regular schedule or purchased in a store. Products may be, for example, water or groceries. A store refers to a location such as a physical store or sales space where products can be purchased by means other than regular delivery.

[0028] Here, kerosene will be used as an example of a product. Examples of stores that sell kerosene include gas stations and kerosene retailers. Here, an example will be given in which the store is a gas station.

[0029] A customer enters into a contract with a kerosene supplier to use regular delivery. For example, the customer sets the delivery destination, the contracted fuel supply amount for a specified period (e.g., one month), the home tank capacity, and a credit card number in the contract. The customer operates the customer terminal 5 and registers these settings in the DB server 3 via a specified website or application.

[0030] The delivery destination indicates the place where kerosene is to be filled. For example, a customer may set their home tank as the delivery destination. This allows kerosene to be filled into the customer's home tank according to a predetermined delivery schedule. Customers can also fill their home tank with kerosene purchased at a store on a spot basis.

[0031] The contracted fuel supply volume indicates the amount of kerosene to be delivered on a regular basis. The customer sets the contracted fuel supply volume to an amount equal to or greater than the minimum fuel supply volume (minimum purchase amount) for a specified period. The home tank capacity indicates the maximum capacity of the home tank at the delivery destination.

[0032] The credit card number indicates the number of the credit card used to purchase kerosene for regular delivery. The credit card number is an example of customer identification information for identifying the customer. The customer can use the credit card to make payment when purchasing kerosene at the store.

[0033] The kerosene supplier operates the management terminal 6 to set a kerosene delivery schedule on the Web server 4 based on the contracted fuel supply amount, home tank capacity, etc. For example, the supplier sets a kerosene delivery cycle (e.g., once a week).

[0034] Once the customer and supplier have completed the setup, regular deliveries begin. When the kerosene is delivered, the DB server 3 adds the amount of kerosene delivered to the virtual tank remaining amount managed in the customer information DB 32. The virtual tank remaining amount is information that virtually represents the remaining amount in the customer's home tank.

[0035] In addition, when a customer purchases kerosene at a store, DB server 3 identifies the customer based on the credit card number presented at the store, and adds the store fuel volume (store purchase volume), which indicates the amount of kerosene purchased at the store, to the remaining amount in the virtual tank.

[0036] The Web server 4 manages the amount of kerosene to be delivered on a regular basis and the delivery schedule, taking into account the amount of fuel refueled at the store. For example, if the virtual tank is nearly full, the Web server 4 skips or postpones the next delivery. This allows the Web server 4 to shift the scheduled delivery date for regular deliveries depending on the customer's purchase of kerosene at the store. In cases where kerosene usage is high, such as in winter, the Web server 4 can also deliver as scheduled, in response to the customer's request.

[0037] Next, the configurations of the weighing machine 1, the POS terminal 2, the DB server 3, the Web server 4, the customer terminal 5, and the management terminal 6 included in the delivery management system 10 will be described in detail.

[0038] (Weighing machine 1) The metering machine 1 is a device for supplying kerosene. The metering machine 1 is equipped with a fuel supply hose (not shown) equipped with a nozzle for supplying kerosene. A customer sets the nozzle in a plastic container or the like to supply fuel. The metering machine 1 may also be equipped with a display unit that displays the type of fuel and the amount of fuel supplied, an audio output unit that outputs audio information about refueling, and the like.

[0039] The weighing machine 1 also includes a reading unit 11 and a measuring unit 12. The reading unit 11 is a reading device that reads customer identification information that a customer presents when purchasing kerosene. The customer identification information is information for identifying a customer. Examples of customer identification information include a credit card number, an electronic money number, or a customer ID. Here, a credit card number is used as an example of customer identification information.

[0040] The reading unit 11 is, for example, a card reader capable of reading information from a credit card. For example, the reading unit 11 is configured to be able to read information from an IC (Integrated Circuit) chip of a credit card using short-range wireless communication. Alternatively, the reading unit 11 may be configured to be able to read information from a magnetic stripe of a credit card. However, the reading unit 11 is not limited to these, and may be a reading device according to the type of customer identification information. The reading unit 11 transmits the credit card number read from the presented credit card to the POS terminal 2.

[0041] The measuring unit 12 measures the amount of kerosene that has been supplied. The measuring unit 12 transmits the measured amount of kerosene to the POS terminal 2 as the store-supplied amount of kerosene that indicates the amount of kerosene purchased at the store.

[0042] (POS terminal 2) The POS terminal 2 is a device that manages kerosene orders at the store. The POS terminal 2 receives the credit card number and the amount of fuel supplied to the store from the weighing machine 1 and performs accounting. The POS terminal 2 also transmits the credit card number and the amount of fuel supplied to the store to the DB server 3.

[0043] (DB Server 3) The DB server 3 is a device that manages customer information related to customers. The DB server 3 receives the credit card number and the amount of fuel supplied to the store from the POS terminal 2, and updates the customer information based on this information.

[0044] The DB server 3 includes a customer identification unit 31 and a customer information DB 32. The customer identification unit 31 is an example of the customer identification unit 101 described above. When a customer who uses regular kerosene delivery purchases kerosene at a store, the customer identification unit 31 refers to the customer information DB 32 and identifies the customer based on the credit card number presented at the store. The customer information DB 32 is a database that stores customer information. The customer identification unit 31 updates the customer information of the identified customer.

[0045] Fig. 4 is a diagram showing an example of customer information stored in the customer information DB 32. As shown in Fig. 4, the customer information DB 32 stores, for example, a customer ID, a credit card number, a virtual tank remaining amount, and a contracted fuel supply amount in association with each other.

[0046] The customer ID is an ID assigned to a customer. The customer ID may be, for example, a customer number managed by a supplier. The customer ID may be used as customer identification information instead of a credit card number. Instead of a credit card, the customer ID can be used as customer identification information by having the weighing machine 1 read a membership card or point card that stores the customer ID.

[0047] The credit card number is an example of customer identification information. Instead of the credit card number, the above-mentioned customer ID or the like may be used as customer identification information.

[0048] The virtual tank remaining amount is information that virtually represents the remaining amount of kerosene in a customer's home tank. The virtual tank remaining amount may be calculated based on the amount of kerosene purchased and used by each customer. For example, when kerosene is filled into the home tank through regular delivery, the customer identification unit 31 increases the virtual tank remaining amount according to the amount of fuel filled. Furthermore, when kerosene in the home tank is used, the customer identification unit 31 decreases the virtual tank remaining amount according to the amount used. For example, the customer identification unit 31 decreases the virtual tank remaining amount using the amount of usage measured by a sensor installed in the home tank. Alternatively, the customer identification unit 31 may decrease the virtual tank remaining amount using a statistical value (e.g., an average value) calculated from the amount of kerosene used by one or more customers.

[0049] The contracted fuel supply amount indicates the amount of fuel that the customer has contracted to supply. The contracted fuel supply amount is set to be equal to or greater than the minimum fuel supply amount.

[0050] The customer identification unit 31 refers to the customer information DB 32 and checks whether the credit card number received from the POS terminal 2 exists in the customer information DB 32. If the credit card number exists in the customer information DB 32, the customer identification unit 31 identifies the customer.

[0051] The customer identification unit 31 treats the amount of kerosene purchased in a regular delivery as the same as the amount of kerosene purchased at a store. Therefore, the customer identification unit 31 counts the amount of kerosene supplied to the store received from the POS terminal 2 as the amount of kerosene purchased by the identified customer. Specifically, the customer identification unit 31 adds the amount of kerosene supplied to the store to the remaining amount of kerosene in the virtual tank of the identified customer. For example, if the remaining amount of kerosene in the virtual tank before the customer purchased kerosene at the store was 50 L and the amount of kerosene supplied to the store was 10 L, the remaining amount of kerosene in the virtual tank after the purchase would be 60 L, since "50 + 10 = 60". The customer identification unit 31 sends the remaining amount of kerosene in the virtual tank after adding the amount of kerosene supplied to the store to the Web server 4.

[0052] (Web Server 4) Returning to Figure 3, the Web server 4 is a device that manages regular deliveries to customers and provides information about regular deliveries. The Web server 4 also registers customer information in advance in the DB server 3 via a predetermined website, application, or the like. For example, the Web server 4 displays a predetermined input form on the customer terminal 5 and accepts input of the customer's name, contact information, credit card number, and the like from the customer terminal 5. The Web server 4 registers the received information in the customer information DB 32 of the DB server 3. The Web server 4 may also accept input of customer information from the management terminal 6 or another terminal device.

[0053] The web server 4 also includes a delivery management unit 41 and a display control unit 42. The delivery management unit 41 is an example of the delivery management unit 102 described above. The delivery management unit 41 manages regular deliveries to customers, taking into account the store refueling amount, which indicates the amount of kerosene purchased at the store.

[0054] For example, the delivery management unit 41 manages the amount of kerosene to be delivered in regular deliveries. The delivery management unit 41 manages the planned delivery amount of kerosene in regular deliveries based on a preset minimum refueling amount. The minimum refueling amount is set in advance in the contract. The delivery management unit 41 may manage the amount of refueling in each delivery as the planned delivery amount, or may manage the amount of refueling corresponding to multiple deliveries as the planned delivery amount.

[0055] Furthermore, when a customer purchases kerosene at a store, the delivery management unit 41 manages the scheduled delivery amount based on an adjusted minimum refueling amount (adjusted minimum purchase amount) obtained by subtracting the store refueling amount from the minimum refueling amount. In this way, the delivery management unit 41 can manage the scheduled delivery amount by using the adjusted minimum refueling amount obtained by subtracting the store refueling amount from the minimum refueling amount as a new minimum refueling amount. For example, assume that the minimum refueling amount for a specified period is previously set to 100 L. If a customer purchases 10 L of kerosene at a store, the delivery management unit 41 sets 90 L as the adjusted minimum refueling amount using the formula "100 - 10 = 90."

[0056] The delivery management unit 41 may change the preset scheduled delivery amount depending on the amount of fuel supplied to the store. For example, the delivery management unit 41 may reduce the scheduled delivery amount for deliveries scheduled after the purchase date at the store depending on the amount of fuel supplied to the store. The delivery management unit 41 may also adjust the scheduled delivery amount by increasing or decreasing the scheduled delivery amount depending on the usage status of kerosene.

[0057] In addition, the delivery management unit 41 manages the delivery schedule of kerosene for regular deliveries. For example, when a customer purchases kerosene at a store, the delivery management unit 41 changes the delivery schedule based on at least one of the date of purchase of the kerosene and the amount of kerosene supplied to the store.

[0058] For example, the delivery management unit 41 skips any delivery scheduled after the purchase date. For example, the delivery management unit 41 determines whether there is a scheduled delivery date within a predetermined period from the purchase date at the store, and if there is a scheduled delivery date, skips the scheduled delivery. The delivery management unit 41 may determine whether the amount of fuel supplied to the store is equal to or greater than a predetermined amount, and if it is equal to or greater than the predetermined amount, skips the scheduled delivery. The delivery management unit 41 may skip the delivery closest to the purchase date, or may skip multiple deliveries depending on the amount of fuel supplied to the store. By skipping scheduled deliveries, customers can avoid unnecessary refueling. Furthermore, the supplier can reduce delivery costs.

[0059] The delivery management unit 41 may postpone a delivery instead of skipping it. In this case, for example, the delivery management unit 41 may reduce the scheduled delivery amount for the postponed delivery compared to the scheduled delivery amount before the postponement. By doing so, the delivery management unit 41 can, for example, increase the delivery amount to other customers. Furthermore, the delivery management unit 41 may adjust the delivery schedule by increasing the scheduled number of deliveries or bringing forward the scheduled delivery date depending on the kerosene usage situation.

[0060] The delivery management unit 41 may manage a delivery cycle that indicates the period of delivery as a delivery schedule. For example, the delivery management unit 41 may change the delivery cycle based on at least one of the date of purchase of kerosene at the store and the amount of kerosene supplied to the store.

[0061] Furthermore, when a customer requests a change regarding regular delivery, the delivery management unit 41 may change at least one of the planned delivery amount and delivery schedule of kerosene in accordance with the change request. For example, the delivery management unit 41 may accept a change request from a customer via the customer terminal 5 and change the planned delivery date (e.g., postpone), skip a scheduled delivery, or change the planned delivery amount. The delivery management unit 41 may accept a change request from the administrator via the management terminal 6 and change the planned delivery amount and / or delivery schedule of kerosene in accordance with the change request.

[0062] The display control unit 42 displays scheduled delivery information for kerosene in regular delivery on a terminal device. The terminal device may be a customer terminal 5 used by a customer, or a management terminal 6 used by a manager of the regular delivery service. The scheduled delivery information includes, for example, a delivery schedule. The scheduled delivery information may also include a scheduled delivery amount.

[0063] FIG. 5 is a diagram showing an example of delivery schedule information, ie, delivery schedule information 511 displayed on the display unit 51 of the customer terminal 5. As shown in FIG. 5, the delivery schedule information 511 is, for example, an image in which a display indicating the scheduled delivery date is superimposed on an image of a calendar. In the example shown, the delivery schedule information 511 includes a scheduled delivery date icon 511a indicating that it is the scheduled delivery date. This allows the customer to easily understand the scheduled delivery date.

[0064] In the example shown in the figure, the delivery cycle is set to once a week, and the scheduled delivery date is set to every Friday. The scheduled delivery amount per delivery is set to 30 L. The display control unit 42 may display this information related to delivery adjacent to the delivery schedule information 511.

[0065] The display control unit 42 may also cause the terminal device to display a change request display for accepting a change request regarding regular deliveries. For example, the display control unit 42 causes the display unit 51 of the customer terminal 5 to display a change request display. This allows the customer to change the delivery schedule that was set in advance.

[0066] 6 shows an example of a change request display, which is a change request display 512 displayed together with delivery schedule information 511. The change request display 512 is a display that allows the customer to select whether or not to change the scheduled delivery date.

[0067] As shown in FIG. 6, the change request display 512 includes a message such as, for example, "This delivery was skipped because kerosene was refueled on September 5th. Would you like the delivery?" The change request display 512 also includes a "Yes" button and a "No" button for the customer to select whether or not they want the delivery. The customer can select either by pressing the "Yes" button or the "No" button via the input unit 52 of the customer terminal 5.

[0068] If the "Yes" button is pressed, the delivery management unit 41 skips the scheduled delivery date of September 8th. If the "No" button is pressed, the delivery management unit 41 does not skip the delivery on September 8th and manages the delivery so that the delivery is carried out as scheduled.

[0069] 6, delivery schedule information 511 may include a store purchase icon 511b indicating that kerosene was purchased at a store, and a skip icon 511c indicating that delivery was skipped. This allows customers to easily understand their purchase history at the store and any changes to their delivery schedule.

[0070] The display control unit 42 may further display the usage status of regular delivery for each customer on the terminal device. For example, the display control unit 42 causes a usage status page for displaying the usage status of regular delivery for each customer to be displayed on the terminal device via a website, an application, or the like. Specifically, the display control unit 42 causes the usage status page to display the amount of kerosene purchased in regular delivery in association with the amount of kerosene purchased at the store. This allows the customer to understand both the usage status of regular delivery and the kerosene purchase status at the store.

[0071] 7 is a diagram showing, as an example of a usage status page, my page 513 displayed on the display unit 51 of the customer terminal 5. As shown in FIG. 7, my page 513 includes, for example, a refueling status 5131 and a purchase history 5132.

[0072] The fuel supply status 5131 indicates the status of fuel supply at the customer. The fuel supply status 5131 includes a contracted fuel supply amount 5131a, a fuel supply amount 5131b, and a planned delivery amount 5131c. The contracted fuel supply amount 5131a indicates the amount of fuel supplied that is set in advance in the contract between the customer and the supplier. The fuel supply amount 5131b indicates the actual amount of fuel supplied for a specified period set forth in the contract. The planned delivery amount 5131c indicates the remaining amount of fuel supplied for that specified period. Specifically, the planned delivery amount 5131c indicates the difference between the contracted fuel supply amount 5131a and the fuel supply amount 5131b.

[0073] Purchase history 5132 shows the customer's kerosene purchase status. Purchase history 5132 shows the amount of kerosene purchased in regular deliveries in association with the amount of kerosene purchased at stores. By displaying the amount purchased in regular deliveries and the amount purchased at stores separately in purchase history 5132, the customer can easily understand how they are using the kerosene they have purchased.

[0074] 5 to 7 are merely examples, and the display control unit 42 may arbitrarily set the display manner of these. For example, when the scheduled delivery date is changed, the display control unit 42 may color-code the schedule before and after the change so that the customer can intuitively understand the change.

[0075] Furthermore, the display control unit 42 may display the remaining amount of the virtual tank shown in Fig. 4 on My Page 513. This allows the customer to check the remaining amount of the virtual tank via a website, an application, or the like.

[0076] The web server 4 may also include a notification unit (not shown) that notifies the customer about regular deliveries. For example, if a scheduled delivery is skipped, the notification unit notifies the customer via a pre-set email address, application, or the like.

[0077] (Customer terminal 5) Returning to Figure 3, the customer terminal 5 is a terminal device used by a customer. The customer terminal 5 is, for example, a smartphone or a PC. Although Figure 3 shows the customer terminal 5 outside the store, the customer may carry the customer terminal 5 into the store. The customer terminal 5 accesses the web server 4 to obtain information about regular deliveries.

[0078] The customer terminal 5 includes a display unit 51 and an input unit 52. The display unit 51 is a display device that displays information about regular deliveries. The display unit 51 is, for example, a liquid crystal display. The display unit 51 may also be a touch panel or the like that has the function of an input unit that accepts input from the customer.

[0079] For example, the display unit 51 displays scheduled delivery information for kerosene. The scheduled delivery information includes, for example, a delivery cycle, a scheduled delivery date, or a scheduled delivery amount on the scheduled delivery date. In addition to the scheduled delivery information, the display unit 51 may also display various other information related to delivery. For example, the display unit 51 may display the remaining amount in a virtual tank, the details of a regular delivery contract, etc. By looking at the information displayed on the display unit 51, customers can easily understand the status of their regular deliveries.

[0080] The input unit 52 is an input device that accepts input from a customer. The input unit 52 is, for example, a keyboard. The customer uses the input unit 52 to make a request to change the delivery schedule, for example.

[0081] (Administrative terminal 6) The management terminal 6 is a terminal device used by an administrator who manages the regular delivery service. Like the customer terminal 5, the management terminal 6 is, for example, a smartphone or a PC. The management terminal 6 has a display unit 61 and an input unit 62. The display unit 61 and the input unit 62 have functions corresponding to the display unit 51 and the input unit 52 of the customer terminal 5, respectively. Therefore, detailed explanations will be omitted here.

[0082] (Processing of delivery management system 10) Next, the processing performed by the delivery management system 10 will be described with reference to Fig. 8. Fig. 8 is a sequence diagram showing the processing performed by the delivery management system 10. It is assumed that the customer has registered customer information such as a credit card number in the DB server 3 in advance. It is also assumed here that multiple types of oil, including kerosene, can be dispensed using the weighing machine 1.

[0083] First, a customer presents a credit card that has been registered in advance with DB server 3 at a store (S11). Here, the customer has the reading unit 11 of weighing machine 1 read the credit card number. The reading unit 11 of weighing machine 1 reads the credit card number (S12). The reading unit 11 transmits the read credit card number to POS terminal 2. The POS terminal 2 acquires the credit card number transmitted from weighing machine 1 (S13).

[0084] The POS terminal 2 instructs the weighing machine 1 to refuel (S14). The weighing machine 1 operates the pump (S15). The customer also sets the refueling nozzle provided on the weighing machine 1 into a plastic container or the like (S16). Next, the weighing machine 1 starts refueling (S17). The weighing unit 12 of the weighing machine 1 ends refueling when the amount of refueled reaches a predetermined amount of oil (S18). The weighing unit 12 transmits the amount of refueled fuel to the POS terminal 2 as the store refueling amount. The customer then removes the nozzle (S19).

[0085] The POS terminal 2 checks the amount of fuel dispensed by the weighing machine 1 (S20). The POS terminal 2 performs the transaction (S21). Here, the POS terminal 2 performs the transaction using the in-store sales price, not the regular delivery price. This allows the customer to dispense fuel at a price lower than that of regular delivery. The POS terminal 2 performs payment using the credit card presented to the weighing machine 1. Note that the POS terminal 2 may also accept payment by methods other than credit cards. The POS terminal 2 also transmits the credit card number and the amount of fuel dispensed at the store to the DB server 3.

[0086] When the transaction is complete, the weighing machine 1 issues a receipt (S22), and the customer removes their credit card (S23).

[0087] The customer identification unit 31 of the DB server 3 determines whether the customer is a subscriber of the regular delivery service based on the credit card number (S24). Specifically, the customer identification unit 31 refers to the customer information DB 32 and determines whether the acquired credit card number is registered in the customer information DB 32. If the customer's credit card number is registered in the customer information DB 32, the customer identification unit 31 determines that the customer is a subscriber, and if not, determines that the customer is not a subscriber. If it is determined that the customer is a subscriber, the customer identification unit 31 identifies the customer.

[0088] If it is determined that the customer is not a contract holder (NO in S24), the processing ends. If it is determined that the customer is a contract holder (YES in S24), the customer identification unit 31 determines whether the type of oil supplied is kerosene (S25). The customer identification unit 31 may obtain the type of oil via the weighing machine 1 and the POS terminal 2.

[0089] If it is determined that the oil type is not kerosene (NO in S25), the processing ends. If it is determined that the oil type is kerosene (YES in S25), the customer identification unit 31 adds the amount of fuel supplied at the store to the remaining amount in the customer's virtual tank in the customer information DB 32 (S26). The customer identification unit 31 treats kerosene purchased at the store as equivalent to kerosene purchased through regular delivery. This allows the customer identification unit 31 to reflect the amount of fuel purchased at the store in the customer information DB 32. The customer identification unit 31 transmits the remaining amount in the virtual tank after adding the amount of fuel supplied at the store to the Web server 4.

[0090] Next, the delivery management unit 41 of the Web server 4 determines whether the relationship between the free space in the virtual tank and the scheduled delivery amount for the next delivery satisfies the condition "free space in virtual tank > scheduled delivery amount" (S27). If the free space in the virtual tank is less than or equal to the scheduled delivery amount (NO in S27), the delivery management unit 41 skips the next scheduled delivery (S28). This is because there is a lot of kerosene remaining in the customer's home tank, and it is expected that there will not be enough free space in the home tank if the delivery is made as scheduled.

[0091] If the free space in the virtual tank is greater than the scheduled delivery amount (YES in S27), the process ends. In this case, the delivery management unit 41 manages the delivery schedule so that delivery is carried out without changing the scheduled delivery date. This is because the remaining amount of kerosene in the customer's home tank is low, and it is assumed that there will be no shortage of free space in the home tank even if delivery is carried out as scheduled.

[0092] In this way, the delivery management unit 41 manages regular deliveries to customers, taking into account the amount of fuel supplied to the store. For example, the delivery management unit 41 can manage the scheduled delivery amount based on an adjusted minimum fuel supply amount, which is the minimum fuel supply amount minus the amount of fuel supplied to the store. This allows customers to purchase cheaper kerosene at the store without considering the minimum fuel supply amount stipulated in the regular delivery contract.

[0093] In addition, the display control unit 42 of the Web server 4 may display the delivery schedule information on the customer terminal 5 or the management terminal 6 in parallel with the above-mentioned processing. For example, the display control unit 42 may display various information shown in Figures 5 to 7 on the display unit 51 of the customer terminal 5. In this way, the customer can easily understand the kerosene purchase status.

[0094] The above describes the configuration and processing of the delivery management system 10. The configuration of the delivery management system 10 described above is merely an example and may be modified as appropriate. For example, if some or all of the components of the delivery management system 10 are realized by multiple information processing devices, circuits, etc., the multiple information processing devices, circuits, etc. may be centrally or decentralized.

[0095] For example, the information processing devices, circuits, etc. may be realized as a client-server system, a cloud computing system, etc., each connected via a communication network. Also, for example, the functions of the DB server 3 and the Web server 4 may be provided in a SaaS (Software as a Service) format.

[0096] Furthermore, in the above explanation, the DB server 3 and the Web server 4 are described separately, but the DB server 3 and the Web server 4 may be realized by a single device. For example, a specific management server can realize the functions of the customer identification unit 31, the customer information DB 32, the delivery management unit 41, and the display control unit 42. For example, the management server can include a processor, memory, and a storage device, and the storage device stores a computer program that implements the processes related to the DB server 3 and the Web server 4, and the customer information DB 32. The processor can realize the functions of the customer identification unit 31, the delivery management unit 41, and the display control unit 42 by loading the computer program from the storage device into the memory and executing the computer program.

[0097] As described above, in the delivery management system 10 disclosed herein, when a customer purchases kerosene at a store, the customer is identified by the customer identification unit 31 of the DB server 3, and regular deliveries are managed by the delivery management unit 41 of the Web server 4, taking into account the amount of fuel supplied to the store.

[0098] For example, the delivery management unit 41 manages the scheduled delivery amount based on the adjusted minimum fuel supply amount obtained by subtracting the store fuel supply amount from the minimum fuel supply amount. In this way, when a customer visits a gas station or the like, the customer can purchase kerosene at a store price that is lower than the unit price for regular deliveries and refill the kerosene into their home tank.

[0099] Furthermore, the delivery management unit 41 changes the delivery schedule based on at least one of the date of purchase of kerosene at the store and the amount of kerosene supplied to the store. For example, the delivery management unit 41 skips deliveries scheduled after the purchase date. This allows customers to avoid unnecessary refueling. Furthermore, the supplier can reduce delivery costs.

[0100] In addition, the display control unit 42 of the Web server 4 displays information on scheduled kerosene delivery for regular deliveries and a change request display that accepts requests for changes to regular deliveries on the terminal devices of customers and administrators, so that customers and others can easily understand the delivery status and change delivery schedules.

[0101] In this way, the delivery management system 10 according to the present disclosure can improve convenience for customers who use regular kerosene deliveries.

[0102] <Hardware configuration example> Each functional component of the delivery management system 100, weighing machine 1, POS terminal 2, DB server 3, Web server 4, customer terminal 5, and management terminal 6 (hereinafter referred to as "delivery management system 100, etc.") may be realized by hardware (e.g., hardwired electronic circuits, etc.) that realizes each functional component, or may be realized by a combination of hardware and software (e.g., a combination of an electronic circuit and a program that controls it, etc.). Below, we will further explain the case where each functional component of the delivery management system 100, etc. is realized by a combination of hardware and software.

[0103] 9 is a block diagram illustrating an example of the hardware configuration of a computer 900 that realizes the delivery management system 100, etc. The computer 900 may be a dedicated computer designed to realize the delivery management system 100, etc., or may be a general-purpose computer. The computer 900 may also be a portable computer such as a smartphone or tablet terminal.

[0104] For example, by installing a predetermined application on the computer 900, the computer 900 realizes each function of the delivery management system 100, etc. The application is composed of a program for realizing the functional components of the delivery management system 100, etc.

[0105] The computer 900 includes a bus 902, a processor 904, a memory 906, a storage device 908, an input / output interface 910, and a network interface 912. The bus 902 is a data transmission path that allows the processor 904, the memory 906, the storage device 908, the input / output interface 910, and the network interface 912 to transmit and receive data to and from each other. However, the method of connecting the processor 904 and other components to each other is not limited to a bus connection.

[0106] The processor 904 is a variety of processors such as a central processing unit (CPU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), or a quantum processor (quantum computer control chip). The memory 906 is a main storage device realized using a random access memory (RAM) or the like. The storage device 908 is an auxiliary storage device realized using a hard disk, a solid state drive (SSD), a memory card, a read only memory (ROM), or the like.

[0107] The input / output interface 910 is an interface for connecting the computer 900 to an input / output device. For example, the input / output interface 910 is connected to an input device such as a keyboard and an output device such as a display device.

[0108] The network interface 912 is an interface for connecting the computer 900 to a network. This network may be a LAN (Local Area Network) or a WAN (Wide Area Network).

[0109] The storage device 908 stores programs (programs that realize the applications described above) that realize the various functional components of the delivery management system 100, etc. The processor 904 reads these programs into the memory 906 and executes them to realize the various functional components of the delivery management system 100, etc.

[0110] Each processor executes one or more programs containing instructions for causing a computer to perform the algorithms described with reference to the figures. The programs contain instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The programs may be stored on various types of non-transitory computer-readable media or tangible storage media. By way of example and not limitation, non-transitory computer-readable media or tangible storage media include RAM, ROM, flash memory, SSD or other memory technologies, CD-ROM, DVD (Digital Versatile Disc), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices. The programs may also be transmitted over various types of transitory computer-readable media or communication media. By way of example and not limitation, transitory computer-readable media or communication media include electrical, optical, acoustic, or other forms of propagated signals.

[0111] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0112] Each drawing is merely an example for describing one or more embodiments. Each drawing may relate not only to one particular embodiment, but also to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0113] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes. (Appendix 1) a customer identification unit that identifies a customer who uses regular product delivery and purchases a product at a store based on customer identification information presented at the store; a delivery management unit that manages regular deliveries to the customer, taking into account a store purchase amount that indicates the amount of merchandise purchased at the store. Delivery management system. (Appendix 2) The delivery management unit Manage the scheduled delivery quantity of the product in the regular delivery based on a preset minimum purchase quantity; When the customer purchases a product at the store, the delivery schedule quantity is managed based on an adjusted minimum purchase quantity obtained by subtracting the store purchase quantity from the minimum purchase quantity. 1. A delivery management system as set forth in Appendix 1. (Appendix 3) The delivery management unit Manage the delivery schedule of the regular deliveries; When the customer purchases a product at the store, the delivery schedule is changed based on at least one of the purchase date of the product and the store purchase amount. 10. A delivery management system as set forth in claim 1 or 2. (Appendix 4) The delivery management unit skips or postpones deliveries scheduled after the purchase date. The delivery management system described in Appendix 3. (Appendix 5) a display control unit that displays information about the scheduled delivery of the products in the regular delivery on the terminal device; A delivery management system according to any one of appendices 1 to 3. (Appendix 6) The display control unit causes the terminal device to display, in association with the purchase amount of the product in the regular delivery and the purchase amount of the product at the store. Attachment 5, a delivery management system. (Appendix 7) the display control unit further causes the terminal device to display a change request display for accepting a change request regarding the regular delivery; The delivery management unit changes at least one of the planned delivery quantity of the product and the delivery schedule in response to the change request. 7. A delivery management system as set forth in appendix 5 or 6. (Appendix 8) The computer a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; a delivery management step of managing regular deliveries to the customer taking into account a store purchase amount indicating the amount of merchandise purchased at the store. Delivery management methods. (Appendix 9) In the delivery management step, Manage the scheduled delivery quantity of the product in the regular delivery based on a preset minimum purchase quantity; When the customer purchases a product at the store, the delivery schedule quantity is managed based on an adjusted minimum purchase quantity obtained by subtracting the store purchase quantity from the minimum purchase quantity. The delivery management method described in Appendix 8. (Appendix 10) a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; a delivery management step of managing regular deliveries to the customer by taking into account a store purchase amount indicating the amount of merchandise purchased at the store. program.

[0114] Some or all of the elements (e.g., configurations and functions) described in Supplements 2 to 7 that are dependent on Supplement 1 may also be dependent on Supplement 8 and Supplement 10 in the same dependent relationship as Supplements 2 to 7. Some or all of the elements described in any Supplement may be applied to various hardware, software, recording means for recording software, systems, and methods. [Explanation of symbols]

[0115] 1 Weighing machine 2. POS terminals 3. Database Server 4. Web Server 5. Customer terminal 6 Management terminal 10 Delivery Management System 11 Reading unit 31 Customer Identification Department 32 Customer information DB 41 Delivery Management Department 42 Display control unit 51 Display section 52 Input section 61 Display section 62 Input section 100 Delivery Management System 101 Customer Identification Department 102 Delivery Management Department 511 Delivery Schedule Information 511a Estimated delivery date icon 511b store purchase icon 511c skip icon 512 Change Request Display 513 My Page 5131 Refueling status 5132 Purchase History 5131a Contract fuel volume 5131b Fuel amount 5131c Estimated delivery amount 900 Computers 902 Bus 904 processor 906 memory 908 Storage Devices 910 Input / Output Interface 912 Network Interface N Network

Claims

1. a customer identification unit that identifies a customer who uses regular product delivery and purchases a product at a store based on customer identification information presented at the store; a delivery management unit that manages regular deliveries to the customer, taking into account a store purchase amount that indicates the amount of merchandise purchased at the store. Delivery management system.

2. The delivery management unit Manage the scheduled delivery quantity of the product in the regular delivery based on a preset minimum purchase quantity; When the customer purchases a product at the store, the delivery schedule quantity is managed based on an adjusted minimum purchase quantity obtained by subtracting the store purchase quantity from the minimum purchase quantity. The delivery management system according to claim 1 .

3. The delivery management unit Manage the delivery schedule of the regular deliveries; When the customer purchases a product at the store, the delivery schedule is changed based on at least one of the purchase date of the product and the store purchase amount. The delivery management system according to claim 1 or 2.

4. The delivery management unit skips or postpones deliveries scheduled after the purchase date. The delivery management system according to claim 3 .

5. a display control unit that displays information about scheduled product deliveries on a terminal device; The delivery management system according to claim 1 or 2.

6. The display control unit causes the terminal device to further display, in association with the purchase amount of the product in the regular delivery and the purchase amount of the product at the store. The delivery management system according to claim 5 .

7. the display control unit further causes the terminal device to display a change request display for accepting a change request regarding the regular delivery; The delivery management unit changes at least one of the planned delivery quantity of the product and the delivery schedule in response to the change request. The delivery management system according to claim 5 .

8. The computer a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; a delivery management step of managing regular deliveries to the customer taking into account a store purchase amount indicating the amount of merchandise purchased at the store. Delivery management methods.

9. In the delivery management step, Manage the scheduled delivery quantity of the product in the regular delivery based on a preset minimum purchase quantity; When the customer purchases a product at the store, the delivery schedule quantity is managed based on an adjusted minimum purchase quantity obtained by subtracting the store purchase quantity from the minimum purchase quantity. The delivery management method according to claim 8.

10. a customer identification step of identifying a customer who uses regular delivery of goods and purchases a product at a store based on customer identification information presented at the store; a delivery management step of managing regular deliveries to the customer by taking into account a store purchase amount indicating the amount of merchandise purchased at the store. program.

Images