A method, system, equipment, and medium for delivery verification based on digital warehouse receipts.

Abstract

This application provides a method, system, device, and medium for goods pickup verification based on digital warehouse receipts. The method includes: upon receiving a pickup authorization request, generating a target outbound order based on the target digital warehouse receipt, with the target outbound order and the target digital warehouse receipt linked through an on-chain warehouse receipt identifier; constructing pickup authorization status data based on the target outbound order; generating a pickup voucher identifier and voucher verification code based on the pickup authorization status data, determining the voucher generation time and voucher expiration time, generating a dynamic pickup voucher, and displaying the dynamic pickup voucher in a scannable form on the buyer's or driver's end; when the warehouse end scans the dynamic pickup voucher, generating a barcode verification request and sending the barcode verification request to the platform server; upon receiving the barcode verification request, generating a pickup verification status set; performing multi-state consistency verification based on the pickup verification status set, generating a verification result, and sending the verification result to the warehouse end. This application can improve the accuracy and security of the goods pickup verification process.

Description

Technical Field

[0001] This application relates to the field of warehouse data processing technology, and in particular to a method, system, equipment and medium for delivery verification based on digital warehouse receipts. Background Technology

[0002] With the application of warehouse management systems, electronic voucher systems, and digital warehouse receipt systems, warehousing platforms typically manage product batches, warehouse locations, inventory quantities, outbound orders, and verification records electronically. They can also use blockchain-based evidence storage nodes to store warehouse receipt summaries, authorization summaries, or verification summaries, thereby improving the credibility and traceability of data records. In such systems, digital warehouse receipts, outbound orders, inventory lock records, electronic delivery vouchers, and verification records are usually maintained by different data tables, functional modules, or external nodes. These various data types need to be linked through fields such as warehouse receipt identifiers, order identifiers, voucher identifiers, product batch identifiers, and warehouse identifiers.

[0003] In actual barcode scanning verification, the platform server needs to read and compare status data from multiple data sources within a short period of time based on the scanning request. For example, electronic vouchers may have independent voucher status and expiration time, digital warehouse receipts may have independent warehouse receipt status and available quantity, off-chain inventory records may have independent locked quantity and inventory status, and historical cancellation records are used to determine whether a voucher or order has been successfully cancelled. Since the generation time, update triggering conditions, and storage location of the above data are not entirely the same, if the platform server only makes judgments based on a single voucher status, a single order record, or a single inventory record, it is easy to encounter data verification deviations such as voucher status not synchronizing with warehouse receipt status, inconsistencies between outbound and locked quantities, inconsistencies between scanned and authorized warehouses, inconsistencies between on-site identity and vehicle information and authorization information, or duplicate cancellation of the same voucher, thereby reducing the accuracy of the pickup verification results.

[0004] Therefore, there is an urgent need for a delivery verification method, system, equipment, and medium based on digital warehouse receipts. Summary of the Invention

[0005] This application provides a method, system, device, and medium for delivery verification based on digital warehouse receipts to solve the problems of the prior art.

[0006] Firstly, this application provides a delivery verification method based on digital warehouse receipts, including:

[0007] Upon receiving a pickup authorization request, a target outbound order is generated based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Based on the target outbound order, the authorization generation time, and the authorization status, pickup authorization status data is constructed.

[0008] Dynamic pickup voucher generation involves generating a pickup voucher identifier and voucher verification code based on the pickup authorization status data, determining the voucher generation time and voucher expiration time, and generating a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time, and voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, it generates a barcode verification request and sends the barcode verification request to the platform server.

[0009] The platform server, upon receiving a scan verification request, generates the following status sets based on the scan verification request, dynamic pickup voucher records, pickup authorization status data, the warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders, and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status.

[0010] Multi-state consistency verification and verification result processing: Based on the set of delivery verification states, multi-state consistency verification is performed, verification results are generated, and the verification results are sent to the warehouse.

[0011] In one possible design, the target digital warehouse receipt includes an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, a warehouse receipt quantity, a locked quantity, a cleared quantity, a redeemable quantity, and a warehouse receipt status.

[0012] The target outbound order includes an outbound order identifier, an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, an outbound quantity, de-identified driver identity verification information, de-identified vehicle verification information, and a pickup time window;

[0013] The pickup authorization status data includes outbound order identifier, on-chain warehouse receipt identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, pickup time window, authorization generation time, and authorization status;

[0014] The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier, and the delivery authorization status data is associated with the target outbound order through an outbound order identifier.

[0015] In one possible design, the dynamic delivery voucher is stored on the platform server in the form of a dynamic delivery voucher record. The dynamic delivery voucher record includes a delivery voucher identifier, a voucher verification code, an on-chain warehouse receipt identifier, an outbound order identifier, a product batch identifier, a warehouse identifier, an outbound quantity, de-identified driver identity verification information, de-identified vehicle verification information, a delivery time window, a voucher generation time, a voucher expiration time, and a voucher status.

[0016] The dynamic pickup voucher is displayed on the buyer's or driver's end in the form of a QR code, barcode, electronic pickup code, or mini-program page voucher. The QR code, barcode, electronic pickup code, or mini-program page voucher includes at least a pickup voucher identifier and a voucher verification code.

[0017] The scan verification request includes the delivery voucher identifier, voucher verification code, scan warehouse identifier, scan time, scan terminal identifier, on-site driver identity verification information, and on-site vehicle verification information.

[0018] In one possible design, after receiving the QR code verification request, the platform server queries the dynamic delivery voucher record based on the delivery voucher identifier, and obtains the on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, and delivery time window from the dynamic delivery voucher record.

[0019] The platform server queries the target digital warehouse receipt based on the on-chain warehouse receipt identifier and obtains the warehouse receipt status of the target digital warehouse receipt at the time of this scan-to-verify transaction.

[0020] The platform server queries the target outbound order based on the outbound order identifier;

[0021] The platform server queries the off-chain inventory lock records based on the outbound order identifier, warehouse identifier, product batch identifier, and outbound quantity.

[0022] The platform server queries historical outbound verification records based on the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier.

[0023] In one possible design, the voucher usage status is generated based on the voucher status in the dynamic delivery voucher record, the voucher expiry time, and the scanning time in the barcode verification request;

[0024] The voucher verification status is generated based on the voucher verification code in the barcode verification request and the voucher verification code stored in the dynamic delivery voucher record;

[0025] The on-chain warehouse receipt status is generated based on the warehouse receipt status of the target digital warehouse receipt queried during this scan-to-verify process;

[0026] The off-chain inventory lock status is generated based on the locked quantity, lock status, and off-chain inventory status in the off-chain inventory lock record.

[0027] The warehouse matching status is generated based on the warehouse identifier in the scanned verification request and the warehouse identifier in the dynamic delivery voucher record.

[0028] The product batch matching status is generated based on the product batch identifier in the dynamic delivery voucher record and the product batch identifier in the off-chain inventory lock record.

