A permission-based approval control and sale commodity directional sharing system and method

Abstract

The present application belongs to the technical field of supply chain management, and particularly relates to a control and sale commodity directional sharing system and method based on permission approval, wherein the method comprises the following steps: S1: in response to a list creation request of a business, obtaining business identity information, target customer information and candidate commodity information; S2: calling a pre-set permission verification engine, and performing pre-position permission verification on the combination of the business, the target customer and the candidate commodity based on a multi-dimensional permission data model; S3: if the verification is passed, the business is allowed to build a sharing list for the target customer from the commodities within the permission range, and a list snapshot ID bound to the list is generated; S4: the built sharing list is submitted to a pre-set approval process; S5: a time-limited sharing link or a two-dimensional code is generated based on the list snapshot ID; and S6: in response to an access request of the target customer through the sharing link or the two-dimensional code.

Description

Technical Field

[0001] This invention belongs to the field of supply chain management technology, and more specifically, relates to a system and method for targeted sharing of controlled-sales goods based on permission approval. Background Technology

[0002] With the deepening development of e-commerce and digital marketing, traditional commodity sales models are gradually shifting online. Especially in highly regulated industries such as pharmaceuticals and high-value equipment, controlled sales models have emerged to maintain market order, prevent cross-selling, and protect the price system.

[0003] Currently, digital management in the controlled sales field mainly relies on two methods: one is the traditional offline model, where salespeople promote products to customers through paper catalogs or spreadsheets, and the approval process relies on manual methods such as telephone and email, which is inefficient and prone to errors; the other is to use standardized ERP or CRM systems. Although such systems have achieved digital order management, their core functions revolve around "order processing" and lack an independent "shared list" concept and corresponding pre-approval mechanism.

[0004] In existing technologies, such as patent publication number CN117252608B, a commodity distribution platform system is proposed. Although this system involves the management of suppliers, physical stores, and distributors, and introduces verification of the customer's business scope, the verification process occurs at the time of order placement, which is a post-event control. Another example is patent publication number CN112381622B, which discloses a big data-based sharing economy service platform that uses a referral bar to achieve multi-level discount sharing; however, its focus is on marketing and promotion, and it does not involve fine-grained control over the permissions of the sharing entities.

[0005] In summary, the existing technology has the following core flaws:

[0006] First, the approval process mainly works after an order is generated, and it cannot effectively control the sharing process before product information reaches customers, which makes it impossible to eliminate the risk of cross-selling at the source.

[0007] Secondly, from product display, list creation, approval, order placement to logistics tracking, it often requires switching between multiple systems or relying on manual information transmission, resulting in disjointed processes, low efficiency, and data errors.

[0008] Finally, existing permission verification is mostly static and coarse-grained, which cannot achieve dynamic and refined binding of the relationship between salespersons, products and customers, making it difficult to adapt to flexible and ever-changing sales control business scenarios.

[0009] Therefore, in view of this, we will study and improve the existing structure and its shortcomings, and provide a system and method for targeted sharing of controlled products based on permission approval, in order to achieve a more practical value. Summary of the Invention

[0010] In view of the problems mentioned in the background art above, the present invention provides a system and method for targeted sharing of controlled sales products based on permission approval.

[0011] Firstly, the technical solution adopted by this invention is as follows: a sales control and targeted sharing system for goods based on permission approval, comprising a permission verification engine configured to dynamically perform pre-verification of permissions on the salesperson, the specific customer, and the selected goods based on a predefined multi-dimensional permission data model before the salesperson creates a goods list for a specific customer; the multi-dimensional permission data model includes at least the salesperson's sales control scope, the goods' business scope, and the customer's qualification scope; and a sharing list management module configured to, in response to the pass result of the permission verification engine, allow the salesperson to construct a sharing list containing selected goods, quantities, and promotional information, and generate a sharing list with the specified goods. The shared list has a unique corresponding list snapshot ID, which is used to solidify the product prices and activity rules at the time of list creation; the approval workflow module is configured to submit the completed shared list to a preset approval node and write back the approval status; the link generation module is configured to generate a time-sensitive sharing link or QR code containing the list snapshot ID after approval; the customer interaction module is configured to provide an integrated client page. When a customer accesses the page through the link, the system retrieves the solidified list information based on the list snapshot ID and completes the integrated operation of list confirmation, order payment, and logistics tracking within the page.

