Method and device for accounting the amount of a combined order

Abstract

The application provides a method and device for checking the amount of a combined order, the method comprising: receiving an order price checking request, the order price checking request comprising at least two SKU objects, wherein each SKU object comprises a SKU identifier and a purchase quantity; performing an overlay category check, an order amount check and a single product proportion check on the order price checking request according to the SKU identifier and the purchase quantity; in response to the overlay category check, the order amount check and the single product proportion check all passing, determining a discount multiplier for each SKU object; calculating the payable amount of each SKU object according to the corresponding discount multiplier; and calculating the total order amount according to the payable amount of each SKU object. The application realizes direct configuration and automatic determination of a complex discount operation intention, supports calling different discount multipliers for different SKU objects and calculating the discount amount of each SKU object, so as to adapt to a multi-format structure in which different discount rules, bulk purchasing and combined promotion coexist.

Description

Technical Field

[0001] This invention relates to the field of financial data processing, and in particular to a method and apparatus for calculating the amount of a combined order. Background Technology

[0002] In the field of business-to-business (B2B) e-commerce, transactions often take the form of combined orders containing multiple stock keeping units (SKUs), with each product in the order corresponding to a unique SKU number.

[0003] In this scenario, a single buyer inquiry or order request may cover multiple product categories, span multiple orders of magnitude, and incorporate multiple pricing factors such as bulk discounts and discount rule references. The pricing engine not only needs to provide a transactional price within milliseconds of response time, but also must ensure that the rules can be configured independently by the operations team, that the pricing results are explainable throughout the entire process, and that it can maintain stable operation under high-concurrency inquiry scenarios.

[0004] Therefore, there is an urgent need in this field for a method to calculate the amount of combined orders, in order to solve the problems of insufficient multi-condition combination triggers and inadequate amount calculation capabilities in complex combined order scenarios. Summary of the Invention

[0005] Firstly, addressing the problems existing in the prior art, the present invention provides a method for calculating the amount of combined orders, which can improve the ability to calculate discount amounts. The method includes:

[0006] Receive an order pricing request, wherein the order pricing request includes at least two SKU objects, and each SKU object includes: SKU identifier and purchase quantity;

[0007] Based on the SKU identifier and the purchase quantity, the order pricing request is subjected to category verification, order amount verification, and single product percentage verification.

[0008] If the category coverage verification, order amount verification, and single category percentage verification all pass, then the discount multiplier for each SKU object is determined.

[0009] Calculate the amount payable for each SKU object according to the corresponding discount rate;

[0010] Calculate the total order amount based on the payable amount for each SKU object.

[0011] According to the method for calculating the amount of a combined order provided by the present invention, after receiving the order pricing request, the method further includes:

[0012] The SKU details corresponding to the order pricing request are loaded in batches according to the SKU identifier; each SKU detail includes: the price, category and discount rule identifier of the SKU object.

[0013] According to the method for calculating the amount of a combined order provided by the present invention, the step of verifying the covered categories includes:

[0014] Determine the category quantity of all SKU objects in the order pricing request;

[0015] Compare the number of product categories for all SKU objects in the order pricing request with the product category quantity threshold;

[0016] If the number of categories of all SKU objects in the order pricing request is not less than the category quantity threshold, then the coverage category verification passes.

[0017] According to the method for calculating the amount of a combined order provided by the present invention, the step of verifying the order amount includes:

[0018] Calculate the original total order amount based on the price of the SKU and the quantity purchased;

[0019] Compare the original total amount of the order with the amount threshold;

[0020] If the original total amount of the order is not less than the amount threshold, then the order amount verification passes.

[0021] According to the method for calculating the amount of a combined order provided by the present invention, the step of verifying the percentage of a single product category includes:

[0022] Based on the price, category, and quantity of the SKU object, calculate the original total order amount and the original amount for each category;

[0023] Based on the original amount of each product category and the original total amount of the order, determine the proportion of the amount corresponding to the largest single product category in the current order in the original total amount of the order;

[0024] If the percentage of the amount corresponding to the largest single category in the current order in the original total amount of the order is not greater than the percentage threshold, then the percentage verification of the single category passes.

[0025] According to the method for calculating the amount of a combined order provided by the present invention, the step of determining the discount rate for each SKU object includes:

[0026] A discount rule identifier for each SKU object is determined based on the SKU identifier of each SKU object; the discount rule identifier includes: a first discount rule identifier, a second discount rule identifier, and a third discount rule identifier;

[0027] In response to the first discount rule identifier corresponding to the SKU object, the original total amount of the order is calculated based on the price of the SKU object and the purchase quantity, and the discount multiplier corresponding to the current SKU object is determined based on the original total amount of the order.

[0028] In response to the second discount rule identifier corresponding to the SKU object, the discount multiplier corresponding to the current SKU object is determined based on the purchase quantity of the SKU object;

[0029] In response to the third discount rule identifier corresponding to the SKU object, the discount multiplier of the current SKU object is determined to be 1.

[0030] According to the method for calculating the amount of a combined order provided by the present invention, before calculating the total order amount based on the payable amount of each SKU object, the method further includes:

[0031] Determine the preset base price for each SKU object;

[0032] For each SKU object, calculate the discounted unit price of the SKU object according to the discount rate;

[0033] If the discounted unit price is less than the preset base price, the amount payable for the current SKU object is calculated based on the preset base price.

[0034] According to the method for calculating the amount of a combined order provided by the present invention, before calculating the total order amount based on the payable amount of each SKU object, the method further includes:

[0035] Determine the premium factor for each SKU object;

[0036] For each SKU object, the amount payable for each SKU object is calculated based on the corresponding discount rate and the premium coefficient.

[0037] According to the method for calculating the amount of a combined order provided by the present invention, after calculating the total order amount based on the payable amount for each SKU object, the method further includes:

[0038] Obtain profit-sharing rules;

[0039] Based on the profit-sharing rules and the total order amount, a profit-sharing breakdown is generated.

[0040] Secondly, the present invention also provides a device for calculating the amount of a combined order, the device comprising:

[0041] A receiving unit is configured to receive an order pricing request, wherein the order pricing request includes at least two SKU objects, each of which includes: an SKU identifier and a purchase quantity;

[0042] The verification unit is configured to perform category verification, order amount verification, and single product percentage verification on the order pricing request based on the SKU identifier and the purchase quantity.

[0043] The discount determination unit is configured to determine the discount multiplier for each SKU object in response to the passing of the coverage category verification, order amount verification, and single category percentage verification.

[0044] The first amount calculation unit is configured to calculate the amount payable for each SKU object according to the corresponding discount rate;

[0045] The second amount calculation unit is configured to calculate the total order amount based on the payable amount for each SKU object.

[0046] The method for calculating the amount of the combined order provided in this application includes at least two SKU objects in the order pricing request. The order pricing request is validated for coverage category, order amount, and single product percentage. Only when the coverage category validation, order amount validation, and single product percentage validation all pass, will the subsequent discount calculation and the final order amount be calculated. This realizes the direct configuration and automatic determination of the intention to perform compound discount operations without the need for manual order review. At the same time, this application also supports calling different discount multipliers for different SKU objects and calculating their discount amounts separately, in order to adapt to the multi-business structure where different discount rules, bulk purchases, and combined promotions coexist. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0048] Figure 1 This is a flowchart illustrating the method for calculating the amount of a combined order provided by the present invention;

[0049] Figure 2 This is a schematic diagram of the structure of the combined order amount calculation device provided by the present invention. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0051] In a first aspect, this application provides a method for calculating the amount of a combined order, such as Figure 1 As shown, the method includes steps 110-150:

[0052] Step 110: Receive order pricing request;

[0053] Specifically, an order pricing request is a message requesting price calculation. In the application scenario of this application, an order pricing request includes at least two SKU objects, and each SKU object includes: an SKU identifier and a purchase quantity, representing the unique identifier and purchase quantity of the SKU object, respectively. An SKU object is used to describe a structured data unit of inventory unit and purchase quantity, and the SKU identifier and purchase quantity can be associated through the SKU object. That is, in this application, a single order pricing request carries the basic pricing data corresponding to multiple SKU objects.

[0054] In a preferred embodiment, after receiving an order pricing request, the SKU details corresponding to the order pricing request are also loaded in batches according to the SKU identifier. The SKU details are used to provide the price, category, and discount rule identifier of the SKU object to subsequent pricing processing. That is, each SKU detail includes: the price, category, and discount rule identifier of the SKU object. The price of the SKU object represents the base selling price corresponding to the current SKU object. The category of the SKU object represents the product category to which the current SKU object belongs, such as "fasteners," "lubricating oil," and "labor protection products," etc. The discount rule identifier of the SKU object represents which type of discount rule is applied when calculating the price discount for the current SKU object.