[0029] The quantity matching status is generated based on the outbound quantity in the dynamic delivery voucher record, the outbound quantity in the target outbound order, and the locked quantity in the off-chain inventory lock record;

[0030] The driver identity matching status is generated based on the on-site driver identity verification information in the QR code verification request and the de-identified driver identity verification information in the dynamic delivery voucher record.

[0031] The vehicle matching status is generated based on the on-site vehicle verification information in the QR code verification request and the de-identified vehicle verification information in the dynamic delivery voucher record.

[0032] The delivery time verification status is generated based on the authorization generation time and delivery time window in the delivery authorization status data, the voucher generation time and voucher expiration time in the dynamic delivery voucher record, and the scanning time in the scanning verification request.

[0033] The number of reconciliations is generated based on historical outbound reconciliation records.

[0034] In one possible design, the verification result includes verification passed and verification failed;

[0035] When the verification result is that the verification is passed, an allow delivery instruction is output to the warehouse end, and the voucher status in the dynamic delivery voucher record, the authorization status in the delivery authorization status data, the target digital warehouse receipt and the off-chain inventory lock record are updated.

[0036] When the verification result is abnormal, an abnormal prompt message is output to the warehouse and an abnormal verification record is generated.

[0037] In one possible design, when the voucher usage status is unverified, the voucher verification status is voucher verification passed, the on-chain warehouse receipt status is pending pickup or partial pickup, the off-chain inventory lock status is locked, the warehouse matching status is warehouse matching, the product batch matching status is batch matching, the quantity matching status is quantity matching, the driver identity matching status is driver identity matching, the vehicle matching status is vehicle matching, the pickup time verification status is time verification passed, and the verification count status meets the single verification condition, the verification result is determined to be verification passed.

[0038] Otherwise, the verification result will be considered an anomaly.

[0039] Secondly, this application provides a delivery verification system based on digital warehouse receipts, including:

[0040] The pickup authorization status data construction module, upon receiving a pickup authorization request, generates a target outbound order based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Based on the target outbound order, the authorization generation time, and the authorization status, the pickup authorization status data is constructed.

[0041] The dynamic pickup voucher generation module generates a pickup voucher identifier and a voucher verification code based on the pickup authorization status data, determines the voucher generation time and voucher expiration time, and generates a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time and voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, it generates a barcode verification request and sends the barcode verification request to the platform server.

[0042] The pickup verification status set construction module is as follows: After receiving the scan verification request, the platform server generates the following statuses based on the scan verification request, dynamic pickup voucher records, pickup authorization status data, warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status, thus constructing the pickup verification status set.

[0043] The multi-state consistency verification and verification result processing module performs multi-state consistency verification based on the set of delivery verification states, generates verification results, and sends the verification results to the warehouse.

[0044] Thirdly, this application provides an electronic device, comprising:

[0045] Processor; and,

[0046] Memory for storing the executable instructions of the processor;

[0047] The processor is configured to perform any of the possible methods described in the first aspect by executing the executable instructions.

[0048] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement any of the possible methods described in the first aspect.

[0049] Compared with the prior art, this application has the following beneficial effects:

[0050] This application provides a method, system, device, and medium for pickup verification based on digital warehouse receipts. The method generates target outbound orders and pickup authorization status data based on target digital warehouse receipts, and further generates dynamic pickup vouchers. This enables warehouse-side barcode scanning and verification requests to be associated with digital warehouse receipts, outbound orders, pickup authorization status data, and dynamic pickup voucher records. Simultaneously, after receiving a barcode scanning and verification request on the platform server, a pickup verification status set is constructed, including voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status. Multi-status consistency verification is performed based on this pickup verification status set. This avoids judgment biases caused by verification based on a single pickup voucher, single order record, or single inventory record, improving the accuracy and reliability of pickup verification results.

[0051] Furthermore, this application limits key fields in the target digital warehouse receipt, target outbound order, delivery authorization status data, dynamic delivery voucher record, and barcode verification request. It generates corresponding verification statuses based on voucher status, voucher expiration time, voucher verification code, warehouse receipt status, inventory lock record, warehouse identifier, product batch identifier, outbound quantity, driver and vehicle verification information, delivery time window, and historical outbound verification records. This enables the platform server to uniformly judge voucher validity, warehouse receipt pickup availability, inventory lock consistency, warehouse and batch consistency, quantity consistency, personnel and vehicle consistency, time validity, and duplicate verification. Upon successful verification, it outputs an allow-out-of-warehouse instruction and updates the dynamic delivery voucher record, delivery authorization status data, target digital warehouse receipt, and off-chain inventory lock record. Upon verification failure, it outputs an error message and generates an error verification record, thereby improving the synchronicity of outbound verification status updates and the completeness of subsequent traceability. Attached Figure Description

[0052] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0053] Figure 1 This is a flowchart illustrating a delivery verification method based on a digital warehouse receipt according to an example embodiment of this application;

[0054] Figure 2 This is a schematic diagram of the structure of a delivery verification system based on a digital warehouse receipt, as illustrated in an example embodiment of this application.

[0055] Figure 3 This is a schematic diagram of the structure of an electronic device according to an example embodiment of this application.

[0056] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0057] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0058] This embodiment proposes a method, system, equipment, and medium for goods pickup verification based on digital warehouse receipts. It is applicable to scenarios involving warehouse pickup, batch goods outbound, digital warehouse receipt verification, and platform-based warehouse management, particularly suitable for applications requiring joint verification of pickup vouchers, digital warehouse receipts, outbound orders, inventory lock status, and on-site driver and vehicle information. This embodiment generates target outbound orders and pickup authorization status data based on target digital warehouse receipts, and further generates dynamic pickup vouchers. This allows the platform server to construct a pickup verification status set and perform multi-status consistency verification during warehouse-side barcode scanning and verification. This avoids warehouses releasing goods solely based on static pickup codes or single order information, improving the accuracy, security, and traceability of the pickup verification process.

[0059] It should be noted that the delivery verification method based on digital warehouse receipts provided in this application is applied to a delivery verification system, which includes a platform server, a buyer's or driver's client, a warehouse, and a blockchain evidence storage node. Among these:

[0060] The platform server is used to manage target digital warehouse receipts, target outbound orders, delivery authorization status data, dynamic delivery voucher records, delivery verification status sets, off-chain inventory lock records, and outbound verification records. It is also used to perform tasks such as constructing delivery authorization status data, generating dynamic delivery vouchers, constructing delivery verification status sets, performing multi-state consistency checks, and processing verification results.

[0061] The buyer's or driver's end refers to the terminal device, mini-program client, or voucher display page used by the buyer or driver to submit pickup authorization requests, fill in or receive driver identity verification information and vehicle verification information, and receive or display dynamic pickup vouchers. The buyer's or driver's end does not directly execute warehouse release operations.

