Automatic sales order processing method and system, terminal and medium

Abstract

The invention discloses a sales order automatic processing method and system, a terminal and a medium, and the method comprises the steps: obtaining customer demand information, creating a sales order based on the customer demand information, and issuing the sales order to a downstream node after the sales order completes the preliminary examination and approval; monitoring examination and approval feedback information of each downstream node, automatically stopping the sales order when the examination and approval feedback information is abnormal, and continuously issuing the sales order after the abnormality is processed; and when the sales order enters a production scheduling stage, performing full-link monitoring on a production process, and synchronizing a monitoring result to each node. According to the invention, automatic creation, graded examination and approval, full-link monitoring and automatic product scheduling of the sales order can be realized, information of each node can be synchronized in time, manual intervention is reduced, the risk of information leakage is reduced, and automatic management of the sales order is comprehensively realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of order processing, and in particular to a sales order automated processing method, system, terminal and medium. BACKGROUND

[0002] Currently, the processing of sales orders is basically realized based on the manual creation and manual approval mode, such as the generation process of electric meters, which undoubtedly leads to a reduction in efficiency. Moreover, the manual processing mode is difficult to ensure that the information of each node is synchronized in time, is not convenient for overall planning and control, and too much manual intervention will also lead to leakage of confidential information, increasing the risk.

[0003] Therefore, the prior art still has defects. SUMMARY

[0004] The technical problem to be solved by the present application is to provide a sales order automated processing method, system, terminal and medium to solve the above defects of the prior art. In a first aspect, the present application provides a sales order automated processing method, wherein the method comprises: obtaining customer demand information, creating a sales order based on the customer demand information, and issuing the sales order to downstream nodes after the sales order is preliminarily approved; monitoring the approval feedback information of each downstream node, automatically stopping the processing of the sales order when the approval feedback information is abnormal, and continuing to issue the sales order after the abnormality is processed; When the sales order enters the production scheduling stage, the production process is monitored in the whole link, and the monitoring result is synchronized to each node.

[0005] In an implementation mode, obtaining customer demand information and creating a sales order based on the customer demand information comprises: obtaining any one or more of market research data, business signing data and platform ordering data to determine the customer demand information; determining the product type based on the customer demand information, and creating a sales order corresponding to the product type based on the product type.

[0006] In an implementation mode, obtaining customer demand information and creating a sales order based on the customer demand information further comprises: When creating a sales order, all nodes of the sales order and the responsible person of each node are set according to the business flow, and the corresponding access authority of the responsible person of each node is set.

[0007] In an implementation manner, all nodes of the sales order and the person in charge of each node are set according to a business flow, and the method further comprises: a special node is set for the sales order, and a trigger condition of the special node and a person in charge corresponding to the trigger condition are set; if the trigger condition is triggered, the sales order automatically starts the special node, and pushes to the person in charge of the trigger condition, and when the person in charge of the trigger condition processes the sales order, the sales order is automatically distributed to a downstream node.

[0008] In an implementation manner, after the sales order completes preliminary approval, the sales order is distributed to a downstream node, comprising: the customer information, product type, product data, delivery period and delivery quantity in the sales order are approved; the person in charge of each node in the sales order is checked, and after the check is correct, it is determined that the sales order completes preliminary approval, and the sales order is distributed to a downstream node according to a business flow.

[0009] In an implementation manner, when the approval feedback information is abnormal, the sales order is automatically processed to stop, and after the exception is processed, the sales order is continued to be distributed, comprising: when the approval feedback information is abnormal, the type of the exception is determined, and the person in charge of the downstream node is notified; the sales order is processed to stop, and a processing scheme is generated based on the type of the exception; after the exception is processed, the progress information of the sales order is updated, and the sales order is continued to be distributed.

[0010] In an implementation manner, when the sales order enters a production scheduling stage, a production process is monitored in a whole link, comprising: when the sales order enters a production scheduling stage, real-time production progress information, material state information and delivery progress information are acquired; the production progress information, the material state information and the delivery progress information are monitored in real time.

[0011] In a second aspect, the embodiment of the present application further provides a sales order automatic processing system, wherein the system is used to implement the steps of the sales order automatic processing method in any of the above schemes, and the system comprises: an order creation module, configured to acquire customer demand information, create a sales order based on the customer demand information, and distribute the sales order to a downstream node after the sales order completes preliminary approval; The order approval module is used to monitor the approval feedback information of each downstream node. When the approval feedback information is abnormal, the sales order is automatically stopped and processed. After the abnormality is resolved, the sales order is sent out again. The production monitoring module is used to monitor the entire production process after the sales order enters the production scheduling stage, and to synchronize the monitoring results to each node.

