A method of detecting service management

Abstract

The application relates to the technical field of computer software, in particular to a detection business management method. The detection business management method comprises the following steps: receiving order information sent by a client; creating a detection order comprising the order information, and synchronizing the detection order and order state information to the client and a businessman terminal; receiving logistics information uploaded to the detection order by the client; updating the order state information to be sample-received, obtaining logistics state from a logistics platform and synchronizing the logistics state to the client; receiving a logistics number input by a detection terminal; matching the detection order corresponding to the logistics number, updating the order state information to be under detection, obtaining detection information of the detection order and sending the detection information to the detection terminal; receiving detection data uploaded by the detection terminal; generating detection results corresponding to the detection order by using the detection data and sending the detection results to the client, and updating the order state information to be completed. By using the detection business management method, the management efficiency and accuracy of the detection business can be improved.

Description

Technical Field

[0001] This application relates to the field of computer software technology, specifically to a method for managing testing operations. Background Technology

[0002] The existing testing business management model has significant flaws in the customer order placement and subsequent data management processes. Traditional testing business management methods rely heavily on manual interaction, which is not only inefficient but also prone to errors. For the testing process, after receiving samples, the testing laboratory needs to repeatedly verify sample information with the business department. This process is cumbersome and lengthy, consuming a significant amount of time and energy for both the testing laboratory and the business department, and is also prone to operational risks due to errors in information transmission. Regarding order settlement and reconciliation, when customers have a high testing frequency, historical order records are scattered, and the business department cannot promptly understand the real-time status of testing orders. This leads to delays and inaccuracies in settlement and reconciliation. The traditional method of manually recording testing orders is not only time-consuming and labor-intensive but also highly susceptible to omissions and errors, significantly increasing the company's operating costs and management risks. Summary of the Invention

[0003] Therefore, this application provides a testing business management method that can improve the management efficiency and accuracy of testing business.

[0004] To address the aforementioned technical problems, this application provides a technical solution: a testing business management method, comprising: receiving order information sent by a client, the order information including customer information, testing information, and salesperson information; creating a testing order including the order information, the order status information of the testing order being "pending sample delivery," and synchronizing the testing order and the order status information to the customer and the corresponding salesperson; receiving logistics information uploaded by the client to the testing order, the logistics information including a tracking number; updating the order status information of the testing order to "pending sample receipt," and simultaneously obtaining the logistics status using the logistics information and synchronizing it to the customer; receiving the tracking number input by the testing terminal; matching the tracking number with the corresponding testing order, updating the order status information of the testing order to "testing in progress," and simultaneously obtaining the testing information of the testing order and sending it to the testing terminal; receiving testing data uploaded by the testing terminal corresponding to the testing information; generating a testing result corresponding to the testing order using the testing data and sending it to the client, and updating the order status information of the testing order to "completed."

[0005] In one specific implementation, receiving the logistics tracking number input by the detection terminal includes: receiving the logistics tracking number input by the detection terminal through scanning a barcode.

[0006] In one specific embodiment, the testing information includes testing package information and sample information. The sample information includes at least one of the following: sample name, sample number, sample quantity, testing requirements, and sample image. Simultaneously acquiring the testing information of the testing order and sending it to the testing terminal includes: generating a sample label using the testing information and sending it to the testing terminal. The sample label is used to print a physical label to be attached to a physical sample. The testing order is then synchronized to the testing terminal.

[0007] In one specific embodiment, the testing service management method further includes: receiving a query message sent by the client; matching the testing order corresponding to the query message; obtaining the testing result corresponding to the testing order; and sending it to the client.

[0008] In one specific embodiment, synchronizing the testing order and the order status information to the customer and the corresponding salesperson includes: generating a status synchronization email and sending it to the salesperson, the status synchronization email including the customer information, the testing information, and the order status information; updating the order status information of the testing order to "pending sample receipt" includes: generating a status synchronization email and sending it to the salesperson, the status synchronization email including the customer information, the testing information, and the updated order status information "pending sample receipt"; updating the order status information of the testing order to "under testing" includes: generating a status synchronization email and sending it to the salesperson, the status synchronization email including the customer information, the testing information, and the updated order status information "under testing"; updating the order status information of the testing order to "completed" includes: generating a status synchronization email and sending it to the salesperson, the status synchronization email including the customer information, the testing information, and the updated order status information "completed".

[0009] In one specific implementation, synchronizing the testing order and the order status information to the customer and the corresponding salesperson information includes: generating a status push message and sending it to the client, the status push message including the order status information; updating the order status information of the testing order to "pending sample receipt" includes: generating the status push message and sending it to the client, the status push message including the updated order status information "pending sample receipt"; updating the order status information of the testing order to "in testing" includes: generating the status push message and sending it to the client, the status push message including the updated order status information "in testing"; updating the order status information of the testing order to "completed" includes: generating the status push message and sending it to the client, the status push message including the updated order status information "completed".

[0010] In one specific implementation, simultaneously acquiring the testing information of the testing order and sending it to the testing terminal includes: generating a test table to be filled using the testing information, and exporting the test table to be filled with the testing data to the testing terminal; receiving the testing data corresponding to the testing information uploaded by the testing terminal includes: receiving the test table with the testing data already filled up uploaded by the testing terminal.

[0011] In one specific implementation, updating the order status information of the testing order to "completed" includes: generating a settlement statement corresponding to the testing order and sending it to the customer; in response to receiving invoicing information sent by the client and a confirmation of payment message uploaded by the finance department, sending an invoice issuance request to the finance department; and receiving the invoice file uploaded to the testing order by the finance department.

[0012] In one specific implementation, after receiving the order information sent by the client and before creating a testing order including the order information, the process includes: sending the order information to the client for order information review; creating a testing order including the order information includes: in response to the result of the order information review being passed, creating the testing order corresponding to the order information.

[0013] In one specific implementation, before receiving the order information sent by the client, the process includes: receiving authentication information sent by the client, the authentication information including at least one of customer type, real-name authentication information, company name, unified social credit code, and invoicing information; sending the authentication information to the client for authentication information review; and, in response to the authentication information review result being passed, activating the client's order placement permission.

