Price management method, electronic equipment and storage medium

Abstract

The invention discloses a price management method, electronic equipment and a storage medium, and the method comprises the steps: obtaining price management rules of a target commodity on a plurality of platforms, and determining the exclusiveness of the price management rules; when the price management rules are mutually exclusive, ranking the priorities of the price management rules, and adding the price management rules after priority ranking into a preset rule engine; and in response to a received price management rule query condition of a target commodity, querying the price management rule priority corresponding to the target commodity in the preset rule engine based on the price management rule query condition to determine the price of the target commodity. The invention discloses a price management method, electronic equipment and a storage medium, which can realize standardization and generalization of price management.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a price management method, electronic device, and storage medium. Background Technology

[0002] With the rapid development of internet technology, online shopping has become an indispensable part of people's daily lives. However, the current online shopping environment still faces many problems. At the technical level, the price management mechanism of online shopping platforms is particularly prominent. Currently, each platform operates independently, generating and managing its own pricing rules. This leads to several significant issues: First, due to the lack of unified standards, the pricing rules of different platforms are not entirely reasonable and may even contain potential unfairness. Second, price information between platforms is opaque, preventing data sharing, and consumers are forced to passively accept prices within a closed system. Finally, the siloed pricing system makes prices across platforms incompatible, reducing the commonality of price information and making unified management extremely difficult. This situation not only affects the consumer shopping experience but also poses a challenge to the healthy development of the entire e-commerce industry. Therefore, exploring a new price management mechanism to achieve price standardization and universalization has become an urgent problem for the e-commerce industry. Summary of the Invention

[0003] The purpose of this application is to provide a price management method, electronic device, and storage medium that can achieve standardization and universalization of price management.

[0004] To achieve the above objectives, the embodiments of this application adopt the following technical solutions: In a first aspect, embodiments of this application provide a price management method, including: Obtain the price management rules for the target product on multiple platforms and determine the mutual exclusivity of the price management rules; When price management rules are mutually exclusive, the priority of the price management rules is sorted, and the price management rules after priority sorting are added to the preset rule engine; In response to receiving the price management rule query conditions for the target product, the system queries the priority of the price management rule corresponding to the target product in the preset rule engine based on the price management rule query conditions to determine the price of the target product.

[0005] In one implementation, determining the mutual exclusivity of price management rules includes: If the query conditions of the first price management rule and the second price management rule overlap, then the first price management rule and the second price management rule are determined to be mutually exclusive.

[0006] In one implementation, prioritizing price management rules includes: The priority of a price management rule is determined based on at least one of the following: the query criteria range of price management rules from multiple platforms, the effective time of the price management rule, and the difference fields between price management rules.

[0007] In one implementation, the priority of a price management rule is determined based on at least one of the following: the query condition range of price management rules across multiple platforms, the effective time of the price management rule, and the difference fields between price management rules. This includes: If the query criteria of the first price management rule are included within the query criteria of the second price management rule, then the priority of the first price management rule is determined to be higher than that of the second price management rule; and / or If the query condition range of the first price management rule is equal to that of the second price management rule, then the priority of the first and second price management rules is determined based on their effective dates and / or the difference fields between them; and / or When the query conditions of the first price management rule and the query conditions of the second price management rule overlap but are not subsets of each other, obtain the difference fields between the query conditions of the first and second price management rules; determine the priority of the first and second price management rules based on the priority of the difference fields.

[0008] In one implementation, if the range corresponding to the query condition of the first price management rule is equal to the range corresponding to the query condition of the second price management rule, then the priority of the first price management rule and the second price management rule is determined based on the effective time of the first price management rule and the second price management rule, and / or the difference field between the first price management rule and the second price management rule, including: If the range corresponding to the query conditions of the first price management rule is equal to the range corresponding to the query conditions of the second price management rule, the price management rule with the later effective time will have higher priority than the price management rule with the earlier effective time.

[0009] In one implementation, the priority among price management rules is determined based on at least one of the following: the query condition range of price management rules across multiple platforms, the effective time of the price management rules, and the difference fields between price management rules. This includes: If the query conditions of the first price management rule and the second price management rule are identical, then the range of query conditions where the same fields in the first price management rule and the second price management rule differ is obtained, and a preset score is added to the price management rule with the largest range of query conditions corresponding to the same fields where the range of query conditions differs. Compare the scores of the first and second price management rules, and determine the priority of the price management rule with the larger score to be higher than that of the price management rule with the smaller score.

