Logistics management method and system for ensuring logistics delivery period

Abstract

Disclosed are a logistics management method and system for ensuring a logistics delivery period. A logistics management method according to one embodiment may comprise the steps of: calculating a shipping deadline compliance rate of a product order for a product of a seller for which an arrival guarantee tag is exposed in a product unit or a store unit; and controlling whether to expose the arrival guarantee tag in the product unit or the store unit on the basis of the shipping deadline compliance rate.

Description

Logistics management method and system to ensure logistics delivery period

[0001] The following description relates to logistics management methods and systems for ensuring logistics delivery periods.

[0002] Fulfillment refers to a service in which a logistics company handles the entire logistics process, from product preparation to packaging and delivery, for sellers. Traditionally, online shopping mall sellers contracted directly with couriers to collect and ship orders. Alternatively, they used 3PL (Third Party Logistics), which pre-stocked products in the logistics company's warehouse and delivered them through a contracted courier. While 3PLs simply handled product warehousing, storage, and delivery, fulfillment is an integrated service that pre-stocks the seller's inventory at a logistics center and then handles warehousing, preparation, packaging, delivery, and even exchanges / refunds based on customer orders. The biggest advantage of fulfillment is its speed, and bundled shipping is only possible for products already in the logistics center.

[0003] Provides a logistics management method and system that can provide seller arrival guarantee service for products by managing the shipment of products from the seller's own warehouse.

[0004] A logistics management method of a computer device including at least one processor, comprising: a step of calculating a delivery deadline compliance rate for a product order for a seller's product on which an arrival guarantee tag is displayed by the at least one processor on a product-by-product or store-by-store basis; and a step of controlling, by the at least one processor, whether to display the delivery guarantee tag by the product-by-product or store-by-store basis.

[0005] According to one side, the step of calculating the above-mentioned dispatch deadline compliance rate may be characterized by calculating the ratio of product orders processed for dispatch within the dispatch deadline among product orders for a first period set based on the aggregation date as the above-mentioned dispatch deadline compliance rate.

[0006] According to another aspect, the arrival guarantee tag is displayed on a product-by-product basis for a product whose delivery attribute is set to arrival guarantee, and the step of controlling whether to display the arrival guarantee tag may include a step of changing the delivery attribute of a product whose delivery attribute is arrival guarantee from arrival guarantee to general delivery, which is a delivery attribute in which the arrival guarantee tag is not displayed, when the delivery deadline compliance rate is less than a preset first threshold.

[0007] According to another aspect, the step of controlling whether or not to expose the arrival guarantee tag may further include a step of retrieving the right to use the arrival guarantee tag for a product unit from the seller, if the compliance rate of the delivery deadline is less than a preset first threshold and there is a non-delivery processing case for a product with the delivery attribute of arrival guarantee.

[0008] According to another aspect, the step of controlling whether or not to expose the arrival guarantee tag may further include a step of providing the seller with the right to use the arrival guarantee tag for the product unit again based on the seller processing all of the unsent items for shipment.

[0009] According to another aspect, the arrival guarantee tag is exposed for products in the store unit of the seller, and the step of controlling whether to expose the arrival guarantee tag may include the step of accumulating one warning to a store whose compliance rate of the delivery deadline for product orders in the store unit is below a second threshold; and the step of revoking the store unit usage right of the arrival guarantee tag from the seller on the first warning issuance date when the number of warnings accumulated within the most recent preset second period becomes the first number.

[0010] According to another aspect, the step of controlling whether the arrival guarantee tag is exposed may further include a step of re-providing the store-unit usage right of the arrival guarantee tag to the seller whose store-unit usage right of the arrival guarantee tag has been revoked if both the first condition and the second condition are satisfied, wherein the first condition includes a condition in which the compliance rate of the delivery deadline of product orders during a preset third period based on the date of application for the store-unit usage right of the arrival guarantee tag is equal to or greater than a third threshold value, and the second condition includes a condition in which the number of product orders during a preset fourth period based on the date of application for the store-unit usage right of the arrival guarantee tag is equal to or greater than a preset number.

[0011] According to another aspect, the logistics management method may further include a step of providing a user interface capable of searching at least one of information on product orders that have not met the delivery deadline for the product and information on products for which the right to use the arrival guarantee tag has been revoked on a product-by-product basis, by the at least one processor.

[0012] A computer program stored on a computer-readable recording medium is provided for executing the above method on a computer device in combination with a computer device.

[0013] A computer-readable recording medium having recorded thereon a program for executing the above method on a computer device is provided.

[0014] A computer device is provided, comprising at least one processor implemented to execute instructions readable by a computer device, wherein, by the at least one processor, for a product of a seller for which an arrival guarantee tag is displayed on a product unit or store unit basis, a delivery deadline compliance rate of a product order is calculated, and based on the delivery deadline compliance rate, whether or not to display the arrival guarantee tag on a product unit or store unit basis is controlled.

