Delivery management system, delivery management method, and delivery management program
The delivery management system addresses the challenge of handling diverse delivery types by using a control unit to read code information and print labels, ensuring accurate and efficient delivery management with options for anonymous delivery and flexible billing.
Patent Information
- Application Number
- JP2020216277
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-12-25
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2040-12-25
AI Technical Summary
Existing delivery management systems struggle to accommodate different delivery types, leading to inaccurate handling and management of delivery items.
A delivery management system that includes a control unit connected to an underwriting device, which reads code information from delivery items to determine appropriate handling and prints delivery destination information on a label.
Enables efficient and accurate delivery management by determining the appropriate handling for different delivery types, including options for anonymous delivery, and facilitates tracking and billing based on delivery site information.
Smart Images

Figure 0007591400000001 
Figure 0007591400000002 
Figure 0007591400000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a delivery management system, a delivery management method, and a delivery management program for carrying out delivery. [Background technology]
[0002] When shipping a package, the package is brought to a collection point or the like. A delivery management device that efficiently and reliably delivers items to be delivered is also under consideration (see, for example, Patent Document 1). In the technology described in this document, when a registration request is acquired from a user's terminal device, the code identification information included in the acquired registration request is associated with delivery information and stored in a delivery management database. When code identification information included in a delivery information confirmation request acquired from a delivery company's terminal device is acquired, the delivery management database is referenced, and a delivery fee is calculated based on the delivery information associated with the code identification information that matches the acquired code identification information, and a payment process for the calculated delivery fee is executed. Depending on the result of the payment process, an instruction to output information related to the delivery origin and delivery destination is output to the delivery company's terminal device. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2017-73098 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, there are cases where the handling of a delivery item differs depending on the delivery type. In this case, if the different handling methods cannot be handled, it is difficult to deliver the delivery item accurately. [Means for solving the problem]
[0005] A delivery management system that solves the above problem includes a control unit connected to an acceptance device that accepts deliveries, and a delivery information storage unit that records delivery destination information for code information. When the control unit acquires code information obtained by reading a code image displayed on the delivery from the acceptance device, the control unit uses the delivery information storage unit to determine how to handle the delivery in accordance with the code information, and outputs a label on which the delivery destination information recorded in the delivery information storage unit is printed to the acceptance device in order to deliver the delivery according to the handling. Effect of the Invention
[0006] According to the present invention, it is possible to provide a delivery management system, a delivery management method, and a delivery management program for efficiently sending deliveries. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 is a schematic configuration diagram illustrating a system configuration according to an embodiment. [Diagram 2] FIG. 2 is an explanatory diagram of a hardware configuration of the embodiment. [Diagram 3] 5A is an explanatory diagram of a user information storage unit, FIG. 5B is an explanatory diagram of a listing information storage unit, and FIG. 5C is an explanatory diagram of a transaction status storage unit according to the embodiment. [Figure 4] 5A is an explanatory diagram of a fee information storage unit, FIG. 5B is an explanatory diagram of a delivery information storage unit, and FIG. 5C is an explanatory diagram of a billing information storage unit according to the embodiment. [Diagram 5] FIG. 4 is an explanatory diagram of a code printed sticker according to an embodiment. [Figure 6] FIG. [Figure 7] FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] An embodiment of a delivery management system, a delivery management method, and a delivery management program will be described with reference to Figures 1 to 7. In this embodiment, a delivery management system used in providing a delivery service by directly dropping an item into a mailbox will be described. For example, assume that an item is put up for auction on an auction site, and the item is shipped to the successful bidder. As shown in FIG. 1, the delivery management system of this embodiment uses a user terminal 10, a transaction server 20, a delivery management server 30, and a delivery terminal 40.
[0009] (Hardware configuration description) Next, the hardware configuration of the information processing device H10 constituting the user terminal 10, the transaction server 20, the delivery management server 30, and the delivery terminal 40 will be described with reference to Fig. 2. The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is an example, and it is also possible to realize the system using other hardware.
[0010] The communication device H11 is an interface that establishes a communication route with other devices and transmits and receives data, and is, for example, a network interface or a wireless interface.
[0011] The input device H12 is a device that accepts input of various information, such as a mouse, a keyboard, a camera (photographing device), etc. The display device H13 is a display or the like that displays various information.
[0012] The storage device H14 is a storage device that stores data and various programs for executing various functions of the user terminal 10, the transaction server 20, the delivery management server 30, and the delivery terminal 40. Examples of the storage device H14 include a ROM, a RAM, a hard disk, etc.
[0013] The processor H15 uses programs and data stored in the storage device H14 to control each process in the user terminal 10, the transaction server 20, the delivery management server 30, and the delivery terminal 40. Examples of the processor H15 include a CPU and an MPU. The processor H15 loads programs stored in a ROM or the like into a RAM and executes various processes for each process.
[0014] The processor H15 is not limited to a processor that performs software processing for all the processes it executes. For example, the processor H15 may be equipped with a dedicated hardware circuit (e.g., an application specific integrated circuit: ASIC) that performs hardware processing for at least a part of the processes it executes. That is, the processor H15 may be configured as a circuit including: (1) one or more processors that operate according to a computer program (software); (2) one or more dedicated hardware circuits that execute at least a part of various processes; or (3) a combination thereof. The processor includes a CPU and memory such as RAM and ROM, and the memory stores program code or instructions configured to cause the CPU to execute processes. The memory, i.e., computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer.
[0015] (Functions of delivery management system) The functions of the delivery management system will be explained using Figure 1. The user terminal 10 used in the delivery management system is a computer terminal used by a user who performs a transaction. In this embodiment, the user terminal 10 is used by a user (seller) who puts up an item at an auction and ships the item that has been sold. The user terminal 10 includes an application execution unit 11. This application execution unit 11 executes a transaction application provided by a transaction site of a transaction server 20 and installed in the user terminal 10. This transaction application holds data related to a user ID, accesses the transaction server 20, and executes transaction processing. Furthermore, the user terminal 10 is equipped with a camera, which is used to capture the two-dimensional code image.
[0016] The trading server 20 is a computer system of a trading site that mediates transactions (auctions in this embodiment) between users. The trading server 20 includes a trading management unit 21, a user information storage unit 22, a commodity information storage unit 23, and a trading information storage unit 24. The transaction management unit 21 executes a process of mediating transactions between sellers of products and buyers of the products.
[0017] As shown in Fig. 3(a), a user management record 220 relating to a user of the present service is recorded in the user information storage unit 22. This user management record 220 is recorded when a user registers for the service. Data relating to the user ID, name, and address are recorded in this user management record 220.
[0018] The user ID data area stores data regarding an identifier for identifying each user. The name and address data areas record data relating to the user's name and address, respectively.
[0019] 3(b), the selling information storage unit 23 records a selling management record 230 for a product being sold on the transaction server 20. This selling management record 230 is recorded when a product is put up for sale. This selling management record 230 records data related to the selling code, the seller, the price, the selling details, and whether anonymity is required.
[0020] The selling code data area stores data on an identifier for identifying each selling item. The seller data area stores data regarding an identifier for identifying the user who put up the item for sale.
[0021] The price data area records data regarding the sales price if this item is offered for sale. The listing details data area records data regarding the description of the listed item. The anonymity required data area records a flag to determine whether anonymous delivery is required. When the anonymity required flag is recorded, the name and address of the transactor are not revealed to the transacting party.
[0022] As shown in Fig. 3(c), the transaction information storage unit 24 records a transaction management record 240 related to a user's transaction. This transaction management record 240 is recorded when a transaction is made. This transaction management record 240 records data related to the transaction code, the auction code, the transaction amount, the seller, the buyer, the delivery address, whether anonymity is required, the two-dimensional code, and the tracking number.
[0023] The transaction code data area stores data regarding an identifier for identifying each transaction. The exhibition code data area stores data related to an identifier for identifying the contents of the transaction (eg, a product).
[0024] The transaction amount data area stores data regarding the amount to be paid in this transaction. The seller data area records data related to an identifier (user ID) for identifying the user who provides (sells) the product in this transaction. This seller will be the sender of the product.
[0025] The buyer data area records data related to an identifier (user ID) for identifying the user (successful bidder) who will purchase the product in this transaction. The buyer is the successful bidder in the auction and will be the recipient of the product.
[0026] The delivery address data area records data on the delivery address of the product. The delivery address is the address specified by the purchaser. In the anonymity necessity data area, a flag for determining whether anonymous delivery is necessary is recorded.
[0027] The two-dimensional code data area contains the code obtained from the code print sticker 500 used when shipping this product. issue Data regarding the number is recorded. The tracking number data area records data regarding an identifier for tracking the delivery status of this product.
[0028] 1 is a computer system that manages deliveries. This delivery management server 30 includes a control unit 31, a fee information storage unit 32, a delivery information storage unit 33, and a billing information storage unit .
[0029] The control unit 31 functions as a delivery management unit 311 and a settlement unit 312 by executing a delivery management program. The delivery management unit 311 executes a process for managing the delivery of deliveries. The settlement unit 312 executes a process for managing the collection of delivery charges.
[0030] As shown in Fig. 4(a), the fee information storage unit 32 stores a fee management record 320 related to shipping charges (handling) for deliveries. This fee management record 320 is recorded when a shipping charge is registered. This fee management record 320 stores data related to the site ID and the delivery charge.
[0031] The site ID data area stores data regarding an identifier for identifying the trading site (trading server 20) where the transaction was conducted. The shipping fee data area records data regarding shipping fees for transactions carried out at each transaction site (transaction server 20).
[0032] As shown in Fig. 4(b), a delivery management record 330 for managing delivery is recorded in the delivery information storage unit 33. This delivery management record 330 is recorded when a delivery item is registered. This delivery management record 330 records data related to a two-dimensional code, a tracking number, a site ID, a sender, a delivery destination, anonymity required, and a delivery status.
[0033] The two-dimensional code data area contains the code obtained from the code print sticker 500 used when shipping this product. issue Data regarding the number is recorded. The tracking number data area records data related to an identifier for checking the delivery status of this delivery item.
[0034] The site ID data area stores data on an identifier for identifying the transaction site (transaction server 20) where the transaction was conducted. The site ID determines how the delivery is handled. The sender data area records data regarding the address and name of the sender of this delivery.
[0035] The delivery destination data area records data relating to the address and name of the delivery destination of the delivery item. In the anonymity necessity data area, a flag for determining whether anonymous delivery is necessary is recorded. The delivery status data area records information about the delivery status of this delivery. In this data area, flags indicating acceptance, in delivery, and delivery completion are recorded.
[0036] As shown in Fig. 4(c), the billing information storage unit 34 records a billing management record 340 related to billing for shipping fees. This billing management record 340 is recorded when delivery is made. This billing management record 340 records data related to a tracking number, a site ID, a two-dimensional code, and shipping fees.
[0037] The tracking number data area records data regarding an identifier for tracking the delivery status of this product. The site ID data area stores data regarding an identifier for identifying the trading site (trading server 20) where the transaction was conducted.
[0038] The two-dimensional code data area contains the code obtained from the code print sticker 500 used when shipping this product. issue Data regarding the number is recorded. The shipping fee data area records data regarding the shipping fee for this delivery item.
[0039] As shown in FIG. 1, a delivery terminal 40 is connected to the delivery management server 30 via a network. This delivery terminal 40 is a computer terminal for inputting the delivery status of a delivery item. The delivery terminal 40 at the delivery acceptance base functions as an acceptance device. A code reader is connected to the delivery terminal 40, and the code reader reads the tracking number affixed to the delivery item. In this case, the delivery terminal 40 transmits the tracking number and tracking information relating to the delivery status to the delivery management server 30. Furthermore, a label printer is connected to the delivery terminal 40 functioning as an acceptance device.
[0040] At the time of shipping, the code printed sticker 500 is affixed to the delivery. As shown in Fig. 5, a two-dimensional code image is printed on the mount 501 of the code printed sticker 500. This two-dimensional code image contains coded information regarding the orderer of the code printed sticker 500, the printing company of the code printed sticker 500, the issue date, issue number, check digit, and shipping confirmation code. This check digit is used to confirm the validity of the issue number and the shipping confirmation code, and is the output value of a confirmation function to which the issue number and the shipping confirmation code are input. The shipping confirmation code is a code used to confirm that the code printed sticker 500 matches the shipping acceptance label. The backing sheet 501 can then be attached to the delivery item using the sealing material on the back side of the backing sheet 501. Furthermore, a delivery confirmation code is printed on the backing sheet 501. A removable storage sticker 502 is attached to this backing sheet 501. The same two-dimensional code image as on the backing sheet 501 is printed on this storage sticker 502. The storage sticker 502 has a memo section. This memo section can be used as a reminder for the sender.
[0041] Next, the delivery management process will be described with reference to FIG. 6 and FIG. First, the application execution unit 11 of the user terminal 10 executes a transaction process (step S101). Specifically, a user who wishes to make a transaction using the transaction server 20 starts a transaction application of the user terminal 10. In this case, the application execution unit 11 accesses the transaction server 20 and transmits a user ID. The transaction server 20 authenticates the user ID using the user information storage unit 22. Next, the transaction server 20 displays a transaction screen on the user terminal 10. The user uses this transaction screen to put up a desired product.
[0042] When a purchaser purchases a listed item using his / her own user terminal 10, the transaction management unit 21 of the transaction server 20 generates a transaction management record 240 with a transaction code attached, and records it in the transaction information storage unit 24. This transaction management record 240 records data related to the transaction code, the listing code, the transaction amount, the seller, the purchaser, the delivery destination, and whether anonymity is required. In this case, the transaction management unit 21 instructs the purchaser to transfer money to the transaction site. Then, when the transaction management unit 21 detects payment from the purchaser, it sends a shipment request for the listed item to the user terminal 10 of the seller. This shipment request includes data related to the purchased listing code.
[0043] The application execution unit 11 of the user terminal 10 that has received the shipping request executes a shipping instruction process (step S102). Specifically, the application execution unit 11 outputs a shipping instruction message. This shipping instruction message includes the auction code.
[0044] In this case, as shown in Fig. 1, the seller packs the product with the shipping instruction listing code in packaging material P1. Then, the seller attaches a code-printed sticker 500 to the packaging material P1. Next, the application execution unit 11 of the user terminal 10 executes a process of photographing a code image (step S103). Specifically, the user launches a transaction application and selects shipping of the listed item on the startup screen. If there are shipping instructions for multiple listed items, the user selects the listed item to be shipped. In this case, the application execution unit 11 launches the camera of the user terminal 10 and outputs a photographing instruction to the display device H13. Then, the user photographs a two-dimensional code image of the code-printed sticker 500 to be used for shipping.
[0045] Next, the application execution unit 11 of the user terminal 10 executes a decoding process (step S104). Specifically, the application execution unit 11 obtains the issue number by decoding the two-dimensional code image. Furthermore, it is possible to confirm that the reading is correct by using information included in the two-dimensional code. In this case, the application execution unit 11 inputs the issue number and the delivery confirmation code into a confirmation function and compares them with the check digit.
[0046] Next, the application execution unit 11 of the user terminal 10 executes a shipping registration process (step S105). Specifically, the application execution unit 11 transmits shipping information to the transaction server 20. The shipping information includes an auction code and issue Include data about the number.
[0047] The transaction management unit 21 of the transaction server 20 that has received the shipping information executes a request process for a tracking number (step S106). Specifically, the transaction management unit 21 extracts the transaction management record 240 in which the auction code of the shipping information is recorded from the transaction information storage unit 24. Then, the transaction management unit 21 adds the following to the transaction management record 240: issueThe transaction management unit 21 records the tracking number. Furthermore, the transaction management unit 21 acquires data related to the address and name recorded in the delivery destination data area of the transaction management record 240. Next, the transaction management unit 21 acquires the user ID recorded in the seller data area of the transaction management record 240. Next, the transaction management unit 21 acquires the name and address associated with the seller's user ID from the user information storage unit 22. Then, the transaction management unit 21 sends a tracking number request to the delivery management server 30. This tracking number request includes the site ID, two-dimensional code, the name and address of the seller, the name and address of the delivery destination, and data related to whether anonymity is required.
[0048] The control unit 31 of the delivery management server 30 that has received the tracking number request executes a process of assigning a tracking number (step S107). Specifically, the delivery management unit 311 of the control unit 31 generates a delivery management record 330 to which a tracking number has been assigned in response to the tracking number request, and records the record in the delivery information storage unit 33.
[0049] Next, the control unit 31 of the delivery management server 30 executes a process of registering the two-dimensional code and the delivery destination information (step S108). Specifically, the delivery management unit 311 of the control unit 31 registers the two-dimensional code ( issue The delivery management unit 311 records data related to the item name, tracking number, site ID, sender (seller's name and address), and delivery destination (delivery destination's name and address). Furthermore, in the anonymity required data area, an anonymity required flag is recorded according to whether anonymity is required. The delivery management unit 311 then transmits a tracking number notification to the transaction server 20. This tracking number notification includes the following: issue Include data regarding shipping number and tracking number.
[0050] The transaction management unit 21 of the transaction server 20 that has received the tracking number notification executes a tracking number notification process (step S109). Specifically, the transaction management unit 21 notifies the user terminals 10 of the seller and the purchaser of the tracking number.
[0051] Next, the application execution unit 11 of the user terminal 10 executes a process for acquiring a tracking number (step S110). Specifically, the application execution unit 11 outputs the acquired tracking number. 1, the seller peels off the storage sticker 502 from the mount 501 of the code-printed sticker 500 and keeps it for himself. If necessary, he records the contents of the product to be shipped and the selling code in the memo field. Furthermore, the application execution unit 11 records and manages the tracking number as history.
[0052] 7, the packaging material P1 with the mount 501 attached thereto is dropped into a post box. The dropped packaging material P1 is collected by a delivery person. Then, the delivery terminal 40 executes the acceptance process (step S201). Specifically, the acceptance person uses the delivery terminal 40 to capture a two-dimensional code image of the mount 501 attached to the collected packaging material P1.
[0053] Next, the delivery terminal 40 executes a decoding process (step S202). Specifically, the delivery terminal 40 obtains the issue number, check digit, and delivery confirmation code by decoding the two-dimensional code image. In this case, the delivery terminal 40 inputs the issue number and delivery confirmation code into a confirmation function and compares it with the check digit to confirm that the reading is correct. Then, the delivery terminal 40 transmits acceptance information to the delivery management server 30. This acceptance information includes the base code of the delivery terminal 40, issue Include data about the number.
[0054] Next, the control unit 31 of the delivery management server 30 executes a process of identifying a delivery destination (step S203). issueThe delivery management unit 311 extracts the delivery management record 330 in which the number is recorded. Then, the delivery management unit 311 records an acceptance flag in the delivery status data area of the delivery management record 330. Next, the delivery management unit 311 checks whether anonymity is required. Then, if the anonymity required flag is recorded, the delivery management unit 311 acquires only the tracking number and delivery destination information. Meanwhile, if the anonymity not required flag is recorded, the delivery management unit 311 acquires the tracking number, sender information, and delivery destination information. Then, the delivery management unit 311 transmits the label information to the delivery terminal 40. This label information includes the tracking number and delivery destination information recorded in the delivery management record 330 (if anonymity is not required, sender information in addition to delivery destination information).
[0055] Next, the delivery terminal 40 executes a printing process for a shipping label (step S204). Specifically, the delivery terminal 40 uses a label printer to print a label based on the label information acquired from the delivery management server 30. This label is printed with the shipping confirmation code read from the code printed sticker 500, the tracking number acquired from the delivery management server 30, and shipping destination information (if anonymity is not required, the shipping destination information and sender information). Then, the person in charge checks the shipping confirmation code on the code printed sticker 500 and the shipping confirmation code on the printed label. After confirming that the two match, the person in charge attaches the label to the packaging material P1.
[0056] Then, the packaging material P1 with the label attached is delivered to the delivery destination via a delivery base. In this case, the control unit 31 of the delivery management server 30 executes a process for registering tracking information (step S205). Specifically, while the packaging material P1 is being delivered, the tracking number is read by the delivery terminal 40 at the delivery base. In this case, the delivery terminal 40 transmits tracking information to the delivery management server 30. This tracking information includes data related to the base code of the delivery terminal 40 and the tracking number. Then, the delivery management unit 311 of the control unit 31 records an in-delivery flag in the delivery status data area of the delivery management record 330 in which the tracking number is recorded.
[0057] The user terminal 10 also executes a process for using the tracking number (step S206). Specifically, when the user wants to check the delivery status, the user starts up a transaction application of the user terminal 10 and selects "check delivery status." In this case, the application execution unit 11 transmits a tracking information request to the delivery management server 30. This tracking information request includes data related to the tracking number.
[0058] In this case, the control unit 31 of the delivery management server 30 executes a delivery status output process (step S207). Specifically, the delivery management unit 311 of the control unit 31 identifies the delivery management record 330 in which the tracking number included in the tracking information request is recorded. Then, if the anonymity required flag is recorded, the delivery management unit 311 transmits the delivery status without including base information to the user terminal 10. In this case, the user terminal 10 outputs the delivery status.
[0059] Then, the control unit 31 of the delivery management server 30 executes a delivery completion registration process (step S208). Specifically, when the packaging material P1 is delivered to the delivery destination, the delivery terminal 40 transmits delivery completion information to the delivery management server 30. This tracking information includes data related to the base code and tracking number of the delivery terminal 40. The delivery management unit 311 of the control unit 31 records a delivered flag in the delivery status data area of the delivery management record 330 in which the tracking number is recorded.
[0060] Next, the control unit 31 of the delivery management server 30 executes a process for determining the fee depending on the site (step S209). Specifically, the settlement unit 312 of the control unit 31 acquires the fee management record 320 in which the site ID of the delivery management record 330 is recorded from the fee information storage unit 32. The delivery management unit 311 then determines the delivery fee (handling) according to the site ID, generates a billing management record 340, and records it in the billing information storage unit 34. This billing management record 340 includes the tracking number, the site ID, issue Include number (2D code) and shipping data.
[0061] Then, when the time for collecting the delivery charges arrives, the control unit 31 of the delivery management server 30 executes a lump-sum billing process (step S210). Specifically, the settlement unit 312 of the control unit 31 extracts the billing management record 340 for each site ID from the billing information storage unit 34 for deliveries delivered during the period from the previous settlement time to the current settlement time. Next, the settlement unit 312 calculates the total amount of the delivery charges recorded in the extracted billing management record 340. The settlement unit 312 then makes a bill including the total amount for each site ID.
[0062] Next, the transaction management unit 21 of the transaction server 20 executes the payment process (step S211). Specifically, the transaction management unit 21 performs the payment process of the shipping fee to the delivery company in response to the payment request.
[0063] According to this embodiment, the following effects can be obtained. (1) In this embodiment, the application execution unit 11 of the user terminal 10 executes a code image capturing process (step S103), a decoding process (step S104), and a shipping registration process (step S105). This allows the transaction to be associated with the delivery. Furthermore, the necessity for anonymous delivery can be set.
[0064] (2) In this embodiment, a two-dimensional code image is printed on the mount 501 of the code printed sticker 500. This two-dimensional code image encodes information regarding the orderer of the code printed sticker 500, the printing company of the code printed sticker 500, the issue date, issue number, check digit, and delivery confirmation code. This makes it possible to confirm the validity of the issue number and delivery confirmation code using the check digit.
[0065] (3) In this embodiment, the transaction management unit 21 of the transaction server 20 executes a process for requesting a tracking number (step S106). This allows the delivery management server 30 to obtain delivery destination information from the transaction server 20. The control unit 31 of the delivery management server 30 then executes a process for assigning a tracking number (step S107) and a process for registering a two-dimensional code and delivery destination information (step S108). This allows the tracking number used for delivery to be set, and the tracking number to be printed and a label to be output.
[0066] In this case, the delivery management unit 311 checks whether anonymity is required. If the anonymity required flag is recorded, the delivery management unit 311 acquires only the tracking number and delivery destination information. This makes it possible to determine how to handle the delivery (whether anonymous delivery is required) based on the anonymous delivery information associated with the delivery number.
[0067] (4) In this embodiment, the transaction management unit 21 of the transaction server 20 executes a tracking number notification process (step S109), which allows the user to obtain the tracking number for checking the delivery status.
[0068] (5) In this embodiment, the delivery terminal 40 executes the acceptance process (step S201) and the decode process (step S202). The control unit 31 of the delivery management server 30 executes the process of identifying the delivery destination (step S203). This allows the delivery destination to be identified. Therefore, the user can post the delivery without writing the delivery destination on the delivery.
[0069] (6) In this embodiment, the delivery terminal 40 executes a printing process for a shipping label (step S204). This allows a label with the delivery destination information printed thereon to be affixed to the delivery. In addition, in the case of anonymous delivery, the sender can be withheld from the delivery destination.
[0070] (7) In this embodiment, the control unit 31 of the delivery management server 30 executes a process for registering tracking information (step S205). This allows the delivery status to be registered using the tracking number.
[0071] (8) In this embodiment, the control unit 31 of the delivery management server 30 executes a delivery completion registration process (step S208) and a fee determination process according to the site (step S209). This makes it possible to bill for the delivery fee for the delivered item. In this case, the handling (fee) of the delivery item can be determined based on the site information associated with the delivery number. Then, a fee with a degree of freedom can be set according to the transaction site.
[0072] This embodiment can be modified as follows: This embodiment and the following modifications can be combined with each other to the extent that there is no technical contradiction. In the above embodiment, the two-dimensional code image of the code-printed sticker 500 contains coded information on the orderer of the code-printed sticker 500, the printing company of the code-printed sticker 500, the issue date, issue number, check digit, and delivery confirmation code. The information included in the two-dimensional code image is not limited to these. For example, a site ID related to a trading site may be included, and the handling of the delivery may be determined according to this site ID. The two-dimensional code image may also contain the size of the delivery. In this case, the fee information storage unit 32 records the delivery fee according to the size. Then, size information is obtained from the two-dimensional code image, and the fee (handling) according to the size is determined. In the above embodiment, the delivery charge (handling) of the delivery item is determined according to the site ID. The information for determining the handling and the handling content are not limited to this. For example, for a delivery item using a 2D code image, the type of delivery item may be specified, and the handling (delivery item management method, delivery method, delivery method, etc.) may be determined according to this type. Then, the control unit 31 of the delivery management server 30 executes the printing process of a shipping label for delivery according to the determined handling (step S204).
[0073] In the above embodiment, the code printed sticker 500 is attached to the delivery. Alternatively, the code printed sticker 500 may be attached to the packaging material P1 in advance. Also, a two-dimensional code image may be printed on the packaging material, and the packaging material on which the two-dimensional code image is printed may be provided to the user. In the above embodiment, the control unit 31 of the delivery management server 30 executes a process for registering tracking information (step S205). In this case, the delivery terminal 40 at the delivery base is used to read the tracking number. Here, the two-dimensional code image of the code printed sticker 500 is read, issue The number may be used to register tracking information.
[0074] In the above embodiment, the application execution unit 11 of the user terminal 10 executes a transaction process (step S101). Data on whether anonymity is required, which is set when the item is put up for sale, is recorded in the transaction information storage unit 24. Alternatively, information on whether anonymity is required may be obtained from the trader or at the time of shipment, and recorded in the transaction information storage unit 24. In the above embodiment, the control unit 31 of the delivery management server 30 executes a process of determining the fee according to the site (step S209). Alternatively or in addition to this, a special offer may be set according to the transaction site. In this case, the transaction management unit 21 of the transaction server 20 that has received the shipping information grants a special offer to the user via the user terminal 10. [Explanation of symbols]
[0075] 10...user terminal, 11...application execution unit, 20...transaction server, 21...transaction management unit, 22...user information storage unit, 23...listing information storage unit, 23...transaction information storage unit, 30...delivery management server, 31...control unit, 311...delivery management unit, 312...settlement unit, 32...fee information storage unit, 33...delivery information storage unit, 34...billing information storage unit, 40...delivery terminal, 500...code printed sticker, 501...backing paper, 502...storage sticker, P1...packaging material.
Claims
1. A control unit connected to a transaction server that manages data related to sender information, delivery destination information, and whether anonymity is required, and an acceptance device that accepts deliveries, A delivery management system including a delivery information storage unit that records delivery destination information including sender information, delivery destination information, and data regarding whether anonymity is required for the issue number, The transaction server obtains an issue number read from a pre-printed code image affixed to the delivery from a user terminal of the sender, and records the issue number in association with sender information, delivery destination information, and data regarding whether anonymity is required; The control unit: Obtaining from the transaction server sender information, delivery destination information, and data on whether anonymity is required, corresponding to the issue number, and recording them in the delivery information storage unit; When an issue number obtained by reading a code image displayed on the delivery item is obtained from the acceptance device, the delivery information storage unit is used to determine whether anonymity is required in handling the delivery item corresponding to the issue number, A delivery management system characterized by determining whether or not to print sender information depending on whether anonymity is required, and outputting a label printed with the delivery destination information recorded in the delivery information storage unit to the acceptance device.
2. The control unit: When the issuing number is obtained from the underwriting device, a tracking code for the issuing number is identified; The delivery management system according to claim 1, characterized in that the tracking code is included in the label.
3. A delivery management system as described in claim 1, characterized in that when the control unit obtains delivery destination information and an issue number obtained by reading a code image displayed on a delivery item from the transaction server, it assigns a tracking code to the issue number, records it in the delivery information storage unit, and returns the tracking code to the transaction server.
4. The method further includes a fee information storage unit that records a delivery fee for a site identifier that manages the transaction server, The control unit: Obtaining a site identifier from the transaction server; Identifying a shipping rate corresponding to the site identifier; 4. The delivery management system according to claim 1, wherein the delivery fee is charged to a transaction server of the site identifier.
5. The fee information storage unit records a delivery fee according to size for the site identifier, The control unit: A delivery management system according to claim 4, characterized in that the size of the delivery item is obtained corresponding to the code image, and a delivery fee corresponding to the site identifier and the size is identified in the fee information storage unit.
6. A delivery management system as described in claim 4 or 5, characterized in that the control unit charges the transaction server a lump sum of the delivery fee for each site identifier depending on the delivery status for a specified period recorded in the delivery information storage unit.
7. A control unit connected to a transaction server that manages data related to sender information, delivery destination information, and whether anonymity is required, and an acceptance device that accepts deliveries, A method for managing delivery using a delivery management system including a delivery information storage unit that records delivery destination information including sender information, delivery destination information, and data on whether anonymity is required for each issue number, The transaction server obtains an issue number read from a pre-printed code image affixed to the delivery from a user terminal of the sender, and records the issue number in association with sender information, delivery destination information, and data regarding whether anonymity is required; The control unit: Obtaining from the transaction server sender information, delivery destination information, and data on whether anonymity is required, corresponding to the issue number, and recording them in the delivery information storage unit; When an issue number obtained by reading a code image displayed on the delivery item is obtained from the acceptance device, the delivery information storage unit is used to determine whether anonymity is required in handling the delivery item corresponding to the issue number, A delivery management method characterized by determining whether or not to print sender information depending on whether anonymity is required, and outputting a label printed with the delivery destination information recorded in the delivery information storage unit to the acceptance device.
8. A control unit connected to a transaction server that manages data related to sender information, delivery destination information, and whether anonymity is required, and an acceptance device that accepts deliveries, A program for performing delivery management using a delivery management system including a delivery information storage unit that records delivery destination information including sender information, delivery destination information, and data regarding whether anonymity is required for an issue number, The transaction server obtains an issue number read from a pre-printed code image affixed to the delivery from a user terminal of the sender, and records the issue number in association with sender information, delivery destination information, and data regarding whether anonymity is required; The control unit, Obtaining from the transaction server sender information, delivery destination information, and data on whether anonymity is required, corresponding to the issue number, and recording them in the delivery information storage unit; When an issue number obtained by reading a code image displayed on the delivery item is obtained from the acceptance device, the delivery information storage unit is used to determine whether anonymity is required in handling the delivery item corresponding to the issue number, A delivery management program characterized by determining whether or not to print sender information depending on whether anonymity is required, and functioning as a means for outputting a label printed with delivery destination information recorded in the delivery information storage unit to the acceptance device.
Citation Information
Patent Citations
Anonymous delivery management system
JP2010026990A
Delivery support system and delivery support method
JP2013015921A
Delivery management device and delivery management program
JP2017073098A
