The first terminal device T1 may request verification of a shipment application from the device 100 of the present disclosure. The first terminal device T1 may transmit the fundamental information, and may transmit the delivery product information which is input individually or registered collectively as a file to the device 100 of the present disclosure.

The device 100 of the present disclosure may store the shipment application including the fundamental information and the delivery product information, and then verify the shipment application. The verification of the shipment application is to check whether the delivery product information input by the seller is correct or not. The device 100 of the present disclosure may check, for example, whether or not required items specified in an item classification code, a delivery address, a country of the delivery address, a unit price, a transaction code, etc. have been input into the delivery product information.

In addition, the device 100 of the present disclosure may check whether or not the information input into the delivery product information is within a normal range or not. For example, in a case where the item classification code or transaction code is not a defined code, or in a case where the delivery address is an address from a place that does not exist or a place where delivery is unavailable, or in a case where the country of the delivery address is a country that does not exist or a country where delivery is unavailable, or in a case where the unit price is a number out of range, the device 100 of the present disclosure may transmit, to the first terminal device T1, a message indicating that the delivery cannot be made with the delivery product information.

In order to verify the delivery product information, the device 100 of the present disclosure may define and store normal input values for each item included in the delivery product information. For example, predefined item classification codes or transaction codes, deliverable addresses, countries to which delivery is available, unit price ranges, etc. may be stored for reference when verification operations are performed.

FIG. 4 is a view briefly illustrating a process of processing verification in the exemplary embodiment of the present disclosure.

When the seller inputs or registers the delivery product information in the first user interface before the first terminal device T1 transmits the fundamental information and delivery product information to the device 100 of the present disclosure, the device 10 of the present disclosure may verify the received delivery product information and transmit a verification result to the first terminal device T1. In the first user interface, information (e.g., a product name, a delivery address, a country code of the delivery address, a recipient name, etc.) about the product to be delivered and the verification result may be displayed.

In this case, the more information about the product to be delivered, the more time it may take when verification is performed. In addition, when delivery product information is collectively submitted as a large file, or when an operation other than verification is performed, there may also arise a problem that a memory capacity being used exceeds a memory capacity of a computing device. In addition, until the verification is completed, the first terminal device T1 may have to continue to wait for a response from the device 100 of the present disclosure, and in the meantime, a connection between the first terminal device T1 and the computing device may also be lost.

In order to avoid the problems that may arise in such a way, the device 100 of the present disclosure may include a verification module 110 and a service module 120. The verification module 110 may be a computing device for executing a verification operation of a shipment application, or may be a software module that is executed on a computing resource of a cloud service or executed on the device 100 of the present disclosure. The service module 120 may be a computing device for executing operations other than the verification, or may be a software module executed on the device 100 of the present disclosure.

As shown in FIG. 4, the first terminal device T1 may first transmit delivery product information to the verification module 110. Then, a connection between the first terminal device T1 and the verification module 110 may be disconnected, and a connection between the first terminal device T1 and the service module 120 may be maintained.

The verification module 110 may store the received delivery product information. The verification module 110 may include a storage, or may store the delivery product information by using a storage service of the cloud service. The verification module 110 may expand a storage or storage service as required, so as to accommodate a large volume of delivery product information files.

The verification module 110 may verify the received delivery product information. When using the cloud service, the verification module 110 may transmit an event or a trigger to a computing resource (e.g., an app engine that implements serverless architecture) of the cloud service, and the computing resource of the cloud service may verify the delivery product information after being activated by the event or the trigger. Information about verification results obtained by the verification module 110 or computing resource of the cloud service may be stored in a database or a storage built by the service module 120.

While the verification module 110 verifies the delivery product information, the first terminal device T1 may exchange data with the service module 120 without waiting. Accordingly, the connection between the first terminal device T1 and the device 100 of the present disclosure is not disconnected, and thus a seller may input another shipment application or delivery product information by using the first terminal device T1.

The first terminal device T1 may query the service module 120 for verification results at regular time intervals. In a case where the verification module 110 has not completed the verification of the delivery product information, the service module 120 may transmit a message indicating that the verification is in progress to the first terminal device T1.

When the verification of the delivery product information is completed, the verification module 110 may store the verification results in the database or storage of the service module 120. When the cloud service is used, the computing resource of the cloud service may terminate an operation thereof. In addition, the service module 120 may receive a query about the verification results from the first terminal device T1 and then transmit the corresponding verification results back to the first terminal device T1.

During verification or after completing the verification, the device 100 of the present disclosure may transmit the delivery product information to a transportation management system S1. The transportation management system S1 may check whether products are deliverable to a country of a delivery address or to a delivery address for each product included in the delivery product information.

