Delivery management server and delivery management method

Abstract

It is possible to improve delivery efficiency for a package for which a delivery request has been made without designation of a delivery date and time.SOLUTION: A delivery management server that manages information regarding joint delivery in which a plurality of delivery companies cooperate with each other to deliver a delivery target package, the delivery management server comprising: a first acquisition unit that acquires destination information indicating a destination from a delivery request source without designation of a delivery date and time; The information processing apparatus includes a first transmission unit configured to transmit a request for inquiring about a desired delivery date and time, a second acquisition unit configured to acquire a desired delivery date and time indicating a delivery date and time from the electronic apparatus as a response to the request, and a second transmission unit configured to notify an electronic apparatus of at least one delivery company of delivery companies that perform joint delivery of the acquired desired delivery date and time.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a delivery management server and a delivery management method. [Background technology]

[0002] One delivery company manages one package from collection to delivery. The delivery company uses its own management system to manage the delivery status of each package from collection to delivery completion as delivery information. In order to manage each package individually, a waybill is attached to each package and an individual identification number assigned to the waybill is used (see, for example, Patent Document 1). On the other hand, in recent years, the use of joint delivery has been increasing from various perspectives, such as driver shortages, improving delivery efficiency, and reducing the number of vehicles required for delivery. In joint delivery, multiple delivery companies work together to deliver collected packages. [Prior art documents] [Patent documents]

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

[0004] However, while joint delivery can improve delivery efficiency, it cannot deliver packages if the recipient is not at home. When a delivery requester requests delivery of a package, a delivery date and time may be specified, but not always. If a delivery date and time is specified when a delivery request is made, by visiting the recipient's address at the specified delivery date and time, the recipient is likely to be at home and the package can be delivered. However, if a shipping request is made without specifying a delivery date and time, the recipient is not necessarily likely to be at home, and the recipient may be at home even when visited for delivery. This reduces delivery efficiency.

[0005] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a delivery management server and a delivery management method that can improve delivery efficiency for packages for which delivery requests have been made without specifying a delivery date and time. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a delivery management server that manages information regarding joint deliveries in which multiple delivery companies work together to deliver packages to be delivered, and has a first acquisition unit that acquires destination information indicating the destination from the delivery requester without specifying a delivery date and time, a first transmission unit that sends a request to the electronic device of the inquiry destination to inquire about the desired delivery date and time based on the contact information included in the acquired destination information, a second acquisition unit that acquires a desired delivery date and time indicating the delivery date and time from the electronic device as a response to the request, and a second transmission unit that notifies the electronic device of at least one of the delivery companies participating in the joint delivery of the acquired desired delivery date and time.

[0007] Another aspect of the present invention is a delivery management method executed by a delivery management server that manages information regarding joint deliveries in which multiple delivery companies work together to deliver packages to be delivered, the delivery management method including: acquiring destination information indicating the destination from a delivery requester without specifying a delivery date and time; sending a request to an electronic device of the inquiry destination based on contact information included in the acquired destination information to inquire about the desired delivery date and time; acquiring a desired delivery date and time indicating the delivery date and time from the electronic device as a response to the request; and notifying the electronic device of at least one of the delivery companies participating in the joint delivery of the acquired desired delivery date and time. [Effects of the Invention]

[0008] As described above, according to this invention, even for packages for which a delivery request has been made without a specified delivery date and time, the delivery date and time are obtained from the recipient and the delivery date and time are notified to the delivery company in a comprehensible manner, thereby improving delivery efficiency. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a schematic block diagram showing the configuration of a delivery system S according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram showing an example of the appearance of a shipping label. [Figure 3] FIG. 2 is a schematic functional block diagram showing the functions of the delivery management server 30. [Figure 4] FIG. 3 is a diagram showing an example of package data stored in a storage unit 302. [Figure 5A] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5B] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5C] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5D] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5E]FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5F] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 5G] FIG. 2 is a diagram illustrating the operation of the delivery system S in the first embodiment. [Figure 6A] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6B] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6C] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6D] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6E] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6F] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6G] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6H] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. [Figure 6I] FIG. 10 is a diagram illustrating the operation of the delivery system S in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] A delivery system S according to one embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing the configuration of a delivery system S according to one embodiment of the present invention. The delivery system S includes user terminals 10 (10a, 10b), POS terminals 20 (20a, 20b), a delivery management server 30, an invoice printing server 40, an invoice printing device 41, a deliverer terminal 50 (50a, 50b), a mobile printer 55 (55a, 55b), a delivery company server 60 (60a, 60b), an EC (Electronic Commerce) site server 70, and a network NW.

[0011] The user terminal 10 (10a, 10b) is a terminal device used by a user. The user may be either a consumer (hereinafter sometimes referred to as a general consumer) or an employee of a company or organization. When used by a general consumer, the user terminal 10 is used at the general consumer's home or on the go. When used by an employee of a company or organization, the user terminal 10 is mainly used in facilities managed by the company or organization. For example, the user terminal 10a is used by a user who has requested delivery, and the user terminal 10b is used by a user at the destination of the package (for example, a recipient). The user terminal 10 may be, for example, any of a smartphone, a tablet, a mobile phone, a PC (Personal Computer), etc. If the user terminal 10 has a camera, it can read a machine-readable code. The machine-readable code represents, for example, waybill identification information that individually identifies the waybill, and may be any of a one-dimensional barcode, a two-dimensional barcode, etc. The machine-readable code is attached to the waybill. The user terminal 10 also has a display unit that displays various data on a display screen, an input unit that accepts input operations for various data, etc. The display unit may be a liquid crystal display panel. The input unit may be any input device such as a touch panel, keyboard, or mouse based on operational input from the user. The input data may be, for example, destination information or delivery requester information. Furthermore, if the user terminal 10 is not equipped with a camera or if a camera is not used, the input data may be waybill identification information. The user terminal 10 is communicably connected to at least one of the delivery management server 30 and the EC site server 70 via the network NW.

[0012] The POS terminals 20 (POS terminal 20a, POS terminal 20b) are communicably connected to the delivery management server 30 via the network NW. The POS terminal 20 optically reads the machine-readable code attached to the shipping invoice using a scanner, and also performs a settlement process for the payment of the delivery fee from the user who has requested delivery. The POS terminal 20 is installed at a base. A base is a base that manages packages for delivery in response to a request from a user who has made a delivery request. Bases include collection bases that collect packages, relay bases that relay collected packages before delivering them to the destination user, and the like. Of these, the POS terminal 20 is installed at a collection base. A collection base may be, for example, a base that accepts packages from a user who has made a delivery request, such as a delivery company office, a convenience store, a drugstore, or a privately owned shop. In this example, the POS terminal 20a is installed at a collection base of a first delivery company, and the POS terminal 20b is installed at another base (for example, at least one of a convenience store, a drugstore, a privately owned shop, or a collection base of a second delivery company).

[0013] The delivery management server 30 is communicably connected via the network NW to the user terminal 10a, the user terminal 10b, the POS terminal 20, the waybill printing server 40, the deliverer terminal 50a, the deliverer terminal 50b, and the EC site server 70. The delivery management server 30 manages joint deliveries in which multiple delivery companies work together to deliver packages to be delivered. Joint delivery may involve multiple delivery companies working together to deliver a package. When joint delivery is performed, the first delivery company may or may not have a contract for joint delivery with other delivery companies. Furthermore, the first delivery company may collect a package and hand it over to one of the multiple companies, which then delivers it to the destination user. Alternatively, the first delivery company may collect a package and deliver it to multiple delivery companies working together in order, with the last delivery company delivering the package to the destination user.

[0014] The delivery management server 30 executes various processes related to delivery. The delivery management server 30 may be shared by multiple delivery companies. The delivery management server 30 may be operated by a company or organization that is not a delivery company. Furthermore, the delivery management server 30 may be operated by one or several of the multiple delivery companies.

[0015] The invoice printing server 40 is communicably connected to the delivery management server 30 via the network NW, and is also communicably connected to the invoice printing device 41. The invoice printing server 40 receives number range data representing the number range used for invoices from the delivery management server 30 or the delivery company server 60, and causes the invoice printing device 41 to print an invoice based on the number range data. The invoice printer 41 is communicatively connected to the invoice print server 40. The invoice printer 41 prints invoices by printing on a print medium based on the number band data output from the invoice print server 40. The print medium used for invoices has one printable surface and the other main surface with an adhesive layer and release paper attached. The printed invoices are delivered to the delivery company's base to which the number band used for the invoice identification information is assigned. Here, the invoice print server 40 and the invoice printer 41 are installed in a location separate from the delivery company's base, although multiple invoice printers 41 may be installed. When multiple invoice printers 41 are installed, they may be installed at the delivery company's base, connected to the delivery company server 60 to which the base belongs, and print invoices in response to instructions from the connected delivery company server 60. The user who made the delivery request or the collection staff at the collection point can attach the printed waybill to the package by peeling off the release paper and attaching the adhesive side to the package. Such waybills can be used as shipping labels.

[0016] The deliverer terminals 50 (50a, 50b) are communicably connected to the delivery management server 30 via the network NW. The deliverer terminals 50 are also communicably connected to a mobile printer 55. The deliverer terminal 50 is used by a person in charge of parcel delivery. For example, it is carried by a collection driver, a delivery driver, etc. The deliverer terminal 50 has a camera, a function for reading machine-readable codes attached to waybills, a display function for displaying various data on a display screen, an input unit for accepting operational input, etc. The display screen may be a liquid crystal display panel provided on the deliverer terminal 50. The deliverer terminal 50 may be, for example, a smartphone, a tablet, a mobile phone, a PC, or the like. The deliverer terminal 50 outputs the print data to the mobile printer 55, thereby causing the mobile printer 55 to print the print data. The print data may be, for example, destination information or part of the destination information.

[0017] The deliverer terminal 50a is used, for example, by a person in charge of collection, and the deliverer terminal 50b is used by a person in charge of delivery. When a joint delivery is performed, at least one of the multiple deliverer terminals 50 is used by a first delivery company, and at least one of the other deliverer terminals 50 is used by a second delivery company. Also, when there are three or more deliverers performing a joint delivery, individual deliverer terminals 50 are used for each of the other deliverers, such as the third delivery company, the fourth delivery company, etc.

[0018] The mobile printers 55 (55a, 55b) are printing devices that are communicably connected to the deliverer terminal 50 and print print data sent from the deliverer terminal 50 onto a print medium. The mobile printer 55 may be a device configured as a separate housing from the deliverer terminal 50, but the mobile printer 55 may also be provided integrally with the deliverer terminal 50.

[0019] The delivery company server 60a is used by the first delivery company. The delivery company server 60a may be a server of a management system that has already been introduced to manage packages that the first delivery company undertakes to deliver. The delivery company server 60b is used by a second delivery company that is a delivery company different from the first delivery company. The delivery company server 60b may be a server of a management system that has already been introduced to manage packages that the second delivery company is contracted to deliver. Here, the case where there are two delivery company servers will be described, but if there are three or more delivery companies, a delivery company server 60 may be provided for each delivery company. In addition, if the delivery company does not have its own management system, a new delivery company server may be introduced to communicate with the delivery management server 30.

[0020] The EC site server 70 is a server that provides a website for electronic commerce, and may be any of an internet shop, an internet flea market site, an internet auction site, etc. The EC site may be a mall-type site. Furthermore, although there is one EC site server 70 in FIG. 1, if there are multiple EC sites, a different EC site server 70 may be provided for each EC site. The EC site server 70 publishes products put up for sale by sellers on the EC site, accepts purchase procedures from purchasers, and publishes progress information regarding the product purchase procedures, delivery status, etc. on the EC site so that the seller or purchaser can understand it. Furthermore, instead of publishing the delivery status on the EC site, the EC site server 70 may publish a link (URL) where the delivery status can be viewed to purchasers, or the delivery management server 30 may notify the purchaser's user terminal 10 of the URL. When a product is put up for sale on an e-commerce site and purchased by a buyer, it is packaged and then delivered by a delivery company. Here, we will explain a case where the buying and selling of products and the shipping status of products can be viewed on an EC site, but this may also be achieved by an EC app rather than a website that publishes the EC site.

[0021] The network NW is a communication network including at least a part of, for example, the Internet, a wide area network (WAN), a local area network (LAN), a provider device, a wireless base station, a dedicated line, etc. The network NW may be wired or wireless, or may be a combination of wired and wireless.

[0022] The above-mentioned delivery management server 30, delivery company server 60, and EC site server 70 may be physical servers or cloud servers provided by a cloud computing service.

[0023] FIG. 2 is a diagram showing an example of the appearance of the shipping label. One of the main surfaces of the invoice is a printing surface on which various data can be printed, and the other main surface has an adhesive layer formed by applying an adhesive. A two-dimensional barcode La, invoice identification information Lb, one-dimensional barcode Lc, and one-dimensional barcode Ld are printed on the invoice, with a portion of the invoice set aside as a reserve area Le. The two-dimensional barcode La is a two-dimensional barcode that represents the invoice identification information. In addition, in the case of corporate use, corporate information may be written following the invoice identification information. In this case, the two-dimensional barcode may include the invoice identification information and the corporate information. The invoice identification information Lb represents the invoice identification information using a character string and is the same as the invoice identification information represented by the two-dimensional barcode La. The one-dimensional barcode Lc and one-dimensional barcode Ld can be used for various management purposes. The reserved area Le is an area where necessary information can be written by hand or labels, slips, etc. can be attached as needed when delivering a package. The package may be delivered without anything written in this reserved area Le, or without a label or slip attached.

[0024] FIG. 3 is a schematic functional block diagram showing the functions of the delivery management server 30. The delivery management server 30 includes a communication unit 301 , a memory unit 302 , a first acquisition unit 303 , a second acquisition unit 304 , a first processing unit 305 , a transmission unit 306 , an identification information management unit 307 , and a control unit 308 . The communication unit 301 communicates with various external devices via the network NW. The memory unit 302 is configured by a storage medium, such as a hard disk drive (HDD), flash memory, electrically erasable programmable read-only memory (EEPROM), random access read / write memory (RAM), read-only memory (ROM), or any combination of these storage media. The storage unit 302 may be, for example, a non-volatile memory.

[0025] The storage unit 302 stores, for example, package data.

