Delivery plan management method, system and apparatus, electronic device, and storage medium

Abstract

Disclosed in the present application are a delivery plan management method, system and apparatus, an electronic device, and a computer storage medium. The method comprises: receiving first delivery plan information of a merchant, wherein the first delivery plan information comprises a first delivery list and a first delivery schedule that correspond to a first delivery plan; verifying the first delivery plan information; when the verification of the first delivery plan information is successful, determining, on the basis of the first delivery list and the first delivery schedule, a first target virtual resource required to complete the first delivery plan; verifying an available virtual resource of the merchant on the basis of the first target virtual resource; when the verification of the available virtual resource of the merchant is successful, generating, in response to an execution request from the merchant for the first delivery plan, a plurality of first pre-orders on the basis of the first delivery plan information; and on the basis of the first pre-orders, generating first instant orders to execute order dispatching processing. The overall delivery plan management can effectively improve the quality of a group meal delivery service.

Description

Distribution planning management methods, systems, devices, electronic equipment and storage media

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 202411943034.4, filed on December 27, 2024, entitled "Method, System, Apparatus, Electronic Device and Storage Medium for Delivery Planning Management", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of mobile communication technology, and in particular to a delivery planning management method, system, device, electronic device, and storage medium. Background Technology

[0004] To meet the needs of modern people dining at home, digital food delivery services have emerged. Through digital platforms, the service area of ​​community canteens and other businesses can be expanded from a few hundred meters to tens of square kilometers. More businesses can also participate in group food delivery services, such as those for the elderly, thus providing a more convenient dining experience for more people.

[0005] Currently, digital platforms primarily target individual food delivery services. There is a need to provide a delivery plan management solution for group food delivery services in order to improve the quality of group food delivery services. Summary of the Invention

[0006] This application provides a delivery planning management method, system, device, electronic device, and storage medium, which can improve the quality of group meal delivery services. The above technical solution is as follows:

[0007] In a first aspect, embodiments of this application provide a delivery planning management method, including:

[0008] Receive the merchant’s first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time schedule; the first delivery list includes multiple first list entries, each first list entry includes the merchant’s first store identifier and the first delivery address of the first delivery object;

[0009] Verify the first delivery plan information;

[0010] If the first delivery plan information is verified, the first target virtual resources required to complete the first delivery plan are determined based on the first delivery list and the first delivery schedule.

[0011] Verify the merchant's available virtual resources based on the first target virtual resources;

[0012] If the merchant's available virtual resources pass the verification, in response to the merchant's execution request for the first delivery plan, multiple first pre-orders are generated based on the first delivery plan information;

[0013] Based on each first pre-order, generate each first immediate order to execute the dispatch process.

[0014] In one possible implementation, the first delivery time arrangement is either a single delivery time arrangement or a multiple delivery time arrangement; the first delivery time arrangement includes a first delivery date and a first delivery time; in the case where the first delivery time arrangement is a multiple delivery time arrangement, the first delivery date is determined by the range of first delivery dates selected by the merchant and the repetition period within the range of first delivery dates.

[0015] In one possible implementation, verifying the first delivery plan information includes:

[0016] Verify that the first store identifier of each item in the first list is consistent;

[0017] If the first store identifier of each first list item is consistent, obtain the first store address corresponding to multiple first list items;

[0018] Calculate the first delivery distance between the first delivery address and the first store address for each first list item;

[0019] Verify whether each first delivery distance is less than or equal to a preset distance threshold.

[0020] In one possible implementation, each first pre-order carries a first delivery timestamp determined by a first delivery schedule;

[0021] Based on each first pre-order, generate each first immediate order to execute the dispatch process, including:

[0022] The first order backlog duration is determined based on the first delivery timestamp carried by each first pre-order;

[0023] Based on the first order retention period of each first pre-order, each first pre-order is converted into a first immediate order for order dispatch processing.

[0024] In one possible implementation, after converting each first pre-order into a first immediate order based on the first contingency period of each first pre-order to execute the dispatch process, the method further includes:

[0025] Update the merchant's available virtual resources based on the number of the first immediate orders converted.

[0026] In one possible implementation, the above-mentioned delivery planning management method also includes:

[0027] If the merchant's available virtual resources pass the verification, in response to the merchant's save request for the first delivery plan, the first delivery plan information is saved as a draft.

[0028] In one possible implementation, the above-mentioned delivery planning management method also includes:

[0029] In response to a merchant's cancellation request for the first delivery plan, obtain the plan status of the first delivery plan;

[0030] If the plan status is pending execution or pending submission, cancel the execution of the first delivery plan;

[0031] The "pending submission" status refers to the planning status of the first delivery plan after the first delivery plan information is saved as a draft; the "pending execution" status refers to the planning status of the first delivery plan after multiple first pre-orders are generated based on the first delivery plan information and before each first immediate order is generated based on each first pre-order.

[0032] In one possible implementation, the above-mentioned delivery planning management method also includes:

[0033] In response to a merchant's edit request for the first delivery plan, obtain the plan status of the first delivery plan;

[0034] When the plan status is pending execution or pending submission, receive the merchant's second delivery plan information; the second delivery plan information includes the second delivery time schedule corresponding to the second delivery plan and the second delivery list; the second delivery list includes multiple second list entries, each of which includes the merchant's second store identifier and the second delivery address of the second delivery object.

[0035] Verify the second delivery plan information;

[0036] If the second delivery plan information is verified, determine the second target virtual resources required to complete the second delivery plan based on the second delivery list and the second delivery schedule;

[0037] Verify the merchant's available virtual resources based on the second target virtual resources;

[0038] If the merchant's available virtual resources pass the verification, in response to the merchant's request to execute the second delivery plan, multiple first pre-orders are cancelled, and multiple second pre-orders are generated based on the second delivery plan information;

[0039] Based on each second pre-order, generate each second immediate order to execute the dispatch process.

[0040] Secondly, embodiments of this application provide a delivery plan management method, applied to a merchant terminal, including:

[0041] Receive the merchant’s first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time schedule; the first delivery list includes multiple first list entries, each first list entry includes the merchant’s first store identifier and the first delivery address of the first delivery object;

[0042] The first delivery plan information is sent to the server so that the server can verify the first delivery plan information. If the first delivery plan information is verified, the first target virtual resource required to complete the first delivery plan is determined according to the first delivery list and the first delivery time arrangement. The available virtual resources of the merchant are verified according to the first target virtual resource. If the available virtual resources of the merchant are verified, the verification result is sent to the merchant terminal.

[0043] Receive the verification result sent by the server;

[0044] In response to a merchant's request to execute the first delivery plan, the execution request for the first delivery plan is sent to the server, so that the server generates multiple first pre-orders based on the first delivery plan information, and generates first immediate orders based on each first pre-order to execute the order dispatch process.

[0045] Thirdly, embodiments of this application provide a delivery planning management system, including: a merchant terminal, an order server, and a delivery server; wherein,

[0046] The merchant terminal is used to receive the merchant's first delivery plan information and send the first delivery plan information to the order server. The first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time arrangement. The first delivery list includes multiple first list entries, and each first list entry includes the merchant's first store identifier and the first delivery address of the first delivery object.

[0047] The order server is used to receive the first delivery plan information sent by the merchant terminal, verify the first delivery plan information, and if the first delivery plan information passes the verification, determine the first target virtual resources required to complete the first delivery plan based on the first delivery list and the first delivery time arrangement, verify the merchant's available virtual resources based on the first target virtual resources, and if the merchant's available virtual resources pass the verification, send the verification result to the merchant terminal.

[0048] The merchant terminal is also used to receive the verification result sent by the order server, and in response to the merchant's execution request for the first delivery plan, send the execution request for the first delivery plan to the order server;

[0049] The order server is also used to generate multiple first pre-orders based on the first delivery plan information, generate each first instant order based on each first pre-order, and send each first instant order to the delivery server;

[0050] The delivery server is used to receive each first instant order and perform order dispatching for each first instant order.

[0051] Fourthly, embodiments of this application provide a delivery planning management device, including:

[0052] The receiving module is used to receive the merchant's first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant's first store identifier and the first delivery address of the first delivery object;

[0053] The first verification module is used to verify the first delivery plan information;

[0054] The determination module is used to determine the first target virtual resources required to complete the first delivery plan, based on the first delivery list and the first delivery schedule, after the first delivery plan information has been verified.

[0055] The second verification module is used to verify the merchant's available virtual resources based on the first target virtual resources;

[0056] The first generation module is used to generate multiple first pre-orders based on the first delivery plan information in response to the merchant's execution request for the first delivery plan, provided that the merchant's available virtual resources have been verified.

[0057] The second generation module is used to generate each first immediate order based on each first pre-order to execute the order dispatch process.

[0058] Fifthly, embodiments of this application provide an electronic device, including: a processor and a memory; wherein the memory stores a computer program, the computer program being adapted to be loaded by the processor and to execute the method steps provided in the first aspect of embodiments of this application.

[0059] Sixthly, embodiments of this application provide a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the method steps provided in the first aspect of embodiments of this application.

[0060] The aforementioned delivery plan management method, system, device, electronic equipment, and computer storage medium, by receiving first delivery plan information including a first delivery list and a first delivery schedule, wherein each item in the first delivery list includes the merchant's first store identifier and the first delivery recipient's first delivery address, facilitates the implementation of a "one-point pickup, multiple-point delivery" group meal delivery service based on the first delivery plan information, reducing operating costs and improving delivery efficiency. By verifying the first delivery plan information, and upon successful verification, determining the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule, and verifying the merchant's available virtual resources based on the first target virtual resource, can reduce the possibility of delivery plan failures due to insufficient available virtual resources of merchants, while ensuring the integrity and accuracy of the delivery plan information, thereby effectively reducing the risks of group meal delivery services. By verifying the initial delivery plan information and the merchant's available virtual resources, and responding to the merchant's execution request for the initial delivery plan, multiple first pre-orders are generated based on the initial delivery plan information. Then, based on each first pre-order, corresponding first immediate orders are generated for dispatch processing. This helps to allow merchants room for changes to the delivery plan before formally executing dispatch processing, improving the flexibility of delivery plan management. The entire delivery plan management solution not only achieves cost reduction and efficiency improvement and flexible delivery plan management, but also reduces the risks of group food delivery services, effectively improving the quality of group food delivery services. Attached Figure Description

