A warehouse logistics in-and-out warehouse linkage express service fee dynamic allocation and accounting method

Abstract

The application provides a warehouse logistics warehouse-in and warehouse-out linkage express service fee dynamic allocation and accounting method, which comprises the following steps: extracting warehouse-in, shelving, packaging, handover and collection operation records from the warehouse, order and express system, constructing an order event chain, and extracting an abnormal identifier. Then, based on the relative position of the key nodes in the order event chain, the linkage operation difference value is calculated, and the collaborative operation unit that actually shares the packaging, handover and collection resources is identified. Next, the basic allocation weight is generated according to the order in the unit, the basic fee pool corresponding to the unit is allocated to each order, and the basic fee is formed. Finally, the basic fee is corrected in combination with the abnormal identifier and the order in the unit, and a record containing the final accounting fee is generated. The application solves the problems of unclear shared fee boundary and unclear abnormal fee attribution in the prior art, and realizes accurate dynamic accounting of express service fees.

Description

Technical Field

[0001] This invention belongs to the field of warehouse management, and in particular relates to a method for dynamic allocation and accounting of express delivery service fees linked to warehouse logistics inbound and outbound operations. Background Technology

[0002] With the development of integrated e-commerce warehousing and distribution, cloud warehousing collaboration, and multi-channel fulfillment models, warehousing and logistics companies typically use warehouse management systems, order management systems, and express delivery interface systems to record operational statuses such as inbound completion, shelving completion, packaging completion, outbound handover, express pickup, as well as order splitting, reshipment, re-delivery, delayed release, and repackaging. These records provide basic data support for the order fulfillment process. In existing technologies, a relatively similar approach is usually to calculate costs based on existing outbound waves, express handover batches, or express billing results in the warehouse system, and to allocate express service fees according to order weight, volume, number of pieces, value, fixed rate templates, or customer-agreed rules. This method can meet general reconciliation needs and is easy to integrate with financial systems, but its accounting basis is mostly concentrated on static order attributes or express billing results, and it does not adequately express the differences in the actual operational organization of each order during the inbound and outbound linkage process. In actual engineering projects, orders from the same warehouse, the same customer, or within the same fulfillment cycle may enter different packaging and handover processes due to differences in warehousing completion time, shelving progress, packing completion time, outbound handover batches, and courier pickup time. Furthermore, abnormal situations such as order splitting, reshipment, re-delivery, delayed release, and repackaging may cause deviations in subsequent packing, handover, or pickup nodes, leading to additional courier service fees or internal service costs. Existing methods of allocating costs based on static rules or post-billing allocation can easily mix orders that actually share packing, handover, and pickup resources with orders that do not participate in the same process into the same allocation scope. It can also easily include the additional operational impact caused by abnormal orders into normal orders, resulting in a disconnect between the cost per order and the actual operational process. Meanwhile, while existing systems record warehouse operations, order status, and express delivery pickup information, this information often remains at the level of business flow records. It hasn't been further organized into an order event chain for cost accounting, nor has it been transformed into a continuous calculation relationship between collaborative work units, the basic cost pool, and the final cost record. This makes it difficult to trace the process of express delivery service fee formation, results in a large workload for manual verification, and lacks clear operational guidelines for handling cost disputes. Therefore, existing technology still needs an engineered method that can transform the inbound and outbound linkage operation process into a computable accounting boundary based on existing warehousing, order, and express delivery data, and further realize the dynamic allocation and final accounting of express delivery service fees. Summary of the Invention

[0003] This invention discloses a method for dynamic allocation and accounting of express delivery service fees linked to warehouse logistics inbound and outbound operations, in order to solve the above-mentioned problems in the prior art.

[0004] To achieve the above objectives, the present invention provides a method for dynamic allocation and accounting of express delivery service fees linked to warehousing and logistics inbound and outbound operations, the method comprising: Construct an order event chain, extract operation records related to cost formation from the warehouse management system, order management system and express interface system. The operation records include inbound completion, shelving completion, packaging completion, outbound handover and express pickup. Arrange the operation records into an order event chain according to the business sequence, and extract the abnormal identifier of the order. Identify collaborative work units, calculate the collaborative work difference value between orders based on the relative work positions of each key node in the order event chain, identify the set of orders that actually share packaging, handover and collection resources, and form collaborative work units; Generate a basic cost allocation result. Generate a basic allocation weight based on the degree of alignment between the order and the subsequent operations within the collaborative work unit. Allocate the basic cost pool corresponding to the collaborative work unit to each order within the unit according to the basic allocation weight to obtain the basic cost allocation result. The cost allocation is corrected and the final accounting result is output. Based on the anomaly identifier and the degree of deviation of the order in the subsequent operation within the collaborative operation unit, the basic cost allocation result is corrected to generate a cost accounting record containing the final accounting cost.

[0005] Furthermore, the construction of the order event chain specifically includes: The time of critical events within the same accounting batch is standardized by range processing, which maps the event times from different systems to a unified comparison scale to obtain the processed event time values. Using the anonymous order identifier as the primary key, the processed time values ​​of five key events for the same order are arranged into an order event chain according to a fixed business sequence.

