Method and apparatus for processing orders

Abstract

A technology is provided that visualizes to a user that attempts are continuing to assign a delivery performer to a corresponding order. A method according to an embodiment of the present disclosure may be performed by an electronic device and may include the steps of: displaying a message box including a first message indicating a search status of searching for the delivery performer in response to a user request to search for the delivery performer; determining whether a defined event has occurred based on the search status; and, based on the occurrence of the event, changing the first message included in the message box to a second message distinct from the first message and dynamically updating the message box.

Description

[Technical Field]

[0001] TECHNICAL FIELD The present disclosure relates to techniques for fulfilling orders, and more particularly to techniques for providing a user with visibility into ongoing attempts to assign a delivery fulfiller to an order. [Background technology]

[0002] Due to various environmental factors, the market size for delivery services is growing rapidly due to the expansion of non-face-to-face services.To ensure the continued growth of the market for delivery services, operators of delivery service platforms need to build platforms that satisfy all parties participating in the delivery service.For example, there is a demand for technology that efficiently handles the allocation of delivery executors to fulfill orders so that all parties participating in the delivery service are satisfied.

[0003] However, in the past, when assigning a delivery person to handle an order, the assignment of a delivery person could be delayed due to reasons such as bad weather, an overload of orders, etc. Such delays could lead to a negative experience for the supplier (user) of the order. Summary of the Invention [Problem to be solved by the invention]

[0004] The technical problem to be solved by the present disclosure is to provide a technology that can prevent a negative experience for a user due to a delay in the allocation of a delivery executor.

[0005] Another technical problem to be solved by the present disclosure is to provide a technology that can effectively reduce the cost of customer service resulting from negative user experiences.

[0006] Yet another technical problem to be solved by the present disclosure is to provide a technology that allows a user to visualize that a delivery executor is continuing to attempt allocation even when the delivery executor is late in making the allocation.

[0007] Yet another technical problem to be solved by the present disclosure is to provide a technology that can dynamically update messages exposed to users when delivery executors' allocations are delayed.

[0008] Yet another technical problem to be solved by the present disclosure is to provide a technology that can dynamically update a map exposed to a user when a delivery executor's allocation is delayed.

[0009] Yet another technical problem to be solved by the present disclosure is to provide a technology that can dynamically update the logic of a delivery executor's allocation when the delivery executor's allocation is delayed.

[0010] Yet another technical problem to be solved by the present disclosure is to provide a technology that can prevent unnecessary additional user actions (e.g., canceling an allocation and then re-requesting an allocation) that may occur when a delivery executor's allocation is delayed.

[0011] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person of ordinary skill in the technical field of the present disclosure from the description of the specification. [Means for solving the problem]

[0012] A method according to an embodiment of the present disclosure may be performed by an electronic device, and may include the steps of: displaying a message box including a first message indicating a search status of searching for a delivery performer in response to a user request to search for the delivery performer; determining whether a defined event has occurred based on the search status; and, based on the occurrence of the event, changing the first message included in the message box to a second message distinct from the first message and dynamically updating the message box.

[0013] In one embodiment, the method may further include initiating search logic for searching for the delivery executor in response to the user request.

[0014] In one embodiment, the method may further include updating the search logic based on the occurrence of the event.

[0015] In one embodiment, updating the search logic may include updating the search logic to upgrade benefits that are awarded to a candidate delivery performer when the candidate delivery performer is assigned as the delivery performer.

[0016] In one embodiment, determining whether the event has occurred may include determining whether the event has occurred based on the number of times the user request has been rejected by the candidate delivery executor.

[0017] In one embodiment, determining whether the event has occurred may include determining whether the event has occurred based on the lapse of time since the user request was sent to the candidate delivery performer.

[0018] In one embodiment, determining whether the event has occurred may include determining whether the event has occurred based on a time point at which an order corresponding to the user request is generated.

[0019] In one embodiment, determining whether the event has occurred may include determining whether the event has occurred based on an expected completion time of an order corresponding to the user request.

[0020] In one embodiment, the step of determining whether the event has occurred may include a step of determining whether the event has occurred based on whether the allocation corresponding to the user request has been completed, and may further include a step of sending an alarm to an external device if the allocation has not been completed.

[0021] In one embodiment, the method may further include displaying a map showing the search status.

[0022] In one embodiment, the method may further include updating the map based on the occurrence of the event.

[0023] A recording medium according to another embodiment of the present disclosure is a non-transitory computer-readable recording medium having a computer program recorded thereon for execution by a processor, the computer program being configured to cause the processor to perform any one of the methods described above when executed by the processor.

[0024] An electronic device according to yet another embodiment of the present disclosure may include a communication interface configured to communicate with a network, a processor configured to execute a computer program including one or more instructions, and a memory on which the computer program is stored, wherein when the computer program is executed by the processor, the processor may be configured to perform any one of the methods described above. [Effects of the Invention]

[0025] According to the present disclosure, it is possible to prevent negative user experiences due to delays in the allocation of delivery executors.

[0026] According to the present disclosure, it is possible to effectively reduce the customer service costs resulting from negative user experiences.

[0027] According to the present disclosure, it is possible to visualize to the user that the delivery executor is continuing to attempt allocation even when the allocation is delayed.

[0028] According to the present disclosure, messages exposed to users when delivery executor allocation is delayed can be dynamically updated.

