Gift electronic mall online purchase transaction system and method

Abstract

The application discloses a kind of gift electronic mall online purchase transaction system and method, it is related to the technical field of e-commerce, including, receiving the gift purchase demand submitted by procurement party in gift electronic mall, the gift purchase demand is converted into procurement constraint condition, and procurement constraint condition is matched with product transaction data in product data management library, and candidate gift purchase scheme is generated;Candidate gift purchase scheme is checked in the current transaction state under transaction performance, and transaction performance checking result is obtained, and from candidate gift purchase scheme, the product transaction data that meets procurement constraint condition and is checked in the current transaction state under transaction performance is determined target gift purchase scheme.The application is converted into procurement constraint condition by gift purchase demand, and is matched with product transaction data in product data management library and checked in the current transaction state under transaction performance, and the problem that product data management and procurement transaction are insufficiently connected is solved.

Description

Technical Field

[0001] This invention relates to the field of e-commerce technology, and in particular to an online procurement and transaction system and method for gift e-commerce. Background Technology

[0002] As e-commerce platforms develop towards corporate procurement, customized transactions, and supply chain collaboration, online gift malls have been widely used in scenarios such as employee benefits, business gifts, and event material procurement. Online gift procurement involves not only product selection and order generation, but also product data management such as product specifications, inventory, pricing, customization, packaging, and delivery. For bulk and customized procurement, buyers are more concerned about the consistency of product data, the fulfillment of procurement plans, and the traceability of the fulfillment process.

[0003] However, existing methods have some shortcomings. The relationship between procurement needs and product transaction data largely relies on product screening or manual confirmation. The purpose of gifts, procurement quantity, budget, customization requirements, and delivery requirements are difficult to reliably translate into procurement constraints. This results in the inventory, pricing, customization rules, and delivery conditions in the product data management database not fully corresponding to procurement needs, and the procurement plan may lack a real basis for fulfillment. In addition, the product data after order confirmation lacks a fixed version benchmark. There is no stable correspondence between the product transaction data at the time of confirmation by the purchaser, the transaction fulfillment verification results, and the fulfillment node data submitted by the supplier. When the product data management database is updated, it is easy for the basis for fulfillment comparison to deviate from the content confirmed by the purchaser, making it difficult to identify problems such as specification replacement, customization deviation, packaging changes, or delivery inconsistencies in a timely manner. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides an online procurement and transaction method for gift e-commerce platforms to solve the problems of insufficient connection between procurement needs and product transaction data, as well as the tendency for the performance comparison benchmark to deviate after order confirmation.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides an online procurement transaction method for a gift e-commerce platform, comprising: receiving a gift procurement request submitted by a purchaser in the gift e-commerce platform; converting the gift procurement request into procurement constraints; matching the procurement constraints with product transaction data in a product data management database to generate candidate gift procurement schemes; performing a transaction fulfillment verification on the candidate gift procurement schemes under the current transaction status to obtain a transaction fulfillment verification result; and determining a target gift procurement scheme from the candidate gift procurement schemes whose product transaction data meets the procurement constraints and passes the transaction fulfillment verification under the current transaction status; responding to the purchaser's confirmation operation on the target gift procurement scheme; solidifying the product transaction data and transaction fulfillment verification result corresponding to the target gift procurement scheme into an order version data record to generate order data to be fulfilled; performing field ordering and summary calculation on the order version data record in the order data to be fulfilled to generate a product data fingerprint; verifying and determining the corresponding order version data record based on the product data fingerprint during the order fulfillment process; comparing the fulfillment node data submitted by the supplier with the order version data record to identify the offset of the fulfillment node data relative to the order version data record; and generating a transaction control result.

[0007] As a preferred embodiment of the online procurement transaction method of the gift e-commerce platform described in this invention, the gift procurement demand refers to the data content submitted by the purchaser in the gift e-commerce platform, which represents the procurement object, transaction conditions, and delivery requirements.

[0008] As a preferred embodiment of the online procurement and transaction method for gift e-commerce described in this invention, the specific steps for converting gift procurement needs into procurement constraints are as follows: The procurement objects, transaction conditions, and delivery requirements in the gift procurement needs are organized into fields to obtain fielded gift procurement needs; Based on the field-based gift procurement requirements, the procurement objects, transaction conditions, and delivery requirements are converted into procurement constraints for matching product transaction data.

[0009] As a preferred embodiment of the online procurement and transaction method for gift e-commerce described in this invention, the procurement constraints include constraints on the procurement object, constraints on transaction conditions, and constraints on delivery requirements. The constraints on the procurement object are used to match the product category, applicable scenario, and product attributes in the product transaction data; The transaction condition constraints are used to match the available quantity, transaction price, and customization rules in the product transaction data; The delivery requirement constraints are used to match the delivery cycle, delivery area, packaging rules, and delivery conditions in the product transaction data.

[0010] As a preferred embodiment of the online procurement and transaction method for gift e-commerce described in this invention, the specific steps for matching procurement constraints with product transaction data in the product data management database to generate candidate gift procurement plans are as follows: Based on the constraints of the procurement object, search for product transaction data in the product data management database to obtain the product transaction data corresponding to the constraints of the procurement object. In the product transaction data corresponding to the constraints of the procurement object, continue to match according to the constraints of the transaction conditions to obtain product transaction data that simultaneously meets the constraints of the procurement object and the constraints of the transaction conditions. Based on the delivery requirement constraints, product transaction data that simultaneously meets the procurement object constraints and transaction condition constraints are matched for delivery to obtain product transaction data that meets the procurement constraints. Product transaction data that meet the procurement constraints are aggregated according to the same gift procurement needs to form candidate gift procurement plans.

[0011] As a preferred embodiment of the online procurement and transaction method for gift e-commerce described in this invention, the transaction fulfillment verification refers to, after generating a candidate gift procurement plan, combining the current transaction status data corresponding to the candidate gift procurement plan, verifying the product conditions, transaction conditions, and delivery conditions of the product transaction data corresponding to the candidate gift procurement plan, so as to determine whether the candidate gift procurement plan can be fulfilled under the current transaction status. The current transaction status data includes product availability, inventory availability, valid quote status, custom fulfillment status, packaging availability, and delivery coverage status.

[0012] As a preferred embodiment of the online procurement and transaction method for gift e-commerce described in this invention, the specific steps for verifying the fulfillment of candidate gift procurement plans are as follows: Based on the procurement constraints and the current transaction status data corresponding to the candidate gift procurement schemes, the product transaction data corresponding to the candidate gift procurement schemes are organized to form transaction fulfillment verification items; According to the transaction fulfillment verification items, the product transaction data and current transaction status data corresponding to the candidate gift procurement plan are verified for product conditions, transaction conditions and delivery conditions to obtain the transaction fulfillment verification results; Based on the transaction fulfillment verification results, the candidate gift procurement schemes that meet the corresponding constraints in the current transaction status, including product conditions, transaction conditions, and delivery conditions, are determined as the target gift procurement schemes.