The transportation management system S1 may transmit a message informing that delivery is available to the device 100 of the present disclosure when a product is deliverable, and may transmit a message including contents (e.g. a natural disaster, war, bankruptcy, strike, etc.) of reasons why delivery is unavailable to the device 100 of the present disclosure when a product is undeliverable. The device 100 of the present disclosure may transmit a shipment availability message including whether a transportation company can deliver a product to a delivery address or not to the first terminal device T1 along with verification results of the delivery product information.

In the first user interface, the seller may check the verification results of the delivery product information and whether the transportation company can deliver the product to the delivery address. When the delivery is available, the seller may select a menu for a shipment application of third party shipping facility in the first user interface.

By using a third terminal device T3, a third party shipping service provider may check the shipment application of third party shipping facility received from the seller and select a menu for approval or rejection of the request. The third terminal device T3 may transmit items selected by the third party shipping service provider to the device 100 of the present disclosure, and the device 100 of the present disclosure may transmit the items to the first terminal device T1. In the first user interface, the seller may check whether the third party shipping service provider has approved or rejected shipment to a third party shipping facility, and in response to this, may send the product to the third party shipping facility.

In step S1020 of providing the product warehousing information, the device 100 of the present disclosure may provide status information of products warehoused at the third party shipping facility to the terminal device T1 of the seller.

FIG. 5A is a view illustrating a second user interface when the seller checks status of the warehoused products in the exemplary embodiment of the present disclosure. FIG. 5B is a view illustrating an example of a stock label in the exemplary embodiment of the present disclosure.

The device 100 of the present disclosure may transmit a web page having the second user interface for checking product warehousing status of the products sent to the third party shipping facility by the seller to the first terminal device T1. An application program of the first terminal device T1 may display the second user interface shown in FIG. 5A. Alternatively, the application program of the first terminal device T1 may display the second user interface that is programmed.

In the second user interface, the seller may check, for each case of shipment application, progress status (i.e., contents for each progress stage), a stock number (i.e., a number issued at the time of applying a shipment application), the number of deliveries (i.e., the number of products included in the shipment application), the number of invoice outputs, a shipment type (i.e., whether regular or bulk delivery), an expected warehousing date, a product warehousing method, request details of the seller, etc.

A menu for printing a stock label for each case of shipment application may be displayed on the second user interface. When the seller selects a label output menu after selecting a case of one or more shipment applications, the device 100 of the present disclosure may transmit the stock label having a format as shown in FIG. 5B to the first terminal device T1.

The stock label may display a stock number, a country code of a delivery address, a delivery company, a shipment type, a product quantity, a name of a shipper which is a seller, an expected warehousing date, a recipient name, the delivery address, etc. The stock number may be displayed with a barcode, a QR code, or a code recognizable by a scanning device, along with a number.

In the second user interface, the seller may print a stock label of the product to be delivered and then send the stock label and product to the third party shipping facility operated by the third party shipping service provider. After the product is warehoused at the third party shipping facility, inspection of the product may be performed.

In step S1030 of inspecting the warehoused product, the device 100 of the present disclosure may receive volume and weight inspection information of the warehoused product from the terminal device T3 of the third party shipping service provider.

The terminal device T3 of the third party shipping service provider may include a volumetric device. The volumetric device may scan a product and measure a volume (or lengths in horizontal, vertical, and height directions) and weight of the product.

FIG. 6 is a view illustrating a third user interface when the third party shipping service provider inputs the volume and weight inspection information of the product in the exemplary embodiment of the present disclosure.

The device 100 of the present disclosure may transmit a web page having the third user interface for inputting volume and weight inspection information of a warehoused product to the third terminal device T3. An application program of the third terminal device T3 may display the third user interface shown in FIG. 6. Alternatively, the application program of the third terminal device T3 may display the third user interface that is programmed.

When the volumetric device of the third terminal device T3 scans the product, the volume (or the lengths in horizontal, vertical, and height directions) and weight information of the product may be displayed in scanned product information of the third user interface.

In addition, when the third terminal device T3 scans a barcode, QR code, or code recognizable by a scanning device, which is displayed in a stock label, information such as a customer company (i.e., a seller) account information, an invoice number of the product sent to the third party shipping facility by the customer company, a stock number, a product code, a product name, a photo of the product taken by the scanning device may be displayed on the scanned product information of the third user interface.

When the third party shipping service provider checks a volume (or lengths in horizontal, vertical, and height directions) and a weight, which are displayed on the third user interface and then selects a menu for registering volume, information about the inspected product may be displayed in a product inspection list of the third user interface. The information about the inspected product may include the product code, the product name, a warehousing application date, the product lengths in the horizontal, vertical, and height directions, the weight, the stock number, a customer company name, an inspection result, etc.

