A tissue paper sales order flow and delivery matching management system

Abstract

This invention relates to the field of order processing and warehousing management technology, and more specifically, to a tissue sales order processing and shipment matching management system. The system includes an order processing object generation module, a volumetric billing snapshot generation module, a warehousing and distribution route generation module, an order splitting and verification gating module, a warehousing and distribution locking execution module, and a performance deviation correction module. The system converts tissue sales orders into candidate package clusters and binds them to delivery billing standards, forming an order package cluster billing snapshot. Based on this snapshot, the status of delivery resources, and delivery channel rules, it generates a warehousing and distribution constraint diagram and a warehousing and distribution route. It performs order splitting and verification on the combined resource routes, and enters the shipment decision stage after meeting the gating conditions. After shipment, it corrects the snapshot, constraint diagram, and gating parameters based on the performance deviation attribution ledger. This system is suitable for order processing and shipment matching management of volume-sensitive products such as tissues.

Description

Technical Field

[0001] This invention relates to the field of order flow and warehousing management technology, and more specifically, to a paper towel sales order flow and delivery matching management system. Background Technology

[0002] Tissue paper products are daily consumer goods, and sales orders are typically characterized by large order quantities, numerous SKUs, a mix of full-case and individual orders, and high shipping frequency. With the increasing prevalence of online sales, distributor ordering, and multi-warehouse shipping models, tissue paper sales orders often require simultaneous processing of order status, inventory resources, warehouse shipping capacity, delivery channel rules, and logistics costs. Existing order management systems generally handle basic processing such as order receipt, inventory matching, warehouse allocation, logistics channel selection, and shipping status updates.

[0003] However, tissue products are significantly more volume-sensitive than ordinary goods. Most tissue products are relatively lightweight, but their outer packaging is bulky, easily leading to a volumetric weight exceeding the actual weight in logistics billing. For orders containing multiple sizes of tissues, shipping in full cases, split shipments, combined boxes, or multiple parcels directly impacts the number of parcels, volumetric weight, chargeable weight, and final shipping costs. Matching shipments solely based on inventory availability, warehouse distance, or basic channel pricing easily overlooks the cost differences arising from different parcel combinations under volumetric billing.

[0004] Current systems typically use product quantity, inventory quantity, warehouse location, and logistics channel as the primary matching criteria when processing tissue orders, lacking an intermediate processing layer that addresses the volumetric attributes of tissues. Specifically, tissues in an order can be packaged in different ways—whether shipped as a whole unit, in smaller units, or in a mixed shipment—and different delivery channels may employ different volumetric weight conversion rules, oversize limits, and billing methods. Existing matching methods generally fail to integrate order package combinations, the difference between actual weight and volumetric weight, the relationship between billing methods, and volumetric billing premiums into the warehousing and distribution route selection process. This results in the actual cost differences for the same order across different warehouses and channels not being reflected in timely shipping decisions.

[0005] Therefore, we propose a paper towel sales order flow and delivery matching management system to solve the above problems. Summary of the Invention

[0006] In order to overcome the above-mentioned defects of the prior art, embodiments of the present invention provide a tissue sales order flow and delivery matching management system to solve the problems mentioned in the background art.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a tissue paper sales order flow and delivery matching management system, comprising: The order flow object generation module is used to generate order flow objects based on tissue sales order data and establish an order flow status chain corresponding to the order flow object; The volumetric billing snapshot generation module is connected to the order flow object generation module. It is used to call the volume-sensitive tissue delivery unit model, convert the order flow object into a candidate package cluster, bind the delivery billing caliber to the candidate package cluster, and generate an order package cluster billing snapshot. The order package cluster billing snapshot includes at least the candidate package cluster, the billing caliber binding relationship, the actual weight-volume weight difference marker, and the volumetric billing premium benchmark. The warehousing and distribution route generation module is connected to the volume billing snapshot generation module. It is used to generate a warehousing and distribution constraint diagram based on the order package cluster billing snapshot, shipping resource status data and delivery channel rule data. The warehousing and distribution constraint diagram is used to generate single-resource warehousing and distribution routes, combined resource warehousing and distribution routes and reserved warehousing and distribution routes. The order splitting and reversal gate module, connected to the warehousing and distribution path generation module, is used to establish a corresponding warehousing and distribution path within the same domain based on a single resource warehousing and distribution path or a reserved warehousing and distribution path. It then compares the combined resource warehousing and distribution path with the corresponding warehousing and distribution path within the same domain to generate an order splitting and reversal package. When the order splitting revenue item in the order splitting and reversal package covers the order splitting loss item, and the volume billing premium constraint, performance dispersion constraint, and abnormal risk constraint are not triggered, the gate lock of the corresponding combined resource warehousing and distribution path is released. Otherwise, the corresponding combined resource warehousing and distribution path is marked as a restricted path, and the corresponding reserved warehousing and distribution path is output. The warehousing and distribution locking execution module, connected to the order splitting and verification gating module, is used to determine the target warehousing and distribution delivery plan among the combined resource warehousing and distribution path, single resource warehousing and distribution path and the reserved warehousing and distribution path after the gating lock is released, and to generate a delivery locking event. The delivery locking event is used to lock the order flow object, target package cluster, target delivery resource, target delivery channel and order flow status chain, and generates a delivery execution task after the lock consistency verification is passed. The performance deviation correction module is connected to the warehousing and distribution lock execution module, the volume billing snapshot generation module, the warehousing and distribution route generation module, and the order splitting and reversal gate control module. It is used to compare the actual delivery data with the target warehousing and distribution delivery plan, generate the performance deviation attribution ledger, and correct the order package cluster billing snapshot generation parameters, warehousing and distribution constraint diagram parameters, and order splitting and reversal gate control parameters when the performance deviation attribution ledger meets the correction stability threshold and is not in the correction freeze window. The order flow object generation module is also used to update the order flow status chain based on the order package cluster billing snapshot, warehousing and distribution path generation results, order splitting and verification results, shipment lock events, and performance deviation attribution ledger.

[0008] In a preferred embodiment, the volume-sensitive tissue paper delivery unit model is generated by the volume-sensitive tissue paper delivery unit graph construction module; the volume-sensitive tissue paper delivery unit graph construction module is used to generate delivery unit nodes, packaging conversion edges, volume billing edges, and packing constraint edges; the delivery unit nodes correspond to the whole package delivery form, split package delivery form, or mixed delivery form of tissue paper products; the packaging conversion edges are used to associate the whole package to split package conversion between different delivery forms; the volume billing edges are used to associate the actual weight-volume weight difference and volume billing premium under different delivery forms; the packing constraint edges are used to associate the packing adaptation relationship when different delivery units are combined to form a package.

[0009] In a preferred embodiment, the volumetric billing snapshot generation module includes an order mapping unit, a package cluster generation unit, a billing caliber binding unit, and a snapshot generation unit. The order mapping unit is used to map order flow objects to volume-sensitive tissue delivery unit models. The package cluster generation unit is used to generate candidate package clusters based on the mapping results and determine the packaging combination relationship and package quantity relationship corresponding to the candidate package clusters. The billing caliber binding unit is used to bind the candidate package clusters with the billing caliber in the delivery channel rules to obtain the billing caliber binding relationship. The snapshot generation unit is used to generate actual weight-volume weight difference markers, volumetric billing premium benchmarks, whole-to-part conversion loss markers, and delivery channel adaptation markers based on the candidate package clusters and the billing caliber binding relationship, and form an order package cluster billing snapshot.

