Logistics order settlement method, device, electronic device and readable storage medium

Abstract

Embodiments of the present invention provide a logistics order settlement method, apparatus, electronic device, and readable storage medium, relating to the field of logistics settlement technology. By configuring a rules engine that includes at least one correspondence between order types and settlement rules, the present invention obtains order data to be settled and the target order type corresponding to the order data. Based on the rules engine and the target order type, the target settlement rule corresponding to the order data is obtained. The order data is then settled according to the target settlement rule, significantly reducing the time required for order settlement and the cost of writing hard code for order settlement.

Description

Technical Field

[0001] The present invention relates to the field of logistics settlement technology, and in particular to a logistics order settlement method, device, electronic device and readable storage medium. Background Art

[0002] With the development of Internet technology, more and more e-commerce platforms have emerged. As the number of e-commerce platforms increases, the logistics industry has also developed rapidly.

[0003] At this stage, logistics orders need to go through various steps of generation, filling, and verification during settlement. In addition, there are various complex relationships between freight, various value-added services, and the products used. As a result, the logic of logistics orders becomes very complicated during settlement, and it needs to be implemented through a lot of complex code, which is time-consuming and costly. Summary of the Invention

[0004] Based on the above research, the present invention provides a logistics order settlement method, device, electronic device and readable storage medium, which can reduce the time consumption of order settlement and reduce the cost of writing hard code.

[0005] The embodiments of the present invention can be implemented through the following implementations:

[0006] In a first aspect, an embodiment of the present invention provides a logistics order settlement method, the method comprising:

[0007] Obtaining order data to be settled and the target order type corresponding to the order data;

[0008] Obtaining a target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type; wherein the rule engine includes at least one correspondence between an order type and a settlement rule;

[0009] The order data is settled according to the target settlement rule.

[0010] In an optional embodiment, obtaining the target settlement rule corresponding to the order data according to the preconfigured rule engine and the target order type includes:

[0011] Detect whether the target order type belongs to the return type;

[0012] If the target order type is a return type, detecting whether the order data includes a set value-added service;

[0013] If value-added services are included, the settlement rules corresponding to the value-added services are searched in the rule engine, and the settlement rules corresponding to the value-added services are set as the target settlement rules corresponding to the order data; wherein, the rule engine is set with at least one corresponding relationship between the value-added service and the settlement rule.

[0014] In an optional implementation manner, obtaining the order data to be settled includes:

[0015] Respond to the target business operation of the business interface and obtain the business event corresponding to the target business operation and the parameters of the business event;

[0016] The order data to be settled is obtained according to the business event and the parameters of the business event.

[0017] In an optional implementation manner, obtaining the target order type corresponding to the order data includes:

[0018] Obtaining parameters of the business event in the order data;

[0019] Matching the parameters of the business event with the business parameters in the business database to obtain target parameters that match the parameters of the business event;

[0020] The order type corresponding to the target parameter is obtained, and the order type corresponding to the target parameter is set as the target order type to which the order data belongs; wherein the business database includes a correspondence between at least one business parameter and an order type.

[0021] In an optional implementation manner, the settling the order data according to the target settlement rule includes:

[0022] Obtain the target field to be settled in the order data;

[0023] According to the target settlement rule, the target field is filled with data to settle the order data.

[0024] In an optional embodiment, before obtaining the target settlement rule corresponding to the order data based on the preconfigured rule engine and the target order type, the method includes:

[0025] In response to a configuration request for rule configuration, a rule file of the rule engine is configured according to the settlement rule in the configuration request and the order type corresponding to the settlement rule; wherein the rule file includes a correspondence between at least one order type and a settlement rule.

[0026] In an optional embodiment, obtaining the target settlement rule corresponding to the order data according to the preconfigured rule engine and the target order type includes:

[0027] Matching the target order type with the order type in the rule file of the rule engine, and searching whether there is an order type identical to the target order type in the rule file;

[0028] If it exists, the settlement rule corresponding to the target order type is obtained according to the correspondence between the order type and the settlement rule in the rule file, and the settlement rule corresponding to the target order type is set as the target settlement rule corresponding to the order data.

[0029] In a second aspect, an embodiment of the present invention provides a logistics order settlement device, the logistics order settlement device comprising:

[0030] A data acquisition module is used to obtain order data to be settled and the target order type corresponding to the order data;

[0031] a rule analysis module, configured to obtain a target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type; wherein the rule engine includes at least one correspondence between an order type and a settlement rule;

[0032] An order settlement module is used to settle the order data according to the target settlement rules.

[0033] In a third aspect, an embodiment of the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the logistics order settlement method described in any one of the aforementioned embodiments is implemented.

[0034] In a fourth aspect, an embodiment of the present invention provides a readable storage medium, which includes a computer program. When the computer program is running, it controls the electronic device where the readable storage medium is located to execute the logistics order settlement method described in any of the aforementioned embodiments.

[0035] The logistics order settlement method, device, electronic device and readable storage medium provided by the embodiments of the present invention configure a rule engine that includes a correspondence between at least one order type and a settlement rule. After obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rule corresponding to the order data can be obtained according to the rule engine and the target order type, and the order data can be settled according to the target settlement rule, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard code during order settlement. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The technical solutions and other beneficial effects of the present invention will be made apparent by describing in detail the specific embodiments of the present invention in conjunction with the accompanying drawings.

[0037] Figure 1 A schematic structural diagram of an electronic device provided by an embodiment of the present invention.

[0038] Figure 2 A flow chart of a logistics order settlement method provided in an embodiment of the present invention.

[0039] Figure 3 A schematic diagram of the principle of the rule engine provided by an embodiment of the present invention.

[0040] Figure 4 A block diagram of a logistics order settlement device provided by an embodiment of the present invention.