[0029] According to the present disclosure, the map exposed to the user can be dynamically updated when delivery executor assignments are delayed.

[0030] The present disclosure allows for the allocation logic to be dynamically updated when delivery executors are delayed in their allocation.

[0031] According to the present disclosure, it is possible to prevent unnecessary additional actions by the user (for example, canceling an allocation and then requesting another allocation) that may occur when the allocation of a delivery executor is delayed.

[0032] The effects of the technical ideas of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those of ordinary skill in the art of the present disclosure from the description of the specification. [Brief explanation of the drawings]

[0033] [Figure 1] FIG. 1 is a diagram illustrating an environment in which an apparatus according to an embodiment of the present disclosure can be applied. [Figure 2] FIG. 1 illustrates a computing device capable of implementing an apparatus according to an embodiment of the present disclosure. [Figure 3] 1 is a flowchart illustrating a method according to an embodiment of the present disclosure. [Figure 4] FIG. 10 illustrates an order acceptance screen for an order in progress that may be referenced in various embodiments of the present disclosure. [Figure 5] FIG. 5 is a diagram showing a message box that can be included in the order reception screen shown in FIG. 4. [Figure 6] FIG. 10 illustrates a message transformation process that can be referenced in various embodiments of the present disclosure. [Figure 7] FIG. 10 illustrates a message transformation process that can be referenced in various embodiments of the present disclosure. [Figure 8] 10 is a flowchart illustrating a method according to another embodiment of the present disclosure. [Figure 9]10 is a flowchart illustrating a method according to yet another embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0034] The various embodiments described in this disclosure are presented for the purpose of clearly explaining the technical idea of ​​the present disclosure and are not intended to limit the present disclosure to specific embodiments. The technical idea of ​​the present disclosure includes various modifications, equivalents, alternatives, and embodiments selectively combining all or part of the embodiments described in this disclosure. Furthermore, the scope of the technical idea of ​​the present disclosure is not limited to the various embodiments presented below or the specific descriptions thereof.

[0035] Terms used in this disclosure, including technical or scientific terms, may have the meaning commonly understood by one of ordinary skill in the art to which this disclosure belongs, unless otherwise defined.

[0036] As used in this disclosure, terms such as "comprise," "may include," "include," "can comprise," "have," "may have," and the like, imply the presence of a subject feature (e.g., a function, operation, or component) but do not exclude the presence of additional features. That is, such terms should be understood as open-ended terms that include the possibility of including other embodiments.

[0037] As used in this disclosure, singular terms may also include plural meanings unless the context clearly dictates otherwise, and this also applies to singular terms recited in the claims.

[0038] As used in this disclosure, unless otherwise indicated in the context, the terms "first," "second," "first," "second," and the like, when referring to multiple similar objects, are used to distinguish one object from another and do not limit the order or importance of those objects.

[0039] As used in this disclosure, phrases such as "A, B, and C," "A, B, or C," "at least one of A, B, and C," or "at least one of A, B, or C" can refer to each listed item or any possible combination of the listed items. For example, "at least one of A or B" can refer to (1) at least one A, (2) at least one B, or (3) all of at least one A and at least one B.

[0040] As used in this disclosure, the phrase "based on" is used to describe one or more factors that influence the decision, act of judgment, or behavior described in the phrase or sentence in which it appears, and does not exclude additional factors that influence that decision, act of judgment, or behavior.

[0041] As used in this disclosure, the expression "coupled" or "connected" to one component (e.g., a first component) to another component (e.g., a second component) can mean that the one component is directly coupled or connected to the other component, or that the one component is further coupled or connected via another component (e.g., a third component).

[0042] The expression "configured to" used in this disclosure may have the meanings of "set to," "capable of," "modified to," "made to," "capable of," etc., depending on the context. This expression is not limited to the meaning of "specially designed in terms of hardware." For example, a processor configured to perform a specific operation can mean a general-purpose processor that can perform the specific operation by executing software, or a special-purpose computer that is structured by programming to perform the specific operation.

[0043] The term "user" as used in this disclosure may refer to an entity that uses a platform related to delivery services. For example, a user may refer to any one of an order consumer, an order supplier, and a delivery executor. However, since this disclosure focuses on techniques for inducing a positive experience for order suppliers, unless otherwise specified, hereinafter, a user may be understood to refer to an order supplier.

[0044] The term "user interface" as used in this disclosure may refer to a physical or virtual medium that allows a user to communicate with an item, a system, a machine, a computer program, etc. According to this disclosure, a user can use a platform related to delivery services through the user interface.

[0045] Hereinafter, various embodiments described in the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings and descriptions relating to the drawings, identical or substantially equivalent components may be designated by the same reference numerals. In addition, in the following descriptions of various embodiments, repeated descriptions of identical or corresponding components may be omitted, but this does not mean that the components are not included in the embodiments.

[0046] 1 illustrates an environment 100 to which devices 110, 120, 130, 141, and 142 according to an embodiment of the present disclosure can be applied. The environment 100 illustrated in FIG. 1 relates to an exemplary environment in which a consumer generates an order via a consumer terminal 130, a supplier receives the consumer's order via a supplier terminal 120 and prepares goods corresponding to the order, and a candidate delivery executor is assigned a delivery process corresponding to the order and delivers the prepared goods via a candidate delivery executor terminal 141 and 142. In this environment 100, a platform operating server 110 can manage a platform related to delivery services provided to each entity's terminal 120, 130, 141, and 142.