[0010] In a preferred embodiment, the warehousing and distribution constraint graph includes parcel cluster nodes, shipping resource nodes, delivery channel nodes, shipping adaptation edges, channel billing edges, and locking conflict edges. Parcel cluster nodes are generated from candidate parcel clusters in the order parcel cluster billing snapshot. Shipping adaptation edges connect parcel cluster nodes and shipping resource nodes, and are configured with resource satisfaction status, packaging processing status, and shipping load status. Channel billing edges connect shipping resource nodes and delivery channel nodes, and are configured with billing caliber adaptation status, delivery restriction status, and volume billing premium status. Locking conflict edges are used to represent the occupancy conflict status between order flow objects, shipping resource nodes, delivery channel nodes, and order flow state chains.

[0011] In a preferred embodiment, the warehousing and distribution route generation module includes a single-resource route generation unit, a combined resource route generation unit, a reserved route generation unit, and a route filtering unit. The single-resource route generation unit generates a single-resource warehousing and distribution route based on the package cluster node, shipping adaptation edge, channel billing edge, and delivery channel node connected to the same shipping resource node. The combined resource route generation unit generates a combined resource warehousing and distribution route based on multiple shipping resource nodes when the single-resource warehousing and distribution route does not meet the order shipping requirements or when the cost status of the single-resource warehousing and distribution route exceeds the preset route constraints. The reserved route generation unit generates a reserved warehousing and distribution route when the single-resource warehousing and distribution route is not executable and the combined resource warehousing and distribution route fails the order splitting and counter-verification gate. The route filtering unit filters the single-resource warehousing and distribution route, combined resource warehousing and distribution route, and reserved warehousing and distribution route based on the availability status, cost status, risk status, and locking status of the shipping adaptation edge, channel billing edge, and locking conflict edge.

[0012] In a preferred embodiment, the split order verification package includes split order benefit items and split order loss items; the split order benefit items include at least the resource satisfaction improvement result of the combined resource warehousing and distribution path relative to the same domain comparison warehousing and distribution path; the split order loss items include at least the packaging quantity increment, volume billing premium increment, fulfillment dispersion increment, and abnormal risk increment; when the split order benefit items cover the split order loss items, and the volume billing premium increment, fulfillment dispersion increment, and abnormal risk increment do not trigger the corresponding constraints, the split order verification gating module releases the gating lock of the corresponding combined resource warehousing and distribution path; when the split order benefit items do not cover the split order loss items, or any increment triggers the corresponding constraint, the split order verification gating module marks the corresponding combined resource warehousing and distribution path as a restricted path.

[0013] In a preferred embodiment, the warehousing and distribution locking execution module includes a path evaluation unit, a conflict resolution unit, a locking event generation unit, and a task generation unit. The path evaluation unit generates path evaluation results for warehousing and distribution paths entering the decision-making process. The path evaluation results include volume billing evaluation results, shipping resource occupancy evaluation results, delivery channel adaptation evaluation results, order flow timeliness evaluation results, and abnormal risk evaluation results. The conflict resolution unit resolves conflicts in warehousing and distribution paths with resource occupancy conflicts, channel occupancy conflicts, or order flow status conflicts based on the locking status of the locking conflict edges, thereby obtaining lockable warehousing and distribution paths. The locking event generation unit determines the target warehousing and distribution path among the lockable warehousing and distribution paths and generates a shipping locking event. The task generation unit generates a shipping execution task after the shipping locking event passes the locking consistency verification.

[0014] In a preferred embodiment, the warehousing and distribution locking execution module further includes a state consistency verification unit; the state consistency verification unit is used to verify the consistency between the shipment locking event and the warehousing and distribution constraint graph when the state of the order flow state chain, target package cluster, target shipment resource or target delivery channel changes; when the consistency verification passes, the shipment execution task can be generated or continue to be executed; when the consistency verification fails, the warehousing and distribution path generation module is triggered to regenerate the warehousing and distribution path.

[0015] In a preferred embodiment, the performance deviation attribution ledger includes volume billing deviation items, packaging combination deviation items, shipping resource deviation items, distribution channel deviation items, lock-in conflict deviation items, retention path deviation items, and order splitting gating deviation items. The performance deviation correction module is used to correct the generation parameters of the volume-sensitive tissue shipping unit model and order package cluster billing snapshot based on the volume billing deviation items and packaging combination deviation items; correct the warehousing and distribution constraint diagram parameters based on the shipping resource deviation items, distribution channel deviation items, lock-in conflict deviation items, and retention path deviation items; correct the order splitting counter-evidence gating parameters based on the order splitting gating deviation items; and correct the stability threshold, which includes at least one of the following: similar deviation persistence condition, deviation magnitude condition, and similar order recurrence condition.

[0016] The technical effects and advantages of this invention are as follows: 1. This invention uses order package cluster billing snapshots to take candidate package clusters, billing caliber binding relationships, actual weight-volume weight difference markers, and volume billing premium benchmarks as pre-data for generating warehousing and distribution routes, so that the volume billing impact of tissue orders can enter the warehousing and distribution constraint diagram and route evaluation process before shipment matching.

[0017] 2. This invention uses a warehousing and distribution constraint graph to uniformly represent package cluster nodes, shipping resource nodes, and delivery channel nodes, as well as shipping adaptation edges, channel billing edges, and locking conflict edges, so that single-resource warehousing and distribution paths, combined resource warehousing and distribution paths, and reserved warehousing and distribution paths are simultaneously constrained by package combinations, shipping resource status, and delivery billing rules.

[0018] 3. This invention uses the same-domain comparison of warehousing and distribution routes and split order verification to perform gating judgment on the resource satisfaction improvement results, packaging quantity increment, volume billing premium increment, fulfillment dispersion increment, and abnormal risk increment of combined resource warehousing and distribution routes, so that the combined resource routes have clear access conditions before entering the shipping decision.

[0019] 4. This invention uses shipment locking events and status consistency verification to synchronously verify the order flow object, target package cluster, target shipment resources, target delivery channels and order flow status chain, and triggers the regeneration of the warehousing and distribution path when the verification fails.

[0020] 5. This invention attributes actual delivery deviations to factors such as volume billing, packaging combination, delivery resources, distribution channels, lock-in conflicts, reserved paths, and order splitting gates by using a performance deviation attribution ledger, a modified stability threshold, and a modified freeze window. When stability conditions are met, the corresponding parameters are corrected in a targeted manner. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the overall process of the present invention; Figure 2 This is a schematic diagram of the volume-sensitive tissue delivery unit model in this invention; Figure 3 This is a schematic diagram illustrating the generation of order package cluster billing snapshots in this invention; Figure 4 This is a schematic diagram of the warehousing and distribution constraint diagram structure in this invention; Figure 5 This is a schematic diagram of the warehousing and distribution path generation and filtering in this invention; Figure 6 This is a schematic diagram of the gate control for splitting single-issue and reverse-issue certificates in this invention; Figure 7 This is a schematic diagram of the joint decision-making and locking execution of warehousing and distribution in this invention; Figure 8 This is a schematic diagram of the shipment locking and status consistency verification in this invention; Figure 9 This is a schematic diagram of the attribution correction for performance deviation in this invention. Detailed Implementation

[0022] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0023] Reference Figure 1 This invention relates to a tissue paper sales order flow and delivery matching management system. The system can be deployed on an order fulfillment server or serve as an intermediary processing service between the order management system, warehouse management system, and transportation management system. The system connects to the sales order platform, product master data system, warehouse inventory system, delivery channel rule base, and delivery performance feedback interface. A unique identifier for each order flow object is used to connect all modules, ensuring that order data, package cluster billing results, warehousing and distribution routes, delivery lock events, and performance deviation records can be mapped to the same order flow process.