[0015] You can provide seller arrival guarantee service for products by managing the shipment of products from the seller's own warehouse.

[0016] FIG. 1 is a diagram illustrating an example of a network environment according to one embodiment of the present invention.

[0017] FIG. 2 is a block diagram illustrating an example of a computer device according to one embodiment of the present invention.

[0018] FIG. 3 is a diagram illustrating an example of a logistics management system according to one embodiment of the present invention.

[0019] FIG. 4 is a drawing illustrating an example of exposing a seller arrival guarantee tag together with a product in one embodiment of the present invention.

[0020] FIG. 5 is a diagram illustrating an example of a standard for product orders that are the subject of aggregation for product unit usage rights in one embodiment of the present invention.

[0021] FIGS. 6 and 7 are drawings showing examples of a user interface provided to a seller for product management in a seller warehouse according to one embodiment of the present invention.

[0022] FIG. 8 is a diagram illustrating an example of a standard for product orders that are aggregation targets for store unit usage rights in one embodiment of the present invention.

[0023] FIG. 9 is a diagram illustrating an example of conditions for retrieving usage rights per store unit in one embodiment of the present invention.

[0024] Figure 10 is a flowchart illustrating an example of a logistics management method according to one embodiment of the present invention.

[0025] Hereinafter, the detailed description will be given with reference to the attached drawings.

[0026] The logistics management system according to embodiments of the present invention may be implemented by at least one computer device. In this case, the computer device may be equipped with and run a computer program according to an embodiment of the present invention, and the computer device may perform the logistics management method according to embodiments of the present invention under the control of the computer program. The computer program described above may be stored on a computer-readable recording medium, which may be coupled to the computer device and cause the computer to execute the logistics management method.

[0027] FIG. 1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention. The network environment of FIG. 1 represents an example including a plurality of electronic devices (110, 120, 130, 140), a plurality of servers (150, 160), and a network (170). FIG. 1 is merely an example for explaining the invention, and the number of electronic devices or servers is not limited to that of FIG. 1. In addition, the network environment of FIG. 1 merely illustrates one example of environments applicable to the present embodiments, and the environments applicable to the present embodiments are not limited to the network environment of FIG. 1.

[0028] The plurality of electronic devices (110, 120, 130, 140) may be fixed terminals or mobile terminals implemented as computer devices. Examples of the plurality of electronic devices (110, 120, 130, 140) include smart phones, mobile phones, navigation systems, computers, laptops, digital broadcasting terminals, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Players), tablet PCs, etc. For example, in FIG. 1, the shape of a smart phone is shown as an example of the electronic device (110), but in embodiments of the present invention, the electronic device (110) may actually mean one of various physical computer devices that can communicate with other electronic devices (120, 130, 140) and / or servers (150, 160) via a network (170) using a wireless or wired communication method.

[0029] The communication method is not limited, and may include not only a communication method that utilizes a communication network (e.g., a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network) that the network (170) may include, but also short-range wireless communication between devices. For example, the network (170) may include any one or more of a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like. In addition, the network (170) may include any one or more of a network topology including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree, or a hierarchical network.

[0030] Each server (150, 160) may be implemented as a computer device or multiple computer devices that communicate with multiple electronic devices (110, 120, 130, 140) via a network (170) to provide commands, codes, files, contents, services, etc. For example, the server (150) may be a system that provides services to multiple electronic devices (110, 120, 130, 140) connected via a network (170).

[0031] FIG. 2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention. Each of the plurality of electronic devices (110, 120, 130, 140) or servers (150, 160) described above can be implemented by the computer device (200) illustrated in FIG. 2.

[0032] Such a computer device (200) may include a memory (210), a processor (220), a communication interface (230), and an input / output interface (240), as illustrated in FIG. 2. The memory (210) may be a computer-readable recording medium, and may include a random access memory (RAM), a read only memory (ROM), and a non-permanent mass storage device such as a disk drive. Here, the non-permanent mass storage device such as a ROM and a disk drive may be included in the computer device (200) as a separate permanent storage device distinct from the memory (210). In addition, an operating system and at least one program code may be stored in the memory (210). These software components may be loaded into the memory (210) from a computer-readable recording medium separate from the memory (210). Such a separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD / CD-ROM drive, a memory card, etc. In another embodiment, the software components may be loaded into the memory (210) via a communication interface (230) other than a computer-readable recording medium. For example, the software components may be loaded into the memory (210) of the computer device (200) based on a computer program installed by files received over a network (170).

[0033] The processor (220) may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the processor (220) via the memory (210) or the communication interface (230). For example, the processor (220) may be configured to execute instructions received according to program code stored in a storage device such as the memory (210).