[0006] Furthermore, the identification collaborative operation unit specifically includes: Within the candidate order pool, calculate the linkage operation difference value for any two orders. The calculation of the linkage operation difference value includes a weighted Euclidean distance term and an anomaly boundary term. The difference value of the linked operation is compared with the collaboration threshold. If the difference value is less than or equal to the collaboration threshold, the order is grouped into the same collaborative operation unit until all orders that meet the conditions in the candidate order pool are grouped.

[0007] Furthermore, the generation of the basic cost allocation result specifically includes: Based on the time position of the order after packaging completion, outbound handover, and express pickup node processing within the collaborative work unit, calculate the average absolute deviation between the order and the average time position of the members within the unit, and convert the average absolute deviation into the basic allocation weight. The basic cost pool corresponding to the collaborative work unit is allocated according to the proportion of the basic allocation weight of each order to the total weight, so as to obtain the basic cost of each order.

[0008] Furthermore, the process of correcting the cost allocation and outputting the final accounting result specifically includes: Within each collaborative work unit, the average absolute deviation between the post-processing time position of order packaging completion, outbound handover, and express pickup nodes and the average time position of members within the unit is calculated to obtain the degree of deviation in subsequent operations. If the order's anomaly flag is 1, the base cost is incrementally corrected based on the degree of deviation in the subsequent operations to generate the final accounting cost; if the anomaly flag is 0, the base cost is retained as the final accounting cost.

[0009] Furthermore, the extraction and cost formation-related operation records also include: Verify the original records. If a record lacks an anonymous order identifier, warehouse identifier, or work batch identifier, mark it as a record to be verified. If multiple records appear for the same event category, the record that is finally confirmed as completed will be selected as the time value for that event; if a key event is missing, the order will not be included in the completed collaborative identification candidate pool.

[0010] Furthermore, the anomaly identifier includes the status of order splitting, resending, re-dispatch, delayed release, repackaging, or cancellation of resending. If an order has one of the above statuses, the anomaly identifier is set to 1; otherwise, it is set to 0.

[0011] Furthermore, before generating the basic cost allocation result, the process also includes: Read the basic cost pool corresponding to the collaborative operation unit from the express delivery interface system or financial reconciliation system; If the same billing record covers multiple collaborative work units, the billing will be split into separate expense pools according to the proportion of member orders in each collaborative work unit within the billing coverage area.

[0012] Furthermore, the generation of cost accounting records containing the final calculated costs specifically includes: Generate records of associated anonymous order identifiers, their respective collaborative work units, basic costs, anomaly identifiers, work offset degrees, anomaly correction amounts, and final calculated costs; The records are written into the financial settlement system or customer billing system through the expense accounting interface.

[0013] Furthermore, in the identification collaborative operation unit, the collaborative threshold is derived from the distribution of order difference values ​​in the warehouse's historical operation records that have been confirmed to belong to the same packaging and handover process.

[0014] The beneficial technical effects of the present invention are at least as follows: To address the aforementioned issues, this invention provides a method for dynamic allocation and accounting of express delivery service fees linked to warehousing and logistics inbound and outbound operations. This method first extracts key operational events directly related to fee formation from the warehouse management system, order management system, and express delivery interface system. It organizes inbound completion, shelving completion, packaging completion, outbound handover, and express delivery pickup into a unified order event chain, retaining anomaly markers that affect fee allocation, enabling dispersed operational records to form an order-level process expression usable for accounting. Subsequently, the method identifies collaborative operational units that actually share packaging, handover, and pickup resources based on the relative operational positions of each key node in the order event chain. During the identification process, it considers the impact of abnormal states on the collaborative boundary, ensuring that the fee allocation boundary is determined by the actual operational process. Furthermore, the method establishes a basic fee pool for collaborative operational units, generating basic fee allocation results based on the order's participation level in later operational nodes such as packaging completion, outbound handover, and express delivery pickup. This ensures that express delivery service fees under normal collaborative conditions are allocated to orders according to actual collaborative operational relationships. For orders with abnormal statuses such as splitting, reshipment, re-delivery, delayed release, or repackaging, the method further adjusts the basic cost based on the degree of offset of the order from the downstream operation center within its respective collaborative work unit, and generates a final accounting record that can be written into the financial settlement system or customer billing system. Simultaneously, it retains the correspondence between the basic cost, the abnormality correction amount, and the final accounting cost. Through the above continuous processing, this invention transforms the scattered work events, express bills, and order statuses in the existing system into a traceable accounting chain oriented towards cost allocation. This ensures that the express service fee for each order reflects both its basic responsibility within the collaborative work unit and the incremental impact of abnormal operations on downstream packaging, handover, and pickup resources. This solves the problems of unclear shared cost boundaries, ambiguous attribution of abnormal costs, and difficulty in correlating billing results with warehouse events in existing technologies. Attached Figure Description

[0015] The present invention will be further described with reference to the accompanying drawings, but the embodiments in the drawings do not constitute any limitation on the present invention. For those skilled in the art, other drawings can be obtained based on the following drawings without creative effort.

[0016] Figure 1 This is a flowchart of a method for dynamically allocating and calculating express delivery service fees in conjunction with warehouse logistics inbound and outbound operations, according to the present invention. Detailed Implementation