[0041] Icon: 100 - electronic device; 10 - logistics order settlement device; 11 - data acquisition module; 12 - rule analysis module; 13 - order settlement module; 20 - memory; 30 - processor; 40 - communication unit; 50 - display unit. DETAILED DESCRIPTION

[0042] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0043] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise" and the like, indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the said features. In the description of the present invention, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0044] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed connections, detachable connections, or integral connections; mechanical connections, electrical connections, or mutual communication; direct connections or indirect connections through an intermediate medium; and internal communication between two components or interaction between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0045] In the present invention, unless otherwise expressly specified or limited, a first feature being "above" or "below" a second feature may include the first and second features being in direct contact, or may include the first and second features being in contact not directly but through another feature between them. Furthermore, a first feature being "above," "above," and "above" a second feature may include the first feature being directly above or obliquely above the second feature, or may simply mean that the first feature is higher in level than the second feature. A first feature being "below," "below," and "below" a second feature may include the first feature being directly below or obliquely below the second feature, or may simply mean that the first feature is lower in level than the second feature.

[0046] The disclosure below provides many different embodiments or examples for realizing different structures of the present invention. In order to simplify the disclosure of the present invention, the components and settings of specific examples are described below. Of course, they are merely examples and are not intended to limit the present invention. In addition, the present invention may repeat reference numbers and / or reference letters in different examples. Such repetition is for the purpose of simplicity and clarity and does not in itself indicate the relationship between the various embodiments and / or settings discussed. In addition, the present invention provides examples of various specific processes and materials, but those skilled in the art will recognize the application of other processes and / or the use of other materials.

[0047] As mentioned in the background, current logistics order settlement processes require generation, filling, and verification. Furthermore, complex relationships exist between freight, various value-added services, and used products. This results in a complex code implementation during logistics order settlement, which is time-consuming and costly. If customers require personalized settlement, the logic becomes extremely complex and difficult to maintain.

[0048] Based on the above research, an embodiment of the present invention provides a logistics order settlement method, device, electronic device and readable storage medium. By configuring a rule engine that includes a correspondence between at least one order type and a settlement rule, after obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rule corresponding to the order data can be obtained according to the rule engine and the target order type, and the order data can be settled according to the target settlement rule, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard code during order settlement.

[0049] See also Figure 1 , Figure 1 This is a schematic diagram of the structure of the electronic device provided in this embodiment. Figure 1 As shown, electronic device 100 includes a logistics order settlement device 10, a memory 20, a processor 30, a communication unit 40, and a display unit 50. The memory 20, processor 30, communication unit 40, and display unit 50 are electrically connected to each other directly or indirectly to enable signal transmission or interaction. For example, these components can be electrically connected to each other via one or more communication buses or signal lines.

[0050] In this embodiment, the logistics order settlement device 10 includes at least one software functional module, which may be stored in the form of software or firmware in the memory 20. The processor 30 is configured to execute the executable module stored in the memory 20 (e.g., the software functional module or computer program included in the logistics order settlement device 10). When the electronic device 100 is running, the processor 30 communicates with the memory 20 via a bus, and the processor 30 executes the executable module to implement the logistics order settlement method described in this embodiment.

[0051] Among them, the memory 20 can be, but is not limited to, random access memory (RAM), read only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0052] The processor 30 is used to perform one or more functions described in this embodiment. In some embodiments, the processor 30 may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). By way of example only, the processor 30 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC) or a microprocessor, or any combination thereof.

[0053] For ease of explanation, only one processor is described in the electronic device 100. However, it should be noted that the electronic device 100 in this embodiment may also include multiple processors, so the steps performed by one processor described in this embodiment may also be performed jointly or individually by multiple processors. For example, if the processor of the electronic device performs step A and step B, it should be understood that step A and step B may also be performed jointly by two different processors or individually in one processor. For example, the processor performs step A and the second processor performs step B, or the processor and the second processor perform steps A and B together.

[0054] In this embodiment, the process definition method disclosed in any implementation manner can be applied to the processor 30 or implemented by the processor 30.

[0055] The communication unit 40 is used to establish a communication connection between the electronic device 100 and other devices through a network, and to send and receive data through the network.

[0056] In some embodiments, the network can be any type of wired or wireless network, or a combination thereof. By way of example only, the network can include a wired network, a wireless network, a fiber optic network, a telecommunications network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a wide area network (WAN), a public switched telephone network (PSTN), a Bluetooth network, a ZigBee network, a near field communication (NFC) network, or any combination thereof.

[0057] In this embodiment, the display unit 40 provides an interactive interface (e.g., a user operation interface) between the electronic device 100 and the user for displaying page information. In this embodiment, the display unit 50 may be a liquid crystal display or a touch display. If it is a touch display, it may be a capacitive touch screen or a resistive touch screen that supports single-point and multi-touch operations. Supporting single-point and multi-touch operations means that the touch display can sense touch operations generated from one or more locations on the touch display and transmit the sensed touch operations to the processor 30 for calculation and processing.

[0058] To facilitate interaction between the user and the display unit 50, in this embodiment, the electronic device 100 may further include an input / output unit, which is used to provide input data to the user to enable interaction between the user and the electronic device 100. The input / output unit may be, but is not limited to, a mouse and a keyboard.

[0059] In some embodiments, the electronic device 100 may include 1 or N display units 50 , where N is a positive integer greater than 1.

[0060] In this embodiment, the electronic device may be a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), a physical server, or the like. This embodiment does not impose any restrictions on the specific type of the electronic device.

[0061] Understandably, Figure 1 The structure shown is for reference only. Figure 1More or fewer components than shown, or with Figure 1 Different configurations shown. Figure 1 The components shown may be implemented in hardware, software, or a combination thereof.