[0034] The communication interface (230) may provide a function for the computer device (200) to communicate with other devices (e.g., the storage devices described above) via the network (170). For example, requests, commands, data, files, etc. generated by the processor (220) of the computer device (200) according to program codes stored in a recording device such as the memory (210) may be transmitted to other devices via the network (170) under the control of the communication interface (230). Conversely, signals, commands, data, files, etc. from other devices may be received by the computer device (200) via the communication interface (230) of the computer device (200) via the network (170). Signals, commands, data, etc. received via the communication interface (230) may be transmitted to the processor (220) or the memory (210), and files, etc. may be stored in a storage medium (the permanent storage device described above) that the computer device (200) may further include.

[0035] The input / output interface (240) may be a means for interfacing with an input / output device (250). For example, the input device may include a device such as a microphone, a keyboard, or a mouse, and the output device may include a device such as a display or a speaker. As another example, the input / output interface (240) may be a means for interfacing with a device that integrates input and output functions, such as a touchscreen. At least one of the input / output devices (250) may be configured as a single device with the computer device (200). For example, a touchscreen, a microphone, a speaker, etc. may be implemented in a form included in the computer device (200), such as a smartphone.

[0036] Additionally, in other embodiments, the computer device (200) may include fewer or more components than those illustrated in FIG. 2. However, it is not necessary to explicitly illustrate most conventional components. For example, the computer device (200) may be implemented to include at least some of the input / output devices (250) described above, or may further include other components such as a transceiver, a database, etc.

[0037] FIG. 3 is a diagram illustrating an example of a logistics management system according to one embodiment of the present invention. The logistics management system (300) may include an ordering platform (310), a logistics company platform (320), a logistics data platform (330), a seller center (340), and a logistics center (350).

[0038] The order platform (310) is a platform that provides a channel through which the products of sellers are displayed. Although FIG. 3 illustrates a single order platform (310), the order platforms of various affiliated companies may be affiliated and included in the logistics management system (300). Such order platforms (310) may include not only platforms operated by companies but also platforms operated by individuals. In addition, the order platform (310) may also include a platform linked to an operator who operates a logistics data platform (330). For example, if the logistics data platform (330) is provided in conjunction with a portal site that provides various services such as an e-mail service, a blog service, a shopping service, a news service, a map service, a translation service, and a payment service, the seller's products may be displayed through various channels of the portal site, and orders for the products may be processed through the shopping service and / or the payment service, or a separate smart store.

[0039] The logistics platform (320) is a platform that manages storage, delivery, etc. of logistics as products of sellers. In FIG. 3, one logistics platform (320) is shown, but the logistics platforms of various affiliated companies may be affiliated and included in the logistics management system (300), and the platforms of individual courier companies may also be affiliated and included in the logistics management system (300).

[0040] The logistics data platform (330) can form a fulfillment alliance in conjunction with the order platform (310) and the logistics company platform (320). To this end, the logistics data platform (330) can collect and process information on overall logistics related to product sales and delivery from the order platform (310) and the logistics company platform (320). To this end, the logistics data platform (330) can include a feed interface (331), an aggregation pipeline (332), and a persistent layer (333).

[0041] As illustrated in FIG. 3, the logistics data platform (330) can collect seller information, sales product information, order information, etc. from the order platform (310) through the feed interface (331), and can collect logistics company information, center information (e.g., information on logistics centers), logistics product information (e.g., information on products received at the logistics center), inventory information (information on the inventory of products received at the logistics center), etc. from the logistics company platform (320). For example, the feed interface (331) can collect information through a scheduled download method, which is a method of downloading information according to a preset download schedule through a web server or FTP (File Transfer Protocol) server provided by an affiliate of the order platform (310) and / or the logistics company platform (320). As another example, the feed interface (331) can collect information through an SFTP upload method, which transfers files from the affiliate's system through SFTP (Secure File Transfer Protocol) through scheduling by the affiliate. As another example, the feed interface (331) may collect information through files uploaded via a front-end browser provided by a management center, such as a seller center (340) or a logistics center (350). The seller center (340) may correspond to a user interface through which a sales manager (seller) can access to upload information or manage product-related settings. Similarly, the logistics center (350) may correspond to a user interface through which a logistics manager can access to upload information or manage logistics-related settings. As another example, the logistics data platform (330) may provide a real-time API (Application Programming Interface) to collect information on specific items. For example, the real-time API may be utilized for additional processing of data linkage items that require real-time performance among the items requiring collection.This real-time API can serve as a complement to the feed interface (331). Furthermore, feeds can be processed in a near-real-time synchronization manner by utilizing the real-time API. This collection method is more efficient for processing and preventing large amounts of data loss than a RESTful-based API because it prevents the loss of key data through periodic synchronization after initial synchronization of a large number of data snapshots. Furthermore, information collected via SFTP upload or scheduled download can be collected in TSV (Tab Separated Values) format, while information collected via the real-time API can be collected in JSON format, but is not limited thereto.