[0061] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0062] Figure 1 is a schematic diagram of a delivery plan management page provided in an exemplary embodiment of this application;

[0063] Figure 2 is a schematic diagram of a newly added delivery plan window provided in an exemplary embodiment of this application;

[0064] Figure 3 is a schematic diagram of the architecture of a delivery planning management system provided in an exemplary embodiment of this application;

[0065] Figure 4 is a flowchart illustrating a delivery planning management method provided in an exemplary embodiment of this application;

[0066] Figure 5 is a flowchart illustrating another delivery planning management method provided in an exemplary embodiment of this application;

[0067] Figure 6 is a schematic diagram of a delivery time scheduling input area provided in an exemplary embodiment of this application;

[0068] Figure 7 is a flowchart illustrating another delivery planning management method provided in an exemplary embodiment of this application;

[0069] Figure 8 is a schematic diagram of an editable delivery plan window provided in an exemplary embodiment of this application;

[0070] Figure 9 is a flowchart illustrating another delivery planning management method provided in an exemplary embodiment of this application;

[0071] Figure 10 is a schematic diagram of the structure of a delivery planning management device provided in an exemplary embodiment of this application;

[0072] Figure 11 is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application. Detailed Implementation

[0073] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0074] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0075] First, let's introduce an application scenario applicable to this embodiment: After registering as a group delivery merchant on an online delivery platform, community canteens and other catering businesses can manage their delivery plans using the delivery plan management page 10 shown in Figure 1. For example, merchants can click the "Add Plan" control 11 in the delivery plan management page 10 to upload delivery plan information and create a new delivery plan. Specifically, after clicking the "Add Plan" control 11, the delivery plan management page 10 will display the "Add Delivery Plan" window 20 shown in Figure 2, allowing users to upload delivery plan information including the plan name, delivery list, and delivery time schedule. If the delivery plan information upload verification passes, the merchant can click the "Submit Plan" control 21 in the "Add Delivery Plan" window 20 to immediately execute the newly added delivery plan, or click the "Save Plan, Do Not Execute" control 22 to temporarily save the uploaded delivery plan information as a draft.

[0076] Once a delivery plan is created, it will be displayed in the plan list 12 shown in Figure 1. Merchants can edit or cancel each delivery plan they create through the operation bar 13 in the plan list 12. In addition, for delivery plans that have already started executing, merchants can view all orders associated with that delivery plan; for delivery plans that have not yet been executed, merchants can submit the plan to execute it immediately.

[0077] Please refer to Figure 3, which is a schematic diagram of the architecture of a delivery planning management system provided in an exemplary embodiment of this application. In this embodiment, a merchant terminal 30 logged into the online delivery platform communicates with the server 31 corresponding to the online delivery platform via a network. In this embodiment, the server 31 may include, but is not limited to, an order server, a delivery server, etc. A data storage system can store the data that the server 31 needs to process. The data storage system can be integrated onto the server 31, or it can be located in the cloud or on other network servers.

[0078] In some possible embodiments, the delivery planning management method provided in this application can be jointly executed by the merchant terminal 30 and the server 31. Accordingly, the delivery planning management device can also be respectively set in the merchant terminal 30 and the server 31.

[0079] In one embodiment, merchant terminal 30 receives first delivery plan information from a merchant and sends it to server 31. Server 31 verifies the first delivery plan information. If the verification passes, server 31 determines the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule. Server 31 then verifies the merchant's available virtual resources based on the first target virtual resource. If the verification passes, server 31 sends the verification result to merchant terminal 30. Merchant terminal 30 receives the verification result from server 31 and, in response to the merchant's execution request for the first delivery plan, sends the execution request for the first delivery plan to server 31. Server 31 generates multiple first pre-orders based on the first delivery plan information and generates first immediate orders based on each pre-order to execute order dispatching.

[0080] In one embodiment, merchant terminal 30 receives first delivery plan information from a merchant and sends it to the order server in server 31. The order server verifies the first delivery plan information. If the verification passes, it determines the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule. It then verifies the merchant's available virtual resources based on the first target virtual resource. If the merchant's available virtual resources pass the verification, it sends the verification result to merchant terminal 30. Merchant terminal 30 receives the verification result from the order server and, in response to the merchant's execution request for the first delivery plan, sends the execution request to the order server. The order server generates multiple first pre-orders based on the first delivery plan information, generates first immediate orders based on each first pre-order, and sends each first immediate order to the delivery server in server 31. The delivery server receives each first immediate order and performs order dispatch processing for each first immediate order.

[0081] In some possible embodiments, the delivery planning management method provided in this application can be executed by the merchant terminal 30. Accordingly, the delivery planning management device can also be installed in the merchant terminal 30.

[0082] In some possible embodiments, the delivery planning management method provided in this application can be executed by server 31. Accordingly, the delivery planning management device can also be located in server 31.

[0083] It is worth noting that the aforementioned first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time schedule; the first delivery list includes multiple first list entries, each of which includes the merchant's first store identifier and the first delivery address of the first recipient. Merchant terminal 30 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, etc. Server 31 can be implemented using a standalone server or a server cluster composed of multiple servers.

[0084] In one embodiment, as shown in Figure 4, a delivery plan management method is provided. Taking the application of this method to merchant terminal 30 in Figure 3 as an example, the method includes the following steps:

[0085] S401: Receive the merchant's first delivery plan information.

[0086] Optionally, the merchant uploads first delivery plan information, including the first delivery list and the first delivery time arrangement, based on the new delivery plan window 20 shown in Figure 2. The merchant terminal receives the first delivery plan information uploaded by the merchant and adds a new delivery plan according to the first delivery plan information.

[0087] The first delivery plan information may include, but is not limited to, delivery plan information for providing meal delivery services to the elderly and other groups. The first delivery list is a detailed delivery list filled out by the merchant according to a pre-set delivery list template. The first delivery list includes multiple first list entries, each including the merchant's first store identifier and the first delivery recipient's first delivery address. Understandably, a merchant may have multiple stores serving catering services; these stores may be located throughout the country, and each store's identifier is unique. The merchant's first store identifier is the identifier of the store under the merchant that serves catering services and awaits delivery personnel; the first store identifier includes, but is not limited to, the first store name and first store ID. The first delivery recipient's first delivery address may include, but is not limited to, textual information describing the geographical location of the first delivery recipient. The first delivery address includes multiple address levels, with the geographical scope of each level progressively decreasing to improve the accuracy of subsequent geocoding. For example, the first delivery address may include four address levels: province, city, district / county, and a specific address representing the street, community, and house number, to ensure the address information of the first delivery recipient is as accurate as possible.

[0088] It is worth noting that, in order to ensure cost reduction and efficiency improvement through the "one-point pickup, multiple-point delivery" model, the preset delivery list template stipulates that the store identifiers included in each list item must be consistent. Therefore, the first store identifiers corresponding to each first list item in the first delivery list of this embodiment must be consistent. If they are inconsistent, the first delivery list uploaded by the merchant will fail the verification, and the merchant needs to modify the first delivery list and upload it again to the merchant terminal for verification.

[0089] Furthermore, to ensure fast and accurate delivery of food to recipients and to guarantee "same-city delivery" service, the preset delivery list template stipulates that the store address corresponding to the store identifier in each list item and the delivery address of the recipient must be less than or equal to a preset distance threshold (e.g., 3 kilometers). Therefore, if the first store identifiers corresponding to each first list item in this embodiment are the same, but the delivery distance between the first store address corresponding to multiple first list items (i.e., the first store address corresponding to the first store identifier) ​​and the first delivery address of each first list item is greater than the preset distance threshold, the first delivery list uploaded by the merchant will fail verification. The merchant needs to modify the first delivery list and upload it again to the merchant terminal for verification.

[0090] In this embodiment, the merchant terminal receives first delivery plan information, which includes a first delivery list and a first delivery time arrangement. Each item in the first delivery list includes the merchant's first store identifier and the first delivery address of the first delivery object. This helps to adopt group meal delivery services such as "one-point pickup and multiple-point delivery" and "same-city delivery" based on the first delivery plan information, thereby reducing operating costs and improving delivery efficiency.

[0091] S402: Verify the first delivery plan information.

[0092] Optionally, the merchant terminal verifies the first delivery list in the first delivery plan information.

[0093] Specifically, the merchant terminal verifies the first store identifier in the first delivery list, checking whether the first store identifiers of each first list item are consistent. If the first store identifiers of each first list item are inconsistent, the first delivery list upload verification fails, and the merchant terminal displays a first delivery list upload failure message in the new delivery plan window 20 shown in Figure 2, such as "Upload failed, please ensure that the store identifiers in the file are consistent." If the first store identifiers of each first list item are consistent, the first delivery list upload verification passes. The merchant terminal further obtains the same first store address corresponding to multiple first list items and verifies whether the first delivery address entered for each first list item meets the preset requirements in the delivery list template based on the first store address. For example, during the verification of the first delivery address, the merchant terminal calculates the first delivery distance between the first delivery address and the first store address of each first list item and verifies whether each first delivery distance is less than or equal to a preset distance threshold (e.g., 3 kilometers). If the first delivery distance is greater than the preset distance threshold, the first delivery list upload verification will fail, and the merchant terminal will display a message indicating that the first delivery list upload failed in the "Add Delivery Plan" window 20 shown in Figure 2, such as "Upload failed. Please ensure that the delivery address in the file meets the delivery list template requirements." If the first delivery distance is less than or equal to the preset distance threshold, the first delivery list upload verification will pass, and the merchant terminal will display a message indicating that the first delivery list upload was successful in the "Add Delivery Plan" window 20 shown in Figure 2.

[0094] It is worth noting that, in practical applications, before the merchant terminal displays the successful upload notification for the first delivery list in the new delivery plan window 20 shown in Figure 2, the merchant terminal also performs validity checks on the file content of the first delivery list. For example, it checks whether the first store identifier exists under the merchant account, whether the first store corresponding to the first store identifier is in operation, whether the first delivery address actually exists, and whether the first delivery address is filled in completely according to the requirements of the delivery list template. In addition, the merchant terminal also performs format checks on the file content of the first delivery list, such as checking whether empty data appears in the first delivery list. This embodiment of the application does not limit this aspect.