[0017] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0018] In one or more embodiments, such as Figure 1 As shown, a method for dynamic allocation and accounting of express delivery service fees linked to warehousing and logistics inbound and outbound operations is disclosed. The method includes the following: S1: Construct an order event chain, extract operation records related to cost formation from the warehouse management system, order management system and express interface system. The operation records include inbound completion, shelving completion, packaging completion, outbound handover and express pickup. Arrange the operation records into an order event chain according to the business sequence, and extract the abnormal identifier of the order.

[0019] Specifically, the system reads operational records directly related to express delivery service fees from the enterprise's existing warehouse management system, order management system, and express delivery interface system, and forms an order event chain. and anomaly indicators In the warehouse management system, records such as "Inbound Completed," "Shelving Completed," "Packaging Completed," and "Outbound Handover" are written by barcode scanners, PDA terminals, automated sorting equipment, or manual operation stations upon completion of the operation. In the order management system, statuses such as "Order Splitting," "Reshipment," "Re-delivery," "Delayed Release," and "Repackaging" are written by the order status flow interface. In the express delivery interface system, "Pickup Completed" is returned by the carrier interface. The system reads fields including anonymous order identifier, anonymous package identifier, event type, event occurrence time, warehouse identifier, operation batch identifier, and abnormal status field. If a single original record lacks an anonymous order identifier, warehouse identifier, or operation batch identifier, the record is not included in the current accounting batch and is written to a record pending verification. The system uses the anonymous order identifier as the primary key to merge operation records of the same order from different systems into a single record group and filters five key events according to the express delivery service fee formation process: Inbound Completed Event, Shelving Completed Event, Packaging Completed Event, Outbound Handover Event, and Express Pickup Event. The "Inbound Completion" event determines when an order enters the current fulfillment cycle; the "Put-away Completion" event determines when an order is ready for outbound shipment; the "Packaging Completion" event determines when an order participates in packaging organization; the "Outbound Handover" event determines when an order enters the courier handover batch; and the "Courier Pickup" event determines when an order enters the courier cost calculation status. For example, although orders A and B belong to the same customer, order A has been packaged and handed over to the courier, while order B is still in the put-away waiting state. Subsequent collaborative identification should be based on the actual positions of the two orders in the aforementioned key events.

[0020] The raw event timestamps come from multiple business systems. These systems may have differences in recording accuracy, interface latency, or batch data transmission. Therefore, the system employs the range standardization concept, commonly used in mathematics, to process the timestamps of critical events within the same accounting batch. Range standardization is originally used to linearly map a batch of data to a uniform comparison scale. This application uses it to process job event times within the same accounting batch, allowing event times from different systems to be compared in relative order within the same batch. The specific calculation is as follows: ; in, Indicates anonymous order The The original time values ​​of key events come from the event time field in the warehouse management system, order management system, or express delivery interface system; It corresponds to only one of the five categories of key events; This represents the earliest time value among all critical events within the current accounting batch; This represents the latest time value among all critical events within the current accounting batch; This represents the processed event time value. The formula is derived from the range standardization formula. The modification in this application is that it only performs batch-level standardization on the time of key events in the chain of inbound / outbound linkage costs, enabling subsequent steps to compare the relative order of different orders within the same work cycle. Since both the numerator and denominator are of the same type of time difference, the resulting... The result is dimensionless and can be directly used to determine the proximity between subsequent orders. If within a certain accounting batch... This indicates that all key events within this batch were recorded at the same time point, and the system will record all events within this batch. Set the value to 0 and mark the batch as a single-point time batch to avoid division by zero. Taking a package handover batch formed in a warehouse between 10:00 AM and 1:30 PM as an example, the completion times for order A (inbound, shelving, packing, outbound handover, and package pickup) are recorded as 10:05, 10:20, 11:00, 11:30, and 11:50 respectively; for order B, the corresponding records are 10:08, 10:25, 11:05, 11:35, and 11:52; and for order C, the corresponding records are 10:10, 10:40, 12:30, 12:50, and 13:10. If the earliest event used for calculation in this batch is 10:05 and the latest event is 13:10, the system converts each event into a relative position. Orders A and B are relatively close in their relative positions across the five event categories, while order C is significantly delayed in the packing, handover, and package pickup stages. Subsequent steps can then be based on... It is determined that orders A and B are more likely to belong to the same collaborative work unit.

[0021] During the event extraction process, the system maps the status fields of different systems to unified event categories according to the event type dictionary. "INBOUND_DONE" or "Received into Warehouse" in the warehouse management system is mapped to the inbound completion event, "SHELVED" or "Placed on Shelves" is mapped to the shelving completion event, "PACKED" or "Packed" is mapped to the packing completion event, "HANDOVER_DONE" or "Handover Completed" is mapped to the outbound handover event; "PICKED_UP" or "Successfully Collected" in the courier interface is mapped to the courier collection event. If the original status code does not match the event type dictionary, the record is written into the pending mapping event queue and does not directly participate in the construction of the current order event chain. If there are multiple records of the same event category, for example, two packing records are generated for the same order due to recheck scanning, the record with the final confirmation completed is selected as the time value of this event; if a key event is missing, for example, the courier interface has not yet returned the collection completion, the courier collection node of this order will not enter the completed accounting chain for the time and will be retained in with the missing placeholder; if any of the key events at the later stage such as packing completion, outbound handover or courier collection is missing, this order will not enter the current completed collaborative recognition candidate pool and only the pending recording status will be retained. After the completion time is processed, the system sorts each anonymous order into an order event chain in a fixed order: ; where, represents the order event chain of the anonymous order ; corresponds to the processed time value of the inbound completion event, corresponds to the processed time value of the shelving completion event, corresponds to the processed time value of the packing completion event, corresponds to the processed time value of the outbound handover event, corresponds to the processed time value of the courier collection event. This formula forms a comparable vector structure by arranging the five key events in a fixed business order, and in subsequent steps, the event values at the same position can be directly read to determine whether the orders are close in the same operation stage. Since the elements in the chain are all dimensionless results obtained from the previous formula, is used as the event chain structure for sorting, comparison and grouping.