[0055] Step 120: Perform category coverage verification, order amount verification, and single product percentage verification on the order pricing request based on SKU identifier and purchase quantity;

[0056] Specifically, currently, the criteria for determining whether an order meets the discount eligibility threshold are generally limited to the order amount. This single-dimensional verification method cannot accurately determine whether an order meets the discount rules. It may incorrectly identify orders that do not meet the discount rules as eligible for discounts, or incorrectly reject orders that do meet the rules. It also fails to accurately represent combined or cross-category discount calculations. Therefore, this application will perform multi-dimensional verification on all SKU objects in the order pricing request, based on their SKU identifier and purchase quantity, covering categories, the original order amount, and the proportion of a single product. This will more accurately express and automatically execute promotional intentions such as "cross-category bundled orders," effectively blocking loopholes like "single-category quantity stacking for discounts," rather than relying on a crude determination based solely on a single amount threshold.

[0057] The order is categorized into three main checks: Category Coverage Check, Order Amount Check, and Single Product Percentage Check. Category Coverage Check determines whether the order's total amount falls within a preset range. Single Product Percentage Check determines if any single SKU's purchase amount exceeds a preset percentage threshold. Only if all three checks pass will an order be deemed eligible for a discount, and the discount will be calculated in subsequent steps.

[0058] In a preferred embodiment, the process for category coverage verification includes: determining the category quantity of all SKU objects in the current single pricing request, and then comparing the category quantity of all SKU objects in the order pricing request with a category quantity threshold. If the category quantity of all SKU objects in the order pricing request is not less than a preset category quantity threshold, the category coverage verification is deemed successful. That is, in this application, one of the conditions for an order to enjoy a discount is that the number of covered categories in the order should be greater than a preset value. It is understandable that an SKU is the smallest traceable unit in inventory management. Generally, if a difference in a certain attribute of a product necessitates separate inventory management, pricing, or sales, different SKUs should be assigned. Therefore, different SKU identifiers may correspond to the same category.

[0059] The order amount verification process includes: calculating the original total order amount based on the listed price of all SKU objects and their corresponding purchase quantities in the current order pricing request, and then comparing the original total order amount with a preset amount threshold. If the original total order amount is not less than the amount threshold, the order amount verification passes. In other words, in this application, the second condition for enjoying a discount is that the original total order amount should be greater than a preset value.

[0060] The process for verifying the percentage of a single product category includes: calculating the original amount for each product category and the original total amount of the order based on the price, category, and quantity of the SKU object in the current order pricing request; then determining the percentage of the amount corresponding to the largest single product category in the current order's original total amount based on the original amount of each product category and the original total amount of the order. If the percentage of the amount corresponding to the largest single product category in the current order's original total amount is not greater than a percentage threshold, the single product category percentage verification passes. In other words, in this application, the third condition for enjoying a discount is that the amount corresponding to at least one product category in the order must have a percentage of the original total amount of the order that is less than a preset value.

[0061] Step 130: If the category coverage verification, order amount verification, and single category percentage verification all pass, then determine the discount multiplier for each SKU object.

[0062] Specifically, in response to the successful verification of product category coverage, order amount, and single product category percentage, the discount multiplier for each SKU is determined separately. That is, this application uses different discount multipliers for different SKUs, rather than a uniform discount multiplier for the entire order. This supports discount rules such as "mixed calculation of multiple product categories and multiple discount multipliers" and "inclusion in trigger statistics but not participating in discounts," adapting to multi-business structures where bulk purchasing and bundled promotions coexist.

[0063] In a preferred embodiment, the discount rules in this application include three categories: a first discount rule that determines the discount multiplier based on the original total order amount, a second discount rule that determines the discount multiplier based on the purchase quantity of SKU objects, and a third discount rule that does not participate in the discount. These three types of rules correspond to the first discount rule identifier, the second discount rule identifier, and the third discount rule identifier, respectively. The discount rule identifier is bound to the SKU identifier, thereby enabling the determination of the discount rule identifier corresponding to each SKU object based on the SKU identifier of each SKU object.