[0047] As shown in Fig. 1, each entity participating in the delivery service can exchange various information related to the delivery service through their terminals 120, 130, 141, and 142, and the platform operating server 110 can process and handle this various information. The operations performed by the platform operating server 110 and each entity's terminals 120, 130, 141, and 142 will be described in more detail in the following specification.

[0048] 1 shows an example in which one supplier terminal 120, one consumer terminal 130, and two potential delivery executor terminals 141 and 142 are each connected to the platform operating server 110, but the number of terminals representing the number of entities participating in the delivery service is not limited. Also, FIG. 1 merely shows a preferred embodiment for achieving the object of the present disclosure, and some components may be added or deleted as necessary.

[0049] Each component shown in FIG. 1 will be described in more detail below.

[0050] The platform operating server 110 may generate an order based on information obtained from the consumer terminal 130. For example, information available for generating an order may include product details, the supplier of the product, the location where the product is to be picked up (e.g., the supplier's address), and the destination where the product is to be delivered (e.g., the consumer's address).

[0051] Furthermore, the platform operating server 110 may transmit the order to the supplier terminal 120. When the order is transmitted to the supplier terminal 120 in this manner, the supplier may identify the new order through the supplier terminal 120 and prepare the product corresponding to the order. Here, the supplier may transmit a user request to search for a delivery executor to the platform operating server 110 through the supplier terminal 120. However, instead of this, the user request may be dynamically acquired by the platform operating server 110 based on, for example, the generation of the order or the transmission of the order to the supplier terminal 120.

[0052] In addition, the platform operating server 110 may transmit a delivery processing request for an order to at least one of one or more candidate delivery executor terminals 141, 142 in response to a user request from the supplier terminal 120. Here, the process of transmitting the delivery processing request may be referred to as search logic for searching for a delivery executor corresponding to the order, and such search logic may be implemented with reference to various known matching technologies.

[0053] For example, one delivery processing request corresponding to one order may be sent to one candidate delivery executor terminal. If the candidate delivery executor terminal to which the delivery processing request was sent accepts the delivery processing request, the platform operating server 110 may complete the allocation of delivery processing corresponding to the order. In this case, the platform operating server 110 may send information about the order to the candidate delivery executor terminal that accepted the delivery processing request, and may send information about the completion of the delivery processing allocation and / or the candidate delivery executor (i.e., the delivery executor) who accepted the delivery processing request to the supplier terminal 120. Furthermore, if the candidate delivery executor terminal to which the delivery processing request was sent rejects the delivery processing request or does not respond to the delivery processing request for a reference period of time or more, the platform operating server 110 may send a delivery processing request to another candidate delivery executor terminal. Such delivery processing requests may be sent to multiple candidate delivery executor terminals without overlapping and may be continued until acceptance occurs.

[0054] As another example, multiple delivery processing requests corresponding to one order may be sent to multiple candidate delivery executor terminals. If the delivery processing request is accepted first, the platform operating server 110 may complete the allocation of delivery processing to the candidate delivery executor terminal that accepted first. In this case, the platform operating server 110 may send information about the order to the candidate delivery executor terminal that accepted the delivery processing request first, and may send information about the completion of the delivery processing allocation and / or the candidate delivery executor (i.e., delivery executor) that accepted the delivery processing request first to the supplier terminal 120.

[0055] When the delivery process for an order is assigned to one of the multiple candidate delivery executor terminals 141, 142 according to the search logic described above, the delivery executor can pick up the product corresponding to the order at the pickup location and deliver the product to the delivery destination.

[0056] In addition to the operations of the platform operating server 110 described above, the platform operating server 110 may perform various operations for processing orders by interoperating with at least some of the supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141 and 142, and may perform all additional or modifiable operations from order acceptance to completion. In particular, the following description of the specification will focus on the platform provided to the supplier terminal 120 as a user interface in the process in which the platform operating server 110 performs search logic, but it should be noted that this does not exclude other operations performed by the platform operating server 110 from the scope of the present disclosure, but is intended to avoid obscuring the gist of the present disclosure.

[0057] The platform operation server 110 may be implemented by one or more computing devices. For example, all functions of the platform operation server 110 may be implemented by a single computing device. As another example, a first function of the platform operation server 110 may be implemented by a first computing device, and a second function of the platform operation server 110 may be implemented by a second computing device. For example, the computing device may be, but is not limited to, a desktop computer, a laptop computer, an application server, a proxy server, or a cloud server, and any type of device having a computing function may be a computing device.

[0058] The supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141, 142 are terminals of the respective entities participating in the delivery service, and can display various pages of the delivery service provided by the platform operating server 110 described above. These various pages of the delivery service may have user interfaces defined as functions related to the delivery service applied to them. The application of these user interfaces may be managed by the platform operating server 110 described above. Furthermore, each of the supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141, 142 can obtain inputs or requests for the various pages of the delivery service, process the inputs or requests, or send them to the platform operating server 110. Here, each of the supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141, 142 can perform operations defined in response to the inputs or requests from the platform operating server 110. As described above, in order to use delivery services through each of the supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141, 142, a web browser or application may be installed on each of the supplier terminal 120, the consumer terminal 130, and the candidate delivery executor terminals 141, 142.