[0013] As a preferred embodiment of the online procurement transaction method for gift e-commerce described in this invention, the order version data record refers to the data record formed after the purchaser confirms the target gift procurement plan, which includes the target gift procurement plan identifier, the product transaction data corresponding to the target gift procurement plan, the transaction fulfillment verification result, the fixed correspondence between the product transaction data and the transaction fulfillment verification result, and the version generation time.

[0014] As a preferred embodiment of the online procurement transaction method for gift e-commerce described in this invention, the specific steps for generating the transaction control result are as follows: The order version data records in the order fulfillment data are ordered by fields and the summary is calculated to generate product data fingerprints and establish the correspondence between product data fingerprints and order version data records. During the order fulfillment process, the corresponding order version data record is determined by verifying the product data fingerprint. The determined order version data record is used as the benchmark for comparing the fulfillment node data. The fulfillment node data submitted by the supplier is organized according to the fields corresponding to the procurement object, transaction conditions and delivery requirements to obtain comparable fulfillment node data. The comparable fulfillment node data is compared with the order version data record, which serves as the benchmark for comparison of fulfillment node data, to identify the offset of fulfillment node data relative to the order version data record, and to generate transaction control results based on the offset identification results. The transaction control results are used to determine the corresponding processing status of pending order data, including continued performance status, suspended performance status, return to supplier for correction status, and purchaser review status.

[0015] Secondly, this invention provides an online procurement and transaction system for a gift e-commerce platform, comprising: a demand matching module, a performance verification module, a version fixing module, and a fingerprint comparison module; the demand matching module is used to receive gift procurement demands submitted by the purchaser in the gift e-commerce platform, convert the gift procurement demands into procurement constraints, and match the procurement constraints with product transaction data in the product data management database to generate candidate gift procurement plans; the performance verification module is used to verify the performance of candidate gift procurement plans under the current transaction status, obtain the performance verification result, and determine from the candidate gift procurement plans that the product transaction data meets the procurement constraints and passes the performance verification under the current transaction status. The system includes: a target gift procurement plan for easy fulfillment verification; a version solidification module, used to respond to the purchaser's confirmation of the target gift procurement plan, solidifying the product transaction data and transaction fulfillment verification results corresponding to the target gift procurement plan into order version data records, generating order data to be fulfilled; and a fingerprint comparison module, used to perform field ordering and summary calculation on the order version data records in the order data to be fulfilled, generating product data fingerprints. During the order fulfillment process, the system verifies and determines the corresponding order version data records based on the product data fingerprints, compares the fulfillment node data submitted by the supplier with the order version data records, identifies the offset of the fulfillment node data relative to the order version data records, and generates transaction control results.

[0016] The beneficial effects of this invention are as follows: By converting gift procurement needs into procurement constraints and matching them with product transaction data in the product data management database and verifying transaction fulfillment, the problem of insufficient connection between product data management and procurement transactions is solved, thereby improving the matching accuracy and fulfillment of gift procurement plans; by solidifying product transaction data and transaction fulfillment verification results into order version data records and comparing fulfillment node data based on product data fingerprints, the problem of easy deviation of the fulfillment comparison benchmark after order confirmation is solved, thereby improving the consistency of transaction data and the stability of fulfillment control. Attached Figure Description

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

[0018] Figure 1 This is a flowchart illustrating the online purchasing and transaction process for a gift e-commerce platform.

[0019] Figure 2 This is a schematic diagram of an online procurement and transaction system for a gift e-commerce platform.

[0020] Figure 3 Flowchart for matching procurement constraints.

[0021] Figure 4 This is a flowchart for verifying the fulfillment of a transaction.

[0022] Figure 5 A flowchart for recording and comparing order version data for fulfillment.

[0023] Figure 6 This is a time-series data comparison chart of the accuracy of contract performance control.

[0024] Figure 7 A comparison chart of procurement matching and performance control indicators. Detailed Implementation

[0025] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0026] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0027] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0028] Reference Figures 1-7 As an embodiment of the present invention, this embodiment provides an online procurement and transaction method for gift e-commerce, including the following steps: In this embodiment, the online procurement transaction method of the gift e-commerce platform is executed by the gift e-commerce platform server. The purchasing terminal is used to submit gift procurement requirements and confirm the target gift procurement plan. The supplier terminal is used to submit product transaction data and fulfillment node data in the order fulfillment process. The product data management library is used to store the product transaction data after field processing. The gift e-commerce platform server interacts with the purchasing terminal, supplier terminal and product data management library respectively, and performs gift procurement requirement field processing, procurement constraint matching, transaction fulfillment verification, order version data record generation, product data fingerprint generation, fulfillment node data comparison and transaction control result generation.

[0029] S1. Receive gift procurement requests submitted by the purchaser in the gift e-commerce platform, convert the gift procurement requests into procurement constraints, and match the procurement constraints with the product transaction data in the product data management database to generate candidate gift procurement plans.

[0030] S1.1 Receive the gift procurement requirements submitted by the purchaser in the gift e-commerce platform, and organize the procurement objects, transaction conditions and delivery requirements in the gift procurement requirements into fields to obtain the fielded gift procurement requirements.

[0031] It should be noted that after receiving the gift procurement requirements submitted by the purchaser, the gift e-commerce platform reads the content filled in on the page, the selected content, and the uploaded customized instructions in the gift procurement requirements. It then organizes the text content, option content, and uploaded customized instructions into a unified gift procurement requirement content that can be processed into fields. It also sorts out invalid blanks, duplicate expressions, and inconsistent formats in the gift procurement requirement content that can be processed into fields, and standardizes the field names, expressions, and units of measurement in the gift procurement requirement content, so that the gift procurement requirement content can be processed into fields according to the procurement object, transaction conditions, and delivery requirements.

[0032] After formatting, based on the meaning expressed in the gift procurement requirements, the requirements are divided into three parts: procurement object, transaction conditions, and delivery requirements. The procurement object indicates the category, purpose, and attributes of the gifts the buyer wishes to purchase. The transaction conditions indicate the quantity, budget, price range, and customization requirements proposed by the buyer. The delivery requirements indicate the delivery deadline, receiving area, packaging requirements, and distribution requirements proposed by the buyer.

[0033] Furthermore, the procurement object is organized into a procurement object field, the transaction conditions into a transaction condition field, and the delivery requirements into a delivery requirement field. The names, formats, and units of the procurement object field, transaction condition field, and delivery requirement field are also made consistent, so that the procurement object field, transaction condition field, and delivery requirement field correspond to the procurement object, transaction conditions, and delivery requirements in the gift procurement requirements, respectively. Field content that does not correspond to the content of the gift procurement requirements is not retained as a fielding result.

[0034] The procurement object field, transaction condition field, and delivery requirement field that have been consistent and organized are linked and saved to form a fielded gift procurement requirement.