[0062] based on Figure 1 This embodiment provides a logistics order settlement method. Figure 1 The electronic device shown in the figure is executed, and the steps of the logistics order settlement method provided by this embodiment are described in detail below. Figure 2 The logistics order settlement method provided in this embodiment includes steps S101 to S103.

[0063] Step S101: Obtain the order data to be settled and the target order type corresponding to the order data. The order data may be sent from other terminals to the electronic device. When the user places an order on the terminal device, the terminal device generates the order data and then sends the order data to the electronic device. For example, when the user initiates shipping on the terminal device, the terminal device generates the shipping order data and then sends the order data to the electronic device. For another example, when the user initiates a return on the terminal device, the terminal device generates the return order data and then sends the order data to the electronic device. A return order refers to a return order initiated by a user to an e-commerce merchant after purchasing goods from the e-commerce merchant.

[0064] In this embodiment, the order data received by the electronic device may include the time when the order was generated, the type of order generated, the type of goods corresponding to the order, the weight of the goods, the user information corresponding to the order (such as mobile phone number, name, etc.), etc. For example, when a user initiates shipping on a terminal device, the terminal device generates order data for shipping, and the order data includes the user information of the shipping user, the user information of the receiving user, the time when the order was generated, the type of order (shipping), the type of goods to be shipped, and the weight of the goods, etc. For another example, when a user initiates a return on a terminal device, the terminal device generates order data for the return, and the order data includes the user information of the returning user, the user information of the merchant, the time when the order was generated, the type of order (return), the type of goods to be returned, and the weight of the goods, etc.

[0065] Order data can also be generated by responding to business operations performed by the user on a business interface. The electronic device can provide a business interface to the user via a display unit. When the user performs a business operation to settle an order in the business interface, the electronic device generates order data to be settled in response to the business operation. The generated order data may include specific data of the business operation and identification information of the business operation. The specific data of the business operation may be the specific operation data performed by the user on the business interface, such as the content filled in, the content modified, etc. The identification information of the business operation represents the identification information of the business operation. Each business operation has unique identification information to distinguish it from other business operations.

[0066] It should be noted that, in this embodiment, the user may be a consumer user or a merchant user, and the specific type of user may be determined according to the specific usage scenario.

[0067] After receiving the order data, the electronic device analyzes the order data to obtain the target order type corresponding to the order data. In an optional embodiment, the terminal device can provide the user with order type options, including return and shipment types. When the user needs to ship goods, he can place an order on the terminal device and select the shipment option. In this way, the order data generated by the terminal device can include the order type field for shipment. When the user needs to return goods, he can place an order on the terminal device and select the return option. In this way, the order data generated by the terminal device can include the order type field for return. Based on this, after receiving the order data, the electronic device can analyze the order data to extract the data corresponding to the order type field, and obtain the target order type corresponding to the order data based on the data corresponding to the order type field.

[0068] When analyzing order data and extracting data corresponding to the order type field, a pre-trained recognition model can be used to analyze and process the order data, extract data corresponding to the order type field in the order data, classify the data corresponding to the order type field, and output the target order type corresponding to the order data. It is understood that the recognition model can be trained using supervised or unsupervised training methods for any network capable of recognition and classification (such as a convolutional neural network, a deep convolutional network, a residual network, etc.).

[0069] Alternatively, the order data may be analyzed and processed using a preset character recognition algorithm, such as optical character recognition (OCR), to extract the data corresponding to the order type field in the order data, and then compare the extracted data with the field data in a pre-configured type database to obtain the target order type corresponding to the order data. The type database stores field data and the order type corresponding to the field data. When comparing the extracted data with the field data in the pre-configured type database, the target field data in the type database that is identical to the extracted data is searched, and then the order type corresponding to the target field data is set as the target order type. Understandably, if the same target field data is not found, an error message is displayed to facilitate the user to manually enter the order type.

[0070] In an optional embodiment, the target order type corresponding to the order data can also be sent by the terminal device to the electronic device. When the terminal device sends the order data, the type of the sent order data can also be marked. When the electronic device receives the order data, it can obtain the target order type corresponding to the order data.

[0071] Step S102: Obtain target settlement rules corresponding to the order data according to the pre-configured rule engine and target order type.

[0072] Among them, the rule engine includes at least one correspondence between order types and settlement rules. After obtaining the order data and the target order type corresponding to the order data, the target order type corresponding to the order data can be matched with the order type in the rule engine to obtain the target settlement rule corresponding to the order data.

[0073] A rule engine is a component embedded within an application. It separates business settlement rules from application code, simplifying the implementation of complex business settlement rules. Examples of rule engines include, but are not limited to, the Drools rule engine, the Aviator expression evaluation engine, the MVEL expression parser, and the EasyRules rule engine.

[0074] Optionally, in this embodiment, the drools rule engine and the Rete algorithm can be used to evaluate the rules. Figure 3 As shown in the figure, the matching engine in the rule engine can be called the inference engine, which includes the pattern matcher and the agenda. The rules accessed by the inference engine are called production memory, and the operation data matched by the inference engine is called working memory.

[0075] A rule is an inference statement consisting of a condition and a conclusion, typically expressed as if...then. The if portion of a rule is called the left-hand side (LHS), and the then portion is called the right-hand side (RHS). A pattern refers to the condition of an if statement. This condition may be composed of several smaller conditions, while a pattern is the smallest atomic condition that cannot be further divided.

[0076] Figure 3 Facts in the rule engine are objects asserted from the application into the working memory, representing the application's data. Rules and facts are input parameters accepted by the rule engine. The Pattern Matcher finds matching rules based on the facts. After finding a matching rule, the Pattern Matcher passes the matching rule and data to the Agenda, which manages the execution order of the rules selected by the Pattern Matcher.