[0026] The first acquisition unit 303 includes an invoice identification information acquisition unit 3031 and a destination information acquisition unit 3032 . The waybill identification information acquisition unit 3031 acquires the waybill identification information. For example, the waybill identification information acquisition unit 3031 acquires the waybill identification information obtained by reading the waybill identification information of the waybill attached to the package to be delivered by the first delivery company. The waybill identification information acquisition unit 3031 may also acquire the waybill identification information of the waybill attached to the package to be delivered from a device of the first delivery company that is the consignor (or the cooperating source) coordinating the package. The destination information acquisition unit 3032 acquires destination information indicating an identifiable destination from the delivery requester, without specifying a delivery date and time. For example, the destination information acquisition unit 3032 acquires destination information from the user terminal 10 based on a user's operational input. The delivery requester is the user terminal 10, and the destination information may be acquired from the user terminal 10, or may be acquired via the EC site server 70, or may be acquired via the delivery company server 60. The destination information may be acquired from the user terminal 10 of the delivery requester, or may be acquired from the user terminal 10 used by the user of the delivery destination.

[0027] The second acquisition unit 304 includes a delivery status acquisition unit 3041 and a desired date and time acquisition unit 3042 . The delivery status acquisition unit 3041 receives status information relating to the delivery status of the package and waybill identification information from a device of any of the delivery companies that delivers the package (for example, the delivery company server 60). The desired date and time acquisition unit 3042 acquires a desired delivery date and time indicating a delivery date and time from an electronic device (for example, the user terminal 10, the EC site server 70) as a response to the request to confirm the scheduled delivery date and time. In response to an inquiry request, the desired delivery date and time acquisition unit 3042 also acquires, from the server of the EC site, the desired delivery date and time transmitted to the server of the EC site from the user terminal 10b used by the destination consumer.

[0028] The first processing unit 305 executes various processes. For example, the first processing unit 305 stores the status information acquired by the second acquisition unit 304 (e.g., delivery status acquisition unit 3041) in the memory unit 302 in association with the waybill identification information acquired by the first acquisition unit 303 (e.g., waybill identification information acquisition unit 3031). The status information may be any information that allows the delivery status to be understood. For example, the first processing unit 305 may store the delivery information acquired by the second acquisition unit 304 (e.g., the delivery status acquisition unit 3041) in the storage unit 302 in association with the waybill identification information acquired by the first acquisition unit 303 (e.g., the waybill identification information acquisition unit 3031). Also, for example, the first processing unit 305 may store the delivery completion information acquired by the second acquisition unit 304 (e.g., the delivery status acquisition unit 3041) in the memory unit 302 in association with the waybill identification information acquired by the first acquisition unit 303 (e.g., the waybill identification information acquisition unit 3031). The first processing unit 305 may also store the entrusted delivery company information and the waybill identification information in the storage unit 302 in association with each other.

[0029] The transmitting unit 306 transmits various types of data. For example, in response to an inquiry from the delivery company server 60 of one of a plurality of delivery companies, the transmission unit 306 transmits the status information stored in the storage unit 302 to the device of the delivery company that made the inquiry.

[0030] The transmitting unit 306 includes a first transmitting unit 3061 and a second transmitting unit 3062 . The first transmission unit 3061 transmits a request to the electronic device to inquire about the desired delivery date and time based on the contact information included in the acquired destination information. The electronic device to be inquired about may be the user terminal 10b, or the first transmission unit 3061 may inquire about the user terminal 10b via the EC site server 70. The second transmission unit 3062 notifies the electronic device (delivery company server 60 or deliverer terminal 50) of at least one of the delivery companies performing the joint delivery of the desired delivery date and time acquired from the user terminal 10. The second transmission unit 3062 may transmit the acquired desired delivery date and time to the server of the EC site.

[0031] The identification information management unit 307 manages waybill identification information that is common to multiple delivery companies and does not overlap. For example, the identification information management unit 307 may generate waybill identification information that is common to multiple delivery companies and does not overlap, and assign it to each delivery company so that it can be used. Alternatively, instead of generating waybill identification information, the identification information management unit 307 may assign to each delivery company a generation rule that results in waybill identification information that is common to multiple delivery companies and does not overlap.

[0032] The control unit 308 controls each unit of the delivery management server 30. The control unit 308 also writes and reads each piece of data stored in the storage unit 302 according to the delivery status.

[0033] This delivery management server 30 is managed by a third-party management company that is different from each of the multiple delivery companies. Also, the delivery management server 30 may be managed by any one of the multiple delivery companies or jointly by several of the multiple delivery companies.

[0034] FIG. 4 is a diagram showing an example of package data stored in the storage unit 302. As shown in FIG. The package data includes waybill identification information and delivery information, which may include information on the delivery requester, destination information, package information, status information, a one-dimensional barcode, and a scheduled delivery date and time. The invoice identification information is information that individually identifies an invoice. The delivery requester information is information relating to the delivery requester, and includes, for example, the address, name, telephone number, etc. of the user who has requested delivery. The destination information is information relating to the destination, and includes, for example, the address, name, and telephone number of the destination user.

[0035] The package information is information relating to the package, and includes, for example, the size of the package, whether it is refrigerated or frozen, delivery charges, and the like. Status information indicates the delivery status of a package, and includes, for example, an acceptance flag, a delivery flag, a delivery completion flag, an absence flag, and handover information. The acceptance flag indicates whether the package has been accepted by the collection officer. For example, an acceptance flag of "0" indicates that the package has not been accepted, and an acceptance flag of "1" indicates that the package has been accepted. The delivery information is data indicating which delivery company will be responsible for which task in delivering a package. For example, the delivery information includes information that allows for understanding which delivery company will be responsible for which section of the delivery section from collection to delivery to the destination address when performing joint delivery. The delivery information may be generated when it is decided that a package to be delivered will be handed over from a first delivery company to a second delivery company, but it may also be generated when the package to be delivered is handed over from the first delivery company to the second delivery company.

[0036] The delivery flag is information that indicates whether the package is currently being delivered. For example, a delivery flag of "0" indicates that the package has not yet been delivered (before the package is accepted, after delivery has been completed, etc.), and a delivery flag of "1" indicates that the package is currently being delivered (between acceptance and delivery to the destination user). The delivery completion flag is information indicating whether the package has been received by the destination user. For example, a delivery completion flag of "0" indicates that the delivery has not been completed (for example, the state between the time the package is left at the collection point and the time delivery to the destination user is completed), and a delivery completion flag of "1" indicates that the delivery of the package to the destination user has been completed. The absence flag is information that indicates whether the delivery driver visited the destination address but the user was not present and so the delivery driver has returned the package. For example, an absence flag of "0" indicates that the delivery driver has not yet visited the destination address, and an absence flag of "1" indicates that the delivery driver visited the destination address but the user was not present and so the delivery driver has returned the package. The one-dimensional barcode is data individually assigned to the waybill L, and represents the one-dimensional barcode Lc attached to the waybill L. In this case, when the one-dimensional barcode Lc is read by the POS terminal 20, the control unit 308 of the delivery management server 30 can identify the one-dimensional barcode stored in the memory unit 302 that corresponds to the one-dimensional barcode Lc acquired from the POS terminal 20, and identify the waybill identification information that corresponds to the identified one-dimensional barcode.

[0037] The scheduled delivery date and time indicates the date and time when the delivery company is scheduled to visit the destination to deliver the package to the destination address. This scheduled delivery date and time may be determined based on the date and time when the delivery company is available for delivery unless the destination consumer requests it.

[0038] The above-mentioned communication unit 301, first acquisition unit 303, second acquisition unit 304, first processing unit 305, transmission unit 306, identification information management unit 307, and control unit 308 may be configured, for example, by a processing unit such as a CPU (Central Processing Unit) or a dedicated electronic circuit.

[0039] Next, the operation of the above-mentioned delivery system S will be described. First Embodiment In the first embodiment, an operation will be described when a package is sent from a delivery requesting user to a destination user without going through the EC site server 70. Figures 5A, 5B, 5C, 5D, 5E, 5F, and 5G are sequence diagrams explaining the operation of the delivery system S.

[0040] <Preparation Phase> The identification information management unit 307 of the delivery management server 30 allocates and issues an available waybill number range (step S400 in FIG. 5). Here, the identification information management unit 307 allocates a different waybill number range to each delivery company. The waybill use number range is data representing waybill identification information that can be used as waybill identification information to be attached to a waybill. For example, the waybill identification information can be represented by a character string, and if the character string is represented by a number, the waybill use number range represents a range of usable numbers. For example, the waybill use number range may be a range of numbers that is specified for each delivery company (sequential numbers), such as N1 to N2 for the first delivery company and N3 to N4 for the second delivery company, or it may be a range of usable character strings that are individually specified (it does not have to be sequential numbers). Furthermore, the waybill identification information may be a string of multiple numbers, a string of letters or symbols, or a string that combines at least two of numbers, letters, and symbols. The waybill identification information is sometimes called a package ID (Identifier).

[0041] Here, the identification information management unit 307 may assign to each delivery company a generation rule that will result in waybill identification information that is common and unique among multiple delivery companies. The generation rule may, for example, include the delivery company identification information of the delivery company generating the waybill identification information as part of the waybill identification information, and the remaining character strings may be concatenated with individual character strings prepared by the generating delivery company, or may further include a character string corresponding to the date of generation. Once such a generation rule is assigned, the delivery company server 60 of each delivery company can generate the waybill identification information in accordance with the generation rule.

[0042] Here, we will explain the case where the waybill identification information is issued by the delivery management server 30, but it is also possible for the delivery management server 30 not to issue the waybill identification information, and for the delivery system S to use the waybill identification information prepared by the delivery company.

[0043] The waybill identification information is generated by the identification information management unit 307, printed on the waybill by the waybill printer 41, attached to the package, and may be made usable again after fulfilling certain conditions, such as the completion of delivery or the passage of a certain period of time. The identification information management unit 307 may assign such reusable numbers as waybill number ranges.

[0044] The delivery management server 30 transmits data of the use number range assigned to the first delivery company to the delivery company server 60a of the first delivery company (Step S200 in FIG. 5).

[0045] When the delivery company server 60a of the first delivery company receives the data of the number range to be used from the delivery management server 30, the delivery company server 60a stores the data of the number range to be used in the storage device of its own management system (FIG. 5, step S201).

[0046] The delivery company server 60a of the first delivery company causes a printer to print an invoice in accordance with the data of the number range indicated by the received invoice use number range data (step S202 in FIG. 5). This printer may be a printer connected to the delivery company server 60a and used by the first delivery company. Alternatively, the invoice may be printed by the invoice printer 41 and handed over to the delivery company after printing. For example, the printing device generates a two-dimensional barcode representing the invoice identification information included in the invoice use number band, and prints a different two-dimensional barcode on each different invoice. Here, the two-dimensional barcode representing the invoice identification information may be printed on the invoice, or the text representing the invoice identification information itself may be printed on the invoice. Alternatively, both the two-dimensional barcode and the text representing the invoice identification information may be printed. While this embodiment describes a case where the invoice identification information is printed as a two-dimensional barcode, a one-dimensional barcode may also be used.

[0047] The printing device prints one invoice identification information on one invoice in accordance with instructions from the invoice printing server 40. Here, if the invoice use number band contains multiple invoice identification information, each invoice identification information is printed on a different invoice.

[0048] Once the waybill is printed, the printed waybill is sent to and placed at the base where the package is delivered. If the delivery company prints the waybill, the printed waybill may be placed at the base, or if the waybill is printed by waybill printer 41, the waybill may be handed over to the delivery company and then placed at the base by the delivery company, or it may be placed directly at the base without being handed over to the delivery company. The base where the waybill is placed is, for example, a base that accepts packages based on a request from a user who has requested delivery, such as a convenience store. The waybill placed at the convenience store is distributed to the user who has requested delivery.

[0049] When a user who has requested delivery wishes to have a package delivered, the user can perform an operation input to the user terminal 10a to register the user in advance with the delivery management server 30. By registering the user, the address, name, telephone number, etc. of the user who has requested delivery can be specified as the address, name, telephone number, etc. of the user who has requested delivery without having to directly input the address, name, telephone number, etc. of the user who has requested delivery from the user terminal 10a, etc., each time delivery is made. When a delivery requesting user registers, the user uses the user terminal 10a to access a web page for user registration made public by the delivery management server 30 and inputs various necessary information on the user registration screen (FIG. 5, step S100). The necessary information includes, for example, the address, name, and telephone number of the delivery requesting user. The user terminal 10a performs user registration processing based on the operation input from the user. The user terminal 10a transmits the various data input by the user to the delivery management server 30 and also transmits a user registration request.

[0050] The delivery management server 30 assigns user identification information that individually identifies the user based on the user registration request sent from the user terminal 10a, and stores the user identification information in association with the various data sent from the user terminal 10a in the storage unit 302 (FIG. 5, step S401). In this way, user processing in the delivery management server 30 is executed.

[0051] <Delivery start phase> When a user who has requested delivery wishes to have a package delivered, the user brings the package to a base (which may be a base such as a convenience store) where the first delivery company collects the package, and receives a waybill at the base. When the user requesting delivery receives the waybill, the user reads the waybill identification information printed on the waybill by photographing it with the camera of the user terminal 10a, and inputs the recipient's address, name, telephone number, etc. as destination information using the input device of the user terminal 10a, and sends the waybill identification information and the recipient's address to the delivery company server 60a of the first delivery company (Figure 5, step S101). Here, if the user requesting delivery does not know the date and time when the recipient user can receive the package, the user inputs the waybill identification information and the recipient information into the user terminal 10a without specifying the delivery date and time. Based on the user's operational input, the user terminal 10a transmits the waybill identification information and the recipient information to the delivery company server 60a without specifying the delivery date and time. Not specifying a delivery date and time can be done by leaving the field for specifying the delivery date and time blank on the input screen of the user terminal 10a, or by selecting ``No preference'' in the field for specifying the delivery date and time and sending the message. Here, when the user terminal 10a accesses the delivery company server 60a, the two-dimensional barcode may contain a URL for accessing the delivery company server 60a, and the user terminal 10a may access the delivery company server 60a based on this URL. This allows the registration procedure of various information for the waybill identification information to be carried out.