[0024] Reference Figure 2After the above data enters the system, it is first organized uniformly according to the processing requirements of the order flow objects. The sales order platform provides order identifiers, product items, order quantities, receiving areas, time requirements, and order splitting restrictions; the product master data system provides the shipping form, packaging level, packaging size, actual weight, relationship between whole and split packages, and packing restrictions for paper towels; the warehouse inventory system provides the inventory availability status of shipping resources, packaging processing capacity, current shipping load, and node occupancy status; the delivery channel rule base provides delivery areas, billing standards, volumetric weight conversion rules, size restrictions, weight restrictions, and channel availability status; the shipping performance feedback interface provides the actual number of packages, actual billing weight, actual shipping cost, actual fulfillment time, and abnormal results. The system unifies the above data in terms of order identifiers, product codes, weight and volume units, removes duplicate records, aligns time nodes, and marks abnormal fields; for data lacking key billing standards, shipping resource status, or product packaging attributes, the order flow object generation module marks the corresponding order as pending completion and does not enter the warehousing and distribution path generation process. For order flow objects marked as pending completion, the system records the type and source of missing fields. Once the product master data, delivery channel rule data, or shipping resource status data are corrected, the order flow object generation module re-executes the field integrity check. Order flow objects that pass the check enter the order modeling completion state and trigger the volume billing snapshot generation module to re-call the volume-sensitive tissue shipping unit model. Order flow objects that still fail the check remain in the pending completion state and do not enter the warehouse and distribution constraint diagram generation process. The processed data is written to the order flow object, the volume-sensitive tissue shipping unit model, the warehouse and distribution constraint diagram, and the performance deviation attribution ledger, respectively, as the basic data for subsequent module calls.

[0025] The preprocessed data is saved as the order flow object field, the product shipping attribute field, the shipping resource status field, the delivery channel rule field, and the performance feedback field, respectively. When the module calls the data, the order identifier and the product code are used as the primary association keys, and the warehouse or shipping point identifier and the delivery channel identifier are used as secondary association keys.

[0026] After receiving the tissue sales order data, the order flow object generation module first performs format validation, duplicate order validation, and order status validation on the order data. The tissue sales order data includes at least the order identifier, product details, order quantity, delivery area, delivery time requirements, whether order splitting is allowed, and the current order status. The validated order data is organized into order flow objects. These order flow objects are not directly used as the shipping plan, but rather as a unified data object for subsequent package cluster billing, warehousing and distribution route generation, and shipment locking.

[0027] The order flow object generation module simultaneously establishes an order flow state chain. This order flow state chain includes at least the following state nodes: order modeling, package cluster billing, warehousing and distribution route generation, order splitting gating, warehousing and distribution locking, shipment execution, and performance feedback correction. Each state node records the state entry time, state source, corresponding intermediate result, and exception flag. Therefore, subsequent modules' generated order package cluster billing snapshots, warehousing and distribution routes, order splitting verification results, shipment locking events, and performance deviation attribution ledgers can all be written back to this order flow state chain, preventing the order status from becoming disconnected from the warehousing and distribution execution process.

[0028] Before processing order flow objects, the volume-sensitive tissue shipping unit generation module calls the volume-sensitive tissue shipping unit model. This model is pre-generated and maintained by the volume-sensitive tissue shipping unit graph construction module. The volume-sensitive tissue shipping unit graph construction module takes tissue product shipping attribute data as input, which may include the tissue product's shipping form, packaging level, relationship between whole package and individual packages, packaging volume, actual weight, packing restrictions, and basic parameters related to delivery billing caliber.

[0029] When changes occur in the product master data regarding packaging dimensions, actual weight, quantity per unit, splitting rules, packing restrictions, or delivery billing methods, the volume-sensitive tissue shipping unit graph construction module re-verifies the corresponding shipping unit nodes, packaging conversion edges, volume billing edges, and packing constraint edges, and configures a version identifier for the updated volume-sensitive tissue shipping unit model. Invalid nodes or edges are retained as historical records but do not participate in new order mappings or candidate package cluster generation. When the volume billing snapshot generation module calls this model, it reads a valid version that matches the current order processing time and delivery channel rules to ensure that the order package cluster billing snapshot is generated based on valid product shipping attributes and billing rules.

[0030] The volume-sensitive tissue paper shipping unit diagram includes shipping unit nodes, packaging conversion edges, volumetric billing edges, and packing constraint edges. Shipping unit nodes correspond to whether the tissue paper product is shipped in a full package, in individual units, or in a mixed package. Packaging conversion edges express the conversion relationship between different shipping formats, such as splitting a full package into multiple individual units, or combining multiple individual units into a mixed package. Volumetric billing edges express the difference between the actual weight and the volumetric weight under different shipping formats, and the resulting volumetric billing premium. Packing constraint edges express whether different shipping units combined into a package meet packing compatibility requirements, including whether they can be packaged together, whether the package capacity is exceeded, and whether there is packing loss.

[0031] When constructing the volume-sensitive tissue shipping unit model, the system does not use the quantity of a single product as the basis for shipping calculations. Instead, it uses the executable packaging form of tissue products during the shipping process as the modeling object. Whole-case shipping unit nodes correspond to packaging forms that can be shipped without being broken down into smaller units. Segmented shipping unit nodes correspond to individual packing forms separated from whole-case units. Mixed shipping unit nodes correspond to packing forms resulting from combinations of different tissue products or different segmented units. Packaging conversion edges record the conversion relationships between whole-case, segmented, and mixed forms, maintaining consistency in product quantity before and after conversion. Volumetric billing edges read the volumetric weight conversion caliber from the delivery channel rules, compare the actual weight of the shipping unit with the volumetric weight converted based on packaging volume, and record the impact of the difference on the billing weight. Packing constraint edges record whether the combined shipping units exceed the package capacity, whether additional packages are needed, and whether there is packing loss. During graph verification, if the packaging conversion relationship cannot maintain consistency in product quantity, or if the packing constraint does not match the volume and weight status of the shipping unit, then that node or edge will not participate in the generation of the order package cluster billing snapshot.

[0032] When generating the mapping graph, the system first generates shipping unit nodes, then establishes packaging conversion edges between nodes; subsequently, it configures volumetric billing edges for relevant nodes based on delivery billing standards; finally, it establishes packing constraint edges based on packing adaptation relationships. Consistency checks are performed after the mapping graph is generated. If the quantity of individual items corresponding to a packaging conversion edge is inconsistent with the number of shipping unit nodes, or if the package capacity corresponding to a packing constraint edge does not match the shipping unit combination relationship, then that edge is marked as unavailable and will not participate in subsequent order mapping. Through this mapping graph, the volume-sensitive attribute of tissue paper products no longer remains in the ordinary product specification field, but becomes the foundational structure for subsequent package cluster billing and route generation.

[0033] Reference Figure 3 After obtaining the order flow object, the volumetric billing snapshot generation module maps the product items in the order to the volume-sensitive tissue shipping unit model. During mapping, the system matches the corresponding shipping unit node and its packaging conversion edge, volumetric billing edge, and packing constraint edge according to the order product, order quantity, and allowed split status. After mapping is completed, the package cluster generation unit forms candidate package clusters.

[0034] When generating candidate package clusters, the package cluster generation unit first matches the order quantity of the same tissue product in the order with the corresponding quantity of the full-case shipping unit. The portion that can be shipped as a full case forms a full-case candidate package cluster; the portion that is insufficient for a full case or allows for splitting forms a split-case candidate package cluster along the packaging conversion edge; when multiple split-case shipping units meet the same-package condition in the packing constraint edge, they are combined to form a mixed candidate package cluster. For the same order, the system can retain multiple candidate package cluster schemes, but each candidate package cluster must meet three conditions: no loss of product quantity, no duplicate use of shipping units, and availability of the packing constraint edge. Package combinations that do not meet the above conditions are not included in the order package cluster billing snapshot. For multiple candidate package cluster schemes that meet the above conditions, the system deduplicates the candidate package clusters according to the shipping unit combination relationship within the package, the package quantity relationship, and the shipping form; for schemes with the same shipping unit combination but different package order, one candidate package cluster record is retained. For candidate package clusters with different shipping unit combinations, the system retains their corresponding full-case, split-case, or mixed shipping status and sends them to the billing caliber binding unit to participate in the billing caliber binding under different delivery channels. Therefore, each candidate package cluster entering the billing snapshot of the order package cluster has a clear packaging combination relationship and package quantity relationship. The candidate package cluster represents one or more packages formed by an order under a certain packaging combination method. Its content includes the combination relationship of the shipping units within the package, the package quantity relationship, and the corresponding whole package, split package, or mixed shipping status.