[0095] In this embodiment, the merchant terminal verifies the first delivery list in the first delivery plan information and promptly feeds back the verification results to the user. This ensures that the first delivery list used to generate the first delivery plan meets the preset content and format requirements, and that the information in the first delivery list is true and valid. This avoids the situation where the first delivery plan cannot be successfully executed due to improper filling of the first delivery list, reduces the risk of group food delivery services, and improves the user experience for merchants.

[0096] S403: If the first delivery plan information is verified, determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule.

[0097] Optionally, if the first delivery plan information is verified, the merchant terminal determines the first total delivery cost (i.e., the first target virtual resource) required to complete the first delivery plan based on the first delivery list and the first delivery schedule.

[0098] Understandably, each item in the first delivery list (such as each row in the first delivery list) represents an independent delivery task, and each delivery task corresponds to a delivery fee. The first delivery schedule can be a single delivery schedule or a multi-delivery schedule. Upon successful verification of the first delivery plan information, the merchant terminal determines the first total delivery fee required to complete the first delivery plan, i.e., determines the first target virtual resource required to complete the first delivery plan, based on the total number of items in the first delivery list and the total number of deliveries corresponding to the first delivery schedule.

[0099] Specifically, when the first delivery schedule is a single delivery schedule, the first target virtual resource required to complete the first delivery plan is directly determined by the total number of delivery tasks in the first delivery list (i.e., the total number of items in the first list). When the first delivery schedule is a multiple delivery schedule, the first target virtual resource required to complete the first delivery plan is jointly determined by the total number of delivery tasks in the first delivery list and the total number of deliveries corresponding to the first delivery schedule. It is worth noting that when the first delivery schedule is a multiple delivery schedule, the delivery cost for completing all delivery tasks in the first delivery list each time can be the same or different. For example, after the total number of deliveries corresponding to the multiple delivery schedules exceeds the preset number of deliveries, the delivery cost for the one or more deliveries exceeding this limit is a discounted price. For example, assuming the preset number of deliveries is thirty, if the first delivery schedule is a thirty-five-delivery schedule, the delivery cost for the last five deliveries can be a discounted price.

[0100] In this embodiment, when the first delivery plan information is verified, the merchant terminal determines the first total delivery cost required to complete the first delivery plan based on the first delivery list and the first delivery time arrangement. This facilitates the subsequent verification of the merchant's available account balance based on the first total delivery cost required to complete the first delivery plan, thereby reducing the possibility of delivery plan failure due to insufficient available virtual resources of the merchant and effectively reducing the risk of group food delivery services.

[0101] S404: Verify the merchant's available virtual resources based on the first target virtual resources.

[0102] Optionally, the merchant terminal verifies whether the merchant's available account balance (i.e., available virtual resources) is sufficient based on the first total delivery cost (i.e., the first target virtual resource) required to complete the first delivery plan. Specifically, the merchant terminal verifies whether the merchant's available virtual resources are greater than or equal to the first target virtual resource. If the merchant's available virtual resources are less than the first target virtual resource, the merchant's available virtual resource verification fails, and the merchant terminal displays an insufficient available virtual resource prompt message in the Add Delivery Plan window 20 shown in Figure 2, such as "Insufficient account balance, please change the plan or recharge." At the same time, the "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 remain in an untriggerable state, and the merchant cannot create a new delivery plan based on the currently uploaded first delivery plan information. If the merchant's available virtual resources are greater than or equal to the first target virtual resource, the merchant's available virtual resource verification passes, and the "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 in the Add Delivery Plan window 20 switch to a triggerable state, allowing the merchant to create the first delivery plan according to the uploaded first delivery plan information.

[0103] In this embodiment, the merchant terminal verifies whether the merchant's available account balance is sufficient based on the first total delivery fee required to complete the first delivery plan. Only when the merchant's available account balance is sufficient is the merchant allowed to create the first delivery plan. This reduces the possibility of some delivery plans failing due to insufficient available virtual resources of the merchant, thereby reducing the risk of group food delivery services.

[0104] S405: If the merchant's available virtual resources pass the verification, in response to the merchant's execution request for the first delivery plan, generate multiple first pre-orders based on the first delivery plan information.

[0105] For example, referring to Figure 2, after the merchant's available virtual resources have passed verification, the merchant can perform a first trigger operation on the "Submit Plan" control 21 in the new delivery plan window 20 to initiate an execution request for the first delivery plan to the merchant terminal. In response to the merchant's execution request for the first delivery plan, the merchant terminal generates multiple first pre-orders based on the first delivery plan information. The first trigger operation can be, but is not limited to, custom interactive actions such as clicking, swiping, or long-pressing. A first pre-order is an order that has been generated but is temporarily in a pending execution state. Since the first pre-order has not yet been formally converted into an immediate order for delivery processing, it can be cancelled at any time.

[0106] Specifically, each item in the first delivery list may include first merchant information (including the first store identifier), first delivery recipient information (including the first delivery address), first meal item details (including the first meal item name and quantity), and first remarks for the first delivery recipient. If the merchant's available virtual resources pass verification, the merchant terminal responds to the merchant's execution request for the first delivery plan by generating multiple first pre-orders carrying a first delivery timestamp, based on the first merchant information, first delivery recipient information, first meal item details, first remarks, and first delivery time arrangement in the first delivery list. This allows for the subsequent generation of multiple first immediate orders based on these multiple pre-orders for order dispatch processing.

[0107] It's worth noting that when the first delivery time is a single delivery time arrangement, the merchant terminal will respond to the merchant's execution request for the first delivery plan by generating multiple first pre-orders corresponding to each item in the first delivery list. Each of these multiple first pre-orders carries the same first delivery-pending timestamp. The merchant terminal will subsequently convert these multiple first pre-orders into multiple first instant orders for dispatch processing. When the first delivery time is a multiple delivery time arrangement, the merchant terminal will respond to the merchant's execution request for the first delivery plan by generating multiple batches of pre-orders corresponding to multiple deliveries at once. Each batch of pre-orders includes multiple first pre-orders generated from multiple items in the first delivery list, and each batch carries a different first delivery-pending timestamp. The merchant terminal will subsequently convert these multiple batches of pre-orders into instant orders in batches for dispatch processing.

[0108] In this embodiment, when the verification of the first delivery plan information and the merchant's available virtual resources passes, the merchant terminal responds to the merchant's execution request for the first delivery plan and generates multiple first pre-orders based on the first delivery plan information. This helps to reserve space for merchants to change the delivery plan before executing the dispatch process, such as canceling the first pre-orders in response to the merchant's editing request for the first delivery plan, thereby improving the flexibility of delivery plan management.

[0109] S406: Generate each first immediate order based on each first pre-order to execute the order dispatch process.

[0110] The first immediate order is an order generated based on the first pre-order and that is in the execution state.

[0111] Understandably, after generating multiple first pre-orders, the merchant terminal performs first order backlog processing on each first pre-order based on the first delivery-pending timestamp carried by each first pre-order. Optionally, the merchant terminal determines the first backlog duration corresponding to each first pre-order based on the first delivery-pending timestamp carried by each first pre-order, and then converts each first pre-order into a first immediate order for order dispatch processing based on the first backlog duration of each first pre-order.

[0112] Optionally, the initial consolidation period for each first pre-order is determined by the delivery time corresponding to the first delivery timestamp carried by each first pre-order and the generation time of the first pre-order. Specifically, the merchant terminal first determines the generation time of the first instant order corresponding to each first pre-order based on the delivery times corresponding to each first delivery timestamp, and then determines the initial consolidation period for each first pre-order based on the generation times of each first instant order and the generation times of each first pre-order to perform the initial consolidation process for each first pre-order.

[0113] For example, the merchant terminal first determines the generation time of each first instant order as a time interval (e.g., 90 minutes) from each delivery time based on the delivery times corresponding to each first delivery timestamp. Then, it subtracts the generation time of each first pre-order from the generation time of each first instant order to obtain the first order backlog duration for each first pre-order. Finally, based on the first order backlog duration for each first pre-order, it generates each first instant order and sends each first instant order to the delivery server for order dispatch processing.

[0114] In this embodiment, the merchant terminal generates each first immediate order based on the first order duration corresponding to each first pre-order to execute the order dispatch process. This not only helps to reserve space for merchants to change the delivery plan before executing the order dispatch process, improving the flexibility of delivery plan management, but also allows sufficient time for the scheduling of delivery tasks, ensuring the rationality of delivery plan management.

[0115] In the aforementioned delivery plan management method, the merchant terminal receives first delivery plan information, including a first delivery list and a first delivery time schedule. Each item in the first delivery list includes the merchant's first store identifier and the first delivery address of the first recipient. This facilitates the implementation of group delivery services such as "one-point pickup and multiple-point delivery" and "same-city delivery" based on the first delivery plan information, reducing operating costs and improving delivery efficiency. By verifying the first delivery list in the first delivery plan information and promptly feeding back the verification results to the user, the method avoids situations where the first delivery plan cannot be successfully executed due to improper completion of the first delivery list, thus improving the user experience for merchants. If the first delivery plan information is verified successfully, the first total delivery cost required to complete the first delivery plan is determined based on the first delivery list and the first delivery time schedule, and the cost is calculated based on the completion of the first delivery plan. The initial total delivery cost for a delivery plan is verified against the merchant's available account balance. Only when the merchant's available account balance is sufficient is the initial delivery plan allowed to be created. This effectively mitigates the risk of partial delivery plan failures due to insufficient available virtual resources, reducing the risk associated with group food delivery services. Once the initial delivery plan information and the merchant's available virtual resources are verified, in response to the merchant's execution request for the initial delivery plan, multiple initial pre-orders are generated based on the initial delivery plan information. Based on the corresponding initial order backlog duration for each initial pre-order, initial immediate orders are generated for dispatch processing. This not only allows merchants room to modify delivery plans before dispatch processing, improving the flexibility of delivery plan management, but also allows sufficient time for delivery task scheduling, ensuring the rationality of delivery plan management. The entire delivery plan management solution not only achieves cost reduction and efficiency improvement and flexible delivery plan management, but also reduces the risk of group food delivery services, effectively improving the quality of group food delivery services.

[0116] In one embodiment, as shown in Figure 5, another delivery plan management method is provided. Taking the application of this method to a merchant terminal logged into an online delivery platform as an example, the method includes the following steps:

[0117] S501: Receive the merchant's first delivery plan information.

[0118] The first delivery plan information may include, but is not limited to, delivery plans providing meal delivery services to the elderly and other groups. The first delivery plan information includes the first plan name, the first delivery list, and the first delivery time schedule. The first delivery list is a detailed delivery list filled out by the merchant according to a pre-set delivery list template. The first delivery list may be, but is not limited to, a spreadsheet file, and includes multiple first list entries (e.g., each row represents one first list entry). Each first list entry includes information such as the first merchant, the first delivery recipient, the first meal item details, and the first set of remarks for the first delivery recipient.

[0119] The aforementioned first merchant information includes, but is not limited to, the first store identifier (such as the first store name and first store ID). The aforementioned first delivery recipient information includes, but is not limited to, the first delivery recipient's name, contact information, and first delivery address. The aforementioned first meal item details include, but are not limited to, the first meal item quantity, the first meal item identifier (such as the first meal item name and first meal item ID), and the first meal item unit price. The aforementioned first delivery recipient's first remarks section is used to fill in any special delivery requirements for the first delivery recipient, such as "The elderly person has difficulty walking, so there may be a longer wait time during delivery." Furthermore, the aforementioned first delivery recipient's first delivery address includes multiple address levels, such as province, city, district / county, and detailed delivery address (such as street, community, and house number), to ensure the address information of the first delivery recipient is as accurate as possible, thereby improving the accuracy of subsequent geocoding based on the first delivery address.

[0120] It is worth noting that the first delivery list is a detailed delivery list filled out by the merchant according to a preset delivery list template. The preset delivery list template specifies, but is not limited to, the following: the store identifiers included in each list item must be consistent; the store address corresponding to each store identifier and the delivery address of the recipient included in each list item must be less than or equal to a preset distance threshold (e.g., 3 kilometers); and the quantity of meals in each list item must be less than or equal to a preset quantity of meals (e.g., 5 servings).

[0121] For example, after a merchant clicks the "Add Plan" control 11 as shown in Figure 1, the merchant terminal displays the "Add Delivery Plan" window 20 as shown in Figure 2 by default. Based on the plan name input area 23, the delivery time arrangement input area 24, and the delivery list upload area 25, the terminal receives the first delivery plan information uploaded by the merchant. The delivery list upload area 25 includes a "Download Template" control 26. Merchants can click the "Download Template" control 26 to download a preset delivery list template, thereby completing the first delivery list according to the format and content requirements specified in the delivery list template.

[0122] Understandably, before the merchant terminal verifies that the merchant's available virtual resources are sufficient based on the first target virtual resources, the "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 shown in Figure 2 remain in an untriggerable state, and the merchant cannot create the first delivery plan based on the uploaded first delivery plan information; only after the merchant terminal verifies that the merchant's available virtual resources are sufficient based on the first target virtual resources, the "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 switch to a triggerable state, and the merchant can create the first delivery plan based on the first delivery plan information.

[0123] In this embodiment, the merchant terminal receives first delivery plan information, including first merchant information, first delivery recipient information, first meal details, and first remarks from the first delivery recipient. This not only helps to achieve accurate delivery but also helps to provide personalized delivery services to the first delivery recipient, thus improving the quality of group delivery services.

[0124] In one embodiment, the first delivery schedule is either a single delivery schedule or a multiple delivery schedule; the first delivery schedule includes a first delivery date and a first delivery time; in the case where the first delivery schedule is a multiple delivery schedule, the first delivery date is determined by a range of first delivery dates selected by the merchant and a repetition period within the range of first delivery dates.

[0125] For example, if the first delivery plan involves only a single delivery, the merchant can enter the first delivery schedule based on the delivery schedule input area 24 shown in Figure 2. Specifically, the delivery schedule input area 24 includes a time input component 27, which integrates a date and time selector. The merchant can enter the first delivery schedule by clicking the time input component 27 and using the date and time selector. This first delivery schedule includes the first delivery date and the first delivery time for the single delivery, such as "July 18, 2024, 12:00".

[0126] If the first delivery plan involves multiple deliveries, the merchant can click the "Multiple Delivery" control 28 shown in Figure 2 to update the display content in the delivery schedule input area 24 of the merchant terminal, as shown in Figure 6. Referring to Figure 6, the delivery schedule input area includes a time input component 27, a date input component 62, a special date exclusion component 63, and a repetition period input area 64. The time input component 27 integrates a date and time selector. Merchants can click the time input component 27 and the date input component 62 to input the first delivery date range corresponding to multiple deliveries and the first delivery time corresponding to each delivery in the multiple deliveries. They can also exclude special dates, such as holidays, from the first delivery date range by checking the special date exclusion component 63. Furthermore, merchants can select the repetition period within the first delivery date range based on the repetition period input area 64. Understandably, the repetition period within the first delivery date range can be one day or multiple days. The first delivery date corresponding to multiple deliveries is determined by the first delivery date range and the repetition period within the first delivery date range selected by the merchant.

[0127] Specifically, the first delivery date range is determined by the planned start date and planned end date of multiple deliveries. Merchants can click on the time input component 27 and use the date and time selector to input the planned start date of multiple deliveries and the first delivery time for each delivery, such as "July 18, 2024, 12:00". They can click on the date input component 62 to input the planned end date of multiple deliveries, such as "August 18, 2024". They can also select the special date exclusion component 63 to exclude all holidays within the first delivery date range (July 18, 2024 to August 18, 2024). Furthermore, merchants can click on the periodic controls in the repetition period input area 64, such as the "Wednesday" control 65 and the "Friday" control 66, to select Wednesdays and Fridays as the repetition period within the first delivery date range. Understandably, based on the above series of operations, the merchant sets the multiple delivery schedule as "delivered every Wednesday and Friday at 12:00 from July 18, 2024 to August 18, 2024".

[0128] In this embodiment, by determining the first delivery date corresponding to multiple delivery schedules based on the first delivery date range selected by the merchant and the repetition period within the first delivery date range, and determining multiple delivery schedules based on the first delivery date and the first delivery time, the delivery time for each delivery task in the first delivery list can be set efficiently. This helps to generate each first delivery time stamp carried by each first pre-order based on the delivery time, effectively improving the efficiency of delivery plan management and the user experience of merchants.

[0129] S502: Verify whether the first store identifier of each first list item is consistent. If yes, proceed to S503; otherwise, proceed to S513.

[0130] Understandably, to ensure cost reduction and efficiency improvement through the "one-point pickup, multiple-point delivery" model, the merchant terminal verifies whether the first store identifier of each item in the first delivery list is consistent. If the first store identifiers of all first list items are consistent, the same first store address corresponding to multiple first list items is obtained for further verification of the first delivery address. If the first store identifiers of the first list items are inconsistent, a message indicating a first delivery list upload failure is displayed, such as "Upload failed, please ensure that the store identifiers in the file are consistent."

[0131] In this embodiment, the merchant terminal verifies whether the first store identifier of each first list item is consistent. If they are inconsistent, a message indicating that the first delivery list upload failed is displayed. This allows the merchant to promptly modify the first delivery list, avoiding the situation where the first delivery plan cannot be executed smoothly due to inconsistent first store identifiers of each first list item. This reduces the risk of group food delivery services and improves the user experience for merchants.

[0132] S503: Retrieve the first store address corresponding to multiple first list entries.

[0133] The address of the first store may include, but is not limited to, textual information describing the geographical location of the first store.

[0134] Optionally, if the first store identifier of each first list item is consistent, the merchant terminal obtains the first store address corresponding to each first list item based on the first store identifier corresponding to each first list item, so as to verify whether the distance between the first delivery address and the first store address corresponding to each first list item is less than or equal to a preset distance threshold.

[0135] For example, when the first store identifier of each first list item is consistent, the merchant terminal obtains text information describing the geographical location of the first store, such as province, city, district / county and detailed address, through a pre-built database, so as to calculate the first delivery distance between the first delivery address and the first store address of each first list item.

[0136] S504: Calculate the first delivery distance between the first delivery address and the first store address for each first list entry.

[0137] The first delivery address for each first list entry may be, but is not limited to, textual information describing the geographical location of the first delivery recipient. Each first delivery address includes multiple address levels. For example, the first delivery address may include four address levels: province, city, district / county, and a specific address indicating the street, community, and house number. The first delivery distance may be, but is not limited to, latitude and longitude distance.

[0138] Optionally, the merchant terminal performs geocoding on the first delivery address and the first store address of each first list item. For example, it uses Gaia (Gaia Global Positioning System) to match latitude and longitude to perform geocoding on the first delivery address and the first store address of each first list item, obtains the latitude and longitude of each first delivery address and the latitude and longitude of the first store address corresponding to each first delivery address, and then calculates the first delivery distance (i.e., latitude and longitude distance) between the first delivery address and the first store address of each first list item based on the latitude and longitude of each first delivery address and the latitude and longitude of the first store address.

[0139] S505: Verify whether each first delivery distance is less than or equal to a preset distance threshold. If yes, proceed to S506; otherwise, proceed to S514.

[0140] The preset distance threshold is a pre-defined distance limit, such as 3 kilometers, and can be adjusted according to actual needs, such as to 2 kilometers, 5 kilometers, 10 kilometers, etc. The smaller the preset distance threshold is set, the fewer primary delivery targets can be covered, and the higher the timeliness of food delivery.

[0141] Optionally, the merchant terminal verifies whether the first delivery distance between the first delivery address and the first store address of each first list item is less than or equal to a preset distance threshold (e.g., 3 kilometers). If each first delivery distance is less than or equal to the preset distance threshold, the quantity of food items in each first list item is further verified. If any first delivery distance is greater than the preset distance threshold, a corresponding message indicating that the first delivery list upload failed is displayed, such as "Upload failed, please ensure that the delivery address in the file meets the requirements."

[0142] In this embodiment, the merchant terminal verifies whether the first store identifier in the first delivery list is consistent. If the first store identifier is consistent, it further verifies whether the first delivery distance between the first store address corresponding to the first store identifier and each first delivery address is less than or equal to a preset distance threshold. This not only helps to ensure that the group meal delivery service of "same-city delivery" and "one-point pickup and multiple-point delivery" is adopted according to the first delivery plan information, thus achieving cost reduction and efficiency improvement, but also avoids the situation where the first delivery plan cannot be successfully executed due to improper filling of the first delivery list by timely feedback of the verification results to the merchant, thereby reducing the risk of group meal delivery service and improving the user experience of the merchant.