[0012] Thirdly, embodiments of the present invention also provide a terminal, wherein the terminal includes a memory, a processor, and a sales order automation processing program stored in the memory and executable on the processor. When the processor executes the sales order automation processing program, it implements the steps of the sales order automation processing method of any of the above solutions.

[0013] Fourthly, embodiments of the present invention also provide a computer-readable storage medium, wherein a sales order automation processing program is stored on the computer-readable storage medium, and the sales order automation processing program implements the steps of the sales order automation processing method described in any one of the above schemes on the computer-readable storage medium.

[0014] Beneficial Effects: Compared with existing technologies, this invention provides an automated sales order processing method. First, customer demand information is acquired, and a sales order is created based on this information. After preliminary approval, the sales order is sent to downstream nodes. Then, the approval feedback information of each downstream node is monitored. If abnormal feedback information is detected, the sales order is automatically halted, and after the abnormality is resolved, the sales order is sent out again. When the sales order enters the production scheduling stage, the entire production process is monitored, and the monitoring results are synchronized to each node. This invention enables automatic creation, hierarchical approval, full-link monitoring, and automatic product scheduling of sales orders. Information from each node can be synchronized in a timely manner, reducing manual intervention, lowering the risk of information leakage, and fully automating sales order management. Attached Figure Description

[0015] Figure 1 A flowchart of a preferred embodiment of the sales order automation processing method provided in this invention.

[0016] Figure 2 This is a schematic diagram of the sales order automated processing system provided in an embodiment of the present invention.

[0017] Figure 3 A schematic diagram of the terminal provided in an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and effects of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0019] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content, operations, or steps, nor does it require execution in the described order. For example, some operations or steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0020] It should be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise. It should be understood that, in order to clearly describe the technical solutions of the embodiments of the present invention, the terms "first" and "second" are used in the embodiments of the present invention to distinguish identical or similar items with essentially the same function and effect. For example, the first control information and the second control information are only used to distinguish different control information and do not limit their order. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or the order of execution, and that the words "first" and "second" do not necessarily imply that they are different. It should also be understood that the terms "and / or" as used in this specification and the appended claims refer to any combination of one or more of the associated listed items and all possible combinations, and include such combinations.

[0021] To address the problems in existing technologies, this embodiment provides an automated sales order processing method. Based on this method, the creation, hierarchical approval, end-to-end monitoring, and automated production scheduling of sales orders can be achieved. In specific application, this embodiment first obtains customer demand information, creates a sales order based on this information, and after the sales order completes preliminary approval, sends it to downstream nodes. Then, it monitors the approval feedback information of each downstream node. If abnormal feedback information is detected, the sales order is automatically halted, and after handling the abnormality, the sales order is sent out again. When the sales order enters the production scheduling stage, the entire production process is monitored, and the monitoring results are synchronized to each node. Based on this embodiment, the automated sales order processing method enables timely synchronization of information across nodes, reduces manual intervention, lowers the risk of information leakage, and fully realizes automated management of sales orders.

[0022] The sales order automation processing method of this embodiment can be applied to a terminal, which can be a smart product terminal such as a computer or mobile phone. Specifically, as shown in the example... Figure 1 As shown in the figure, the sales order automation processing method of this embodiment includes the following steps: Step S100: Obtain customer demand information, create a sales order based on the customer demand information, and after the sales order has completed preliminary approval, send the sales order to the downstream node.

[0023] In this embodiment, the sales order is created by the sales manager, specifically the marketing personnel who sign contracts. The sales order is created based on customer demand information, which reflects the products the customer wants to purchase. Therefore, this embodiment first needs to obtain the customer demand information and then create the sales order based on it. After the sales order is created, it undergoes preliminary approval. If the sales order meets the requirements, it is then sent to downstream nodes. In this embodiment, the downstream nodes are set according to the product's business process. For example, taking the business process of water and electricity meter production as an example, the contract signing personnel create the sales order and then send it to the R&D personnel. The R&D personnel develop the product based on the sales order and then send it to the engineering personnel. The engineering personnel conduct inventory checks on the products in the sales order and organize the raw materials for producing the product. The sales order is then sent to the planning department, where personnel determine the production schedule based on the products in the sales order and then begin production. Therefore, the nodes that the sales order in this embodiment needs to pass through include at least the marketing department, R&D department, engineering department, and planning department. During the production process, it also needs to pass through various process nodes. Therefore, once a sales order meets the requirements, it will be pushed to downstream nodes according to the business process so that the person in charge of the downstream node can process it.