[0062] The warehouse end refers to the verification terminal, handheld barcode scanner, warehouse management mini-program or warehouse management system used by warehouse management personnel to scan and identify dynamic delivery vouchers, collect the scanning warehouse identifier, scanning time, barcode terminal identifier, on-site driver identity verification information and on-site vehicle verification information, and initiate a barcode verification request to the platform server.

[0063] The blockchain evidence storage node is used to receive warehouse receipt summaries, delivery authorization summaries, or outbound verification summaries uploaded by the platform server and return the corresponding on-chain identifiers. The blockchain evidence storage node is used for trusted evidence storage and traceability, and is not limited to a specific consensus mechanism, smart contract structure, or blockchain type.

[0064] Figure 1 This is a flowchart illustrating a delivery verification method based on digital warehouse receipts, according to an example embodiment of this application. Figure 1 As shown, the delivery verification method based on digital warehouse receipts provided in this embodiment includes:

[0065] Step S101: Constructing delivery authorization status data. After receiving the delivery authorization request, a target outbound order is generated based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Delivery authorization status data is constructed based on the target outbound order, the authorization generation time, and the authorization status.

[0066] In this step, after receiving the pickup authorization request, the platform server begins the pickup authorization status data construction process. The pickup authorization request is initiated by the buyer based on the target digital warehouse receipt and includes the on-chain warehouse receipt identifier, the requested pickup quantity, driver identity verification information, vehicle verification information, and expected pickup time. The platform server queries the target digital warehouse receipt based on the on-chain warehouse receipt identifier in the pickup authorization request and generates the target outbound order and pickup authorization status data after successful verification.

[0067] In this implementation, the target digital warehouse receipt is generated by the platform server after the goods are confirmed to be in the warehouse and the ownership of the goods is confirmed. The platform server generates the target digital warehouse receipt for a specific owner based on the warehouse inventory records and the ownership confirmation records. The target digital warehouse receipt includes an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, the warehouse receipt quantity, the locked quantity, the verified quantity, the available quantity for pickup, and the warehouse receipt status.

[0068] The on-chain warehouse receipt identifier originates from the on-chain notarized record corresponding to the target digital warehouse receipt. It uniquely associates the target digital warehouse receipt and serves as the primary field for establishing the link between the target digital warehouse receipt, the target outbound order, and the dynamic delivery voucher. The on-chain notarized record is generated after the platform server uploads the warehouse receipt summary corresponding to the target digital warehouse receipt to the blockchain notarization node. Based on this notarized record, the blockchain notarization node returns the on-chain warehouse receipt identifier. The platform server then writes this identifier into the target digital warehouse receipt, enabling the target digital warehouse receipt, the target outbound order, and the dynamic delivery voucher to be linked and traced through the on-chain warehouse receipt identifier.

[0069] The commodity batch identifier is used to identify the batch of goods corresponding to the target digital warehouse receipt.

[0070] The warehouse identifier is used to identify the target warehouse where the batch of goods is located.

[0071] The quantity of warehouse receipts is used to represent the quantity of goods that have been confirmed as the ownership of the goods by the holder.

[0072] The locked quantity is used to represent the quantity that has been occupied by outbound tasks but has not yet been cleared.

[0073] The quantity that has been cleared is used to represent the quantity that has been cleared out of the warehouse.

[0074] The quantity of goods available for pickup is determined by the platform server based on the quantity of warehouse receipts, the quantity locked, and the quantity already verified.

[0075] The warehouse receipt status is used to indicate whether the target digital warehouse receipt is in a pending delivery, partially delivered, delivered, frozen, or abnormal state. Specifically, a warehouse receipt status of pending delivery or partially delivered indicates that the target digital warehouse receipt is in a delivery-allowed state. A warehouse receipt status of delivered, frozen, or abnormal indicates that the target digital warehouse receipt is in a delivery-disallowed state.

[0076] After the target digital warehouse receipt is generated, the platform server updates the locked quantity, cleared quantity and available quantity in the target digital warehouse receipt based on the inventory lock record and outbound verification record, and updates the warehouse receipt status based on the verification status, frozen status or abnormal status of the target digital warehouse receipt.

[0077] For example, if a target warehouse stores 100 tons of a certain batch of powdered sugar, of which 20 tons have already had their pickup rights confirmed, the platform server generates a target digital warehouse receipt based on these 20 tons of pickup rights. This target digital warehouse receipt records the batch identifier, warehouse identifier, warehouse receipt quantity, locked quantity, verified quantity, pickup quantity, and warehouse receipt status. After the platform server uploads the warehouse receipt summary corresponding to the target digital warehouse receipt to the blockchain evidence storage node, the blockchain evidence storage node returns an on-chain warehouse receipt identifier, which the platform server writes into the target digital warehouse receipt. Subsequently, the platform server uses the on-chain warehouse receipt identifier to locate the corresponding on-chain evidence storage record for the target digital warehouse receipt and, combined with the pickup quantity and warehouse receipt status maintained by the platform server, determines whether the target digital warehouse receipt is still in a pickup state.

[0078] In this implementation, the target outbound order is a warehouse-side outbound execution task record generated by the platform server based on the redeemable rights corresponding to the target digital warehouse receipt. The target outbound order is not a duplicate record of the target digital warehouse receipt, but is used to convert some or all of the redeemable rights in the target digital warehouse receipt into a specific warehouse-side pickup and verification task.

[0079] For example, if a target buyer has already confirmed ownership of 20 tons of a certain batch of powdered sugar in a target warehouse, the platform server generates a target digital warehouse receipt based on this 20-ton pick-up right. This target digital warehouse receipt records the target buyer's ownership of the goods, the pick-up quantity, and the warehouse receipt status for that batch. When the target buyer applies to pick up only 10 tons, the platform server does not generate a new digital warehouse receipt. Instead, it generates a target outbound order based on the target digital warehouse receipt, specifying the outbound quantity as 10 tons. This target outbound order instructs the warehouse to perform barcode scanning, verification, and outbound processing for these 10 tons of goods.

[0080] When a buyer submits a pickup authorization request, the request includes the on-chain warehouse receipt identifier, the quantity of goods requested for pickup, driver identity verification information, vehicle verification information, and the expected pickup time.

[0081] The platform server queries the target digital warehouse receipt based on the on-chain warehouse receipt identifier in the pickup authorization request, and obtains the commodity batch identifier, warehouse identifier, pickup quantity and warehouse receipt status from the target digital warehouse receipt.

[0082] When the target digital warehouse receipt is in a state where pickup is permitted, and the requested pickup quantity is not greater than the pickup quantity of the target digital warehouse receipt, the platform server generates a target outbound order.

[0083] In this implementation, the target outbound order includes an outbound order identifier, an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, an outbound quantity, de-identified driver identity verification information, de-identified vehicle verification information, and a pickup time window.

[0084] The platform server first configures an outbound order identifier for the target outbound order. The outbound order identifier is used to uniquely identify the outbound execution task at the warehouse.