[0143] S506: Verify whether the quantity of each item in the first list is less than or equal to the preset quantity of items. If yes, proceed to S507; otherwise, proceed to S515.

[0144] The preset quantity of meals is a pre-defined quantity of meals, such as 3 servings, 5 servings, etc.

[0145] Understandably, each item in the first delivery list (such as each row in the first delivery list) represents an independent delivery task, and each delivery task corresponds to a delivery fee. Therefore, an upper limit needs to be set on the number of meals in each item to avoid excessive losses for the online delivery platform.

[0146] Optionally, the merchant terminal retrieves the quantity of each item in the first delivery list line by line, verifying whether the quantity of each item is less than or equal to a preset quantity (e.g., 5 items). If the quantity of each item is less than or equal to the preset quantity, further verification is performed on the merchant's available virtual resources. If the quantity of any item in the first delivery list exceeds the preset quantity, a message indicating upload failure of the first delivery list is displayed, such as "Upload failed, please ensure that the quantity of items in the file meets the requirements."

[0147] In this embodiment, the merchant terminal verifies whether the quantity of each item in the first list is less than or equal to the preset quantity of food items, which helps ensure that the online delivery platform charges a reasonable delivery fee and reduces the risk of group food delivery services.

[0148] S507: Based on the first delivery list and the first delivery schedule, determine the first target virtual resources required to complete the first delivery plan.

[0149] Optionally, if the first delivery plan information is verified, the merchant terminal determines the first total delivery cost (i.e., the first target virtual resource) required to complete the first delivery plan based on the first delivery list and the first delivery schedule.

[0150] Understandably, each item in the first delivery list represents an independent delivery task, and each delivery task corresponds to a delivery fee. The first delivery schedule can be a single delivery schedule or multiple delivery schedules. Upon successful verification of the first delivery plan information, the merchant terminal determines the first total delivery fee required to complete the first delivery plan, i.e., determines the first target virtual resource required to complete the first delivery plan, based on the total number of items in the first delivery list and the total number of deliveries corresponding to the first delivery schedule.

[0151] S508: Verify whether the first target virtual resource is less than or equal to the merchant's available virtual resources. If yes, proceed to S509; otherwise, proceed to S516.

[0152] Optionally, the merchant terminal verifies whether the merchant's available account balance (i.e., available virtual resources) is sufficient based on the first total delivery cost (i.e., the first target virtual resource) required to complete the first delivery plan.

[0153] Specifically, the merchant terminal verifies whether the merchant's available virtual resources are greater than or equal to the first target virtual resources. Referring to Figure 2, if the merchant's available virtual resources are greater than or equal to the first target virtual resources, the verification passes. The "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 in the new delivery plan window 20 on the merchant terminal switch from an untriggerable state to a triggerable state, allowing the merchant to create a first delivery plan based on the uploaded first delivery plan information. If the merchant's available virtual resources are less than the first target virtual resources, the verification fails. The merchant terminal displays an insufficient available virtual resource message in the new delivery plan window 20, such as "Insufficient account balance, please change the plan or recharge." Simultaneously, the "Submit Plan" control 21 and the "Save Plan, Do Not Execute" control 22 remain untriggerable, preventing the merchant from creating a new delivery plan based on the currently uploaded first delivery plan information.

[0154] Understandably, the merchant creates the first delivery plan based on the uploaded first delivery plan information. This can be done either by triggering the "Submit Plan" control 21, which causes the merchant terminal to execute the first delivery plan immediately, or by triggering the "Save Plan, Do Not Execute" control 22, which causes the merchant terminal to save the first delivery plan information but not execute the first delivery plan immediately.

[0155] In this embodiment, the merchant terminal verifies whether the merchant's available account balance is sufficient based on the first total delivery fee required to complete the first delivery plan. Only when the merchant's available account balance is sufficient is the merchant allowed to create the first delivery plan. This reduces the possibility of some delivery plans failing due to insufficient available virtual resources of the merchant, thereby reducing the risk of group food delivery services.

[0156] S509: In response to a merchant’s request to execute a first delivery plan, generate multiple first pre-orders based on the first delivery plan information.

[0157] Optionally, if the merchant's available virtual resources pass the verification, the merchant terminal responds to the merchant's execution request for the first delivery plan and generates multiple first pre-orders based on the first delivery plan information.

[0158] Specifically, once the merchant's available virtual resources pass verification, the merchant terminal responds to the merchant's execution request for the first delivery plan by generating multiple first pre-orders carrying the first delivery timestamp based on the first merchant information, first delivery object information, first food item details, first remarks requirements, and first delivery time arrangement in the first delivery list. This allows for the subsequent generation of multiple first instant orders based on the multiple first pre-orders to execute the order dispatch process.

[0159] It is worth noting that when the first delivery time is a single delivery time arrangement, the merchant terminal will respond to the merchant's execution request for the first delivery plan by generating multiple first pre-orders corresponding to each item in the first delivery list. Each of these multiple first pre-orders carries the same first delivery-pending timestamp. The merchant terminal will subsequently convert these multiple first pre-orders into multiple first instant orders for dispatch processing. When the first delivery time is a multiple delivery time arrangement, the merchant terminal will respond to the merchant's execution request for the first delivery plan by generating multiple batches of first pre-orders corresponding to multiple deliveries at once. Each batch of first pre-orders includes multiple first pre-orders generated from multiple items in the first delivery list, and each batch of first pre-orders carries a different first delivery-pending timestamp. The merchant terminal will subsequently convert these multiple batches of first pre-orders into first instant orders in batches for dispatch processing.

[0160] In this embodiment, when the verification of the first delivery plan information and the merchant's available virtual resources passes, the merchant terminal responds to the merchant's execution request for the first delivery plan and generates multiple first pre-orders based on the first delivery plan information. This helps to reserve space for merchants to change the delivery plan before executing the dispatch process, such as canceling the first pre-orders in response to the merchant's editing request for the first delivery plan, thereby improving the flexibility of delivery plan management.

[0161] S510: Determine the first order backlog duration for each first order based on the first delivery timestamp carried by each first order.

[0162] Optionally, the merchant terminal first determines the generation time of the first instant order corresponding to each first pre-order based on the delivery time corresponding to each first delivery time stamp, and then determines the first order holding time of each first pre-order based on the generation time of each first instant order and the generation time of each first pre-order to perform the first order holding process on each first pre-order.

[0163] For example, the merchant terminal determines the generation time of each first instant order as a time that is a preset time (e.g., ninety minutes) away from each delivery time based on each delivery time corresponding to each first delivery timestamp. Then, the first order waiting time is obtained by subtracting the generation time of each first pre-order from the generation time of each first instant order.

[0164] S511: Based on the first order retention period of each first pre-order, convert each first pre-order into a first immediate order to execute the order dispatch process.

[0165] Optionally, the merchant terminal generates each first instant order based on the first order retention period corresponding to each first pre-order, and then sends each first instant order to the delivery server so that the delivery server assigns the delivery tasks corresponding to each first instant order to the delivery personnel, thereby executing the order dispatch process.

[0166] In this embodiment, the merchant terminal determines the first order backlog duration of each first order based on the first delivery timestamp carried by each first order, and generates each first immediate order for order dispatch processing based on the first order backlog duration. This not only helps to reserve space for merchants to change the delivery plan before order dispatch processing, improving the flexibility of delivery plan management, but also allows sufficient time for scheduling delivery tasks, ensuring the rationality of delivery plan management.

[0167] S512: Update the merchant's available virtual resources based on the number of the first immediate orders converted.

[0168] Optionally, the merchant terminal adopts a real-time settlement method, deducting the corresponding delivery fee for each first instant order from the merchant's available account balance at the moment each first instant order is generated. Specifically, the merchant terminal calculates the total delivery fee for all first instant orders based on the number of converted first instant orders and the delivery fee corresponding to each first instant order, and deducts the total delivery fee from the merchant's available account balance (i.e., available virtual resources), thereby updating the merchant's available account balance.

[0169] It is worth noting that when the delivery time arrangement corresponding to the first delivery plan is a single delivery time arrangement, the merchant terminal deducts the total delivery cost of multiple first instant orders generated simultaneously, that is, deducts the first total delivery cost (i.e., the first target virtual resource) required to complete the first delivery plan all at once. When the delivery time arrangement corresponding to the first delivery plan is a multiple delivery time arrangement, the merchant terminal deducts the total delivery cost corresponding to each batch of first instant orders at the time of generation of each batch of first instant orders, that is, deducts the first total delivery cost required to complete the first delivery plan in batches.

[0170] In addition, after updating the merchant's available virtual resources based on the number of first instant orders converted, the merchant terminal will also display the updated details of available virtual resources on the delivery plan management page 10 shown in Figure 1, that is, the delivery fee details of multiple first instant orders, so that the merchant can understand the specific deduction situation of the first delivery plan.

[0171] In this embodiment, the merchant terminal adopts a real-time settlement method to update the merchant's available virtual resources. After updating the merchant's available virtual resources, it displays the update details of available virtual resources. This not only enables batch deductions and reserves space for merchants to change delivery plans, improving the flexibility of delivery plan management, but also allows merchants to understand the specific deduction status of the first delivery plan, improving the user experience of merchants and the service quality of group food delivery.

[0172] S513: The corresponding message is "First delivery list upload failed".

[0173] For details, please refer to S502, which will not be repeated here.

[0174] S514: The corresponding message is "First delivery list upload failed".

[0175] For details, please refer to S505, which will not be repeated here.

[0176] S515: The corresponding message is "First delivery list upload failed".

[0177] For details, please refer to S506, which will not be repeated here.

[0178] S516: Displays a message indicating insufficient available virtual resources.

[0179] For details, please refer to S508, which will not be repeated here.