[0077] In this embodiment, facts can represent the acquired order data and / or the target order type corresponding to the order data, and rules can represent the formulated settlement rules. After obtaining the order data and the target order type corresponding to the order data, the rule engine can search for the target settlement rules that match the order data based on the target order type corresponding to the order data.

[0078] Step S103: settle the order data according to the target settlement rules.

[0079] Among them, after obtaining the target settlement rules corresponding to the order data, the order data can be settled according to the target settlement rules.

[0080] In an optional embodiment, the electronic device is configured with an execution engine for executing specific operations according to the rules output by the agenda. After obtaining the target settlement rules corresponding to the order data, the execution engine settles the order data according to the target settlement rules.

[0081] The logistics order settlement method provided in this embodiment configures a rule engine that includes a correspondence between at least one order type and a settlement rule. After obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rule corresponding to the order data can be obtained according to the rule engine and the target order type. The order data is settled according to the target settlement rule, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard code during order settlement.

[0082] Since, in actual applications, users can implement logistics settlement by performing settlement operations on the provided business interface, in this embodiment, the step of obtaining the order data to be settled may further include:

[0083] Respond to the target business operation of the business interface and obtain the business event corresponding to the target business operation and the parameters of the business event.

[0084] According to the business event and its parameters, the order data to be settled is obtained.

[0085] Among them, the electronic device can provide a business interface to the user through the display unit, and the business interface includes a variety of business operation buttons. When the user needs to perform a certain business operation, he can operate the business operation button corresponding to the business operation in the business interface. The electronic device executes the corresponding business by responding to the user's operation.

[0086] In this embodiment, the target business operations of the business interface represent business operations for order settlement, including, but not limited to, batch modification of orders, order correction, modification of old and new orders (including crossover, duplication, forwarding and return, etc.), and unreviewed interface and other business operations.

[0087] When a user performs a target business operation in the business interface, the electronic device responds to the target business operation in the business interface by calling an interface, obtaining the business event corresponding to the target business operation and its parameters, and then obtaining the order data to be settled based on the business event and its parameters. The business event parameters include the corresponding identification information and the specific content of the business event, and the generated order data includes the corresponding identification information and the specific content of the business event.

[0088] In this embodiment, the identification information corresponding to the business event is used to distinguish it from other business events. The identification information can be at least one of letters, numbers, words, and symbols.

[0089] For example, when a user performs an order modification operation on a business interface, the electronic device can obtain the business event corresponding to the business operation as an order modification by calling the interface. The business event parameters include identification information corresponding to the order modification and the specific modification content. Then, the electronic device generates the order data corresponding to the business operation based on the business event and the business event parameters. It is understandable that the generated order data includes the identification information of the order modification and the specific modification content.

[0090] It can be understood that in this embodiment, the user may be an e-commerce merchant user or a consumer user who purchases e-commerce products.

[0091] After obtaining the order data, the order data can be analyzed to obtain the target order type corresponding to the order data.

[0092] In this embodiment, for order data sent from other terminals to the electronic device, the target order type corresponding to the order data can be obtained by analyzing the order data, extracting the data corresponding to the order type field, and comparing the data corresponding to the order type field with a pre-established order type data table (order type database). For example, if the order type field is set to product_Code, after receiving the order data, the electronic device analyzes the order data and obtains the data corresponding to product_Code as SE0131. After comparing SE0131 with the pre-established order type data table, it is obtained that SE0131 indicates an e-commerce return, and the target order type corresponding to the order data can be obtained as a return type.

[0093] In this embodiment, for the order data corresponding to the business operation in the business interface, the target order type corresponding to the order data can be obtained based on the parameters of the business event. Optionally, this can be achieved by the following steps:

[0094] Get the parameters of the business event in the order data.

[0095] The parameters of the business event are matched with the business parameters in the business database to obtain target parameters that match the parameters of the business event.

[0096] The order type corresponding to the target parameter is obtained, and the order type corresponding to the target parameter is set as the target order type to which the order data belongs; wherein the business database includes at least one correspondence between a business parameter and an order type.

[0097] After obtaining the order data corresponding to the business operation, the order data is analyzed to extract the parameters of the business event in the order data, and then the parameters of the business event are matched with the business parameters in the business database to obtain target parameters that match the parameters of the business event.

[0098] In this embodiment, the parameters of a business event include identification information corresponding to the business event and the specific content of the business event. After obtaining the parameters of the business event, the identification information corresponding to the business event is matched with the business parameters in the business database to check whether there is a business parameter identical to the identification information of the business event. If so, the business parameter is used as the target parameter. If not, the user is prompted to determine whether an operation has been made incorrectly and the business interface is redisplayed to the user, allowing the user to perform the business operation again on the business interface.

[0099] In this embodiment, the business database contains a correspondence between at least one business parameter and an order type. Therefore, after obtaining the target parameter, the order type corresponding to the target parameter can be obtained based on the correspondence between the business parameter and the order type, and the order type corresponding to the target parameter can be set as the target order type to which the order data belongs. For example, for a business event of order modification, the identification information of the business event, i.e., the identification information of the order modification, can be matched with the business parameters in the business database to obtain a target business parameter that is the same as the identification information of the order modification. Then, based on the correspondence between the business parameter and the order type, it can be obtained that the order type corresponding to the target business parameter is a return type. After obtaining that the order type corresponding to the target business parameter is a return type, the order type of the order data generated by the order modification can be set to a return type, thereby obtaining the target order type corresponding to the order data.

[0100] The logistics order settlement method provided in this embodiment utilizes a rules engine configuration. For settlement operations on the business interface, after obtaining order data and its type in response to the business operation, the method also determines the corresponding target settlement rule based on the rules engine and the order type, and then performs order settlement based on the target settlement rule. This significantly reduces the time required for order settlement operations on the business interface and reduces the cost of writing hard-coded code for order settlement.