[0035] The billing caliber binding unit binds candidate package clusters with the billing calibers in the delivery channel rules. Delivery channel rules may include actual weight billing, volumetric weight billing, billing based on the larger of actual weight and volumetric weight, oversize restrictions, regional delivery restrictions, and channel inaccessibility conditions. During binding, the system determines the billing caliber for each candidate package cluster under different delivery channels and establishes a billing caliber binding relationship. For the same candidate package cluster, if the volumetric weight is significantly higher than the actual weight under a certain delivery channel, an actual weight-volumetric weight difference marker is generated; if this difference leads to an increase in the billable weight, a volumetric billing premium benchmark is generated.

[0036] The volumetric billing premium benchmark can be determined according to the volumetric weight conversion method in the delivery channel rules. Specifically, the system first reads the packaging volume, actual weight, and volumetric weight conversion factor or conversion rule corresponding to the delivery channel for the candidate package cluster, and then converts the packaging volume into volumetric weight. When the delivery channel uses the higher of actual weight and volumetric weight for billing, the higher one is used as the billing weight. If the volumetric weight is higher than the actual weight, the difference between the volumetric weight and the actual weight, the increase in billing weight caused by the difference, and the corresponding channel billing method are all written into the volumetric billing premium benchmark. This volumetric billing premium benchmark is not directly used as the shipment conclusion, but serves as the volumetric billing premium status of the channel billing side and the basis for volumetric billing evaluation in subsequent route evaluation.

[0037] For cases where additional packages are generated due to conversion from full-package to partial-package or combination of partial-package, a conversion loss flag is generated. If a candidate package cluster does not meet the size, weight, or regional restrictions of a certain delivery channel, a delivery channel adaptation flag is generated. The conversion loss flag and the delivery channel adaptation flag are written into the status field corresponding to the candidate package cluster, and serve as the status source for the package cluster node and the channel billing edge in the warehousing and distribution constraint diagram.

[0038] The aforementioned candidate package clusters, billing caliber binding relationships, actual weight-volume weight difference markers, volumetric billing premium benchmarks, whole-to-part conversion loss markers, and delivery channel adaptation markers collectively form an order package cluster billing snapshot. This order package cluster billing snapshot is sent to the warehousing and distribution path generation module, which generates package cluster nodes in the warehousing and distribution constraint graph and provides the channel billing edge with billing caliber adaptation status and volumetric billing premium status.

[0039] The process of generating order package cluster billing snapshots uses candidate package clusters as the smallest billing analysis object. For each candidate package cluster, the system first determines its corresponding actual weight, packaging volume, number of packages, and compatible delivery channels, and then reads the billing caliber of the corresponding delivery channel. When the delivery channel uses the higher of actual weight and volumetric weight for billing, the system compares the actual weight of the candidate package cluster with the volumetric weight calculated according to the channel rules, and uses the side affecting the billing weight as the billing basis for the candidate package cluster. If the volumetric weight is higher than the actual weight and causes the billing weight to increase, a volumetric billing premium benchmark is generated; if the conversion from whole package to split package or the recombination of multiple split packages leads to an increase in the number of packages, a whole-to-split conversion loss flag is generated; if the candidate package cluster exceeds the size, weight, or regional restrictions of the delivery channel, a delivery channel adaptation flag is generated. These flags are not used as the final shipping conclusion, but rather as the source of the state of package cluster nodes and channel billing edges in the warehousing and distribution constraint diagram, used for subsequent path generation, path filtering, and split order verification.

[0040] After receiving the order package cluster billing snapshot, the warehousing and distribution route generation module simultaneously reads the shipping resource status data and delivery channel rule data. The shipping resource status data may include the warehouse or shipping point's inventory availability status, packaging capacity, current shipping load, node occupancy status, and whether full-case or split-case processing is supported. The delivery channel rule data may include the delivery area, billing caliber, delivery restrictions, channel status, and restrictions related to volumetric billing premiums.

[0041] Reference Figure 4The warehousing and distribution path generation module first generates a warehousing and distribution constraint graph. This constraint graph includes parcel cluster nodes, shipping resource nodes, delivery channel nodes, shipping adaptation edges, channel billing edges, and locking conflict edges. Parcel cluster nodes are generated from candidate parcel clusters in the order parcel cluster billing snapshot. Shipping adaptation edges connect parcel cluster nodes and shipping resource nodes, used to record resource fulfillment status, packaging processing status, and shipping load status. Channel billing edges connect shipping resource nodes and delivery channel nodes, used to record billing caliber adaptation status, delivery restriction status, and volume billing premium status. Locking conflict edges are used to record the occupancy conflict status between order flow objects, shipping resource nodes, delivery channel nodes, and order flow state chains.

[0042] In the warehousing and distribution constraint graph, the shipping adaptation edge, channel billing edge, and locking conflict edge are all configured with edge states. The shipping adaptation edge records at least the inventory satisfaction state, packaging processing state, shipping load state, and node occupancy state between the parcel cluster and the shipping resource; the channel billing edge records at least the billing caliber adaptation state of the delivery channel to the parcel cluster, the delivery restriction state, and the volume billing premium state; the locking conflict edge records the occupancy conflict state between the order flow object, shipping resource, delivery channel, and order flow state chain. The above edge states include available state, cost state, risk state, and locked state, which can be divided into available, restricted, and unavailable according to a preset state table, or into low, medium, and high levels; among them, the unavailable state indicates that the corresponding edge does not meet the minimum execution conditions, the restricted state indicates that the corresponding edge meets the minimum execution conditions but there are cost or risk impacts, and the available state indicates that the corresponding edge meets the current path generation conditions.

[0043] The path filtering unit filters single-resource warehousing and distribution paths, combined-resource warehousing and distribution paths, and reserved warehousing and distribution paths based on the edge status of the shipping adaptation edge, channel billing edge, and locking conflict edge. Paths containing unavailable shipping adaptation edges, unavailable channel billing edges, or irresolvable locking conflict edges are eliminated; paths containing restricted edges but still meeting the minimum execution conditions are retained, and their cost status and risk status are written into the path evaluation results; when the risk status of a path reaches the preset risk limit, the path will not enter the subsequent decision-making process. The preset status table and risk limit can be determined by historical execution data, distribution channel rules, warehouse processing rules, or manually configured path constraint tables.

[0044] Reference Figure 5The single-resource path generation unit searches the warehousing and distribution constraint graph for the package cluster nodes, shipping adaptation edges, channel billing edges, and delivery channel nodes connected to the same shipping resource node to form a single-resource warehousing and distribution path. A single-resource warehousing and distribution path represents a path where one shipping resource completes the shipping of the corresponding package cluster for an order. The combined resource path generation unit is activated when a single-resource warehousing and distribution path cannot meet the order shipping requirements, or when the cost of a single-resource warehousing and distribution path exceeds the preset path constraints. A combined resource path involves multiple shipping resource nodes jointly undertaking the shipping of the corresponding package cluster. When generating a combined resource warehousing and distribution path, the system uses package cluster nodes as allocation objects, binding different package cluster nodes to shipping resource nodes that meet the shipping adaptation edge conditions. Each package cluster node can only be bound to one shipping resource node in the same combined resource warehousing and distribution path; all pending package cluster nodes under the same order flow object should be covered by the combined resource warehousing and distribution path. If there are uncovered package cluster nodes, or if the same package cluster node is repeatedly assigned to multiple shipping resource nodes, the combined resource warehousing and distribution path will be marked as unavailable and will not enter the order splitting and verification gate control process. When the combined resource path is generated, the system will associate the split package clusters with paths to ensure that each package cluster still corresponds to the same order flow object.

