Delivery charge sharing system and delivery charge sharing method

WO2026202992A1PCT designated stage Publication Date: 2026-10-01NT T INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/011317
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-03-24
Publication Date
2026-10-01

Smart Images

  • Figure JP2025011317_01102026_PF_FP_ABST
    Figure JP2025011317_01102026_PF_FP_ABST
Patent Text Reader

Abstract

This delivery charge sharing system comprises: a plurality of business operator terminals that register, in concealed form, delivery charges determined for respective combinations of times and areas in response to operations performed by different business operators engaged in electronic commerce; a delivery charge integration database that holds information indicating the delivery charges registered from each of the plurality of business operator terminals; and one or more delivery company terminals that display information indicating the delivery charges registered in the delivery charge integration database. 
Need to check novelty before this filing date? Find Prior Art

Description

Delivery fee sharing system and delivery fee sharing method

[0001] The present invention relates to a delivery fee sharing system and a delivery fee sharing method.

[0002] In recent years, while the number of delivery workers has been decreasing in the logistics industry, demand for EC (Electronic Commerce) systems has been growing. The era when shippers choose transport companies has shifted to a situation where transport companies also select shippers, and there already exists a mechanism for delivery companies to disclose their delivery fees to EC businesses (see, for example, Non-Patent Document 1).

[0003] “[Latest 2024] Thorough Comparison of Parcel Delivery and Delivery Company Fees from 5 Major Providers”, E-Commerce Magazine by futureshop, [online], <searched March 3, Reiwa 7>, Internet, <URL: https: / / www.future-shop.jp / magazine / courier-delivery-courier-fee>

[0004] However, conventional mechanisms do not support dynamic pricing, and there is no mechanism that allows delivery companies to refer to delivery fees across different EC sites side by side. That is, there has been a problem that conventional mechanisms cannot adapt to the era in which delivery companies select shippers.

[0005] In view of the above circumstances, an object of the present invention is to provide a technology capable of adapting to the era in which delivery companies select shippers while improving convenience for both EC businesses and delivery companies.

[0006] One aspect of the present invention is a delivery fee sharing system comprising: a plurality of business operator terminals that conceal and register delivery fees determined for each combination of time and area in accordance with operations of different business operators conducting electronic commerce; a delivery fee integration database that stores information indicating delivery fees registered from each of the plurality of business operator terminals; and one or more delivery company terminals that display information indicating the delivery fees registered in the delivery fee integration database.

[0007] One aspect of the present invention is a shipping fee sharing method that, in response to the operations of different businesses conducting e-commerce, registers shipping fees determined for each combination of time and area in an anonymized manner, and displays information indicating the shipping fees registered in a shipping fee integration database that holds information indicating the registered shipping fees.

[0008] This invention makes it possible to improve convenience for both e-commerce businesses and delivery companies while also adapting to an era where delivery companies can choose their clients.

[0009] This figure shows an example configuration of the shipping fee sharing system according to the present invention. This figure visualizes the data structure in the shipping fee integration DB in the embodiment. This figure shows an example configuration of the e-commerce business terminal in the embodiment. This figure shows an example configuration of the delivery company terminal in the embodiment. This flowchart shows the processing flow performed by the e-commerce business terminal in the embodiment. This flowchart shows the processing flow performed by the delivery company terminal in the embodiment.

[0010] One embodiment of the present invention will be described below with reference to the drawings.

[0011] Figure 1 shows an example configuration of the shipping fee sharing system 100 according to the present invention. The shipping fee sharing system 100 comprises an e-commerce business terminal 10, a delivery company terminal 20, and a shipping fee integration DB 30. In the example shown in Figure 1, the shipping fee sharing system 100 is shown to have three e-commerce business terminals 10-1 to 10-3 and three delivery company terminals 20-1 to 20-3, but the shipping fee sharing system 100 only needs to have multiple e-commerce business terminals 10 and one or more delivery company terminals 20. In the shipping fee sharing system 100 according to the present invention, the e-commerce business and the delivery company operate under a contract that only covers the exchange of shipping fees (individual contract).