[0042] The aggregation pipeline (332) can process operations for aggregating the collected information. For example, each of the ordering platform (310) and the logistics company platform (320) may have their own data management format. Accordingly, the aggregation pipeline (332) can convert and aggregate the collected information according to a format predefined for the logistics data platform (330) and store it in a persistent layer (333). At this time, the aggregation pipeline (332) can perform the functions of extracting data for each item from the collected information, checking for and filtering duplicate data, checking the validity of the extracted data (determining whether the extracted data conforms to the predefined format and changing the format of the data if it does not conform), and arranging the data order and storing it in the persistent layer (333). If necessary, the aggregation pipeline (332) may further include a monitoring function for the administrator, a function for deleting data when information is not continuously received from affiliates, and a function for reporting the status of the collected information (collection success, failure, etc.) to affiliates.

[0043] In some embodiments, when using a real-time API, the process of extracting data for each item from the collected information, checking for duplicate data and filtering it, determining whether the extracted data conforms to a predefined format, and changing the format of the data if it does not conform can be processed using the functions of the API.

[0044] Basically, the collected information can be stored in a persistent layer (333) in an upsert manner that is always accumulated, and when data needs to be deleted, a method of separately marking it for deletion can be used. The persistent layer (333) can be implemented through a Distributed Database Management System (DDBMS), a Hadoop Distributed File System (HDFS), Amazon Simple Storage Service (S3), and / or a log database. However, this is only one example, and the structure for storing the collected information is not limited to the examples described above.

[0045] In addition, according to an embodiment, the logistics data platform (330) may further provide a function for reprocessing data in response to changes in data stored in the permanent layer (333) through the aggregation pipeline (332), a function for transmitting at least some of the reprocessed data to the seller center (340) or the logistics center (350), a function for reprocessing the validity check of the reprocessed data and the sorting of the data order, etc. Accordingly, information (e.g., logistics product information, inventory information, etc.) that is changed in an affiliate (e.g., logistics company platform (320)) can be managed in real time or near real time by the logistics data platform (330).

[0046] The seller center (340) can provide a function that allows sales managers to access the center, and the logistics center (350) can provide a function that allows logistics managers to access the center to upload information or check monitoring information on information collection.

[0047] FIG. 4 is a diagram illustrating an example of displaying a seller arrival guarantee tag along with a product according to an embodiment of the present invention. The logistics data platform (330) can provide a seller arrival guarantee service that guarantees the arrival date of a product to a buyer and compensates if the product does not arrive on the guaranteed date. In this case, the seller arrival guarantee tag can be displayed along with the seller's product or store at the store level and / or product level of the seller participating in the seller arrival guarantee service. The embodiment of FIG. 4 illustrates an example of a user interface (410) for shopping search. In this case, the seller arrival guarantee tag, as shown in the dotted boxes (420, 430), can be displayed together with the product displayed through the user interface (410). The display of such a seller arrival guarantee tag can induce an influx of buyers to the channel for purchasing the seller's product.

[0048] Sellers can participate in the Seller Arrival Guarantee Service by agreeing to adhere to the shipping deadline. However, this Seller Arrival Guarantee Service carries the risk of increased shipping delays and compensation expenses if sellers voluntarily fail to adhere to the shipping deadline. Accordingly, the logistics data platform (330) can suspend the display of the Seller Arrival Guarantee tag for each product or store of a seller who does not meet the preset conditions related to compliance with the shipping deadline. This suspension of the Seller Arrival Guarantee tag can be maintained until the seller again meets the preset conditions. Once the seller again meets the preset conditions, the Seller Arrival Guarantee tag can be displayed again with the seller's products or stores.

[0049] FIG. 5 is a diagram illustrating an example of the criteria for product orders that are subject to aggregation for product-level usage rights in accordance with one embodiment of the present invention. The embodiment of FIG. 5 illustrates examples of which product orders can be subject to aggregation in relation to the seller's guaranteed arrival service for each product. For example, the aggregation results may be sequentially reflected daily between 11:00 AM and 2:00 PM. However, due to the time required for aggregation and result reflection, a difference of 5 to 10 minutes may occur daily. Furthermore, product orders with a delivery deadline of 10:00 AM on the day before the aggregation date and 10:00 AM on the aggregation date and a delivery attribute of "Seller Guaranteed Arrival" may be subject to aggregation. In this case, the logistics data platform (330) can determine which product orders are subject to aggregation and whether they meet the delivery deadline based on the delivery deadline initially set at the time of the product order (not the delayed delivery deadline due to delayed delivery processing). Figure 5 shows an example in which “Product Order 1” and “Product Order 2”, whose delivery attribute is “Guaranteed Arrival by Seller” and whose delivery deadline is after 10:00 AM on the day before the aggregation date and before 10:00 AM on the aggregation date, are selected as aggregation targets.