[0024] In practical applications, this embodiment can acquire user demand information from multiple dimensions, such as market research data, business contract data, and platform order data. Market research data refers to market personnel conducting research on market demand to identify products with high market demand, and then creating sales orders for those products. Business contract data consists of business contracts signed between market personnel and customers, which include the products the customers need to purchase; therefore, sales orders can be created based on these products. Platform order data refers to purchase orders placed by customers on e-commerce platforms; sales orders can be created based on the products in these purchase orders. Of course, in specific applications, this embodiment can determine whether a user's purchase order is a repeat order from an existing customer. If it is, the customer's previous sales orders can be retrieved directly from the order database and reused, requiring only updates to certain information (such as the delivery date). This shortens the sales order creation process and improves efficiency.

[0025] Of course, this embodiment can use a modular retrieval approach when creating sales orders. This embodiment can pre-set corresponding order modules based on product types to form an order database. In practical applications, bullet modules can be further created based on customer information, and each order module includes several sub-modules. These sub-modules correspond to various nodes in the business process. For example, sub-modules for the marketing department, R&D department, engineering department, and planning department can be set according to nodes. A corresponding person in charge can be pre-set for each sub-module, and multiple persons in charge can be set for each sub-module, sorted according to permission priority. In this embodiment, all sub-modules in each order module can be retrieved individually. Thus, once the product type is determined, the corresponding sub-module is directly retrieved from the order database to form the current sales order.

[0026] Furthermore, taking the business process of water and electricity meter production as an example, when creating a sales order, this embodiment can further determine the product type based on the customer demand information, and create a sales order corresponding to the product type. In this embodiment, the product type can be product model, product function, or product category, etc. Since the responsible persons for different product types may differ, and the production processes corresponding to different product types in subsequent production stages may also differ, this embodiment needs to create corresponding sales orders for each product type to facilitate end-to-end management. Moreover, when creating a sales order, this embodiment sets all nodes of the sales order and the responsible person for each node according to the business flow, and sets corresponding access permissions for the responsible person of each node. By setting access permissions, it ensures that the responsible person of this node can only access the content of this node, avoiding information leakage. Of course, in practical applications, independent nodes can be set according to the actual situation. The access permissions of this independent node cover all nodes in the entire process. The responsible person of the independent node can not only access all nodes in the entire process, but also create nodes, change the responsible person, and change the information in the sales order. Therefore, the independent node has the highest priority and can monitor the entire cycle of the product from the creation of the sales order to product delivery.

[0027] In the initial approval of sales orders, this embodiment can approve customer information, product type, product data, delivery date, and delivery quantity. The responsible person for each node in the sales order is verified. After verification, the sales order is considered to have completed the initial approval process and is then distributed to downstream nodes according to the business flow. In practical application, if any anomalies are found during the initial approval process, such as an unmet delivery date or incorrect order price, the sales order is rejected and returned to the person who created it for modification before re-entering the initial approval process. In this embodiment, the email address of the responsible person at each node is linked to the sales order. When a sales order reaches any node, a notification is sent to the email address of the responsible person at that node to promptly remind them to process the approval.

[0028] In another implementation, this embodiment can also set special nodes for the sales orders, and set trigger conditions for the special nodes and the responsible persons corresponding to the trigger conditions. If the trigger condition is triggered, the sales order automatically starts the special node and is pushed to the responsible person of the trigger condition. After the responsible person of the trigger condition processes the sales order, the sales order is automatically sent down to downstream nodes. For example, taking the business process of water and electricity meter production as an example, the trigger conditions in this embodiment can be set based on the amount of the sales order. For instance, when the order amount is less than 500,000, the responsible person is the person who signs the order, and no special node needs to be created; when the order amount is between 500,000 and 2,000,000, a special node can be created, and the responsible person of this special node is the sales manager; when the order amount is more than 2,000,000, a special node can be created, and the responsible person of this special node is the general manager. This allows for the creation of different special nodes based on different sales orders, and the responsible persons of the special nodes can approve the sales orders, achieving hierarchical approval of sales orders.