[0014] The beneficial effects of this application include: the testing business management method can utilize the order information provided by the customer to form a continuously updated testing order. The customer and the salesperson associated with the testing order can obtain the status of the testing order in a timely and automatic manner. The testing personnel can also use the express tracking number to efficiently and accurately obtain the testing information of the testing order. In this way, the originally isolated links such as salesperson's business development, customer order placement, sample delivery, testing laboratory sample receipt, testing execution, and test result generation can be linked together through a unified testing order. At each key node, status updates and information synchronization are automatically triggered, eliminating the need for cumbersome and inefficient manual communication and verification. This greatly reduces the proportion of manual operation in the testing business, reduces the probability of human oversight and errors, and effectively improves the management efficiency and accuracy of the testing business.

[0015] Meanwhile, since all operations, status changes, and data uploads in the testing business are recorded in the testing order, a complete digital archive is formed, which greatly improves the efficiency of subsequent auditing, problem tracing, analysis and comparison. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the implementation will be briefly introduced below. Obviously, the drawings described below are some implementations of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 This is a first flowchart illustrating an embodiment of the testing business management method of this application;

[0018] Figure 2 This is a second flowchart illustrating an embodiment of the testing business management method of this application;

[0019] Figure 3 This is a third flowchart illustrating an embodiment of the testing business management method of this application;

[0020] Figure 4 This is a fourth flowchart illustrating an embodiment of the testing business management method of this application;

[0021] Figure 5 This is the fifth flowchart of an embodiment of the testing business management method of this application;

[0022] Figure 6 This is a schematic diagram of multi-terminal interaction in an embodiment of the testing business management method of this application. Detailed Implementation

[0023] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of the invention. However, those skilled in the art will understand that the invention can be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of this application with unnecessary detail.

[0024] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0025] It should also be understood that the terminology used in this application specification is for the purpose of describing particular embodiments only and is not intended to limit the application. As used in this application 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. The terms “first” and “second” are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include at least one of that feature. In the description of this application, “a plurality” means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0026] 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 a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0027] Many specific details are set forth in the following description in order to provide a full understanding of this application. However, this application may also be implemented in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0028] The existing testing business management model has significant flaws in the customer order placement and subsequent data management processes. Traditional testing business management methods rely heavily on manual interaction, which is not only inefficient but also prone to errors. For the testing process, after receiving samples, the testing laboratory needs to repeatedly verify sample information with the business department. This process is cumbersome and lengthy, consuming a significant amount of time and energy for both the testing laboratory and the business department, and is also prone to operational risks due to errors in information transmission. Regarding order settlement and reconciliation, when customers have a high testing frequency, historical order records are scattered, and the business department cannot promptly understand the real-time status of testing orders. This leads to delays and inaccuracies in settlement and reconciliation. The traditional method of manually recording testing orders is not only time-consuming and labor-intensive but also highly susceptible to omissions and errors, significantly increasing the company's operating costs and management risks.

[0029] In order to improve or solve the above technical problems, the inventors of this application, after long-term research, have proposed at least the following embodiments.

[0030] Please see Figure 1 , Figure 6 , Figure 1 This is a schematic flowchart of the first embodiment of the testing business management method of this application.Figure 6 This is a schematic block diagram illustrating multi-terminal interaction in an embodiment of the testing business management method of this application. It should be noted that if substantially the same result is obtained, this embodiment does not necessarily replace it with a similar solution. Figure 1 , Figure 6 The illustrated process sequence is limited. For example... Figure 1 , Figure 6 As shown in the figure, a specific embodiment of this application provides a detection business management method, including:

[0031] S100: Receives order information sent by the client.

[0032] The testing business management method embodiment in this specific implementation can run on the server-side device system. The server can be server-side software running on devices such as desktop computers, servers, and mobile terminals. In this specific implementation, the server-side software serves as the executing entity for running the testing business management method of this application.

[0033] A client application refers to a dedicated user interface or application used by clients who commission testing services. It can run on electronic devices such as desktop computers and mobile terminals. Specifically, a client application can be a WeChat mini-program for the testing company. The client application serves as a digital portal for clients to conduct full-cycle business interactions with the testing organization, and is a core tool for clients to achieve self-service, status tracking, and result acquisition. Furthermore, the client application has a human-computer interaction interface, allowing clients to perform various operations through the human-computer interface of the electronic device running the client application.

[0034] Data transmission between the electronic device hosting the server software and the electronic device hosting the client can be accomplished via Ethernet, WLAN (Wireless Local Area Network), or other means.

[0035] The order information may include customer information, testing information, and salesperson information. The order information is the raw data used to create a testing order. Customer information may include at least one of the following: customer name, tax ID, customer contact person, or customer contact information.

[0036] In one specific embodiment of this application, the testing information may include testing package information and sample information. Sample information may include at least one of the following: sample name, sample number, sample quantity, testing requirements, and sample image.

[0037] Among them, the testing package refers to a standardized testing package that is pre-set by the testing organization and includes fixed testing items, standards and prices. The testing package information refers to various specific information in the standardized testing package, such as the testing object, the name of the testing indicator, the testing method, and the standard on which the testing is based.

[0038] For example, an environmental water quality testing package may include four items: pH value, chemical oxygen demand, ammonia nitrogen, and total phosphorus. This testing package is implemented in accordance with the "Surface Water Environmental Quality Standard" and is priced at RMB [amount missing]. A textile safety package suitable for infants and young children may include items such as formaldehyde content, pH value, color fastness, and decomposable carcinogenic aromatic amine dyes. This testing package is implemented in accordance with GB 31701 standard and is priced at RMB [amount missing].

[0039] Standardized testing packages encapsulate the complex testing capabilities of testing organizations into easily understandable and selectable products. Different standardized testing packages also form a corresponding set of standardized and efficient testing processes, which can greatly improve the efficiency of customer ordering and testing personnel testing.

[0040] For example, when a customer places an order, they can select a standardized testing package from a drop-down menu or list on the client's order interface. The client's order interface can then automatically display the testing items, standards, and prices corresponding to that standardized testing package, without requiring the customer to manually fill in each item.

[0041] Optionally, the client's human-computer interaction interface may display the contact information of the testing company's customer service personnel, or include a button to trigger online customer service. Customers can contact the testing company's customer service personnel through the contact information or the trigger button. When no standardized testing package meets the customer's needs, the customer can contact customer service personnel to customize a personalized testing package using the client application.

[0042] Sample information is a description of the physical sample submitted by the customer. Before testing, personnel in the testing organization who need to handle the physical sample can use the sample information to confirm whether the received physical sample is correct.