[0035] S1.2. Based on the field-based gift procurement requirements, convert the procurement object, transaction conditions, and delivery requirements into procurement constraints for matching product transaction data.

[0036] It should be noted that the purchase object field, transaction condition field, and delivery requirement field in the fieldized gift purchase requirements should be verified for completeness, and the field content that corresponds to the content of the gift purchase requirements should be retained; field content that is not filled in, cannot be identified, or is inconsistent with the content of the gift purchase requirements should not be included as part of the purchase constraints.

[0037] Furthermore, the gift category, gift purpose, and gift attributes in the "Purchase Object" field are used as matching conditions for the product category, applicable scenario, and product attributes in the product transaction data, respectively, forming the "Purchase Object" constraint content; the purchase quantity in the "Transaction Conditions" field is used as the matching condition for the available quantity in the product transaction data; the purchase budget and transaction price range are used together as the matching condition for the transaction quotation in the product transaction data; and the customization requirements are used as the matching condition for the customization rules in the product transaction data, forming the "Transaction Conditions" constraint content; the delivery deadline, receiving area, packaging requirements, and delivery requirements in the "Delivery Requirements" field are used as matching conditions for the delivery cycle, delivery area, packaging rules, and delivery conditions in the product transaction data, respectively, forming the "Delivery Requirements" constraint content.

[0038] During the above conversion process, the field names, field contents, and units of measurement in the fieldized gift procurement requirements are organized accordingly, so that the procurement object field, transaction condition field, and delivery requirement field are converted into matching conditions that can be compared with the product transaction data. Among them, the field name is used to determine the corresponding data item in the product transaction data, the field content is used to determine the content that the corresponding data item needs to meet, and the unit of measurement is used to determine the comparison basis for quantity, price, period, and regional scope.

[0039] The constraints on the procurement object, the transaction conditions, and the delivery requirements are linked together to form procurement constraints.

[0040] S1.3 Match the procurement constraints with the product transaction data in the product data management database, filter the product transaction data that meets the procurement constraints, and generate candidate gift procurement plans.

[0041] It should be noted that the product data management database is the basic database used by the gift e-commerce platform to manage tradable gift data. The product transaction data in the product data management database comes from the product listing information, inventory information, quotation information, customization information, packaging information and delivery information submitted by suppliers. After being organized by field name, field content and unit of measurement, it forms data records that can be used for online procurement transactions.

[0042] Furthermore, the product transaction data has data items corresponding to the constraints of the procurement object, the constraints of the transaction conditions, and the constraints of the delivery requirements. Among them, the data items corresponding to the constraints of the procurement object include product category, applicable scenario, and product attributes; the data items corresponding to the constraints of the transaction conditions include available quantity, transaction price, and customization rules; and the data items corresponding to the constraints of the delivery requirements include delivery cycle, delivery area, packaging rules, and delivery conditions.

[0043] During the matching process, product transaction data is searched in the product data management database based on the constraints of the procurement object. The product category, applicable scenario, and product attributes in the product transaction data are matched with the gift category, gift purpose, and gift attributes in the constraints of the procurement object, respectively, to obtain product transaction data that corresponds to the constraints of the procurement object. Product transaction data that cannot be matched with the constraints of the procurement object will not be included in the subsequent matching.

[0044] Furthermore, the product transaction data corresponding to the constraints of the procurement object is further matched with the constraints of the transaction conditions to ensure that the available quantity in the product transaction data meets the procurement quantity requirements, that the transaction price in the product transaction data meets the procurement budget and transaction price range requirements, and that the customized rules in the product transaction data meet the customization requirements, thus obtaining product transaction data that simultaneously meets the constraints of the procurement object and the constraints of the transaction conditions.

[0045] Furthermore, the product transaction data that simultaneously meets the constraints of the procurement object and the transaction conditions is further matched with the constraints of the delivery requirements, so that the delivery cycle in the product transaction data meets the delivery deadline requirements, the delivery area in the product transaction data covers the receiving area, the packaging rules in the product transaction data meet the packaging requirements, and the delivery conditions in the product transaction data meet the delivery requirements, thus obtaining product transaction data that meets the procurement constraints.

[0046] Product transaction data that meets the procurement constraints are aggregated according to the same gift procurement needs, and the aggregated product transaction data is used to form candidate gift procurement plans.

[0047] S2. Perform transaction fulfillment verification on the candidate gift procurement schemes under the current transaction status, obtain the transaction fulfillment verification results, and determine the target gift procurement scheme from the candidate gift procurement schemes whose product transaction data meets the procurement constraints and passes the transaction fulfillment verification under the current transaction status.

[0048] S2.1 Based on the procurement constraints and the current transaction status data corresponding to the candidate gift procurement schemes, organize the product transaction data corresponding to the candidate gift procurement schemes to form a transaction fulfillment verification item for determining whether the candidate gift procurement schemes can be fulfilled under the current transaction status.

[0049] It should be noted that the above matching is used to filter product transaction data that meets the procurement constraints from the product data management library. The transaction fulfillment verification is used to determine whether the candidate gift procurement plan still meets the fulfillment conditions after the candidate gift procurement plan is generated, based on the current transaction status data corresponding to the candidate gift procurement plan. The current transaction status data includes product availability status, inventory availability status, quotation validity status, customization fulfillment status, packaging availability status, and delivery coverage status. Product availability status is used to determine whether the product category, applicable scenario, and product attributes still correspond to the procurement object constraints. Inventory availability status is used to determine whether the available quantity meets the procurement quantity in the procurement constraints. Quotation validity status is used to determine whether the transaction quotation is within the procurement budget and transaction price range in the procurement constraints. Customization fulfillment status is used to determine whether the customization rules can meet the customization requirements in the procurement constraints. Packaging availability status is used to determine whether the packaging rules can meet the packaging requirements in the procurement constraints. Delivery coverage status is used to determine whether the delivery area and delivery conditions can meet the receiving area and delivery requirements in the procurement constraints.

[0050] Specifically, based on the procurement object constraints in the procurement constraints, data related to product category, applicable scenario, and product attribute are extracted from the product transaction data and product availability status corresponding to the candidate gift procurement schemes. The extracted data is then organized into product condition verification items. These product condition verification items are used to subsequently determine whether the product category, applicable scenario, product attribute, and product availability status in the candidate gift procurement schemes comply with the procurement object constraints.

[0051] Based on the transaction constraints in the procurement constraints, data related to the available quantity, transaction price, and customization rules are extracted from the product transaction data, inventory availability, quotation validity, and customization fulfillment status corresponding to the candidate gift procurement schemes. The extracted data is then organized into transaction condition verification items. These verification items are used to subsequently determine whether the available quantity, transaction price, customization rules, inventory availability, quotation validity, and customization fulfillment status in the candidate gift procurement schemes comply with the transaction constraint requirements.