[0064] In response to the first discount rule identifier corresponding to the SKU object, it indicates that the discount multiplier for the current SKU object should be determined based on the original order amount. This correspondence between the amount and the discount multiplier is stored in the amount tier discount table. In this table, each amount range corresponds to a discount multiplier, with the ranges using a left-closed, right-open format (lower amount limit, upper amount limit). If the upper limit is empty, it indicates no upper bound; if the lower limit is empty, it is considered an invalid configuration. The original total order amount is calculated based on the SKU object's price and quantity. The amount range into which the original total order amount falls is determined in the amount tier discount table, thus determining the discount multiplier corresponding to the original total order amount. This discount multiplier is the discount multiplier corresponding to the current SKU object. If multiple tiers are matched simultaneously due to overlapping range configurations, the discount multiplier corresponding to the one with the largest lower limit is selected to ensure the determinism and uniqueness of the tier selection.

[0065] In response to the second discount rule identifier corresponding to the SKU object, it indicates that the discount multiplier for the current SKU object should be determined based on its purchase quantity. The correspondence between purchase quantity and discount multiplier is stored in the quantity tier discount table. In this table, each quantity range corresponds to a discount multiplier, and the range is in the form of [lower quantity limit, upper quantity limit], which is closed on both sides. If the upper limit is empty, it means there is no upper limit; if the lower limit is empty, it is considered an invalid configuration. Based on the purchase quantity of the current SKU object, the range in the quantity tier discount table is determined, thereby determining the discount multiplier corresponding to the current SKU object. If multiple tiers are matched simultaneously due to overlapping range configurations, the discount multiplier corresponding to the one with the largest lower limit is selected.

[0066] In response to the third discount rule identifier corresponding to the SKU object, it indicates that the current SKU object does not participate in the discount activity, and the discount multiplier for the current SKU object is 1. It is understandable that although an individual SKU object can be set to "not participate in the discount", its corresponding amount and number of categories are still included in the verification process in step 120 to avoid the statistical scope being incorrectly narrowed.

[0067] In addition, if the discount multiplier value corresponding to the amount range or the purchase quantity range is missing or empty, it can also be processed as a discount multiplier of 1.

[0068] Of course, those skilled in the art can set other discount rules as needed and set corresponding discount identifiers. For example, different discount rates can be set based on the amount of the SKU object, etc., which will not be listed here.

[0069] Step 140: Calculate the amount payable for each SKU object according to the corresponding discount rate;

[0070] Specifically, for each SKU object, the amount of the SKU object is first calculated based on its listed price and purchase quantity, and then the amount of the SKU object is multiplied by the corresponding discount rate to obtain the amount payable after discount. The calculation of the amount payable can be rounded according to the preset precision.

[0071] In some cases, if the discount rate is too large or the listed price of the SKU is low, the amount payable calculated based on the discount rate may be lower than the reasonable cost price, resulting in an abnormally low total order amount, causing price imbalance and transaction losses. Therefore, in a preferred embodiment, before calculating the total order amount based on the payable amount for each SKU, this application also needs to determine whether the discounted price of the SKU has "fallen below the floor price". That is, a preset floor price is determined for each SKU, and for each SKU, the discounted unit price is calculated based on the discount rate. In response to the discounted unit price being less than the preset floor price, the payable amount for the current SKU is calculated based on the preset floor price and the current purchase quantity of the SKU, and the floor price breach event is marked for subsequent risk control and auditing.

[0072] The aforementioned preset base price can be obtained from the preset base price configuration list based on the SKU identifier. In a more preferred embodiment, the preset base price can also be obtained by parsing the profit-sharing rules and cost rules. This process includes: first, obtaining the profit-sharing rules and cost rules associated with the SKU identifier. Both the profit-sharing rules and cost rules are structured data, including information such as cost values, profit-sharing ratios, and profit-sharing calculation methods. Then, obtaining the cost amount of the current SKU object from the cost rules and the profit-sharing ratio of the current SKU object from the profit-sharing rules. Multiplying the cost amount by the profit-sharing ratio to obtain the profit-sharing amount, and then adding the cost amount and the profit-sharing amount to obtain the preset base price. In this process, the obtained preset base price is automatically calculated and generated based on the cost value and profit-sharing ratio, avoiding manual configuration of base prices item by item, reducing maintenance costs, and reducing the possibility of configuration errors.

