Multi-level inventory resource allocation method, device, medium and product
By employing a multi-tiered inventory resource allocation method, priority customers are dynamically identified and a shared resource pool is constructed. This addresses the issues of low efficiency, poor fairness, and insufficient market liquidity in resource allocation, achieving flexible and controllable resource management and fair and transparent market liquidity.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHANGHAI GANGSOFT INFORMATION TECH ENG CO LTD
- Filing Date
- 2026-04-30
- Publication Date
- 2026-06-19
Smart Images
Figure CN122243368A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of information technology, and in particular to multi-level inventory resource allocation methods, equipment, media and products. Background Technology
[0002] Traditional solutions typically employ static single-level allocation or a simple first-come, first-served strategy, which leads to the following technical problems:
[0003] Problem 1: The inability to hierarchically and proportionally divide resources based on multiple dimensions leads to inefficient resource utilization, especially in complex scenarios where existing commitments (long-term contracts) need to be met while balancing futures and spot demand, easily resulting in idle resources or supply gaps.
[0004] Issue 2: The customer allocation rules lack flexibility and fail to reflect priority and historical performance. The existing scheme struggles to achieve differentiated allocation among customers, failing to dynamically prioritize and allocate based on unused spending (historical spending power) or cumulative spending thresholds (priority indicators). This results in high-spending, high-priority customers not receiving corresponding priority allocation rights, reducing the fairness and incentive of the allocation process.
[0005] Question 3: Inadequate concurrency control can easily lead to resource over-provisioning or order failures. Traditional stand-alone or simple locking solutions are prone to discrepancies between cached and actual available resources during high-concurrency order submissions. When multiple customers submit orders simultaneously, the existing locking mechanism is either too coarse-grained (global locks cause performance bottlenecks) or inappropriately granular (leading to race conditions in certain scenarios), ultimately resulting in over-provisioning or system order rejection.
[0006] Question 4: The conversion between futures and spot markets lacks automation and timeliness. Most existing solutions rely on manual review or timed batch processing to convert unused futures contracts into spot contracts. This is not only inefficient but also prone to missing market opportunities, resulting in futures resources not being promptly converted into spot supply and reducing market liquidity.
[0007] Question 5: Insufficient Resource Sharing and Transparency. In traditional solutions, long-term contracts, futures, and spot markets operate independently, resulting in fragmented resource information and making it difficult to form a unified shared resource pool. This creates information silos in the market, hindering efficient resource flow and fair access for customers.
[0008] Therefore, how to provide multi-level inventory resource allocation methods, equipment, media, and products to solve the aforementioned technical problems in the existing technology has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention
[0009] One object of this application is to provide a multi-level inventory resource allocation method, device, medium, and product, at least to solve the problem.
[0010] To achieve the above objectives, some embodiments of this application provide the following aspects:
[0011] In a first aspect, some embodiments of this application provide a multi-level inventory resource allocation method, comprising: receiving inventory resource information from at least one database to obtain a detailed list of allocable inventory resources for the day; dividing the detailed list of allocable inventory resources for the day into futures resources and spot resources; allocating futures resources according to priority customers and non-priority customers, and updating the detailed list of allocable inventory resources for the day; when a customer bill of lading request is received, automatically deducting the inventory resources corresponding to the customer bill of lading request from the detailed list of allocable inventory resources for the day, allocating the deducted resources to the customer who needs to make a bill of lading, and converting the futures resources into spot resources; and constructing and publishing a futures-spot shared resource pool.
[0012] Secondly, some embodiments of this application also provide an electronic device, the electronic device comprising: one or more processors; and a memory storing computer program instructions, which, when executed, cause the processor to perform the steps of the multi-level inventory resource allocation method described above.
[0013] Thirdly, some embodiments of this application also provide a computer-readable medium having computer program instructions stored thereon, which can be executed by a processor to implement the multi-level inventory resource allocation method described above.
[0014] Fourthly, some embodiments of this application also provide a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the multi-level inventory resource allocation method described above.
[0015] Compared with related technologies, the solution provided in this application has the following main advantages.
[0016] First, by dynamically dividing cargo resources at multiple levels, flexible and controllable resource allocation is achieved, significantly improving resource utilization efficiency.
[0017] Second, based on the dynamic allocation of customer priority and non-priority, it realizes the automatic identification of high-value customers and gives them priority status, resulting in fair and incentivizing differentiated resource allocation.
[0018] Third, based on the automatic futures-spot conversion and shared resource pool aggregation method, unconsumed futures are automatically converted into spot and included in a unified shared resource pool. Compared with manual review or simple batch processing, this significantly improves conversion efficiency and market liquidity, while ensuring complete transparency and fair allocation of resources. Attached Figure Description
[0019] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.
[0020] Figure 1 An exemplary flowchart for multi-level inventory resource allocation is provided for some embodiments;
[0021] Figure 2 An exemplary flowchart for another multi-level inventory resource allocation provided for some embodiments;
[0022] Figure 3 An exemplary structural diagram of an electronic device is provided for some embodiments. Detailed Implementation
[0023] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0024] In this embodiment of the disclosure, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information comply with relevant laws and regulations and do not violate public order and good morals.
[0025] First Embodiment
[0026] The first embodiment relates to a multi-level inventory resource allocation method. For example... Figure 1 As shown, the method may include the following steps:
[0027] S11, Receive inventory resource information from at least one database to obtain a detailed list of allocable inventory resources for the day;
[0028] S12, the daily inventory resource allocation details list is divided into futures resources and spot resources;
[0029] S13, allocate futures resources according to priority customers and non-priority customers, and update the daily inventory resource allocation details list;
[0030] S14. When a customer bill of lading request is received, the inventory resources corresponding to the customer bill of lading request are automatically deducted from the daily inventory resource allocation details list, so as to allocate the deducted resources to the customer who needs the bill of lading and convert the futures resources into spot resources.
[0031] S15, build and publish the futures-spot shared resource pool.
[0032] The first embodiment relates to a multi-level inventory resource allocation method. The core of this embodiment lies in receiving inventory resource information from at least one database to obtain a detailed list of allocable inventory resources for the day; segmenting the detailed list of allocable inventory resources for the day into futures resources and spot resources; allocating futures resources according to priority customers and non-priority customers, and updating the detailed list of allocable inventory resources for the day; when a customer bill of lading request is received, automatically deducting the inventory resources corresponding to the customer's bill of lading request from the detailed list of allocable inventory resources for the day, allocating the deducted resources to the customer requiring the bill of lading, and converting the futures resources into spot resources; and constructing and publishing a futures-spot shared resource pool. By dynamically allocating goods resources across multiple levels, flexible and controllable resource allocation is achieved, significantly improving resource utilization efficiency. Furthermore, based on customer priority and non-priority dynamic resource allocation, fair and incentivizing differentiated resource allocation is realized. Additionally, based on automatic futures-spot conversion and shared resource pool aggregation methods, unconsumed futures are automatically converted into spot goods and incorporated into a unified shared resource pool. Compared to manual review or simple batch processing, this significantly improves conversion efficiency and market liquidity, while ensuring complete transparency and fair allocation of resources. The following details the implementation of the multi-level inventory resource allocation method in this embodiment. These details are provided for ease of understanding and are not essential for implementing this solution.
[0033] Second Embodiment
[0034] The second embodiment relates to a multi-level inventory resource allocation method. The second embodiment is an improvement upon the first embodiment, with the main difference being the addition of a distributed lock concurrency control mechanism based on product category and daily timeframe, and automatic conversion and shared aggregation of futures and spot goods based on a product category-based timed strategy.
[0035] The second embodiment relates to another multi-level inventory resource allocation method. For example... Figure 2 As shown, the method may include the following steps:
[0036] S21, receive inventory resource information from at least one database to obtain a detailed list of allocable inventory resources for the day.
[0037] As a preferred embodiment, S21 specifically includes the following steps:
[0038] S211, collect inventory resource information from at least one database, and normalize the data in the inventory resource information and synchronize the daily production output in real time; wherein, the inventory resource information includes the inventory balance (by category, specification, and material), the daily production output (by production line, category, and specification), the amount of material occupied during operation (work-in-process) and / or the amount of material not yet shipped (orders with confirmed bills of lading but not yet shipped).
[0039] S212, determine the available quantity and available weight of each type of goods in the daily inventory.
[0040] As a preferred option, the available quantity of each type of goods in the daily inventory is determined as follows:
[0041] Available quantity = Remaining inventory + Daily output - Material used for machine start-up
[0042] Among them, the starting material occupancy refers to the quantity of work-in-process that must be retained during the production process, and is not included in the resources available for allocation on that day.
[0043] Available weight = Number of available pieces × Weight per piece - Weight not yet shipped
[0044] The unit weight refers to the standard weight of the goods. The unshipped weight refers to the amount of goods for which a bill of lading has been issued but not yet shipped, and must be deducted from the available weight.
[0045] S213, perform weight accuracy processing on the available weight of each type of cargo.
[0046] In this embodiment, in order to ensure consistency between the financial actuarial caliber and the system allocation caliber, step S213 will round the available weight according to the precision requirements of the product category. For example, for high-precision products such as rebar, the weight is retained to two decimal places (in tons).
[0047] S214, the processed data is organized into a structured list to form the daily inventory resource allocation details list. The daily inventory resource allocation details list includes fields and descriptions, wherein the fields include warehouse ID, product name, material, specifications, unit weight, number of available pieces, available weight, whether it is a special specification, and / or data timestamp; the descriptions include the warehouse to which the goods belong, product category name, material code, specification identifier, standard part weight, number of pieces available for allocation on the day, weight available for allocation on the day, and / or data update time. In this embodiment, the daily inventory resource allocation details list provides the data foundation for all subsequent allocation operations.
[0048] S22 divides the daily inventory resource allocation details into futures resources and spot resources.
[0049] As a preferred embodiment, S22 specifically includes the following steps:
[0050] S221, Read the long-term contract ratio and divide the total long-term contract amount from the available weight for allocation on the current day according to the long-term contract ratio. In this embodiment, long-term contracts are a type of futures contract. Therefore, in order to prioritize fulfilling the commitments of long-term contract customers and ensure business continuity, while reserving flexible resource space to cope with market changes, this step adopts the first level of division, namely the division of long-term contracts and non-long-term contracts.
[0051] S222, group the product category into long-term contract groups based on the total long-term contract volume.
[0052] For example, if a long-term contract for a certain product category includes Group A and Group B, it will be further subdivided according to the proportion of unresolved issues in each group.
[0053] The share of long-term contract group A = total long-term contract amount × (unclaimed amount of group A / total unclaimed amount of all groups)
[0054] The share of long-term contract group B = total long-term contract amount × (unclaimed amount of group B / total unclaimed amount of all groups)
[0055] S223, for goods marked as having special specifications, allocate them separately to the long-term contract side according to a preset fixed quantity or fixed proportion;
[0056] S224. Organize the long-term contract share (number of available pieces and available weight) that each group can obtain, as well as the corresponding fields (category, specifications, warehouse, etc.), for long-term contract allocation to form a long-term contract shared resource list for the day.
[0057] S225, the total amount of non-long-term contracts is separated from the weight available for allocation on that day.
[0058] Specifically, the total amount of non-long-term contracts = the total amount available on the day - the total amount of long-term contracts.
[0059] S226, the total non-long-term contract volume is further divided according to the ratio of futures and spot goods, and each commodity is recorded on both the futures and spot sides according to fields (e.g., warehouse, category, specification, unique identifier of unit weight) to obtain the allocable number of futures and spot resources (i.e., the allocable quantity and total allocable amount of futures and spot resources). This embodiment focuses on the non-long-term contract portion, and performs secondary division according to different trading attributes, which satisfies the expectations of futures clients while preserving liquidity in the spot market.
[0060] S227, forming a long-term contract shared resource list and a multi-dimensional allocation matrix for futures / spot markets.
[0061] Wherein, futures resources = non-long-term contract portion × futures ratio
[0062] Spot resources = Non-long-term contract portion × (1 - Futures ratio)
[0063] Compared to the single allocation strategy of existing technologies, this application utilizes a dynamic segmentation method of multi-level proportional chains to achieve flexible and controllable resource allocation through multi-level sequential segmentation of long-term contracts, futures, and spot markets, as well as secondary segmentation of long-term contract groups, which greatly improves resource utilization efficiency.
[0064] S23, allocate futures resources according to priority customers and non-priority customers, and update the daily inventory resource allocation details list.
[0065] As a preferred embodiment, S23 specifically includes the following steps:
[0066] S231, iterate through all futures clients and compare their current undelivered commodity resources with a pre-configured cumulative threshold. If a futures client's current undelivered commodity resources are greater than or equal to the cumulative threshold, then the futures client is marked as a priority client. In this embodiment, the pre-configured cumulative threshold is used to identify clients with high spending power, automatically assigning them priority status. During futures allocation, their undelivered resource requirements can be directly met without competing with other clients.
[0067] S232, sort all futures clients according to their current unutilized commodity resources (e.g., in descending order) to form a priority client queue.
[0068] S233. According to the differentiated allocation logic, allocate the corresponding current unused commodity resources to each futures client. The allocation logic is as follows: Iterate through each client in the priority client queue. If the remaining amount of futures resources is greater than or equal to the current unused commodity resources, the priority client's current futures resource allocation equals the current unused commodity resources, and the remaining amount of futures resources equals the futures resources minus the priority client's current futures resource allocation. If the current unused commodity resources are greater than the remaining amount of futures resources, and the remaining amount of futures resources is greater than 0, the priority client's current futures resource allocation equals the remaining amount of futures resources. If the remaining amount of futures resources is 0 or the priority client's current futures resource allocation is 0, stop iterating.
[0069] S234, deduct the allocation amount corresponding to each futures client from the futures resources.
[0070] S235 allocates the remaining futures resources according to the proportion of unclaimed volume for each non-priority customer.
[0071] Specifically, the allocation of futures resources to customer i = remaining futures resources × customer i's unused portion, where customer i's unused portion = customer i's unused portion / the sum of unused portions of all non-priority customers. The unused portion is used for the proportional allocation of non-priority customers, reflecting historical consumption performance; customers with strong consumption power (large unused portions) receive a larger allocation share.
[0072] S236, based on the precision requirements of the product category, perform precision processing on the weight of the allocation results of futures resources for priority customers and the allocation results of futures resources for non-priority customers to ensure that the total allocation amount does not exceed the total distributable quantity, and compile the allocation results of futures resources for priority customers and the allocation results of futures resources for non-priority customers to form a preview list of customer futures allocations for the day.
[0073] The allocation results of futures resources for priority clients and the allocation results of futures resources for non-priority clients include:
[0074] Customer ID, Product Category, Specifications, Futures Allocation Quantity, Futures Allocation Weight, Priority Mark... ... ... ... ...
[0075] In this implementation, by classifying futures contracts at the customer level and combining pre-configured cumulative volume thresholds and the percentage of unclaimed volume, this application can further differentiate allocations based on customers' cumulative spending power and historical unclaimed volume, achieving dynamic adjustment of priorities. Compared to single-level allocation or first-come, first-served allocation, this multi-tiered design significantly improves resource utilization efficiency and satisfaction.
[0076] As a preferred embodiment, step S23 further includes the following steps:
[0077] For each item (e.g., groups by category, specification, warehouse, and unit weight), a goods resource pool is constructed and recorded. Each record includes fields and corresponding descriptions. The fields include: Goods ID, Category, Specification, Warehouse ID, Unit Weight, Total Allocable Weight, Number of Futures Allocable Units, Futures Allocable Weight, Number of Spot Allocable Units, Spot Allocable Weight, Daily Identifier Date Stamp, and Expiry Date. The corresponding descriptions include: Unique Identifier, Category Name, Specification Identifier, Warehouse, Standard Unit Weight, Calculated from step S23, Number of Futures Allocable Units on the Daily Side, Number of Futures Allocable Weight on the Daily Side, Number of Spot Allocable Units on the Daily Side, Spot Allocable Weight on the Daily Side, and Expiry Date for Expiry Control and Resources.
[0078] Develop a query index for the goods resource pool (e.g., by category + specification + daily identifier) to improve the efficiency of data querying in the resource pool.
[0079] Once the preview list of client futures allocations for the day is confirmed, it will be included in the day's inventory.
[0080] Detailed list of allocable resources.
[0081] For each customer, a daily record of futures resource allocation is created and maintained, and a detailed list of allocable inventory resources for the day, along with the corresponding goods resources, is cached. Each record includes fields and corresponding descriptions. Fields include: Customer ID, Futures Allocation Category Group, Futures Allocation Details, Day Identifier, Validity Period, Used Quantity / Weight, and Remaining Available Quantity / Weight. The corresponding descriptions include: Customer Unique Identifier, All Categories Allocated to This Customer on That Day, Allocated Quantity / Weight by Category / Specification, Date Stamp (usually 23:59:59 of the current day, initially 0, updated upon subsequent order fulfillment), and Total Allocated Quantity minus Used Quantity.
[0082] Add version numbers and update timestamps to cached resources to synchronize metadata and support subsequent consistency checks and expiration deletion.
[0083] Once the resources are updated, a message queue is sent to the customer indicating that the goods resources for the day are ready.
[0084] S24, When a customer's bill of lading request is received, the inventory resources corresponding to the customer's bill of lading request are automatically deducted from the daily allocable inventory resource list to allocate the deducted resources to the customer who needs to submit the bill of lading. The daily allocable inventory resource list refers to the resource list after the confirmation of the daily futures allocation results at the customer level, which is used for automatic deduction when the order is submitted.
[0085] As a preferred embodiment, step S24 specifically includes the following steps:
[0086] S241, upon receiving a customer's bill of lading request, extract key order parameters from the customer's bill of lading requirements. These key parameters include customer ID, product category, specifications, number of items that can be picked up, and / or weight that can be picked up.
[0087] S242 uses the category and date stamp as the lock key to acquire a distributed lock. Distributed locks apply locks at the granularity of category and date identifier, avoiding the performance bottleneck of global locks and preventing race conditions caused by overly fine-grained locks. For example, the lock timeout is set to 5 seconds to prevent deadlocks caused by failures.
[0088] S243, after acquiring the distributed lock, verify whether the remaining quantity in the daily inventory resource allocation details list is greater than or equal to the requested quantity in the customer's bill of lading request. If so, continue to verify whether the futures resources and / or spot resources in the goods resources are consistent with the version number in the cache. If not, roll back all updates. If consistent, it means that the double verification has passed, and the next step, the deduction operation, can continue. If inconsistent, it means that the verification has failed, and all updates are rolled back. This embodiment uses double verification, that is, after acquiring the distributed lock, first verifying the remaining available quantity in the customer's automatically allocated resource list, and secondly verifying the consistency of the version number of the goods resource pool, to ensure the real-time synchronization of the two data sources and the integrity of preventing over-allocation.
[0089] S244, based on the requested quantity in the customer's bill of lading request, perform the corresponding deduction operation to update the number of used items and the remaining quantity of current goods in the daily inventory resource allocation details list, and update the number of existing futures items and existing spot items that can be allocated in the goods resource pool.
[0090] In this embodiment, the number of used items and the remaining quantity of existing items in the daily inventory resource allocation details list are as follows:
[0091] The current number of used items = the quantity applied for this time + the number of used items.
[0092] Current remaining quantity of goods = Number of remaining usable items - Quantity requested in this application
[0093] The number of divisible futures contracts and the number of divisible spot contracts currently available in the commodity resource pool are as follows:
[0094] Existing futures divisible units = Total futures divisible units - Current application volume from the futures side
[0095] Existing stock available for splitting = Existing stock available for splitting - Current application quantity from the spot market
[0096] S245, record the deduction operation and check whether all deduction operations were successful. If not, roll back all updates; if yes, release the distributed lock and provide a success confirmation message and a resource snapshot of the bill of lading. The recorded details include order ID, customer ID, category, specifications, number / weight of applications, deduction time, and / or a snapshot of available quantities before and after the deduction.
[0097] To ensure consistency between the cache and the database, thereby preventing resource over-consumption in high-concurrency order submission scenarios, the system's order rejection rate is significantly reduced. The S24 method also includes:
[0098] S246. After each successful deduction, immediately refresh and update the daily inventory resource allocation details list and goods resource pool. At each preset time interval, perform a timed verification to check the amount of resources in the cache against the actively allocated / used amount in the database. If the two quantities are inconsistent, calibrate the resources in the cache based on the data recorded in the database.
[0099] S25 converts futures resources into spot resources while performing the deduction operation.
[0100] As a preferred option, step S25 specifically includes the following steps:
[0101] S251, read the preset futures-spot conversion timing strategy according to the category level (e.g., triggered once each at 14:00, 16:00, and 18:00 daily). The preset futures-spot conversion timing strategy includes the conversion trigger time, whether the long-term contract share can be transferred to the commodity resource pool, and the parameters of the spot order after conversion.
[0102] S252, if the preset futures-spot conversion timing strategy reads that it supports the transfer of long-term contract shares into the commodity resource pool, then collect the unused portion of the long-term contract group.
[0103] S253, determine whether to transfer the long-term contract share to the goods resource pool. If so, transfer the unused portion of the long-term contract group to the long-term contract shared resource pool in the goods resource pool and generate the long-term contract shared resource list for the day.
[0104] S254, count the remaining futures resources in the commodity resources, and use a conversion strategy to convert the remaining futures resources into spot resources. The conversion strategy includes the spot divisible weight being equal to the divisible weight of the remaining futures resources, the futures divisible weight being equal to 0, and marking the resources converted from futures to spot.
[0105] The specific conversion process is as follows:
[0106] Scan all records in the cargo resource pool, for each cargo:
[0107] Unconsumed futures weight = Divisible futures weight - Weight of futures consumed on the current day
[0108] S255 converts the total unconsumed futures weight into spot attributes and updates the commodity resource pool, marking the futures contracts, for example, as being marked as converted from futures to spot. Here, the spot divisible weight equals the total unconsumed futures weight, and the futures divisible weight is 0.
[0109] S26, Build and publish the futures-spot shared resource pool.
[0110] As a preferred embodiment, step S27 specifically includes the following steps:
[0111] S261 generates a spot order for each commodity resource converted from futures to spot. The spot order includes fields and corresponding descriptions for each field. Fields include: Order ID, Category, Specifications, Available Weight, Minimum Available Weight, Maximum Available Weight, Publication Time, and Validity Period. The corresponding descriptions include a system-generated unique identifier, the commodity specifications originating from the futures conversion, the converted spot weight, a strategy-configured value (e.g., 5T), a strategy-configured value (e.g., 100T), and the timestamp of the futures-to-spot conversion cancellation and conversion.
[0112] S262, This involves statistically analyzing spot resources within commodity resources, integrating spot resources, daily long-term contract shared resources, and futures resources into a unified data structure to construct a futures-spot shared resource pool. This pool is then written to a distributed cache, and the cached data is updated, audited, and recorded. Recorded information includes the conversion trigger time, the list of commodities involved in the conversion, snapshots of resource quantities before and after the conversion, and the spot order ID generated after the conversion. This embodiment utilizes an automatic futures-spot conversion and shared pool aggregation method based on a category-based timed strategy. Unconsumed futures are automatically converted into spot and incorporated into a unified shared resource pool. Compared to manual review or simple batch processing, this significantly improves conversion efficiency and market liquidity while ensuring complete transparency and fair allocation of resources.
[0113] S263, Release the Futures-Spot Shared Resource Pool. The Futures-Spot Shared Resource Pool contains a unified set of resources, including spot assets converted from unused futures contracts, long-term contract shared resources, and targeted futures-spot shared resources, which are publicly available and consumable by all market participants.
[0114] The multi-level inventory resource allocation method provided in this embodiment has the following main advantages:
[0115] First, by dynamically dividing cargo resources at multiple levels, flexible and controllable resource allocation is achieved, significantly improving resource utilization efficiency.
[0116] Second, based on the dynamic allocation of customer priority and non-priority, it realizes the automatic identification of high-value customers and gives them priority status, resulting in fair and incentivizing differentiated resource allocation.
[0117] Third, based on the automatic futures-spot conversion and shared resource pool aggregation method, unconsumed futures are automatically converted into spot and included in a unified shared resource pool. Compared with manual review or simple batch processing, this significantly improves conversion efficiency and market liquidity, while ensuring complete transparency and fair allocation of resources.
[0118] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this application. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this application.
[0119] Third Embodiment
[0120] This embodiment provides an electronic device. The electronic device can be various forms of digital computer, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, mainframe computers, cellular phones, smartphones, wearable devices, and other similar computing devices.
[0121] The electronic device includes: one or more processors; and a memory storing computer program instructions, which, when executed, cause the processor to perform the steps of the multi-level inventory resource allocation method provided in any one or more of the above embodiments.
[0122] Figure 3 An exemplary structural diagram of the electronic device is disclosed. The electronic device includes one or more processors 1101, a memory 1102, an input device 1103, and an output device 1104. The various components are interconnected via a bus or other means (the diagram shows an example of bus connection). The processor 1101 can be used to execute instructions stored in the memory 1102 to control the overall operation of the electronic device. The memory 1102 may include a program storage area and a data storage area, wherein the program storage area stores the operating system and applications required for at least one function; the data storage area stores data created according to the use of the electronic device, etc. The memory 1102 may include high-speed random access memory and may also include non-transitory memory, such as disk storage devices, flash memory devices, or other non-transitory solid-state storage devices. In some embodiments, the memory 1102 may also include storage resources located remotely to the processor and accessible via a network.
[0123] Input device 1103 can be used to receive input numerical or character information or user operation signals, such as a touch screen, keypad, mouse, trackpad, touchpad, indicator, one or more mouse buttons, trackball, joystick, etc. Output device 1104 may include display devices (such as liquid crystal displays, light-emitting diode displays, plasma displays, and optional touch screens), auxiliary lighting devices (such as LEDs), and haptic feedback devices (such as vibration motors), etc.
[0124] To facilitate user interaction, the electronic device may be configured to include a display device (such as an LCD or CRT monitor) and input devices such as a keyboard and pointing devices (e.g., a mouse or touchpad). Feedback can be any form of sensory feedback (e.g., visual feedback, auditory feedback); input may also be received via voice, touch, or other means.
[0125] This embodiment also relates to a computer-readable medium storing a computer program / instructions that, when executed by a processor, implement the steps of the multi-level inventory resource allocation method provided in any one or more of the above embodiments. The computer-readable medium may be a memory included in an electronic device, or it may be a standalone storage medium not assembled into the device.
[0126] It should be noted that the computer-readable medium described in this application may be a computer-readable signal medium, a computer-readable storage medium, or a combination of both. Examples include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. Specific examples of storage media may include, but are not limited to, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory, optical fibers, portable CD-ROMs, optical storage devices, magnetic storage devices, etc., or any suitable combination thereof.
[0127] Computer-readable media may store one or more programs that can be used by or in conjunction with an instruction execution system. The media may be permanent or non-permanent, removable or non-removable, and may store information by any method or technology, including computer-readable instructions, data structures, program modules, or other data.
[0128] The computer program code used to implement the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages (such as Java, Smalltalk, and C++) and conventional procedural programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. The remote computer can be connected to the user's computer via any network (including a local area network or a wide area network) or can be connected to an external computer.
[0129] In the above embodiments, the functions can be implemented in whole or in part by software, hardware, firmware, or any combination thereof, for example, by using application-specific integrated circuits, general-purpose computers, or other similar hardware devices. In some embodiments, the software program of this application can be executed by a processor to implement the steps or functions; it can also be implemented by hardware, for example, as a circuit that works in conjunction with the processor to execute the steps or functions.
[0130] This embodiment also provides a computer program product, including one or more computer programs / instructions. When executed by a processor, the computer programs / instructions generate all or part of the processes or functions described in the embodiments of this application. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one storage medium to another via wired (e.g., DSL) or wireless (e.g., Wireless, Microwave) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.
[0131] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-specific system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0132] The scope of this application is defined by the appended claims rather than the foregoing description, and is therefore intended to encompass all variations falling within the meaning and scope of equivalents of the claims. No reference numerals in the claims should be construed as limiting the scope of the claims. Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in a device claim may also be implemented by a single unit or device in software or hardware. Terms such as "first," "second," etc., are used only for distinguishing descriptions and do not indicate any particular order, nor should they be construed as indicating or implying relative importance.
[0133] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily made by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims, and the above embodiments should be regarded as exemplary and non-limiting.
Claims
1. A multi-level inventory resource allocation method, characterized in that, include: Receive inventory resource information from at least one database to obtain a detailed list of available inventory resources for the day; The daily inventory resource allocation details list is divided into futures resources and spot resources. Allocate futures resources according to priority customers and non-priority customers, and update the daily inventory resource allocation details list; When a customer bill of lading request is received, the inventory resources corresponding to the customer bill of lading request are automatically deducted from the daily inventory resource allocation details list, and the deducted resources are allocated to the customer who needs the bill of lading, and the futures resources are converted into spot resources. Build and publish a futures-spot shared resource pool.
2. The multi-level inventory resource allocation method according to claim 1, characterized in that, The steps of receiving inventory resource information from at least one database to obtain a detailed list of available inventory resources for the day include: Inventory resource information is collected from at least one database, and the data in the inventory resource information is normalized and synchronized with the daily production output in real time; wherein, the inventory resource information includes the inventory balance, daily production output, material occupancy and / or unsold material occupancy. Determine the available quantity and weight of each type of item in the daily inventory; The available weight of each type of cargo is processed for weight accuracy. The processed data is organized into a structured list to form the daily inventory resource allocation details list; the daily inventory resource allocation details list includes fields and descriptions corresponding to each field, wherein the fields include warehouse ID, product name, material, specifications, single piece weight, number of available pieces, available weight, whether it is a special specification and / or data timestamp; the descriptions include the warehouse to which the goods belong, product category name, material code, specification identifier, standard piece weight, number of pieces available for allocation on the day, weight available for allocation on the day and / or data update time.
3. The multi-level inventory resource allocation method according to claim 2, characterized in that, The steps for stratifying the daily inventory of allocable resources into futures and spot resources include: Read the long-term contract ratio and divide the total long-term contract amount from the weight available for allocation on that day according to the long-term contract ratio; The product category is grouped into long-term contract groups based on the total volume of the segmented long-term contracts. For goods marked as having special specifications, they are allocated separately to the long-term contract side according to a preset fixed quantity or fixed proportion; The available long-term contract share for each group, along with the corresponding fields, is organized for long-term contract allocation to form a daily long-term contract shared resource list.
4. The multi-level inventory resource allocation method according to claim 3, characterized in that, The steps of stratifying the daily inventory resource allocation details into futures resources and spot resources also include: The total amount of non-long-term contracts is separated from the weight available for allocation on that day; The total non-long-term contract volume is further divided according to the ratio of futures and spot prices, and then each volume is further divided according to specific fields. Goods are recorded on both the futures and spot sides to obtain futures and spot resources.
5. The multi-level inventory resource allocation method according to claim 4, characterized in that, The steps for allocating futures resources according to priority and non-priority clients and updating the daily list of allocable inventory resources include: Iterate through all futures clients and compare their current undelivered commodity resources with their pre-configured cumulative thresholds. The values are compared, and if the current undelivered amount of goods resources of a futures client is greater than or equal to the cumulative threshold, the futures client is marked as a priority client. All futures clients are sorted according to their current unused resources to form a priority client queue; According to the differentiated allocation logic, each futures client is allocated their corresponding current unused commodity resources. The allocation logic is as follows: Iterate through each client in the priority client queue. If the remaining amount of futures resources is greater than or equal to the current unused commodity resources, the priority client's current futures resource allocation equals the current unused commodity resources, and the remaining amount of futures resources equals the futures resources minus the priority client's current futures resource allocation. If the current unused commodity resources are greater than the remaining amount of futures resources, and the remaining amount of futures resources is greater than 0, the priority client's current futures resource allocation equals the remaining amount of futures resources. If the remaining amount of futures resources is 0 or the priority client's current futures resource allocation is 0, stop iterating. The allocation corresponding to each futures client is deducted from the futures resources; The remaining futures resources will be allocated according to the proportion of unclaimed volume for each non-priority client. Organize the allocation results of futures resources for priority clients and non-priority clients to form a preview list of client futures allocations for the day.
6. The multi-level inventory resource allocation method according to claim 5, characterized in that, The step of allocating futures resources according to priority customers and non-priority customers and updating the daily inventory resource allocation details list further includes: Construct a cargo resource pool for each cargo. Establish a query index for the cargo resource pool; Once the preview list of client futures allocations for the day is confirmed, it will be included in the day's inventory. Detailed list of allocatable resources; Create a daily record of client futures resource allocation for each client, and record the available inventory resources for that day. The allocation details list and the aforementioned goods resources are cached; Add version numbers and update timestamps to cached resources to synchronize metadata; Once the resources are updated, send the information that the goods resources for the day are ready to the customer.
7. The multi-level inventory resource allocation method according to claim 6, characterized in that, When a customer bill of lading request is received, the steps of automatically deducting the corresponding inventory resources from the daily allocable inventory resource list and allocating the deducted resources to the customer requiring the bill of lading include: Upon receiving a customer's bill of lading request, key order parameters are extracted from the customer's bill of lading requirements; The key parameters of the order include customer ID, category, specifications, number of items that can be picked up, and / or weight that can be picked up; Use the product category and date stamp as the lock key to obtain a distributed lock; After acquiring the distributed lock, verify whether the remaining quantity in the daily inventory resource allocation details list is sufficient. The quantity is greater than or equal to the quantity requested in the customer's bill of lading request; if so, continue to check whether the futures resources and / or spot resources in the cargo resources are consistent with the version number in the cache. If so, it means that the double verification has passed and the next step can be executed; if not, it means that the verification has failed. Based on the requested quantity in the customer's bill of lading request, perform the corresponding deduction operation to update the number of used items and the remaining quantity of current goods in the daily inventory resource allocation details list, and update the number of existing futures items and existing spot items that can be allocated in the goods resource pool. Record the deduction operation, check whether all deduction operations were successful. If not, roll back all updates; if yes, release the distributed lock, and send back a success confirmation message and a resource snapshot of the bill of lading. The steps to convert futures resources into spot resources include: The preset futures-spot conversion timing strategy is read according to the category level; the preset futures-spot conversion timing strategy includes the conversion trigger time, whether the long-term contract share can be transferred to the commodity resource pool, and the parameters of the spot order after conversion; Determine whether to transfer long-term contract shares to the commodity resource pool. If so, read the preset futures-spot conversion timing strategy to find that supports the transfer of long-term contract shares to the commodity resource pool, and then collect the unused portion of the long-term contract group. Transfer the unused portion of the long-term contract group to the long-term contract shared resource pool in the goods resource pool, and generate the long-term contract shared resource list for the day; The remaining futures resources in the commodity resources are counted, and the remaining futures resources are converted into spot resources using conversion strategies. The conversion strategies include the spot divisible weight being equal to the divisible weight of the remaining futures resources, the futures divisible weight being equal to 0, and marking the resources converted from futures to spot. For each commodity resource that is transferred from futures to spot, generate a spot order; The steps to build and publish a futures-spot shared resource pool include: The statistics of commodity resources include spot resources, and spot resources, daily long-term contract shared resources, and futures resources converted into spot resources are integrated to build a futures-spot shared resource pool.
8. An electronic device, characterized in that, The electronic device includes: One or more processors; and A memory storing computer program instructions, which, when executed, cause the processor to perform the steps of the multi-level inventory resource allocation method as described in any one of claims 1 to 7.
9. A computer-readable medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the multi-level inventory resource allocation method according to any one of claims 1 to 8.
10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the multi-level inventory resource allocation method according to any one of claims 1 to 8.