[0043] The sample name is a common or conventional designation for the sample, such as "tomato" or "a certain brand and model of mobile phone motherboard." The sample number is a unique code generated by the customer or system to identify the sample, enabling differentiation and traceability. The sample quantity is the physical unit of measurement for the submitted samples. Testing requirements refer to any special instructions, additional conditions, or personalized needs proposed by the customer for this testing process, supplementing the standardized testing package. Sample images are photographs or videos uploaded by the customer reflecting the appearance, condition, markings, or specific parts of the physical sample. Corresponding to the textual sample name, the sample images serve as visual verification evidence of the physical sample.

[0044] Optionally, the sampling requirements for physical samples can be displayed on the client's interface for filling in sample information. This helps customers prepare suitable samples, reduces the probability that physical samples sent by customers do not meet the testing requirements, resulting in inaccurate test results or failure to perform testing, and improves the efficiency of testing operations and the accuracy of test results.

[0045] In the method provided in this specific embodiment, the testing information is refined from both the testing package and physical samples. Standardized data fields are set for the testing process of physical samples, so that customer needs can be entered into the system in a machine-readable and process-understandable way and can correspond to the standard testing process. This avoids the problems of misunderstanding caused by customers' vague description of their needs, laboratory misdiagnosis, or repeated communication and confirmation.

[0046] Furthermore, the standardized testing packages offer customers a standardized, menu-driven selection, guiding the ordering process. While ensuring complete testing information, they simplify the configuration of complex testing items, lowering the barrier to entry for customers. Sample information can be compared with the testing package information, reducing the probability of mismatch between the standardized testing package and the actual sample, thereby improving the accuracy of customer orders and more efficiently and accurately meeting their testing needs.

[0047] S200: Create a testing order that includes order information, with the order status information set to "sample pending delivery," and synchronize the testing order and order status information to the customer and the corresponding salesperson information.

[0048] The salesperson's end refers to the dedicated interface or software module used by a company's salespersons, such as sales representatives and account managers. It's an integrated digital workbench for salespeople to manage customers, track orders, coordinate progress, and conduct business communication. Specifically, the salesperson's end can be a web portal or application that runs on electronic devices such as desktop computers, smartphones, and tablets. It features a user-friendly interface that allows salespeople to perform various operations.

[0049] Data transmission between the electronic device hosting the server software and the electronic device hosting the salesperson's device can be accomplished via Ethernet, WLAN (Wireless Local Area Network), or other means.

[0050] A testing order is a digital entity generated by the server based on order information and spans the entire testing process, containing the order information provided by the client. The order status information is updated in real-time as the testing process progresses. This status information identifies the stage of the testing order within the process and serves to notify both the client and the sales representative. Specifically, when the order status is "Pending Sample Shipment," it indicates that the testing order has just been created and is awaiting the customer to ship the corresponding sample.

[0051] Synchronization can refer to the server proactively pushing or updating changes to the test orders and order status information to the client and salesperson's terminal interface in real time or near real time. This ensures that the information on the client and salesperson's end is consistent with the server, allowing the client and salesperson to obtain the latest status of the test orders and their order status information in real time or near real time through the client and salesperson's end.

[0052] For example, when the testing laboratory changes the order status to "Pending Sample Delivery", the server can add the testing order to the order list of the client that uploaded the order information and display the order status information of the testing order as "Pending Sample Delivery". At the same time, the server can add the testing order to the salesperson's client corresponding to the salesperson information and display the order status information of the testing order as "Pending Sample Delivery".

[0053] S300: Receives logistics information uploaded by the client to the inspection order.

[0054] Specifically, this logistics information may include a tracking number. The tracking number can be a unique tracking number provided by the courier or logistics company when the customer sends the sample. In the testing business management method provided in this specific embodiment, after the tracking number is uploaded to the server, a link can be established between the physical sample and the testing order.

[0055] S400: Updates the order status information of the inspection order to "samples to be received", and at the same time uses logistics information to obtain the logistics status and synchronizes it to the customer.

[0056] After the customer sends out the physical sample, the server can use the tracking number to retrieve the sample's shipping status from the logistics company's or courier company's open interface by uploading the tracking number to the testing order. The shipping status refers to the real-world transportation status of the physical sample corresponding to the testing order. By synchronizing the shipping status to the client, the customer can use the client to track the sample's progress.

[0057] When the order status is "Pending Sample Receipt," it means that the customer has sent out the physical sample, which is currently in transit and awaiting delivery to the testing laboratory.

[0058] S500: Receives the logistics tracking number entered by the detection terminal.

[0059] The testing terminal is the end point used by the testing laboratory. Testing personnel can use it to obtain testing information, upload test results, and perform other operations. After receiving the sample package, the testing laboratory can input the tracking number from the physical sample package into the server through the testing terminal.

[0060] Specifically, the testing terminal can be a workstation of a Laboratory Information Management System (LIMS) with a fully functional software system. Alternatively, it can be a computer connected to the testing instrument, capable of directly acquiring data from or controlling the instrument. It can also be a tablet or mobile terminal used by testing personnel, allowing them to record data and view testing information on-site.

[0061] Data transmission between the electronic device hosting the server software and the electronic device hosting the detection terminal can be accomplished via Ethernet, WLAN (Wireless Local Area Network), or other means.

[0062] In one specific embodiment of this application, step S500, "receiving the logistics tracking number input by the detection terminal," may include receiving the logistics tracking number input by the detection terminal through scanning a barcode.

[0063] Specifically, the tracking number can be manually entered by inspectors using human-computer interaction devices such as keyboards, touchscreens, and mice. Alternatively, inspectors can quickly enter the tracking number by scanning a barcode using a device equipped with barcode scanning capabilities. On the outer packaging of express or logistics items, a barcode encoded using the tracking number is usually printed along with the tracking number. This barcode uses specific encoding rules to convert character information such as numbers and letters into a graphic identifier composed of a set of parallel lines and blank areas of varying widths and reflectivities. The barcode scanning equipment in the testing laboratory can identify the width sequence of the lines and blank areas by illuminating the barcode with light and detecting the differences in reflected light, then decode the original character information according to the encoding rules, thus deciphering the tracking number.

[0064] Among them, devices with barcode scanning capabilities can include at least one of the following: light pen, chargecoupled device (CCD) reader, laser scanner, image-type red light barcode reader, mobile phone, tablet computer, etc.