[0045] The reserved path generation unit handles path-restricted situations. When a single-resource warehousing and distribution path is unexecutable and a combined-resource warehousing and distribution path fails subsequent order splitting verification gates, the reserved path generation unit generates a reserved warehousing and distribution path based on the package cluster nodes, shipping resource nodes, delivery channel nodes, and order flow status chain that still meet the order flow constraints. The reserved warehousing and distribution path can be a delayed shipping path, a path awaiting resource release, or a low-risk path that maintains the order flow status without interruption. When a reserved warehousing and distribution path enters the warehousing and distribution lock decision, it is only used to record the continuing processing direction and subsequent review conditions for the current order flow object, and does not automatically generate an actual shipping execution task. Only after shipping resources are released, delivery channels become available again, order deadlines are approaching, or manual review is passed, does the warehousing and distribution path generation module regenerate a single-resource or combined-resource warehousing and distribution path that meets the execution conditions. Only then does the warehousing and distribution lock execution module create a shipping lock event and a shipping execution task based on the regenerated path. This path is not used as simple backup information, but rather enters the warehousing and distribution lock decision when order splitting is restricted, to prevent orders from having no executable flow results due to order splitting failure.

[0046] After a reserved warehousing and distribution route is generated, the system writes it into the reserved route node in the order flow status chain, and records the reason for retention, the restricted combined resource warehousing and distribution route, the triggered gating constraints, and the conditions for the next route review. The conditions for the next route review can be the release of shipping resources, the restoration of availability of delivery channels, the approaching order deadline, or the passing of manual review. If the review conditions are met, the warehousing and distribution route generation module rereads the current shipping resource status data and delivery channel rule data, and regenerates the single-resource warehousing and distribution route, the combined resource warehousing and distribution route, and the reserved warehousing and distribution route; if the review conditions are not met, the reserved warehousing and distribution route continues to maintain the continueable flow status in the order flow status chain, and no actual shipping execution task is generated.

[0047] Reference Figure 6 The order splitting and verification gating module is used to determine whether a combined resource warehousing and distribution path is necessary to enter the decision-making process. This module establishes a comparable warehousing and distribution path within the same domain, based on either a single resource warehousing and distribution path or a retained warehousing and distribution path. The comparable warehousing and distribution path within the same domain corresponds to the same order flow object, the same delivery area, and the same or similar order flow status, ensuring comparability in the comparison relationship.

[0048] The order splitting and verification package generation unit compares the combined resource warehousing and distribution path with the corresponding warehousing and distribution path in the same domain to generate an order splitting and verification package. The order splitting and verification package includes splitting benefit items and splitting loss items. Splitting benefit items include at least the improvement in resource fulfillment resulting from the combined resource warehousing and distribution path compared to the corresponding warehousing and distribution path in the same domain, such as improved inventory fulfillment, improved availability of shipping resources, or improved order flowability. Splitting loss items include at least the increase in packaging quantity, the increase in volumetric billing premium, the increase in fulfillment dispersion, and the increase in abnormal risk. The increase in packaging quantity reflects the increase in the number of packages after splitting; the increase in volumetric billing premium reflects the degree to which splitting leads to an increase in volumetric weight billing; the increase in fulfillment dispersion reflects the degree to which multi-path shipping causes dispersion in signing time or fulfillment nodes; and the increase in abnormal risk reflects the increase in the risk of misdelivery, omission, rejection, or abnormal returns after splitting.

[0049] When determining whether the benefits of order splitting cover the losses, the system first converts the resource fulfillment improvement result, packaging quantity increment, volumetric billing premium increment, fulfillment dispersion increment, and abnormal risk increment into a gating level under the same evaluation caliber. The resource fulfillment improvement result indicates whether the combined resource warehousing and distribution path changes the order from an unexecutable state to an executable state, or whether the fulfillment level of shipping resources meets the preset shipping conditions. The packaging quantity increment, volumetric billing premium increment, fulfillment dispersion increment, and abnormal risk increment serve as the sources of loss levels. If the resource fulfillment improvement result does not meet the preset shipping conditions, it is directly determined that the order splitting benefits do not cover the order splitting losses. If the resource fulfillment improvement result meets the preset shipping conditions, it continues to compare whether each loss level exceeds its corresponding upper limit. Only when the resource fulfillment improvement meets the shipping conditions, and the packaging quantity increment, volumetric billing premium increment, fulfillment dispersion increment, and abnormal risk increment all do not exceed their corresponding upper limits, is it determined that the order splitting benefits cover the order splitting losses. The above gating levels and upper limits can be determined by historical order execution results, distribution channel rules, or preset strategy tables.

[0050] In the order splitting counter-evidence gating system, the splitting benefit and loss items are processed using the same criteria before entering the judgment stage. Resource fulfillment improvement results are represented by the improvement in inventory fulfillment, shipping resource availability, and order flowability of the combined resource warehousing and distribution route compared to the same domain's control route. Packaging quantity increment is represented by the increase in the number of packages in the combined resource warehousing and distribution route compared to the same domain's control route. Volumetric billing premium increment is represented by the increase in the sum of volumetric billing premiums for each package cluster after order splitting relative to the control route. Fulfillment dispersion increment is represented by the difference in estimated arrival time, outbound node, or signed batch caused by different shipping resources or different delivery channels. Abnormal risk increment is represented by the increase in the risk of delivery anomalies, misdeliveries, omissions, or rejections in the route after order splitting. The thresholds for the above increments can be determined according to historical execution data, delivery channel rules, or preset strategy tables. When any of the volumetric billing premium increment, fulfillment dispersion increment, or abnormal risk increment reaches its corresponding upper limit, the gating lock on that combined resource warehousing and distribution route will not be released, even if the resource fulfillment improvement result is high. Only when the resources available can cover the overall losses caused by order splitting, and the aforementioned constraints are not triggered, will the combined resource warehousing and distribution path enter the subsequent warehousing and distribution lock execution process.

[0051] The thresholds for the aforementioned constraints can be determined based on historical execution data of similar orders, delivery channel rules, or preset strategy tables. If the order splitting benefit item covers the order splitting loss item, and none of the increments trigger the corresponding constraints, the order splitting counter-verification gating module releases the gating lock on the corresponding combined resource warehousing and distribution path, and this path enters the warehousing and distribution locking execution module. If the order splitting benefit item does not cover the order splitting loss item, or any increment triggers the corresponding constraint, the combined resource warehousing and distribution path is marked as a restricted path, and the corresponding reserved warehousing and distribution path is output. Through this mechanism, the system will not directly adopt multi-warehouse order splitting simply because of insufficient single-warehouse inventory or high load, but will first determine whether the cost of order splitting in terms of volume billing, fulfillment dispersion, and abnormal risks is acceptable.