[0073] Step 150: Calculate the total order amount based on the payable amount for each SKU object;

[0074] Specifically, the discounted amounts of all SKUs are summed to obtain the final total order amount.

[0075] In a preferred embodiment, this application also sets a premium coefficient for SKUs to address potential price differences in scarcity, delivery costs, and service costs among different SKUs. For example, if a region experiences a sudden natural disaster, the costs associated with delivery and service for all goods in that region will rise sharply in the short term. Adjusting the prices of all goods in that region one by one is obviously inefficient. However, if all SKUs in that region are selected and adjusted, and the premium coefficient is adjusted uniformly, a unified price adjustment can be achieved in one step, reducing the number of related price adjustment steps. That is, the premium coefficient for each SKU is determined before calculating the total order amount based on the payable amount for each SKU. For each SKU, after calculating the discounted amount according to the corresponding discount rate, it is necessary to multiply it by its premium coefficient to calculate the payable amount for each SKU. Then, the discounted amounts of all SKUs are summed to obtain the final total order amount. If the discounted unit price of any SKU falls below the base price, the base price is multiplied by the purchase quantity and then by the premium coefficient to calculate the payable amount for each SKU.

[0076] Understandably, the aforementioned discount multiplier, preset base price, premium coefficient, and other factors related to the amount calculation are merely price calculation parameters and do not involve any evaluation or guidance of a person's behavior, identity, or moral values. They can be written into the order data as price composition information, and the entire chain of write-back results is explained and auditable by setting corresponding tags, so that consumers can query and regulatory agencies can verify them.

[0077] In addition, after obtaining the total order amount, a profit-sharing breakdown can be generated based on business needs, allowing technical personnel to better set pricing and discount rules. First, the currently effective profit-sharing rules are retrieved from the profit-sharing rule database. This database stores profit-sharing rules in structured data, including the identifiers of participating entities, profit-sharing ratios, and profit-sharing calculation methods. Then, using the participating entity identifiers, profit-sharing ratios, profit-sharing calculation methods, and the current total order amount, the profit-sharing amount for each participant is calculated, generating the profit-sharing breakdown. After summarizing the profit-sharing, the final output includes complete decision-making information, including: the original total order amount, the final total order amount, details of three verification items, the discount multiplier for each SKU, whether the minimum price has been reached, the premium amount, and other details, as well as the profit-sharing breakdown, to support the solidification of inquiry orders, approval processes, and post-event auditing.

[0078] For the aforementioned category quantity thresholds, amount thresholds, percentage thresholds, amount tier discount tables, quantity tier discount tables, profit-sharing rule databases, and other design data and their corresponding relationships, all can be written to the relevant databases on the management side and then synchronously updated to the current system's cache by the refresh service. Subsequent calls to this data can directly retrieve it from the system cache. Furthermore, this method supports full cache refreshes and incremental refreshes based on the scope of changes, and can be triggered by asynchronous or scheduled tasks. New rules or data do not require a new version release, creating logical read-write separation and decoupling "strategy changes" from "application releases."

[0079] The above describes the overall process of the method for calculating the amount of combined orders provided in this application. The following is a specific embodiment that further illustrates the specific execution process of this method.

[0080] In one specific embodiment, the preset threshold for the number of product categories is "3", the preset threshold for the amount is "30,000" (currency unit omitted in this application), and the preset threshold for the proportion is "0.4". This means that an order must contain products across "3" product categories, the original total amount of the order must reach "30,000", and the amount of one product category in the order must account for "0.4" of the original total amount of the order in order for the order to enjoy the corresponding discount.

[0081] A pricing request for an order is received. This request includes three SKU objects: "SKU-A", "SKU-B", and "SKU-C", belonging to the categories "Fasteners", "Lubricants", and "Labor Protection Supplies" respectively. The listed prices are "100", "200", and "50", with purchase quantities of "200", "100", and "200" respectively. For this order, if the quantities of the three categories are not less than the threshold of "3" categories, the original total order amount of "50,000" is not less than the threshold of "30,000", and the respective percentage of the amount for "Fasteners" and "Lubricants" is "0.4" and not greater than the threshold of "0.4", then the category verification, order amount verification, and single category percentage verification all pass.