[0101] In this embodiment, after obtaining the target order type corresponding to the order data, the target order type corresponding to the order data can be matched with the order type in the rule engine to obtain the target settlement rule corresponding to the order data, and the order data can be settled based on the target settlement rule.

[0102] Optionally, in this embodiment, according to the target settlement rule, the step of settling the order data may include:

[0103] Get the target field to be settled in the order data.

[0104] According to the target settlement rules, fill the target fields with data to settle the order data.

[0105] After obtaining the target settlement rules corresponding to the order data, the order data can be analyzed to extract the target fields to be settled in the order data. The target settlement rules are then executed and, based on the target settlement rules, the target fields are populated with data to settle the order data. For example, the target fields to be settled in the order data may include packaging fees, payment location, monthly settlement card number, payment method, and payment employee number. After obtaining the target settlement rules, the target fields to be settled in the order data are populated with data based on the target settlement rules. The result is that the packaging fee is paid by post and settled in cash, the payment location is the original shipping location of the waybill, the monthly settlement card number is left blank, the payment method change is left blank, and the payment employee number is the receiving employee number.

[0106] Optionally, in this embodiment, if the target field to be settled in the order data is not extracted, an error prompt can be given so that the user can manually enter data to settle the order. The error prompt can also be stored in the log information so that subsequent developers can locate and solve the problem.

[0107] The logistics order settlement method provided in this embodiment introduces a rule engine. After obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rules corresponding to the order data can be obtained according to the rule engine and the target order type. The order data is settled according to the target settlement rules, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard codes during order settlement.

[0108] In this embodiment, the rule engine is applicable to the following scenarios: 1. Complex business problems with no obvious existing solutions, or where the fundamental business problems are not thoroughly understood. For some new businesses, development is often tentative and subject to frequent changes. 2. Volatile requirements and the need for frequent updates, such as rules for events, where the content of an event may need to be changed monthly. This embodiment separates the settlement rules for businesses from the application code by configuring the rule engine, simplifying the implementation of complex settlement rules. It also supports dynamic modification of settlement rules, enabling rapid response to rule changes caused by changing requirements.

[0109] To reduce time consumption and improve reliability, in this embodiment, by formulating a rule file, when modifying the settlement rules of a business, only the rule file needs to be updated. Based on this, in this embodiment, before obtaining the target settlement rules corresponding to the order data based on the pre-configured rule engine and the target order type, the logistics order settlement method provided by this embodiment may also include:

[0110] In response to a configuration request for rule configuration, a rule file of the rule engine is configured according to the settlement rule in the configuration request and the order type corresponding to the settlement rule; wherein the rule file includes a correspondence between at least one order type and a settlement rule.

[0111] Optionally, for ease of operation, when configuring settlement rules, business personnel can package the settlement rules to be configured and the order types corresponding to the settlement rules, and send them to the electronic device in the form of a configuration request. After receiving the configuration request, the electronic device responds to the configuration request and configures the settlement rules in the configuration request and the order types corresponding to the settlement rules in the rule file of the rule engine.

[0112] Optionally, when configuring settlement rules, the business personnel can also fill in the configured settlement rules and the order type corresponding to the settlement rules on the operation interface. The electronic device configures the filled-in settlement rules and the order type corresponding to the settlement rules in the rule file of the rule engine by responding to the business personnel's operations on the operation interface.

[0113] After the rule file is configured, the rule engine can achieve rule matching by reading the content in the rule file.

[0114] Accordingly, in this embodiment, by configuring the rule file, when modifying the settlement rules, only the rule file needs to be updated, which reduces time consumption and improves reliability. Therefore, after configuring the rule file of the rule engine, the logistics order settlement method provided by this embodiment may also include:

[0115] In response to an update request for rule update, the rule file of the rule engine is updated according to the settlement rule in the update request and the order type corresponding to the settlement rule.

[0116] Among them, when updating the settlement rules, the business personnel can package the settlement rules to be updated and the order types corresponding to the settlement rules, and send them to the electronic device in the form of an update request. After receiving the update request, the electronic device responds to the update request and updates the rule file of the rule engine according to the settlement rules in the update request and the order types corresponding to the settlement rules.

[0117] Similarly, when updating the settlement rules, the business personnel can also fill in the settlement rules to be updated and the order type corresponding to the settlement rules on the operation interface. The electronic device responds to the business personnel's operations on the operation interface and updates the rule file of the rule engine according to the filled-in settlement rules and the order type corresponding to the settlement rules.

[0118] When updating the rule file of the rule engine according to the settlement rules in the update request and the order type corresponding to the settlement rules, the content in the rule file can be modified according to the settlement rules in the update request and the order type corresponding to the settlement rules, or the content in the rule file can be replaced according to the settlement rules in the update request and the order type corresponding to the settlement rules.

[0119] In an optional implementation, in order to improve reliability, a first rule file can also be configured locally, and the rule file of the rule engine can be configured and updated according to the content of the first rule file. Optionally, this can be achieved by the following steps:

[0120] In response to a configuration request for rule configuration, the settlement rule in the configuration request and the order type corresponding to the settlement rule are added to a preset first rule file.

[0121] According to the first rule file, a second rule file of the rule engine is configured; wherein the second rule file includes a correspondence between at least one order type and a settlement rule.

[0122] The first rule file is a locally stored rule file, and the second rule file is a rule file read by the rule engine. When configuring the second rule file of the rule engine based on the first rule file, that is, configuring the content of the second rule file based on the content included in the first rule file, the content in the second rule file can be configured to be the same as the content in the first rule file, or partial content can be selected from the first rule file and the second rule file can be configured based on the selected content. Therefore, in this embodiment, the first rule file can include the same content as the second rule file, and can also include rule content not included in the second rule file.