[0052] Based on the delivery requirements constraints in the procurement constraints, data related to delivery cycle, delivery area, packaging rules, and delivery coverage are extracted from the product transaction data, packaging availability status, and delivery coverage status corresponding to the candidate gift procurement schemes. The extracted data is then organized into delivery condition verification items. These delivery condition verification items are used to subsequently determine whether the delivery cycle, delivery area, packaging rules, delivery conditions, packaging availability status, and delivery coverage status in the candidate gift procurement schemes meet the delivery requirements constraints.

[0053] The product condition verification items, transaction condition verification items, and delivery condition verification items are associated with the same candidate gift procurement plan to form transaction fulfillment verification items.

[0054] S2.2. According to the transaction fulfillment verification items, verify the product transaction data and current transaction status data corresponding to the candidate gift procurement plan for product conditions, transaction conditions and delivery conditions, and obtain the transaction fulfillment verification results.

[0055] It should be noted that during product condition verification, the product category, applicable scenario, and product attributes in the product condition verification items are compared with the gift category, gift purpose, and gift attributes in the procurement object constraints. The correspondence refers to: the product category field content is consistent with the gift category field content, or the product category field content belongs to the category range defined by the gift category field content; the applicable scenario field content is consistent with the gift purpose field content, or the applicable scenario field content covers the gift purpose field content; the attribute name and attribute value in the product attribute field cover the attribute name and attribute value in the gift attribute field. When the product category, applicable scenario, and product attributes all meet the above correspondence, and the product availability status is available, the product condition is determined to meet the procurement object constraints. When any content does not meet the above correspondence, or the product availability status is not available, the product condition is determined to not meet the procurement object constraints.

[0056] When verifying transaction conditions, the available quantity, transaction price, and customization rules in the transaction condition verification items are compared with the purchase quantity, purchase budget, transaction price range, and customization requirements in the transaction condition constraints. The judgment is also made in conjunction with the inventory availability status, quotation validity status, and customization fulfillment status. If the available quantity is not less than the purchase quantity, the inventory availability status is available, the transaction price is not higher than the purchase budget and falls within the transaction price range, the quotation validity status is valid, the customization rules meet the customization requirements, and the customization fulfillment status is fulfillable, then the transaction conditions are deemed to comply with the transaction condition constraints. If any of these conditions are not met, or if the inventory availability status is not available, the quotation validity status is not valid, or the customization fulfillment status is not fulfillable, then the transaction conditions are deemed to not comply with the transaction condition constraints.

[0057] When verifying delivery conditions, the delivery cycle, delivery area, packaging rules, and delivery conditions in the delivery condition verification items are compared with the delivery deadline, receiving area, packaging requirements, and delivery requirements in the delivery requirement constraints, and the judgment is made in conjunction with the packaging availability status and delivery coverage status. When the delivery cycle does not exceed the delivery deadline, the delivery area covers the receiving area, the packaging rules meet the packaging requirements, the packaging availability status is available, the delivery conditions meet the delivery requirements, and the delivery coverage status is coverable, the delivery conditions are determined to meet the delivery requirement constraints. When any item does not meet the delivery requirement constraints, or the packaging availability status is not available, or the delivery coverage status is not coverable, the delivery conditions are determined to not meet the delivery requirement constraints.

[0058] The determination of product conditions, transaction conditions, and delivery conditions is linked to the same candidate gift procurement plan to form a transaction fulfillment verification result. Among them, a candidate gift procurement plan that meets all the corresponding constraints in the product conditions, transaction conditions, and delivery conditions is marked as meeting the transaction fulfillment verification in the transaction fulfillment verification result; a candidate gift procurement plan that does not meet any of the product conditions, transaction conditions, and delivery conditions in the transaction fulfillment verification result is marked as not meeting the transaction fulfillment verification, and the content that does not meet the corresponding constraint is recorded.

[0059] The expression for verifying the fulfillment of a transaction is: ; ; in, Indicates the first The results of the transaction fulfillment verification of each candidate gift procurement plan; Indicates the first The first of the candidate gift procurement plans Does the data item satisfy the condition of the first...? Class constraints, when When, it indicates that the corresponding transaction fulfillment verification item is met. When this condition is met, it indicates that the corresponding transaction fulfillment verification item is not satisfied. Indicates the first One candidate gift procurement plan; This represents a set of target gift procurement options; This represents an index of candidate gift procurement schemes; This represents the index of the data item in the candidate gift procurement plan; Indicates the constraint type, with values... , and ; Indicate the procurement target; Indicates the terms of the transaction; Indicates delivery requirements; Indicates the first A set of data items under class constraints.

[0060] No. Each data item includes product transaction data items and current transaction status data items corresponding to the candidate gift procurement plan; the current transaction status data items include product availability status, inventory availability status, valid quotation status, customized fulfillment status, packaging availability status, and delivery coverage status.

[0061] S2.3. Based on the transaction fulfillment verification results, the candidate gift procurement schemes that meet the corresponding constraints in the current transaction status are determined as the target gift procurement schemes.

[0062] It should be noted that the candidate gift procurement plans are distinguished according to the transaction fulfillment verification results. Candidate gift procurement plans marked as not meeting the transaction fulfillment verification are excluded from the scope of the target gift procurement plan, while candidate gift procurement plans marked as meeting the transaction fulfillment verification are considered as determinable objects.

[0063] Furthermore, the identifiable objects are confirmed to ensure that the product conditions, transaction conditions, and delivery conditions in the transaction fulfillment verification results are all compliant. Among them, compliance of product conditions indicates that the product category, applicable scenario, and product attributes meet the constraints of the procurement object; compliance of transaction conditions indicates that the available quantity, transaction price, and customization rules meet the constraints of the transaction conditions; and compliance of delivery conditions indicates that the delivery cycle, delivery area, packaging rules, and delivery conditions meet the constraints of the delivery requirements.

[0064] If the product conditions, transaction conditions, and delivery conditions are all met, the candidate gift procurement plan is identified as a target gift procurement plan that satisfies the procurement constraints and has the conditions for performance. Here, having the conditions for performance means that the product transaction data and current transaction status data corresponding to the candidate gift procurement plan can meet the corresponding constraints in terms of product conditions, transaction conditions, and delivery conditions.

[0065] The target gift procurement plan is linked and saved with the corresponding product transaction data and transaction fulfillment verification results. This allows the target gift procurement plan to be used as the object of subsequent confirmation by the purchaser, and the corresponding product transaction data and transaction fulfillment verification results can be solidified into order version data records in the future.

[0066] S3. Respond to the purchaser's confirmation of the target gift procurement plan, solidify the product transaction data and transaction fulfillment verification results corresponding to the target gift procurement plan into order version data records, and generate order data to be fulfilled.

[0067] S3.1 Response to the purchaser's confirmation of the target gift procurement plan, confirm the correspondence between the product transaction data corresponding to the target gift procurement plan and the transaction fulfillment verification result, and obtain the confirmed product transaction data and the corresponding transaction fulfillment verification result.