[0052] Reference Figure 7 The warehousing and distribution locking execution module receives the combined resource warehousing and distribution paths, single resource warehousing and distribution paths, and reserved warehousing and distribution paths that have been unlocked by the gate lock, and then evaluates the paths entering the decision-making process. The path evaluation unit generates path evaluation results based on the order package cluster billing snapshot and the warehousing and distribution constraint graph. The path evaluation results include volume billing evaluation results, shipping resource occupancy evaluation results, delivery channel adaptation evaluation results, order flow timeliness evaluation results, and abnormal risk evaluation results. During the evaluation, the volume billing evaluation results are derived from the volume billing premium benchmark and the channel billing edge status; the shipping resource occupancy evaluation results are derived from the shipping adaptation edge and the locking conflict edge; the delivery channel adaptation evaluation results are derived from the delivery channel rules and the channel billing edge; the order flow timeliness evaluation results are derived from the order flow state chain and the delivery timeliness requirements; and the abnormal risk evaluation results are derived from the path risk status and historical similar execution records.

[0053] The conflict resolution unit resolves conflicts in warehousing and distribution paths based on the locking status of the locked conflict edges, addressing conflicts related to resource occupancy, channel occupancy, or order flow status. If a conflicting path can be resolved by releasing unexecuted locks, adjusting reserved paths, or switching delivery channels, the locking status of that path is updated. If the conflict cannot be resolved, the path is not added to the set of lockable warehousing and distribution paths. The target warehousing and distribution path is determined from the set of lockable paths, and a target warehousing and distribution delivery plan is generated.

[0054] When determining target warehousing and distribution routes, the system first excludes routes with irresolvable locking conflicts, unavailable delivery channels, or order statuses that do not allow shipment. For the remaining lockable routes, the system ranks them based on volumetric pricing evaluation results, delivery resource utilization evaluation results, delivery channel suitability evaluation results, order processing timeliness evaluation results, and abnormal risk evaluation results. For volume-sensitive orders such as tissue paper, volumetric pricing evaluation results and delivery channel suitability evaluation results are prioritized in the ranking. When the volumetric pricing evaluation results of two routes are at the same level, the delivery resource utilization evaluation results and order processing timeliness evaluation results are compared. If the volumetric pricing evaluation result of one route is better than that of another route, but its order processing timeliness evaluation result is lower than the preset timeliness requirement, that route is not considered a priority route. If the delivery channel suitability evaluation result of a route is in a restricted state but not unavailable, the system writes this restricted state into the abnormal risk evaluation result and includes it in the ranking. When the abnormal risk evaluation result reaches the preset risk limit, regardless of whether the volumetric pricing evaluation result is better, that route is not considered a target warehousing and distribution route. The above sorting rules can be configured in the path evaluation strategy table and updated with the warehousing and distribution constraint graph parameters. When the abnormal risk assessment result of any path reaches the preset risk limit, that path will not be used as the target warehousing and distribution path. The finally selected target warehousing and distribution path is written into the target warehousing and distribution delivery plan and serves as the basis for generating the delivery lock event.

[0055] A target warehousing and distribution plan should include at least the target package cluster, target shipping resources, target delivery channels, target warehousing and distribution routes, and target order flow nodes.

[0056] Reference Figure 8 The lock event generation unit generates a shipping lock event based on the target warehousing and distribution plan. The shipping lock event is written to the order flow object, target package cluster, target shipping resource, target delivery channel, and order flow state chain. After the shipping lock event is generated, the state consistency verification unit triggers verification under the following circumstances: the order flow state chain changes, the billing snapshot corresponding to the target package cluster changes, the status of the target shipping resource changes, the status of the target delivery channel changes, or the lock conflict edge in the warehousing and distribution constraint diagram changes. The verification content includes the consistency of the package cluster, resource occupancy, channel availability, and order flow state between the shipping lock event and the warehousing and distribution constraint diagram.

[0057] When a shipment lock event is generated, the system records the order flow object version, the order package cluster billing snapshot version, the target shipment resource status version, the target delivery channel rule version, and the current node in the order flow status chain. During status consistency verification, the system compares the current version information with the version information in the shipment lock event. If the target package cluster billing snapshot is regenerated, the target shipment resource occupancy status changes, the target delivery channel becomes unavailable, or the order flow status chain has entered a node where shipment is not allowed, the consistency verification is deemed to have failed, and the warehousing and distribution path generation module is triggered to regenerate the warehousing and distribution path. If only non-critical fields that do not affect package cluster billing, shipment resource availability, and delivery channel availability change, the original shipment lock event is retained, and the shipment execution task continues. This versioned locking method is used to prevent a determined shipment plan from being executed after substantial changes in the order, resource, or channel status.

[0058] Non-critical field changes include data updates that do not alter the number of candidate package clusters, the billing caliber binding relationship, the availability status of target shipping resources, the reachability status of target delivery channels, or the shipping permission status in the order flow status chain. If a field change causes a regeneration of the package cluster billing snapshot, a change in target shipping resources from available to restricted or unavailable, a change in the billing caliber of the target delivery channel, or an entry into a paused or canceled shipping node in the order flow status chain, then the change is considered a critical change, and the status consistency review will fail. By distinguishing between critical and non-critical changes, shipping lock events can avoid frequent failures due to irrelevant information updates, and can promptly revert to the warehousing and distribution path generation process when status changes affecting shipping execution conditions occur.

[0059] When the consistency review passes, the task generation unit generates a shipping execution task. The shipping execution task can include execution nodes such as picking, review, packaging, outbound, and delivery, and corresponds to the order flow state chain. After each execution node is completed, the task generation unit or its connected state write-back unit writes the node completion status, completion time, execution resources, and exception flag into the order flow state chain. If any node in picking, review, packaging, outbound, or delivery encounters an exception, the system writes the corresponding exception into the order flow state chain and associates the exception information with the shipping lock event. For exceptions affecting the availability of the target package cluster, target shipping resources, or target delivery channel, the state consistency review unit re-executes the consistency review, and if necessary, triggers the warehousing and distribution path generation module to regenerate the warehousing and distribution path. If the consistency review fails, the warehousing and distribution lock execution module triggers the warehousing and distribution path generation module to regenerate the warehousing and distribution path, and the original shipping lock event is marked as invalid or pending review. This process is used to resolve the problem of inconsistencies between the shipping plan and actual execution conditions caused by changes in order status, warehousing resources, and delivery channels.

[0060] After the shipment task is completed, the performance deviation correction module collects the shipment performance data. This data may include the actual number of packages, actual chargeable weight, actual transportation costs, actual delivery channels, actual shipping resources, actual fulfillment time, abnormal return status, and actual lock conflict handling results. During deviation comparison, the system compares the shipment performance data with the target package cluster, volumetric billing premium benchmark, route evaluation results, shipment lock events, and order splitting verification results in the target warehousing and distribution plan to generate the performance deviation result.

[0061] Reference Figure 9 The attribution ledger generation unit generates an attribution ledger based on the performance deviation results. Differences between actual chargeable weight, actual volumetric chargeable premium, and order package cluster chargeable snapshots are written into the volumetric chargeable deviation item; differences between actual package quantity, actual packing combination, and candidate package clusters are written into the packing combination deviation item; differences between actual shipping resource capacity, outbound node, resource occupancy status, and shipping adaptation edge are written into the shipping resource deviation item; differences between actual delivery costs, delivery restrictions, fulfillment timeliness, and channel chargeable edge are written into the delivery channel deviation item; discrepancies between shipping lock events and actual resource or channel occupancy are written into the lock conflict deviation item; deviations in actual costs after a reserved warehousing and distribution path is adopted are written into the reserved path deviation item; and differences between the actual order splitting revenue or loss of a combined resource warehousing and distribution path and the order splitting counter-certification package are written into the order splitting gating deviation item. Each deviation item is associated with the order flow object, target warehousing and distribution path, and shipping lock event for subsequent targeted correction calls.