[0050] Additionally, a standard is required to automatically change the product-specific delivery attribute to "Not in Compliance with Delivery Deadline" for products that do not meet the delivery deadline. For example, "Guaranteed Seller Arrival" products with a delivery deadline compliance rate of less than n% (e.g., 90%) based on daily aggregate results may be subject to automatic change in delivery attribute. Here, the delivery deadline compliance rate may refer to the percentage of product orders that were processed for delivery within the delivery deadline among all product orders subject to aggregation. For example, if 97 out of 100 product orders for a specific product A were shipped within the delivery deadline, the delivery deadline compliance rate for that product A may be 97%. If there are no product orders subject to aggregation, the delivery deadline compliance rate for that day may be excluded from calculation.

[0051] At this time, the logistics data platform (330) may select products with a delivery attribute of "Guaranteed Seller Arrival" and a delivery deadline compliance rate of less than n% as targets for automatic change of delivery attributes. In this case, the logistics data platform (330) may change the delivery attribute of products selected for automatic change of delivery attributes from "Guaranteed Seller Arrival" to "Standard Delivery" between 11:00 AM and 2:00 PM on the aggregation date.

[0052] Meanwhile, at this point in time, the seller has the right to use the seller arrival guarantee service, so the seller can change the delivery attribute of the product to "Seller Arrival Guarantee."

[0053] Furthermore, criteria are required for revoking a seller's right to use the seller arrival guarantee service. For example, among products selected for automatic change of delivery attributes, products with seller arrival guarantees that have been processed as unshipped may be selected for revocation of the right to use. "Unshipped" items here may refer to "seller arrival guarantee" product orders that have not been processed for delivery by 10:00 AM on the aggregation date. In this case, the logistics data platform (330) may revoke the seller's right to use the seller arrival guarantee service for the relevant product between 11:00 AM and 2:00 PM on the aggregation date. This may mean that the system processes the request so that the seller cannot change the delivery attribute of the relevant product back to "seller arrival guarantee." In other words, the logistics data platform (330) may revoke the right to use the seller's product with an unshipped item among products selected for automatic change of delivery attributes, thereby restricting the seller from further using the "seller arrival guarantee" delivery attribute for the relevant product.

[0054] The right to use the product can be re-issued to the seller around 11:00 AM the day after the seller has processed the shipment of all outstanding items for the product. In this case, the seller can re-set the product's delivery attribute to "Guaranteed Delivery to Seller."

[0055] FIGS. 6 and 7 are diagrams illustrating examples of user interfaces provided to sellers for managing products in their warehouses, according to one embodiment of the present invention. FIGS. 6 and 7 each illustrate examples of user interfaces that enable sellers to manage information on products registered by them. These user interfaces can be provided through the seller center (340) described above. FIG. 6 illustrates an example of searching for information on products for which the seller has the right to use the product but has not yet met the shipping deadline (unshipped items), and FIG. 7 illustrates an example of searching for information on products for which the right to use has been revoked. By providing these user interfaces to sellers through the seller center (340), the logistics data platform (330) can encourage sellers to voluntarily meet the shipping deadline.

[0056] Figure 8 is a diagram illustrating an example of the criteria for product orders that are subject to aggregation for store-level usage rights in accordance with one embodiment of the present invention. The embodiment of Figure 8 illustrates examples of which product orders can be subject to aggregation in relation to the usage rights of the seller's guaranteed delivery service at the store level. For example, the aggregation results may be sequentially reflected daily between 11:00 AM and 2:00 PM. Even in this case, aggregation and result reflection may take time, resulting in a 5-10 minute discrepancy between days. Furthermore, product orders with a delivery deadline of "Seller Guaranteed Delivery" and a delivery attribute of "Seller Guaranteed Delivery" may be subject to aggregation. In this case, the logistics data platform (330) can determine which product orders are subject to aggregation and whether they meet the delivery deadline based on the delivery deadline initially set at the time of the product order (not the delayed delivery deadline due to delayed delivery processing). Orders canceled before the shipping deadline may be excluded from the aggregated data. Figure 8 shows an example where "Product Order 1" and "Product Order 2," whose delivery attribute is "Guaranteed Delivery by Seller" and whose shipping deadline is 13 days before the aggregation date and after 10:00 AM but before 10:00 AM on the aggregation date, are selected for aggregation.

[0057] Figure 9 is a diagram illustrating an example of conditions for revoking store-level usage rights in one embodiment of the present invention. First, the logistics data platform (330) may issue a single warning to a store whose store-level shipping deadline compliance rate is less than m% (e.g., 95%). The store-level shipping deadline compliance rate may be calculated as the percentage of aggregated product orders across all sales channels that were shipped within the shipping deadline. If there are no aggregated product orders as of the aggregation date, the calculation of the store-level shipping deadline compliance rate for that day may be excluded. Furthermore, a warning may not be issued for 14 days from the date of warning even if the store-level shipping deadline compliance rate is less than 95%. In this case, if three warnings have been issued in the past three months, the logistics data platform (330) may revoke the store-level seller arrival guarantee service usage rights on the third warning date. Figure 9 illustrates an example where, as of September 1 (9 / 1), if three warnings have been accumulated in the past three months, the user's access rights are revoked on the third warning date. Figure 9 also illustrates an example where, even if a third warning has been issued, the user's access rights are maintained if three warnings have not been accumulated in the past three months. When store-level access rights are revoked, the delivery attribute of all "Seller Guaranteed Delivery" products of the seller may be changed to "Standard Delivery," and the system may be configured to prevent sellers from setting / changing the delivery attribute of products to "Seller Guaranteed Delivery."