[0082] After passing the above verification, the cache is read to determine the first discount rule identifier corresponding to the SKU object "SKU-A", the second discount rule identifier corresponding to the SKU object "SKU-B", and the third discount rule identifier corresponding to the SKU object "SKU-C". The cache is then read to determine that the amount-based discount table contains records for "[30000, 100000) corresponding to 0.95, [100000, +∞) corresponding to 0.90", and the quantity-based discount table contains records for "[1,50] corresponding to 0.98, [51,200] corresponding to 0.95, [201, +∞) corresponding to 0.92". Therefore, for the SKU object "SKU-A", the original total order amount falls within the range [30000, 100000), and its discount rate is 0.95. Combining this with the purchase quantities of "100" and "200", the current payable amount is "19000". For SKU "SKU-B", the purchase quantity falls within the range of [51, 200], and its discount rate is 0.95. Combining this with the purchase quantities of its listed prices "200" and "100", the current amount payable is "19000". For SKU "SKU-C", its discount rate is 1, and combining this with the purchase quantities of its listed prices "50" and "200", the current amount payable is "10000".

[0083] After calculating the discount, the preset base prices for "SKU-A", "SKU-B", and "SKU-C" were determined to be "60", "150", and "40" respectively by reading the cache. Therefore, the discounted unit prices for "SKU-A", "SKU-B", and "SKU-C", "95", "190", and "50" respectively, are all no lower than the preset base prices. Furthermore, reading the cache confirmed that the premium coefficient for "SKU-A", "SKU-B", and "SKU-C" is all "1". Therefore, the final order amount, calculated using the amounts payable for the three SKU objects "19000", "19000", and "10000", is "48000".

[0084] Finally, by reading the cache, the profit-sharing rules of "e-commerce platform A receives 5% of the order amount" and "agent B receives 20% of the order amount" are determined, and the profit-sharing details of "distributor A receives 2400 and operator B receives 9600" are generated.

[0085] The method for calculating the amount of the combined order provided in this application includes at least two SKU objects in the order pricing request. The order pricing request is validated for coverage category, order amount, and single product percentage. Only when the coverage category validation, order amount validation, and single product percentage validation all pass, will the subsequent discount calculation and the final order amount be calculated. This realizes the direct configuration and automatic determination of the intention to perform compound discount operations without the need for manual order review. At the same time, this application also supports calling different discount multipliers for different SKU objects and calculating their discount amounts separately, in order to adapt to the multi-business structure where different discount rules, bulk purchases, and combined promotions coexist.

[0086] In a second aspect, this application also provides a device for calculating the amount of combined orders. The device for calculating the amount of combined orders provided by this invention will now be described, and the device described below corresponds to the method described above for calculating the amount of combined orders. Figure 2 This is a schematic diagram of the structure of the combined order amount calculation device provided by the present invention, as shown below. Figure 2 As shown, the device includes:

[0087] The receiving unit 210 is configured to receive an order pricing request, wherein the order pricing request includes at least two SKU objects, each of which includes: an SKU identifier and a purchase quantity;

[0088] The verification unit 220 is configured to perform category verification, order amount verification, and single product percentage verification on the order pricing request based on the SKU identifier and the purchase quantity.

[0089] The discount determination unit 230 is configured to determine the discount multiplier for each SKU object in response to the passing of the coverage category verification, order amount verification, and single category percentage verification.

[0090] The first amount calculation unit 240 is configured to calculate the payable amount for each SKU object according to the corresponding discount rate;

[0091] The second amount calculation unit 250 is configured to calculate the total order amount based on the payable amount for each SKU object.

[0092] The combined order amount calculation device provided in this application includes at least two SKU objects in the order pricing request. It performs category coverage verification, order amount verification, and single product percentage verification on the order pricing request. Only when the category coverage verification, order amount verification, and single product percentage verification all pass, will the subsequent discount calculation and the final order total amount calculation be performed. This realizes the direct configuration and automatic determination of the compound discount operation intention without the need for manual order review. At the same time, this application also supports calling different discount multipliers for different SKU objects and calculating their discount amounts separately, so as to adapt to the multi-business structure where different discount rules, bulk purchases and combined promotions coexist.

[0093] Other preferred embodiments, specific implementations, technical problems that can be solved, and technical effects that can be achieved by the above-mentioned combined order amount calculation device all correspond to the combined order amount calculation method, and will not be repeated here.