[0085] Simultaneously, the on-chain warehouse receipt identifier corresponding to the target digital warehouse receipt is written into the target outbound order, and the product batch identifier and warehouse identifier in the target outbound order are set to be consistent with the target digital warehouse receipt. The outbound quantity in the target outbound order is then set to the requested pickup quantity.

[0086] A pickup time window is generated based on the expected pickup time and the warehouse's verifiable time rules. The pickup time window includes a pickup start time and a pickup end time, which are used to limit the time range within which this pickup authorization can be verified by the warehouse.

[0087] The driver identity verification information and vehicle verification information are summarized or anonymized to form anonymized driver identity verification information and anonymized vehicle verification information. In one implementation, the driver identity verification information includes the driver's name, driver's contact number, and driver's license number; the vehicle verification information includes the license plate number and vehicle registration mark. The platform server summarizes or anonymizes the driver's contact number, driver's license number, and license plate number to obtain anonymized values ​​for the driver's contact number, driver's license number, and license plate number, respectively, thus forming anonymized driver identity verification information and anonymized vehicle verification information. This enables identity and vehicle matching to be completed during the subsequent generation of dynamic delivery vouchers and warehouse verification, while reducing the exposure of complete plaintext personal information in vouchers and stored evidence data.

[0088] Thus, the target outbound order is established, and at the same time, the target outbound order is associated with the target digital warehouse receipt through the on-chain warehouse receipt identifier.

[0089] After a target outbound order is generated, the platform server generates an inventory lock record based on the outbound order identifier, warehouse identifier, product batch identifier, and outbound quantity, or associates the target outbound order with an existing inventory lock record. The inventory lock record is used to represent the quantity of inventory in the target warehouse that has been locked for the corresponding product batch for this target outbound order, and is used to generate the off-chain inventory lock status and quantity matching status during subsequent warehouse-side scanning and verification.

[0090] The platform server constructs pickup authorization status data based on the target outbound order. Specifically:

[0091] The platform server establishes a correlation between the pickup authorization status data and the target outbound order based on the outbound order identifier in the target outbound order. It then reads the on-chain warehouse receipt identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, and pickup time window from the target outbound order. Thus, the pickup authorization status data is associated with the target outbound order through the outbound order identifier.

[0092] Simultaneously, the platform server records the current system time as the authorization generation time and initializes the authorization status to valid. The authorization status is used to characterize the current availability of this delivery authorization. The authorization status is not a field directly read from the target outbound order or the target digital warehouse receipt, but rather a status field generated or updated by the platform server based on the construction results of the delivery authorization status data, the delivery time window, the warehouse receipt status of the target digital warehouse receipt, and subsequent verification results.

[0093] Authorization status includes valid, expired, revoked, and completed. When the platform server first constructs the pickup authorization status data, it initializes the authorization status to valid. When the pickup time window expires and the dynamic pickup voucher has not been verified, the authorization status is updated to expired. When the pickup authorization is revoked, or the warehouse receipt status of the target digital warehouse receipt changes to frozen, abnormal, or other disallowed pickup status, the authorization status is updated to revoked. After the warehouse scans and verifies the data and completes the outbound processing, the authorization status is updated to completed.

[0094] Thus, the pickup authorization status data is complete. This data includes the outbound order identifier, on-chain warehouse receipt identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, pickup time window, authorization generation time, and authorization status.

[0095] Through the above method, before generating dynamic delivery vouchers, the platform server first constructs delivery authorization status data based on the on-chain warehouse receipt identifier corresponding to the target digital warehouse receipt and the outbound order identifier corresponding to the target outbound order. This data includes the product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, delivery time window, authorization generation time, and authorization status. Therefore, the dynamic delivery voucher generation process can be based on a defined outbound task, product batch, target warehouse, outbound quantity, driver verification information, vehicle verification information, and delivery time window. Furthermore, the warehouse can perform consistency checks based on the same set of delivery authorization status data during barcode scanning and verification.

[0096] Step S102: Dynamic pickup voucher generation. Based on the pickup authorization status data, a pickup voucher identifier and a voucher verification code are generated. The voucher generation time and voucher expiration time are determined. A dynamic pickup voucher is generated based on the pickup authorization status data, the pickup voucher identifier, the voucher verification code, the voucher generation time, and the voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, a scan verification request is generated and sent to the platform server.

[0097] In this step, after constructing the pickup authorization status data, the platform server reads the authorization status from the pickup authorization status data. When the authorization status is valid, the platform server continues to generate dynamic pickup vouchers; when the authorization status is expired, revoked, or completed, the platform server stops generating dynamic pickup vouchers.

[0098] Specifically, when the authorization status is valid, the platform server generates a pickup voucher identifier and a voucher verification code based on the pickup authorization status data, and determines the voucher generation time and voucher expiration time according to the pickup time window in the pickup authorization status data. Subsequently, the platform server generates a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time, and voucher expiration time.

[0099] In this implementation, the dynamic delivery voucher includes a delivery voucher identifier, voucher verification code, on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, delivery time window, voucher generation time, voucher expiration time, and voucher status. The on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, and delivery time window are obtained from the delivery authorization status data. The delivery voucher identifier, voucher verification code, voucher generation time, voucher expiration time, and voucher status are written by the platform server when generating the dynamic delivery voucher. Specifically:

[0100] The delivery voucher identifier is generated by the platform server based on the voucher type prefix, warehouse identifier, voucher generation date, and daily incrementing sequence number, and is used to uniquely identify this dynamic delivery voucher. For example, the delivery voucher identifier can be represented as "TH-WH001-20260604-000001", where "TH" represents the delivery voucher type, "WH001" represents the warehouse identifier, "20260604" represents the voucher generation date, and "000001" represents the incrementing sequence number generated by the warehouse on that date.

[0101] The voucher verification code is generated by the platform server using the random number generation module. This code, along with the delivery voucher identifier, serves as the verification entry point for dynamic delivery vouchers, preventing the initiation of a scan-to-verify request based solely on the delivery voucher identifier, which could be guessed or forged.

[0102] The voucher generation time is the system time recorded by the platform server when it generates the dynamic pickup voucher; the voucher expiration time is determined according to the pickup time window, and the voucher expiration time is no later than the pickup end time in the pickup time window.

[0103] The voucher status is used to identify whether a dynamic delivery voucher is in an unverified, verified, expired, or revoked state. When a dynamic delivery voucher is first generated, the platform server initializes the voucher status to unverified. After the warehouse completes normal scanning and verification, the platform server updates the voucher status to verified. When a dynamic delivery voucher exceeds its expiration time and has not been verified, the platform server updates the voucher status to expired. When the target outbound order is revoked or the corresponding delivery authorization status is revoked, the platform server updates the voucher status to revoked.