[0068] It should be noted that the gift e-commerce platform determines the confirmed target gift procurement plan and obtains the associated product transaction data and transaction fulfillment verification results stored in the target gift procurement plan, so that the target gift procurement plan confirmed by the purchaser, the product transaction data, and the transaction fulfillment verification results correspond to the same target gift procurement plan.

[0069] Furthermore, the product transaction data corresponding to the target gift procurement plan is verified against the transaction fulfillment verification results. This verifies that the product category, applicable scenarios, and product attributes in the product transaction data correspond to the product condition judgment content in the transaction fulfillment verification results. It also verifies that the available quantity, transaction price, and customization rules in the product transaction data correspond to the transaction condition judgment content in the transaction fulfillment verification results. Finally, it verifies that the delivery cycle, delivery area, packaging rules, and delivery conditions in the product transaction data correspond to the delivery condition judgment content in the transaction fulfillment verification results.

[0070] During the aforementioned confirmation process, when all items in the product transaction data correspond to the corresponding judgment items in the transaction fulfillment verification result, and the corresponding judgment items all come from the product transaction data and the current transaction status data, the product transaction data is determined as the confirmed product transaction data, and the corresponding transaction fulfillment verification result is used as the transaction fulfillment verification result corresponding to the confirmed product transaction data; when any item in the product transaction data does not correspond to the corresponding judgment item in the transaction fulfillment verification result, the product transaction data is not used as the confirmed product transaction data, and subsequent version solidification processing of the product transaction data is stopped.

[0071] S3.2. Solidify the confirmed product transaction data and the corresponding transaction fulfillment verification results into a version and generate an order version data record.

[0072] It should be noted that version solidification refers to saving the confirmed product transaction data, the corresponding transaction fulfillment verification results, and the correspondence between the two as fixed version content after the purchaser confirms the target gift procurement plan. This ensures that the order version data records used for subsequent fulfillment comparisons are consistent with the content confirmed by the purchaser.

[0073] Specifically, the confirmed product transaction data is recorded and organized, and then arranged according to the correspondence between the purchase object, transaction conditions and delivery requirements to form the product transaction data content to be solidified.

[0074] Furthermore, the corresponding transaction fulfillment verification results are associated with the product transaction data content to be solidified, so that the judgment content of product conditions, transaction conditions and delivery conditions corresponds to the corresponding content in the product transaction data content to be solidified; during the association process, the judgment content that meets the transaction fulfillment verification is retained, and the content of candidate gift procurement schemes that have not participated in the confirmation of the target gift procurement scheme is not written into the product transaction data content to be solidified.

[0075] Furthermore, the product transaction data to be solidified and the corresponding transaction fulfillment verification results are fixedly stored, so that the product transaction data and transaction fulfillment verification results corresponding to the same target gift procurement plan form a fixed correspondence.

[0076] The product transaction data content that has been fixed and saved, the corresponding transaction fulfillment verification results, and the fixed correspondence between the two are associated to generate order version data records.

[0077] Furthermore, the order version data record includes the order version identifier, the target gift procurement plan identifier, the confirmed product transaction data, the corresponding transaction fulfillment verification result, the fixed correspondence, and the version generation time. After the order version data record is generated, it will not be replaced by subsequent updates to inventory information, quotation information, customization information, packaging information, and delivery information in the product data management database. When the product transaction data in the product data management database is updated, the updated product transaction data will not overwrite the already generated order version data record.

[0078] S3.3 Generate pending order data based on order version data records.

[0079] It should be noted that the order version data record is used to represent the fixed version content formed when the purchaser confirms it, while the order data to be fulfilled is used to represent the order processing object that has entered the fulfillment stage. The order version data record is used as the basic content of the order data to be fulfilled, and the product transaction data and transaction fulfillability verification results in the order version data record are not regenerated or replaced, so that the order data to be fulfilled can continue the fixed content after the purchaser confirms it.

[0080] Specifically, the order version data record is associated with the order identification content formed after the purchaser confirms the target gift procurement plan, so that the order data to be fulfilled can correspond to the order version data record; the order identification content is used to distinguish the orders confirmed by different purchasers, without changing the product transaction data and transaction fulfillment verification results in the order version data record.

[0081] Furthermore, according to the procurement object, transaction conditions, and delivery requirements in the order version data record, the order data to be fulfilled is organized accordingly, so that the order data to be fulfilled retains the product transaction data, transaction fulfillment verification results, and the correspondence between the order version data records for subsequent performance comparison.

[0082] After completing the corresponding organization, the order version data record is written into the pending order data, so that the pending order data carries the order version data record confirmed by the purchaser, and serves as the processing object in the subsequent order fulfillment process.

[0083] It should also be noted that existing technologies typically generate ordinary order data directly after the purchaser confirms the order, without solidifying the product transaction data and transaction fulfillment verification results at the time of purchase confirmation. This leads to inconsistencies between the data benchmark used for fulfillment comparison and the data content at the time of purchase confirmation when subsequent product data is updated. This solution solidifies the product transaction data and transaction fulfillment verification results at the time of purchase confirmation into order version data records, ensuring that the data for orders to be fulfilled continues the fixed content at the time of purchase confirmation. This provides a stable data benchmark for subsequent data comparison at fulfillment nodes, avoids drift in the fulfillment comparison benchmark caused by product data updates, and improves the data consistency and transaction processing stability of order fulfillment comparison.

[0084] S4. Perform field ordering and summary calculation on the order version data records in the order data to be fulfilled, generate product data fingerprints, verify and determine the corresponding order version data records based on the product data fingerprints during the order fulfillment process, compare the fulfillment node data submitted by the supplier with the order version data records, identify the offset of the fulfillment node data relative to the order version data records, and generate transaction control results.

[0085] S4.1 Perform field sorting and summary calculation on the order version data records in the order data to be fulfilled, generate product data fingerprints, and establish the correspondence between product data fingerprints and order version data records.

[0086] It should be noted that the purpose of order version data records is to ensure that the content in the order version data records participates in subsequent summary calculations in a fixed field order, thereby avoiding the generation of different product data fingerprints for the same content due to different field arrangement orders.

[0087] Specifically, order version data records are read from the pending order data, and the product transaction data in the order version data records are sorted by field according to the order of purchase object, transaction conditions and delivery requirements. Among them, the purchase object corresponds to the product category, applicable scenario and product attributes, the transaction conditions correspond to the available quantity, transaction price and customization rules, and the delivery requirements correspond to the delivery cycle, delivery area, packaging rules and delivery conditions.

[0088] Furthermore, the transaction fulfillment verification results in the order version data record are ordered by field according to the order of product conditions, transaction conditions, and delivery conditions, so that the transaction fulfillment verification results correspond to the product transaction data with the completed field ordering; wherein, the judgment content of product conditions corresponds to the procurement object in the order version data record, the judgment content of transaction conditions corresponds to the transaction conditions in the order version data record, and the judgment content of delivery conditions corresponds to the delivery requirements in the order version data record.