[0123] After the second rule file is configured, the rule engine can implement rule matching by reading the content in the second rule file.

[0124] Accordingly, when updating the settlement rules, you can respond to the update request for the rule update, update the first rule file according to the settlement rule in the update request and the order type corresponding to the settlement rule, and then replace the second rule file of the rule engine as a whole based on the first rule file. There is no need to filter the content in the rule file in the rule engine, nor to package and publish it. You can complete the rule update by directly restarting.

[0125] Because the business rules in the logistics industry are changeable and complex, before the introduction of the rule engine, changes in requirements required code writing and modification, reorganization and testing of processes, which was time-consuming and could take 3-5 days in total. However, after the introduction of the rule engine, the logistics order settlement method provided in this embodiment only requires modifying the rule file and testing the new process to respond to changes in requirements, greatly shortening the time consumption to as little as 1 day and enabling rapid response to changes.

[0126] The rule engine is currently mainly used in scenarios such as risk control model configuration, user points configuration (such as changes in points caused by daily operations), and simple offline calculations (such as statistics of various types of relatively small data volumes). It is responsible for the calculation of some rules. This embodiment introduces a rule engine in the logistics industry to settle logistics orders, which can quickly respond to changes in logistics business rules and improve the efficiency of logistics order settlement.

[0127] In this embodiment, after configuring the rule file of the rule engine, after obtaining the order data and the target order type of the order data, the target settlement rule corresponding to the order data can be obtained according to the rule file of the rule engine. Optionally, this can be achieved by the following steps:

[0128] The target order type is matched with the order type in the rule file of the rule engine, and an order type identical to the target order type is found in the rule file.

[0129] If it exists, the settlement rule corresponding to the target order type is obtained according to the correspondence between the order type and the settlement rule in the rule file, and the settlement rule corresponding to the target order type is set as the target settlement rule corresponding to the order data.

[0130] After obtaining the target order type corresponding to the order data, the target order type is matched against the order types in the rule engine's rule file, searching the rule file for an order type identical to the target order type. If an order type identical to the target order type exists, the corresponding settlement rule is determined based on the correspondence between order types and settlement rules in the rule file, thereby obtaining the settlement rule corresponding to the target order type. Once the settlement rule corresponding to the target order type is obtained, it is set as the target settlement rule corresponding to the order data.

[0131] In this embodiment, if an order type identical to the target order type is not matched in the rule file, it is determined that the target order type is not configured with a settlement rule, and the order data does not have a corresponding settlement rule. After determining that the order data does not have a corresponding settlement rule, the business personnel can be notified so that the business personnel can settle the order data.

[0132] The logistics order settlement method provided in this embodiment separates business settlement rules from application code by configuring a rule engine, making the implementation of complex business settlement rules simpler and supporting dynamic modification of business settlement rules, thereby quickly responding to rule changes caused by changes in demand.

[0133] Given that the current e-commerce platform's logistics business volume is large, the reverse logistics business generated is also large, that is, the return business volume is also large. In order to realize the logistics order settlement of returned products, the logistics order settlement method provided in this embodiment may further include:

[0134] Check whether the target order type is a return type.

[0135] If the target order type is a return type, check whether the order data includes the set value-added services.

[0136] If value-added services are included, the settlement rules corresponding to the value-added services are searched in the rule engine, and the settlement rules corresponding to the value-added services are set as the target settlement rules corresponding to the order data; wherein, the rule engine is set with at least one corresponding relationship between the value-added service and the settlement rule.

[0137] Among them, after obtaining the target order type corresponding to the order data, it is possible to detect whether the target order type is a return type. In this embodiment, when detecting whether the target order type is a return type, it is possible to detect whether the data corresponding to the target order type is return type data. If it is return type data, then the target order type is determined to be a return type. For example, the order type field is set to product_Code. After receiving the order data, the electronic device analyzes the order data and obtains the data corresponding to product_Code as SE0131. Among them, SE0131 is set to indicate an e-commerce return, and then it can be obtained that the target order type corresponding to the order data is a return type.

[0138] After determining that the target order type is a return type, the order data is checked to see if it includes the set value-added services. Optionally, in this embodiment, for return orders, the set value-added services may include packaging fees, overweight fees, insurance, original order return, special safety, and inspection services.

[0139] When checking whether the order data includes the specified value-added services, the order data can be checked for fields containing these value-added services, such as the service code and fee code corresponding to the value-added services. If so, the order data is determined to include the value-added services. For example, the value-added service code for packaging charges can be IN67, the value-added service code for overweight charges can be OS09, the value-added service code for insurance can be IN02, the value-added service code for original order returns can be IN101, the value-added service code for special safety can be IN21, and the value-added service code for inspection can be IN52. If the order data is found to include the value-added service code OS09, the order data is determined to include the overweight charge value-added service. If the order data is found to include the value-added service code IN67, the order data is determined to include the packaging charge value-added service. For another example, the fee code corresponding to packaging charges may be 67, the fee code corresponding to overweight charges may be 134, the fee code corresponding to insurance may be 3, the fee code corresponding to original order return may be 93, the fee code corresponding to special safety may be 23, and the fee code corresponding to inspection may be 52. If it is detected that the order data includes the fee code 134, it is determined that the order data includes the overweight fee value-added service. If it is detected that the order data includes the fee code 67, it is determined that the order data includes the packaging fee value-added service.

[0140] In this embodiment, the rules engine can also configure the settlement rules corresponding to each value-added service. Therefore, after detecting that the order data includes a specified value-added service, the settlement rule corresponding to the value-added service can be searched and then set as the target settlement rule corresponding to the order data. For example, if the order data includes a packaging fee value-added service, the rules engine can search for the settlement rule corresponding to the packaging fee value-added service and then set the settlement rule corresponding to the packaging fee value-added service as the target settlement rule corresponding to the order data.