[0104] In this embodiment, the dynamic pickup voucher is a verifiable voucher data object generated by the platform server based on pickup authorization status data. The dynamic pickup voucher is stored in the dynamic pickup voucher record table on the platform server in the form of dynamic pickup voucher records. The dynamic pickup voucher record table uses the pickup voucher identifier as a query index and stores the pickup voucher identifier, voucher verification code, on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, pickup time window, voucher generation time, voucher expiration time, and voucher status.

[0105] In a specific implementation, the dynamic pickup voucher is displayed on the buyer's or driver's end in the form of a QR code, barcode, electronic pickup code, or mini-program page voucher. The QR code, barcode, electronic pickup code, or mini-program page voucher includes at least a pickup voucher identifier and a voucher verification code. The displayed content of the dynamic pickup voucher is used to trigger scanning and verification at the warehouse end and does not need to be written into all fields of the dynamic pickup voucher record table.

[0106] Taking a QR code as an example, the QR code content includes a delivery voucher identifier and a voucher verification code. The QR code content does not include anonymized driver and vehicle verification information, nor does it include the complete plaintext information corresponding to the driver and vehicle verification information.

[0107] In this implementation, after scanning the dynamic delivery voucher, the warehouse parses it to obtain the delivery voucher identifier and voucher verification code, and collects the scanning warehouse identifier, scanning time, scanning terminal identifier, on-site driver identity verification information, and on-site vehicle verification information. Based on the delivery voucher identifier, voucher verification code, scanning warehouse identifier, scanning time, scanning terminal identifier, on-site driver identity verification information, and on-site vehicle verification information, the warehouse generates a scan verification request and sends the scan verification request to the platform server.

[0108] In this way, before the platform server scans and verifies the data at the warehouse, it first organizes the on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, pickup time window, pickup voucher identifier, voucher verification code, voucher generation time, voucher expiration time, and voucher status into a dynamic pickup voucher. The dynamic pickup voucher is then saved as a queryable backend voucher record. This allows the warehouse to initiate a scan and verification request after scanning the code using the pickup voucher identifier and voucher verification code. The platform server then verifies the corresponding digital warehouse receipt, outbound order, and pickup authorization status data.

[0109] Step S103: Construction of the delivery verification status set. After receiving the scan verification request, the platform server generates the following statuses based on the scan verification request, dynamic delivery voucher records, delivery authorization status data, warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, delivery time verification status, and verification count status. This completes the construction of the delivery verification status set.

[0110] In this step, the barcode verification request is generated by the warehouse after scanning the dynamic delivery voucher. The barcode verification request includes the delivery voucher identifier, voucher verification code, scanning warehouse identifier, scanning time, scanning terminal identifier, on-site driver identity verification information, and on-site vehicle verification information. Specifically, the delivery voucher identifier is used to query the dynamic delivery voucher record; the voucher verification code is used to generate the voucher verification status; the scanning warehouse identifier is used to generate the warehouse matching status; the scanning time is used to generate the delivery time verification status; the scanning terminal identifier identifies the scanning device or warehouse management terminal used by the warehouse; and the on-site driver identity verification information and on-site vehicle verification information are used to generate the driver identity matching status and vehicle matching status, respectively.

[0111] After receiving the QR code verification request, the platform server queries the dynamic delivery voucher record based on the delivery voucher identifier, and obtains the on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, and delivery time window from the dynamic delivery voucher record;

[0112] The platform server queries the target digital warehouse receipt based on the on-chain warehouse receipt identifier to obtain the warehouse receipt status of the target digital warehouse receipt at the time of this scan-to-verify transaction.

[0113] The platform server queries the target outbound order based on the outbound order identifier;

[0114] The platform server queries the off-chain inventory lock records based on the outbound order identifier, warehouse identifier, product batch identifier, and outbound quantity;

[0115] The platform server queries historical outbound verification records based on the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier.

[0116] In this embodiment, the off-chain inventory lock record is an inventory holding record generated or associated by the platform server after the target outbound order is generated. It is used to characterize the quantity of inventory in the target warehouse that has been locked for the target outbound order for the corresponding product batch. The off-chain inventory lock record includes an outbound order identifier, a warehouse identifier, a product batch identifier, a locked quantity, a locked status, and an off-chain inventory status. Among them, the locked quantity is used to compare with the outbound quantity in the dynamic delivery voucher record, and the locked status and off-chain inventory status are used to determine whether the corresponding inventory lock record and inventory can be used for this outbound reconciliation.

[0117] In this implementation, historical outbound reconciliation records are reconciliation result records generated and saved by the platform server during the outbound reconciliation process. These records include a delivery voucher identifier, an on-chain warehouse receipt identifier, an outbound order identifier, a reconciliation result, a reconciliation time, and a reconciliation status. The reconciliation status indicates whether the corresponding reconciliation record is a successful one. The platform server queries historical outbound reconciliation records to determine whether the same dynamic delivery voucher, the same target digital warehouse receipt, and the same target outbound order have already undergone successful reconciliation.

[0118] In this implementation, the pickup verification status set includes voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status. Each status in the pickup verification status set is used as an input status value for subsequent multi-status consistency verification. When constructing the pickup verification status set, the platform server does not directly generate allow-to-deliver instructions or abnormal verification results. Instead, it converts the barcode verification request, dynamic pickup voucher record, pickup authorization status data, target digital warehouse receipt status, off-chain inventory lock record, target delivery order, and historical delivery verification record into a verifiable status set. Specifically:

[0119] The voucher usage status includes unverified, verified, expired, and revoked. The voucher usage status is generated based on the voucher status in the dynamic delivery voucher record, the voucher expiration time, and the scan time in the scan verification request. When the voucher status in the dynamic delivery voucher record is unverified and the scan time does not exceed the voucher expiration time, the voucher usage status is unverified; when the voucher status in the dynamic delivery voucher record is verified, the voucher usage status is verified; when the voucher status in the dynamic delivery voucher record is unverified but the scan time exceeds the voucher expiration time, the voucher usage status is expired; when the voucher status in the dynamic delivery voucher record is revoked, the voucher usage status is revoked.

[0120] The voucher verification status includes "verification passed" and "verification failed." The voucher verification status is generated based on the voucher verification code in the barcode verification request and the voucher verification code stored in the dynamic delivery voucher record. The platform server compares the voucher verification code in the barcode verification request with the voucher verification code stored in the dynamic delivery voucher record to generate the voucher verification status. If a dynamic delivery voucher record can be found in the dynamic delivery voucher record table based on the delivery voucher identifier, and the voucher verification code in the barcode verification request matches the voucher verification code stored in the dynamic delivery voucher record, the voucher verification status is "verification passed." If no dynamic delivery voucher record is found, or if the voucher verification code in the barcode verification request does not match the voucher verification code stored in the dynamic delivery voucher record, the voucher verification status is "verification failed."