[0089] After the field ordering is completed, the order version data records with fixed field names, content, and order are used as the objects for summary calculation. Specifically, the order version identifier, target gift procurement plan identifier, version generation time, product category, applicable scenario, product attributes, available quantity, transaction price, customization rules, delivery cycle, delivery area, packaging rules, delivery conditions, product condition judgment content, transaction condition judgment content, and delivery condition judgment content are sequentially concatenated according to the field order to obtain the data to be summarized. A hash digest is then calculated on the data to be summarized to obtain a summary value that can identify the content of the order version data record. This summary value is used as the product data fingerprint. The target gift procurement scheme identifier is used to identify the target gift procurement scheme corresponding to the order version data record. The version generation time is used to determine the solidification time of the order version data record. The hash digest calculation can use the SHA-256 algorithm, the SM3 algorithm, or a digest algorithm that can generate a fixed digest value based on the data to be digested. The product data fingerprint is used to represent the content of the order version data record after the purchaser confirms it. When any of the target gift procurement scheme identifier, version generation time, product transaction data, or transaction fulfillment verification result in the order version data record changes, or the order of the fields changes, the product data fingerprint obtained by the digest calculation will change accordingly.

[0090] The product data fingerprint expression is: ; in, Represents product data fingerprint; This indicates the order version data record; This represents the order version data records after being sorted by the fields; This indicates summary calculation, which can generate summary values ​​based on order version data records ordered by fields.

[0091] The product data fingerprint is associated with and saved with the order version data record, and the product data fingerprint is written into the order data to be fulfilled, so that a corresponding relationship is formed between the product data fingerprint and the order version data record.

[0092] S4.2 During the order fulfillment process, the corresponding order version data record is determined by verifying the product data fingerprint. The determined order version data record is used as the benchmark for comparing the fulfillment node data. The fulfillment node data submitted by the supplier is organized according to the fields corresponding to the procurement object, transaction conditions and delivery requirements to obtain comparable fulfillment node data.

[0093] It should be noted that the fulfillment node data submitted by the supplier represents the actual fulfillment content submitted by the supplier for the order to be fulfilled during the order fulfillment process. The fulfillment node data must include at least fields that correspond to the procurement object, transaction conditions, and delivery requirements in the order version data record. Specifically, the fields corresponding to the procurement object include actual fulfillment content that corresponds to the product category, applicable scenario, and product attributes; the fields corresponding to the transaction conditions include actual fulfillment content that corresponds to the available quantity, transaction price, and customization rules; and the fields corresponding to the delivery requirements include actual fulfillment content that corresponds to the delivery cycle, delivery area, packaging rules, and delivery conditions. Other content included in the fulfillment node data submitted by the supplier that does not correspond to the procurement object, transaction conditions, and delivery requirements in the order version data record will not be retained as comparable fulfillment node data.

[0094] For example, the fulfillment node data is submitted at at least one of the following nodes: the stock preparation node, the customization confirmation node, the packaging node, and the shipping node; the fulfillment node data submitted at different fulfillment nodes are all processed according to the fields corresponding to the purchase object, transaction conditions, and delivery requirements in the order version data record.

[0095] During order fulfillment, based on the correspondence between product data fingerprints and order version data records in the order data to be fulfilled, it is verified whether the product data fingerprint can be matched with the order version data record. When the product data fingerprint can be matched with the order version data record, the corresponding order version data record is determined as the data comparison benchmark for the fulfillment node. When the product data fingerprint cannot be matched with the order version data record, the data comparison benchmark for the fulfillment node is not determined, no comparable fulfillment node data is formed, and a transaction control result indicating an order version verification anomaly is generated, causing the order data to be fulfilled to enter a suspended fulfillment state.

[0096] Specifically, after determining the order version data record based on the product data fingerprint, the supplier's submitted performance node data is processed according to the procurement object, transaction conditions, and delivery requirements in the order version data record. This ensures that the content in the performance node data corresponding to the product category, applicable scenario, and product attributes corresponds to the procurement object in the order version data record; the content in the performance node data corresponding to the available quantity, transaction price, and customization rules corresponds to the transaction conditions in the order version data record; and the content in the performance node data corresponding to the delivery cycle, delivery area, packaging rules, and delivery conditions corresponds to the delivery requirements in the order version data record.

[0097] Furthermore, the fields of the fulfillment node data that have completed the corresponding field processing are organized, and the field names, field contents and units of measurement in the fulfillment node data are organized into an expression form that can be directly compared with the order version data record; content in the fulfillment node data submitted by the supplier that cannot form a corresponding relationship with the order version data record is not retained as comparable fulfillment node data.

[0098] After the fields are sorted out, the performance node data that can be compared with the benchmark performance node data is identified as comparable performance node data.

[0099] S4.3 Compare the comparable fulfillment node data with the order version data record that serves as the benchmark for comparing the fulfillment node data, identify the offset of the fulfillment node data relative to the order version data record, and generate transaction control results.

[0100] It should be noted that after obtaining comparable performance node data, the comparable performance node data is compared with the procurement object, transaction conditions and delivery requirements in the order version data record, so that the performance node data and the order version data record confirmed by the purchaser are compared under the same data item, avoiding mismatch between the performance node data submitted by the supplier and the content confirmed by the purchaser.

[0101] Specifically, the content corresponding to the procurement object in the comparable performance node data is compared with the procurement object in the order version data record. When the actual performance content in the comparable performance node data that corresponds to the product category, applicable scenario, and product attribute matches the product category, applicable scenario, and product attribute in the order version data record, it is determined that there is no offset in the performance node data regarding the procurement object. When any content does not match the corresponding content in the order version data record, it is identified that there is an offset in the performance node data relative to the order version data record regarding the procurement object.

[0102] Furthermore, the content corresponding to the transaction conditions in the comparable fulfillment node data is compared with the transaction conditions in the order version data record. When the actual fulfillment content in the comparable fulfillment node data that corresponds to the available quantity, transaction price, and customization rules meets the available quantity, transaction price, and customization rules in the order version data record, it is determined that there is no deviation in the transaction conditions of the fulfillment node data. When any content does not meet the corresponding content in the order version data record, it is identified that there is a deviation in the transaction conditions of the fulfillment node data relative to the order version data record.

[0103] Furthermore, the content corresponding to the delivery requirements in the comparable fulfillment node data is compared with the delivery requirements in the order version data record. When the actual fulfillment content in the comparable fulfillment node data that corresponds to the delivery cycle, delivery area, packaging rules, and delivery conditions meets the delivery cycle, delivery area, packaging rules, and delivery conditions in the order version data record, it is determined that there is no deviation in the delivery requirements of the fulfillment node data. When any content does not meet the corresponding content in the order version data record, it is identified that there is a deviation in the delivery requirements of the fulfillment node data relative to the order version data record.