[0022] The system also extracts the exception flag from the order management system or the warehouse exception handling module. If the anonymous order has statuses such as order splitting, reissuing, redirection, delayed release, repacking, canceling and reissuing in the current accounting batch that will change the packing handover relationship or the attribution of courier fees, then takes 1; if there is no such status, then Set the value to 0. For example, if order A is split and reshipped after packaging, and the system reads the "split order" status, then... If order B successfully completes the processes of warehousing, shelving, packaging, handover, and pickup, then... This step outputs two results: the order event chain. and anomaly indicators . It consists of the processing time values ​​of five types of key operational events, which are used to identify whether an order is actually in the same inbound / outbound linkage operation process; The order status field is used to determine whether an order may incur additional charges. Through this process, logs that were originally scattered across the warehousing, order, and courier systems are organized into a unified structure for courier service fee calculation. Subsequent steps can then be collaboratively identified based on the order's position in the actual operational process.

[0023] S2: Identify collaborative work units. Based on the relative work positions of each key node in the order event chain, calculate the collaborative work difference value between orders, identify the set of orders that actually share packaging, handover and collection resources, and form collaborative work units.

[0024] Specifically, step two follows the order event chain formed in step one. and anomaly indicators It is used to identify sets of orders that actually share warehousing and express delivery resources within the same accounting batch and to form collaborative operation units. In warehousing and logistics inbound / outbound linkage scenarios, the formation of express delivery service fees is usually related to whether the order goes through multiple operational nodes such as packaging, outbound handover, and express pickup. Therefore, this step will output the results from step one. As the primary object of computation, As a basis for adjusting the collaborative boundary. Among them, to Corresponding to orders The time and location after the processing of the following stages: warehousing completion, shelving completion, packaging completion, outbound handover, and express delivery pickup. Indicates order The system checks for abnormal states such as order splitting, reshipment, re-delivery, delayed release, repackaging, and cancellation / re-shipment. First, it determines a candidate order pool based on warehouse and work batch identifiers. For example, if a single warehouse forms a courier handover batch in the morning, the system will place the order event chain within that batch, where all three key downstream nodes—packaging completion, outbound handover, and courier pickup—with valid time values, into the same candidate order pool for collaborative identification. If a warehouse has multiple handover batches on the same day, this step is executed in the corresponding candidate order pool for each batch. The resulting collaborative work unit directly reflects the actual organizational boundaries in the warehouse handover and courier pickup processes and serves as the object for subsequent basic cost allocation.

[0025] Within the candidate order pool, the system selects any two orders. and Calculate the difference value of the coordinated operation The initial source for this calculation is the weighted Euclidean distance in mathematics, which is typically used to measure the degree of difference between two multidimensional vectors when the importance of different dimensions varies. This application considers five key operational nodes as a five-dimensional operational trajectory of an order in the inbound / outbound linkage process, and assigns weights to different nodes based on the actual stages in which express service fees are generated: Inbound completion and shelving completion mainly reflect the order entering the fulfillment cycle and meeting the conditions for outbound delivery; packaging completion, outbound handover, and express pickup more directly affect packaging organization, handover batches, and express billing, therefore, the latter half of the nodes are assigned higher weights. Based on the weighted Euclidean distance, this application further adds an anomaly boundary term, enabling orders with closely linked events but different anomaly states to be appropriately distinguished during collaborative identification, facilitating the retention of a basis for handling abnormal fees in subsequent steps. The specific calculation is as follows: ; in, Indicates order With orders The difference value of the linkage operation; and The order event chains are respectively from the output of step one. and , indicating an order With orders In the The time frame following the handling of critical events; Indicates the first The weights of key events in collaborative identification are pre-set in the warehouse operation configuration table. For example, the weights of inbound completion, shelving completion, packaging completion, outbound handover, and express delivery pickup can be set separately. , , , , This corresponds to the relative impact of the five operational nodes on the formation of express delivery service fees; This represents the anomaly boundary adjustment coefficient, configured by the enterprise based on the impact of historical anomaly orders on the outbound organization. For example, it can be set to... to ; and The orders output in step one are respectively and orders The formula identifies anomalies. The first part, derived from weighted Euclidean distance, measures the difference between two order event chains on multi-node work trajectories; the second part, derived from differences in abnormal states, reflects the difference in work organization stability between abnormal and normal orders. Because... , , , , and All are used as proportional positions, weights, or status indicators in the calculation, and the results are... As a dimensionless difference value, it can be compared with a co-evaluation threshold that is also dimensionless. Compare.