[0058] In addition, sellers can reapply for the seller arrival guarantee service after 14 days from the date of revocation of the right to use the seller arrival guarantee service. The seller center (340) may provide a user interface through which sellers can check the date when reapplication is possible. At this time, the logistics data platform (330) may re-grant the seller the right to use the seller arrival guarantee service based on the following conditions (conditions 1 to 3). The first condition may be a condition in which the seller changes the delivery attribute of the product(s) to be operated as "Seller Arrival Guaranteed" to "Depart Today" (setting the "Depart Today" standard time for the product(s) from 3:00 PM to 11:30 PM). The second condition may be a condition in which the seller's compliance rate for the delivery deadline of "Depart Today" product orders for the two weeks immediately preceding the date of reapplication for the right to use the service is a% (for example, 97%) or higher. Additionally, the third condition may be that the number of "Departing Today" product orders exceeded 200 in the two weeks preceding the seller's re-application for access rights. If the seller satisfies all of the first through third conditions, the logistics data platform (330) may re-grant the seller access to the seller arrival guarantee service.

[0059] In the examples above, the numerical values ​​such as time period, ratio, and number of product orders are all examples and are not limited thereto.

[0060] Table 1 below shows an example of product order judgment for product-specific usage rights aggregation.

[0061] #ProductOrderNumberDeliveryTypeOrderDateDeliveryDeadlineWhetherTotalAggregationEffectiveTimeTotalAggregation1111SellerWorksGuaranteed2024.6.210:002024.6.323:59O2024.6.411:002112SellerWorksGuaranteed2024.6.210:002024.6.423:59O2024.6.511:003113SellerWorksGuaranteed2024.6.223:002024.6.504:00O2024.6.511:004114DepartingToday2024.6.223:002024.6.320:00X

[0062] Here, Tables 1 and 2 in Table 1 illustrate examples where the aggregated reflection date differs even when the order date is the same but the shipping deadline is different. The aggregated reflection date can be set based on the shipping deadline. Furthermore, Table 1 3 illustrates an example where the aggregated reflection date is determined based on the shipping deadline, even if the shipping deadline is set to a date after the order date or the day after the order date due to a holiday or other reasons. Furthermore, Table 1 4 indicates that only product orders with a delivery type of "Guaranteed Delivery by Seller" are subject to aggregation.

[0063] Table 2 below presents examples of the results of determining whether a product order met its shipping deadline and whether it was processed as unshipped. The example in Table 2 assumes that the aggregated results will be reflected at 11:00 AM on June 2, 2024.

[0064] #Product order numberProduct numberDelivery deadlineDelivery processing dateDelivery deadline complianceNon-delivery processing11111112024.6.204:002024.6.123:00O-2112112024.6.204:002024.6.200:00O-3113112024.6.204:002024.6.201:00O-4114122024.6.123:592024.6.122 :00O-5115122024.6.123:592024.6.202:00XX6116122024.6.123:592024.6.203:00XX7117112024.6.204:002024.6.201:00O-8118112024.6.204:002024.6.209:00XO9119112024.6.204:00-(Unprocessed)XO

[0065] Table 3 below shows examples of the results of determining whether to automatically change the delivery attributes for each product and whether to revoke the right to use.

[0066] CASE Product number Seller arrival guarantee Product order delivery deadline compliance number Delivery deadline compliance rate Number of non-delivery processing Delivery attribute Automatic change Whether to retrieve usage rights A1133100%-X-B123133.33%0OXC113133.33%2OOD130---X-

[0067] In Table 3, A represents an example in which the delivery attribute of "Guaranteed Seller Arrival" is maintained, B represents an example in which the delivery attribute of "Guaranteed Seller Arrival" is automatically changed to "Standard Delivery," and C represents an example in which not only the delivery attribute is automatically changed, but also the usage rights are revoked. In Table D, the delivery deadline compliance status can be set to "Insufficient Data," and the delivery attribute can be maintained as "Guaranteed Seller Arrival." Figure 10 is a flowchart illustrating an example of a logistics management method according to an embodiment of the present invention. The logistics management method according to this embodiment can be performed by a computer device (200) implementing a logistics data platform (330). At this time, the processor (220) of the computer device (200) can be implemented to execute control instructions according to the code of the operating system included in the memory (210) or the code of at least one computer program. Here, the processor (220) can control the computer device (200) to perform steps (1010 to 1030) included in the method of FIG. 10 according to control commands provided by code stored in the computer device (200).