[0065] In the method provided in this specific embodiment, the method of inputting the tracking number is limited to scanning the barcode. Automated and standardized machine recognition replaces manual visual reading and manual input. This improves the efficiency of tracking number input while ensuring the consistency between the tracking number input at the detection end and the tracking number on the physical sample packaging. It eliminates problems such as order matching failure and incorrect sample attribution caused by human error or manual input, thereby improving the accuracy and efficiency of tracking number input.

[0066] S600: Use the logistics tracking number to match the corresponding testing order, update the order status information of the testing order to "under testing", and at the same time obtain the testing information of the testing order and send it to the testing end.

[0067] Once the tracking number is received from the testing end, the server can use that tracking number to find the testing order associated with it, thereby obtaining the testing information of the testing order and sending it to the testing end. The testing personnel can then use this information to test the physical sample, thus starting the testing process. The server can then update the order status information of the testing order to "testing in progress".

[0068] When the order status is "under testing", it means that the testing laboratory has received the physical sample and obtained the testing information for the physical sample, and is currently testing the physical sample.

[0069] Since the tracking number directly links the testing order with the physical sample, there is no need to set special identifiers for the physical sample and the testing order to establish a relationship. This allows testing personnel to accurately and efficiently match the physical sample with the testing information without excessive manual verification, greatly improving the efficiency of testing physical samples.

[0070] Please see Figure 2 , Figure 2 This is a schematic flowchart of the second process of an embodiment of the testing business management method of this application. It should be noted that if substantially the same result is obtained, this embodiment does not necessarily replace it with the original. Figure 2 The illustrated process sequence is limited. For example... Figure 2 As shown, in step S600, "simultaneously acquiring the testing information of the testing order and sending it to the testing terminal" may include:

[0071] S601: Generate sample labels using the inspection information from the inspection order and send them to the inspection terminal. The sample labels are used to print physical labels to attach to the physical samples.

[0072] The sample label is automatically generated by the server based on the testing information of the testing order corresponding to the logistics tracking number after the testing laboratory receives the physical sample, and then sent to the testing end. The testing end can print out the sample label to form a physical label, which can be attached to the physical sample and can serve as a physical identity certificate and a concise work instruction card for the physical sample during the testing process.

[0073] For example, the physical label can directly display the corresponding testing information, testing order number, and logistics tracking number in text form. It can also include barcodes, QR codes, or other encodings, allowing testing personnel to obtain the testing information by scanning the codes.

[0074] S602: Synchronize the testing order to the testing terminal.

[0075] The testing terminal can be used to display testing orders synchronized from the server, thereby obtaining testing information, order status information, etc. of the testing order.

[0076] It should be noted that steps S601 and S602 are independent of each other and have no specific order. When performing the method provided in this specific embodiment, steps S601 and S602 can be performed simultaneously or sequentially.

[0077] In the method provided in this specific embodiment, the printed sample label accompanies the physical sample throughout the entire testing cycle. During any transfer, sorting, testing, or storage process in the testing laboratory, the testing information of the physical sample can be quickly confirmed by scanning or viewing this sample label. Furthermore, in addition to the physical sample label, this method can directly synchronize testing orders from the server to the testing terminal. Testing personnel can then view the corresponding testing information for the physical sample through the testing terminal, fully utilizing the testing orders on the server and providing diverse methods for viewing testing information. This offers testing personnel a more comprehensive way to view testing information, thereby further ensuring the accuracy of physical sample testing.

[0078] S700: Receives detection data uploaded by the detection terminal that corresponds to the detection information.

[0079] The test data is a collection of data compiled by the testing laboratory after the physical sample has undergone the testing process corresponding to the test information, based on the original records, observations, spectra, photographs and other process data generated during the testing process.

[0080] In a specific embodiment of this application, step S600, "simultaneously obtaining the testing information of the testing order and sending it to the testing end", may include: using the testing information to generate a test table to be filled, and exporting the test table containing the testing data to the testing end.

[0081] Step S700, "receiving the detection data corresponding to the detection information uploaded by the detection terminal," includes receiving a test table with pre-filled detection data uploaded by the detection terminal.

[0082] The testing terminal allows testing personnel to upload testing data, enter or upload testing data, and observe results.

[0083] Specifically, the testing terminal can provide a structured test form, which testing personnel can use to record the test data and then upload the test form filled with the test data to the server.

[0084] Optionally, the detection end can be connected to a detection instrument, thereby automatically collecting detection data from the detection instrument and filling it into the test table.

[0085] Optionally, the testing terminal can also be used to query historical testing records of the sample or similar samples in the testing laboratory, enabling testing personnel to plan and analyze the testing process of physical samples using historical data.

[0086] S800: Generates test results corresponding to the test order using the test data and sends them to the client, updating the order status information of the test order to "completed".

[0087] The test results are files generated by the server using the test data. They are legally valid, standardized, and formal test reports with clear conclusions. Specifically, they can be digital test reports in PDF format.

[0088] The server can use the testing data uploaded by the testing terminal to generate testing results corresponding to the testing order, and send the testing results to the client so that the client receives the testing results that match the physical sample sent out, that is, the testing process of the testing order has been completed.

[0089] When the order status is "completed," it means that the testing laboratory has completed the testing of the physical sample and the customer can obtain the test results of the physical sample through the client.

[0090] Optionally, after generating the test results, the server can also store the test results and test data in the test order, so that the test order includes complete data from order placement to result issuance. The test order can be stored on the device where the server is located or on a storage device connected to the server, and the server can efficiently retrieve data from the test order when needed.

[0091] The testing business management method provided in this specific embodiment can utilize the order information provided by the customer to form a continuously updated testing order. The customer and the salesperson associated with the testing order can obtain the status of the testing order in a timely and automatic manner. The testing personnel can also use the express tracking number to efficiently and accurately obtain the testing information of the testing order. In this way, the previously isolated links such as salesperson business development, customer order placement, sample delivery, testing laboratory sample receipt, testing execution, and test result generation can be linked together through a unified testing order. At each key node, status updates and information synchronization are automatically triggered, eliminating the need for cumbersome and inefficient manual communication and verification. This greatly reduces the proportion of manual operation in the testing business, reduces the probability of human error and omissions, and effectively improves the management efficiency and accuracy of the testing business.

[0092] Meanwhile, since all operations, status changes, and data uploads in the testing business are recorded in the testing order, a complete digital archive is formed, which greatly improves the efficiency of subsequent auditing, problem tracing, analysis and comparison.

[0093] In a specific embodiment of this application, after the step "receiving the test form with filled test data uploaded by the testing terminal" and before the step S800 "generating the test result corresponding to the test order using the test data and sending it to the client", the following may be included:

[0094] S701: Identify whether the test table has a verification mark.

[0095] The test data entered into the test form needs to be reviewed by the testing personnel responsible for verification to ensure the reliability of the test data in the test form. Regardless of whether the verification step is carried out before or after the test data is entered into the test form, as long as the test data has been verified by the testing personnel and the verification result is passing, the test form with the entered test data will have a verification mark made by the testing personnel responsible for verification.

[0096] S702: In response to the test table not having a verification mark, suspend the detection business management method until a test table with a verification mark is received.

[0097] When the server detects that the test table does not have a review mark, it means that the test data in this test table has not been reviewed by the testers or the review result is unsatisfactory. In other words, the test data in the test table may have omissions, errors, or other problems. At this time, the server can suspend the test business management method provided in this application, that is, not execute step S800, until it receives a test table with a review mark.

[0098] In the method provided in this specific embodiment, it is possible to determine whether the test data in the test table has been reviewed by the responsible testing personnel by identifying whether the test table uploaded by the testing terminal has a review mark, and to provide timely remedial measures for the testing personnel, thereby ensuring the reliability of the generated test results.

[0099] In a specific embodiment of this application, in step S200, "synchronizing the detected order and order status information to the customer and the corresponding salesperson information" may include: generating a status synchronization email and sending it to the salesperson.

[0100] Status synchronization emails can include customer information, detection information, and order status information. Status synchronization emails are emails automatically generated by the system based on a preset email template and sent to a designated salesperson when the system detects changes in the order status information.

[0101] In step S400, "updating the order status information of the inspection order to 'samples to be received'" may include: generating a status synchronization email and sending it to the salesperson. The status synchronization email includes customer information, inspection information, and the order status information updated to 'samples to be received'.

[0102] In step S600, "updating the order status information of the detected order to 'in progress'" may include: generating a status synchronization email and sending it to the salesperson. The status synchronization email includes customer information, detection information, and the updated order status information to 'in progress'.

[0103] In step S800, "updating the order status information of the detected order to completed" may include: generating a status synchronization email and sending it to the salesperson. The status synchronization email includes customer information, detection information, and the updated completed order status information.

[0104] In the method provided in this specific implementation, the server generates a status synchronization email at each node where the order status changes and sends it to the relevant salesperson's terminal. Since receiving the email does not require the recipient to be online in real time, unread emails by the recipient will be persistently stored in the mail server, allowing the salesperson to check the status synchronization email at any time and any place through the salesperson's terminal, ensuring that the order status information can be effectively synchronized to the salesperson.

[0105] Furthermore, the status synchronization emails include customer information, testing information, and updated order status information for the testing orders. This creates a linear, timestamped electronic file for the testing orders on the salesperson's end, which can serve as an official basis for salespersons to confirm service progress, conduct internal performance evaluations, and clarify responsibilities, greatly improving the efficiency of salespersons' work.

[0106] In a specific embodiment of this application, step S200, "and synchronizing the detected order and order status information to the customer and the corresponding salesperson information" may include: generating a status push message and sending it to the client, wherein the status push message includes order status information.

[0107] Status push messages refer to short and formatted instant notifications that are triggered by the server and sent proactively to the client through the technical channels provided by the mobile operating system or instant messaging platform. They can inform customers of changes in order status information in a high-priority and direct manner.

[0108] Optionally, even if the corresponding software is not running in the foreground, status push messages can still be displayed through the system notification bar, lock screen, or other means.

[0109] The mobile operating system may include at least one of the following: iOS's APNs (Apple Push Notification Service), Android's FCM (Firebase Cloud Messaging), and GCM (Google Cloud Messaging). The instant messaging platform may include WeChat service notifications.

[0110] In step S400, "updating the order status information of the detected order to 'samples to be received'" may include: generating a status push message and sending it to the client, wherein the status push message includes the updated order status information to 'samples to be received'.

[0111] In step S600, "updating the order status information of the detected order to 'in detection'" may include: generating a status push message and sending it to the client, the status push message including the updated order status information to 'in detection'.

[0112] In step S800, "updating the order status information of the detected order to 'complete'" may include: generating a status push message and sending it to the client, the status push message including the updated order status information as 'complete'.

[0113] In the method provided in this specific implementation, a status push message, an instant, lightweight, and highly reachable notification mechanism, is introduced for the client. Ordinary order status information is synchronously upgraded to a push service with strong awareness, so that changes in order status information are no longer passively waiting for customers to query through the client, but are actively sent to the client as an instant reminder. Status push messages are more direct and harder to ignore, ensuring that updates to order status information can be effectively delivered to the customer.

[0114] Please see Figure 4 ,Figure 6 , Figure 4 This is a schematic flowchart of the fourth step in an embodiment of the testing business management method of this application. It should be noted that if substantially the same result is obtained, this embodiment does not necessarily replace it with the original. Figure 4 , Figure 6 The illustrated process sequence is limited. For example... Figure 4 , Figure 6 As shown in a specific embodiment of this application, step S800, after "updating the order status information of the detected order to 'completed'", may include:

[0115] S801: Generate a settlement statement corresponding to the inspection order and send it to the customer.

[0116] The settlement statement is an electronic formal payment notification document automatically calculated and generated by the server based on the order information in completed testing orders. It lists the total amount payable and details. The settlement statement is the legal basis for testing companies to initiate payment to customers. For example, the settlement statement may include key information such as customer name, testing order number, testing fee details, total amount, receiving account, and payment deadline. The testing fee details may include, depending on the specific circumstances, at least one of the following: unit price for each test item, quantity of each test item, express fee, and service fee, as well as the total amount obtained by adding up all fees.

[0117] Once the testing process is complete, i.e., the order status information of the testing order is updated to "completed", the server can generate a settlement form corresponding to the testing order and send it to the customer, immediately starting the settlement process. This eliminates the time spent manually preparing settlement forms, improves the efficiency of the settlement process, and can also urge customers to complete the payment process.

[0118] Specifically, methods for sending the settlement statement to the client may include the server generating a file containing the settlement statement and uploading that file to the inspection order. Alternatively, the server may send the file containing the settlement statement to the client as an email attachment. Another method may involve the server generating a client push message containing the settlement statement, which the client can trigger to retrieve the settlement statement.

[0119] S802: In response to receiving the invoicing information sent by the client and the confirmation of receipt uploaded by the finance department, send an invoice issuance request to the finance department.