[0180] In the aforementioned delivery plan management method, the merchant terminal receives first delivery plan information, including first merchant information, first delivery recipient information, first meal item details, and first delivery recipient's first remarks. This facilitates accurate delivery and provides personalized delivery services to the first delivery recipient. By verifying whether the first store identifier of each first list item is consistent, whether the first delivery distance between the first store address corresponding to the first store identifier and each first delivery address is less than or equal to a preset distance threshold, whether the quantity of each meal item in each first list item is less than or equal to a preset quantity, and whether the merchant's available account balance is sufficient, the method avoids situations where the first delivery plan cannot be successfully executed due to improper filling of the first delivery list or insufficient merchant's available account balance, thus reducing the risk of group delivery services. By generating multiple first pre-orders and converting each first pre-order into a first immediate order based on the first order backlog duration, the method not only helps to reserve space for merchants to modify delivery plans before executing order dispatch processing, improving the flexibility of delivery plan management, but also allows sufficient time for scheduling delivery tasks, ensuring the rationality of delivery plan management. By adopting real-time settlement, the system updates merchants' available virtual resources and displays detailed updates afterward. This not only enables phased deductions, allowing merchants room to modify delivery plans, but also enables them to understand the specific deductions for the first delivery plan, improving the user experience. For the primary delivery recipient, this solution achieves precise delivery and personalized food delivery services; for merchants, it effectively reduces the risks of group food delivery services and improves the flexibility and rationality of delivery plan management. The overall delivery plan management solution effectively improves the quality of group food delivery services.

[0181] In one embodiment, as shown in Figure 7, another delivery plan management method is provided. Taking the application of this method to a merchant terminal logged into an online delivery platform as an example, the method includes the following steps:

[0182] S701: Receive the merchant's first delivery plan information.

[0183] Specifically, S701 is the same as S401, and will not be repeated here.

[0184] S702: Verify the first delivery plan information.

[0185] Specifically, S702 is the same as S402, and will not be repeated here.

[0186] S703: If the first delivery plan information is verified, determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule.

[0187] Specifically, S703 is the same as S403, which will not be repeated here.

[0188] S704: Verify the merchant's available virtual resources based on the first target virtual resources.

[0189] Specifically, S704 is the same as S404, and will not be repeated here.

[0190] S705: If the merchant's available virtual resources pass the verification, in response to the merchant's save request for the first delivery plan, save the first delivery plan information as a draft.

[0191] For example, referring to Figure 2, when the merchant's available virtual resources pass verification, the "Save Plan, Do Not Execute Yet" control 22 in the new delivery plan window 20 switches from an untriggerable state to a triggerable state. The merchant can perform a first triggering operation (such as clicking, swiping, etc.) on the "Save Plan, Do Not Execute Yet" control 22 to initiate an execution request for the first delivery plan to the merchant terminal. In response to the merchant's save request for the first delivery plan, the merchant terminal saves the first delivery plan information, including the first delivery list and the first delivery time schedule, as a draft.

[0192] It is worth noting that after the merchant terminal saves the first delivery plan information as a draft, the plan status of the first delivery plan is "pending execution".

[0193] In this embodiment, the merchant terminal, upon successful verification of the merchant's available virtual resources, responds to the merchant's request to save the first delivery plan and saves the first delivery plan information as a draft. This allows the merchant to save the delivery plan without immediately executing it, thus improving the flexibility of delivery plan management.

[0194] S706: In response to a merchant's edit request for the first delivery plan, obtain the plan status of the first delivery plan.

[0195] For example, please refer to Figure 1. Assume that the first delivery plan corresponds to the first row of delivery plans in the plan list 12 of the delivery plan management page 10, and the name of the first plan corresponding to the first delivery plan is "Delivery Plan 1". Merchants can initiate an edit request for the first delivery plan by triggering the "Edit" control 14. The merchant terminal responds to the merchant's edit request for the first delivery plan and obtains the plan status of the first delivery plan.

[0196] Understandably, after generating each first immediate order based on each first pre-order, the merchant terminal sends the first immediate order to the delivery server for order dispatch and updates the merchant's available virtual resources based on the number of converted first immediate orders. However, it cannot edit delivery plans that are in progress or terminated. Therefore, in response to a merchant's request to edit a first delivery plan, the merchant terminal first obtains the plan status of the first delivery plan and determines whether the plan status belongs to either the pending submission status or the pending execution status—both editable plan statuses.

[0197] Specifically, the planning status of the first delivery plan may include, but is not limited to, pending submission, pending execution, in execution, terminating, and terminated status. The pending submission status is the planning status of the first delivery plan after the first delivery plan information is saved as a draft; the pending execution status is the planning status of the first delivery plan after multiple first pre-orders are generated based on the first delivery plan information, but before each first immediate order is generated from each first pre-order; the in execution status is the planning status of the first delivery plan after each first pre-order is generated, but before each first immediate order completes its dispatch processing; and the terminating status is the planning status of the first delivery plan after the merchant submits a cancellation request for the first delivery plan, but before the merchant terminal cancels the execution of the first delivery plan.

[0198] S707: Receive the merchant's second delivery plan information when the plan status is pending execution or pending submission.

[0199] For example, please refer to Figure 1. Assuming that the first delivery plan corresponds to the first row of the delivery plan in the plan list 12 of the delivery plan management page 10, after the merchant terminal obtains that the plan status of the first delivery plan is pending submission, the edit delivery plan window 80 shown in Figure 8 will pop up on the delivery plan management page 10 shown in Figure 1 to receive the merchant's second delivery plan information.

[0200] Please refer to Figure 8. The delivery plan editing window 80 includes a plan name editing area 81, a delivery time schedule editing area 82, a delivery list editing area 83, a "Save Plan, Do Not Execute Yet" control 22, and a "Submit Plan" control 21. The plan name editing area 81, delivery time schedule editing area 82, and delivery list editing area 83 display the state before editing by default, i.e., displaying the first delivery plan information corresponding to the first delivery plan. Merchants can modify the first delivery plan information to obtain the second delivery plan information. The second delivery plan information includes the second plan name, the second delivery time schedule, and the second delivery list; the second delivery list includes multiple second list entries, each including the merchant's second store identifier and the second delivery address of the second delivery recipient.

[0201] S708: Verify the second delivery plan information.

[0202] Optionally, the merchant terminal verifies the second delivery list in the second delivery plan information.

[0203] Specifically, the merchant terminal verifies the second store identifier in the second delivery list, checking whether the second store identifiers of each second list item are consistent. If the second store identifiers of each second list item are inconsistent, the second delivery list upload verification fails, and the merchant terminal displays a second delivery list upload failure message in the edit delivery plan window 80 shown in Figure 8, such as "Upload failed, please ensure that the store identifiers in the file are consistent." If the second store identifiers of each second list item are consistent, the second delivery list upload verification passes. The merchant terminal further obtains the same second store address corresponding to multiple second list items and verifies whether the second delivery address entered for each second list item meets the preset requirements in the delivery list template based on the second store address. For example, during the verification of the second delivery address, the merchant terminal calculates the second delivery distance between the second delivery address and the second store address of each second list item and verifies whether each second delivery distance is less than or equal to a preset distance threshold (e.g., 3 kilometers). If the second delivery distance is greater than the preset distance threshold, the second delivery list upload verification will fail, and the merchant terminal will display a message indicating that the second delivery list upload failed in the Edit Delivery Plan window 80 shown in Figure 8, such as "Upload failed. Please ensure that the delivery address in the file meets the delivery list template requirements." If the second delivery distance is less than or equal to the preset distance threshold, the second delivery list upload verification will pass, and the merchant terminal will display a message indicating that the second delivery list upload was successful in the Edit Delivery Plan window 80 shown in Figure 8.

[0204] It is worth noting that, in practical applications, before the merchant terminal displays the successful upload notification for the second delivery list in the edit delivery plan window 80 (as shown in Figure 8), the merchant terminal also performs validity checks on the file content of the second delivery list. For example, it checks whether the second store identifier exists under the merchant account, whether the second store corresponding to the second store identifier is in operation, whether the second delivery address actually exists, and whether the second delivery address is filled in completely according to the requirements of the delivery list template. In addition, the merchant terminal also performs format checks on the file content of the second delivery list, such as checking whether empty data appears in the second delivery list. This embodiment of the application does not limit this aspect.

[0205] S709: If the second delivery plan information is verified, determine the second target virtual resources required to complete the second delivery plan based on the second delivery list and the second delivery schedule.

[0206] Optionally, if the second delivery plan information is verified, the merchant terminal determines the second total delivery cost (i.e., the second target virtual resource) required to complete the second delivery plan based on the second delivery list and the second delivery schedule.

[0207] Understandably, each item in the second delivery list (such as each row in the second delivery list) represents an independent delivery task, and each delivery task corresponds to a delivery fee. The second delivery schedule can be a single delivery schedule or a multiple delivery schedule. Upon successful verification of the second delivery plan information, the merchant terminal determines the second total delivery fee required to complete the second delivery plan based on the total number of second delivery list items and the total number of deliveries corresponding to the second delivery schedule; that is, it determines the second target virtual resource required to complete the second delivery plan.

[0208] Specifically, when the second delivery schedule is a single-delivery schedule, the second target virtual resources required to complete the second delivery plan are directly determined by the total number of delivery tasks in the second delivery list (i.e., the total number of items in the second list). When the second delivery schedule is a multiple-delivery schedule, the second target virtual resources required to complete the second delivery plan are jointly determined by the total number of delivery tasks in the second delivery list and the total number of deliveries corresponding to the second delivery schedule. It is worth noting that when the second delivery schedule is a multiple-delivery schedule, the delivery cost for completing all delivery tasks in the second delivery list each time can be the same or different. For example, after the total number of deliveries corresponding to the multiple delivery schedules exceeds the preset number of deliveries, the delivery cost for the one or more deliveries exceeding this limit is a discounted price. For example, assuming the preset number of deliveries is thirty, in the case of a thirty-five-delivery schedule in the second delivery schedule, the delivery cost for the last five deliveries can be a discounted price.

[0209] S710: Verify the merchant's available virtual resources based on the second target virtual resources.