[0068] In step (1010), the computer device (200) may calculate the delivery deadline compliance rate for product orders of a seller for which an arrival guarantee tag is displayed, either on a product-by-product or store-by-store basis. For example, the computer device (200) may calculate the delivery deadline compliance rate as the ratio of product orders processed for delivery within the delivery deadline among product orders during a first period set based on the aggregation date. In this case, the first period may be set to be different for each product and each store. For example, the first period for each product may be one day (for example, from 10:00 PM on the day before the aggregation date to 10:00 AM on the aggregation date). On the other hand, the first period for each store may refer to the entire period during which products are sold through the store.

[0069] In step (1020), the computer device (200) can control whether to display the arrival guarantee tag for each product or store based on the compliance rate of the delivery deadline.

[0070] In one embodiment, the arrival guarantee tag may be displayed on a per-item basis for products whose delivery attribute is set to arrival guarantee. A seller may set the delivery attribute to "Seller Arrival Guaranteed" on a per-item basis to display the arrival guarantee tag for specific products. In this case, the computer device (200) may change the delivery attribute of a product whose delivery deadline compliance rate is below a preset first threshold and whose delivery attribute is arrival guarantee from arrival guarantee to general delivery, which does not display the arrival guarantee tag. In this case, since the seller has the right to use the arrival guarantee tag on a per-item basis, the seller may change the delivery attribute back to arrival guarantee ("Seller Arrival Guaranteed"). Meanwhile, if the delivery deadline compliance rate is below a preset first threshold and there is an unshipped case for a product whose delivery attribute is arrival guarantee, the computer device (200) may revoke the right to use the arrival guarantee tag on a per-item basis from the seller. In this case, the seller cannot change the delivery attribute of the product to "Arrival Guaranteed" because the seller does not have the right to use the arrival guarantee tag at the product level. The arrival guarantee tag is not displayed for products whose delivery attribute is not "Arrival Guaranteed." Meanwhile, the computer device (200) may re-provide the seller with the right to use the arrival guarantee tag at the product level based on the seller having processed all unshipped items as shipped. In this case, the seller can change the delivery attribute of the product back to "Arrival Guaranteed," and the arrival guarantee tag may be displayed again along with information about the product.

[0071] In another embodiment, the arrival guarantee tag may be displayed for products within a seller's store. In this case, the seller may set the delivery attribute to "Seller Arrival Guaranteed" for each product to ensure that the arrival guarantee tag is displayed for specific products. In this case, the computer device (200) may issue and accumulate one warning to a store whose order delivery deadline compliance rate for each store falls below a second threshold. Furthermore, if the number of warnings accumulated within a recent, preset second period (e.g., three months) reaches the first number (e.g., three warnings), the computer device (200) may revoke the seller's store-level access to the arrival guarantee tag on the first warning issuance date. Once the store-level access is revoked, the arrival guarantee tag is no longer displayed for any products within the store. This store-level access may be re-provided to the seller if the seller satisfies both the first and second conditions. Here, the first condition may include a condition in which the compliance rate of product orders for delivery deadlines exceeds a third threshold during a preset third period (e.g., two weeks) based on the date of application for store-level access to the arrival guarantee tag. Furthermore, the second condition may include a condition in which the number of product orders exceeds a preset number (e.g., 200) during a preset fourth period (e.g., two weeks) based on the date of application for store-level access to the arrival guarantee tag. Product orders counted under the first and second conditions may be those with a delivery attribute of "Depart Today."

[0072] In step (1030), the computer device (200) may provide a user interface capable of searching for at least one of information about product orders that have not met their delivery deadlines and information about products for which the right to use the arrival guarantee tag has been revoked. Examples of such a user interface have been described in detail in FIGS. 6 and 7 .

[0073] In this way, according to embodiments of the present invention, it is possible to provide a seller arrival guarantee service for products by managing the shipment of products from the seller's own warehouse.

[0074] The systems or devices described above may be implemented as hardware components, or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used alone; however, one of ordinary skill in the art will recognize that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, a processing unit may include multiple processors, or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.

[0075] Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may independently or collectively command the processing device. The software and / or data may be embodied in any type of machine, component, physical device, virtual equipment, computer storage medium, or device for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0076] The method according to the embodiment may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program commands, data files, data structures, etc., singly or in combination. The medium may continuously store a computer-executable program, or may temporarily store it for execution or download. In addition, the medium may be various recording means or storage means in the form of a single or multiple hardware combinations, and is not limited to a medium directly connected to a computer system, but may also be distributed over a network. Examples of the medium may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and those configured to store program commands, including ROM, RAM, and flash memory. In addition, examples of other media may include recording media or storage media managed by app stores that distribute applications, sites that supply or distribute various software, servers, etc. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0077] Although the embodiments described above have been described by way of limited examples and drawings, those skilled in the art will appreciate that various modifications and variations can be made based on the above teachings. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.

[0078] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