[0052] Here, if the user requesting delivery has registered in advance, they can log in from the delivery service's web service or application program and set the user-registered data as delivery requester information without manually entering the address, page number, telephone number, etc. of the delivery requester. If the delivery requester user has not registered in advance, the delivery requester user may input their own address, name, telephone number, etc. as delivery requester information from the user terminal 10a. In this case, the delivery management server 30 may assign a guest account to the unregistered user and manage the delivery requester user using the guest account for a certain period of time.

[0053] Here, the user terminal 10a may read the waybill identification information with a camera, transmit the waybill identification information to the delivery company server 60a, and then have the user who made the delivery request input the delivery destination information, and transmit the delivery destination information to the delivery company server 60a. Alternatively, the user terminal 10a may have the user input the delivery destination information, transmit the delivery destination information to the delivery company server 60a, and then read the waybill identification information on the waybill with a camera, and transmit the waybill identification information to the delivery company server 60a. Furthermore, user terminal 10a may read the waybill identification information with a camera, temporarily store the read waybill identification information in a storage area within user terminal 10a, and after the user inputs destination information, transmit the waybill identification information together with the destination information to delivery company server 60a. Furthermore, user terminal 10a may read the waybill identification information with a camera, temporarily store the input destination information in a storage area within user terminal 10a, and after the user inputs destination information, transmit the waybill identification information together with the destination information to delivery company server 60a. Furthermore, the waybill identification information can be extracted from the two-dimensional barcode by reading it with the user terminal 10a, but if the waybill identification information is printed on the waybill as a character string rather than a two-dimensional barcode, the character string can be extracted by photographing the character string with the camera of the user terminal 10a and performing OCR (Optical Character Reader) processing on the photographed image. Also, if a character string representing the waybill identification information is printed on the waybill, the user who has requested delivery can register it by manually entering the character string directly into the user terminal 10a.

[0054] The delivery company server 60a receives the waybill identification information, delivery requester information, delivery destination information, and information indicating that the delivery date and time is not specified, which are sent from the user terminal 10a (FIG. 5, step S203).

[0055] When the user requesting delivery sends to the delivery company server 60a information indicating that the waybill identification information, destination information, and delivery date and time have not been specified, the user attaches the waybill with the waybill identification information attached to the package to be delivered and hands it over to a person in charge at the base. Here, when the package is shipped, the waybill identification information, destination information, etc. are sent from the user terminal 10a to the delivery company server 60a, but they may also be sent to the delivery management server 30. Then, the delivery management server 30 may send the waybill identification information, destination information, etc. to the delivery company server 60, thereby sharing information about the package. When handing over the package, the user requesting delivery may or may not handwrite the address, name, and telephone number of the user requesting delivery, and the address, name, and telephone number of the user at the destination, in the spare area Le of the waybill, as necessary. Here, since the destination information and the information of the user requesting delivery are already registered in the waybill identification information, it is not necessary to write or print information about the destination and the user requesting delivery as character strings directly on the waybill.

[0056] The delivery company server 60a also uses the address included in the delivery requester information and the address included in the destination information as provisional data, calculates a delivery route based on this provisional data, and stores the delivery route in association with the waybill identification information. The delivery company server 60a may also transmit a provisional delivery schedule corresponding to the delivery route based on the provisional data to the user terminal 10a, and display it on the user terminal 10a.

[0057] When the delivery requester delivers the package to a person in charge at the base (for example, the base of the first delivery company or a convenience store), the person in charge reads the invoice identification information printed on the invoice attached to the package using the scanner of the POS terminal 20, and stores the package in a storage location. The POS terminal 20 transmits the read invoice identification information to the delivery company server 60a.

[0058] After receiving the waybill identification information, delivery requester information, delivery destination information, and information indicating that the delivery date and time are not specified from the user terminal 10a, the delivery company server 60a acquires the waybill identification information from the POS terminal 20a, and stores the waybill identification information, delivery requester information, delivery destination information, and information indicating that the delivery date and time are not specified in a storage device within the delivery company server 60a, and sends a collection instruction to the deliverer terminal 50 in charge of collecting the package, causing it to perform the collection operation (Figure 5 step S204). For example, when sending a collection instruction, the delivery company server 60a identifies the location from which the item was collected based on the identification information assigned to the POS terminal 20, and sends a collection instruction to the delivery person terminal 50 that includes information that allows the identified location to be identified. When the deliverer terminal 50 receives this collection instruction, it displays the collection instruction on the display screen. For example, if the package is accepted at a convenience store, the screen will display which convenience store the package was picked up at. This allows the driver in charge of collection to know that the package will be picked up. Furthermore, if the package is accepted at the collection base of the first delivery company, the delivery person of the first delivery company can understand the collection acceptance status based on the information displayed on the display screen of the deliverer terminal 50.

[0059] The driver in charge of collection of the first delivery company carries the deliverer terminal 50a and travels to each base to collect the package based on the collection instructions. Here, the driver travels along a route that includes the base where the package is stored and picks up the package stored at the base. The driver in charge of collection who receives the package reads the waybill identification information attached to the package using the deliverer terminal 50a and presses the "collection button" to indicate that the package has been collected. When the deliverer terminal 50a reads the waybill identification information and presses the collection button, it transmits the waybill identification information, data indicating that the package has been collected, and the collection date and time to the delivery company server 60a. Here, although a waybill L is attached to the package, the destination information and information on the delivery requester are not necessarily written on the waybill. Therefore, it is difficult to determine from the face of the waybill alone whether the use of the waybill has begun, for example, whether it has been accepted by the delivery company. However, by reading the waybill identification information on the waybill with the user terminal 10 or the deliverer terminal 50, accessing the delivery management server 30 and referencing various data corresponding to the waybill identification information, it is possible to determine whether the use of the waybill has begun, whether the package has been accepted by the delivery company, information on the delivery requester, destination information, etc. In addition, the driver in charge of collection can input an operation to the deliverer terminal 50a to print part of the destination information. The deliverer terminal 50a reads the waybill identification information attached to the waybill of the package for which part of the destination information is to be printed, and when an operation input to print part of the destination information is made, the deliverer terminal 50a causes the mobile printer 55a connected to the deliverer terminal 50a to print the part of the read waybill information. The mobile printer 55a prints part of the destination information on a print medium based on the instruction from the deliverer terminal 50a. The part of the destination information may be information including at least a part of the address, name, and telephone number of the destination. In addition, the deliverer terminal 50a may cause the mobile printer 55a to print a character string representing the part of the destination information, or may generate a two-dimensional barcode corresponding to the part of the destination information and cause the mobile printer 55a to print the generated two-dimensional barcode. In this way, part of the destination information may be printed on a print medium and attached to the spare area Le of the waybill L. When part of the destination information is printed and attached to the waybill L, the destination can be ascertained even in a situation where the deliverer terminal 50 cannot access the delivery management server 30 (for example, due to radio wave reception being unavailable). Although the case where some of the destination information is printed on the label has been described, it is not necessarily required that the information is printed. The driver in charge of collection loads the packages into the vehicle and delivers them from the base such as a convenience store to a relay point.

[0060] When the delivery company server 60a receives data indicating collection and the waybill identification information from the deliverer terminal 50a, it references the storage device within the delivery company server 60a and checks whether it matches the waybill identification information sent from the POS terminal 20 and registered. If the comparison shows that the waybill identification information matches, the delivery company server 60a updates the status information corresponding to the waybill identification information stored in the storage device. In this case, the status is updated to "Collected," indicating that the package has been accepted. When the status is updated, the delivery company server 60a performs a linkage process by transmitting data indicating that the package has been collected, waybill identification information, delivery destination information, delivery requester information, and information indicating that the delivery date and time has not been specified to the delivery management server 30 (FIG. 5, step S205). The information indicating that the delivery date and time has not been specified may be any information that allows the user at the destination to understand that the delivery date and time has not been specified. For example, it may be information indicating that the user at the destination has not specified a delivery date and time, or it may be a tentative delivery schedule calculated by the first delivery company (or the delivery management server 30). The tentative delivery schedule is used when the user at the destination has not specified a delivery date and time, and therefore can be used as information indicating that the delivery date and time has not been specified. Here, if the package is to be delivered jointly, the delivery company server 60a may also transmit a delivery company ID indicating which delivery company the package will be entrusted to.

[0061] When the first acquisition unit 303 of the delivery management server 30 receives data indicating that the item has been collected, waybill identification information, destination information, delivery requester information, information indicating that the delivery date and time has not been specified, and the delivery company ID indicating the contractor from the deliverer terminal 50a (step S402 in Figure 5), it stores this information in the memory unit 302 (step S403 in Figure 5). By receiving the delivery company ID representing the entrusted party, the delivery management server 30 can know that the package will be handed over from the first delivery company to the second delivery company, and even in the case of joint delivery, it can know which delivery company is responsible for the package handover and delivery section, making it possible to clarify who is responsible for the delivery of the package.

[0062] When information about the collected package is stored in the storage unit 302, the delivery management server 30 generates a delivery route corresponding to the waybill identification information. The delivery route is a route that includes bases (e.g., relay bases) that the package passes through on the way from the collection base to the address indicated by the destination information. Once the delivery route is generated, the delivery management server 30 calculates the scheduled delivery date and time based on the delivery route and the date and time the package was collected (Step S404 in Figure 5). Here, the delivery management server 30 stores in advance route data determined by the area to which the base where the package is collected based on the delivery route belongs and the area to which the address indicated by the destination information belongs, and scheduled data showing the relationship between the estimated number of days for delivery starting from the collection date and time, and can determine the estimated delivery date and time by referring to this scheduled data. This delivery route may be generated by the delivery management server 30, but may also be generated by the delivery company server 60 or the deliverer terminal 50, which then notifies the delivery management server 30 of the delivery route. The delivery scheduled date and time may be calculated by the delivery management server 30, or may be calculated by the delivery company server 60 or the deliverer terminal 50, which then notifies the delivery management server 30 of the delivery scheduled date and time.

[0063] The control unit 308 of the delivery management server 30 transmits a delivery schedule message including the waybill identification information, delivery information, delivery route, collection date and time, etc. to the delivery company server 60. In this case, since the delivery company ID representing the contractor associated with the waybill identification information is information indicating the second delivery company, the delivery schedule message is transmitted to the delivery company server 60b of the second delivery company.

[0064] When the delivery company server 60b of the second delivery company receives the delivery schedule message transmitted from the delivery management server 30 (Step S300 in FIG. 5), it writes and stores the message in the storage device of the delivery company server 60b. The delivery company server 60b of the second delivery company determines whether delivery is possible on the scheduled delivery date and time based on the address and delivery route indicated by the destination information included in the delivery schedule message and the collection date and time stored in the delivery company server 60b (FIG. 5, step S301), and sends a response regarding the scheduled delivery date and time together with the waybill identification information to the delivery management server 30. This response may be a response indicating that the scheduled delivery date and time is acceptable, or may be a different candidate date and time indicating a possible delivery date and time determined by the second delivery company instead of the scheduled delivery date and time presented by the delivery management server 30. After this response, the second delivery company starts delivering the package based on the delivery schedule message (FIG. 5, step S302).

[0065] When the control unit 308 of the delivery management server 30 receives from the delivery company server 60b a response indicating that delivery is possible on the scheduled delivery date and time and waybill identification information (step S405 in Figure 5), it stores information indicating that the scheduled delivery date and time is acceptable based on the response content and updates the scheduled delivery date and time stored in the memory unit 302 (step S406 in Figure 5). When the scheduled delivery date and time is updated, the delivery management server 30 sends a delivery wish request message to the user terminal 10b of the destination user, which is a message inquiring whether or not to change the scheduled delivery date and time (steps S407 and S408 in FIG. 5). This delivery wish request message includes, for example, waybill identification information, scheduled delivery date and time, delivery requester information, etc. The delivery request message may include a message inquiring whether or not to change the scheduled delivery date and time, or may notify the user of the scheduled delivery date and time without inquiring whether or not to change the date and time. The delivery wish request message may be sent using SMS (Short Message Service) or RCS (Rich Communication Service) with the telephone number included in the destination information as the destination. If the destination information includes an e-mail address that can be received by the user terminal 10b of the destination user, or if the e-mail address is registered in advance in the delivery management server 30, the delivery wish request message may be sent by e-mail. In addition, when sending a delivery request message to the user terminal 10b of the destination user, the delivery management server 30 may control notifications by, for example, checking the destination user's past redelivery record and specifying the allowable time for message notifications (for example, not sending notifications during late night hours).

[0066] When the user terminal 10b receives this delivery wish request message (step S501 in FIG. 5), it notifies the user that the message has been received by a ringtone, a screen display, etc. Then, in response to an instruction from the user to open the message, the user terminal 10b displays the received delivery wish request message on the display screen and transmits an open notification to the delivery management server 30 (step S502 in FIG. 5). Here, the user terminal 10b is configured to send an opening notification to the delivery management server 30, but it may also be configured to send an arrival notification to the delivery management server 30 in response to the delivery wish request message reaching the user terminal 10b.

[0067] When the delivery management server 30 receives the opening notification from the user terminal 10b, it writes the fact that the delivery wish request message has been opened in the status information (Step S409 in FIG. 5). Then, the control unit 308 of the delivery management server 30 determines whether or not a reply has been received from the destination consumer after a predetermined time has elapsed since the delivery wish request message was sent (Step S410 in FIG. 5). Here, the delivery management server 30 may proceed to processing step S410 in Figure 5 based on receiving an opening notification from the user terminal 10b, or may proceed to processing step S410 in Figure 5 in response to an arrival notification based on the delivery wish request message reaching the user terminal 10b.

[0068] The destination user checks the scheduled delivery date and time on the user terminal 10b and determines whether to change the scheduled delivery date and time. If there is no need to change the scheduled delivery date and time, the destination user does not need to reply to the delivery request message, or may reply "no change." If the user of the destination wishes to change the scheduled delivery date and time, the user inputs the desired delivery date and time into the user terminal 10b. Upon receiving this operation input from the user, the user terminal 10b transmits a change message notifying the desired delivery date and time to the delivery management server 30 (Step S503 in FIG. 5).

[0069] If the delivery management server 30 has not received a reply from the destination user terminal 10b even after a predetermined period of time has passed since sending the delivery wish request message (step S410-NO in Figure 5), it sends a message to the delivery company server 60b indicating that there has been no reply to the delivery wish request message.