[0010] In one embodiment, the price management rules include mutual exclusion information and priority information; before adding the price management rules to the preset rule engine, the method further includes: Determine whether the mutual exclusion and priority indicators of the price management rules of multiple platforms are complete; If incomplete, supplement the missing mutual exclusion identifiers and / or missing priority identifiers according to the platform's default rules.

[0011] In one embodiment, based on price management rule query conditions, the price management rule priority corresponding to the target product is queried in a preset rule engine to determine the price of the target product, including: When the mutual exclusion flags of multiple platform price management rules for a target product are set to mutual exclusion, the highest priority price management rule for the target product in the preset rule engine is retrieved. Based on the query conditions of the price management rules, retrieve the price item corresponding to the highest priority price management rule from the pre-stored price details table; Determine the price of the target product based on the price list items.

[0012] In a second aspect, this application provides an electronic device, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the steps of the price management method as described in any of the first aspects.

[0013] Thirdly, this application provides a computer-readable storage medium that, when the instructions in the computer-readable storage medium are executed by a processor, implements the steps of the price management method as described in any of the first aspects.

[0014] This application provides a price management method, electronic device, and storage medium. The method includes: acquiring price management rules for a target product across multiple platforms and determining the mutual exclusivity of these rules; when price management rules are mutually exclusive, prioritizing the rules and adding the prioritized rules to a preset rule engine; and, in response to receiving a price management rule query condition for the target product, querying the priority of the corresponding price management rule in the preset rule engine based on the query condition to determine the price of the target product. Therefore, the price management method provided in this application, by acquiring price management rules from different platforms and prioritizing mutually exclusive rules to determine the price of the corresponding product according to the priority order, achieves standardized and universal price management. Attached Figure Description

[0015] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart illustrating a price management method provided for one embodiment of this application; Figure 2 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0017] The terms "first," "second," etc., used in this specification and claims are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in sequences other than those illustrated or described herein. Furthermore, in this specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0018] See Figure 1 This is a flowchart illustrating a price management method provided in an embodiment of this application. This price management method can be executed by an electronic device provided in this embodiment. The electronic device can be implemented using software and / or hardware, such as a server, a computer (for running PC programs and WeChat mini-programs), and a database server (for storing member information, price information, rule information, platform and tenant information, etc.). In this embodiment, the execution entity of the price management method is taken as the processor of a computer. The price management method provided in this embodiment includes: Step S1: Obtain the price management rules of the target product on multiple platforms and determine the mutual exclusivity of the price management rules.

[0019] In this embodiment, the price management rules include price query conditions, mutual exclusion identifiers, priority order, and maximum or minimum identifiers. Price query conditions may include price type (price types include price, discount, tax, etc., and price types can be expanded according to business needs), material code, business unit, sales entity, minimum price limit, maximum price limit, validity period, and other factors. It should be noted that a single price management rule does not necessarily need to include all of the above factors; if a factor is missing, it is not filtered.

[0020] In addition, a price data entry mainly includes: material code, business unit, reference price, highest price, lowest price, etc.

[0021] Understandably, to achieve precise control over the pricing of target products, this embodiment focuses on the detailed management of multiple pricing elements, such as price, discounts, and taxes. In the context of multi-platform operation, different platforms employ significantly different price management rules, with varying pricing mechanisms and strategies. Therefore, this embodiment first analyzes and identifies potential conflicts between these price management rules from different platforms, i.e., the mutual exclusion between various price management rules, ensuring that the mutual influence between rules can be reasonably handled when multiple rules coexist. Based on this, corresponding processing strategies are further formulated according to the mutual exclusion relationships between these rules to determine the final pricing method. This not only ensures the accuracy of pricing but also improves the adaptability and flexibility of the entire price management system, thereby better meeting the needs of multi-platform operation.

[0022] In one embodiment, determining the mutual exclusivity of price management rules includes: if the query condition ranges of the first price management rule and the second price management rule overlap, then determining that the first price management rule and the second price management rule are mutually exclusive.

[0023] Specifically, the query condition range of the price management rules for the target product across multiple platforms is maintained. If the condition range corresponding to the query condition of the current price rule intersects with the condition range corresponding to the query condition of any other existing price rule, the mutual exclusion flag of the newly added current price rule is marked as "mutually exclusive"; otherwise, it is marked as "not mutually exclusive".