1. A method for managing logistics of a computer device including at least one processor, A step of calculating the compliance rate of the delivery deadline of a product order for a seller's product for which an arrival guarantee tag is displayed by at least one processor on a product-by-product or store-by-store basis; and A step of controlling whether to display the arrival guarantee tag in units of products or units of stores based on the compliance rate of the delivery deadline by at least one processor. A logistics management method including:

2. In paragraph 1, The steps for calculating the above delivery deadline compliance rate are: A logistics management method characterized in that the ratio of product orders processed for shipment within the shipment deadline among product orders for a first period set based on the aggregation date is calculated as the shipment deadline compliance rate.

3. In paragraph 1, The above arrival guarantee tag is displayed on a per-product basis for products whose delivery attribute is set to arrival guarantee. The step of controlling whether the above arrival guarantee tag is exposed is as follows: A step for changing the delivery attribute of a product whose delivery deadline compliance rate is below the preset first threshold and whose delivery attribute is guaranteed delivery from guaranteed delivery to general delivery, which is a delivery attribute in which the guaranteed delivery tag is not displayed. A logistics management method characterized by including:

4. In paragraph 3, The step of controlling whether the above arrival guarantee tag is exposed is as follows: If the above delivery deadline compliance rate is below the preset first threshold and there is a non-delivery case for a product with a delivery attribute of arrival guarantee, a step of retrieving the right to use the product unit of the arrival guarantee tag from the seller. A logistics management method characterized by further including:

5. In paragraph 4, The step of controlling whether the above arrival guarantee tag is exposed is as follows: A step of providing the seller with the right to use the product unit of the arrival guarantee tag again based on the seller processing all of the undelivered items. A logistics management method characterized by further including:

6. In paragraph 1, The above arrival guarantee tag is displayed for products in the seller's store unit, The step of controlling whether the above arrival guarantee tag is exposed is as follows: A step of accumulating and issuing one warning to a store whose compliance rate for the delivery deadline of product orders per store is below the second threshold; and If the number of warnings accumulated within the most recent preset second period becomes the first number, a step of revoking the store unit usage right of the arrival guarantee tag from the seller on the date of issuance of the first warning. A logistics management method characterized by including:

7. In paragraph 6, The step of controlling whether the above arrival guarantee tag is exposed is as follows: If the seller whose store unit usage right of the above arrival guarantee tag has been revoked satisfies both the first condition and the second condition, the step of providing the seller with the store unit usage right of the above arrival guarantee tag again Including more, The above first condition includes a condition in which the compliance rate of the delivery deadline of product orders for a preset third period based on the date of application for the store unit usage right of the arrival guarantee tag is greater than or equal to the third threshold. The above second condition includes a condition that the number of product orders during the preset fourth period is greater than or equal to the preset number based on the date of application for store unit usage rights of the arrival guarantee tag. A logistics management method characterized by .

8. In paragraph 1, A step of providing a user interface that can search at least one of information about product orders that have not met the delivery deadline for the product and information about products for which the right to use the arrival guarantee tag has been revoked for each product, by at least one processor. A logistics management method that further includes:

9. A computer program stored on a computer-readable recording medium for executing the method of any one of claims 1 to 8 on a computer device in combination with a computer device.

10. At least one processor implemented to execute instructions readable by a computer device. Including, By at least one processor, For products from sellers that display the arrival guarantee tag at the product level or store level, calculate the compliance rate of product order shipment deadlines. Controlling whether to display the arrival guarantee tag for each product or store based on the compliance rate of the above delivery deadline. A computer device characterized by:

11. In paragraph 10, To calculate the above-mentioned deadline compliance rate, by the at least one processor, Calculate the rate of product orders that were processed for shipment within the delivery deadline among product orders made during the first period based on the aggregation date as the delivery deadline compliance rate. A computer device characterized by:

12. In paragraph 10, The above arrival guarantee tag is displayed on a per-product basis for products whose delivery attribute is set to arrival guarantee. In order to control whether the above arrival guarantee tag is exposed, by the at least one processor, The above delivery deadline compliance rate is below the preset first threshold, and the delivery attribute of a product with the delivery attribute of guaranteed arrival is changed from guaranteed arrival to general delivery, which is a delivery attribute where the guaranteed arrival tag is not displayed. A computer device characterized by:

13. In paragraph 10, The above arrival guarantee tag is displayed for products in the seller's store unit, In order to control whether the above arrival guarantee tag is exposed, by the at least one processor, A warning is issued once to a store whose compliance rate for the delivery deadline for product orders at the store level is below the second threshold, and the warning is accumulated. If the number of warnings accumulated within the last preset second period reaches the first number, the right to use the store unit of the arrival guarantee tag is revoked from the seller on the date of issuance of the first warning. A computer device characterized by:

14. In paragraph 10, By at least one processor, Providing a user interface that can search for at least one of the following: information on product orders that have not met the delivery deadline for the product, and information on products for which the right to use the above arrival guarantee tag has been revoked for each product. A computer device characterized by:

Images