[0120] The "financial end" refers to the system terminal or software module used by the company's financial personnel to handle financial processes such as receiving payments, making payments, issuing invoices, and reconciling accounts. It can be part of an Enterprise Resource Planning (ERP) system or an independent financial system. Data transmission between the electronic device hosting the server-side software and the electronic device hosting the financial end can be accomplished via Ethernet, WLAN (Wireless Local Area Network), or other means.

[0121] Invoicing information refers to the collection of enterprise or personal information that complies with national tax regulations, uploaded by customers through a client application when applying for value-added tax invoices and other documents. It is essential data for initiating a compliant invoicing request to the finance department. Invoicing information typically includes the invoice header and taxpayer identification number.

[0122] Furthermore, the invoice information may also include at least one of the following: the recipient's registered address, contact number, bank account information, and invoice receiving email address. Optionally, when the invoice information includes the invoice receiving email address, the invoice issued by the finance department can be sent to the invoice receiving email address by the server.

[0123] A payment confirmation message is a confirmation instruction sent proactively by the finance department to the server after verifying that payment for a certain order has been received from the customer. It is a key security switch that triggers the invoicing process. An invoice issuance request is an invoicing instruction automatically generated and sent to the finance department after all three conditions are met: "detection completed," "customer has submitted invoicing information," and "finance department has confirmed receipt of payment."

[0124] For example, after receiving the settlement statement, the customer can complete the payment process directly through the client. For instance, if the client is a WeChat mini-program, the customer can make the payment directly within the mini-program. Customers can also make payments through offline transfers based on the receiving account information in the settlement statement. Customers can also make payments through the business personnel associated with the testing order. Regardless of the payment method used, the confirmation message will only be sent through the finance department after the finance personnel confirm that the funds have been received.

[0125] Furthermore, when a customer's account has multiple unpaid settlement orders, the customer can combine them for settlement. For example, when the client is in the form of a WeChat mini-program, the customer can select multiple settlement orders to be settled simultaneously for combined payment. Alternatively, after communicating and confirming with sales or finance personnel, the customer can pay for multiple settlement orders at once via offline transfer.

[0126] Once the server receives the payment confirmation message from the finance department, it indicates that the customer has completed the settlement for the testing order. After receiving the payment confirmation message and the invoicing information from the client, the server can send an invoice issuance request to the finance department to issue an invoice to the customer.

[0127] This eliminates the need for manual communication and operations among salespersons, finance personnel, and customers during the settlement and invoicing process. It effectively solves problems such as long settlement cycles, cumbersome reconciliation, delayed invoicing, and difficulties in managing payments under the traditional manual reconciliation model. It also resolves financial risks such as amount errors and asynchronous invoicing and payments caused by manual processing.

[0128] S803: Received the invoice file uploaded to the testing order by the finance department.

[0129] The finance department can upload invoice files to the corresponding testing orders, allowing customers to obtain the corresponding invoice files from the testing orders through the client. This enables a one-stop process from placing a testing order to issuing an invoice within the client, improving the efficiency and convenience of customers' testing services.

[0130] Using the method provided in this specific implementation, after the testing service is substantially completed, the business settlement and financial invoicing processes can be automatically connected, extending the management of testing business from the testing service to the back end, realizing the integration and automation of testing business and financial management. While reducing the workload of sales staff, customers and financial personnel, it solves most of the risks that may be caused by manual operation, and effectively ensures the timeliness, accuracy, efficiency and compliance of cash flow management of testing business.

[0131] In a specific embodiment of this application, after step S100 "receiving order information sent by the client" and before step S200 "creating a testing order including order information", the process may include: sending the order information to the client for order information review.

[0132] The client-side component is the software terminal or user interface used by the company's customer service personnel to review and process customer order information. Data transmission between the electronic device hosting the server-side software and the electronic device hosting the client-side software can be accomplished via Ethernet, WLAN (Wireless Local Area Network), or other means.

[0133] Order information review refers to the process by which customer service personnel manually check and judge the completeness, accuracy, compliance, and feasibility of the order information submitted by the customer, based on the testing company's preset business rules, technical specifications, and pricing policies. The order information review can output a clear binary result, namely, approval or rejection.

[0134] For example, after a customer submits a soil heavy metal testing order on the client-side software, customer service personnel can log in to the client software using a computer. The client software will display the soil heavy metal testing order information pending review, and the customer service personnel can review the order information through the client software. If the customer service personnel find that the testing object in the testing package information does not match the actual sample in the sample information, the customer service personnel can reject the soil heavy metal testing order information. The server will then send a rejection message to the client and return the soil heavy metal testing order information to the client.

[0135] Specifically, a rejection message can include an explanation of which part of the order information is not acceptable, and the rejection message can also include suggestions for modifying the order information.

[0136] Optionally, the client interface for filling in sample information can display the sampling requirements for physical samples, thereby assisting customers in preparing suitable samples, reducing the workload of customer service personnel during the review process, and improving the efficiency of customers placing orders.

[0137] Furthermore, customer service personnel can contact customers using the contact information they provided while or after the rejection process, thereby enabling them to communicate with and guide customers.

[0138] In step S200, “creating a test order including order information” may include: in response to the result of the order information review being passed, creating a test order including order information.

[0139] In the method provided in this specific embodiment, a step of reviewing order information is added between step S100 and step S200. Customer service personnel can manually review the order information through the customer service terminal. Only the approved order information can trigger the step of creating a testing order, thereby ensuring the accuracy, feasibility, compliance, standardization and completeness of the subsequent testing process, reducing the probability of problems in the testing process and greatly improving the efficiency of testing business execution and management.

[0140] Please see Figure 5 , Figure 6 , Figure 5 This is a schematic flowchart of the fifth embodiment of the testing business management method of this application. It should be noted that if substantially the same result is obtained, this embodiment does not necessarily reflect that outcome. Figure 5 , Figure 6 The illustrated process sequence is limited. For example... Figure 5 , Figure 6 As shown in a specific embodiment of this application, step S100 "receiving order information sent by the client" may include the following:

[0141] S111: Receive authentication information sent by the client. The authentication information includes at least one of the following: customer type, real-name authentication information, company name, unified social credit code, and invoicing information.