[0029] In addition, regarding access control, this embodiment also employs a dynamic access control mechanism. When the person in charge of a node is on a business trip or leaves the company, a new person in charge can be assigned based on their job level or a pre-set management personnel database, and the new person in charge can be authorized.

[0030] Step S200: Monitor the approval feedback information of each downstream node. When the approval feedback information is abnormal, automatically stop the sales order and continue to issue the sales order after the abnormality is resolved.

[0031] Once a sales order has passed initial review, it can be sent to downstream nodes. At each downstream node, approval feedback is promptly obtained. If any abnormal feedback is detected, such as when the engineering department manager discovers a shortage of raw materials for the product or that the materials do not meet requirements, an error message will be entered in the approval comments section of that node. This error will trigger a halt command, suspending the sales order. The sales order will only be reinstated and sent to downstream nodes after the error has been resolved.

[0032] In practical applications, when abnormal approval feedback information occurs, the system automatically determines the type of abnormality based on the current information and notifies the responsible persons of downstream nodes. The time required to handle the abnormality can then be estimated, and the progress information of the sales order can be adjusted. Simultaneously, the responsible persons of specific nodes can be notified to maintain control over the entire process. Furthermore, this embodiment can generate a handling plan based on the current abnormality type. The responsible person of the current node handles the abnormality based on this plan, and after the abnormality is handled, the progress information of the sales order is updated, and the sales order is reissued.

[0033] Step S300: After the sales order enters the production scheduling stage, the entire production process is monitored, and the monitoring results are synchronized to each node.

[0034] Once a sales order enters the production scheduling stage, production can begin on the ordered products. To achieve end-to-end monitoring, this embodiment can monitor the production status and data of each process and synchronize the monitoring results to each node, so that the person in charge of each node can understand the production status in real time.

[0035] In practical applications, this embodiment can acquire production progress information, material status information, and delivery progress information in real time. Then, it monitors these information in real time. If any of these information becomes abnormal, an anomaly will be promptly output and pushed to the relevant responsible person for handling. Once production is complete, the product is shipped, and the shipping progress is pushed to the order processing personnel in the marketing department.

[0036] In practical applications, production progress information, material status information, and delivery progress information can be synchronized to the ERP (Enterprise Resource Planning) system. Furthermore, this embodiment can synchronize the monitoring results of the entire chain nodes to the computers and mobile terminals of the corresponding responsible persons, so that the responsible persons can obtain the latest information at any time.

[0037] To facilitate end-to-end management of sales orders, this embodiment utilizes digital twin technology to build a full-chain visualization platform for sales orders, transforming abstract data into physical scenarios. Specifically, this full-chain visualization platform can include a supply chain layer, a production layer, and a logistics layer. The supply chain layer can display the real-time procurement progress of core materials used in the production of the product, such as displaying "Sensor Supplier A: Shipped, expected to arrive tomorrow." The production layer can recreate the actual production line scene of the product. For example, it can display the production processes of product B, including: injection molding workshop → mechanism assembly workshop → calibration workshop → intelligent module installation workshop, as well as displaying production data and progress for each process. The logistics layer can connect to the logistics system to display the real-time location of shipped orders and mark logistics risk points. In this embodiment, logistics risk points include weather conditions, traffic conditions, and whether delivery is delayed.

[0038] In other implementations, this embodiment can also set up an order progress query port, such as a mini-program, to provide customers with a dedicated query portal, allowing them to monitor order status in real time and reduce communication costs associated with expediting orders. Of course, when providing the query port to customers, only the progress of the product production stage should be available, and independent query permissions should be set to prevent the leakage of confidential information. If an anomaly occurs during the product production process of a sales order (such as material delays), an anomaly notification will be automatically pushed to the customer, informing them of the delivery delay. For example, a notification might be sent to the customer: "Your order is delayed due to the NB-IoT module; the estimated delivery time has been extended from 10 days to 12 days."

[0039] Meanwhile, to ensure timely product delivery, this embodiment can also conduct a delivery period simulation exercise after the sales order enters the production scheduling stage. This simulation checks whether the products in the sales order can be delivered on time according to the current production schedule. If the simulation result indicates a potential delivery delay, the production schedule is automatically adjusted to ensure timely delivery. Furthermore, this embodiment can also obtain real-time data on the load status of equipment at each process stage during product manufacturing and adjust the production schedule in the sales order based on the load status. This allows idle equipment to be put into production, reducing overloaded equipment. This not only increases capacity and production efficiency but also ensures on-time or even early delivery.