[0062] The stability correction unit is used to determine whether the performance deviation attribution ledger meets the stability correction threshold. The stability correction threshold includes at least one of the following: persistence of similar deviations, deviation magnitude, and recurrence of similar orders. The persistence of similar deviations can be determined by consecutive deviation records occurring under the same product category, the same or similar delivery area, the same delivery channel, or the same shipping resources. The deviation magnitude can be determined by deviations in actual billing weight, actual transportation costs, actual fulfillment timeliness, or actual package quantity reaching a preset magnitude. The recurrence of similar orders can be determined by the number of repeated deviations under the same package cluster billing snapshot type or the same warehousing and distribution route type. If the performance deviation attribution ledger does not meet the stability correction threshold, or is currently in a correction freeze window, the system only saves the deviation records and maintains the existing parameters; only when the stability correction threshold is met and the system is not in a correction freeze window will the targeted correction process begin.

[0063] During targeted corrections, if the volumetric billing deviation item shows that the actual billable weight is consistently higher than the billable weight in the order parcel cluster billing snapshot, then the volumetric billing premium benchmark for the corresponding shipping unit node or volumetric billing edge is increased; if the packaging combination deviation item shows that the actual number of parcels is consistently higher than the number of candidate parcel clusters, then the packing loss status of the corresponding packing constraint edge is adjusted or the priority of that packaging combination entering the candidate parcel cluster is reduced; if the shipping resource deviation item shows that the actual processing capacity of a certain shipping resource is lower than the processing capacity recorded by the shipping adaptation edge, then the shipping load status or resource satisfaction status of that shipping resource node is adjusted; if the delivery channel deviation item shows that a certain delivery channel... If the actual cost or actual delivery time consistently deviates from the channel billing edge status, the cost status or risk status of that channel billing edge will be adjusted. If lock conflict deviations persist, the conflict level of the corresponding lock conflict edge will be increased. If the reserved path deviation shows that the actual cost of adopting the reserved warehousing and distribution path consistently exceeds the expected cost, or if the reserved path fails to be converted into an executable path for an extended period, the priority of the reserved path entering the decision-making process, the conditions for the next path review, or the cost status of the reserved path will be adjusted. For reserved warehousing and distribution paths that still cannot be converted into executable paths after multiple reviews, the system will reduce the priority of similar reserved paths in subsequent orders. If the order splitting gating deviation shows that the actual loss of the combined resource path is higher than the order splitting loss item in the order splitting counter-evidence package, the gating level of the corresponding order splitting loss item will be increased or the coverage level of the corresponding order splitting revenue item will be decreased. The corrected parameters only apply to the same type of goods, the same type of package cluster, the same type of delivery channel, or the same type of warehousing and distribution path corresponding to the deviation item.

[0064] After the above corrections are completed, the corrected parameters are fed back to the volume billing snapshot generation module, the warehousing and distribution route generation module, and the order splitting and reversal gate control module, respectively. These are used for subsequent paper towel sales order order package cluster billing snapshot generation, warehousing and distribution constraint diagram generation, warehousing and distribution route filtering, and order splitting and reversal gate control judgment. If the performance deviation attribution ledger does not meet the correction stability threshold, or is currently in the correction freeze window, the system only saves the corresponding deviation record and does not change the current matching parameters.

[0065] After targeted correction is completed, the system writes the correction source, correction time, applicable order scope, and correction anti-shake flag to the corrected parameter. The correction source corresponds to the deviation item in the performance deviation attribution ledger; the applicable order scope limits the correction to similar products, similar package clusters, similar delivery channels, or similar warehousing and distribution routes, preventing it from being extended to unrelated orders; the correction anti-shake flag restricts the repeated adjustment of the same parameter within a preset observation period. New deviation records generated during the observation period are first entered into the attribution ledger and do not immediately trigger another correction; if similar deviations continue to occur after the observation period ends, they are re-evaluated according to the correction stability threshold. Through this process, the system can feed back actual shipping deviations to subsequent order processing while maintaining the traceability and stability of parameter updates.

[0066] In the aforementioned main implementation path, the order package cluster billing snapshot addresses the lack of a volume billing intermediate layer for tissue orders before shipment; the warehousing and distribution constraint graph addresses the lack of a unified constraint expression between package clusters, shipping resources, and delivery channels; the order splitting and verification gating addresses the lack of profit and loss comparison and judgment before multi-warehouse order splitting; the shipment locking event and status consistency review address the problem of order status not being synchronized with warehousing and distribution execution conditions; and the performance deviation attribution ledger and stability correction mechanism address the problem of shipment results being difficult to feed back to subsequent matching rules.

[0067] Building upon the main implementation, a manual review entry point can also be set up. When the combined resource warehousing and distribution path is marked as a restricted path, but the order has high timeliness requirements or the customer specifies partial shipments, the system can submit the corresponding split order verification package, retained warehousing and distribution path, and constraint trigger items for manual review. The manual review result is recorded as a review node in the order flow status chain and can be used as reference data for subsequent stability assessments. This supplementary method does not change the main implementation path; it simply provides traceable intervention records under special business conditions.

[0068] If it is necessary to verify the delivery matching effect of this embodiment, historical tissue orders can be selected as the control order set, and similar orders processed using this embodiment can be used as the verification order set. The control order set and the verification order set should be comparable in terms of order product type, receiving area, delivery channel range, and delivery resource range. During verification, the number of candidate package clusters, actual number of packages, estimated chargeable weight, actual chargeable weight, target warehousing and distribution route, actual transportation cost, fulfillment time, and abnormal results for each order can be recorded. The deviations caused by mismatch in volumetric billing caliber, increased number of packages after order splitting, and failure to review lock conflicts in the two sets of orders should be compared. If the specification or subsequent response needs to claim a specific proportional effect, it should be supported by such comparative records. When quantitative verification data is not provided, the effect of this embodiment should be described as reducing matching deviations caused by the failure to identify volumetric billing factors, reducing the risk of unreasonable order splitting, and improving the traceability of the warehousing and distribution lock process, rather than being directly limited to a fixed percentage reduction in cost or a decrease in the abnormality rate.

[0069] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A paper towel sales order flow and delivery matching management system, characterized in that, include: The order flow object generation module is used to generate order flow objects based on tissue sales order data and establish an order flow status chain corresponding to the order flow object; The volumetric billing snapshot generation module is connected to the order flow object generation module. It is used to call the volume-sensitive tissue delivery unit model, convert the order flow object into a candidate package cluster, bind the delivery billing caliber to the candidate package cluster, and generate an order package cluster billing snapshot. The order package cluster billing snapshot includes at least the candidate package cluster, the billing caliber binding relationship, the actual weight-volume weight difference marker, and the volumetric billing premium benchmark. The warehousing and distribution route generation module is connected to the volume billing snapshot generation module. It is used to generate a warehousing and distribution constraint diagram based on the order package cluster billing snapshot, shipping resource status data and delivery channel rule data. The warehousing and distribution constraint diagram is used to generate single-resource warehousing and distribution routes, combined resource warehousing and distribution routes and reserved warehousing and distribution routes. The order splitting and reversal gate module, connected to the warehousing and distribution path generation module, is used to establish a corresponding warehousing and distribution path within the same domain based on a single resource warehousing and distribution path or a reserved warehousing and distribution path. It then compares the combined resource warehousing and distribution path with the corresponding warehousing and distribution path within the same domain to generate an order splitting and reversal package. When the order splitting revenue item in the order splitting and reversal package covers the order splitting loss item, and the volume billing premium constraint, performance dispersion constraint, and abnormal risk constraint are not triggered, the gate lock of the corresponding combined resource warehousing and distribution path is released. Otherwise, the corresponding combined resource warehousing and distribution path is marked as a restricted path, and the corresponding reserved warehousing and distribution path is output. The warehouse and distribution locking execution module, connected to the order splitting and counter-verification gate control module, is used to determine the target warehouse and distribution delivery plan among the combined resource warehouse and distribution path, single resource warehouse and distribution path and the reserved warehouse and distribution path after the gate control lock is released, and to generate a delivery lock event; The shipment lock event is used to lock the order flow object, target package cluster, target shipment resource, target delivery channel and order flow status chain, and generates a shipment execution task after the lock consistency verification is passed; The performance deviation correction module is connected to the warehousing and distribution lock execution module, the volume billing snapshot generation module, the warehousing and distribution route generation module, and the order splitting and reversal gate control module. It is used to compare the actual delivery data with the target warehousing and distribution delivery plan, generate the performance deviation attribution ledger, and correct the order package cluster billing snapshot generation parameters, warehousing and distribution constraint diagram parameters, and order splitting and reversal gate control parameters when the performance deviation attribution ledger meets the correction stability threshold and is not in the correction freeze window. The order flow object generation module is also used to update the order flow status chain based on the order package cluster billing snapshot, warehousing and distribution path generation results, order splitting and verification results, shipment lock events, and performance deviation attribution ledger.