The third terminal device T3 may transmit the volume (or the lengths in the horizontal, vertical, and height directions) and weight information of the scanned product to the device 100 of the present disclosure. The device 100 of the present disclosure may store the received information. In addition, the device 100 of the present disclosure may transmit data obtained by processing the volume (or the measured lengths in the horizontal, vertical, and height directions) and weight information measured for each product to the third terminal device T3, so as to allow the third terminal device T3 to obtain the volume and weight information without having to measure the volume (or lengths in the horizontal, vertical, and height directions) and the weight of the same product. The device 100 of the present disclosure and the third terminal device T3 may identify whether products are the same as each other by using their product codes. Accordingly, when the third terminal device T3 transmits the scanned product code to the device 100 of the present disclosure, the device 100 of the present disclosure may provide the volume and weight information of a product having the same product code as the received product code to the third terminal device T3.

In step S1040 of providing the shipment information, the device 100 of the present disclosure may provide status information of the product, which is shipped from the third party shipping facility, to the terminal device T1 of the seller. In addition, the device 100 of the present disclosure may receive invoice information from the transportation management system S1 and then transmit the invoice information to the third terminal device T3.

The device 100 of the present disclosure may transmit a message for requesting generation of an invoice for the product for which inspection has been completed to the transportation management system S1. The message may include the delivery product information of the product for which the inspection has been completed, and may include, for example, the product name, an item classification code, a product price, a delivery address, a country code of the delivery address, a recipient name, a unit price, a transaction code, etc.

In response to the message, the transportation management system S1 may generate invoice information for the inspection-completed product and transmit the invoice information to the device 100 of the present disclosure. The invoice information may include, for example, an invoice number, an invoice number-related code such as a barcode, QR code, or code recognizable by a scanning device, the product name, the item classification code, the delivery address, the country of the delivery address, the recipient name, etc.

The third terminal device T3 may transmit a message for requesting printing of an invoice to the device 100 of the present disclosure. In response to the message, the device 100 of the present disclosure may process the invoice information received from the transportation management system S1 according to a prepared format and then transmit the invoice information to the third terminal device T3. The third terminal device T3 may print the processed invoice by using a printing device, and the third party shipping service provider may attach the printed invoice to the product and ship the product to the transportation company.

The device 100 of the present disclosure may request inquiry of the invoice information for the product for which the inspection has been completed from the transportation management system S1. In response to this request, the transportation management system S1 may transmit the invoice information for the inspection-completed product.

FIG. 7 is a view illustrating a fourth user interface through which the seller inquires shipment status in the exemplary embodiment of the present disclosure.

The seller or the third party shipping service provider may select a menu for inquiring the shipment status of the product in application programs of the terminal devices T1 and T3.

The device 100 of the present disclosure may transmit a web page having the fourth user interface through which the seller or the third party shipping service provider inquires the shipment status of the product to the first terminal device T1 and the third terminal device T3. The application programs of the first terminal device T1 and the third terminal device T3 may display the fourth user interface shown in FIG. 7. Alternatively, the application programs of the first terminal device T1 and the third terminal device T3 may display the fourth user interface that is programmed.

In the fourth user interface, the seller or third party shipping service provider may check, for each product, whether the invoice is printed or not, shipment progress status, whether the inspection is completed or not, an order number, a transportation company name, an invoice number, the delivery address, the country code of the delivery address, the recipient name, etc.

The seller or third party shipping service provider may select one product in the fourth user interface and then select a menu for printing an invoice, so as to print the invoice. When the seller selects one product and then selects a menu for cancellation, the first terminal device T1 may transmit order number information of the product for which the third party shipping service has been canceled to the device 100 of the present disclosure. The third party shipping service provider may use the third terminal device T3 to check the product for which the third party shipping service has been cancelled, and then stop shipping the corresponding product.

The device 100 of the present disclosure may receive delivery status information of shipped product from the transportation management system S1. In addition, the device 100 of the present disclosure may display the delivery status information of the shipped product in a shipment progress status item of the fourth user interface and provide the delivery status information to the first terminal device T1 and the third terminal device T3.

FIG. 8A is a timing diagram illustrating a process of making a shipment application of a product by a seller in the exemplary embodiment of the present disclosure.

Before making the shipment application, the seller may query whether a product is deliverable to a delivery address or not. In this case, a first terminal device T1 of the seller may transmit delivery product information to the device 100 of the present disclosure. The device 100 of the present disclosure may verify a delivery address and make a request to a transportation management system S1, so as to query whether the product is deliverable to the delivery address or not. The transportation management system S1 may transmit a message including whether the product is deliverable to the delivery address to the device 100 of the present disclosure, and the device 100 of the present disclosure may send a message including a verification result and whether the product is deliverable to the delivery address to the first terminal device T1.

In a case where the product is deliverable to the delivery address, the shipment application may be made in advance regardless of a time point when the product is warehoused at a third party shipping facility after the product is shipped. After requesting shipment, the seller may request an inquiry about product delivery status (i.e., before product warehousing at the third party shipping facility, product warehousing in progress, completion of the product warehousing, shipment to the third party shipping facility in progress, completion of the shipment, delivery by a transportation company in progress, completion of the delivery, etc.), and the device