[0012] The e-commerce terminal 10 is a communication terminal operated by an e-commerce business. In the example shown in Figure 1, e-commerce terminal 10-1 is a communication device owned by Company A, e-commerce terminal 10-2 is a communication device owned by Company R, and e-commerce terminal 10-3 is a communication device owned by Company Y. The e-commerce terminal 10 registers information indicating the shipping fees for each e-commerce business (hereinafter referred to as "shipping fee information") in the shipping fee integration DB 30 in response to the e-commerce business's operation. The e-commerce terminal 10 registers the shipping fee information in the shipping fee integration DB 30 in an encrypted state. As a result, the shipping fee information remains confidential among e-commerce businesses.

[0013] Furthermore, e-commerce businesses operate the e-commerce terminal 10 to run their e-commerce sites. Customers register information regarding delivery quality on the e-commerce site. This allows e-commerce businesses to receive delivery quality feedback from customers via the e-commerce site.

[0014] Shipping fees are calculated using dynamic pricing. That is, shipping fees are set according to the area and time of day. Shipping fee information is registered with a shipping fee ID, an e-commerce business (anonymous), a shipping area, a time of day (in hours), and a shipping fee. The shipping fee ID represents information used to identify the shipping fee information. The e-commerce business (anonymous) represents information used to identify the e-commerce business, but is kept anonymous in this invention. The shipping area represents information used to identify the area where the goods should be delivered. For example, the shipping area is expressed in 3D mesh units. The time of day represents the time of day when the delivery should be requested. For example, the time of day is expressed in hours. The shipping fee represents the shipping fee for the goods to be delivered.

[0015] The delivery company terminal 20 is a communication terminal operated by the delivery company. In the example shown in Figure 1, delivery company terminal 20-1 is a communication device held by delivery company 1, delivery company terminal 20-2 is a communication device held by delivery company 2, and delivery company terminal 20-3 is a communication device held by delivery company 3. The delivery company terminal 20 displays delivery fee information registered in the delivery fee integration DB 30 in response to operations by the delivery company's personnel. This allows the delivery company's personnel to refer to delivery fee information for each e-commerce business (delivery fees by area and time of day) registered in the delivery fee integration DB 30.

[0016] Furthermore, since the shipping fee information registered in the integrated shipping fee database 30 is encrypted, the shipping company's representative can access the shipping fee information by decrypting it on the shipping company's terminal 20. In order for the shipping company to be able to access the shipping fee information, the shipping company's representative must know the decryption information needed to decrypt the shipping fee information. The decryption information may be predetermined information.

[0017] The shipping fee integration DB 30 is a database that holds shipping fee information for each e-commerce business. The shipping fee integration DB 30 is deployed, for example, on the cloud. The shipping fee integration DB 30 registers shipping fee information in response to requests from the e-commerce business terminal 10. The shipping fee integration DB 30 provides the shipping fee information it holds in response to requests from the shipping company terminal 20.

[0018] Figure 2 is a diagram (Entity Relationship (ER) diagram) visualizing the data structure in the shipping fee integration DB 30 in the embodiment. As shown in Figure 2, the shipping fee integration DB 30 includes shipping case information such as shipping case ID, shipping fee ID, and status information, and shipping fee information is registered in the hierarchy of shipping fee IDs. The shipping case ID represents information for identifying cases for which an e-commerce business has made a shipping request. Therefore, a case identified by one shipping case ID represents a shipping case of a specific e-commerce business. The shipping fee ID represents information for identifying shipping fee information. The status represents the current status of the shipping request identified by the shipping case ID. The status may be represented, for example, as "entered" and "not entered". "Entered" means that the shipping request identified by the shipping case ID has been assigned to a certain shipping company. "Not entered" means that the shipping company for the shipping request identified by the shipping case ID has not yet been assigned.

[0019] Figure 3 shows an example of the configuration of the e-commerce terminal 10 in the embodiment. The e-commerce terminal 10 includes a communication unit 11, a display unit 12, an operation unit 13, a control unit 14, and a shipping fee database 15.