[0040] Furthermore, in other implementations, this embodiment can also collect and summarize anomalies occurring throughout the entire sales order process, categorize them, and summarize the causes of the anomalies. It also further collects the handling solutions for each anomaly, summarizes and maps the summarized anomaly causes and corresponding handling solutions, and forms an optimized solution library. This allows for the rapid retrieval of corresponding solutions when similar or identical anomalies occur during the processing of similar or identical sales orders in the future, improving the efficiency of anomaly handling.

[0041] In summary, this embodiment first obtains customer demand information, creates a sales order based on this information, and then sends the sales order to downstream nodes after initial approval. Next, it monitors the approval feedback information of each downstream node. If any abnormal feedback is detected, the sales order is automatically halted, and then sent out again after the anomaly is resolved. Once the sales order enters the production scheduling stage, the entire production process is monitored, and the monitoring results are synchronized to each node. This embodiment enables automatic creation, hierarchical approval, end-to-end monitoring, and automatic product scheduling of sales orders. Information from each node can be synchronized in a timely manner, reducing manual intervention, lowering the risk of information leakage, and fully automating the management of sales orders.

[0042] Based on the above embodiments, the present invention also provides a sales order automated processing system, which is used to implement the steps of the above method embodiments. Specifically, as Figure 2 As shown in the diagram, the system in this embodiment includes: an order creation module 10, an order approval module 20, and a production monitoring module 30. The order creation module 10 is used to acquire customer demand information, create sales orders based on the customer demand information, and after the sales order completes preliminary approval, send the sales order to downstream nodes. The order approval module 20 is used to monitor the approval feedback information of each downstream node, automatically halt the sales order when the approval feedback information is abnormal, and continue sending the sales order after handling the abnormality. The production monitoring module 30 is used to perform full-link monitoring of the production process after the sales order enters the production scheduling stage, and synchronize the monitoring results to each node.

[0043] In one implementation, the order creation module 10 includes: The information acquisition unit is used to acquire one or more of market research data, business contract data, and platform order data to determine the customer demand information. The order creation unit is used to determine the product type based on the customer demand information, and to create a sales order corresponding to the product type.

[0044] In one implementation, the order creation module 10 further includes: The permission setting unit is used to set all nodes of the sales order and the person in charge of each node according to the business flow when creating a sales order, and to set the corresponding access permissions for the person in charge of each node.

[0045] In one implementation, the permission setting unit further includes: The special node determination subunit is used to set special nodes for the sales order, and to set the trigger conditions for the special node and the person in charge corresponding to the trigger conditions; A special node processing subunit is used to automatically start a special node for the sales order when the triggering condition is triggered, and push it to the person in charge of the triggering condition. After the person in charge of the triggering condition finishes processing the sales order, the sales order is automatically sent to the downstream node.

[0046] In one implementation, the order creation module 10 includes: The information approval unit is used to approve the customer information, product type, product data, delivery date, and delivery quantity in the sales order. The order issuance unit is used to verify the person in charge of each node in the sales order. After verification, it determines that the sales order has completed the preliminary approval and issues the sales order to the downstream node according to the business flow.

[0047] In one implementation, the order approval module 20 includes: The anomaly analysis unit is used to determine the anomaly type when the approval feedback information is abnormal, and to notify the person in charge of the downstream node. The solution determination unit is used to stop the sales order and generate a processing solution based on the exception type; The progress update unit is used to update the progress information of the sales order after the exception is handled, and to continue to issue the sales order.

[0048] In one implementation, the production monitoring module 30 includes: The real-time information acquisition unit is used to acquire production progress information, material status information, and delivery progress information in real time after the sales order enters the production scheduling stage. The real-time information monitoring unit is used to monitor the production progress information, the material status information, and the delivery progress information in real time.

[0049] The working principle of each functional module in the system embodiment of this example is the same as that of each step in the above-described automated sales order processing method, and will not be repeated here.

[0050] Each module in the aforementioned automated sales order processing system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the terminal in hardware form or independent of it, or stored in the terminal's memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0051] Based on the above embodiments, the present invention also provides a terminal, the principle block diagram of which can be as follows: Figure 3 As shown. The terminal may include one or more processors 100 ( Figure 3 (Only one is shown in the image), memory 101, and computer program 102 stored in memory 101 and executable on one or more processors 100. For example, a sales order automation processing program. When one or more processors 100 execute computer program 102, they can implement the various steps in the sales order automation processing method embodiment. Alternatively, when one or more processors 100 execute computer program 102, they can implement the functions of various modules / units in the sales order automation processing system embodiment, without limitation here.