[0012] Furthermore, the permission verification engine incorporates a verification interceptor based on a three-dimensional dynamic model of the salesperson, product, and customer. The verification interceptors are ordered by weight from low to high as follows: a filter based on the salesperson's team rules, a filter based on the salesperson's personal sales control scope, a filter based on the product's sales area and customer type, and a filter based on the customer's real-time qualifications. The permission verification engine assigns a preset score to each filter layer and adopts a veto system, determining that the permission verification is passed only when all levels of verification meet the standards.

[0013] Furthermore, the multi-dimensional permission data model includes at least the following seven data structures: the product groups and product lists that the salesperson's team can sell; the product and customer information locked by the salesperson; the product business scope; the customer business scope; the sales region and customer type; the sales scope controlled by the salesperson personally; the sales scope controlled by the salesperson's team; the permission verification engine determines the final range of products that the salesperson can sell for a specific customer by calculating the intersection of the above multiple data structures.

[0014] Furthermore, the data structure of the product and customer information locked by the salesperson includes at least the salesperson ID, locked product identifier, locked customer identifier, lock effective time, and lock duration; starting from the lock effective time, after the preset lock duration is reached, the lock relationship between the salesperson and the product and customer is automatically released.

[0015] Furthermore, the generation rule for the list snapshot ID is: based on a composite encoding of timestamp, salesperson ID, and customer ID; the list product information and its real-time snapshot include at least the product ID, main product ID of the activity, activity type, final selling price, product quantity, and gift information.

[0016] Furthermore, the shared link or QR code has a preset validity period, which expires automatically; the list information displayed on the client page is locked based on the list snapshot ID, prohibiting customers or salespersons from modifying it online.

[0017] Furthermore, it also includes an order traceability module, which is configured to associate and store the generated order data with the list snapshot ID after the customer places an order, so as to realize full-link data traceability from permission verification, list creation, approval, order placement to fulfillment.

[0018] Secondly, the technical solution adopted by the present invention is as follows: a method for targeted sharing of controlled-sales products based on permission approval, comprising the following steps: S1: In response to a salesperson's list creation request, obtain the salesperson's identity information, target customer information, and candidate product information; S2: Call a preset permission verification engine, and perform pre-permission verification on the combination of the salesperson, target customer, and candidate products based on a multi-dimensional permission data model; S3: If the verification passes, allow the salesperson to build a sharing list for the target customer from products within the permission scope, and generate a list snapshot ID bound to the list; S4: Submit the built sharing list to a preset approval process; S5: After approval, generate a time-sensitive sharing link or QR code based on the list snapshot ID, and provide it to the target customer; S6: In response to the target customer's access request via the sharing link or QR code, parse the list snapshot ID, retrieve the solidified list product information, and display it on the integrated client page for the customer to complete order payment and logistics tracking.

[0019] Furthermore, the pre-permission verification in step S2 specifically includes: S21: performing a first layer of filtering based on the salesperson team rules; S22: performing a second layer of filtering based on the salesperson's personal sales control scope and the product and customer information locked by the salesperson; S23: performing a third layer of filtering based on the product sales area and customer type; S24: performing a fourth layer of filtering based on the customer's real-time qualifications; S25: performing a weighted score on the combination of the above four layers of filtering, adopting a veto system, and only when all levels of verification meet the standards is the verification deemed passed.

[0020] Thirdly, the technical solution of the present invention is as follows: a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a method for targeted sharing of controlled sales products based on permission approval.

[0021] The beneficial effects of this invention are:

[0022] 1. This invention moves the control node from traditional order approval to information sharing approval. Access control and compliance verification are completed before product information reaches customers, cutting off the possibility of illegal sharing and sales at the source and fundamentally eliminating the risk of cross-selling.

[0023] 2. By constructing a 3D model of salespersons, products, and customers, and integrating seven types of core data structures, combined with a four-layer weight verification and weighted scoring algorithm, we have achieved accurate and dynamic calculation of sales permissions in complex sales control scenarios, solving the problems of incomplete dimensions and rigid logic in existing technology for permission verification.