[0020] The communication unit 11 communicates with other devices. For example, the communication unit 11 communicates with the shipping fee integration DB 30. The communication unit 11 transmits shipping fee information to the shipping fee integration DB 30. As a result, the communication unit 11 registers the shipping fee information in the shipping fee integration DB 30.

[0021] The display unit 12 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The display unit 12 displays the input screen for shipping fee information to be registered in the shipping fee integration DB 30, as well as the screen of the e-commerce site.

[0022] The operation unit 13 is configured using existing input devices such as a keyboard, pointing device (mouse, tablet, etc.), buttons, and touch panel. The operation unit 13 is operated by the user when inputting user instructions into the e-commerce terminal 10. For example, the operation unit 13 accepts input of shipping fee information and registration instructions.

[0023] The control unit 14 controls the entire e-commerce terminal 10. The control unit 14 is composed of a processor such as a CPU (Central Processing Unit) and memory. The control unit 14 implements the functions of the management unit 141, encryption unit 142, and registration unit 143 by executing a program.

[0024] Some or all of the management unit 141, encryption unit 142, and registration unit 143 may be implemented by hardware (including circuitry) such as ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), or FPGA (Field Programmable Gate Array), or by the cooperation of software and hardware. The program may be recorded on a computer-readable recording medium. Computer-readable recording media include non-temporary storage media such as flexible disks, magneto-optical disks, ROM (Read Only Memory), CD-ROMs, and hard disks built into computer systems. The program may be transmitted via a telecommunications line.

[0025] Some of the functions of the management unit 141, encryption unit 142, and registration unit 143 do not need to be pre-installed on the e-commerce terminal 10, and may be realized by installing additional application programs on the e-commerce terminal 10.

[0026] The management unit 141 determines the shipping fee for each time and area combination using an algorithm that automatically adjusts prices according to fluctuations in demand, in response to instructions input via the operation unit 13. The algorithm that automatically adjusts prices according to fluctuations in demand is, for example, dynamic pricing. The management unit 141 registers the shipping fee information, which shows the shipping fee for each determined time and area combination, in the shipping fee DB 15.

[0027] The encryption unit 142 encrypts the shipping fee information registered in the shipping fee DB 15 in response to instructions input via the operation unit 13. The method for encrypting the shipping fee information is predetermined. For example, the encryption method is assumed to be the same for all e-commerce businesses.

[0028] The registration unit 143 registers the shipping fee information encrypted by the encryption unit 142 in the shipping fee integration DB via the communication unit 11.

[0029] Figure 4 shows an example of the configuration of a delivery company terminal 20 in an embodiment. The delivery company terminal 20 includes a communication unit 21, a display unit 22, an operation unit 23, and a control unit 24.

[0030] The communication unit 21 communicates with other devices. For example, the communication unit 21 communicates with the shipping fee integration DB 30. The communication unit 21 sends a request for shipping fee information to the shipping fee integration DB 30. The communication unit 21 receives the shipping fee information sent from the shipping fee integration DB 30 in response to the request.

[0031] The display unit 22 is a display device such as a liquid crystal display or an organic EL display. The display unit 22 displays a screen showing the shipping fee information received by the communication unit 21.

[0032] The operation unit 23 is configured using existing input devices such as a keyboard, pointing device (mouse, tablet, etc.), buttons, and touch panel. The operation unit 23 is operated by the user when inputting user instructions into the delivery company terminal 20. For example, the operation unit 23 accepts input such as instructions to request delivery fee information and entry instructions.

[0033] The control unit 24 controls the entire delivery company terminal 20. The control unit 24 is configured using a processor such as a CPU and memory. The control unit 24 implements the functions of the information acquisition unit 241 and the management unit 242 by executing a program.