[0094] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0095] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0096] 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 process, method, article, or apparatus. Unless otherwise specified, 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 that element.

[0097] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for calculating the amount of a combined order, characterized in that, The method includes: Receive an order pricing request, wherein the order pricing request includes at least two SKU objects, and each SKU object includes: SKU identifier and purchase quantity; Based on the SKU identifier and the purchase quantity, the order pricing request is subjected to category verification, order amount verification, and single product percentage verification. If the category coverage verification, order amount verification, and single category percentage verification all pass, then the discount multiplier for each SKU object is determined. Calculate the amount payable for each SKU object according to the corresponding discount rate; Calculate the total order amount based on the payable amount for each SKU object.

2. The method according to claim 1, characterized in that, After receiving the order pricing request, the method further includes: The SKU details corresponding to the order pricing request are loaded in batches according to the SKU identifier; each SKU detail includes: the price, category and discount rule identifier of the SKU object.

3. The method according to claim 2, characterized in that, The steps for verifying the coverage categories include: Determine the category quantity of all SKU objects in the order pricing request; Compare the number of product categories for all SKU objects in the order pricing request with the product category quantity threshold; If the number of categories of all SKU objects in the order pricing request is not less than the category quantity threshold, then the coverage category verification passes.

4. The method according to claim 2, characterized in that, The order amount verification steps include: Calculate the original total order amount based on the price of the SKU and the quantity purchased; Compare the original total amount of the order with the amount threshold; If the original total amount of the order is not less than the amount threshold, then the order amount verification passes.

5. The method according to claim 2, characterized in that, The steps for verifying the percentage of a single product category include: Based on the price, category, and quantity of the SKU object, calculate the original total order amount and the original amount for each category; Based on the original amount of each product category and the original total amount of the order, determine the proportion of the amount corresponding to the largest single product category in the current order in the original total amount of the order; If the percentage of the amount corresponding to the largest single category in the current order in the original total amount of the order is not greater than the percentage threshold, then the percentage verification of the single category passes.

6. The method according to claim 2, characterized in that, The steps for determining the discount multiplier for each SKU object include: A discount rule identifier for each SKU object is determined based on the SKU identifier of each SKU object; the discount rule identifier includes: a first discount rule identifier, a second discount rule identifier, and a third discount rule identifier; In response to the first discount rule identifier corresponding to the SKU object, the original total amount of the order is calculated based on the price of the SKU object and the purchase quantity, and the discount multiplier corresponding to the current SKU object is determined based on the original total amount of the order. In response to the second discount rule identifier corresponding to the SKU object, the discount multiplier corresponding to the current SKU object is determined based on the purchase quantity of the SKU object; In response to the third discount rule identifier corresponding to the SKU object, the discount multiplier of the current SKU object is determined to be 1.

7. The method according to claim 1, characterized in that, Before calculating the total order amount based on the payable amount for each SKU object, the method further includes: Determine the preset base price for each SKU object; For each SKU object, calculate the discounted unit price of the SKU object according to the discount rate; If the discounted unit price is less than the preset base price, the amount payable for the current SKU object is calculated based on the preset base price.

8. The method according to claim 1, characterized in that, Before calculating the total order amount based on the payable amount for each SKU object, the method further includes: Determine the premium factor for each SKU object; For each SKU object, the amount payable for each SKU object is calculated based on the corresponding discount rate and the premium coefficient.

9. The method according to claim 1, characterized in that, After calculating the total order amount based on the payable amount for each SKU object, the method further includes: Obtain the profit-sharing rules; Based on the profit-sharing rules and the total order amount, a profit-sharing breakdown is generated.

10. A device for calculating the amount of a combined order, characterized in that, The device includes: A receiving unit is configured to receive an order pricing request, wherein the order pricing request includes at least two SKU objects, each of which includes: an SKU identifier and a purchase quantity; The verification unit is configured to perform category verification, order amount verification, and single product percentage verification on the order pricing request based on the SKU identifier and the purchase quantity. The discount determination unit is configured to determine the discount multiplier for each SKU object in response to the passing of the coverage category verification, order amount verification, and single category percentage verification. The first amount calculation unit is configured to calculate the amount payable for each SKU object according to the corresponding discount rate; The second amount calculation unit is configured to calculate the total order amount based on the payable amount for each SKU object.

Images