[0141] It can be understood that in this embodiment, when configuring the settlement rules corresponding to each value-added service, it is also possible to configure the rule file of the rule engine by responding to the configuration request of the rule configuration, according to the settlement rules in the configuration request and the value-added service corresponding to the settlement rule. After the rule file is configured, the rule engine can achieve rule matching by reading the content in the rule file.

[0142] In this embodiment, after finding the settlement rules corresponding to the value-added service in the rule engine, the order data can be settled according to the settlement rules corresponding to the value-added service. Specifically, the target fields to be settled in the order data are populated with data according to the settlement rules corresponding to the value-added service to achieve settlement of the order data. For example, the target fields to be settled in the order data may include packaging fee, payment location, monthly settlement card number, payment method, payment employee number, etc. When the value-added service including packaging fee is detected in the order data, the target fields to be settled in the order data are populated with data according to the settlement rules corresponding to the value-added service. The result is that the packaging fee is paid by post and settled in cash, the payment location is the original shipping location of the waybill, the monthly settlement card number is left blank, the payment method change is left blank, and the payment employee number is the receiving employee number.

[0143] To provide personalized service and settlement for each customer (such as an e-commerce merchant), in this embodiment, the rules engine can also configure settlement rules corresponding to each customer. After obtaining order data, the rule engine detects the customer access code in the order data, searches for the corresponding settlement rule based on the customer access code, and then settles the order data based on the settlement rule corresponding to the customer access code. For example, if the customer access code (client code) in the order data is detected as "MYJFFC", the corresponding settlement rule is searched based on "MYJFFC", and the order data is settled based on the found settlement rule. In this way, personalized settlement can be achieved for each customer, with simple logic and easy maintenance.

[0144] In an optional implementation, in order to improve personalized services, in this embodiment, personalized settlement rules can also be formulated for each customer's return order. The correspondence between the customer access code, order type, and value-added services and settlement rules is configured in the rule engine. In this way, personalized settlement can be achieved for each customer. For example, when the customer access code in the order data is MYJFFC, that is, (client Code = "MYJFFC"), the product type is e-commerce return, that is, (productCode = "SE0131"), and the packaging fee value-added service is included, then when the settlement rules are found and the order data is settled according to the settlement rules, the corresponding packaging fee can be obtained as postage and current payment, the payment location is the original shipping location of the waybill, the monthly settlement card number is set to blank, the payment method change is set to blank, and the payment employee number is the receiving employee number.

[0145] The logistics order settlement method provided in this embodiment completes the reverse logistics support of the e-commerce platform by configuring the rule engine, separates the business settlement rules from the application code, simplifies the implementation of complex business settlement rules, and supports dynamic modification of business settlement rules, thereby quickly responding to rule changes caused by changes in demand.

[0146] The logistics order settlement method provided in this embodiment improves maintainability by configuring a rules engine, reducing the cost and risk of hard-coding business settlement rules. Before the rule engine was introduced, establishing and implementing business settlement rules required at least 30-100 lines of code. However, with the introduction of the rules engine in this embodiment, a single business settlement rule can be written in just 10 lines.

[0147] Based on the same invention concept, please refer to Figure 4 This embodiment also provides a logistics order settlement device 10, which is used Figure 1 The electronic equipment shown, such as Figure 4 As shown, the logistics order settlement device 10 may include a data acquisition module 11 , a rule analysis module 12 and an order settlement module 13 .

[0148] The data acquisition module 11 is used to obtain order data to be settled and the target order type corresponding to the order data. The rule analysis module 12 is used to obtain the target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type. The rule engine includes at least one correspondence between order types and settlement rules.

[0149] The order settlement module 13 is used to settle the order data according to the target settlement rules.

[0150] In an optional embodiment, the rule analysis module 12 is used to:

[0151] Check whether the target order type is a return type.

[0152] If the target order type is a return type, check whether the order data includes the set value-added services.

[0153] If value-added services are included, the settlement rules corresponding to the value-added services are searched in the rule engine, and the settlement rules corresponding to the value-added services are set as the target settlement rules corresponding to the order data; wherein, the rule engine is set with at least one corresponding relationship between the value-added service and the settlement rule.

[0154] In an optional embodiment, the data acquisition module 11 is used to:

[0155] Respond to the target business operation of the business interface and obtain the business event corresponding to the target business operation and the parameters of the business event.

[0156] According to the business event and its parameters, the order data to be settled is obtained.

[0157] In an optional embodiment, the data acquisition module 11 is used to:

[0158] Get the parameters of the business event in the order data.

[0159] The parameters of the business event are matched with the business parameters in the business database to obtain target parameters that match the parameters of the business event.

[0160] The order type corresponding to the target parameter is obtained, and the order type corresponding to the target parameter is set as the target order type to which the order data belongs; wherein the business database includes at least one correspondence between a business parameter and an order type.

[0161] In an optional embodiment, the order settlement module 13 is used to:

[0162] Get the target field to be settled in the order data.

[0163] According to the target settlement rules, fill the target fields with data to settle the order data.

[0164] In an optional embodiment, the logistics order settlement device 10 may further include a rule configuration module. Before obtaining the target settlement rule corresponding to the order data based on the pre-configured rule engine and the target order type, the rule configuration module is configured to:

[0165] In response to a configuration request for rule configuration, a rule file of the rule engine is configured according to the settlement rule in the configuration request and the order type corresponding to the settlement rule; wherein the rule file includes a correspondence between at least one order type and a settlement rule.

[0166] In an optional embodiment, the rule analysis module 12 is used to:

[0167] The target order type is matched with the order type in the rule file of the rule engine, and an order type identical to the target order type is found in the rule file.