[0034] Some or all of the information acquisition unit 241 and the management unit 242 may be implemented by hardware (including circuitry) such as ASICs, PLDs, and FPGAs, or by the cooperation of software and hardware. The program may be recorded on a computer-readable recording medium. Computer-readable recording media include non-temporary storage media such as flexible disks, magneto-optical disks, ROMs (Read Only Memory), CD-ROMs, and hard disks built into computer systems. The program may be transmitted via a telecommunications line.

[0035] Some of the functions of the information acquisition unit 241 and the management unit 242 do not need to be pre-installed on the delivery company terminal 20, and may be realized by installing additional application programs on the delivery company terminal 20.

[0036] The information acquisition unit 241 acquires shipping fee information registered in the shipping fee integration DB 30 in response to instructions input via the operation unit 23.

[0037] The management unit 242 decrypts the shipping fee information acquired by the information acquisition unit 241. The information regarding the decryption key for decrypting the shipping fee information is shared among the shipping companies, but not among the e-commerce businesses. Therefore, even if an e-commerce business accesses the integrated shipping fee database 30, they cannot access shipping fee information registered by other e-commerce businesses. The information regarding the decryption key for decrypting the shipping fee information may be shared among the shipping companies in any way. Furthermore, the management unit 242 makes an entry for the shipping case identified by the decrypted shipping fee information, in response to instructions entered via the operation unit 23. An entry for a shipping case means an application for that shipping case.

[0038] Figure 5 is a flowchart illustrating the processing flow performed by the e-commerce terminal 10 in the embodiment. Although Figure 5 explains the process using an example from one e-commerce business, the same process is performed by all e-commerce businesses. The e-commerce business operates the e-commerce terminal 10 to calculate the shipping fee for each combination of time and area (step S101). The management unit 141 of the e-commerce terminal 10 calculates the shipping fee for each combination of time and area using dynamic pricing. The management unit 141 registers the calculated shipping fee information for each combination of time and area in the shipping fee DB 15 (step S102).

[0039] The encryption unit 142 encrypts the shipping fee information registered in the shipping fee DB 15 in response to instructions from the e-commerce business operator. The registration unit 143 applies to the integrated shipping fee DB 30 for registration of the encrypted shipping fee information via the communication unit 11 (step S103). The registration unit 143 determines whether or not the registration of the shipping fee information has been accepted (step S104). If the integrated shipping fee DB 30 provides a response indicating that the registration of the shipping fee information has been completed, the registration unit 143 determines that the registration of the shipping fee information has been accepted. On the other hand, if the integrated shipping fee DB 30 does not provide a response indicating that the registration of the shipping fee information has been completed, the registration unit 143 determines that the registration of the shipping fee information has not been accepted.

[0040] Here, if a response indicating that the registration of shipping fee information has been completed is not received from the shipping fee integration DB 30, it may be due to network congestion, a timeout, or a network error or system error (including permission errors) such as the EC business operator not having the necessary application authority. If the registration unit 143 determines that the registration of shipping fee information could not be accepted (step S104-NO), the EC business operator terminal executes the process in step S102.

[0041] On the other hand, if the registration unit 143 determines that the registration of shipping fee information has been accepted (step S104-YES), the shipping fee information is registered in the shipping fee integration DB 30 (step S105).

[0042] FIG. 6 is a flowchart showing the flow of processing performed by the delivery company terminal 20 according to the embodiment. In FIG. 6, processing at one delivery company will be described as an example, but the same processing is executed by all delivery companies. A person in charge at a delivery company operates the delivery company terminal 20 to refer to delivery fee information registered in the integrated delivery fee DB (step S201). Specifically, the information acquisition unit 241 of the delivery company terminal 20 accesses the integrated delivery fee DB and acquires delivery fee information registered in the integrated delivery fee DB. The information acquisition unit 241 displays the acquired delivery fee information on the display unit 22. At this time, the information acquisition unit 241 may display delivery fee information of a plurality of EC businesses on the display unit 22.