[0052] In one embodiment, the processor 100 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0053] In one embodiment, memory 101 may be an internal storage unit of an electronic device, such as a hard drive or RAM. Memory 101 may also be an external storage device of the electronic device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc. Furthermore, memory 101 may include both internal and external storage units. Memory 101 is used to store computer programs and other programs and data required by the terminal. Memory 101 can also be used to temporarily store data that has been output or will be output.

[0054] Those skilled in the art will understand that Figure 3 The block diagram shown is merely a partial structural diagram related to the present invention and does not constitute a limitation on the terminal to which the present invention is applied. A specific terminal may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0055] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, operational databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual operating data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0056] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for automating sales order processing, characterized in that, The method includes: Obtain customer demand information, create a sales order based on the customer demand information, and after the sales order has completed preliminary approval, issue the sales order to the downstream nodes; Monitor the approval feedback information of each downstream node. When the approval feedback information is abnormal, automatically stop the sales order and continue to send the sales order after the abnormality is resolved. Once the sales order enters the production scheduling stage, the entire production process is monitored, and the monitoring results are synchronized to each node.

2. The automated sales order processing method according to claim 1, characterized in that, Obtaining customer demand information and creating a sales order based on the customer demand information includes: Obtain one or more of the following: market research data, business contract data, and platform order data, to determine the customer demand information; Based on the customer demand information, the product type is determined, and a sales order corresponding to the product type is created.

3. The automated sales order processing method according to claim 1, characterized in that, Obtaining customer demand information and creating a sales order based on the customer demand information also includes: When creating a sales order, set all nodes of the sales order and the person in charge of each node according to the business flow, and set the corresponding access permissions for the person in charge of each node.

4. The automated sales order processing method according to claim 3, characterized in that, The sales order is configured according to the business flow, including all nodes and the person in charge of each node, and also includes: Set a special node for the sales order, and set the trigger conditions for the special node and the person in charge corresponding to the trigger conditions; If the triggering condition is triggered, the sales order will automatically start a special node and be pushed to the person in charge of the triggering condition. After the person in charge of the triggering condition has processed the sales order, the sales order will be automatically sent to the downstream node.

5. The automated sales order processing method according to claim 3, characterized in that, After the sales order has completed its initial approval, the sales order is sent to downstream nodes, including: Approving the customer information, product type, product data, delivery date, and delivery quantity in the sales order; Verify the person in charge of each node in the sales order. After confirming that the verification is correct, determine that the sales order has completed the initial approval and issue the sales order to the downstream node according to the business flow.

6. The automated sales order processing method according to claim 1, characterized in that, When the approval feedback information is abnormal, the sales order is automatically stopped, and after the abnormality is resolved, the sales order is reissued, including: When the approval feedback information is abnormal, determine the type of abnormality and notify the person in charge of the downstream node; The sales order is stopped, and a processing plan is generated based on the exception type; After the exception is handled, the progress information of the sales order is updated, and the sales order is reissued.

7. The automated sales order processing method according to claim 1, characterized in that, Once the sales order enters the production scheduling stage, the entire production process is monitored, including: Once the sales order enters the production scheduling stage, real-time production progress information, material status information, and delivery progress information are obtained. The production progress information, the material status information, and the delivery progress information are monitored in real time.

8. A sales order automated processing system, characterized in that, The system is used to implement the steps of the sales order automated processing method according to any one of claims 1-7, and the system includes: The order creation module is used to obtain customer demand information, create sales orders based on the customer demand information, and send the sales orders to downstream nodes after the sales orders have completed preliminary approval. The order approval module is used to monitor the approval feedback information of each downstream node. When the approval feedback information is abnormal, the sales order is automatically stopped and processed. After the abnormality is resolved, the sales order is sent out again. The production monitoring module is used to monitor the entire production process after the sales order enters the production scheduling stage, and to synchronize the monitoring results to each node.

9. A terminal, characterized in that, The terminal includes a memory, a processor, and a sales order automation processing program stored in the memory and executable on the processor. When the processor executes the sales order automation processing program, it implements the steps of the sales order automation processing method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a sales order automation processing program, which implements the steps of the sales order automation processing method as described in any one of claims 1-7 on the computer-readable storage medium.

Images