[0142] Authentication information refers to the collection of data that customers must submit to the platform for identity verification and registration before placing an order using the client for the first time, in order to prove their legal identity and eligibility for services. Customer type can be used to distinguish the legal entity nature of a customer and determine the applicable terms of service for reviewing customer information. For example, the options for customer type may include corporate customers, individual customers, and public institution customers.

[0143] Real-name authentication information is provided based on customer type and can be used to verify the true identity of an individual or the legal representative of a company. For example, for corporate customers, real-name authentication information can be the name and ID number of the company's legal representative. For individual customers, real-name authentication information can be the individual's name and ID number.

[0144] When the client type is a corporate client or a public institution client, the company name can be the official registered full name of the corporate or public institution. Optionally, this official registered full name must be consistent with the business license.

[0145] The Unified Social Credit Code is a unique, permanent, and official identification code for enterprises and organizations registered in China, typically consisting of 18 digits and letters.

[0146] Invoicing information refers to tax-related information provided by customers in order to receive invoices. For example, invoicing information may include at least one of the following: company name, taxpayer identification number (i.e., unified social credit code), taxpayer address, taxpayer telephone number, bank name, bank account number, etc.

[0147] S112: Send the authentication information to the client for verification.

[0148] Authentication information verification refers to the process by which the customer service department verifies and approves the authenticity, completeness, and compliance of the authentication information submitted by the customer. Its purpose is to verify whether the customer's identity is genuine and valid, and whether the authentication information provided by the customer accurately matches their identity.

[0149] For example, the client can utilize third-party data services to verify, for instance, whether the company name corresponding to the unified social credit code actually exists and is in a normal status. It can also verify whether the ID number in the real-name authentication information matches the name in the authentication information. Furthermore, it can check whether the company name, unified social credit code, and company name in the invoicing information submitted by the customer match and are logically consistent. Optionally, these verification steps can be performed automatically by the client; they can also be performed manually by client software assisted by customer service personnel; or they can be performed entirely manually by customer service personnel, with the client only serving to display authentication information to them.

[0150] Furthermore, when customers upload authentication information, they can also be required to upload scanned copies of their business licenses, photocopies of the legal representative's ID cards, etc., as attachments for verification of the authentication information.

[0151] S113: In response to the authentication information verification result being passed, the client's order placement permission is granted.

[0152] Among them, the order placement permission refers to the permission granted by the server to a customer account logged in on the client after the authentication information has been verified, allowing the customer to use the customer account to upload order information through the client to create a testing order.

[0153] For example, before order placement permission is granted, even if a customer logs into their account in the client's human-computer interaction interface, they cannot trigger the "Create New Order" area; they can only see the customer's personal information and the testing company's introduction to standardized testing packages. After approval, the customer's order placement permission is granted, and the "Create New Order" area in the client's human-computer interaction interface is highlighted. The customer can then trigger the "Create New Order" area to enter the order interface and begin filling in the order information, i.e., proceed to step S100.

[0154] In the method provided in this specific implementation, an authentication process for customer account qualification access and identity verification is set at the forefront of the testing business management. This ensures that all customer accounts that can place orders on the platform are verified, have complete information, and are traceable legal entities or individuals. Based on the review of customer qualifications, a reliable order placement premise is established, thereby reducing the management burden of subsequent processes such as reviewing order information, executing testing procedures, and reconciling payments. The starting point for risk control, compliance management, and operational efficiency is moved from the order placement to the customer themselves, fundamentally eliminating the commercial and compliance risks caused by customer identity issues.

[0155] Meanwhile, information such as company name and invoicing information in the certification information can be directly accessed in the subsequent testing, settlement and invoice issuance process, so that customers do not have to upload information temporarily and customer service personnel do not have to conduct temporary review, further improving the efficiency of testing business execution and management.

[0156] Please see Figure 3 , Figure 3 This is a schematic flowchart of the third embodiment of the testing business management method of this application. It should be noted that if substantially the same result is obtained, this embodiment does not necessarily reflect that outcome. Figure 3 The illustrated process sequence is limited. For example... Figure 3 As shown in a specific embodiment of this application, the detection business management method further includes:

[0157] S901: Receives query messages sent by the client.

[0158] A query message refers to a search request sent by a customer through the client to retrieve historical testing orders and results. The server will then retrieve the corresponding testing orders and results from the database based on this request. For example, the client's human-computer interaction interface may display a "Historical Data" button, which the customer can trigger to send a query message.

[0159] Furthermore, the query message can also be a search condition or a combination of search conditions input by the customer through the human-computer interface. For example, a customer can directly enter the complete order number as the query message in the search box on the client's human-computer interaction page, allowing the server to directly locate that specific testing order. When a customer only remembers the physical sample or the approximate name of the testing package, they can enter keywords such as "steel, corrosion" in the search box. The server will then search for "steel, corrosion" in the testing orders under that customer's account and return all testing orders whose order information contains the keywords "steel, corrosion".

[0160] The query information may include at least one of the following: sample information, testing package information, customer information, salesperson information, and logistics information.

[0161] Optionally, the client's human-computer interaction interface can also have an advanced search area, which can display multiple search dimensions and their sub-options. For example, if a customer selects "Food Microbiology Testing" as an option under the "Testing Packages" dimension in the advanced search, and then selects "Last Six Months" as an option under the "Test Result Time Range" dimension, the server will search the customer's account for "Food Microbiology Testing" and "Last Six Months" in the testing orders, and return all food microbiology testing orders that match the results generated in the last six months.

[0162] After step S800, the customer can send a query message to inquire about testing orders through the client, thereby obtaining historical testing orders and their testing results that match the query message. Specifically, if a customer has multiple historical testing orders and the order information for these orders is duplicated, the customer's query operation may retrieve multiple historical testing orders and their testing results.

[0163] S902: Match the detection order corresponding to the query message, obtain the detection result corresponding to the detection order, and send it to the client.

[0164] Among them, matching the test orders corresponding to the query message refers to the process by which the server, after receiving a query message sent by a customer account, executes a retrieval algorithm in the database based on the query message to obtain the test orders corresponding to that customer account, so as to find all test orders that meet the conditions in the query message.

[0165] Obtaining the test results corresponding to a test order refers to the process by which, after a specific test order is matched, the server retrieves the test results corresponding to that test order from the database or file storage system it is connected to.

[0166] The server uses query messages to match the corresponding testing orders, obtains the testing results corresponding to the testing orders, and sends them to the client. This allows the client to view the testing results that match their query messages and to view, analyze, and compare historical testing results.