[0043] A person in charge at a delivery company refers to the delivery fee information displayed on the screen of the display unit 22, and determines whether or not there is delivery fee information that matches the company's economic conditions. When there is delivery fee information that matches the company's economic conditions, the person in charge at the delivery company operates the operation unit 23 of the delivery company terminal 20 to select an EC business operator (anonymous) specified by the delivery fee information that matches the company's economic conditions (step S202). Thereafter, the person in charge at the delivery company operates the operation unit 23 to enter the selected EC business operator (anonymous) (step S203).

[0044] The management unit 242 controls the communication unit 11 to transmit an entry request for the selected EC business operator (anonymous) to the integrated delivery fee DB 30. The management unit 242 determines whether or not matching with the entered EC business operator (anonymous) was possible (step S204). If the management unit 242 determines that matching with the entered EC business operator (anonymous) was not possible (step S204: NO), the processing from step S201 onward is executed.

[0045] If the management unit 242 determines that matching with the entered EC business operator (anonymous) was possible (step S204: YES), the management unit 242 updates the status on the integrated delivery fee DB 30 (step S205). For example, the management unit 242 updates the status of a delivery project specified by the delivery project ID of the entered EC business operator (anonymous) among the projects registered on the integrated delivery fee DB 30 from "unentered" to "entered".

[0046] According to the delivery charge sharing system 100 configured as described above, the system comprises: a plurality of EC merchant terminals 10 that conceal and register delivery charge information in accordance with operations of an EC merchant; an integrated delivery charge DB 30 that stores the delivery charge information registered from each of the plurality of EC merchant terminals 10; and one or more delivery company terminals 20 that display the delivery charge information registered in the integrated delivery charge DB 30.

[0047] This enables both the EC merchant and the delivery company to simultaneously enjoy respective advantages. For example, an EC merchant can freely set delivery charges according to the company's own economic conditions, demands, and other factors. Furthermore, for example, a delivery company can comprehensively refer to the delivery charges of each EC merchant, and implement resource allocation and selection of EC merchants in consideration of economic factors. Such a mechanism makes it possible to improve the convenience for both EC merchants and delivery companies, while adapting to the era in which delivery companies select shippers.

[0048] Furthermore, EC merchants need to set delivery charges that allow them to be selected by delivery companies, and delivery companies need to improve delivery quality so that they are selected by EC merchants. Stimulating competition among both EC merchants and delivery companies can comprehensively increase the value provided to customers.

[0049] The embodiments of the present invention have been described above in detail with reference to the drawings. However, the specific configuration is not limited to these embodiments, and includes designs and the like that do not depart from the scope of the gist of the present invention.

[0050] The present invention is applicable to the logistics industry.

[0051] 10, 10-1 to 10-3... EC merchant terminal, 20, 20-1 to 20-3... delivery company terminal, 30... integrated delivery charge DB, 11, 21... communication unit, 12, 22... display unit, 13, 23... operation unit, 14, 24... control unit, 15... delivery charge DB, 100... delivery charge sharing system, 141... management unit, 142... encryption unit, 143... registration unit, 241... information acquisition unit, 242... management unit

Claims

1. A shipping fee sharing system comprising: multiple business terminals that register shipping fees in an anonymized manner for each combination of time and area in response to operations by different businesses conducting e-commerce; a shipping fee integration database that holds information indicating the shipping fees registered from each of the multiple business terminals; and one or more shipping company terminals that display the information indicating the shipping fees registered in the shipping fee integration database.

2. The shipping fee sharing system according to claim 1, wherein the plurality of business terminals determine shipping fees for each combination of time and area using an algorithm that automatically adjusts prices in response to fluctuations in demand.

3. The shipping fee sharing system according to claim 1 or 2, wherein when one or more shipping company terminals receive a registration instruction from a user for a shipping case identified by the information indicating the displayed shipping fee, the terminal transmits the registration instruction to the shipping fee integration database.

4. A shipping fee sharing method that involves registering shipping fees determined for each combination of time and area in accordance with the operations of different businesses conducting e-commerce, while keeping the shipping fees confidential, and displaying the information indicating the shipping fees registered in a shipping fee integration database that holds information indicating the registered shipping fees.