[0026] For example, within a single courier handover batch, the event chain for order A is as follows: The event chain for order B is as follows: The event chain of order C is as follows: Take weights , , , , Abnormal boundary adjustment coefficient Both Order A and Order B are normal orders, that is... , The difference between order A and order B is then... The calculation result is approximately The difference between order A and order C is... The calculation result is approximately If the event chain of order D is However, order D was split and reshipped. Therefore, the basic trajectories of orders A and D are relatively similar, approximately... Then superimpose abnormal boundary terms back, Approximately The calculation results reveal three business states: Order A and Order B have a highly similar overall operational rhythm; Order C lags significantly behind in packaging, handover, and pickup stages; and although Order D has a similar operational rhythm, abnormal states are preserved within the collaboration boundary.

[0027] The system obtains the relationships between orders in the candidate order pool. Then, according to the collaboration threshold Generate collaborative work units . This is derived from the distribution of order discrepancies confirmed to belong to the same packing and handover process in the warehouse's historical operation records. For example, a warehouse's historical records show that orders within the same outbound handover batch... Mainly concentrated The following are different handover batches Most exceeded Then you can Configured as In actual implementation, the system first selects orders from the candidate order pool that have not yet been grouped and The order was used as a seed order. Starting with this seed order, absorb orders that meet the difference criteria; the absorbed normal orders continue to serve as expansion points to absorb other orders that meet the criteria, until the current collaborative work unit no longer receives new orders. For For orders that meet the discrepancy criteria, the system allows them to be added to existing collaborative work units and retains their exception flags for subsequent cost correction; if all remaining ungrouped orders in the current candidate order pool are... Then select the time value after the outbound handover node is processed. The earliest order that has not yet been grouped is considered the seed order. If multiple orders exist... If they are the same, continue to select the time value after the express pickup node is processed. If the earliest orders are still the same, they are selected based on their anonymous order identifiers, and then the order with the earliest identifier is chosen. If there is only one order in the candidate order pool, that order directly forms a single-member collaborative work unit. This grouping process can be represented as: ; in, Indicates the first One collaborative work unit; This indicates the seed order for this collaborative work unit, which is generated from the candidate order pool that has not yet been grouped. Order selection; This represents the orders in the candidate order pool that are yet to be judged; It indicates that it has been included Orders; Indicates seed order Orders to be judged The difference value of the linkage operation; This indicates orders that have been assigned to a unit. Orders to be judged The difference value of the linkage operation; The collaborative threshold is determined by configuring historical warehouse outbound waves or express delivery batch records. This formula originates from the concept of connected components in graph theory, treating orders as nodes and order relationships satisfying the threshold as connections. This application applies it to the identification of inbound and outbound linked operations, enabling orders on the same continuous operation chain to form a collaborative operation unit. The first formula calculates the difference between orders, and the second rule forms an order set based on the difference and the threshold. The relationship between the two is to first quantify the operational differences between orders, and then construct collaborative operation units based on the difference boundaries.

[0028] Following the previous numerical example, if the collaboration threshold Order A and Order B Approximately ,satisfy Order B enters the collaborative work unit where Order A is located; Order A and Order C... Approximately greater than Order C will proceed to a separate evaluation process; Orders A and D... Approximately If the threshold condition is met, order D enters the collaborative work unit where order A is located, and carries... If order B and order E satisfy... Even if there is a slight time difference between order A and order E, order E can still enter the same market through order B. This corresponds to the actual situation of continuous packaging and handover in warehousing operations. Ultimately, this can form... Order D is marked as abnormal; Order C, due to its significant differences from other orders in this unit, can be considered as a new candidate in subsequent rounds. Or it can enter other collaborative work units.

[0029] System generation Then, a work unit identifier is written to each collaborative work unit, and the anonymous order identifier and corresponding order event chain contained in the unit are recorded. and anomaly indicators .For example, If the system records orders A, B, D, and E, then... The member set, and retains each order in the member record. and The following steps will be based on As the calculation object of the basic cost pool, it also uses the data reserved within the cell. Identify additional charges incurred by abnormal orders. The output is a set of collaborative work units. Each Each order corresponds to a set of orders that share packaging, handover, and pickup resources during the inbound / outbound process. Through this process, the continuous collaborative relationships in warehousing operations are transformed into a set of order boundaries that can be directly used for cost accounting. Subsequent basic cost allocation can then be based on each order. Expand.

[0030] S3: Generate basic cost allocation results. Generate basic allocation weights based on the degree of alignment between orders and subsequent operations within the collaborative work unit. Allocate the basic cost pool corresponding to the collaborative work unit to each order within the unit according to the basic allocation weights to obtain the basic cost allocation results.

[0031] Specifically, step three receives the collaborative work unit output from step two. and read each The order event chain that has already been preserved in the middle and anomaly indicators Simultaneously, it reads the basic cost pool corresponding to the collaborative work unit from the express delivery interface system or financial reconciliation system. .in, Indicates the first Each collaborative work unit comes from the grouping results of step two; Indicates order The five-node order event chain originates from step one and is retained by step two. In the member records; Indicates order The anomaly marker originates from step one and is retained along with the order member record; Represents collaborative work unit The corresponding basic express delivery service fee amount is obtained by matching the express delivery bill, express delivery handover batch bill, or internal service fee billing table. During matching, the system uses warehouse identifier, express delivery handover batch, operation batch identifier, and pickup batch number for association. For example, the total basic service fee for a certain express delivery handover batch in the express delivery bill might be... If step two identifies two collaborative work units within the batch, the system will allocate the corresponding fees to the appropriate units based on the correspondence between the handover batches and the work units. If a single billing record covers multiple collaborative work units and cannot be further split on the billing side, it will first be split into its own billing entries based on the proportion of orders placed by members of each collaborative work unit within the scope of the billing. The goal of this step is to first establish the basic cost allocation results under normal collaborative conditions. This result then serves as the basis for anomaly correction in step four.