[0121] On-chain warehouse receipt status includes pending pickup, partial pickup, pickup completed, frozen, and abnormal. The on-chain warehouse receipt status is generated based on the warehouse receipt status of the target digital warehouse receipt queried during this scan-to-verify process. The platform server obtains the pickup voucher identifier from the scan-to-verify request and queries the dynamic pickup voucher record based on the pickup voucher identifier. It reads the on-chain warehouse receipt identifier from the dynamic pickup voucher record and queries the target digital warehouse receipt maintained by the platform server based on the on-chain warehouse receipt identifier; it reads the warehouse receipt status in the target digital warehouse receipt at the time of this scan-to-verify process and generates the on-chain warehouse receipt status based on the read warehouse receipt status. When the on-chain warehouse receipt status is pending pickup or partial pickup, it indicates that the target digital warehouse receipt is in a pickup-allowed state; when the on-chain warehouse receipt status is pickup completed, frozen, or abnormal, it indicates that the target digital warehouse receipt is in a pickup-disallowed state. The platform server does not use the historical warehouse receipt status saved in the dynamic delivery voucher record as the on-chain warehouse receipt status. Instead, when the warehouse initiates a barcode verification, it obtains the delivery voucher identifier from the barcode verification request and obtains the on-chain warehouse receipt identifier through the dynamic delivery voucher record. It then queries the warehouse receipt status in the target digital warehouse receipt in real time to avoid delays in verification results caused by changes in the status of the target digital warehouse receipt after the dynamic delivery voucher is generated.

[0122] Off-chain inventory lock status includes locked, unlocked, insufficient lock, and abnormal inventory. The off-chain inventory lock status is generated based on the locked quantity, lock status, and off-chain inventory status in the off-chain inventory lock record. The platform server queries the off-chain inventory lock record based on the outbound order identifier, warehouse identifier, product batch identifier, and outbound quantity in the dynamic delivery voucher record. When an off-chain inventory lock record corresponding to the outbound order identifier, warehouse identifier, and product batch identifier exists, and the locked quantity is greater than or equal to the outbound quantity, the off-chain inventory lock status is locked; when no corresponding off-chain inventory lock record exists, the off-chain inventory lock status is unlocked; when a corresponding off-chain inventory lock record exists, but the locked quantity is less than the outbound quantity, the off-chain inventory lock status is insufficient lock; when the corresponding off-chain inventory lock record is unavailable or in an abnormal state, the off-chain inventory lock status is abnormal inventory.

[0123] Warehouse matching status includes warehouse matching and warehouse mismatch. The warehouse matching status is generated based on the warehouse identifier scanned in the barcode verification request and the warehouse identifier in the dynamic delivery voucher record. The platform server compares the warehouse identifier scanned in the barcode verification request with the warehouse identifier in the dynamic delivery voucher record. When the warehouse identifier scanned in the request matches the warehouse identifier in the dynamic delivery voucher record, the warehouse matching status is "warehouse matching"; when the warehouse identifier scanned in the request matches the warehouse identifier in the dynamic delivery voucher record, the warehouse matching status is "warehouse mismatch".

[0124] Product batch matching status includes batch matching and batch mismatch. The batch matching status is generated based on the product batch identifier in the dynamic delivery voucher record and the product batch identifier in the off-chain inventory lock record. The platform server compares the product batch identifier in the dynamic delivery voucher record with the product batch identifier in the off-chain inventory lock record. When the product batch identifier in the dynamic delivery voucher record matches the product batch identifier in the off-chain inventory lock record, the product batch matching status is batch matching; when the product batch identifier in the dynamic delivery voucher record does not match the product batch identifier in the off-chain inventory lock record, the product batch matching status is batch mismatch.

[0125] Quantity matching status includes quantity matching, quantity mismatch, and insufficient quantity. The quantity matching status is generated based on the outbound quantity in the dynamic delivery voucher record, the outbound quantity in the target outbound order, and the locked quantity in the off-chain inventory lock record. The platform server compares the outbound quantity in the dynamic delivery voucher record, the outbound quantity in the target outbound order, and the locked quantity in the off-chain inventory lock record. When the outbound quantity in the dynamic delivery voucher record matches the outbound quantity in the target outbound order, and the locked quantity in the off-chain inventory lock record is greater than or equal to the outbound quantity, the quantity matching status is quantity matching. When the outbound quantity in the dynamic delivery voucher record does not match the outbound quantity in the target outbound order, the quantity matching status is quantity mismatch. When the outbound quantity in the dynamic delivery voucher record matches the outbound quantity in the target outbound order, but the locked quantity in the off-chain inventory lock record is less than the outbound quantity, the quantity matching status is insufficient quantity.

[0126] Driver identity matching status includes driver identity matching and driver identity mismatch. The driver identity matching status is generated based on the on-site driver identity verification information in the QR code verification request and the anonymized driver identity verification information in the dynamic delivery voucher record. The platform server generates an on-site driver identity verification value based on the on-site driver identity verification information in the QR code verification request and compares the on-site driver identity verification value with the anonymized driver identity verification information in the dynamic delivery voucher record. When the on-site driver identity verification value matches the anonymized driver identity verification information in the dynamic delivery voucher record, the driver identity matching status is "driver identity matching"; when the on-site driver identity verification value does not match the anonymized driver identity verification information in the dynamic delivery voucher record, the driver identity matching status is "driver identity mismatch".

[0127] Vehicle matching status includes vehicle matched and vehicle mismatch. The vehicle matching status is generated based on the on-site vehicle verification information in the QR code verification request and the anonymized vehicle verification information in the dynamic delivery voucher record. The platform server generates an on-site vehicle verification value based on the on-site vehicle verification information in the QR code verification request and compares the on-site vehicle verification value with the anonymized vehicle verification information in the dynamic delivery voucher record. When the on-site vehicle verification value matches the anonymized vehicle verification information in the dynamic delivery voucher record, the vehicle matching status is vehicle matched; when the on-site vehicle verification value does not match the anonymized vehicle verification information in the dynamic delivery voucher record, the vehicle matching status is vehicle mismatch.

[0128] The pickup time verification status includes time verification passed, authorization time sequence abnormality, earlier than the pickup time window, and later than the pickup time window. The pickup time verification status is based on the authorization generation time and pickup time window in the pickup authorization status data, the voucher generation time and voucher expiration time in the dynamic pickup voucher record, and the scan time generation in the scan verification request. The platform server obtains the authorization generation time and pickup time window from the pickup authorization status data, the voucher generation time and voucher expiration time from the dynamic pickup voucher record, and the scan time from the scan verification request. The platform server first performs time sequence verification on the authorization generation time, voucher generation time, voucher expiration time, and scan time. When the authorization generation time is later than the voucher generation time, or the voucher generation time is later than the scan time, or the authorization generation time is later than the voucher expiration time, the pickup time verification status is authorization time sequence abnormal. When the authorization generation time is not later than the voucher generation time, the voucher generation time is not later than the scan time, and the authorization generation time is not later than the voucher expiration time, the platform server compares the scan time with the pickup time window. When the scanning time is no earlier than the pickup start time and no later than the pickup end time, the pickup time verification status is "Time Verification Passed"; when the scanning time is earlier than the pickup start time, the pickup time verification status is "Earlier than the Pickup Time Window"; when the scanning time is later than the pickup end time, the pickup time verification status is "Later than the Pickup Time Window".