[0024] For example, suppose the query condition range of the first price management rule is A, and the query condition range of the second price management rule is B. Since A and B intersect, the mutual exclusion flag for the first and second price management rules is set to "mutually exclusive." That is, when the first and second price management rules are mutually exclusive, their query condition ranges overlap, which may cause the system to be unable to determine which price management rule to select when pricing the target product. Therefore, by determining the mutual exclusion of each price management rule, when the query condition ranges of multiple price management rules overlap, the system can select the price management rule with higher priority to price the target product.

[0025] Step S2: When price management rules are mutually exclusive, sort the priority of the price management rules and add the price management rules after priority sorting to the preset rule engine.

[0026] As mentioned above, when price management rules are mutually exclusive, the query conditions of these rules may overlap, potentially preventing the system from accurately selecting the appropriate rule. Therefore, prioritizing mutually exclusive price management rules and storing the sorted rules in a pre-defined rule engine allows for direct referencing of matching rules when pricing target products, thus improving the accuracy and efficiency of price management.

[0027] In one embodiment, prioritizing price management rules includes: determining the priority of price management rules based on at least one of the following: the query condition range of price management rules across multiple platforms, the effective time of price management rules, and the difference fields between price management rules.

[0028] Understandably, with multiple platforms and multiple rules coexisting, clear guiding principles are needed to determine which price management rule should be prioritized and implemented when multiple price management rules apply to the same product.

[0029] First, prioritizing rules based on scope ensures that the most specific rules, those best matching the current query criteria, are executed first. This guarantees the applicability and relevance of the rules, making price management more precise. Second, the effective date of the rules helps determine priority, as newer rules may reflect the latest market strategies or regulatory changes. Prioritizing the most recent rules ensures the timeliness and adaptability of price management strategies. Third, price management rules may differ, such as different discount rates or price adjustment mechanisms. Prioritizing based on these differences helps the system prioritize the rule with the greatest impact on business operations, or the rule specified according to business strategy, when rule conflicts occur.

[0030] In one embodiment, the priority of a price management rule is determined based on at least one of the following: the query condition range of price management rules across multiple platforms, the effective time of the price management rule, and the difference fields between price management rules. This includes: if the query condition range of a first price management rule is smaller than the query condition range of a second price management rule, and the query condition range of the first price management rule is included in the query condition range of the second price management rule, then the priority of the first price management rule is determined to be higher than the priority of the second price management rule; and / or if the query condition range of the first price management rule is equal to the query condition range of the second price management rule, then the priority of the first price management rule and the second price management rule is determined based on the effective time of the first price management rule and the second price management rule, and / or the difference fields between the first price management rule and the second price management rule.

[0031] Specifically, when the query condition range of the first price management rule is a proper subset of the query condition range of the second price management rule, the first price management rule is prioritized over the second. Understandably, if the query condition range of the first price management rule is a proper subset of the query condition range of the second price management rule, it means that the first price rule applies to a more specific scenario or condition. Generally, more specific price management rules better meet specific business needs or strategic objectives. Therefore, prioritizing price management rules with smaller query condition ranges ensures more accurate pricing that meets the needs of specific markets or customer groups.

[0032] In one embodiment, if the range corresponding to the query condition of the first price management rule is equal to the range corresponding to the query condition of the second price management rule, then the priority of the first price management rule and the second price management rule is determined according to the effective time of the first price management rule and the second price management rule, and / or the difference field between the first price management rule and the second price management rule. This includes: if the range corresponding to the query condition of the first price management rule is equal to the range corresponding to the query condition of the second price management rule, the price management rule with the later effective time is determined to have a higher priority than the price management rule with the earlier effective time.

[0033] Understandably, the effective date of price management rules can reflect the latest market strategies or regulatory changes, and prioritizing the latest rules can ensure the timeliness and adaptability of price management strategies.

[0034] In one embodiment, the priority of price management rules is determined based on at least one of the following: the query condition range of price management rules across multiple platforms, the effective time of price management rules, and the difference fields between price management rules. This includes: when the query condition range of a first price management rule intersects with the query condition range of a second price management rule but they are not subsets of each other, obtaining the difference fields between the query conditions of the first and second price management rules; determining the priority of the first and second price management rules based on the priority of the difference fields; if the query conditions of the first and second price management rules have no difference fields, obtaining the query condition ranges where the same fields differ between the first and second price management rules, and adding a preset score to the price management rule with the largest query condition range corresponding to the same fields where the query condition ranges differ; comparing the score values ​​of the first and second price management rules, and determining the price management rule with the larger score value as having a higher priority than the price management rule with the smaller score value.