[0024] 3. By introducing shared list snapshot IDs, the pre-authorization verification records, list content, approval status, and subsequent order data are connected, forming a complete and tamper-proof data chain. This not only ensures the traceability and consistency of list content but also provides solid data support for business auditing and problem investigation.

[0025] 4. The system achieves full-process digital integration from sharing and approval to customer order placement. Automated qualification verification and intelligent approval routing significantly reduce manual intervention and communication costs, and shorten the cycle from business opportunity to transaction.

[0026] 5. By deeply integrating customer qualifications with the product sharing process, the system can automatically and enforce compliance checks, providing a solid technical guarantee for enterprises' compliant operation in highly regulated fields such as pharmaceuticals. Attached Figure Description

[0027] The present invention can be further illustrated by the non-limiting embodiments given in the accompanying drawings;

[0028] Figure 1 This is a structural block diagram of the controlled sales product targeted sharing system based on permission approval in Embodiment 1 of the present invention;

[0029] Figure 2 This is a flowchart illustrating the steps of the controlled sales product targeted sharing method based on permission approval in Embodiment 2 of the present invention;

[0030] Figure 3 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present invention. Detailed Implementation

[0031] Example 1:

[0032] like Figure 1 As shown, a sales control product targeted sharing system based on permission approval includes a permission verification engine, a sharing list management module, an approval workflow module, a link generation module, a customer interaction module, and an optional order traceability module.

[0033] First, the permission verification engine is configured to perform dynamic pre-verification of permissions for the salesperson, the specific customer, and the products to be selected based on a predefined multi-dimensional permission data model before the salesperson creates a product list for a specific customer. The multi-dimensional permission data model includes at least the salesperson's sales control scope, the product business scope, and the customer's qualification scope.

[0034] The permission verification engine is one of the core modules of this invention. Its permission data model includes at least the following seven data structures, which are stored in the system database and organized through association relationships:

[0035] Table 1: Contents of Seven Types of Data Structures

[0036] Data Structure Number Data structure name Includes dimensions DS-01 Product groups and product lists that a salesperson's team can sell. Team ID, Product Group ID, Product ID, Authorization Effective Date, Authorization Expiration Date DS-02 Product and customer information locked by salesperson Salesperson ID, Locked Product ID, Locked Customer ID, Locking Strategy ID, Locking Effective Time, Locking Duration, Associated Order Number DS-03 Business scope of goods Product ID, List of Applicable Regions, List of Applicable Customer Types, List of Required Qualifications DS-04 Customer business scope Customer ID, Region, Customer Type, List of Uploaded Qualifications, Qualification Validity Period DS-05 Product sales regions and customer types Product ID, List of Permitted Sales Regions, List of Permitted Sales Customer Types, List Identifier DS-06 Salesperson's Personal Sales Control Scope Salesperson ID, list of sellable customer types, list of sellable regions, customer list DS-07 Sales team sales control scope Team ID, List of Sellable Customer Types, List of Sellable Regions, Customer List

[0037] The permission verification engine determines the final range of salable products for a specific customer by calculating the intersection of the above data structures. The specific algorithm is as follows:

[0038] Based on DS-06 and DS-07, the union of the salesperson's individual scope and the scope of their team is taken as the overall effective scope R1 of the salesperson; then, based on DS-03 and DS-05, the sales restrictions of the product in terms of region and customer type are determined, resulting in the effective applicable scope R2 of the product; then, based on DS-04, the effective scope R3 of the customer in terms of qualification and region is determined; finally, R = R1 ∩ R2 ∩ R3 is calculated, and R is the set of products that the salesperson can sell to the customer.

[0039] The permission verification engine includes a built-in verification interceptor based on a 3D dynamic model of the salesperson, product, and customer. The verification interceptors are listed in order of weight from lowest to highest:

[0040] The first layer: a filter based on the sales team rules. It first uses DS-01 and DS-07 to remove products that do not meet the team's common control requirements. For example, if a product is not on the team's authorized sales list, it will be directly blocked.

[0041] The second layer is a filter based on the salesperson's personal sales control scope. Building upon the first layer, and based on DS-02 and DS-06, it further narrows the scope, retaining only the salesperson's personally authorized products and products currently under lock-in validity.