[0210] Optionally, the merchant terminal verifies whether the merchant's available account balance (i.e., available virtual resources) is sufficient based on the second total delivery cost (i.e., the second target virtual resource) required to complete the second delivery plan. Specifically, the merchant terminal verifies whether the merchant's available virtual resources are greater than or equal to the second target virtual resource. If the merchant's available virtual resources are less than the second target virtual resource, the merchant's available virtual resource verification fails, and the merchant terminal displays an insufficient available virtual resource prompt message in the delivery plan editing window 80 shown in Figure 8, such as "Insufficient account balance, please change the plan or recharge." At the same time, the "Save plan, do not execute for now" control 22 and the "Submit plan" control 21 remain in an untriggerable state, and the merchant cannot generate a new delivery plan based on the currently uploaded second delivery plan information. If the merchant's available virtual resources are greater than or equal to the second target virtual resource, the merchant's available virtual resource verification passes, and the "Save plan, do not execute for now" control 22 and the "Submit plan" control 21 in the delivery plan editing window 80 switch to a triggerable state, allowing the merchant to generate a second delivery plan based on the uploaded second delivery plan information.

[0211] S711: If the merchant's available virtual resources pass the verification, in response to the merchant's request to execute the second delivery plan, cancel multiple first pre-orders and generate multiple second pre-orders based on the second delivery plan information.

[0212] For example, referring to Figure 8, after the merchant's available virtual resources have passed verification, the merchant can execute a second triggering operation on the "Submit Plan" control 21 in the Edit Delivery Plan window 80 to initiate an execution request for the second delivery plan to the merchant terminal. In response to the merchant's execution request for the second delivery plan, the merchant terminal generates multiple second pre-orders based on the second delivery plan information. The second triggering operation can be, but is not limited to, custom interactive actions such as clicking, swiping, or long-pressing. The second pre-orders are orders that have been generated but are temporarily in a pending execution state. Since the second pre-orders have not yet been formally converted into immediate orders for delivery processing, they can also be cancelled at any time.

[0213] Specifically, each item in the second delivery list may include second merchant information (including the second store identifier), second delivery recipient information (including the second delivery address), second meal item details (including the second meal item name and quantity), and second remarks for the second delivery recipient. Upon successful verification of the merchant's available virtual resources, the merchant terminal responds to the merchant's execution request for the second delivery plan, cancels multiple first pre-orders, and generates multiple second pre-orders carrying second delivery timestamps based on the second merchant information, second delivery recipient information, second meal item details, second remarks, and the second delivery time schedule in the second delivery list. This allows for the subsequent generation of multiple second immediate orders based on these second pre-orders for order dispatch processing.

[0214] It is worth noting that the first pre-order refers to the order that has been generated but is temporarily in the pending execution state. In the case that the first delivery time arrangement of the first delivery plan is multiple delivery time arrangements, the merchant terminal responds to the merchant's execution request for the second delivery plan and cancels the multiple unexecuted first pre-orders, which are the first pre-orders that have not yet been converted into the first instant order.

[0215] S712: Generate each second immediate order based on each second pre-order to execute the dispatch process.

[0216] The second immediate order is an order generated based on the second pre-order and is in the execution state.

[0217] Understandably, after generating multiple second pre-orders, the merchant terminal performs second order consolidation processing on each second pre-order based on the second delivery-pending timestamp carried by each second pre-order. Optionally, the merchant terminal determines the corresponding second consolidation duration for each second pre-order based on the second delivery-pending timestamp carried by each second pre-order, and then converts each second pre-order into a second immediate order for order dispatch processing based on the second consolidation duration of each second pre-order.

[0218] Optionally, the second consolidation period for each second pre-order is determined by the delivery time corresponding to the second delivery timestamp carried by each second pre-order and the generation time of the second pre-order. Specifically, the merchant terminal first determines the generation time of the second instant order corresponding to each second pre-order based on the delivery times corresponding to each second delivery timestamp, and then determines the second consolidation period for each second pre-order based on the generation time of each second instant order and the generation time of each second pre-order to perform the second consolidation processing on each second pre-order.

[0219] For example, the merchant terminal first determines the generation time of each second instant order based on the delivery time corresponding to each second delivery time stamp, setting it to be a time interval (e.g., 90 minutes) from each delivery time. Then, it subtracts the generation time of each second pre-order from the generation time of each second instant order to obtain the second order holding time corresponding to each second pre-order. Finally, based on the second order holding time corresponding to each second pre-order, it generates each second instant order and sends it to the delivery server for order dispatch processing.

[0220] In this embodiment, the merchant terminal, in response to the merchant's editing request for the first delivery plan, verifies the plan status of the first delivery plan. If the plan status of the first delivery plan is editable, it verifies the second delivery plan information and the merchant's available virtual resources. Only when the verification of the second delivery plan information and the merchant's available virtual resources passes is multiple first pre-orders cancelled and a second pre-order corresponding to the second delivery plan generated. Based on each second pre-order, each second immediate order is generated to execute the order dispatch process. This not only reduces costs and increases efficiency and lowers the risk of group food delivery services, but also ensures the rationality of delivery plan management and can effectively improve the quality of group food delivery services.

[0221] The aforementioned delivery plan management method, upon successful verification of the merchant's available virtual resources, responds to the merchant's request to save the first delivery plan by saving the information as a draft. This allows merchants to save delivery plans without immediately executing them, improving the flexibility of delivery plan management. Furthermore, by responding to the merchant's request to edit the first delivery plan, the method verifies the plan's status. Only when the first delivery plan is in either the "pending submission" or "pending execution" editable state is the merchant allowed to edit it. This not only reduces costs and increases efficiency, lowers the risk of group food delivery services, but also ensures the rationality of delivery plan management. Adopting this delivery plan management scheme can effectively improve the quality of group food delivery services.

[0222] In one embodiment, as shown in Figure 9, another delivery plan management method is provided. Taking the application of this method to a merchant terminal logged into an online delivery platform as an example, the method includes the following steps:

[0223] S901: Receives the merchant's first delivery plan information.

[0224] Specifically, S901 is the same as S401, and will not be repeated here.

[0225] S902: Verify the first delivery plan information.

[0226] Specifically, S902 is the same as S402, and will not be repeated here.

[0227] S903: If the first delivery plan information is verified, determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery schedule.

[0228] Specifically, S903 is identical to S403, which will not be repeated here.

[0229] S904: Verify the merchant's available virtual resources based on the first target virtual resources.

[0230] Specifically, S904 is the same as S404, which will not be repeated here.

[0231] S905: If the merchant's available virtual resources pass the verification, in response to the merchant's execution request for the first delivery plan, generate multiple first pre-orders based on the first delivery plan information.

[0232] Specifically, S905 is identical to S405, which will not be repeated here.

[0233] S906: In response to a merchant's cancellation request for the first delivery plan, obtain the plan status of the first delivery plan.

[0234] For example, please refer to Figure 1. Assume that the first delivery plan corresponds to the first delivery plan in the plan list 12 of the delivery plan management page 10, and the first plan name corresponding to the first delivery plan is "Delivery Plan 1". Merchants can initiate a cancellation request for the first delivery plan by triggering the "Cancel" control 15. The merchant terminal responds to the merchant's cancellation request for the first delivery plan and obtains the plan status of the first delivery plan.

[0235] S907: If the plan status is pending execution or pending submission, cancel the execution of the first delivery plan.

[0236] For example, please refer to Figure 1. Assuming that the first delivery plan corresponds to the second row of the delivery plan in the plan list 12 of the delivery plan management page 10, after the merchant terminal obtains that the plan status of the first delivery plan is pending execution, it cancels the generation of multiple first pre-orders based on the first delivery plan information to cancel the execution of the first delivery plan.

[0237] It is worth noting that this embodiment only describes a preferred implementation of the present application. If the first delivery plan corresponds to the first row of delivery plans in the plan list 12 of the delivery plan management page 10, the merchant terminal deletes the first delivery plan from the plan list 12 after obtaining the plan status of the first delivery plan as pending submission, so that the merchant cannot submit the first delivery plan in the pending execution status based on the "submit" control 16.

[0238] In this embodiment, the merchant terminal verifies the plan status of the first delivery plan in response to the merchant's cancellation request for the first delivery plan. If the plan status of the first delivery plan is pending execution or pending submission, the execution of the first delivery plan is cancelled, which improves the flexibility of delivery plan management and can effectively improve the quality of group meal delivery services.

[0239] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0240] Based on the inventive concept of the above-described delivery planning management method, as shown in FIG10, this application embodiment also provides a delivery planning management device 100 for implementing the above-described delivery planning management method. The delivery planning management device 100 includes:

[0241] The receiving module 101 is used to receive the merchant's first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant's first store identifier and the first delivery address of the first delivery object.

[0242] The first verification module 102 is used to verify the first delivery plan information;

[0243] The determination module 103 is used to determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery time arrangement, provided that the first delivery plan information has been verified.

[0244] The second verification module 104 is used to verify the merchant's available virtual resources based on the first target virtual resources;

[0245] The first generation module 105 is used to generate multiple first pre-orders based on the first delivery plan information in response to the merchant's execution request for the first delivery plan, provided that the merchant's available virtual resources have been verified.

[0246] The second generation module 106 is used to generate each first immediate order based on each first pre-order to perform order dispatch processing.

[0247] In one embodiment, the first delivery schedule is either a single delivery schedule or a multiple delivery schedule; the first delivery schedule includes a first delivery date and a first delivery time; in the case where the first delivery schedule is a multiple delivery schedule, the first delivery date is determined by a range of first delivery dates selected by the merchant and a repetition period within the range of first delivery dates.

[0248] In one embodiment, the first verification module 102 is specifically used to verify whether the first store identifier of each first list item is consistent; if the first store identifier of each first list item is consistent, obtain the first store address corresponding to the multiple first list items; calculate the first delivery distance between the first delivery address and the first store address of each first list item; and verify whether each first delivery distance is less than or equal to a preset distance threshold.

[0249] In one embodiment, each first pre-order carries a first delivery timestamp determined by a first delivery schedule; the second generation module 106 is specifically used to determine the first order backlog duration of each first pre-order based on the first delivery timestamp carried by each first pre-order; and to convert each first pre-order into a first immediate order for order dispatch processing based on the first order backlog duration of each first pre-order.

[0250] In one embodiment, the delivery planning management device 100 further includes a virtual resource update module for updating the merchant's available virtual resources based on the number of the first instant orders converted.

[0251] In one embodiment, the delivery plan management device 100 further includes a response module for saving the first delivery plan information as a draft in response to the merchant's save request for the first delivery plan, provided that the merchant's available virtual resources have been verified.