[0104] The expression for identifying the data offset of the fulfillment node is: ; ; in, Indicates the first The data of the first fulfillment node in the [number]th [year] Offset results on class constraint types; Indicates the first The total offset of each fulfillment node data relative to the order version data record; Indicates the first In the data of each fulfillment node, compared with the first... Under class constraints, the first The actual performance content corresponding to each data item; This indicates that in the order version data record, the version is related to the first... Under class constraints, the first The fixed content corresponding to each data item; Indicates the first The offset results of each performance node data under the constraints of the procurement object; Indicates the first The offset results of individual performance node data under transaction condition constraints; Indicates the first The offset results of each performance node data under delivery requirement constraints; This represents the fulfillment node data index, used to distinguish different groups of fulfillment node data submitted by the supplier during the order fulfillment process; Represents the consistency discriminant function, when the... In the data of the first fulfillment node Under class constraints, the first The actual performance content corresponding to each data item Conforms to the fixed content in the order version data record hour, Take 0, when Does not meet hour, Take 1.

[0105] The system summarizes the offset identification of fulfillment node data relative to the order version data record. When no offset of procurement object, transaction condition, or delivery requirement is identified, a transaction control result indicating that the fulfillment node data conforms to the order version data record is generated, and the order data to be fulfilled continues to enter the subsequent fulfillment process. When at least one of the offset of procurement object, transaction condition, or delivery requirement is identified, a transaction control result indicating that the fulfillment node data does not conform to the order version data record is generated. The content that does not conform to the order version data record is recorded in the transaction control result, and the order data to be fulfilled enters one of the following transaction processing states: suspended fulfillment, returned to supplier for correction, or buyer review.

[0106] The expression for the transaction control result is: ; in, Indicates the first The transaction control results corresponding to each performance node data; This indicates the product data fingerprint verification result; This indicates that the product data fingerprint can verify and identify the corresponding order version data record; This indicates that the product data fingerprint cannot be verified and the corresponding order version data record cannot be determined; Indicates the first The data for each fulfillment node has not shifted relative to the order version data record; Indicates the first The data for each fulfillment node has shifted relative to the order version data record; This means that if the product data fingerprint verification passes and the fulfillment node data does not shift, the order data to be fulfilled will continue to enter the subsequent fulfillment process; This indicates that when the product data fingerprint verification fails or the fulfillment node data deviates, the order data to be fulfilled enters a transaction processing state of suspension of fulfillment, return to supplier for correction, and review by the purchaser.

[0107] Furthermore, when the product data fingerprint cannot be verified and the corresponding order version data record is identified, the transaction control result determines that the order data to be fulfilled enters the suspended fulfillment state; when the product data fingerprint can be verified and the corresponding order version data record is identified, but the fulfillment node data deviates from the order version data record, if the deviation originates from at least one of the following: missing fields, inconsistent field formats, and inconsistent units of measurement in the fulfillment node data, the transaction control result determines that the order data to be fulfilled enters the return to supplier for correction state; if the deviation originates from at least one of the following: procurement object, transaction quotation, customization rules, delivery cycle, delivery area, packaging rules, and delivery conditions, which change relative to the order version data record, the transaction control result determines that the order data to be fulfilled enters the purchaser's review state.

[0108] Figure 6 The results show the changes in the accuracy of performance control between the present invention and various control schemes at continuous time positions. The curve of the present invention is generally higher than that of the control schemes and maintains a high accuracy during fluctuations. This indicates that by determining the performance comparison benchmark through order version data records and product data fingerprints, the impact of product data updates and performance node data offsets on transaction control results can be reduced, thereby improving the stability of performance control.

[0109] Figure 7 The differences between the present invention and various control schemes in terms of matching accuracy, fulfillment success rate, fulfillment deviation identification accuracy, and fulfillment comparison benchmark deviation rate were compared. The present invention outperformed the control schemes in the first three indicators and underperformed them in the fulfillment comparison benchmark deviation rate. This indicates that the present invention improves the matching accuracy, fulfillability, and fulfillment control accuracy of the gift procurement scheme by matching procurement constraints, verifying transaction fulfillability, solidifying order version data records, and comparing product data fingerprints, while reducing the risk of fulfillment comparison benchmark deviation.

[0110] Figure 6 and Figure 7 The present invention solution refers to the online procurement transaction method of this embodiment, which sequentially performs procurement constraint matching, transaction fulfillment verification, order version data recording and solidification, and product data fingerprint comparison. Comparison Solution A is a standard order filtering solution, which only filters based on basic product fields and directly generates standard order data. Comparison Solution B is a solution that only performs procurement constraint matching but does not perform transaction fulfillment verification. Comparison Solution C is a solution that performs procurement constraint matching and transaction fulfillment verification but does not perform order version data recording and solidification. Comparison Solution D is a solution that performs order version data recording and solidification but does not use product data fingerprints for verification and comparison.

[0111] This embodiment also provides an online procurement and transaction system for a gift e-commerce platform, including: a demand matching module, a performance verification module, a version fixing module, and a fingerprint comparison module; The demand matching module is used to receive gift purchase requests submitted by buyers in the gift e-commerce platform, convert the gift purchase requests into purchase constraints, and match the purchase constraints with product transaction data in the product data management database to generate candidate gift purchase plans. The fulfillment verification module is used to verify the fulfillment of candidate gift procurement plans under the current transaction status, obtain the transaction fulfillment verification result, and determine the target gift procurement plan from the candidate gift procurement plans whose product transaction data meets the procurement constraints and passes the transaction fulfillment verification under the current transaction status. The version solidification module is used to respond to the purchaser's confirmation of the target gift procurement plan, solidify the product transaction data and transaction fulfillment verification results corresponding to the target gift procurement plan into order version data records, and generate order data to be fulfilled; The fingerprint comparison module is used to perform field ordering and summary calculation on the order version data records in the order data to be fulfilled, generate product data fingerprints, verify and determine the corresponding order version data records based on the product data fingerprints during the order fulfillment process, compare the fulfillment node data submitted by the supplier with the order version data records, identify the offset of the fulfillment node data relative to the order version data records, and generate transaction control results.

[0112] In summary, this invention addresses the problem of insufficient connection between product data management and procurement transactions by: converting gift procurement needs into procurement constraints and matching them with product transaction data in the product data management database and verifying transaction fulfillment; and by solidifying product transaction data and transaction fulfillment verification results into order version data records and comparing fulfillment node data based on product data fingerprints, it solves the problem of easy deviation in the fulfillment comparison benchmark after order confirmation, thereby improving the consistency of transaction data and the stability of fulfillment control.