[0035] Understandably, when the query conditions of two price management rules overlap but are not subsets of each other, the priority of the corresponding price management rules is determined by the priority of the difference field. The difference field is key to determining which rule should be given priority when the conditions overlap. It should be noted that the priority of the difference field is usually predefined by business logic, strategy, or management decisions. For example, if a certain difference field (such as "promotional area") is considered a more important condition, then the rule containing this field will be given higher priority and applied first in the case of overlap.

[0036] For example, suppose the first price management rule applies to the case of "order amount greater than 100 and user level is VIP", and the second price management rule applies to the case of "order amount greater than 200 and user level is ordinary". The query conditions of these two price management rules overlap (e.g., the case of order amount greater than 100 and greater than 200), but they are not subsets of each other. In this case, if "user level" is identified as a differentiating field, and the business decision considers "user level" to be a more important condition, then the first rule (for VIP users) will be given higher priority.

[0037] It should be noted that when the query range of the first price management rule and the second price management rule is the same, no points will be awarded.

[0038] The first and second price management rules have identical query conditions, meaning there's no unique field to distinguish them. However, the same field might have different ranges. For example, if both rules have an "order amount" field, but the first rule's query range is "order amount greater than 100," while the second rule's is "order amount greater than 200," then the "order amount" field has a different range. When comparing the breadth of the query range, if one rule's range is wider (i.e., applicable to more scenarios or conditions), that rule will receive a higher score. Using the "order amount" example again, because the first rule's range (greater than 100) is broader than the second rule's (greater than 200), the first rule would gain one point.

[0039] Therefore, when two price management rules have no different fields, priority is determined by comparing the different query ranges of the same fields. The price management rule with a wider query range (i.e., the rule with broader applicability) will be assigned a higher score and thus may have a higher priority. This ensures that when multiple price management rules apply, the rule's breadth of application can determine which one should be prioritized.

[0040] In one embodiment, the price management rules include mutual exclusion information and priority information; before adding the price management rules to the preset rule engine, the method further includes: determining whether the mutual exclusion identifiers and priority identifiers of the price management rules of multiple platforms are complete; if they are incomplete, supplementing the missing mutual exclusion identifiers and / or missing priority identifiers according to the platform's default rules.

[0041] As mentioned earlier, a price management rule mainly includes: price query conditions, mutual exclusion flags, priority flags, and maximum / minimum flags. However, since the initial price management rules were obtained directly from various platforms, they may be incomplete. Specifically, mutual exclusion flags, priority flags, and maximum / minimum flags may be missing. Before adding these price management rules to the preset rule engine, these missing values ​​need to be added. These missing values ​​can be manually configured or modified, or they can be automatically added according to the default rules.

[0042] It should be noted that when the price management rules are mutually exclusive, the priority identifier cannot be empty; when the price management rules are not mutually exclusive, the maximum or minimum identifier cannot be empty.

[0043] In one embodiment, based on price management rule query conditions, the price management rule priority corresponding to the target product is queried in a preset rule engine to determine the price of the target product. This includes: when the mutual exclusion flags of multiple platform price management rules for the target product are mutually exclusive, obtaining the price management rule with the highest priority for the target product in the preset rule engine; obtaining the price item corresponding to the price management rule with the highest priority from a pre-prepared price detail table through the price management rule query conditions; and determining the price of the target product based on the price item.

[0044] The price management method provided in this application, in the case of mutually exclusive price management rules, obtains the highest priority price management rule, retrieves the corresponding price item from the price details table based on the query conditions of that price management rule (generally only one price item; in special cases where multiple price items exist, the most recently entered price item is usually used), and returns the product price value from that price item to the user. If the highest priority price management rule does not retrieve any price item, the method continues to match the price details table according to the principle of decreasing priority rules, and so on, until a price is retrieved. If no price item is retrieved by any of the price management rules, a "price retrieval failed" message is returned.

[0045] If the price management rules are not mutually exclusive, the corresponding price item is retrieved from the price details table according to the query conditions of the price management rule. If there are multiple price items, the maximum or minimum flag of the price management rule is further checked. If the flag is "maximum", the maximum price in the price item is returned to the user. If it is "minimum", the minimum price in the price item is returned to the user. If no price item is found, the "price retrieval failed" prompt is returned directly.

[0046] In addition, the price management method provided in the application also includes: using Redis as the medium for storing price management rules, and the corresponding price management rules will automatically become invalid after a specified period.