[0168] If it exists, the settlement rule corresponding to the target order type is obtained according to the correspondence between the order type and the settlement rule in the rule file, and the settlement rule corresponding to the target order type is set as the target settlement rule corresponding to the order data.

[0169] The logistics order settlement device provided in this embodiment is configured with a rule engine that includes a correspondence between at least one order type and a settlement rule. After obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rule corresponding to the order data can be obtained according to the rule engine and the target order type, and the order data can be settled according to the target settlement rule, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard code during order settlement.

[0170] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method, and will not be described in detail here.

[0171] Based on the above, this embodiment further provides a readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the logistics order settlement method described in any of the aforementioned embodiments is implemented.

[0172] The readable storage medium may be, but is not limited to, a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and other media that can store program codes.

[0173] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the readable storage medium described above can refer to the corresponding process in the aforementioned method, and will not be elaborated here.

[0174] In summary, the logistics order settlement method, device, electronic device and readable storage medium provided by the embodiments of the present invention, by configuring a rule engine that includes a correspondence between at least one order type and a settlement rule, after obtaining the order data to be settled and the target order type corresponding to the order data, the target settlement rule corresponding to the order data can be obtained according to the rule engine and the target order type, and the order data can be settled according to the target settlement rule, which greatly reduces the time consumption of order settlement and reduces the cost of writing hard code during order settlement.

[0175] In the several implementations provided in the embodiments of the present invention, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device and method implementations described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions, and operations of the devices, methods, and computer program products according to multiple implementations of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or part of a code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0176] In addition, the functional modules in the embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0177] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, electronic device, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk. It should be noted that, in this article, the terms "include", "comprising" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements inherent to such a process, method, article or device. Without further constraints, an element defined by the phrase "comprises a..." does not preclude the existence of additional identical elements in the process, method, article or apparatus that includes the element.

[0178] The above descriptions are merely various embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be readily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A logistics order settlement method, characterized in that: The method comprises: Obtaining order data to be settled and the target order type corresponding to the order data; Obtaining a target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type; wherein the rule engine includes at least one correspondence between an order type and a settlement rule; Settling the order data according to the target settlement rules; Wherein, obtaining the target settlement rule corresponding to the order data according to the pre-configured rule engine and the target order type includes: Detect whether the target order type belongs to the return type; If the target order type is a return type, detecting whether the order data includes a set value-added service; If a value-added service is included, searching the rule engine for a settlement rule corresponding to the value-added service and setting the settlement rule corresponding to the value-added service as the target settlement rule corresponding to the order data; wherein the rule engine is configured with at least one correspondence between a value-added service and a settlement rule; and the rule engine is also configured with a correspondence between a customer access code and a settlement rule; The settling of the order data according to the target settlement rule includes: Obtaining a target field to be settled in the order data; the value-added service is a second-level service under a first-level item of the target field; According to the target settlement rule, the target field is filled with data to settle the order data.

2. The logistics order settlement method according to claim 1, characterized in that: The obtaining of order data to be settled includes: Respond to the target business operation of the business interface and obtain the business event corresponding to the target business operation and the parameters of the business event; The order data to be settled is obtained according to the business event and the parameters of the business event.

3. The logistics order settlement method according to claim 1, characterized in that: The obtaining of the target order type corresponding to the order data includes: Obtaining parameters of the business event in the order data; Matching the parameters of the business event with the business parameters in the business database to obtain target parameters that match the parameters of the business event; The order type corresponding to the target parameter is obtained, and the order type corresponding to the target parameter is set as the target order type to which the order data belongs; wherein the business database includes a correspondence between at least one business parameter and an order type.

4. The logistics order settlement method according to claim 1, characterized in that: Before obtaining the target settlement rule corresponding to the order data according to the pre-configured rule engine and the target order type, the method includes: In response to a configuration request for rule configuration, a rule file of the rule engine is configured according to the settlement rule in the configuration request and the order type corresponding to the settlement rule; wherein the rule file includes a correspondence between at least one order type and a settlement rule.

5. The logistics order settlement method according to any one of claims 1 to 4, characterized in that: Obtaining a target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type includes: Matching the target order type with the order types in the rule file of the rule engine, and searching whether there is an order type identical to the target order type in the rule file; If it exists, the settlement rule corresponding to the target order type is obtained according to the correspondence between the order type and the settlement rule in the rule file, and the settlement rule corresponding to the target order type is set as the target settlement rule corresponding to the order data.

6. A logistics order settlement device, characterized in that: The logistics order settlement device includes: A data acquisition module is used to obtain order data to be settled and the target order type corresponding to the order data; a rule analysis module, configured to obtain a target settlement rule corresponding to the order data based on a pre-configured rule engine and the target order type; wherein the rule engine includes at least one correspondence between an order type and a settlement rule; An order settlement module, configured to settle the order data according to the target settlement rules; The rule analysis module is specifically configured to detect whether the target order type is a return type; if the target order type is a return type, detect whether the order data includes a set value-added service; if the value-added service is included, search the rule engine for a settlement rule corresponding to the value-added service, and set the settlement rule corresponding to the value-added service as the target settlement rule corresponding to the order data; the rule engine is configured with at least one correspondence between a value-added service and a settlement rule; and the rule engine is also configured with a correspondence between a customer access code and a settlement rule. The order settlement module is specifically used to obtain the target field to be settled in the order data; the value-added service is a second-level service under the first-level item of the target field; According to the target settlement rule, the target field is filled with data to settle the order data.

7. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the program, the method for settling a logistics order according to any one of claims 1 to 5 is implemented.

8. A readable storage medium, characterized in that: The readable storage medium includes a computer program, which, when running, controls the electronic device where the readable storage medium is located to execute the logistics order settlement method according to any one of claims 1 to 5.

Images