[0113] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for online procurement and transaction in a gift e-commerce marketplace, characterized in that: include: Receive gift procurement requests submitted by buyers in the gift e-commerce platform, convert the gift procurement requests into procurement constraints, and match the procurement constraints with product transaction data in the product data management database to generate candidate gift procurement plans. The transaction fulfillment verification is performed on the candidate gift procurement schemes under the current transaction status to obtain the transaction fulfillment verification results. The target gift procurement schemes that meet the procurement constraints and pass the transaction fulfillment verification under the current transaction status are then determined from the candidate gift procurement schemes. In response to the purchaser's confirmation of the target gift procurement plan, the product transaction data and transaction fulfillment verification results corresponding to the target gift procurement plan are solidified into order version data records, generating order data to be fulfilled; The system performs field ordering and summary calculation on the order version data records in the order fulfillment data to generate product data fingerprints. During the order fulfillment process, the system verifies and determines the corresponding order version data records based on the product data fingerprints. The system compares the fulfillment node data submitted by the supplier with the order version data records to identify the offset of the fulfillment node data relative to the order version data records and generates transaction control results.

2. The online procurement and transaction method for gift e-commerce as described in claim 1, characterized in that, The aforementioned gift procurement requirements refer to the data submitted by the purchaser on the gift e-commerce platform, which indicates the procurement object, transaction conditions, and delivery requirements.

3. The online procurement and transaction method for gift e-commerce as described in claim 2, characterized in that, The specific steps for converting gift procurement needs into procurement constraints are as follows: The procurement objects, transaction conditions, and delivery requirements in the gift procurement needs are organized into fields to obtain fielded gift procurement needs; Based on the field-based gift procurement requirements, the procurement objects, transaction conditions, and delivery requirements are converted into procurement constraints for matching product transaction data.

4. The online procurement and transaction method for gift e-commerce as described in claim 3, characterized in that, The procurement constraints include constraints on the procurement object, constraints on transaction conditions, and constraints on delivery requirements; The constraints on the procurement object are used to match the product category, applicable scenario, and product attributes in the product transaction data; The transaction condition constraints are used to match the available quantity, transaction price, and customization rules in the product transaction data; The delivery requirement constraints are used to match the delivery cycle, delivery area, packaging rules, and delivery conditions in the product transaction data.

5. The online purchasing and transaction method for gift e-commerce as described in claim 4, characterized in that, The process of matching procurement constraints with product transaction data in the product data management database to generate candidate gift procurement plans involves the following steps: Based on the constraints of the procurement object, search for product transaction data in the product data management database to obtain the product transaction data corresponding to the constraints of the procurement object. In the product transaction data corresponding to the constraints of the procurement object, continue to match according to the constraints of the transaction conditions to obtain product transaction data that simultaneously meets the constraints of the procurement object and the constraints of the transaction conditions. Based on the delivery requirement constraints, product transaction data that simultaneously meets the procurement object constraints and transaction condition constraints are matched for delivery to obtain product transaction data that meets the procurement constraints. Product transaction data that meet the procurement constraints are aggregated according to the same gift procurement needs to form candidate gift procurement plans.

6. The online procurement and transaction method for gift e-commerce as described in claim 1, characterized in that, The transaction fulfillment verification refers to, after generating a candidate gift procurement plan, combining the current transaction status data corresponding to the candidate gift procurement plan, verifying the product conditions, transaction conditions, and delivery conditions of the product transaction data corresponding to the candidate gift procurement plan, in order to determine whether the candidate gift procurement plan can be fulfilled under the current transaction status. The current transaction status data includes product availability, inventory availability, valid quote status, custom fulfillment status, packaging availability, and delivery coverage status.

7. The online procurement and transaction method for gift e-commerce as described in claim 6, characterized in that, The specific steps for verifying the feasibility of the candidate gift procurement plan are as follows: Based on the procurement constraints and the current transaction status data corresponding to the candidate gift procurement schemes, the product transaction data corresponding to the candidate gift procurement schemes are organized to form transaction fulfillment verification items; According to the transaction fulfillment verification items, the product transaction data and current transaction status data corresponding to the candidate gift procurement plan are verified for product conditions, transaction conditions and delivery conditions to obtain the transaction fulfillment verification results; Based on the transaction fulfillment verification results, the candidate gift procurement schemes that meet the corresponding constraints in the current transaction status, including product conditions, transaction conditions, and delivery conditions, are determined as the target gift procurement schemes.

8. The online procurement and transaction method for gift e-commerce as described in claim 1, characterized in that, The order version data record refers to the data record formed after the purchaser confirms the target gift procurement plan, which includes the target gift procurement plan identifier, the product transaction data corresponding to the target gift procurement plan, the transaction fulfillment verification result, the fixed correspondence between the product transaction data and the transaction fulfillment verification result, and the version generation time.

9. The online procurement and transaction method for gift e-commerce as described in claim 8, characterized in that, The specific steps for generating the transaction control result are as follows: The order version data records in the order fulfillment data are ordered by fields and the summary is calculated to generate product data fingerprints and establish the correspondence between product data fingerprints and order version data records. During the order fulfillment process, the corresponding order version data record is determined by verifying the product data fingerprint. The determined order version data record is used as the benchmark for comparing the fulfillment node data. The fulfillment node data submitted by the supplier is organized according to the fields corresponding to the procurement object, transaction conditions and delivery requirements to obtain comparable fulfillment node data. The comparable fulfillment node data is compared with the order version data record, which serves as the benchmark for comparison of fulfillment node data, to identify the offset of fulfillment node data relative to the order version data record, and to generate transaction control results based on the offset identification results. The transaction control results are used to determine the corresponding processing status of pending order data, including continued performance status, suspended performance status, return to supplier for correction status, and purchaser review status.

10. An online procurement and transaction system for a gift e-commerce platform, based on the online procurement and transaction method for a gift e-commerce platform as described in any one of claims 1 to 9, characterized in that, include: The module includes a demand matching module, a performance verification module, a version solidification module, and a fingerprint comparison module. The demand matching module is used to receive gift purchase requests submitted by buyers in the gift e-commerce platform, convert the gift purchase requests into purchase constraints, and match the purchase constraints with product transaction data in the product data management database to generate candidate gift purchase plans. The fulfillment verification module is used to verify the fulfillment of candidate gift procurement plans under the current transaction status, obtain the transaction fulfillment verification result, and determine the target gift procurement plan from the candidate gift procurement plans whose product transaction data meets the procurement constraints and passes the transaction fulfillment verification under the current transaction status. The version solidification module is used to respond to the purchaser's confirmation of the target gift procurement plan, solidify the product transaction data and transaction fulfillment verification results corresponding to the target gift procurement plan into order version data records, and generate order data to be fulfilled; The fingerprint comparison module is used to perform field ordering and summary calculation on the order version data records in the order data to be fulfilled, generate product data fingerprints, verify and determine the corresponding order version data records based on the product data fingerprints during the order fulfillment process, compare the fulfillment node data submitted by the supplier with the order version data records, identify the offset of the fulfillment node data relative to the order version data records, and generate transaction control results.

Images