[0032] In warehousing and logistics inbound / outbound linkage scenarios, orders within the same collaborative work unit participate in the packaging, handover, and pickup processes, but the degree to which each order aligns with the central operational rhythm of that unit varies. The closer the operational rhythm is to the center of the unit, the more typically the order participates in the unit's joint packaging, handover, and pickup processes; the closer the operational position is to the edge of the unit, the weaker the order's participation in the joint operational process, even though it is included in the same collaborative work unit. Therefore, the system first determines the order based on its position within the unit. exist The degree of fit of the subsequent operations within the system generates the basic allocation weight. This calculation originates from the mathematical concept of mean absolute deviation (MAD), which measures the degree of deviation of a sample from the center of the sample set. This application applies it to the three most sensitive nodes in courier service fee formation: packaging completion, outbound handover, and courier pickup. The degree of deviation is converted into a weight for fee allocation, specifically calculated as follows: ; in, Indicates order In its respective collaborative work unit The basic allocation weight within; This represents the collaborative participation adjustment coefficient, which is configured by the enterprise based on the differences in cost allocation for historical orders from the same batch. For example, it can be taken as... to ; , , From the order event chain , respectively representing orders The time and location after the packaging is completed, the warehouse is handed over, and the express delivery is picked up; , , Representing collaborative work units The average post-processing time of all member orders at the packaging completion, outbound handover, and express pickup stages is determined by... Each order The formula is derived directly from the average absolute deviation, converting the deviation of the subsequent operation into the degree of fit, and then... This establishes positive weights, allowing the degree to which an order participates in collaborative operations to influence the basic cost allocation process. In the formula, each event value represents its relative position obtained in step one. It is a proportionality coefficient, therefore For dimensionless weights; if If there is only one order, then the average post-processing time position of that order across the three back-end nodes is equal to the post-processing time position of its corresponding node. .

[0033] get Then, the system allocates collaborative work units according to the proportional allocation principle in cost accounting. Corresponding basic cost pool The cost is allocated to each order within the unit. The original form of proportional allocation was to distribute the total cost according to the proportion of each object's weight to the total weight. This application changes the allocation weight to be obtained from the degree of fit between the order's subsequent operations. This ensures that the allocation of basic costs corresponds to the actual packaging, handover, and collection process, specifically calculated as follows: ; in, Indicates order The basic cost allocation result under normal collaborative conditions; Represents collaborative work unit The corresponding basic cost pool comes from the cost records in the express delivery interface system or the financial reconciliation system; Indicates order The basic allocation weights are obtained from the previous formula; Represents collaborative work unit Any member order within; This represents the sum of the basic order allocation weights for all members within the collaborative work unit. The left side of the formula is the order cost, and the right side is the cost pool multiplied by a dimensionless ratio; the calculation result is consistent with the cost pool. All orders Adding equals This ensures that the basic cost pool is fully allocated.

[0034] For example, a collaborative work unit Includes Order A, Order B, and Order C, corresponding to the basic cost pool. The processing times of the three orders at the packaging completion, outbound handover, and express pickup stages are as follows: Order A is... Order B is Order C is The system first calculates the average post-processing time position of the three downstream nodes of the unit, for example... , , If we take Then, orders A, B, and C will each obtain their respective results according to the previous formula. Because orders A and B are closer to the central operational rhythm of this unit, their It will be slightly higher than order C, which deviated more significantly. The system will then... According to each order The weights of Order A, Order B, and Order C are allocated proportionally to the total weights. This result reflects the basic sharing of the shared express delivery service fee among orders under normal collaborative conditions, with anomalies identified by... The member record is retained until step four for further processing of cost corrections arising from abnormal operations.

[0035] The system completes each After calculating the basic costs for all orders, output the order basic cost allocation results. And associate the anonymous order identifier and the corresponding collaborative work unit in the result record. Order event chain and anomaly indicators For example, if If the system contains orders A, B, and C, then it will write the corresponding data for each of the three orders. , and And retain each order and The next step, step four, will directly read... As the basis for fee adjustments, and in conjunction with and Generate final accounting costs and expense accounting records Through this step, the collaborative operation boundary identified in step two is transformed into a calculable basic cost allocation result, enabling the express delivery service fee calculation to move from operation unit identification to order-level cost calculation.

[0036] S4: Correct the cost allocation and output the final accounting result. Based on the anomaly identifier and the degree of order offset in the subsequent operation within the collaborative operation unit, correct the basic cost allocation result and generate a cost accounting record containing the final accounting cost.