[0042] The third layer: Filters based on product sales region and customer type. Building upon the second layer, and using DS-03 and DS-05, this layer verifies whether the candidate product matches the target customer's region and customer type. For example, if a certain drug is only sold through hospital channels, and the current customer is a pharmacy, this layer's verification will fail.

[0043] The fourth layer: a filter based on the customer's real-time qualifications. Building upon the first three layers, this layer uses DS-04 to verify whether the customer possesses the real-time qualifications required to purchase the product. For example, if the customer has not uploaded a Class II medical device business registration certificate, then sharing Class II medical device products with them is prohibited.

[0044] The permission verification engine assigns a preset score to each filter level, such as 25 points per level, for a total of 100 points. However, it employs a veto system, meaning that permission verification is only considered successful if all levels of verification meet the criteria; if any level fails, the verification process terminates and returns a failure message. This design ensures the rigor of permission verification and meets the zero-tolerance control requirements of the sales control business.

[0045] Second, the shared list management module is configured to respond to the pass result of the permission verification engine, allowing salespersons to build a shared list containing selected products, quantities and promotional information, and generate a list snapshot ID that uniquely corresponds to the shared list. The list snapshot ID is used to solidify the product price and activity rules at the time of list creation.

[0046] The generation rule for the inventory snapshot ID is as follows: it is based on a composite encoding of the timestamp, salesperson ID, and customer ID. For example, it can be in the following format: {timestamp}_{8-bit salesperson ID hash}_{6-bit customer ID hash}, such as 20240321143025_A3B7F92C_1D4E6F.

[0047] The core function of this ID is to solidify the product prices and promotional rules at the moment the list is created. Specifically, when a salesperson builds a list, the shared list management module records the current base price of the product, participating promotions such as discounts, coupons, and gifts, and a snapshot of the promotional rules, and stores this information bound to the list snapshot ID. List product information and its real-time snapshot must include at least the following fields:

[0048] Table 2: Fields and their descriptions

[0049] field name illustrate snapshot_id List snapshot ID, primary key sku_id Product SKU ID activity_id Main product ID for the event (if participating in the event) activity_type Activity type (e.g., 0 - no activity, 1 - discount for purchases over a certain amount, 2 - discount, 3 - buy-one-get-one-free) final_price Final selling price (price after calculation for the promotion) quantity Quantity of goods gift_sku_id Gift SKU ID gift_quantity Number of free gifts create_time List creation timestamp

[0050] Third, the approval workflow module is configured to submit the completed sharing list to the preset approval node and write back the review status.

[0051] Specifically, after the salesperson completes the list construction and clicks submit for review, the approval workflow module creates an approval task and pushes it to the corresponding superior administrator according to the preset approval routing rules, such as by amount, by product category, or by customer level.

[0052] The approver can view the list details in the approval center, including product details, prices, customer information, and permission verification records, and make a decision to approve or reject the application.

[0053] The approval workflow module writes the review status, such as pending review, approved, or rejected, back to the shared list data table in real time, so that business personnel can view the review progress in real time on the front end.

[0054] Fourth, the link generation module is configured to generate a time-sensitive shareable link or QR code containing the snapshot ID of the list after approval.

[0055] Specifically, the link generation module receives the approval notification and obtains the manifest snapshot ID. It then generates a unique external link address, for example: https: / / mall.xxx.com / share?id={manifest snapshot ID}&expire={expiration timestamp}, where the expiration timestamp is calculated based on a preset validity period, such as 72 hours.

[0056] It also supports generating QR code images containing the same information, making it convenient for sales staff to share in face-to-face scenarios. The generated links or QR codes have a preset validity period, which automatically expires, and the client will be prompted with "Link has expired" when accessing them, thus enhancing security.

[0057] Fifth, the customer interaction module is configured to provide an integrated client page, such as an H5 page or a mini-program page. When a customer accesses the page through a link or QR code shared by a salesperson, the system first parses the list snapshot ID and expiration timestamp in the link: if the current time exceeds the expiration timestamp, the system returns an expired page; if the link is valid, the system retrieves the solidified list information from the database based on the list snapshot ID, including product name, specifications, solidified price, and gift information.

[0058] Customers can complete the process within a single integrated page:

[0059] List Confirmation: Review the product details, quantity, price, and free gifts. Once you confirm everything is correct, click "Place Order".