[0047] The price management method provided in this application obtains price management rules from different platforms, prioritizes mutually exclusive price management rules, and determines the price of corresponding commodities according to the priority order. This enables the standardization and universalization of price management.

[0048] The foregoing has described specific embodiments of this specification. 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 result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0049] Figure 2 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 2 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0050] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 2 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0051] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0052] The processor reads the corresponding computer program from non-volatile memory into memory and then runs it, forming a data processing device at the logical level. The processor executes the program stored in memory and specifically performs the price management method provided in this embodiment.

[0053] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0054] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by a portable electronic device including multiple applications, enable the portable electronic device to perform the price management method provided in this application.

[0055] In summary, the above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0056] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0057] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0058] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0059] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A price management method, characterized in that: include: Obtaining price management rules for target products on multiple platforms and determining the mutual exclusivity of the price management rules; When the price management rules are mutually exclusive, sorting the priorities of the price management rules, and adding the price management rules after the priority sorting to the preset rule engine; In response to receiving the price management rule query condition of the target product, based on the price management rule query condition, the priority of the price management rule corresponding to the target product is queried in the preset rule engine to determine the price of the target product.

2. The method according to claim 1, characterized in that Determining the mutual exclusivity of the price management rules includes: If the query condition ranges of the first price management rule and the second price management rule overlap, it is determined that the first price management rule and the second price management rule are mutually exclusive.

3. The method according to claim 1, characterized in that The prioritizing of the price management rules includes: The priority of the price management rules is determined according to at least one of the query condition range of the price management rules of the multiple platforms, the effective time of the price management rules, and the difference field between the price management rules.

4. The method according to claim 3, characterized in that Determining the priority corresponding to the price management rule according to at least one of the query condition range of the price management rules of the multiple platforms, the effective time of the price management rule, and the difference field between the price management rules includes: If the query condition range of the first price management rule is included in the query condition range of the second price management rule, determining that the priority of the first price management rule is higher than the priority of the second price management rule; and / or If the query condition range of the first price management rule is equal to the query condition range of the second price management rule, determining the priority of the first price management rule and the second price management rule according to the effective time of the first price management rule and the second price management rule, and / or the difference field between the first price management rule and the second price management rule; and / or When the query condition range of the first price management rule and the range corresponding to the query condition of the second price management rule intersect but are not subsets of each other, obtain the difference field of the query conditions of the first price management rule and the second price management rule; determine the priority of the first price management rule and the second price management rule according to the priority of the difference field.

5. The method according to claim 4, characterized in that If the query condition range of the first price management rule is equal to the query condition range of the second price management rule, determining the priority of the first price management rule and the second price management rule according to the effective time of the first price management rule and the second price management rule, and / or the difference field between the first price management rule and the second price management rule, including: If the query condition range of the first price management rule is equal to the query condition range of the second price management rule, it is determined that the price management rule with a later effective time has a higher priority than the price management rule with an earlier effective time.

6. The method according to claim 3, characterized in that Determining the priorities among the price management rules according to at least one of the query condition ranges of the price management rules of the multiple platforms, the effective time of the price management rules, and the difference fields among the price management rules includes: If there is no difference in the query conditions of the first price management rule and the second price management rule, obtain the query condition range of the same field in the first price management rule and the second price management rule, and increase the preset score value for the price management rule with the largest query condition range corresponding to the same field in which the query condition range is different; The integral values ​​of the first price management rule and the second price management rule are compared, and the priority of the price management rule with a larger integral value is determined to be higher than the price management rule with a smaller integral value.

7. The method according to claim 1, characterized in that The price management rules include mutual exclusivity information and priority information; Before adding the price management rule to the preset rule engine, the method further includes: Determining whether the mutual exclusivity identifiers and priority identifiers of the price management rules of the multiple platforms are complete; If it is incomplete, fill in the missing mutually exclusive identifiers and / or missing priority identifiers according to the platform's default rules.

8. The method according to claim 1 or 7, characterized in that: The querying of the price management rule priority corresponding to the target commodity in the preset rule engine based on the price management rule query condition to determine the price of the target commodity includes: When the mutual exclusivity marks of the multiple platform price management rules of the target product are mutually exclusive, obtaining the price management rule with the highest priority for the target product in the preset rule engine; Obtaining the price list item corresponding to the price management rule with the highest priority from the pre-stored price list according to the price management rule query condition; The price of the target product is determined according to the price list item.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the steps of the price management method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the steps of the price management method according to any one of claims 1 to 8 are implemented.

Images