[0129] The reconciliation count status includes whether the single reconciliation conditions are met or not. The reconciliation count status is generated based on historical outbound reconciliation records. The platform server queries historical outbound reconciliation records based on the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier. When no successful reconciliation record corresponding to the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier is found, the reconciliation count status is "meets the single reconciliation conditions"; when a successful reconciliation record corresponding to the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier is found, the reconciliation count status is "does not meet the single reconciliation conditions".

[0130] It should be noted that the generation rules for on-site driver identity verification values ​​and on-site vehicle verification values ​​are consistent with the generation rules for de-identified driver identity verification information and de-identified vehicle verification information.

[0131] Based on the above-mentioned voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and number of verifications, the platform server constructs a pickup verification status set.

[0132] In this way, before performing multi-state consistency verification, the platform server first converts the scan verification request, dynamic pickup voucher record, pickup authorization status data, target digital warehouse receipt status, off-chain inventory lock record, target outbound order and historical outbound verification record into a set of verifiable pickup verification statuses. This allows subsequent multi-state consistency verification to be performed item by item based on the same set of statuses, avoiding the warehouse from releasing goods directly based solely on the existence of the pickup code or the order.

[0133] Step S104: Multi-state consistency verification and verification result processing. Based on the set of delivery verification states, perform multi-state consistency verification, generate verification results, and send the verification results to the warehouse.

[0134] In this step, the verification results include verification pass and verification fail. When the verification result is verification pass, an allow-to-deliver instruction is output to the warehouse, and the voucher status in the dynamic delivery voucher record, the authorization status in the delivery authorization status data, the target digital warehouse receipt, and the off-chain inventory lock record are updated; when the verification result is verification fail, an exception prompt message is output to the warehouse, and an exception verification record is generated. Specifically:

[0135] In this embodiment, the platform server performs multi-state consistency verification on the pickup verification status set, including:

[0136] When the voucher usage status is "not rescinded", the voucher verification status is "voucher verification passed", the on-chain warehouse receipt status is "pending pickup or partial pickup", the off-chain inventory lock status is "locked", the warehouse matching status is "warehouse matching", the product batch matching status is "batch matching", the quantity matching status is "quantity matching", the driver identity matching status is "driver identity matching", the vehicle matching status is "vehicle matching", the pickup time verification status is "time verification passed", and the rescinding count status is "meets the single rescinding condition", the verification result is determined to be "verification passed".

[0137] Otherwise, the verification result will be considered an anomaly.

[0138] When the verification result is successful, the platform server generates a record for this outbound reconciliation. This record includes the delivery voucher identifier, on-chain warehouse receipt identifier, outbound order identifier, reconciliation result, reconciliation time, and reconciliation status. The platform server updates the voucher status in the dynamic delivery voucher record to "reconciled," updates the authorization status in the delivery authorization status data to "completed," and updates the locked quantity, reconciled quantity, available delivery quantity, and warehouse receipt status in the target digital warehouse receipt based on the outbound quantity. Simultaneously, the corresponding off-chain inventory lock record is updated to the "reconciled" status.

[0139] When the verification result is abnormal, the platform server generates an abnormal verification record. The abnormal verification record includes the delivery voucher identifier, the outbound order identifier, the scanning time, the scanning warehouse identifier, and the scanning terminal identifier. The platform server returns the abnormal verification result to the warehouse, causing the warehouse to stop the current outbound verification operation.

[0140] Figure 2 This is a schematic diagram illustrating the structure of a delivery verification system based on digital warehouse receipts, according to an example embodiment of this application. Figure 2 As shown, the delivery verification system 200 based on digital warehouse receipts provided in this embodiment includes: a delivery authorization status data construction module 210, a dynamic delivery voucher generation module 220, a delivery verification status set construction module 230, and a multi-state consistency verification and verification result processing module 240.

[0141] The pickup authorization status data construction module 210, after receiving the pickup authorization request, generates a target outbound order based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Based on the target outbound order, the authorization generation time, and the authorization status, the pickup authorization status data is constructed.

[0142] The dynamic pickup voucher generation module 220 generates a pickup voucher identifier and a voucher verification code based on the pickup authorization status data, determines the voucher generation time and voucher expiration time, and generates a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time and voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, it generates a barcode verification request and sends the barcode verification request to the platform server.

[0143] The pickup verification status set construction module 230, after the platform server receives the scan verification request, generates the following statuses based on the scan verification request, dynamic pickup voucher records, pickup authorization status data, warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status and verification count status, and constructs the pickup verification status set.

[0144] The multi-state consistency verification and verification result processing module 240 performs multi-state consistency verification based on the set of delivery verification states, generates verification results, and sends the verification results to the warehouse.

[0145] Figure 3 This is a schematic diagram of the structure of an electronic device according to an example embodiment of this application. For example... Figure 3 As shown, the electronic device 300 provided in this embodiment includes: a processor 301 and a memory 302; wherein:

[0146] Memory 302 is used to store computer programs, and the memory may also be flash memory.

[0147] Processor 301 is used to execute the execution instructions stored in the memory to implement the various steps in the above method. For details, please refer to the relevant descriptions in the preceding method embodiments.

[0148] Alternatively, the memory 302 can be either standalone or integrated with the processor 301.

[0149] When the memory 302 is a device independent of the processor 301, the electronic device 300 may further include:

[0150] Bus 303 is used to connect the memory 302 and the processor 301.

[0151] This embodiment also provides a readable storage medium storing a computer program, which, when executed by at least one processor of an electronic device, enables the electronic device to perform the methods provided in the various embodiments described above.

[0152] This embodiment also provides a program product including a computer program stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the electronic device to perform the methods provided in the various embodiments described above.

[0153] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the foregoing claims.

[0154] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope.

Claims

1. A method for verifying delivery based on digital warehouse receipts, characterized in that, include: Upon receiving a pickup authorization request, a target outbound order is generated based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Based on the target outbound order, the authorization generation time, and the authorization status, pickup authorization status data is constructed. Dynamic pickup voucher generation involves generating a pickup voucher identifier and voucher verification code based on the pickup authorization status data, determining the voucher generation time and voucher expiration time, and generating a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time, and voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, it generates a barcode verification request and sends the barcode verification request to the platform server. The platform server, upon receiving a scan verification request, generates the following status sets based on the scan verification request, dynamic pickup voucher records, pickup authorization status data, the warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders, and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status. Multi-state consistency verification and verification result processing: Based on the set of delivery verification states, multi-state consistency verification is performed, verification results are generated, and the verification results are sent to the warehouse.