[0060] Order placement and payment: Fill in the shipping address, invoice information, etc., submit the order and complete the online payment;

[0061] Logistics tracking: After payment, the page will automatically redirect to the order details page, where you can check the logistics status in real time.

[0062] Sixth, the order traceability module is configured to associate and store the generated order data with the manifest snapshot ID after a customer places an order. Specifically, a `snapshot_id` field is added to the main order table to record the manifest snapshot ID that generated the order. This achieves end-to-end data traceability from permission verification, manifest creation, approval, order placement to fulfillment. Operations or auditing personnel can use the manifest snapshot ID to query all associated order information, approval records, permission verification logs, etc., with a single click, greatly improving data governance capabilities.

[0063] It's important to note that the list information displayed on the client-side page is locked based on the list snapshot ID, preventing customers or sales representatives from modifying it online. If modifications are needed, the sales representative must recreate the list and submit it for approval, ensuring the seriousness and traceability of the transaction.

[0064] Example 2:

[0065] This embodiment provides a method for targeted sharing of controlled-sale products based on permission approval, applied to the system of Embodiment 1, and includes the following steps:

[0066] Step S1: In response to the salesperson's list creation request, the system obtains the salesperson's identity information (salesperson ID), target customer information (customer ID), and candidate product information (list of product SKU IDs). This information can be obtained through the request message submitted by the salesperson after selecting customers and products on the front-end page.

[0067] Step S2: Invoke the pre-built permission verification engine and, based on the multi-dimensional permission data model, perform pre-verification of permissions for the combination of salesperson, target customer, and candidate products. This step further includes:

[0068] S21: First-level filtering based on sales team rules;

[0069] S22: A second layer of filtering is performed based on the salesperson's personal sales control scope and the product and customer information locked by the salesperson;

[0070] S23: Third-level filtering based on product sales region and customer type;

[0071] S24: Fourth-level filtering based on real-time customer qualifications;

[0072] S25: The combination that passes the above four layers of filtering is weighted and scored. A veto system is adopted. The verification is deemed to have passed only when all levels of verification meet the standards.

[0073] Step S3: If the verification in Step S2 passes, the salesperson is allowed to build a sharing list for the target customer from the products within their authorized scope. The salesperson can adjust the product quantity and select promotional activities. After the salesperson submits the list, the system generates a list snapshot ID according to the rule {timestamp}_{salesperson ID hash}_{customer ID hash}, and binds and stores the current product price, activity rule snapshot, and list snapshot ID together.

[0074] Step S4: Submit the completed sharing list to the preset approval process. The approval workflow module creates an approval task and pushes it to the corresponding approver. The system waits for the approval result.

[0075] Step S5: After approval, the system receives a notification and generates a time-sensitive shareable link or QR code based on the list snapshot ID. The link embeds an expiration timestamp, the expiration time of which can be configured according to business rules.

[0076] Step S6: Target customers access the system via a shared link or QR code. The system parses the link and verifies its validity. If the link is valid, it retrieves the fixed list product information based on the list snapshot ID. Customers complete the integrated operation of list confirmation, order payment, and logistics tracking within the integrated client page.

[0077] Example 3: Application Scenarios in the Pharmaceutical Industry

[0078] To more clearly illustrate the technical effects of this invention, a specific application scenario in the pharmaceutical industry will be used as an example.

[0079] Scenario: Xiao Wang, a sales representative for a pharmaceutical company, is responsible for promoting a controlled-sale drug, X, to chain pharmacies (referred to as Client A) and independent pharmacies (referred to as Client B) within a certain region. Drug X is a prescription drug and can only be sold to pharmacies with a "Drug Business License." Company regulations stipulate that Xiao Wang is the only authorized seller of this drug in region A, and in region B, it can only be sold to chain pharmacies; sales to independent pharmacies are prohibited.

[0080] Traditional approach: Xiao Wang needs to first confirm whether Customer A and Customer B are qualified, and then send the drug information to the pharmacy's purchasing agent via phone or WeChat; if the purchasing agent is interested, Xiao Wang needs to return to the company to fill out a paper or electronic approval form and wait for approval from superiors; after approval, Xiao Wang sends the price information to the purchasing agent, who then logs into the company's ERP system to place the order. During this process, if the drug price changes or the customer's qualification is about to expire, disputes are very likely to arise.