[0167] After receiving the test results, the client can view the results online or download them to the memory of the electronic device where the client is located, so that they can view them offline or perform further operations.

[0168] The method provided in this specific embodiment, in addition to managing ongoing testing orders, also provides customers with a means to self-service retrieve historical testing orders and associated testing results. It supports multi-dimensional queries based on sample information, testing package information, and customer information, flexibly adapting to different customer memory points, query needs, and query habits. Essentially, it provides customers with a private, structured testing archive, allowing them to independently query specific testing results at any time. This enables the aggregation, comparison, and analysis of data based on these historical testing results, allowing the method to provide deeper support for product development while offering testing services. For example, when samples from different batches of the same product are submitted for testing multiple times, customers can query the product's historical testing results and analyze the trends in these results to provide data support for quality control.

[0169] Therefore, the testing business management method provided in this specific embodiment can not only be used by testing companies to manage testing orders internally, but also assist customers in managing their historical testing orders and test results. The process of querying test results does not require manual service from the testing company. Even if there are changes in personnel or organizational structure on both sides, it will not affect the query of historical test results, which greatly improves the work efficiency of both parties and also increases the closeness of cooperation between customers and testing companies.

[0170] In this application, the terms "embodiment" and "implementation" mean that a specific feature or characteristic described in connection with an embodiment can be included in at least one embodiment of this application. The appearance of these phrases in various places in the specification does not necessarily refer to the same embodiment, nor are they independent or alternative embodiments mutually exclusive with other embodiments. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described in this application can be combined with other embodiments. Furthermore, it should be understood that the features, elements, or characteristics described in the various embodiments of this application can be arbitrarily combined to form another embodiment that does not depart from the spirit and scope of the technical solution of this application, provided there is no contradiction between them.

[0171] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to the above preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions to the technical solutions of this application should not depart from the spirit and scope of the technical solutions of this application.

Claims

1. A method for managing testing operations, characterized in that, include: Receive order information sent by the client, the order information including customer information, testing information and salesperson information; Create a testing order that includes the order information, the order status information of the testing order is "sample to be sent", and synchronize the testing order and the order status information to the customer and the corresponding salesperson information; Receive logistics information uploaded by the client to the testing order, the logistics information including the tracking number; The order status information of the inspection order is updated to "samples to be received," and the logistics status is obtained using the logistics information and synchronized to the customer. Receive the logistics tracking number input by the detection terminal; The tracking number is used to match the corresponding inspection order, the order status information of the inspection order is updated to "in inspection", and the inspection information of the inspection order is obtained and sent to the inspection terminal. Receive detection data uploaded by the detection terminal that corresponds to the detection information; The detection data is used to generate a detection result corresponding to the detection order and sent to the client, and the order status information of the detection order is updated to "completed".

2. The testing business management method according to claim 1, characterized in that, The receipt of the logistics tracking number input by the detection terminal includes: receiving the logistics tracking number input by the detection terminal through scanning the barcode.

3. The testing business management method according to claim 1, characterized in that, The testing information includes testing package information and sample information. The sample information includes at least one of the following: sample name, sample number, sample quantity, testing requirements, and sample image. The step of simultaneously acquiring the testing information of the testing order and sending it to the testing terminal includes: using the testing information to generate a sample label and sending it to the testing terminal, wherein the sample label is used to print a physical label to be attached to a physical sample; The testing order is synchronized to the testing terminal.

4. The testing business management method according to claim 3, characterized in that, The testing business management method also includes: Receive the query message sent by the client; Match the test order corresponding to the query message, obtain the test result corresponding to the test order, and send it to the client.

5. The testing business management method according to claim 1, characterized in that, The step of synchronizing the detection order and the order status information to the customer and the corresponding salesperson information includes: generating a status synchronization email and sending it to the salesperson, wherein the status synchronization email includes the customer information, the detection information and the order status information; The step of updating the order status information of the test order to "pending sample receipt" includes: generating a status synchronization email and sending it to the salesperson. The status synchronization email includes the customer information, the test information, and the order status information updated to "pending sample receipt". The step of updating the order status information of the detected order to "in detection" includes: generating the status synchronization email and sending it to the salesperson, wherein the status synchronization email includes the customer information, the detection information, and the order status information updated to "in detection"; The step of updating the order status information of the inspection order to "completed" includes: generating the status synchronization email and sending it to the salesperson. The status synchronization email includes the customer information, the inspection information, and the order status information updated to "completed".

6. The testing business management method according to claim 1, characterized in that, The step of synchronizing the detected order and the order status information to the customer and the corresponding salesperson information includes: generating a status push message and sending it to the client, wherein the status push message includes the order status information; The step of updating the order status information of the inspection order to "pending sample receipt" includes: generating the status push message and sending it to the client, wherein the status push message includes the order status information updated to "pending sample receipt"; The step of updating the order status information of the detected order to be in the detection includes: generating the status push message and sending it to the client, wherein the status push message includes the order status information updated to be in the detection; The step of updating the order status information of the detected order to "completed" includes: generating the status push message and sending it to the client, wherein the status push message includes the updated order status information as "completed".

7. The testing business management method according to claim 1, characterized in that, The step of simultaneously acquiring the testing information of the testing order and sending it to the testing terminal includes: using the testing information to generate a test table to be filled, and exporting the test table to be filled with the testing data to the testing terminal; The receipt of detection data corresponding to the detection information uploaded by the detection terminal includes: receiving the test table filled with the detection data uploaded by the detection terminal.

8. The testing business management method according to claim 1, characterized in that, After updating the order status information of the inspection order to "completed", the following steps are included: Generate a settlement statement corresponding to the inspection order and send it to the customer; In response to receiving the invoicing information sent by the client and the confirmation of receipt message uploaded by the finance department, an invoice issuance request is sent to the finance department; The invoice file uploaded to the testing order by the finance department has been received.

9. The testing business management method according to any one of claims 1 to 8, characterized in that, After receiving the order information sent by the client, and before creating a testing order that includes the order information, the process includes: sending the order information to the client for order information review. The creation of the testing order that includes the order information includes: in response to the result of the order information review being passed, creating the testing order corresponding to the order information.

10. The testing business management method according to claim 9, characterized in that, The process of receiving order information sent by the client includes: The system receives authentication information sent by the client, which includes at least one of the following: customer type, real-name authentication information, company name, unified social credit code, and invoicing information. The authentication information is sent to the client for verification. If the authentication information is approved, the client's order placement permission will be granted.

Images