[0059] In one embodiment, the user interfaces provided to the terminals 120, 130, 141, and 142 of the respective subjects may be implemented so that at least some of the components (user interface elements) differ from each other depending on the attributes of each subject. Specifically, the first user interface provided to the supplier terminal 120 and the second user interface provided to the consumer terminal 130 may be implemented so that at least some of the components differ from each other depending on the attributes of each subject.

[0060] 1 can communicate through a network, which may be embodied by any type of wired or wireless network, such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network (MRCN), or wireless broadband (WiBro).

[0061] Fig. 2 illustrates a computing device 200 that can embody the devices 110, 120, 130, 141, and 142 according to an embodiment of the present disclosure. That is, the platform operating server 110, the supplier terminal 120, the consumer terminal 130, or the candidate delivery executor terminals 141 and 142 illustrated in Fig. 1 may be embodied by the computing device 200 illustrated in Fig. 2. For reference, in this disclosure, the computing device 200 may be interchangeably referred to as an electronic device.

[0062] Computing device 200 may include one or more processors 210, one or more memories 220, or a communication interface 230. In one embodiment, some components of computing device 200 may be omitted, and other components (e.g., a display or an input device) may be added to computing device 200. Additionally, or alternatively, some components may be integrated or embodied as one or more individual components. In this disclosure, one or more processors 210 may be referred to as processor 210. The term processor 210 may refer to a collection of one or more processors, unless otherwise specified in the context. In this disclosure, one or more memories 220 may be referred to as memory 220. The term memory 220 may refer to a collection of one or more memories, unless otherwise specified in the context.

[0063] Each component shown in FIG. 2 will now be described in more detail.

[0064] The processor 210 can perform calculations and information processing related to control or communication with each component of the computing device 200. Specifically, the processor 210 can run software (or computer programs) received from other components and control at least one component of the computing device 200 connected to the processor 210. As an example, the processor 210 can load instructions (e.g., instructions, code, or code segments) or information into the memory 220, process the instructions or information stored in the memory 220, and store the resulting information from the processing in the memory 220. The processor 210 is also operatively connected to the components of the computing device 200 and can perform various calculations, processing, generation, processing, and other operations related to the present disclosure.

[0065] The memory 220 may store various information. The information stored in the memory 220 is information that is acquired, processed, or used by at least one component of the computing device 200 and may include software. The software may include one or more instructions that, when loaded into the memory 220, cause the processor 210 to perform operations according to various embodiments of the present disclosure. That is, the processor 210 can perform operations according to various embodiments of the present disclosure by executing one or more of the instructions described above. The memory 220 may include, for example, volatile or non-volatile memory. In one embodiment, the program stored in the memory 220 may include an operating system for controlling the resources of the computing device 200, an application, or middleware that provides various functions to applications so that the applications can utilize the resources of the computing device 200.

[0066] The communication interface 230 can establish a wired or wireless communication channel with other devices and transmit and receive various information to and from other devices. In one embodiment, the communication interface 230 may include at least one port for connecting to another device via a wired cable to communicate with the other device. In this case, the communication interface 230 can communicate with the other device through the at least one port. In one embodiment, the communication interface 230 includes a cellular communication module and may be configured to connect to a cellular network (e.g., 3G, LTE, 5G, Wibro, or Wimax). In one embodiment, the communication interface 230 includes a short-range communication module and can transmit and receive information to and from other devices using short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), or UWB). In one embodiment, the communication interface 230 may include a contactless communication module for contactless communication. The contactless communication may include at least one contactless proximity communication technology, such as near field communication (NFC), radio frequency identification (RFID), or magnetic secure transmission (MST). In addition to the various examples described above, the computing device 200 may be embodied in various known ways for communicating with other devices, and the scope of the present disclosure is not limited by the examples described above.