[0081] In this invention, due to the pre-configuration of permissions, the system administrator configures a multi-dimensional permission data model in the background: DS-06, Xiao Wang's personal sales control scope: Customer A is not on the list, Customer B is on the list for drug X; DS-07, Xiao Wang's team's sales control scope: Authorized to sell drug X in region A; DS-03, Drug X's business scope, applicable regions: region A and region B; applicable customer types: chain pharmacies and independent pharmacies; required qualification: "Drug Business License"; DS-04, Customer A's qualification: Uploaded valid "Drug Business License"; Customer B's qualification: Not uploaded or expired.

[0082] Therefore, during the list creation and verification process, Xiao Wang selects customer A in the system and attempts to add medicine X. The permission verification engine initiates four layers of verification: team rules approved, personal scope approved, product area approved, and customer qualifications approved. Upon successful verification, Xiao Wang can create a list containing medicine X for customer A; the price and promotional activities are fixed, and a list snapshot ID is generated.

[0083] When Xiao Wang tried to create a list for customer B, the permission verification engine started the verification: if the team rules passed but the personal rules failed, the verification was rejected and the system prompted Xiao Wang that he did not have the right to sell medicine X to this customer.

[0084] In the above case, after Xiao Wang submitted the list he created for customer A, his supervisor quickly approved it on his mobile phone. The system automatically generated a shareable link valid for 72 hours, which Xiao Wang sent to the pharmacy's purchasing agent via WeChat. At this point, the customer could place an order by having the purchasing agent click the link to access an integrated H5 page. The page clearly displayed the name, specifications, fixed price, and free gift information for drug X. After confirming that everything was correct, the purchasing agent filled in the shipping address and made the online payment. The system automatically associated the order with the list snapshot ID.

[0085] Furthermore, this invention enables end-to-end traceability. Three months later, auditors can trace this transaction. By reverse-engineering the order number to find the list snapshot ID, they can clearly see: the complete log of Xiao Wang's permission verification when the list was created, the approval records at that time, and the fixed product price snapshot. Even if the price of drug X has increased during this period, it will not affect the traceability of this historical transaction.

[0086] As can be seen from the above scenarios, this invention effectively achieves the significant effects of pre-emptive interception, prohibition of sharing with unqualified customers, precise control, authorization based on customer type, process efficiency improvement, full online process and data traceability, and snapshot ID throughout the entire process in the pharmaceutical sales control scenario.

[0087] Appendix Figure 3 A schematic diagram of a computer system suitable for implementing the embodiments of this application is shown. It should be noted that... Figure 3The computer system of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0088] As attached Figure 3 As shown, the computer system includes a central processing unit (CPU), which can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) or a program loaded from storage into random access memory (RAM), such as executing the methods described in the above embodiments. The RAM also stores various programs and data required for system operation. The CPU, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0089] The following components are connected to the I / O interface: input sections including keyboards, mice, etc.; output sections including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage sections including hard drives; and communication sections including network interface cards such as LAN (local area network) cards and modems. The communication sections perform communication processing via networks such as the Internet. Drives are also connected to the I / O interface as needed. Removable media, such as disks, optical discs, magneto-optical discs, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage section as required.

[0090] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit (CPU), it performs various functions defined in the system of this application.

[0091] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer's processor, causes the computer to perform the rule engine configuration method for early warning as described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0092] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, system, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, system, or device. Computer programs contained on computer-readable media can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0093] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains 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 a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0094] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0095] The present invention has been described in detail above. The specific embodiments are provided only to help understand the method and core ideas of the present invention. It should be noted that those skilled in the art can make various improvements and modifications to the present invention without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims

1. A system for targeted sharing of controlled-sale products based on access control and approval, characterized in that: include The permission verification engine is configured to perform dynamic pre-permission verification on the salesperson, the specific customer, and the products to be selected based on a predefined multi-dimensional permission data model before the salesperson creates a product list for a specific customer. The multi-dimensional permission data model includes at least the sales scope controlled by the salesperson, the scope of product operation, and the scope of customer qualifications. The shared list management module is configured to respond to the pass result of the permission verification engine, allowing salespersons to build a shared list containing selected products, quantities and promotional information, and generate a list snapshot ID that uniquely corresponds to the shared list. The list snapshot ID is used to solidify the product price and activity rules at the time of list creation. The approval workflow module is configured to submit the completed sharing list to the preset approval node and write back the approval status. The link generation module is configured to generate a time-sensitive shareable link or QR code containing the snapshot ID of the list after approval. The customer interaction module is configured to provide an integrated client page. When a customer accesses the page through the link, the system retrieves the solidified list information based on the list snapshot ID and completes the integrated operation of list confirmation, order payment and logistics tracking within the page.