2. The delivery verification method based on digital warehouse receipts according to claim 1, characterized in that, The target digital warehouse receipt includes an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, a warehouse receipt quantity, a locked quantity, a verified quantity, a redeemable quantity, and a warehouse receipt status; The target outbound order includes an outbound order identifier, an on-chain warehouse receipt identifier, a product batch identifier, a warehouse identifier, an outbound quantity, de-identified driver identity verification information, de-identified vehicle verification information, and a pickup time window; The pickup authorization status data includes outbound order identifier, on-chain warehouse receipt identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, pickup time window, authorization generation time, and authorization status; The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier, and the delivery authorization status data is associated with the target outbound order through an outbound order identifier.

3. The delivery verification method based on digital warehouse receipts according to claim 1, characterized in that, The dynamic pickup voucher is stored on the platform server in the form of a dynamic pickup voucher record. The dynamic pickup voucher record includes a pickup voucher identifier, a voucher verification code, an on-chain warehouse receipt identifier, an outbound order identifier, a product batch identifier, a warehouse identifier, an outbound quantity, de-identified driver identity verification information, de-identified vehicle verification information, a pickup time window, a voucher generation time, a voucher expiration time, and a voucher status. The dynamic pickup voucher is displayed on the buyer's or driver's end in the form of a QR code, barcode, electronic pickup code, or mini-program page voucher. The QR code, barcode, electronic pickup code, or mini-program page voucher includes at least a pickup voucher identifier and a voucher verification code. The scan verification request includes the delivery voucher identifier, voucher verification code, scan warehouse identifier, scan time, scan terminal identifier, on-site driver identity verification information, and on-site vehicle verification information.

4. The delivery verification method based on digital warehouse receipts according to claim 3, characterized in that, After receiving the QR code verification request, the platform server queries the dynamic delivery voucher record based on the delivery voucher identifier, and obtains the on-chain warehouse receipt identifier, outbound order identifier, product batch identifier, warehouse identifier, outbound quantity, anonymized driver identity verification information, anonymized vehicle verification information, and delivery time window from the dynamic delivery voucher record. The platform server queries the target digital warehouse receipt based on the on-chain warehouse receipt identifier and obtains the warehouse receipt status of the target digital warehouse receipt at the time of this scan-to-verify. The platform server queries the target outbound order based on the outbound order identifier; The platform server queries the off-chain inventory lock records based on the outbound order identifier, warehouse identifier, product batch identifier, and outbound quantity. The platform server queries historical outbound verification records based on the delivery voucher identifier, on-chain warehouse receipt identifier, and outbound order identifier.

5. The delivery verification method based on digital warehouse receipts according to claim 1, characterized in that, The voucher usage status is generated based on the voucher status, voucher expiration time, and scan time in the scan verification request in the dynamic delivery voucher record. The voucher verification status is generated based on the voucher verification code in the scan verification request and the voucher verification code stored in the dynamic delivery voucher record; The on-chain warehouse receipt status is generated based on the warehouse receipt status of the target digital warehouse receipt queried during this scan-to-verify process; The off-chain inventory lock status is generated based on the locked quantity, lock status, and off-chain inventory status in the off-chain inventory lock record. The warehouse matching status is generated based on the warehouse identifier in the scanned verification request and the warehouse identifier in the dynamic delivery voucher record. The product batch matching status is generated based on the product batch identifier in the dynamic delivery voucher record and the product batch identifier in the off-chain inventory lock record. The quantity matching status is generated based on the outbound quantity in the dynamic delivery voucher record, the outbound quantity in the target outbound order, and the locked quantity in the off-chain inventory lock record; The driver identity matching status is generated based on the on-site driver identity verification information in the QR code verification request and the de-identified driver identity verification information in the dynamic delivery voucher record. The vehicle matching status is generated based on the on-site vehicle verification information in the QR code verification request and the de-identified vehicle verification information in the dynamic delivery voucher record. The delivery time verification status is generated based on the authorization generation time and delivery time window in the delivery authorization status data, the voucher generation time and voucher expiration time in the dynamic delivery voucher record, and the scanning time in the scanning verification request. The number of reconciliations is generated based on historical outbound reconciliation records.

6. The delivery verification method based on digital warehouse receipts according to claim 1, characterized in that, The verification results include verification passed and verification abnormal; When the verification result is that the verification is passed, an allow delivery instruction is output to the warehouse end, and the voucher status in the dynamic delivery voucher record, the authorization status in the delivery authorization status data, the target digital warehouse receipt and the off-chain inventory lock record are updated. When the verification result is abnormal, an abnormal prompt message is output to the warehouse and an abnormal verification record is generated.

7. The delivery verification method based on digital warehouse receipts according to claim 6, characterized in that, When the voucher usage status is unverified, the voucher verification status is voucher verification passed, the on-chain warehouse receipt status is pending pickup or partial pickup, the off-chain inventory lock status is locked, the warehouse matching status is warehouse matching, the product batch matching status is batch matching, the quantity matching status is quantity matching, the driver identity matching status is driver identity matching, the vehicle matching status is vehicle matching, the pickup time verification status is time verification passed, and the verification count status meets the single verification condition, the verification result is determined to be verification passed. Otherwise, the verification result will be considered an anomaly.

8. A delivery verification system based on digital warehouse receipts, characterized in that, include: The pickup authorization status data construction module, upon receiving a pickup authorization request, generates a target outbound order based on the target digital warehouse receipt. The target outbound order is associated with the target digital warehouse receipt through an on-chain warehouse receipt identifier. Based on the target outbound order, the authorization generation time, and the authorization status, the pickup authorization status data is constructed. The dynamic pickup voucher generation module generates a pickup voucher identifier and a voucher verification code based on the pickup authorization status data, determines the voucher generation time and voucher expiration time, and generates a dynamic pickup voucher based on the pickup authorization status data, pickup voucher identifier, voucher verification code, voucher generation time and voucher expiration time. The dynamic pickup voucher is displayed in a scannable form on the buyer's or driver's end. When the warehouse scans the dynamic pickup voucher, it generates a barcode verification request and sends the barcode verification request to the platform server. The pickup verification status set construction module is as follows: After receiving the scan verification request, the platform server generates the following statuses based on the scan verification request, dynamic pickup voucher records, pickup authorization status data, warehouse receipt status of the target digital warehouse receipt queried during this scan verification, off-chain inventory lock records, target outbound orders and historical outbound verification records: voucher usage status, voucher verification status, on-chain warehouse receipt status, off-chain inventory lock status, warehouse matching status, product batch matching status, quantity matching status, driver identity matching status, vehicle matching status, pickup time verification status, and verification count status, thus constructing the pickup verification status set. The multi-state consistency verification and verification result processing module performs multi-state consistency verification based on the set of delivery verification states, generates verification results, and sends the verification results to the warehouse.

9. An electronic device, characterized in that, include: processor; as well as, Memory for storing the executable instructions of the processor; The processor is configured to execute the method of any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 7.

Images