[0037] Specifically, step four takes the basic cost allocation results output in step three and reads each collaborative work unit. Domestic orders Basic Fees And continue to use the order event chain preserved in the unit. and anomaly indicators .in, From the collaborative work unit formed in step two, From the five-node event chain formed in step one, The abnormal status recorded in step one This is derived from the basic allocation results of the collaborative work unit cost pool in step three. This step converts the additional work occupancy caused by abnormal events into cost adjustment amounts and outputs the final calculated cost for the order. and expense accounting records In actual warehousing and logistics processes, abnormal events such as order splitting, reshipment, re-delivery, delayed release, and repackaging typically have a concentrated impact on downstream operational nodes such as packaging completion, outbound handover, and courier pickup. Therefore, this step focuses on examining the order's status within its designated area. Instead of re-dividing collaborative work units, the internal offset is relative to the subsequent operations of the same unit order.

[0038] The system first in each collaborative work unit Internal calculation order degree of job deviation This calculation originates from the mathematical concept of mean absolute deviation (MAD), which measures the degree of deviation of a single sample from the center of the sample set. This application applies this concept to the inbound / outbound linkage operation chain, limiting the offset calculation to three downstream nodes: packaging completion, outbound handover, and express delivery pickup. These three nodes directly determine the additional packaging, handover, and pickup organization costs in the express delivery service fee. The specific calculation is as follows: ; in, Indicates order In the corresponding collaborative work unit The degree of deviation in the later stages of the operation; , , From the order event chain , respectively representing orders The time and location after the packaging is completed, the warehouse is handed over, and the express delivery is picked up; , , Representing collaborative work units The average post-processing time position of all member orders at the packaging completion, outbound handover, and express pickup stages is determined by... Each order The average is calculated directly. This formula is derived from the mean absolute deviation. This application changes the deviation object from ordinary sample values ​​to the express delivery service fee, forming the three most sensitive downstream operation nodes, so that the delayed packaging, delayed handover, or delayed pickup of abnormal orders can be converted into a calculable degree of offset. In the formula, each term represents the processed relative position difference. This is a dimensionless offset value.

[0039] In obtaining Then, the system will mark the anomaly. With offset degree The base cost that works together in step three This forms the final accounting cost. This calculation originates from the basic cost-plus concept in cost accounting, which involves adding incremental costs caused by specific operational factors to a predetermined basic cost. This application applies this concept to the accounting of express delivery service fees, limiting incremental costs to the impact of abnormal orders on subsequent operational deviations within the collaborative work unit; when... At that time, the order maintains the basic cost result unchanged, only when Furthermore, anomaly correction is only introduced when there is a deviation in the subsequent operation. The specific calculation is as follows: ; in, Indicates order The final accounting cost; This indicates the order output from step three. Basic costs; This represents the abnormal cost adjustment factor, which is configured by the company based on the proportion of additional packaging, additional handover, or additional collection costs caused by historical abnormal operations. For example, it can be taken as... to ; This indicates the order output from step one. Anomaly indicators; This indicates the degree of deviation in the subsequent operations obtained from the previous formula. The logic of this formula is to first determine the basic cost that the order should bear under normal collaborative operations in step three, and then make incremental corrections based on the abnormal conditions and the deviation in the subsequent operations. and All figures are cost values, with dimensionless correction coefficients in parentheses. Therefore, the calculation results are consistent with the basic costs.

[0040] For example, a collaborative work unit Including orders A, B, and C, the basic costs output in step three are as follows: , , The average post-processing time positions of the three downstream nodes within this unit are as follows: , , Order C was split and reshipped. The corresponding later node in the event chain is , , ,but If the enterprise configures its costs based on historical abnormal activity costs... Then the final cost of order C is If the exception flag for orders A and B is 0, then their final costs will remain as follows: and In this example, abnormal order C bears the incremental costs caused by its own abnormal job offset, while normal orders still enter settlement according to the basic costs formed in step three.

[0041] The system completes each order. After calculation, cost accounting records are generated. Each Associated anonymous order identifier and associated collaborative work unit Basic Fees Abnormal indicators Degree of deviation from work Abnormal correction amount and final accounting costs The data is then written to the financial settlement system or customer billing system via the expense accounting interface. During the actual writing process, the system generates an accounting record based on the order dimension; for example, the record corresponding to order C includes its order details. Basic Fees Abnormal indicators Degree of deviation from work Abnormal correction amount and final cost The financial system generates the settlement amount or internal cost collection amount for the order based on this. If the expense accounting interface is unavailable during the current writing cycle, the system writes the record to the pending settlement queue and retains the current accounting batch identifier. The system will then perform the supplementary writing after the interface is restored.

[0042] This step outputs two results: the final calculated cost. and expense accounting records . Used to determine the actual courier service fee that should be included for each order. This process is used to incorporate the calculation results into the settlement system and retain the accounting basis. Through this process, the basic cost allocation results formed in step three are further transformed into executable order-level accounting results, and the additional operational impact of abnormal events on the packaging, handover, and pickup processes is also included in the final cost.

[0043] This invention also provides a device for dynamically allocating and calculating warehousing and logistics inbound / outbound express delivery service fees, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor. When the processor executes the computer program, it implements the steps described in the above embodiment of a method for dynamically allocating and calculating warehousing and logistics inbound / outbound express delivery service fees, for example... Figure 1 The steps S1 to S4 described above; or, when the processor executes the computer program, it implements the functions of each module in the above system embodiments.

[0044] For example, the computer program can be divided into one or more modules, which are stored in the memory and executed by the processor to complete the present invention. The one or more modules can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program in the warehousing and logistics inbound / outbound linkage express delivery service fee dynamic allocation and accounting device.