2. The controlled-sales product targeted sharing system based on permission approval according to claim 1, characterized in that: The permission verification engine has a built-in verification interceptor based on a three-dimensional dynamic model of the salesperson, product, and customer. The verification interceptors, ranked from lowest to highest weight, are: a filter based on sales team rules, a filter based on the salesperson's individual sales control scope, a filter based on product sales area and customer type, and a filter based on real-time customer qualifications. The permission verification engine assigns a preset score to each layer of filters and adopts a veto system, determining that the permission verification is passed only when all layers of verification meet the standard.

3. The controlled-sales product targeted sharing system based on permission approval according to claim 2, characterized in that: The multi-dimensional permission data model includes at least the following seven data structures: the product groups and product lists that the salesperson's team can sell; the product and customer information locked by the salesperson; the product business scope; the customer business scope; the sales region and customer type; the sales scope controlled by the individual salesperson; and the sales scope controlled by the salesperson's team. The permission verification engine determines the final range of salable products for a specific customer by calculating the intersection of the above-mentioned multiple data structures.

4. A controlled-sales product targeted sharing system based on permission approval according to claim 3, characterized in that: The data structure for the products and customer information locked by the salesperson must include at least the salesperson ID, locked product identifier, locked customer identifier, lock effective time, and lock duration; The lock relationship between the salesperson and the product / customer will be automatically released after the preset lock duration begins.

5. A controlled sales product targeted sharing system based on permission approval according to claim 1, characterized in that: The rule for generating the list snapshot ID is: a composite encoding based on timestamp, salesperson ID, and customer ID; The product information in the list and its real-time snapshot include at least the product ID, main product ID of the event, event type, final price, product quantity, and gift information.

6. A controlled-sales product targeted sharing system based on permission approval according to claim 1, characterized in that: The shared link or QR code has a preset validity period and will automatically expire after that; the list information displayed on the client page is locked based on the list snapshot ID, prohibiting customers or salespersons from modifying it online.

7. A controlled-sales product targeted sharing system based on permission approval according to claim 1, characterized in that: It also includes an order traceability module, which is configured to associate and store the generated order data with the list snapshot ID after the customer places an order, so as to realize full-link data traceability from permission verification, list creation, approval, order placement to fulfillment.

8. A method for targeted sharing of controlled-sale products based on permission approval, characterized in that: Includes the following steps: S1: In response to the salesperson's list creation request, obtain the salesperson's identity information, target customer information, and product information to be selected; S2: Call the pre-set permission verification engine and perform pre-permission verification on the combination of salesperson, target customer and candidate product based on the multi-dimensional permission data model; S3: If the verification passes, the salesperson is allowed to build a sharing list for the target customer from the products within the scope of authorization, and generate a list snapshot ID bound to the list; S4: Submit the prepared sharing list to the preset approval process; S5: After approval, generate a time-sensitive sharing link or QR code based on the list snapshot ID and provide it to the target customer; S6: In response to access requests from target customers via shared links or QR codes, parse the list snapshot ID, retrieve the solidified list product information, and display it on the integrated client page so that customers can complete order placement, payment, and logistics tracking.

9. A method for targeted sharing of controlled-sale products based on permission approval according to claim 8, characterized in that: The pre-access permission verification in step S2 specifically includes: S21: First-level filtering based on sales team rules; S22: A second layer of filtering is performed based on the salesperson's personal sales control scope and the product and customer information locked by the salesperson; S23: Third-level filtering based on product sales region and customer type; S24: Fourth-level filtering based on real-time customer qualifications; S25: The combination that passes the above four layers of filtering is weighted and scored. A veto system is adopted. The verification is deemed to have passed only when all levels of verification meet the standards.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in claim 8 or 9.

Images