[0252] In one embodiment, the response module is further configured to respond to a merchant's cancellation request for the first delivery plan by obtaining the plan status of the first delivery plan; and cancel the execution of the first delivery plan if the plan status is pending execution or pending submission; wherein, the pending submission status is the plan status of the first delivery plan after the first delivery plan information is saved as a draft; and the pending execution status is the plan status of the first delivery plan after multiple first pre-orders are generated based on the first delivery plan information and before each first immediate order is generated based on each first pre-order.

[0253] In one embodiment, the response module is further configured to respond to the merchant's editing request for the first delivery plan and obtain the plan status of the first delivery plan; the receiving module 101 is further configured to receive the merchant's second delivery plan information when the plan status is pending execution or pending submission; the second delivery plan information includes the second delivery time arrangement and the second delivery list corresponding to the second delivery plan; the second delivery list includes multiple second list entries, each second list entry including the merchant's second store identifier and the second delivery address of the second delivery object; the first verification module 102 is further configured to verify the second delivery plan information; the determining module 103 is further configured to, if the second delivery plan information is verified as passed, determine the second target virtual resources required to complete the second delivery plan based on the second delivery list and the second delivery time arrangement; the second verification module 104 is further configured to verify the merchant's available virtual resources based on the second target virtual resources; the first generation module 105 is further configured to, if the merchant's available virtual resources are verified as passed, respond to the merchant's execution request for the second delivery plan, cancel multiple first pre-orders, and generate multiple second pre-orders based on the second delivery plan information; the second generation module 106 is further configured to generate each second immediate order based on each second pre-order to execute the order dispatch process.

[0254] Each module in the aforementioned delivery planning management device 100 can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0255] This application also provides an electronic device, which can be a terminal, and its internal structure is shown in Figure 10. The electronic device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a delivery planning management method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the electronic device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the electronic device, or external keyboards, touchpads, or mice, etc.

[0256] Those skilled in the art will understand that the structure shown in Figure 10 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0257] This application also provides a computer storage medium storing instructions that, when run on a computer or processor, cause the computer or processor to perform one or more steps in the above embodiments. If the constituent modules of the above-described electronic device are implemented as software functional units and sold or used as independent products, they can be stored in the above-described computer-readable storage medium.

[0258] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer storage medium or transmitted through the computer storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs (DVDs)), or semiconductor media (e.g., solid-state drives (SSDs)).

[0259] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks. Unless otherwise specified, the technical features of this embodiment and its implementation can be combined arbitrarily.

[0260] The embodiments described above are merely preferred embodiments of this application and are not intended to limit the scope of this application. Any modifications and improvements made by those skilled in the art to the technical solutions of this application without departing from the spirit of this application should fall within the protection scope defined by the claims.

[0261] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A method for managing delivery plans, characterized in that, The method includes: Receive the merchant’s first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant’s first store identifier and the first delivery address of the first delivery object; Verify the first delivery plan information; If the first delivery plan information is verified, the first target virtual resource required to complete the first delivery plan is determined based on the first delivery list and the first delivery schedule. Verify the merchant's available virtual resources based on the first target virtual resource; If the merchant's available virtual resources pass the verification, in response to the merchant's execution request for the first delivery plan, multiple first pre-orders are generated based on the first delivery plan information; the multiple first pre-orders can be cancelled. Based on each of the first pre-orders, generate each of the first immediate orders to execute the order dispatch process; The verification of the first delivery plan information includes: Verify that the first store identifiers of each of the first list entries are consistent; If the first store identifiers of the first list entries are inconsistent, it is determined that the verification of the first delivery plan information fails.

2. The method as described in claim 1, characterized in that, The first delivery schedule is either a single delivery schedule or a multiple delivery schedule; the first delivery schedule includes a first delivery date and a first delivery time; in the case of the first delivery schedule being a multiple delivery schedule, the first delivery date is determined by the first delivery date range selected by the merchant and the repetition period within the first delivery date range.

3. The method as described in claim 1, characterized in that, The method further includes: If the first store identifier of each of the first list entries is consistent, obtain the first store address corresponding to the plurality of first list entries; Calculate the first delivery distance between the first delivery address and the first store address for each of the first list entries; Verify whether each of the first delivery distances is less than or equal to a preset distance threshold.

4. The method as described in claim 1, characterized in that, Each of the first pre-orders carries a first delivery timestamp determined by the first delivery schedule; The step of generating each first immediate order based on each first pre-order to execute the order dispatch process includes: The first order backlog duration for each of the first pre-orders is determined based on the first delivery timestamp carried by each of the first pre-orders. Based on the first order retention period of each first pre-order, each first pre-order is converted into a first immediate order for order dispatch processing.

5. The method as described in claim 4, characterized in that, After converting each first pre-order into a first immediate order based on the first congestion period of each first pre-order for order dispatching, the method further includes: Update the merchant's available virtual resources based on the number of the first instant orders converted.

6. The method as described in claim 1, characterized in that, The method further includes: If the merchant's available virtual resources pass the verification, in response to the merchant's request to save the first delivery plan, the first delivery plan information is saved as a draft.

7. The method as described in claim 6, characterized in that, The method further includes: In response to the merchant's cancellation request for the first delivery plan, obtain the plan status of the first delivery plan; If the plan status is pending execution or pending submission, the first delivery plan will be cancelled. The "pending submission" status refers to the planning status of the first delivery plan after the first delivery plan information is saved as a draft; the "pending execution" status refers to the planning status of the first delivery plan after multiple first pre-orders are generated based on the first delivery plan information and before each first immediate order is generated based on each first pre-order.

8. The method as described in claim 7, characterized in that, The method further includes: In response to the merchant's edit request for the first delivery plan, the plan status of the first delivery plan is obtained; When the plan status is either pending execution or pending submission, the merchant's second delivery plan information is received; the second delivery plan information includes a second delivery time schedule and a second delivery list corresponding to the second delivery plan; the second delivery list includes multiple second list entries, each of which includes the merchant's second store identifier and the second delivery address of the second delivery object. Verify the second delivery plan information; If the second delivery plan information is verified, the second target virtual resources required to complete the second delivery plan are determined based on the second delivery list and the second delivery schedule. Verify the merchant's available virtual resources based on the second target virtual resources; If the merchant's available virtual resources pass the verification, in response to the merchant's request to execute the second delivery plan, the multiple first pre-orders are cancelled, and multiple second pre-orders are generated based on the second delivery plan information; Based on each of the second pre-orders, generate each of the second immediate orders to execute the dispatch process.

9. A method for managing delivery plans, characterized in that, Applied to merchant terminals, the method includes: Receive the merchant’s first delivery plan information; the first delivery plan information includes the first delivery list corresponding to the first delivery plan and the first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant’s first store identifier and the first delivery address of the first delivery object; The first delivery plan information is sent to the server so that the server can verify the first delivery plan information. If the first delivery plan information is verified, the first target virtual resource required to complete the first delivery plan is determined according to the first delivery list and the first delivery time arrangement. The available virtual resources of the merchant are verified according to the first target virtual resource. If the available virtual resources of the merchant are verified, the verification result is sent to the merchant terminal. Receive the verification pass result sent by the server; In response to the merchant's request to execute the first delivery plan, the execution request for the first delivery plan is sent to the server, so that the server generates multiple first pre-orders based on the first delivery plan information, and generates each first immediate order based on each first pre-order to execute the order dispatch process; the multiple first pre-orders can be cancelled; The verification of the first delivery plan information includes: Verify that the first store identifiers of each of the first list entries are consistent; If the first store identifiers of the first list entries are inconsistent, it is determined that the verification of the first delivery plan information fails.

10. A delivery planning and management system, characterized in that, The delivery planning and management system includes: merchant terminals, an order server, and a delivery server; wherein... The merchant terminal is used to receive the merchant's first delivery plan information and send the first delivery plan information to the order server; the first delivery plan information includes a first delivery list corresponding to the first delivery plan and a first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant's first store identifier and the first delivery address of the first delivery object. The order server is configured to receive the first delivery plan information sent by the merchant terminal, verify the first delivery plan information, and, if the first delivery plan information passes the verification, determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery time arrangement, verify the merchant's available virtual resources based on the first target virtual resource, and, if the merchant's available virtual resources pass the verification, send the verification result to the merchant terminal. The merchant terminal is also configured to receive the verification pass result sent by the order server, and in response to the merchant's execution request for the first delivery plan, send the execution request for the first delivery plan to the order server; The order server is further configured to generate multiple first pre-orders based on the first delivery plan information, generate multiple first instant orders based on each first pre-order, and send each first instant order to the delivery server; the multiple first pre-orders can be cancelled; The delivery server is used to receive each of the first instant orders and perform order dispatching processing for each of the first instant orders; The verification of the first delivery plan information includes: Verify that the first store identifiers of each of the first list entries are consistent; If the first store identifiers of the first list entries are inconsistent, it is determined that the verification of the first delivery plan information fails.

11. A delivery planning management device, characterized in that, The device includes: The receiving module is used to receive the merchant's first delivery plan information; the first delivery plan information includes a first delivery list corresponding to the first delivery plan and a first delivery time arrangement; the first delivery list includes multiple first list entries, and each first list entry includes the merchant's first store identifier and the first delivery address of the first delivery object. The first verification module is used to verify the first delivery plan information; The determination module is used to determine the first target virtual resource required to complete the first delivery plan based on the first delivery list and the first delivery time arrangement, provided that the first delivery plan information has been verified. The second verification module is used to verify the merchant's available virtual resources based on the first target virtual resources; The first generation module is configured to, in response to the merchant's execution request for the first delivery plan, generate multiple first pre-orders based on the first delivery plan information, provided that the merchant's available virtual resources have been verified as valid; the multiple first pre-orders are cancelable. The second generation module is used to generate each first instant order based on each of the first pre-orders to perform order dispatching; The verification of the first delivery plan information includes: Verify that the first store identifiers of each of the first list entries are consistent; If the first store identifiers of the first list entries are inconsistent, it is determined that the verification of the first delivery plan information fails.

12. An electronic device, characterized in that, include: A processor and a memory; the memory stores a computer program, and the processor executes the computer program to implement the method steps of any one of claims 1-8 or 9.

13. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions adapted for loading by a processor and executing the method steps as claimed in any one of claims 1-8 or 9.

Images