[0045] The aforementioned device for dynamically allocating and calculating warehousing and logistics inbound / outbound express delivery service fees can be a desktop computer, laptop, handheld computer, or cloud server, among other computing devices. This device may include, but is not limited to, processors and memory. Those skilled in the art will understand that the device may also include input / output devices, network access devices, and buses.

[0046] The processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the warehousing and logistics inbound / outbound linkage express delivery service fee dynamic allocation and calculation equipment, connecting all parts of the equipment via various interfaces and lines.

[0047] The memory can be used to store the computer program and / or modules. The processor, by running or executing the computer program and / or modules stored in the memory, and by calling the data stored in the memory, realizes various functions of the warehousing and logistics inbound / outbound linkage express service fee dynamic allocation and accounting device. The memory may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc.; the data storage area may store data created according to the operation of the controller, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital card (SD card), flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0048] The module integrating the dynamic allocation and accounting of express delivery service fees for warehouse logistics inbound and outbound operations, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0049] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0050] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.

Claims

1. A method for dynamic allocation and accounting of express delivery service fees linked to warehousing and logistics inbound and outbound operations, characterized in that, The method includes: Construct an order event chain, extract operation records related to cost formation from the warehouse management system, order management system and express interface system. The operation records include inbound completion, shelving completion, packaging completion, outbound handover and express pickup. Arrange the operation records into an order event chain according to the business sequence, and extract the abnormal identifier of the order. Identify collaborative work units, calculate the collaborative work difference value between orders based on the relative work positions of each key node in the order event chain, identify the set of orders that actually share packaging, handover and collection resources, and form collaborative work units; Generate a basic cost allocation result. Generate a basic allocation weight based on the degree of alignment between the order and the subsequent operations within the collaborative work unit. Allocate the basic cost pool corresponding to the collaborative work unit to each order within the unit according to the basic allocation weight to obtain the basic cost allocation result. The cost allocation is corrected and the final accounting result is output. Based on the anomaly identifier and the degree of deviation of the order in the subsequent operation within the collaborative operation unit, the basic cost allocation result is corrected to generate a cost accounting record containing the final accounting cost.

2. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The construction of the order event chain specifically includes: The time of critical events within the same accounting batch is standardized by range processing, which maps the event times from different systems to a unified comparison scale to obtain the processed event time values. Using the anonymous order identifier as the primary key, the processed time values ​​of five key events for the same order are arranged into an order event chain according to a fixed business sequence.

3. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The identification collaborative operation unit specifically includes: Within the candidate order pool, calculate the linkage operation difference value for any two orders. The calculation of the linkage operation difference value includes a weighted Euclidean distance term and an anomaly boundary term. The difference value of the linked operation is compared with the collaboration threshold. If the difference value is less than or equal to the collaboration threshold, the order is grouped into the same collaborative operation unit until all orders that meet the conditions in the candidate order pool are grouped.

4. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The specific results of generating the basic cost allocation include: Based on the time position of the order after packaging completion, outbound handover, and express pickup node processing within the collaborative work unit, calculate the average absolute deviation between the order and the average time position of the members within the unit, and convert the average absolute deviation into the basic allocation weight. The basic cost pool corresponding to the collaborative work unit is allocated according to the proportion of the basic allocation weight of each order to the total weight, so as to obtain the basic cost of each order.

5. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The process of adjusting the cost allocation and outputting the final accounting results specifically includes: Within each collaborative work unit, the average absolute deviation between the post-processing time position of order packaging completion, outbound handover, and express pickup nodes and the average time position of members within the unit is calculated to obtain the degree of deviation in subsequent operations. If the order's anomaly flag is 1, the base cost is incrementally corrected based on the degree of deviation in the subsequent operations to generate the final accounting cost; if the anomaly flag is 0, the base cost is retained as the final accounting cost.

6. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The operational records related to extraction and cost formation also include: Verify the original records. If a record lacks an anonymous order identifier, warehouse identifier, or work batch identifier, mark it as a record to be verified. If multiple records appear for the same event category, the record that is finally confirmed as completed will be selected as the time value for that event; if a key event is missing, the order will not be included in the completed collaborative identification candidate pool.

7. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The anomaly identifier includes the status of order splitting, resending, re-delivery, delayed release, repackaging, or cancellation of resending. If an order has any of the above statuses, the anomaly identifier is set to 1; otherwise, it is set to 0.

8. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The process of generating the basic cost allocation results also includes: Read the basic cost pool corresponding to the collaborative operation unit from the express delivery interface system or financial reconciliation system; If the same billing record covers multiple collaborative work units, the billing will be split into separate expense pools according to the proportion of member orders in each collaborative work unit within the billing coverage area.

9. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, The generation of cost accounting records that include the final calculated costs specifically includes: Generate records of associated anonymous order identifiers, their respective collaborative work units, basic costs, anomaly identifiers, work offset degrees, anomaly correction amounts, and final calculated costs; The records are written into the financial settlement system or customer billing system through the expense accounting interface.

10. The method for dynamic allocation and accounting of warehousing and logistics inbound / outbound express delivery service fees according to claim 1, characterized in that, In the identification collaborative operation unit, the collaborative threshold is derived from the distribution of order difference values ​​in the warehouse's historical operation records that have been confirmed to belong to the same packaging and handover process.

Images