[0067] In one embodiment, the computing device 200 may include a display. The display may display various screens (e.g., one or more pages) under the control of the processor 210. For example, a web browser or a dedicated application may be installed on the computing device 200 to display screens to which various interfaces are applied on the display. The display may also be configured to be capable of interacting with a user and receiving user input from the user. Such a display may be implemented in the form of a touch sensor panel (TSP) that can recognize contact or proximity of various external objects (e.g., a user's finger or stylus).

[0068] In one embodiment, computing device 200 may include an input device (e.g., a mouse or keyboard) that can receive information from outside computing device 200 (e.g., a user) for use by components of computing device 200.

[0069] The processor 210, memory 220, and communication interface 230 shown in FIG. 2 are connected to each other via a bus, a GPIO (General Purpose Input / Output), an SPI (Serial Peripheral Interface), or an MIPI (Mobile Industry Processor Interface), and can transmit and receive information or signals.

[0070] The following provides a detailed description of methods according to various embodiments of the present disclosure. Although the following figures illustrate operations in a particular order, it should be noted that the operations do not necessarily have to be performed in the particular order or sequential order shown, or that all of the illustrated operations must be performed to achieve desired results.

[0071] Furthermore, the operations of the methods described with reference to the following drawings may be performed by a computing device. In other words, the operations of the methods may be embodied as one or more instructions executed by a processor of a computing device. All operations included in such a method may be performed by one physical computing device, but, for example, a first operation of the method may be performed by a first computing device and a second operation of the method may be performed by a second computing device. That is, the operations included in the method may be distributed across multiple computing devices.

[0072] In the following description, the operations of the above-described method will be assumed to be performed by the supplier terminal 120 shown in Fig. 1. For the sake of convenience, the subject of the operations included in the method may be omitted, but unless otherwise specified in the context, the operations may be interpreted as being performed by the supplier terminal 120.

[0073] 3 is a flowchart showing a method according to an embodiment of the present disclosure. The operations shown in FIG. 3 will be described in detail below.

[0074] In response to the user request, a message box may be displayed (S310). Although this operation is described as being performed by the provider terminal 120, this operation may also be understood as an operation in which the platform operating server 110 transmits information corresponding to the message box to the provider terminal 120 in order to display the message box.

[0075] A user request may be a request from a supplier (i.e., a user) to locate a delivery fulfilment agent. As described with reference to Figure 1, a user request may be generated by the supplier's intention or may be generated dynamically depending on the creation or submission of an order.

[0076] The message box may be a component of the user interface provided on the supplier terminal 120, which may contain a message that the user can recognize as text. Such a message box may contain a message (e.g., a first message, a second message) indicating the search status of the delivery executor search.

[0077] Here, the search status may represent the progress of the search logic for searching for a delivery performer. Such search status may include, for example, the number of times the user request (or a delivery processing request processed from the user request) has been rejected by a candidate delivery performer, the elapsed time since the user request (or a delivery processing request processed from the user request) was sent to a candidate delivery performer, the elapsed time since the order was generated, the remaining time until the expected completion of the order, and whether the delivery processing assignment has been completed.

[0078] In order to display the search status as a message, consecutive values ​​can be classified into multiple classes, and representative messages for each of the multiple classes can be determined in advance. As a specific example, the number of rejections can be 0 to 3 can be classified into the first class, the number of rejections can be 4 to 6 can be classified into the second class, and the number of rejections can be 7 or more can be classified into the third class. Also, for example, "A" can be determined as the representative message corresponding to the first class, "B" can be determined as the representative message corresponding to the second class, and "C" can be determined as the representative message corresponding to the third class. In this example, the provider terminal 120 can display "A" on the display in a search status where the number of rejections is 0, "B" can be displayed in a search status where the number of rejections is 5, and "C" can be displayed in a search status where the number of rejections is 9.

[0079] That is, by performing the operations (S320, S330) described below, the class transition (e.g., change from the first class to the second class) can be determined based on whether or not an event has occurred, and the message contained in the message box can be dynamically updated.

[0080] Based on the search state, it may be determined whether or not a defined event has occurred (S320). Although this operation is described as being performed by the provider terminal 120, the determination of whether or not an event has occurred may be understood as an operation performed by the platform operating server 110.

[0081] The events are defined based on the search state and may be rules pre-created by the operator of the platform involved in the delivery service to cause a result (e.g., a dynamic update of a message). Such events may be rules created to determine the transition of classes defined by the search state, i.e., the progress state of the search logic.

[0082] In one embodiment, the operation of determining whether an event has occurred (S320) may include an operation of determining whether an event has occurred based on the number of times a user request (or a delivery processing request) has been rejected by a candidate delivery agent.

[0083] For specific examples related to this embodiment, please refer to the description of operation S310.

[0084] According to this embodiment, an event is generated in advance so that it depends on the number of times a user request (or delivery processing request) is rejected by a candidate delivery agent, and by determining whether or not the event has occurred, a result defined to correspond to the event can be generated depending on the number of rejections.

[0085] In another embodiment, the operation of determining whether an event has occurred (S320) may include an operation of determining whether an event has occurred based on the elapsed time since the user request (or delivery processing request) was sent to the candidate delivery performer.

[0086] As a specific example, if the elapsed time since the request was sent to multiple candidate delivery persons is within one minute, the request may be classified as Class 1, and if the elapsed time exceeds one minute, the request may be classified as Class 2. Furthermore, for example, "A" may be determined as the representative message corresponding to Class 1, and "B" may be determined as the representative message corresponding to Class 2. In this example, the supplier terminal 120 may display "A" on the display in a search state in which 30 seconds have elapsed since the request was sent to multiple candidate delivery persons, and "B" on the display in a search state in which 5 minutes have elapsed. This example may be based on search logic that sends a user request (or delivery processing request) corresponding to one order to multiple candidate delivery persons terminals 141, 142. However, if search logic that sequentially sends a user request (or delivery processing request) corresponding to one order to multiple candidate delivery persons terminals 141, 142 is applied, the occurrence of an event may be determined based on the total elapsed time since the request was sent to the multiple candidate delivery persons.

[0087] According to this embodiment, an event is generated in advance so that it depends on the time that has passed since the user request (or delivery processing request) was sent to the candidate delivery executor, and by determining whether or not the event has occurred, a result defined to correspond to the event can be generated depending on the time that has passed since the request was sent to the candidate delivery executor.

[0088] In yet another embodiment, the operation of determining whether an event has occurred (S320) may include an operation of determining whether an event has occurred based on the time of generation of an order corresponding to a user request.

[0089] As a specific example, when an order is generated in response to a user request, if the event occurs within one minute, it can be classified as Class 1, and if the elapsed time exceeds one minute, it can be classified as Class 2. For example, a representative message corresponding to Class 1 can be determined as "A," and a representative message corresponding to Class 2 can be determined as "B." In this example, the supplier terminal 120 can display "A" on the display in a search state where 30 seconds have elapsed since the order was generated, and can display "B" on the display in a search state where 5 minutes have elapsed.

[0090] According to this embodiment, an event is generated in advance so as to depend on the time at which an order corresponding to a user request is generated, and by determining whether or not the event has occurred, a result defined to correspond to the event can be generated depending on the elapsed time from the time at which the order was generated.

[0091] In yet another embodiment, the operation of determining whether an event has occurred (S320) may include an operation of determining whether an event has occurred based on an expected completion time of an order corresponding to the user request.

[0092] The expected completion time of an order may be the time when the products corresponding to the order are expected to be delivered to the consumer's delivery destination. The expected completion time of such an order may be predicted based on factors such as the breakdown of products included in the order, the cooking time of the products, weather, the status of the pool of candidate delivery fulfillers, the distance between the pickup location and the delivery destination, and the distance between the location of the delivery fulfiller and the pickup location.

[0093] As a specific example, if the remaining time until the expected completion of an order corresponding to a user request exceeds 30 minutes, it may be classified as Class 1; if the remaining time is more than 10 minutes but less than 30 minutes, it may be classified as Class 2; if the remaining time is more than 5 minutes but less than 10 minutes, it may be classified as Class 3; and if the remaining time is 5 minutes or less, it may be classified as Class 4. Furthermore, for example, "A" may be determined as the representative message corresponding to Class 1, "B" may be determined as the representative message corresponding to Class 2, "C" may be determined as the representative message corresponding to Class 3, and "D" may be determined as the representative message corresponding to Class 4. In this example, the supplier terminal 120 may display "A" on the display in a search state where the remaining time until the expected completion of the order is 35 minutes, "B" may be displayed on the display in a search state where the remaining time is 15 minutes, "C" may be displayed on the display in a search state where the remaining time is 6 minutes, and "D" may be displayed on the display in a search state where the remaining time is 1 minute.

[0094] According to this embodiment, an event is generated in advance so as to depend on the remaining time until the expected completion of an order corresponding to a user request, and by determining whether or not the event has occurred, a result defined to correspond to the event can be generated depending on the remaining time.

[0095] In yet another embodiment, the operation of determining whether an event has occurred (S320) may include an operation of determining whether an event has occurred based on whether allocation corresponding to a user request has been completed.

[0096] As a specific example, if allocation corresponding to a user request has not been completed, the message may be classified into a first class, and if allocation has been completed, the message may be classified into a second class. Also, for example, "A" may be determined as a representative message corresponding to the first class, and "B" may be determined as a representative message corresponding to the second class. In this example, the provider terminal 120 may display "A" on the display in a search state in which allocation corresponding to a user request has not been completed, and may display "B" on the display in a search state in which allocation has been completed.

[0097] According to this embodiment, an event is generated in advance so as to depend on whether or not an allocation corresponding to a user request has been completed, and by determining whether or not the event has occurred, a result defined to correspond to the event can be generated upon completion of the allocation.

[0098] Based on the occurrence of an event, the message box may be dynamically updated (S330). Although this operation is described as being performed by the provider terminal 120, this operation may also be understood as an operation in which the platform operating server 110 transmits information corresponding to the message box to the provider terminal 120 to update the message box.

[0099] Dynamic update of a message box refers to a phenomenon in which a message box is automatically updated without user input. Here, message box update refers to various changes to a message, such as changes to the message content, message color, message size, message layout, etc. In other words, any change that can be visually recognized by the user may be included in a message box update.

[0100] This action may cause a message box to be updated with a message corresponding to the search state at the time the event occurred.

[0101] An alarm may be sent to an external device (e.g., the platform operating server 110) (S340). Although this operation is described as being performed by the provider terminal 120, this operation may also be understood as the platform operating server 110 receiving the alarm.

[0102] The alarm may be information that notifies the platform operator of the need to allocate a delivery process to correspond to the order. Such an alarm may be, for example, an alarm sound generated from a speaker of the platform operating server 110 (or a device related thereto), or a pop-up alarm or a specific message displayed on the display of the platform operating server 110 (or a device related thereto). However, in addition to the above examples, various known methods for notifying the platform operator of the need to allocate a delivery process may be applied within the scope of the present disclosure.

[0103] Such an alarm may be sent from the supplier terminal 120 to the platform operating server 110 based on, for example, a comparison of the elapsed time since the user request (or delivery processing request) was sent to the candidate delivery performer, the elapsed time since the order was generated, or the remaining time until the expected completion of the order, with a critical time. For example, the alarm may be sent from the supplier terminal 120 to the platform operating server 110 when the elapsed time exceeds the critical time or when the remaining time is less than the critical time. According to this example, the platform operator can be notified of an order that particularly requires allocation of delivery processing.

[0104] In one embodiment, the sending of an alarm (S340) may be the event described in the determining whether an event has occurred (S320). That is, the sending of an alarm may be determined as the occurrence of an event, and the message box may be dynamically updated.

[0105] In other embodiments, the order may be processed by increasing the allocation priority of the alarmed order, for example, by sending a delivery processing request for the alarmed order to the terminal of a candidate delivery person with a high allocation acceptance rate, or by sending a bonus that may be provided upon acceptance to the terminal of the candidate delivery person together with the delivery processing request for the alarmed order. Processing of such orders may be performed by the platform operating server 110 shown in FIG. 1.

[0106] As described above with reference to FIG. 3, a message box included in a screen exposed to a user via the provider terminal 120 can be dynamically updated. This update is performed in a manner that allows the user to recognize visual changes, allowing the user to visually confirm that delivery executor allocation is being continuously attempted. This prevents the user from performing unnecessary additional actions that may occur when delivery executor allocation is delayed, such as canceling the allocation and then re-requesting allocation. Furthermore, by significantly reducing negative user experiences caused by allocation delays, the customer response costs resulting from such negative experiences can also be effectively reduced.

[0107] Hereinafter, drawings that can be referred to in various embodiments of the present disclosure will be described with reference to FIGS.

[0108] FIG. 4 illustrates an order intake screen 400 for an order in progress that may be referenced in various embodiments of the present disclosure.

[0109] The order acceptance screen 400 may be an example of a page that is displayed on the display of the supplier terminal 120. Referring to FIG.

[0110] The navigation tabs 410 may include a component that exposes a default page (e.g., Home) of the order taking screen 400 and a component that exposes orders categorized by order status (e.g., Awaiting Acceptance, In Progress, Completed). When a particular component is selected by the user, a page corresponding to that particular component may be displayed to the user as the order taking screen 400.

[0111] If the "In Progress" component in the navigation tab 410 is selected, a list of orders that the user currently needs to process may be displayed on the order receipt screen 400. In this case, the order receipt screen 400 may include one or more message boxes 420.

[0112] A detailed description of message box 420 is provided with reference to FIG.

[0113] 4 merely shows a preferred embodiment for achieving the object of the present disclosure, and as necessary, some components may be added or deleted from the order reception screen 400. Furthermore, the size or arrangement of some components may be changed.

[0114] FIG. 5 shows a message box 500 that may be included in the order reception screen shown in FIG.

[0115] The message box 500 may be a component that contains information corresponding to an order that the user is currently processing. Such a message box 500 may include an identifier 510 corresponding to the order, a time the order was created 520, a breakdown of the products included in the order 530, consumer requests associated with the order 540, an indicator 550 indicating the search status of allocations corresponding to the order, a message 560 indicating the search status, and a remaining preparation time 570 for the products corresponding to the order.

[0116] The search status message 560 may be dynamically updated in the manner described with reference to Figure 3. Details of the update are described with reference to Figures 6 and 7.

[0117] 5 merely shows a preferred embodiment for achieving the object of the present disclosure, and some components may be added or deleted from the message box 500 as needed. In addition, the size or arrangement of some components may be changed.

[0118] 6 and 7 illustrate message transformation processes that may be referenced in various embodiments of the present disclosure.

[0119] 6 and 7, the message indicating the search status may be changed. Specifically, based on the occurrence of an event, the message box may be dynamically updated, such as changing from a first message 610, 710 to a second message 620, 720, changing from the second message 620, 720 to a third message 630, 730, or changing from the third message 630, 730 to a fourth message 640, 740.

[0120] While Figures 6 and 7 show the content of the message being modified, various other modifications to the message may be within the scope of this disclosure, such as changing the color of the message, changing the size of the message, or changing the placement of the message.

[0121] Various methods of the present disclosure will now be described with reference to FIGS.

[0122] Fig. 8 is a flowchart showing a method according to another embodiment of the present disclosure. In Fig. 8, the target of update based on the occurrence of an event may be different from that in Fig. 3. Specifically, in the method shown in Fig. 3, the target of update may be a message box, while in the method shown in Fig. 8, the target of update may be search logic. The operation shown in Fig. 8 will now be described in detail.

[0123] In response to a user request, a search logic for searching for a delivery performer may be initiated (S810). According to this operation, the search logic for searching for a delivery performer may be initiated in response to a user request for searching for a delivery performer. If the user request is dynamically acquired by the platform operating server 110 upon order creation, the search logic may be initiated immediately upon order creation.

[0124] It may be determined whether or not an event defined based on the search state has occurred (S820). This operation may be understood as the same operation as the operation of determining whether or not an event has occurred (S320) described with reference to Fig. 3, and detailed description of this operation will be omitted.

[0125] Based on the occurrence of the event, the search logic may be updated (S830).

[0126] In one embodiment, this operation may include updating the search logic to upgrade the incentives (e.g., delivery fees) that are awarded to the candidate delivery performers when they are assigned as delivery performers. In this case, upgrading the incentives may increase the candidate delivery performers' delivery acceptance rate. In another embodiment, this operation may include updating the search logic to increase the distance between the pickup location and the candidate delivery performers' current location. In this case, expanding the pool of candidate delivery performers may increase the likelihood of assigning a delivery job.

[0127] An alarm may be transmitted to an external device (S840). This operation may be understood as the same operation as the alarm transmission operation (S840) described with reference to Fig. 3, and detailed description of this operation will be omitted.

[0128] As described above with reference to Figure 8, the logic for attempting to allocate a delivery process corresponding to an order, i.e., the search logic for searching for a delivery performer, can be dynamically updated. The method shown in Figure 8 can be implemented in parallel with the method shown in Figure 3, so that along with the visual change in the message box, the actual search logic can be updated to improve the possibility of allocating a delivery process corresponding to an order.

[0129] Fig. 9 is a flowchart showing a method according to yet another embodiment of the present disclosure. In Fig. 9, the target of update based on the occurrence of an event may be different from that in Fig. 3. Specifically, in the method shown in Fig. 3, the target of update may be a message box, while in the method shown in Fig. 9, the target of update may be a map. The operation shown in Fig. 9 will now be described in detail.

[0130] In response to a user request, a map may be displayed (S910).

[0131] The map may indicate a search status. Here, the search status may be displayed on the map as a radius within which to search for potential delivery performers. Such a radius may be an indicator of the limit of the distance between a pickup location and a specific point (e.g., the location of a potential delivery performer).

[0132] According to this operation, a map showing the search status may be displayed on the display of the supplier terminal 120 in response to a user request to search for a delivery performer. If the user request is dynamically acquired by the platform operating server 110 upon order creation, the map may be displayed immediately upon order creation.

[0133] It may be determined whether or not an event defined based on the search state has occurred (S920). This operation may be understood as the same operation as the operation of determining whether or not an event has occurred (S320) described with reference to Fig. 3, and detailed description of this operation will be omitted.

[0134] Based on the occurrence of the event, the map may be updated (S930).

[0135] In one embodiment, this action may include updating the map so that the search radius displayed on the map is increased, thereby providing a visual indication to the user of the expanded pool of potential delivery performers.

[0136] An alarm may be transmitted to an external device (S940). This operation may be understood as the same operation as the alarm transmission operation (S840) described with reference to Fig. 3, and detailed description of this operation will be omitted.

[0137] As described above with reference to Fig. 9, a map showing the search status for finding a delivery person can be dynamically updated. The method shown in Fig. 9 can be implemented in parallel with the method shown in Fig. 3, so that the user can more effectively recognize visual changes. This can maximize the effect of the method shown in Fig. 3.

[0138] In the flowcharts of the present disclosure, the operations of a method or algorithm are described in a sequential order, but may be performed in any combinable order, as well as sequentially. The description of the flowcharts of the present disclosure does not preclude variations or modifications to the method or algorithm, and does not imply that any operation is essential or preferred. In one embodiment, at least some operations may be performed in parallel, iteratively, or heuristically. In other embodiments, at least some operations may be omitted, and other operations may be added.

[0139] Various embodiments of the present disclosure may be embodied as software on a machine-readable storage medium (MRSM). The software may be software for implementing various embodiments of the present disclosure. The software may be inferred from various embodiments of the present disclosure by a programmer skilled in the art. For example, the software may be a computer program including instructions readable by a computing device. A computing device is a device that can operate in accordance with instructions retrieved from a storage medium, and may be interchangeably referred to as, for example, an electronic device. In one embodiment, a processor of the computing device executes the retrieved instructions and causes components of the computing device to perform functions corresponding to the instructions. A storage medium may refer to any type of machine-readable recording medium on which information is stored. The storage medium may include, for example, a read-only memory (ROM), a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, or an optical information storage device. In one embodiment, the storage medium may be embodied in a distributed form across computer systems connected via a network. In this case, the software may be stored and executed in a distributed manner across the computer systems. In another embodiment, the storage medium may be a non-transitory storage medium, which refers to a tangible medium in which information is stored semi-permanently or temporarily, and does not include transitory signals.

[0140] Although the technical idea of ​​the present disclosure has been described above using various embodiments, the technical idea of ​​the present disclosure includes various substitutions, modifications, and alterations that can be made within the scope of what can be understood by a person having ordinary skill in the art to which the present disclosure pertains. Furthermore, it should be understood that these substitutions, modifications, and alterations are included within the scope of the appended claims.

Claims

1. A method performed by an electronic device, comprising: displaying a message box including a first message indicating a search status of the delivery executor in response to a user request to search for the delivery executor; determining whether or not a defined event occurs based on the search state; and based on the occurrence of the event, changing the first message contained in the message box to a second message that is distinct from the first message, and dynamically updating the message box.

2. The method of claim 1 , further comprising initiating search logic to search for the delivery performer in response to the user request.

3. The method of claim 2 , further comprising updating the search logic based on the occurrence of the event.

4. The step of updating the search logic comprises:

4. The method of claim 3, including updating the search logic to upgrade incentives awarded to candidate delivery performers when they are assigned as the delivery performer.

5. The step of determining whether or not an event has occurred includes: The method of claim 1 , further comprising determining whether the event has occurred based on the number of times the user request is rejected by a candidate delivery performer.

6. The step of determining whether or not an event has occurred includes: The method of claim 1 , further comprising determining whether the event has occurred based on the lapse of time since the user request was sent to the candidate delivery performer.

7. The step of determining whether or not an event has occurred includes: The method of claim 1 , further comprising determining whether the event has occurred based on a time point at which an order corresponding to the user request is generated.

8. The step of determining whether or not an event has occurred includes: The method of claim 1 , further comprising determining whether the event has occurred based on an expected completion time of an order corresponding to the user request.

9. The step of determining whether or not an event has occurred includes: determining whether the event has occurred based on whether the allocation corresponding to the user request has been completed; The method of claim 1 , further comprising sending an alarm to an external device if the allocation is not complete.

10. The method of claim 1 further comprising displaying a map showing the search status.

11. The method of claim 10 further comprising updating the map based on the occurrence of the event.

12. A non-transitory computer-readable recording medium having a computer program to be executed by a processor recorded thereon, A non-transitory computer-readable storage medium, the computer program being configured, when executed by the processor, to cause the processor to perform the method of any one of claims 1 to 11.

13. a communication interface configured to be able to communicate with a network; a processor configured to execute a computer program including one or more instructions; a memory in which the computer program is stored; An electronic device, wherein when the computer program is executed by the processor, the processor is configured to perform the method of any one of claims 1 to 11.

Images