[0070] The delivery company server 60b receives a message from the delivery management server 30 indicating that there has been no reply to the delivery wish request message (Step S303 in FIG. 5).

[0071] On the other hand, if the delivery management server 30 receives a change message from the user terminal 10b within a certain period of time after sending the delivery request message (step S410-YES in Figure 5, step S411), it writes the desired delivery date and time as the scheduled delivery date and time in the memory unit 302 based on this change message (step S412 in Figure 5), and sends the change message and the waybill identification information to the delivery company server 60b as a recipient desired delivery date and time message. In the following embodiment, a case will be described in which a desired delivery date and time is written in a field that stores the scheduled delivery date and time, and the desired delivery date and time is controlled to be used as the scheduled delivery date and time. However, in addition to the automatically calculated scheduled delivery date and time or the scheduled delivery date and time specified by the delivery company, fields such as a desired delivery date and time (the user's desired delivery date and time), a confirmed delivery date and time, etc. may be prepared, and control may be exercised so that information appropriate to these items is written. Then, information confirmed using each data managed using these items may be registered as the "confirmed delivery date and time." This is also true in the following embodiments.

[0072] When the delivery company server 60b receives the recipient's desired delivery date and time message (step S304 in FIG. 5), it determines whether delivery is possible according to the desired delivery date and time included in the recipient's desired delivery date and time message. The determination of whether delivery is possible may be made according to an operation input from an operator of the delivery company server 60b indicating whether delivery is possible, or may be made by determining whether the number of parcels that can be delivered at the desired delivery date and time has exceeded the number. If the delivery company server 60b determines that delivery is possible according to the desired delivery date and time, it sends a final delivery date and time decision message to the delivery management server 30 indicating that delivery is possible according to the desired delivery date and time, and if it determines that delivery is not possible at the desired delivery date and time, it sends a candidate date and time message to the delivery management server 30 indicating a candidate delivery date and time that is another scheduled delivery date. The delivery management server 30 may calculate several candidate delivery dates based on the candidate time slots available to the delivery company and the delivery status of the parcel, and transmit these to the delivery company server 60b, so that the delivery company server 60b can select from these candidate dates.

[0073] When the delivery management server 30 receives the final delivery date and time decision message or the candidate date and time message sent from the delivery company server 60b (step S413 in FIG. 5), it updates the scheduled delivery date and time stored in the storage unit 302 based on the received message (step S414 in FIG. 5). Here, if delivery is possible according to the desired delivery date and time, the process of updating the scheduled delivery date and time may be skipped, or the scheduled delivery date and time may be updated by overwriting it with the same value. Then, the delivery management server 30 transmits the delivery date and time final decision message or the candidate date and time message as a delivery date and time message to the user terminal 10b of the destination. Here, the delivery management server 30 may not send a final delivery date and time decision message if delivery is possible according to the desired delivery date and time, and may send a candidate date and time message to the destination user terminal 10b if there is a change to the desired delivery date and time.

[0074] When the user terminal 10b receives the delivery date and time message (Step S504 in FIG. 5), it displays the delivery date and time on the display screen. This allows the recipient user to check the returned delivery date and time against the desired delivery date and time. Based on the recipient user's input, the user terminal 10b sends information to the delivery management server 30 indicating whether the returned delivery date and time is acceptable or whether another desired date and time is a candidate date and time.

[0075] When the delivery management server 30 receives information from the user terminal 10b indicating whether the returned delivery date and time is acceptable or a candidate date and time that is another desired date and time, the delivery management server 30 updates the scheduled delivery date in the storage unit 302 based on the received content (FIG. 5, step S415). Here, if the returned content indicates that the delivery date and time is acceptable, the delivery management server 30 skips updating the scheduled delivery date and time stored in the storage unit 302, and if it is a candidate date and time, writes the candidate date and time as the scheduled delivery date and time. The delivery management server 30 then sends information indicating that the returned delivery date and time is acceptable, or information indicating another desired candidate date and time, as a recipient desired delivery date and time message to the delivery company server 60b.

[0076] When the delivery company server 60b receives the recipient's desired delivery date and time message (Step S306 in FIG. 5), it determines whether delivery is possible according to the desired delivery date and time included in the recipient's desired delivery date and time message. The determination of whether delivery is possible may be made according to an operation input from an operator of the delivery company server 60b indicating whether delivery is possible, or may be made by determining whether the number of parcels that can be delivered at the desired delivery date and time has been exceeded. If it is determined that delivery is possible according to the desired delivery date and time, the delivery company server 60b stores the desired delivery date and time in the storage device of the delivery company server 60b as the scheduled delivery date and time. On the other hand, if it is determined that delivery is not possible at the desired delivery date and time, the process may be executed from step S305 in Fig. 5 to continue adjusting the scheduled delivery date between the delivery management server 30 and the user terminal 10b.

[0077] Here, after a certain period of time has passed since the delivery request message was sent, if a change message is sent from the user terminal 10b (step S505 in Figure 5), and the delivery management server 30 receives the change message (step S416 in Figure 5), it determines whether or not to allow the delivery date and time to be changed (step S417 in Figure 5). Here, the delivery management server 30 determines whether the change is within the grace period set for the change even after a certain period has passed since the delivery request message was sent. If the grace period has passed, the delivery management server 30 determines that the change is not acceptable (FIG. 5, step S417-NO), and sends a message to the user terminal 10b indicating that the desired delivery date and time cannot be changed. Here, after a certain period of time has passed since the delivery request message was sent, or after the grace period has passed, it may be difficult for the second delivery company to change the date and time even if the user attempts to do so due to its delivery schedule, so changes to the desired delivery date and time may not be accepted. Furthermore, even if changes to the scheduled delivery date and time are not accepted, since there is a high possibility that the package will not arrive (due to the recipient being absent, etc.) even if the package is delivered according to the scheduled delivery date registered at that time, the delivery management server 30 may send to the user terminal 10b a message indicating that the desired delivery date and time cannot be changed, including a message indicating that the package will be temporarily stored at the delivery company's office, etc. Furthermore, the delivery company may again present (transmit) to the user terminal 10b a date on which delivery is available. Note that, here, it is determined whether or not the change is permissible in step S417 of FIG. 5, but it is also possible to allow all changes without determining whether or not the change is permissible, or to disallow all changes. Also, here, the processing of step S505 in FIG. 5 is the starting point, and the processing has been described for when a delivery request message is sent and a change message is sent from user terminal 10b after a certain period of time has passed. However, instead of a period of time, the processing from step S505 in FIG. 5 may be executed when the number of times the delivery date and time have been changed reaches a predetermined number.

[0078] When the user terminal 10b receives the message indicating that the desired delivery date and time cannot be changed (Step S506 in FIG. 5), the user terminal 10b displays a message indicating that the desired delivery date and time cannot be changed on the display screen, thereby letting the user of the user terminal 10b know that the desired delivery date and time cannot be changed.

[0079] On the other hand, if the grace period has not expired, the delivery management server 30 determines that the change is acceptable (step S417 in Figure 5 - YES), updates the scheduled delivery date stored in the memory unit 302 based on the desired delivery date and time (step S418 in Figure 5), and sends a change message to the delivery company server 60b notifying it of the updated scheduled delivery date.

[0080] When the delivery company server 60b receives the change message notifying the updated scheduled delivery date (step S308 in FIG. 5), it writes the received scheduled delivery date into the storage device of the delivery company server 60b.

[0081] <On the day of delivery (just before) phase> When the scheduled delivery date arrives, the delivery company server 60b updates the storage device of the delivery company server 60b with information about the delivery status according to the route and other factors for delivery of packages whose scheduled delivery date and time corresponds to the delivery date (step S309 in FIG. 5), and then transmits the delivery status information, including the route and other factors, to the delivery management server 30 (step S310 in FIG. 5). Here, the processing of steps S309 and S310 in FIG. 5 is performed for packages whose scheduled delivery date and time corresponds to the current day. However, the processing of steps S309 and S310 in FIG. 5 may also be performed for packages that are a certain period of time before the scheduled delivery date and time. The certain period of time may be one day before the scheduled delivery date and time, or may be a period when the scheduled delivery date and time is relatively close, such as two or three days before.

[0082] When the delivery management server 30 receives the delivery status from the delivery company server 60b, it updates the status stored in the memory unit 302 based on the delivery status, the route, etc. (Step S419 in Figure 5), and calculates the estimated arrival time at the destination address (Step S420 in Figure 5). This estimated arrival time may be calculated by the delivery management server 30, or may be calculated by the delivery company server 60 or the deliverer terminal 50, which then notifies the delivery management server 30 of the calculated estimated arrival time. The estimated arrival time may be calculated for packages whose scheduled delivery date and time corresponds to the current day, or may be calculated for packages a certain period of time before the scheduled delivery date and time. The certain period of time may be one day before the scheduled delivery date and time, or may be a period when the scheduled delivery date is relatively close, such as two or three days before. The delivery management server 30 calculates the estimated arrival time for each package based on the number of packages, the destination address, the route, etc. When calculating the estimated arrival time, the delivery management server 30 may also use information such as the number of packages, the destination address, and the route, as well as past redelivery attempts (tendencies in times of absence), and whether deliveries are not made during late night hours. The delivery management server 30 then transmits the calculated estimated arrival time to the delivery company server 60b.

[0083] When the delivery company server 60b receives the estimated arrival time from the delivery company server 60b (FIG. 5, step S312), it transmits the estimated arrival time to the delivery person terminal 50b of the delivery person of the second delivery company. This allows the delivery person of the delivery person terminal 50b to confirm the estimated arrival time (FIG. 5, step S313). The deliverer terminal 50 or the delivery company server 60b sends an estimated arrival time confirmation completion message indicating that the estimated arrival time has been confirmed to the delivery management server 30. Here, if the delivery person at the deliverer terminal 50b can confirm the estimated arrival time, it is not necessarily necessary to send the estimated arrival time confirmation completion message to the delivery management server 30.

[0084] When the delivery management server 30 receives an estimated arrival time confirmation completion message from the delivery company server 60b (step S421 in FIG. 5), it transmits an estimated arrival time message notifying the estimated arrival time to the user terminal 10b (steps S422 and S423 in FIG. 5). When sending an estimated arrival time message to the user terminal 10b of the recipient user, the delivery management server 30 may control notifications by, for example, taking into account the recipient user's past redelivery attempts and specifying the allowable time for message notifications (e.g., not sending notifications during late night hours). For example, the delivery management server 30 may calculate the estimated arrival time on the day before the scheduled delivery date indicated by the scheduled delivery date and time, and send the message notification on the day before. Also, if the time period indicated by the scheduled arrival date and time is early in the morning on the scheduled delivery date (e.g., 10:00 AM), sending the estimated arrival time message around 8:00 AM or 9:00 AM on the scheduled delivery date will result in the recipient user receiving the estimated arrival time message just before the scheduled delivery time (e.g., 1 to 2 hours before). This is because the recipient user may become aware of the delivery when the scheduled arrival time is approaching, which may give the impression that the notification timing is late. In addition, here, if the time period indicated by the scheduled delivery time is in the morning, the estimated arrival time message may be sent the day before, and if the time period indicated by the scheduled delivery time is in the afternoon, the estimated arrival time message may be sent in an early time period (for example, in the morning) on ​​the scheduled delivery day.

[0085] When the user terminal 10b receives the estimated arrival time message (step S507 in FIG. 5), it notifies the user that the message has been received by a ringtone, a screen display, etc. Then, in response to an instruction from the user to open the message, the user terminal 10b displays the estimated arrival time message on the display screen and transmits an opening notification to the delivery management server 30 (step S507A in FIG. 5). Here, the estimated arrival time message may include content inquiring whether there has been any change to the estimated arrival time, or may notify the estimated arrival time without inquiring whether there has been any change. Here, the user terminal 10b is configured to send an opening notification to the delivery management server 30, but it may also be configured to send an arrival notification to the delivery management server 30 in response to the delivery wish request message reaching the user terminal 10b.

[0086] When the delivery management server 30 receives the opening notification from the user terminal 10b, it writes the fact that the estimated arrival time message has been opened in the status information. Then, the control unit 308 of the delivery management server 30 determines whether or not a reply has been received from the destination consumer after a predetermined time has elapsed since the estimated arrival time message was sent (Step S425 in FIG. 5). Here, the delivery management server 30 may proceed to processing step S425 in Figure 5 based on receiving an opening notification from the user terminal 10b, or may proceed to processing step S425 in Figure 5 in response to an arrival notification based on the delivery wish request message reaching the user terminal 10b.

[0087] The destination user checks the estimated arrival time on the user terminal 10b and determines whether to change the estimated arrival time. If the destination user does not need to change the estimated arrival time, they may not reply to the estimated arrival time message or may reply "no change." Furthermore, if the destination user wishes to change the estimated arrival time, the desired delivery date and time is entered into user terminal 10b, which then transmits the desired delivery date and time as a change message to delivery management server 30 (FIG. 5, step S508). Here, the destination user has registered the desired delivery date and time or confirmed the scheduled delivery date and time in advance, but if they are unable to make it on the day of delivery, they can change the desired delivery date and time. This allows a user who suddenly becomes unable to make it on the day of delivery to have the delivery scheduled for a different date and time, thereby preventing the delivery company from visiting the user while they are absent to make the delivery.

[0088] If a predetermined time has passed since the delivery management server 30 sent the estimated arrival time message but the delivery management server 30 has not received a reply from the destination user terminal 10b (step S425-NO in Figure 5), the delivery management server 30 sends a message to the delivery company server 60b indicating that there has been no reply to the estimated arrival time message.

[0089] When the delivery company server 60b receives a message from the delivery management server 30 indicating that there has been no reply to the estimated arrival time message (FIG. 5, step S314), it may send a message indicating that there has been no reply to the estimated arrival time message to the delivery person terminal 50b of the delivery person of the second delivery company. This allows the delivery person at the delivery person terminal 50b to understand that there has been no reply to the estimated arrival time message. Therefore, it can be understood that the destination user does not currently wish to change the estimated arrival time.

[0090] On the other hand, if the delivery management server 30 receives a change message from the user terminal 10b changing the desired arrival date and time within a certain period of time after sending the estimated arrival time message (step S425 in Figure 5 - YES), it updates the estimated arrival time stored in the memory unit 302 based on this change message changing the desired arrival date and time by writing it as the recipient's desired arrival date and time based on the desired arrival date and time (step S426 in Figure 5), and sends it to the delivery company server 60b as a recipient's desired arrival date and time message.

[0091] When the delivery company server 60b receives the recipient desired arrival date and time message (FIG. 5, step S315), it determines the arrival date and time according to the desired arrival date and time included in the recipient desired arrival date and time message (FIG. 5, step S316). Here, the delivery company server 60b sends the recipient desired arrival date and time message to the delivery person's delivery terminal 50b. This allows the delivery person at the delivery person terminal 50b to confirm the desire to change the arrival date and time based on the recipient desired arrival date and time message. On the other hand, if the delivery person at the deliverer terminal 50 cannot accommodate the arrival date and time requested by the destination user, the delivery person inputs another candidate date and time from the deliverer terminal 50, transmits it to the delivery company server 60b, and if the change is acceptable, presses the "OK" button to allow the change and send a notification to determine the arrival date and time. Based on the content transmitted from the deliverer terminal 50, the delivery company server 60b transmits to the delivery management server 30 a message determining the arrival date and time or a message informing of other candidate dates and times. The delivery management server 30 may calculate several candidate delivery dates based on the candidate time slots available to the delivery company and the delivery status of the parcel, and transmit these to the delivery company server 60b, so that the delivery company server 60b can select from these candidate dates.

[0092] When the delivery management server 30 receives a message from the delivery company server 60b to determine the arrival date and time or a message informing of another candidate date, it either leaves the scheduled delivery date stored in the storage unit 302 as is or updates it to another candidate date based on the content of the message (FIG. 5, step S428).The delivery management server 30 then sends to the user terminal 10b an arrival date and time message informing that delivery is possible at the desired arrival date and time, or a candidate date and time message informing of another candidate date.

[0093] When the user terminal 10b receives the arrival date and time message or the candidate date and time message, it notifies the user that the message has been received by using a ringtone, a screen display, or the like. Then, in response to a command from the user to open the message, the user terminal 10b displays the arrival date and time message or the candidate date and time message on the display screen (step S509 in FIG. 5). This allows the user of the user terminal 10b to check the contents of the message. Then, based on the operation input of the destination user, the user terminal 10b presses an "OK" button indicating that the user agrees with the arrival date and time indicated in the arrival date and time message, or presses an "OK" button indicating that the user agrees with the candidate date and time based on the candidate date and time message. Alternatively, if the user wishes to further change the arrival date and time, the user can input another candidate date and time into the user terminal 10b. Here, the delivery management server 30 may not send an arrival date and time message if delivery is possible according to the desired delivery date and time, and may send a candidate date and time message to the destination user terminal 10b if there is a change to the desired delivery date and time.

[0094] When the delivery management server 30 receives from the user terminal 10b any of information indicating agreement on the arrival date and time, information indicating agreement on the candidate date and time, and information indicating another candidate date and time (FIG. 5, step S510), it updates the scheduled delivery date in the storage unit 302 based on the received content (FIG. 5, step S429). Here, if the returned content indicates that the arrival date and time or the candidate date and time is sufficient, the delivery management server 30 may skip updating the scheduled delivery date and time stored in the storage unit 302, or may update it. Also, if the returned content is another candidate date and time, the delivery management server 30 writes the other candidate date and time as the scheduled delivery date and time. The delivery management server 30 then transmits information indicating the arrival date and time or the candidate date and time, or another desired date and time, to the delivery company server 60b as a recipient desired delivery date and time message.

[0095] When the delivery company server 60b receives the recipient's desired delivery date and time message (FIG. 5, step S317), it determines whether it can accommodate the request based on any of the information included in the recipient's desired delivery date and time message indicating agreement on the arrival date and time, information indicating agreement on a candidate date and time, or information indicating another candidate date and time. The determination of whether it can accommodate the request may be made based on an operation input from an operator of the delivery company server 60b indicating whether it can accommodate the request, or it may be made by sending the recipient's desired delivery date and time message to the deliverer terminal 50, having the delivery person at the deliverer terminal 50b check the recipient's desired delivery date and time message (FIG. 5, step S318), and determining whether it can accommodate the request based on the content entered as a result.

[0096] If it is determined that delivery is possible according to the desired delivery date and time, the delivery company server 60b stores the desired delivery date and time in the storage device of the delivery company server 60b as the scheduled delivery date and time. Here, the delivery company server 60b may notify the delivery management server 30 that the desired delivery date and time has been confirmed as the scheduled delivery date and time. On the other hand, if it is determined that delivery is not possible at the desired delivery date and time, the process may be executed from step S316 in FIG. 5, so that adjustment of the scheduled delivery date can continue between the delivery management server 30 and the user terminal 10b.

[0097] When the driver arrives at the delivery destination at a time corresponding to the desired delivery date and time based on the destination information corresponding to the waybill identification information (step S319 in Fig. 5), the driver hands the package over to the user at the destination (step S320 in Fig. 5). The user at the destination receives the package (step S511 in Fig. 5). The user at the destination reads the waybill identification information attached to the package using user terminal 10b, and obtains the destination information associated with the waybill identification information and information about the delivery requester from delivery management server 30, thereby being able to confirm that the package is addressed to them, the delivery requester, etc.

[0098] When the package is handed over, an input regarding "delivery completed" is made. The input regarding "delivery completed" may be made by the user of the destination pressing a "receipt completed" button on the user terminal 10b owned by the user, which transmits the waybill identification information and information indicating "receipt completed" from the user terminal 10b to the delivery company server 60b or the delivery management server 30 (step S512 in FIG. 5). Furthermore, the input regarding "delivery completed" may be made by the driver inputting the waybill identification information and information indicating "delivery completed" into the deliverer terminal 50, which then transmits the waybill identification information and the information indicating "delivery completed" from the deliverer terminal 50 to the delivery company server 60b. Furthermore, if there is a copy of the delivery slip for the destination used by the second delivery company, the user at the destination may stamp the copy of the delivery slip to indicate that the package has been received, and the driver may take this copy of the delivery slip back to the base (office, etc.) of the second delivery company, confirm that it has been stamped, and then an operator may input "delivery completed" from the terminal device of the second delivery company installed at the base.

[0099] When the delivery company server 60b of the second delivery company receives the information corresponding to "Delivery Completed" and the waybill identification information from the deliverer terminal 50b or the user terminal 10b, it writes "Delivery Completed" to the storage device of the delivery company server 60b (Step S320A in FIG. 5). Then, the delivery company server 60b performs status information linking processing by sending the waybill identification information and delivery completion information indicating "Delivery Completed" to the delivery management server 30 (Step S321 in FIG. 5).

[0100] The delivery status acquisition unit 3041 of the delivery management server 30 acquires the waybill identification information and delivery completion information indicating "delivery completed" by receiving it from the delivery company server 60b (Step S430 in FIG. 5). Then, the first processing unit 305 of the delivery management server 30 associates the waybill identification information with the information indicating "delivery completed" based on the information acquired by the delivery status acquisition unit 3041, and stores the information by writing it into the storage unit 302 (Step S431 in FIG. 5).

[0101] Here, the information indicating "delivery completed" is notified from the delivery company server 60b of the second delivery company, which is the outsourcee, to the delivery management server 30. However, the information indicating "delivery completed" and the waybill identification information may be sent from the delivery company server 60b of the second delivery company to the delivery company server 60a of the first delivery company, and the information indicating "delivery completed" and the waybill identification information may be sent from the delivery company server 60a to the delivery management server 30. For example, if a first delivery company outsources delivery of a package to a second delivery company, but the first delivery company, which is the outsourcee, is managing the package, the information indicating "delivery completed" may be sent from the delivery company server 60a to the delivery management server 30. Furthermore, for example, if a malfunction occurs in the delivery company server 60b of the second delivery company and it is unable to send information indicating "delivery completed" to the delivery management server 30, the second delivery company may contact the first delivery company to inform them of delivery completion, and then the delivery company server 60a of the first delivery company may send information indicating "delivery completed" and the waybill identification information on their behalf.

[0102] When information indicating "delivery completed" is written, the delivery management server 30 may perform status information linking processing by sending the waybill identification information and the information indicating "delivery completed" to the delivery company server 60a.

[0103] Second Embodiment In the second embodiment, an operation will be described in which a product is delivered as a parcel in response to a purchase of a product put up for sale on the EC site server 70 in the delivery system S shown in Fig. 1. Figs. 6A, 6B, 6C, 6D, 6E, 6F, 6G, 6H, and 6I are sequence diagrams showing the operation of the delivery system S.

[0104] <Preparation Phase> The control unit 308 of the delivery management server 30 generates an EC site ID that can identify the EC site operated by the EC site server 70, and also generates a delivery company ID that identifies each delivery company (step S440 in Figure 6), and sends the EC site ID and each delivery company ID to the EC site server 70, the delivery company server 60a, and the delivery company server 60b, respectively (steps S441, S442, S443 in Figure 6).

[0105] When the EC site server 70 receives the EC site ID and each delivery company ID from the delivery management server 30, it stores them in a storage unit within the EC site server 70 (Step S640 in FIG. 6). When the delivery company server 60a receives the EC site ID and each delivery company ID from the delivery management server 30, it stores them in the storage unit within the delivery company server 60a (Step S240 in FIG. 6). When the delivery company server 60b receives the EC site ID and each delivery company ID from the delivery management server 30, it stores them in the storage unit within the delivery company server 60b (Step S340 in FIG. 6).

[0106] When a user of the user terminal 10a puts a product up for sale on an EC site operated by the EC site server 70, the user accesses the EC site operated by the EC site server 70 from the user terminal 10a at the first time of use, enters customer information, and performs a new registration procedure (step S140 in FIG. 6). The user terminal 10a accepts the user's name, address, telephone number, etc. as customer information based on input operations from the user, and transmits this customer information to the EC site server 70 (step S141 in FIG. 6).

[0107] On the other hand, when a user of the user terminal 10b purchases a product from an EC site operated by the EC site server 70, the user accesses the EC site operated by the EC site server 70 from the user terminal 10b for the first time, enters customer information, and performs a new registration procedure (step S540 in FIG. 6). When performing the new registration procedure, the user may register a notification method for receiving messages regarding package delivery from the EC site. For example, the user may be asked to select either a notification method in which a notification is sent from the EC site to an EC site app running on the user terminal 10b, or a notification method in which a message is sent directly from the delivery management server 30 to the user terminal 10b. The user may also be asked to select one of notification methods such as RCS (Rich Communication Services), SMS (Short Message Service), and email. The user terminal 10b accepts the user's name, address, telephone number, etc. as customer information based on input operations from the user, and transmits this customer information to the EC site server 70 (Step S541 in FIG. 6).

[0108] The EC site server 70 stores the customer information received from the user terminal 10a and the customer information received from the user terminal 10b in the storage unit of the EC site server 70 (Step S641 in FIG. 6). The EC site server 70 issues a customer ID to identify the customer in response to the customer information received from the user terminal 10a, associates it with the customer information, and stores it in the storage unit of the EC site server 70. The EC site server 70 notifies the user terminal 10a of the issued customer ID and notifies that customer registration has been completed. This completes customer registration for the user who is the seller (the user who has made the delivery request). Furthermore, the EC site server 70 issues a customer ID for identifying the customer in response to the customer information received from the user terminal 10b, associates it with the customer information, and stores it in the storage unit of the EC site server 70. The EC site server 70 notifies the user terminal 10b of the issued customer ID and notifies that customer registration has been completed. This completes customer registration for the user who will be the purchaser (user who will be the recipient).

[0109] Also, in the preparation phase, the delivery management server 30 may assign an available waybill number range to issue waybill identification information, as in step S400 of Figure 5. Here, the delivery management server 30 may use waybill identification information prepared by each delivery company without assigning an available waybill number range. When using waybill identification information prepared by the delivery company, it may use a waybill L that reflects the prepared destination identification information, or it may use a delivery slip prepared by the delivery company.

[0110] <Purchase Phase> When a user of the user terminal 10a puts a product up for sale on an EC site, the user inputs product information and a delivery method into the user terminal 10a (step S142 in FIG. 6). Based on the user's operational input, the user terminal 10a transmits the product information and information indicating the delivery method to the EC site server 70 (step S143 in FIG. 6). The product information may include image data representing an external appearance of the product, the product name, product specifications, product price, a description of shipping fees, a description of the delivery method, a description of the product, etc. The delivery method includes a delivery company ID, a delivery type (regular, refrigerated, etc.), package size, etc. Here, the user who puts up the product may specify the delivery company, or the purchaser, who is the recipient of the package, may specify the delivery company, or the delivery management server 30 may select a delivery company with favorable conditions depending on the delivery situation, etc. The delivery company may be decided when the product is put up for sale, or may be decided when the purchase is decided.

[0111] The EC site server 70 associates the product information, information indicating the delivery method, and the user's customer information transmitted from the user terminal 10a and stores them as listing information in the storage device of the EC site server 70 (step S642 in FIG. 6).The EC site server 70 then publishes the listing details on the EC site based on the stored listing information.

[0112] The user of the user terminal 10b accesses the EC site published by the EC site server 70 using the user terminal 10b and performs an operation input to purchase the product to be purchased (step S542 in FIG. 6). Here, based on the operation input from the user, the user terminal 10b accesses the EC site server 70, displays data such as the product image, price, description, price, and delivery method, and based on the operation input to purchase, sends a purchase request and instructions on the delivery method to the EC site server 70 (step S543 in FIG. 6). As an instruction on the delivery method, it is possible to specify a delivery date and time, but in this case, the delivery date and time has not been specified (e.g., unanswered or undecided). The purchase request includes information that can identify the product to be purchased, customer information of the user who is the purchaser, a payment method, etc.

[0113] When the EC site server 70 receives a purchase request and instructions on how to receive the product from the user terminal 10b, it associates the product information with the fact that the product requested for purchase has already been purchased, the customer information of the purchaser, the payment method, instructions on how to receive the product, etc., and stores them in the storage device of the EC site server 70 (step S643 in Figure 6). The EC site server 70 then sends the EC site ID, recipient customer information (customer information of the user who is the purchaser), delivery company ID based on the delivery method, and receipt method (here, receipt date and time is not specified) to the delivery management server 30 (steps S644 and S645 in Figure 6).

[0114] The delivery management server 30 receives the EC site ID, recipient customer information (customer information of the user who is the purchaser), a delivery company ID based on the delivery method, and a receiving method (here, receiving date and time is not specified) from the EC site server 70, and writes these to the storage unit 302 of the delivery management server 30 as data related to the package to be delivered (step S444 in FIG. 6). Here, the delivery management server 30 assigns a customer ID to the recipient customer information and stores it in association with the waybill identification information. The customer ID assigned here may be the customer ID issued at the time of customer registration in step S641 in FIG. 6 described above.

[0115] The delivery management server 30 also generates waybill identification information to be used when delivering the parcel to be delivered and stores it in association with data related to the parcel to be delivered. Here, the delivery management server 30 may generate new waybill identification information, or may extract and use unused waybill identification information from the waybill use number range issued to the EC site server 70 or the delivery company corresponding to the delivery company ID. Alternatively, the delivery management server 30 may use waybill identification information that has been independently prepared by the delivery company corresponding to the delivery company ID and that has been notified to the delivery management server 30 in advance as available for use. The delivery management server 30 then generates a two-dimensional barcode for the waybill identification information. The delivery management server 30 then transmits the generated two-dimensional barcode, delivery company ID, customer ID, and waybill identification information to the EC site server 70 (step S445 in Figure 6), and also transmits the EC site ID, customer ID, and waybill identification information to the delivery company server 60b of the second delivery company, which is the delivery company corresponding to the delivery company ID (step S446 in Figure 6).

[0116] When the EC site server 70 receives the two-dimensional barcode, delivery company ID, and waybill identification information from the delivery management server 30, it associates these with the product information and stores them in the storage device of the EC site server 70 (Step S645A in FIG. 6).

[0117] When the delivery company server 60b receives the EC site ID, customer ID, and invoice identification information, it stores them in the storage device of the delivery company server 60b (Step S341 in FIG. 6). Here, since the purchased product is in the shipping preparation stage and has not yet been collected, a status indicating that the product is waiting for collection is written.

[0118] <Delivery start phase> The EC site server 70 transmits the two-dimensional barcode information, delivery company ID, customer ID, invoice identification information, payment method, etc., associated with the product information of the purchased product to the user terminal 10a of the user who is the seller of the product (step S646 in FIG. 6). Here, the customer ID is transmitted instead of the customer information (name, address, etc.) of the purchaser being transmitted to the user terminal 10a, so that the shipping process can be carried out without disclosing the name and address of the purchaser to the seller.

[0119] The user terminal 10a receives the two-dimensional barcode information, the delivery company ID, the customer ID, the waybill identification information, and the payment method, and displays the two-dimensional barcode on the display screen based on the two-dimensional barcode information (FIG. 6, step S144). This allows the user who put up the item to know that the item has been purchased by the buyer. The seller then packs up the purchased item, brings it to a collection point (e.g., a convenience store), and hands it over at the collection point. At the same time, the seller displays the two-dimensional barcode on the display screen of the user terminal 10a, and has it read by a barcode scanner of a terminal device (e.g., POS terminal 20) at the collection point. Once the reading of the two-dimensional barcode is complete, the user who is the seller inputs an operation input indicating that the shipping procedure has been completed into the user terminal 10a. As a result, the user terminal 10a transmits a notification of a collection request to the delivery company server 60b of the second delivery company, along with the waybill identification information and the customer ID, based on the delivery company ID (step S145 in FIG. 6). Here, the user terminal 10a may transmit the notification of the collection request to the delivery management server 30, along with the delivery company ID, waybill identification information, and customer ID of the delivery company server 60b of the second delivery company, and the delivery management server 30 may transmit the waybill identification information and the customer ID to the delivery company server 60b of the second delivery company corresponding to the delivery company ID. Furthermore, since the customer information of the user (seller) who has requested delivery and the customer ID are associated with the waybill identification information and stored in the delivery management server 30, the user who is the seller does not need to enter the delivery destination information or information about the user who has requested delivery into the user terminal 10a. If the seller does not want the buyer to know the name, address, etc. of the seller, the seller can request delivery without disclosing this information to the buyer (anonymous delivery), or the seller can be assigned a seller ID that identifies the seller and communicate the seller ID to the buyer as the sender of the delivery request. This seller ID may be the customer ID issued to the seller when registering the customer in step S641 of Figure 6 described above. If the seller does not want to know the buyer's name, address, etc., the buyer can request delivery without disclosing the information to the seller (anonymous delivery), or the buyer can be assigned a buyer ID that identifies the buyer and communicate the buyer ID to the seller's user as the recipient (purchaser). This buyer ID may be the customer ID issued to the buyer when registering as a customer in step S641 of Figure 6 above.

[0120] When the POS terminal 20 reads the two-dimensional barcode, it may transmit the read two-dimensional barcode to the delivery management server 30 and make a collection request. The POS terminal 20 also causes a printer to print the read two-dimensional barcode on a printing medium of the shipping label L. The parcel receptionist at the collection point who operates the POS terminal 20 attaches the printed two-dimensional barcode to the parcel. The parcel is then stored.

[0121] When the delivery company server 60b of the second delivery company receives the collection request notification along with the waybill identification information from the user terminal 10a, it associates the status information with the waybill identification information stored in the storage device, rewrites the status information to "Collection Requested," and sends a message instructing the delivery to the delivery terminal 50a carried by the driver in charge of collection. When the delivery driver in charge of collection receives the collection message at the delivery terminal 50a, he or she goes to the collection base, collects the package, and reads the two-dimensional barcode attached to the collected package with the delivery terminal 50a (step S342 in Figure 6). The driver in charge of collection then delivers the package to the relay base. Based on the identification information assigned to the POS terminal 20 that read the two-dimensional barcode on the package, the driver in charge of collection can identify the base where the package was collected and go to that base. In addition, upon collection, the delivery company server 60b sends to the delivery management server 30 a message indicating that a collection request has been made, including the delivery company ID, customer ID, waybill identification information (steps S343 and S344 in FIG. 6).

[0122] When the delivery management server 30 receives the delivery company ID, customer ID, waybill identification information, and a message indicating that a collection request has been made from the delivery company server 60b, it associates the delivery company ID, customer ID, waybill identification information, and stores the status information as "Collected" in the storage unit 302. The delivery management server 30 then reads the recipient customer information (customer information of the purchaser user) and receiving method corresponding to the waybill identification information (step S447 in FIG. 6), and transmits these to the delivery company server 60b together with the waybill identification information (step S448 in FIG. 6). In this case, since the receiving date and time has not been specified, a receiving method indicating that it has not been specified is transmitted.

[0123] When the delivery company server 60b receives the recipient customer information (customer information of the purchaser user), the receiving method, and the waybill identification information for the waybill identification information from the delivery management server 30, it writes the recipient customer information and the receiving method in the memory device of the delivery company server 60b in association with the waybill identification information (step S345 in Figure 6). Then, the delivery company server 60b transmits the delivery company ID, the customer ID, and the waybill identification information to the delivery management server 30 (Step S346 in FIG. 6).

[0124] When the delivery management server 30 receives the delivery company ID, customer ID, and waybill identification information from the delivery company server 60b, it writes the completion of the processing related to the collection of the package as status information in the memory unit 302, corresponding to the waybill identification information (step S449 in Figure 6). Then, the delivery management server 30 transmits the customer ID, the waybill identification information, and the status information (indicating that the collection process has been completed) to the EC site server 70 (Step S450 in FIG. 6).

[0125] When the EC site server 70 receives the customer ID, waybill identification information, and status information (indicating that the collection process has been completed) from the delivery management server 30, it stores this information in the memory device of the EC site server 70, thereby registering that the collection process has been completed (step S647 in Figure 6).

[0126] Next, the delivery management server 30 calculates the scheduled delivery date and time for the collected package (step S451 in FIG. 6). The method for calculating the scheduled delivery date and time may be the same as step S404 in FIG. 5. This calculation of the scheduled delivery date and time may be performed by the delivery management server 30, or may be performed by the delivery company server 60 or the deliverer terminal 50, which may then notify the delivery management server 30 of the scheduled delivery date and time. Once the scheduled delivery date and time is obtained, the control unit 308 of the delivery management server 30 transmits a delivery schedule message to the delivery company server 60b of the second delivery company (Step S452 in FIG. 6).

[0127] When the delivery company server 60b of the second delivery company receives the delivery schedule message sent from the delivery management server 30, it writes it to the storage device of the delivery company server 60b and stores it. The delivery company server 60b of the second delivery company determines whether delivery is possible on the scheduled delivery date and time based on the address, delivery route, and collection date and time indicated by the destination information included in the delivery schedule message (step S347), and sends a response regarding the scheduled delivery date and time to the delivery management server 30 together with the waybill identification information (step S348 in Figure 6). This response may be a response indicating that the scheduled delivery date and time is acceptable, or it may be a response indicating a possible delivery date and time determined by the second delivery company instead of the scheduled delivery date and time presented by the delivery management server 30. After this reply, the second delivery company starts delivering the package based on the delivery schedule message (Step S349 in FIG. 6).

[0128] When the control unit 308 of the delivery management server 30 receives the reply and the waybill identification information from the delivery company server 60b, it updates the scheduled delivery date and time stored in the storage unit 302 based on the reply content (Step S453 in FIG. 6). When the scheduled delivery date and time is updated, the delivery management server 30 sends a delivery request message to the EC site server 70 (steps S454 and S455 in FIG. 6). This delivery request message includes, for example, waybill identification information, scheduled delivery date and time, etc. In addition, when sending a delivery request message to the EC site server 70, the delivery management server 30 may control notifications by checking the destination user's past redelivery history and specifying the allowable time for message notifications (for example, not sending notifications during late night hours).

[0129] When the EC site server 70 receives the delivery wish request message from the delivery management server 30, it publishes the scheduled delivery date and time on the EC site so that it can be viewed from the user terminal 10b (step S648 in FIG. 6). For example, it can be made viewable from the user terminal 10b by posting it on a user-only page that can be accessed by logging in from the user terminal 10b. Here, the delivery wish request message may be sent from the delivery management server 30 to the EC site server 70 and may be viewable on a user-specific page, or the delivery management server 30 may notify the user terminal 10b without going through the EC site server 70. Based on the waybill identification information included in the delivery wish request message and the destination information of the user terminal 10b included in the customer information of the purchaser associated with the waybill identification information, the delivery wish request message is sent to the user terminal 10b (step S649 in FIG. 6). This delivery wish request message may be sent using the message exchange function of the EC site app for browsing the EC site, or may be sent using SMS (Short Message Service) or RCS (Rich Communication Service) with the telephone number included in the destination information as the destination. Furthermore, if an email address that can be received by the user terminal 10b of the destination user has been registered in advance as customer information in the delivery management server 30, or if it is included in the destination information, the delivery wish request message may be sent by email.

[0130] When the user terminal 10b receives this delivery request message, it notifies the user that the message has been received by a ringtone, a screen display, or the like (step S544 in FIG. 6). Then, in response to an instruction from the user to open the message, the user terminal 10b displays the received delivery request message on the display screen and transmits an opening notification to the EC site server 70 (step S545 in FIG. 6). Here, the delivery request message may include content inquiring whether or not to change the scheduled delivery date and time, or may notify the scheduled delivery date and time without inquiring whether or not to change it. Also, here, the user terminal 10b is configured to send an opening notification to the EC site server 70, but it may also be configured to send an arrival notification to the EC site server 70 in response to the delivery wish request message reaching the user terminal 10b.

[0131] When the EC site server 70 receives the opening notification from the user terminal 10b, it transmits opening information indicating that the item has been opened together with the waybill identification information to the delivery management server 30 (Step S650 in FIG. 6).

[0132] When the delivery management server 30 receives the opening information and the waybill identification information from the EC site server 70, it stores the opening information in the storage unit 302 in association with the waybill identification information (step S456 in FIG. 6). As a result, status information indicating that the delivery wish request message has been opened is written. Then, the control unit 308 of the delivery management server 30 determines whether or not a reply has been received from the destination consumer after a predetermined time has elapsed since the delivery wish request message was sent (step S457 in FIG. 6). Here, the delivery management server 30 may proceed to processing step S457 based on receiving an opening notification from the user terminal 10b, or may proceed to processing step S457 in response to an arrival notification based on the delivery wish request message reaching the user terminal 10b.

[0133] The destination user checks the scheduled delivery date and time on the user terminal 10b and determines whether to change the scheduled delivery date and time. If there is no need to change the scheduled delivery date and time, the destination user does not need to reply to the delivery request message, or may reply "no change." If the destination user wishes to change the scheduled delivery date and time, the destination user inputs the desired delivery date and time into the user terminal 10b. Based on the user's operational input, the user terminal 10b transmits the desired delivery date and time as a change message to the EC site server 70 (Step S546 in FIG. 6).

[0134] In addition, if the delivery management server 30 has not received a reply from the destination user terminal 10b even after a predetermined period of time has passed since sending the delivery wish request message (step S457-NO in Figure 6), it sends a message to the delivery company server 60b indicating that there has been no reply to the delivery wish request message.

[0135] The delivery company server 60b receives a message from the delivery management server 30 indicating that there has been no reply to the delivery wish request message (Step S350 in FIG. 6).

[0136] When the EC site server 70 receives the change message from the user terminal 10b, it accepts the change to the desired delivery date and time (step S651 in FIG. 6) and transmits the change message to the delivery management server 30 (step S652 in FIG. 6).

[0137] If the delivery management server 30 receives a change message from the EC site server 70 within a certain period of time after sending the delivery request message (step S457 in Figure 6 - YES), it writes the desired delivery date and time as the recipient's desired delivery date and time into the scheduled delivery date and time based on this change message (step S458 in Figure 6), and sends the desired delivery date and time to the delivery company server 60b as a recipient's desired delivery date and time message (step S459 in Figure 6).

[0138] When the delivery company server 60b receives the recipient's desired delivery date and time message, it determines whether delivery is possible according to the desired delivery date and time included in the recipient's desired delivery date and time message (FIG. 6, step S351). The determination of whether delivery is possible may be made according to an operation input from an operator of the delivery company server 60b indicating whether delivery is possible, or may be made by determining whether the number of parcels that can be delivered at the desired delivery date and time has exceeded the number. If the delivery company server 60b determines that delivery is possible according to the desired delivery date and time, it sends a final delivery date and time determination message to the delivery management server 30 indicating that delivery is possible according to the desired delivery date and time, and if it determines that delivery is not possible at the desired delivery date and time, it sends a candidate date and time message to the delivery management server 30 indicating a candidate delivery date and time that is another scheduled delivery date (Figure 6, step S352). Here, in response to a request from the delivery company server 60b, the delivery management server 30 may extract multiple other candidate dates and times from the candidate time periods that the delivery company can handle and the delivery status of the package, and send them to the delivery company server 60b.

[0139] When the delivery management server 30 receives the final delivery date and time decision message or the candidate date and time message sent from the delivery company server 60b, it updates the scheduled delivery date and time in the storage unit 302 based on the received message (step S459 in FIG. 6). Here, if delivery is possible according to the desired delivery date and time, the process of updating the scheduled delivery date and time may be skipped, or the scheduled delivery date and time may be updated by overwriting it with the same value. Then, the delivery management server 30 transmits the delivery date and time finalization message or the candidate date and time message as a delivery date and time message to the EC site server 70 (Step S460 in FIG. 6).

[0140] When the EC site server 70 receives the delivery date and time message from the delivery management server 30, it makes the final delivery date and time message or the candidate delivery date and time message included in the delivery date and time message publicly available on the EC site so that it can be viewed from the user terminal 10b (step S653 in FIG. 6). For example, it can be made available for viewing from the user terminal 10b by posting it on a user-only page that can be accessed by logging in from the user terminal 10b. The EC site server 70 also transmits a delivery date and time message to the user terminal 10b. Here, the delivery date and time message may be sent from the delivery management server 30 to the EC site server 70 and may be viewable on a user-specific page, or may be notified from the delivery management server 30 to the user terminal 10b without going through the EC site server 70.

[0141] When the user terminal 10b receives the delivery date and time message, it notifies the user that the message has been received by a ringtone, a screen display, or the like. After receiving the delivery date and time message, the user terminal 10b displays the user-specific page of the EC site based on the user's operation input (steps S654 and S547 in FIG. 6), thereby allowing the user of the user terminal 10b to check the delivery date and time. Here, the delivery date and time message may include content inquiring whether or not to change the delivery date and time, or, rather than inquiring whether or not to change the delivery date and time, a candidate date and time message may be notified when candidate dates and times need to be notified. If the displayed delivery date and time is acceptable, the user presses the "OK" button on the user terminal 10b, and the user terminal 10b sends a notification to the EC site server 70 indicating that the delivery date and time has been agreed upon.If the displayed delivery date and time is no longer suitable, the user terminal 10b sends another candidate date and time to the EC site server 70 based on the user's input (step S548 in Figure 6).

[0142] When the EC site server 70 receives a notification indicating that the delivery date and time has been agreed upon or information specifying another candidate date and time, it stores the notification in a storage device and accepts the notification (step S654A in FIG. 6). Then, the EC site server 70 transmits the notification indicating that the delivery date and time has been agreed upon or the information specifying another candidate date and time received from the user terminal 10b to the delivery management server 30 (Step S655 in FIG. 6).

[0143] When the delivery management server 30 receives from the EC site server 70 a notification indicating that the delivery date and time have been agreed upon or information specifying another candidate date and time, it updates the scheduled delivery date in the storage unit 302 based on the received content (FIG. 6, step S460A). Here, if the returned content is a notification indicating that the delivery date and time have been agreed upon, the delivery management server 30 skips updating the scheduled delivery date and time stored in the storage unit 302, and if the returned content is information specifying another candidate date and time, it writes the candidate date and time as the scheduled delivery date and time. The delivery management server 30 then sends a notification indicating that the delivery date and time has been agreed upon or information specifying another candidate date and time to the delivery company server 60b as a recipient desired delivery date and time message.

[0144] When the delivery company server 60b receives the recipient's desired delivery date and time message (step S353 in FIG. 6), it determines whether delivery is possible according to the delivery date and time or the desired delivery date and time included in the recipient's desired delivery date and time message (step S354 in FIG. 6). The determination of whether delivery is possible may be made according to an operation input from an operator of the delivery company server 60b indicating whether delivery is possible, or may be made by determining whether the number of parcels that can be delivered at the desired delivery date and time has been exceeded. If it is determined that delivery is possible according to the desired delivery date and time, the delivery company server 60b stores the desired delivery date and time in the storage device of the delivery company server 60b as the scheduled delivery date and time. On the other hand, if it is determined that delivery is not possible at the desired delivery date and time, the process may be executed from step S351, so that adjustment of the scheduled delivery date and time may continue between the delivery management server 30 and the user terminal 10b.

[0145] Here, after a certain period of time has passed since the delivery request message was sent, an operation input to change the scheduled delivery date and time is made from the user terminal 10b (step S549 in Figure 6), and the change message is sent to the EC site server 70 (step S550 in Figure 6).The EC site server 70 then accepts the change message by receiving it (step S656 in Figure 6) and sends the change message to the delivery management server 30 (step S657 in Figure 6).

[0146] When the delivery management server 30 receives the change message, it determines whether or not to allow the change of the delivery date and time (step S461). Here, the delivery management server 30 determines whether the change is within the grace period set for the change even after a certain period has passed since the delivery request message was sent. If the grace period has passed, the delivery management server 30 determines that the change is not acceptable (step S461-NO) and sends a message to the EC site server 70 indicating that the desired delivery date and time cannot be changed. Here, in step S451, it is determined whether or not the change is permissible, but it is also possible to allow all changes without determining whether or not the change is permissible, or to disallow all changes. Also, here, the processing of step S549 in FIG. 6 is the starting point, and the processing has been described for when a delivery request message is sent and a change message is sent from user terminal 10b after a certain period of time has passed. However, instead of a period of time, the processing from step S549 in FIG. 6 may be executed when the number of times the delivery date and time have been changed reaches a predetermined number.

[0147] The EC site server 70 publishes the message received from the delivery management server 30, indicating that the desired delivery date and time cannot be changed, on the user-dedicated page of the user terminal 10b, and transmits the message to the user terminal 10b (FIG. 6, step S658). Here, the EC site server 70 may notify the user of the message indicating that the desired delivery date and time cannot be changed by any of SMS, RCS, email, etc. After receiving the message, the user terminal 10b displays the user-specific page of the EC site based on the user's operational input (FIG. 6, step S550). This allows the user of the user terminal 10b to confirm that the desired delivery date and time cannot be changed. In addition, although changes to the scheduled delivery date and time are not accepted here, since there is a high possibility that the package will not arrive (due to the recipient being absent, etc.) even if it is delivered according to the scheduled delivery date registered at this time, the EC site server 70 or the delivery management server 30 may send to the user terminal 10b a message indicating that the desired delivery date and time cannot be changed, including a message that the package will be temporarily stored at the delivery company's office, etc. Also, the delivery company may again present (send) a date on which it can deliver to the user terminal 10b.

[0148] On the other hand, if the grace period has not expired, the delivery management server 30 determines that the change is acceptable (step S461-YES), updates the scheduled delivery date stored in the memory unit 302 based on the desired delivery date and time (step S462), and sends a message to the delivery company server 60b informing it of the updated scheduled delivery date.

[0149] When the delivery company server 60b receives the message notifying the updated scheduled delivery date (step S354A in FIG. 6), it writes the received scheduled delivery date into the storage device of the delivery company server 60b.

[0150] <On the day of delivery (just before) phase> When the scheduled delivery date arrives, the delivery company server 60b updates the data stored in the storage device of the delivery company server 60b regarding the delivery status of the package whose scheduled delivery date and time corresponds to the delivery date, based on the delivery route and other factors (step S355 in FIG. 6), and then transmits the delivery status information, including the delivery route and other factors, to the delivery management server 30 (steps S356 and S357 in FIG. 6). Here, the processing of steps S355, S356, and S357 in FIG. 6 is performed for packages whose scheduled delivery date and time correspond to the current day. However, the processing of steps S355, S356, and S357 in FIG. 6 may also be performed for packages that are a certain period of time before the scheduled delivery date and time. The certain period of time may be one day before the scheduled delivery date and time, or may be a period when the scheduled delivery date and time is relatively close, such as two or three days before.

[0151] When the delivery management server 30 receives the delivery status from the delivery company server 60b, it updates the status stored in the memory unit 302 based on the delivery status (step S463 in Figure 6) and calculates the estimated arrival time at the destination address (step S464 in Figure 6). This estimated arrival time may be calculated by the delivery management server 30, or may be calculated by the delivery company server 60 or the deliverer terminal 50, which then notifies the delivery management server 30 of the estimated arrival time. The estimated arrival time may be calculated for packages whose scheduled delivery date and time corresponds to the current day, or may be calculated for packages a certain period of time before the scheduled delivery date and time. The certain period of time may be one day before the scheduled delivery date and time, or may be a period when the scheduled delivery date is relatively close, such as two or three days before. The delivery management server 30 calculates the estimated arrival time for each package based on the number of packages, the destination address, the route, etc. When calculating the estimated arrival time, the delivery management server 30 may also use information such as the number of packages, the destination address, and the route, as well as past redelivery attempts (tendencies in times of absence), and whether deliveries are not made during late night hours. The delivery management server 30 then transmits the calculated estimated arrival time to the delivery company server 60b.

[0152] When the delivery company server 60b receives the estimated arrival time from the delivery company server 60b (Step S358 in FIG. 6), it transmits the estimated arrival time to the delivery person terminal 50b of the delivery person of the second delivery company. This allows the delivery person at the delivery person terminal 50b to confirm the estimated arrival time (Step S359). The deliverer terminal 50 or the delivery company server 60b sends to the delivery management server 30 an estimated arrival time confirmation completion message indicating that the estimated arrival time has been confirmed.

[0153] When the delivery management server 30 receives the estimated arrival time confirmation completion message from the delivery company server 60b (step S465 in FIG. 6), it sends an estimated arrival time message notifying the estimated arrival time to the EC site server 70 (step S466 in FIG. 6). When sending a message confirming the estimated arrival time to the EC site server 70, the delivery management server 30 may control notifications by checking the destination user's past redelivery history and specifying the allowable time for message notifications (for example, not sending notifications during late night hours).

[0154] When the EC site server 70 receives the estimated arrival time message from the delivery management server 30 (step S467 in FIG. 6), it publishes the estimated arrival time on the EC site so that it can be viewed from the user terminal 10b (step S659 in FIG. 6). For example, the estimated arrival time can be made viewable from the user terminal 10b by posting it on a user-only page that can be accessed by logging in from the user terminal 10b. Then, the EC site server 70 transmits the estimated arrival time message to the user terminal 10b.

[0155] When the user terminal 10b receives the estimated arrival time message, it notifies the user that the message has been received by ringing, displaying a message on the screen, etc. Then, in response to an instruction from the user to open the message, the user terminal 10b displays a user-only page on the EC site (steps S660 and S551 in FIG. 6). This allows the user of the user terminal 10b to check the estimated arrival time. Here, the estimated arrival time message may include content inquiring whether there has been any change to the estimated arrival time, or may notify the estimated arrival time without inquiring whether there has been any change.

[0156] In response to displaying the user-dedicated page, the user terminal 10b transmits an opening notification indicating that the estimated arrival time message has been opened to the EC site server 70 (Step S552 in FIG. 6). Also, here, the user terminal 10b is configured to send an opening notification to the EC site server 70, but it may also be configured to send an arrival notification to the EC site server 70 in response to the estimated arrival time message arriving at the user terminal 10b.

[0157] When the EC site server 70 receives the opening notification from the user terminal 10b, it transmits opening information indicating that the item has been opened together with the waybill identification information to the delivery management server 30 (Step S661 in FIG. 6).

[0158] When the delivery management server 30 receives the opening information and the waybill identification information from the EC site server 70, it stores the opening information in the storage unit 302 in association with the waybill identification information (step S468 in FIG. 6). As a result, status information indicating that the delivery wish request message has been opened is written. Then, the control unit 308 of the delivery management server 30 determines whether or not a reply has been received from the destination user after a predetermined time has elapsed since the delivery wish request message was sent (step S469 in FIG. 6). Here, the delivery management server 30 may proceed to processing step S469 based on receiving an opening notification from the user terminal 10b, or may proceed to processing step S469 in response to an arrival notification based on the delivery wish request message reaching the user terminal 10b.

[0159] The destination user checks the estimated arrival time on the user terminal 10b and determines whether to change the estimated arrival time. If the destination user does not need to change the estimated arrival time, they may not reply to the estimated arrival time message or may reply "no change." Furthermore, if the destination user wishes to change the estimated arrival time, the destination user inputs the desired delivery arrival date and time into the user terminal 10b. Based on the user's operational input, the user terminal 10b sends a change message to the EC site server 70 (steps S553 and S662 in FIG. 6). Here, the destination user previously registered the desired delivery date and time, but if the user is unable to make it as the estimated arrival time on the delivery day approaches, the destination user can change the desired delivery date and time. This allows the delivery to be rescheduled for a different date and time for users who suddenly become unable to make it and are absent from the home, thereby preventing the delivery company from visiting the user to make the delivery while the user is absent.

[0160] When the EC site server 70 receives the change message from the user terminal 10b, it accepts the change message (step S663 in FIG. 6) and transmits the change message to the delivery management server 30 (step S664 in FIG. 6).

[0161] If a predetermined time has passed since the delivery management server 30 sent the estimated arrival time message but the delivery management server 30 has not received a reply from the destination user terminal 10b (step S469-NO), the delivery management server 30 sends a message to the delivery company server 60b indicating that there has been no reply to the estimated arrival time message.

[0162] When the delivery company server 60b receives a message from the delivery management server 30 indicating that there has been no reply to the estimated arrival time message (Step S360 in FIG. 6), it may send a message indicating that there has been no reply to the estimated arrival time message to the delivery person terminal 50b of the delivery person of the second delivery company. This allows the delivery person at the delivery person terminal 50b to understand that there has been no reply to the estimated arrival time message. Therefore, it can be understood that the destination user does not currently wish to change the estimated arrival time.

[0163] On the other hand, if the delivery management server 30 receives a change message from the EC site server 70 within a certain period of time after sending the estimated arrival time message to change the desired arrival date and time (step S469 of Figure 65 - YES), it updates the estimated arrival time stored in the memory unit 302 based on this change message by writing it as the recipient's desired arrival date and time based on the desired arrival date and time (step S470 of Figure 6), and sends it to the delivery company server 60b as a recipient's desired arrival date and time message.

[0164] When the delivery company server 60b receives the recipient desired arrival date and time message (FIG. 6, step S361), it determines the arrival date and time according to the desired arrival date and time included in the recipient desired arrival date and time message (FIG. 6, step S362). Here, the delivery company server 60b sends the recipient desired arrival date and time message to the delivery person's delivery terminal 50b. This allows the delivery person at the delivery person terminal 50b to confirm the desire to change the arrival date and time based on the recipient desired arrival date and time message. If the delivery person at the deliverer terminal 50 cannot accept (cannot accommodate) a change to the desired arrival date and time requested by the destination user, the delivery person inputs another candidate date from the deliverer terminal 50, sends it to the delivery company server 60b, and if the change is acceptable, presses the "OK" button to send a notification that the arrival date and time has been determined by accepting the change. Based on the content transmitted from the deliverer terminal 50, the delivery company server 60b transmits to the delivery management server 30 a message determining the arrival date and time, or a candidate date and time message informing other candidate dates and times. Here, in response to a request from the delivery company server 60b, the delivery management server 30 may extract multiple other candidate dates and times from the candidate time periods that the delivery company can handle and the delivery status of the package, and send them to the delivery company server 60b.

[0165] When the delivery management server 30 receives a message from the delivery company server 60b to determine the arrival date and time or a message informing of another candidate date (step S471 in FIG. 6), it updates the scheduled delivery date stored in the storage unit 302 to the arrival date and time or another candidate date based on the content of the message (step S472 in FIG. 6).Then, the delivery management server 30 transmits to the EC site server 70 an arrival date and time message informing that delivery is possible according to the desired arrival date and time, or a candidate date and time message informing of another candidate date.

[0166] When the EC site server 70 receives the arrival date and time message or the candidate date and time message from the delivery management server 30 (step S473 in FIG. 6), it makes the arrival date and time message or the candidate date and time publicly available on the EC site so that it can be viewed from the user terminal 10b (step S665 in FIG. 6). For example, it can be made viewable from the user terminal 10b by posting it on a user-only page that can be accessed by logging in from the user terminal 10b. In addition, the EC site server 70 transmits the arrival date and time message or the candidate date and time message received from the delivery management server 30 to the user terminal 10b.

[0167] When the user terminal 10b receives the message from the EC site server 70, it notifies the user that the message has been received by a ringtone, a screen display, or the like. After receiving the delivery date and time message, the user terminal 10b displays a user-specific page on the EC site based on the user's input (steps S354 and S555 in FIG. 6), allowing the user of the user terminal 10b to check the arrival date and time or candidate dates and times. Here, the EC site server 70 may not transmit the arrival date and time message that is determined to be available to the user terminal 10b, but may notify the user terminal 10b of the candidate date and time message. Then, based on the operational input of the destination user, the user presses the "OK" button to indicate that they agree with the arrival date and time indicated in the arrival date and time message, or if they wish to further change the arrival date and time, they input another candidate date and time into user terminal 10b. Based on the user's input, the user terminal 10b sends to the EC site server 70 a message indicating that the arrival date and time is OK based on the user pressing the "OK" button, indicating that the arrival date and time indicated in the arrival date and time message is agreed upon, or a message specifying another candidate date and time (step S556 in Figure 6).

[0168] The EC site server 70 receives a message from the user terminal 10b indicating that the arrival date and time is OK or a message specifying another candidate date and time (step S666 in FIG. 6), and transmits a change message to the delivery management server 30 (step S667 in FIG. 6).

[0169] When the delivery management server 30 receives from the EC site server 70 information indicating agreement on the arrival date and time or information indicating another candidate date and time, it updates the scheduled delivery date in the storage unit 302 based on the received content (step S474 in FIG. 6). Here, if the returned content indicates that the arrival date and time or the candidate date and time is acceptable, the delivery management server 30 skips updating the scheduled delivery date and time stored in the storage unit 302, and if it is another candidate date and time, it writes the other candidate date and time as the scheduled delivery date and time. The delivery management server 30 then transmits information indicating the arrival date and time or the candidate date and time, or another desired date and time, to the delivery company server 60b as a recipient desired delivery date and time message.

[0170] When the delivery company server 60b receives the recipient's desired delivery date and time message (step S363 in FIG. 6), it determines whether it can accommodate the request based on either information included in the recipient's desired delivery date and time message indicating an agreement on the arrival date and time, or information indicating another candidate date and time. The determination of whether it can accommodate the request may be made based on an operation input from an operator of the delivery company server 60b indicating whether it can accommodate the request, or it may be made by sending the recipient's desired delivery date and time message to the deliverer terminal 50, having the delivery person at the deliverer terminal 50b check the recipient's desired delivery date and time message (step S364), and determining whether it can accommodate the request based on the content entered as a result.

[0171] If the delivery company server 60b determines that delivery cannot be made at the desired delivery date and time, it may continue to adjust the scheduled delivery date between the delivery management server 30, the user terminal 10b, and the EC site server 70 by executing processing from step S362.

[0172] When the driver arrives at the delivery destination at the time corresponding to the desired delivery date and time based on the destination information corresponding to the waybill identification information (step S365 in FIG. 6), the driver hands the package over to the user at the destination (step S366 in FIG. 6). The user at the destination receives the package (step S557). The user at the destination reads the waybill identification information attached to the package using user terminal 10b, and obtains the destination information associated with the waybill identification information and information about the delivery requester from delivery management server 30, thereby being able to confirm that the package is addressed to them, the delivery requester, etc.

[0173] When the package is handed over, an input regarding "delivery completed" is made. The input regarding "delivery completed" is made by the user of the destination pressing a "receipt completed" button on the user terminal 10b owned by the user, which then transmits the waybill identification information and information indicating "receipt completed" from the user terminal 10b to the delivery company server 60b (step S558 in FIG. 6). Here, the user terminal 10b may be configured to transmit information indicating "receipt completed" to the delivery management server 30. Furthermore, the input regarding "delivery completed" may be made by the driver inputting the waybill identification information and information indicating "delivery completed" into the deliverer terminal 50, which then transmits the waybill identification information and the information indicating "delivery completed" from the deliverer terminal 50 to the delivery company server 60b. Furthermore, if there is a copy of the delivery slip for the destination used by the second delivery company, the user at the destination may stamp the copy of the delivery slip to indicate that the package has been received, and the driver may take this copy of the delivery slip back to the base (office, etc.) of the second delivery company, confirm that it has been stamped, and then an operator may input "delivery completed" from the terminal device of the second delivery company installed at the base.

[0174] When the delivery company server 60b of the second delivery company receives the information corresponding to "Delivery Completed" and the waybill identification information from the deliverer terminal 50b or the user terminal 10b, it writes "Delivery Completed" to the storage device of the delivery company server 60b (Step S367 in FIG. 6).The delivery company server 60b then performs status information linking processing by sending the waybill identification information and delivery completion information indicating "Delivery Completed" to the delivery management server 30 (Steps S368 and S369 in FIG. 6).

[0175] The delivery status acquisition unit 3041 of the delivery management server 30 acquires the waybill identification information and delivery completion information indicating "delivery completed" by receiving it from the delivery company server 60b. Then, the first processing unit 305 of the delivery management server 30 associates the waybill identification information with the information indicating "delivery completed" based on the information acquired by the delivery status acquisition unit 3041, and stores the information by writing it into the storage unit 302 (Step S475 in FIG. 6).

[0176] Then, the delivery management server 30 transmits a message indicating "delivery completed" together with the shipping label identification information to the EC site server 70 (Step S476 in FIG. 6). When the EC site server 70 receives the message indicating delivery completion and the waybill identification information from the delivery management server 30, it writes the status indicating delivery completion in association with the waybill identification information into the storage device (step S668 in FIG. 6).

[0177] In the second embodiment described above, the case where products sold on the EC site are collected by a second delivery company assigned a delivery company ID specified as the delivery method and delivered to the destination user is described, but the package may also be delivered in cooperation with another delivery company.

[0178] Furthermore, according to the second embodiment described above, the destination user accesses the EC site server 70 from the user terminal 10b to check or change the delivery date and time. This allows the destination user to simply communicate with the EC site where they purchased the product, and continue to communicate with the EC site even during the delivery phase. This avoids the seamless experience that would occur if the user communicated with the delivery management server 30 instead of the EC site when moving to the delivery phase. In addition, although the destination user accesses the EC site server 70 from the user terminal 10b to check or change the delivery date and time, it is also possible to communicate directly with the delivery management server 30 without accessing the EC site server 70. In this case, the user does not need to go through the EC site server 70. Furthermore, the EC site server 70 does not need to go through the EC site server 70 to process parcel delivery, as the delivery management server 30 can directly communicate with the user terminal 10b without going through the EC site server 70. This eliminates the need to perform delivery-related processing, thereby preventing an increase in the processing load.

[0179] According to the first and second embodiments described above, when a joint delivery is performed, even if a package is accepted without a specified delivery date and time, the delivery management server 30 initiates an inquiry to the destination user about the desired delivery date and time after the package is accepted and before delivery, and acquires the desired delivery date and time. As a result, even if a package is accepted without a specified delivery date and time, multiple delivery companies do not need to initiate an action to acquire the desired delivery date and time. Therefore, there is no need for multiple delivery companies participating in joint delivery to make an agreement among themselves as to which of the multiple delivery companies will execute the action to acquire the desired delivery date and time. This reduces the burden of various coordination tasks between delivery companies participating in joint delivery to separate the tasks of which company will perform collection work for the desired delivery date and time. Furthermore, the reduced coordination task of joint delivery makes it easier for delivery companies to enter the joint delivery business.

[0180] In addition, the delivery management server 30 may be operated by one of the delivery companies that perform joint delivery. In this case, a delivery company that uses the delivery management server 30 but does not operate the delivery management server 30 can have the delivery company that operates the delivery management server 30 perform the collection work for the desired delivery date and time, so it does not have to perform the work itself.

[0181] Furthermore, according to the first and second embodiments described above, for a package accepted for collection without a specified scheduled delivery date and time, instead of simply inquiring about the desired delivery date and time from the destination user, a scheduled delivery date and time is generated and transmitted to the destination user's user terminal 10b for confirmation by the user. Thus, if a user is simply inquired about a preferred desired delivery date and time, the destination user must select a number of candidate dates and consider which of the candidate dates to select. This can take time, and the user may have difficulty deciding. In contrast, according to the above-described embodiment, the delivery management server 30 presents the destination user with a scheduled delivery date and time, specifically indicating when the user is likely to visit, for confirmation. This facilitates the response because the destination user only needs to decide whether the presented scheduled delivery date and time is acceptable. Furthermore, if the scheduled delivery date and time is convenient, further consideration of the schedule is unnecessary. Consideration of the schedule can be performed only when the scheduled delivery date and time is not convenient, reducing the number of cases where consideration is required.

[0182] In the above-described embodiment, the destination information acquisition unit 3032 acquires destination information indicating the destination from the delivery request source without specifying a delivery date and time. However, the destination information may also be acquired together with a delivery date and time specification from the delivery request source. When a delivery date and time is specified, the delivery management server 30 may accept the specified delivery date and time, and may inquire from the user of the delivery destination about whether the delivery date and time should be changed, or may accept a request from the user of the delivery destination to change the delivery date and time.

[0183] The delivery management server 30 in the above-described embodiment may be implemented by a computer. In this case, a program for implementing this function may be recorded on a computer-readable recording medium, and the program may be loaded and executed by a computer system. Note that the term "computer system" as used herein includes hardware such as an operating system and peripheral devices. Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" may also include devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or devices that store programs for a fixed period of time, such as volatile memory within the computer system serving as the server or client. The program may also be designed to implement some of the above-described functions, or may be capable of implementing the above-described functions in combination with programs already stored in the computer system, or may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0184] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention. [Explanation of symbols]

[0185] 10, 10a, 10b User terminal 20, 20a, 20b POS terminal 30 Delivery management server 40 Waybill Print Server 41 Invoice Printer 50, 50a, 50b Delivery terminal 55, 55a, 55b Mobile Printer 60, 60a, 60b Delivery company server 70 EC site server 301 Communications Department 302 Storage section 303 First acquisition part 304 Second Acquisition Department 305 First Processing Section 306 Transmission Unit 307 Identification Information Management Department 308 Control Unit 3031 Waybill Identification Information Acquisition Unit 3032 Destination Information Acquisition Unit 3041 Delivery Status Acquisition Unit 3042 Desired date and time acquisition section 3061 First Transmission Unit 3062 Second Transmission Unit La 2D barcode Lb Waybill Identification Information Lc one-dimensional barcode Ld one-dimensional barcode Le Reserve Area NW Network S Delivery System

Claims

1. A delivery management server that manages information regarding joint deliveries in which multiple delivery companies work together to deliver packages, a first acquisition unit that acquires destination information representing a destination from a delivery request source without specifying a delivery date and time; a first sending unit that sends a request to the electronic device of the inquiry destination based on the contact information included in the acquired destination information, to inquire about the desired delivery date and time; a second acquisition unit that acquires a desired delivery date and time, which indicates a delivery date and time, from the electronic device as a response to the request; a second transmission unit that notifies the electronic device of at least one of the delivery companies that perform the joint delivery of the acquired desired delivery date and time; A delivery management server having:

2. The package is a product sold on an EC (Electronic Commerce) site, The second transmission unit The acquired desired delivery date and time is transmitted to the server of the EC site. The delivery management server according to claim 1 .

3. The second acquisition unit In response to the inquiry request, the desired delivery date and time transmitted from the terminal device used by the recipient consumer to the server of the EC site is acquired from the server of the EC site. The delivery management server according to claim 2 .

4. A delivery management method executed by a delivery management server that manages information regarding joint delivery in which multiple delivery companies cooperate to deliver packages to be delivered, Receive destination information representing the destination from the delivery request source without specifying the delivery date and time, Sending a request to the electronic device of the inquiry destination based on the contact information included in the acquired destination information, inquiring about the desired delivery date and time; A desired delivery date and time representing a delivery date and time is acquired from the electronic device as a response to the request; The electronic device of at least one of the delivery companies that will be performing the joint delivery is notified of the acquired desired delivery date and time. A delivery management method including:

Images