2. The tissue paper sales order flow and delivery matching management system according to claim 1, characterized in that: The volume-sensitive tissue delivery unit model is generated by the volume-sensitive tissue delivery unit map construction module; The volume-sensitive tissue delivery unit graph construction module is used to generate delivery unit nodes, packaging conversion edges, volume billing edges, and packing constraint edges. The shipping unit node corresponds to the shipping status of paper towels in whole packages, in single packages, or in a mixed manner. The packaging conversion edge is used to connect the complete and disassembled packaging between different shipping methods; The volumetric billing edge is used to associate the actual weight-volume weight difference and the volumetric billing premium under different shipping methods; Packing constraint edges are used to associate the packing fit relationship when different shipping units are combined to form a package.

3. The tissue paper sales order flow and delivery matching management system according to claim 2, characterized in that: The volume billing snapshot generation module includes an order mapping unit, a package cluster generation unit, a billing caliber binding unit, and a snapshot generation unit; The order mapping unit is used to map order flow objects to volume-sensitive tissue paper delivery unit models; The package cluster generation unit is used to generate candidate package clusters based on the mapping results, and to determine the packaging combination relationship and package quantity relationship corresponding to the candidate package clusters; The billing caliber binding unit is used to bind candidate package clusters with the billing caliber in the delivery channel rules to obtain the billing caliber binding relationship; The snapshot generation unit is used to generate actual weight-volume weight difference markers, volumetric billing premium benchmarks, whole-to-part conversion loss markers, and delivery channel adaptation markers based on the candidate package clusters and the binding relationship of billing standards, and to form order package cluster billing snapshots.

4. The tissue paper sales order flow and delivery matching management system according to claim 3, characterized in that: The warehousing and distribution constraint graph includes parcel cluster nodes, shipping resource nodes, delivery channel nodes, shipping adaptation edges, channel billing edges, and locking conflict edges; Parcel cluster nodes are generated from candidate parcel clusters in the order parcel cluster billing snapshot; The shipping adapter connects the package cluster node and the shipping resource node, and configures the resource satisfaction status, packaging processing status and shipping load status. The channel billing edge connects the shipping resource node and the delivery channel node, and configures the billing caliber adaptation status, delivery restriction status, and volume billing premium status; Locked conflict edges are used to represent the occupancy conflict state between order flow objects, shipping resource nodes, delivery channel nodes, and order flow state chains.

5. The tissue paper sales order flow and delivery matching management system according to claim 4, characterized in that: The warehousing and distribution route generation module includes a single resource route generation unit, a combined resource route generation unit, a reserved route generation unit, and a route filtering unit. The single-resource path generation unit is used to generate a single-resource warehousing and distribution path based on the package cluster node, shipping adaptation edge, channel billing edge and delivery channel node connected to the same shipping resource node. The combined resource path generation unit is used to generate a combined resource warehousing and distribution path based on multiple shipping resource nodes when a single resource warehousing and distribution path does not meet the order delivery requirements or the cost status of a single resource warehousing and distribution path exceeds the preset path constraints. The reserved path generation unit is used to generate a reserved warehousing and distribution path when a single resource warehousing and distribution path is not executable and a combined resource warehousing and distribution path fails the split order and reverse verification gate control. The path filtering unit is used to filter single-resource warehousing and distribution paths, combined-resource warehousing and distribution paths, and reserved warehousing and distribution paths based on the availability status, cost status, risk status, and locking status of the shipping adaptation edge, channel billing edge, and locking conflict edge.

6. The tissue paper sales order flow and delivery matching management system according to claim 5, characterized in that: The split order reverse asset package includes split order gains and split order losses; The benefits of splitting orders should at least include the improved resource fulfillment of the combined resource warehousing and distribution route compared to the comparable warehousing and distribution route in the same domain; The loss items for splitting orders include at least the increase in packaging quantity, the increase in volumetric billing premium, the increase in fulfillment dispersion, and the increase in abnormal risk. When the revenue from splitting orders covers the losses from splitting orders, and the incremental volume billing premium, incremental performance dispersion, and incremental abnormal risk do not trigger the corresponding constraints, the splitting order counter-evidence gating module releases the gating lock on the corresponding combined resource warehousing and distribution path. When the profit item from splitting orders does not cover the loss item from splitting orders, or when any increment triggers the corresponding constraint, the splitting order counter-verification gating module will mark the corresponding combined resource warehousing and distribution path as a restricted path.

7. The tissue paper sales order flow and delivery matching management system according to claim 6, characterized in that: The warehouse and distribution locking execution module includes a path evaluation unit, a conflict resolution unit, a locking event generation unit, and a task generation unit. The route evaluation unit is used to generate route evaluation results for the warehousing and distribution routes that enter the decision-making process. The route evaluation results include volume billing evaluation results, shipping resource utilization evaluation results, delivery channel adaptation evaluation results, order flow timeliness evaluation results, and abnormal risk evaluation results. The conflict resolution unit is used to resolve conflicts in warehousing and distribution paths that have resource occupation conflicts, channel occupation conflicts, or order flow status conflicts based on the locking status of the locked conflict edges, so as to obtain lockable warehousing and distribution paths; The lock event generation unit is used to determine the target warehousing and distribution route in the lockable warehousing and distribution route and generate a shipment lock event; The task generation unit is used to generate a shipment execution task after the shipment lock event passes the lock consistency verification.

8. The tissue paper sales order flow and delivery matching management system according to claim 7, characterized in that: The warehouse and distribution lock execution module also includes a state consistency verification unit; The state consistency verification unit is used to verify the consistency between the shipment lock event and the warehouse and distribution constraint diagram when the state of the order flow state chain, target package cluster, target shipping resource or target delivery channel changes; Once the consistency review is passed, the shipment execution task can be generated or continued. If the consistency review fails, the warehouse and distribution path generation module is triggered to regenerate the warehouse and distribution path.

9. The tissue paper sales order flow and delivery matching management system according to claim 8, characterized in that: The performance deviation attribution ledger includes volume billing deviation items, packaging combination deviation items, shipping resource deviation items, distribution channel deviation items, lock-in conflict deviation items, reserved route deviation items, and order splitting gate control deviation items; The performance deviation correction module is used to correct the parameters generated by the volume-sensitive tissue delivery unit model and the order package cluster billing snapshot based on the volume billing deviation item and the packaging combination deviation item; Correct the warehouse and distribution constraint diagram parameters based on the shipping resource deviation item, delivery channel deviation item, locked conflict deviation item, and reserved route deviation item; Correct the order splitting gate control parameters based on the order splitting gate control deviation item; The modified stability threshold includes at least one of the following: the condition of persistence of similar deviations, the condition of deviation magnitude, and the condition of recurrence of similar orders.

Images