Quick purchasing and warehousing system suitable for maintenance factory

Abstract

The invention provides a quick purchasing and warehousing system suitable for a maintenance shop, and the system can achieve the cross-system butt joint of a maintenance shop store system and an accessory supplier system, thereby achieving the purchasing linkage between the supplier system and a maintenance shop store, such as the query of an accessory supplier sales list, the quick warehousing of the maintenance shop store, one-key account checking and the like. The method effectively solves the complex operation problems of manual inputting, purchasing and warehousing and account checking in the process of purchasing the automobile parts by the maintenance shop store at present, can save the time cost of the maintenance shop store, and can improve the purchasing efficiency of the maintenance shop store.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a fast procurement and warehousing system suitable for repair shops. Background Technology

[0002] In the automotive aftermarket, parts suppliers and repair shops, as two core entities, are increasingly leveraging software systems to optimize their daily operations and adapt to the rapid development of the internet. Because their business scenarios differ, they typically require separate software systems tailored to their specific needs. However, the current process has significant flaws in the physical transaction stage: parts suppliers generate sales invoices in their systems, while repair shops must manually verify paper sales invoices and enter purchase information, ultimately requiring manual reconciliation of accounts at the end of the month. During this process, the two systems operate independently and cannot coordinate, necessitating manual matching, data entry, and reconciliation, leading to inefficiency and difficulties in data traceability. Summary of the Invention

[0003] This specification describes one or more embodiments of a rapid procurement and warehousing system suitable for repair shops. It is able to at least partially overcome the aforementioned technical problems.

[0004] This specification provides one or more embodiments of a rapid procurement and warehousing system suitable for repair shops, the system comprising: The interface module is used for data interaction with the supplier's system; The binding module is used to create and maintain the binding relationship between the repair shop store system and the supplier system; The procurement management module is used to respond to the procurement and warehousing request initiated by the repair shop store system, call the binding module to query the supplier system bound to the repair shop store system, and determine the target supplier system according to the selection operation of the repair shop store system; and call the docking module to access the target supplier system to obtain the target sales order, create a purchase order according to the target sales order, and associate and store the target sales order and the purchase order locally to realize the warehousing registration. The procurement management module is also used to: respond to a reconciliation request, locate the purchase order based on the supplier system name in the invoice, verify the invoice based on the purchase order and the target sales order associated with the purchase order, and obtain the verification result.

[0005] As an optional implementation of the above system, the docking module is specifically used for: Assign a unique identifier to the supplier system; Configure the interface for accessing the supplier system; All interfaces accessing the same vendor system are associated with the vendor system's ID.

[0006] Specifically, the binding module is used for: Provide a binding operation interface for the repair shop store system, and create a binding relationship between the repair shop store system and the supplier system based on the binding operation of the repair shop store user.

[0007] As an optional implementation of the above system, after the procurement management module obtains the target supplier system in response to the procurement warehousing request, it generates a sales order query request based on the identifier of the target supplier system, the identifier of the repair shop store system, and the procurement warehousing request, and sends the sales order query request to the interface module. The interface module pre-stores tokens issued by each supplier system. After obtaining the sales order query request, it sends the token of the target supplier system and the query request to the target supplier system, so that the target supplier system can authenticate the maintenance and repair shop system based on the token and determine the access permissions, thereby determining whether the request content of the sales order query request is within the access permissions. If so, the sales order information is returned; otherwise, the sales order query request is rejected.

[0008] Specifically, the procurement management module is used for: After receiving the sales order information returned by the docking module, the sales order information is fed back to the repair shop store system; The target sales order is determined based on the selection operation of the repair shop store system, and the purchase order is created based on the target sales order.

[0009] Specifically, the procurement management module is used for: Create the aforementioned purchase order; Based on the accessory standard code recorded in the target sales order, map the accessory name in the target sales order to the accessory name in the local inventory list, and fill it in the purchase order; Match the quantity of accessories in the target sales order to the purchase order; Based on the received goods information, the accessories and their quantities in the purchase order are checked. If any discrepancies are found, the discrepancy category is marked.

[0010] As an optional implementation of the above system, the procurement management module is specifically used for: After the bill is verified, payment information is generated and submitted to the repair shop's store system.

[0011] As an optional implementation of the above system, the procurement management module is specifically used for: For the purchase orders that have already been settled, mark the purchase order and the target sales order associated with the purchase order.

[0012] Beneficial Effects: One or more embodiments of this specification provide a fast procurement and warehousing system suitable for repair shops. This system enables cross-system integration between the repair shop's system and the parts supplier's system, thereby achieving procurement linkage between the supplier system and the repair shop, such as querying parts supplier sales order lists, fast warehousing at the repair shop, and one-click reconciliation. It effectively solves the problems of complex manual entry and reconciliation operations currently faced by repair shops in purchasing auto parts. This invention can save repair shops time and improve their procurement efficiency. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a schematic diagram of a quick procurement and warehousing system for repair shops, which is described in one embodiment of this specification.

[0015] Figure 2 This is a timing diagram of the docking module involved in one embodiment of this specification in a specific implementation scenario.

[0016] Figure 3 This is a schematic diagram of the binding operation interface involved in one embodiment of this specification. Detailed Implementation

[0017] First, it should be noted that the terminology used in the embodiments of this invention is for the purpose of describing specific embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0018] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments in this specification, and not all of the embodiments. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0019] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0020] The following will provide a more detailed description of the quick procurement and warehousing system for repair shops described in this specification, in conjunction with the accompanying drawings and specific embodiments. However, this detailed description does not constitute a limitation on the embodiments of this specification.

[0021] In some embodiments, a fast procurement and warehousing system suitable for repair shops is provided, such as... Figure 1 As shown, the system mainly includes an interface module, a binding module, and a procurement management module.

[0022] The interface module is used to connect with the supplier system and exchange data with it. The interface module mainly provides the following functions: 1) Collect and screen compatible supplier systems, and register the information of the supplier systems in a table, including the supplier system name (usually the supplier name), interface, request method, interface parameter signature, encrypted message, etc.

[0023] 2) Clearly define the interface functions provided by each supplier's system. Basic requirements include interfaces for querying parts supplier sales order numbers and interfaces for querying sales order details.

[0024] 3) Determine the request and interaction method with the supplier interface; 4) Assign a unique identifier to the supplier system and associate all interfaces accessing the same supplier system with the supplier system ID; 5) Adapt and connect to the supplier's system.

[0025] Please refer to Figure 2 , Figure 2The diagram illustrates the timing of the above-mentioned interface module in a specific implementation scenario. In this scenario, the repair shop system needs to query data from parts supplier systems A, B, and X.

[0026] In this implementation scenario, the workflow of the interface module is as follows: First, complete the basic configuration for connecting with Parts Supplier System A, Parts Supplier System B, and Parts Supplier System X.

[0027] Secondly, identify the target supplier systems that need to be accessed (i.e., parts supplier system A, parts supplier system B, and parts supplier system X), and determine which interface of the target supplier system to call based on business needs. For example, if the repair shop store system needs to view the sales order list of parts suppliers, the interface module needs to call the interface provided by parts supplier system A, parts supplier system B, and parts supplier system X for querying the sales order list.

[0028] Next, the system calls the designated interface to access the parts supplier system and obtains the sales order list from each supplier system.

[0029] Finally, the sales order lists from various supplier systems are combined into structured data and returned to the procurement management module, which then returns the structured sales order list to the repair shop store system.

[0030] The binding module is used to create and maintain the binding relationship between the repair shop system and the supplier system. Specifically, the binding module is used to provide the repair shop system with, for example... Figure 3 The binding operation interface shown creates a binding relationship between the repair shop system and the supplier system IDs based on the binding operation of the repair shop user. Repair shop users can open the binding operation interface on the repair shop system and then enter the supplier system information to be bound (such as the supplier system name, ID, etc.), thereby achieving the binding between the repair shop system and the supplier system.

[0031] The procurement management module is used to connect with the repair shop system, respond to the business requests of the repair shop system, and call the connection module to obtain the data required by the repair shop, automatically generate purchase orders for the registration of auto parts in the warehouse, and automatically reconcile accounts, etc.

[0032] In an automated warehousing scenario, after a repair shop receives auto parts from a supplier, the shop's customer initiates a purchase and warehousing request through the repair shop's system. The procurement management module responds to this request by first calling the binding module to query the supplier systems bound to the repair shop's system and returning the results. Then, based on the customer's selection on the repair shop's system, it determines the target supplier system. Next, the procurement management module calls the interface module to access the target supplier system to obtain the target sales order. Based on the target sales order, it automatically creates a purchase order and associates the target sales order and the purchase order, storing them locally to complete the warehousing registration.

[0033] Optionally, repair shops can also query the supplier's sales order list and sales order details. For example, after receiving auto parts from a supplier, a repair shop can initiate a query request for the sales order list and sales order details to verify whether the quantity and type of parts received match the supplier's sales order at the time of shipment. The specific process is as follows: (1) Repair shop store users initiate a sales order list query request for the supplier through the repair shop store system.

[0034] (2) After receiving the sales order list query request, the procurement management module accesses the binding module to determine the supplier system identifier (ID).

[0035] (3) The procurement management module sends a sales order list query request with the supplier system identifier to the docking module. After the docking module determines the interface based on the supplier system identifier, it accesses the supplier system, obtains the sales order list, and returns it to the procurement management module.

[0036] (4) The procurement management module returns the sales order list to the repair shop store system.

[0037] (5) Repair shop store users can view the sales order list on the repair shop store system and select the sales order for which they want to view details.

[0038] (6) The repair shop store system initiates a sales order details query request.

[0039] (7) The procurement management module calls the binding module to obtain the supplier system identifier based on the sales order details query request, and then sends the supplier system identifier and sales order details query request to the docking module. The docking module accesses the supplier system and obtains the sales order content.

[0040] (8) The procurement management module sends the sales order content to the repair shop store system.

[0041] In the reconciliation scenario, repair shop customers initiate a reconciliation request through the repair shop system. They search for the purchase order based on the supplier system name in the bill, verify the bill based on the purchase order and the target sales order associated with the purchase order, and obtain the verification result.

[0042] Because a single supplier may have supply relationships with multiple repair shops, the supplier's system may store sales data from multiple repair shops. To achieve data isolation and confidentiality when retrieving data, ensuring that repair shops can only obtain sales data relevant to their own stores from the supplier's system, the following methods can be used in some implementations for data querying during procurement and warehousing.

[0043] Specifically, after the procurement management module receives the target supplier system in response to the procurement receipt request, it generates a sales order query request based on the target supplier system's identifier, the repair shop system's identifier, and the procurement receipt request. This sales order query request is then sent to the interface module. The interface module pre-stores tokens issued by each supplier system. After receiving the sales order query request, the interface module sends the target supplier system's token and the query request to the target supplier system. This allows the target supplier system to authenticate the repair shop system based on the token and determine access permissions. It then determines whether the content of the sales order query request falls within the access permissions (which can be set to only allow access to data related to the repair shop). If so, the sales order information is returned; otherwise, the sales order query request is rejected.

[0044] After receiving the sales order information from the interface module, the procurement management module feeds the sales order information back to the repair shop system. Based on the selection operation of the repair shop system, the target sales order is determined, and a purchase order is created based on the target sales order.

[0045] The specific process for creating a purchase order in the procurement management module is as follows: Create a new purchase order; Based on the accessory standard code (such as OE code) recorded in the target sales order, map the accessory name in the target sales order to the accessory name in the local inventory list and fill it in the newly created purchase order; Match the quantity of accessories in the target sales order to the purchase order; Based on the received goods information, verify the accessories and quantities in the purchase order. If any discrepancies are found, mark the category of the discrepancy for subsequent reconciliation.

[0046] Optionally, the procurement management module can also be used to generate payment information and submit it to the repair shop store system after the reconciliation statement has been verified.

[0047] Optionally, the procurement management module can also be used to: mark settled purchase orders and their associated target sales orders, thereby creating traceable inbound and reconciliation records.

[0048] The above describes a fast procurement and warehousing system for repair shops, as presented in the embodiments of this specification. This system enables cross-system integration between the repair shop's system and the parts supplier's system, thereby achieving procurement linkage between the supplier system and the repair shop. This includes features such as querying parts supplier sales order lists, fast warehousing for repair shops, and one-click reconciliation. It effectively solves the problems of complex manual entry and reconciliation operations currently faced by repair shops when purchasing auto parts. This invention can save repair shops time and improve their procurement efficiency.

[0049] It is understood that the structures illustrated in the embodiments of this specification do not constitute a specific limitation on the system of the embodiments of this specification. In other embodiments of the specification, the above system may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0050] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0051] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0052] It should be noted that the above examples are merely specific embodiments of the present invention, and the present invention is obviously not limited to the above embodiments, with many similar variations. All modifications that can be directly derived or conceived by those skilled in the art from the content disclosed in this invention should fall within the protection scope of this invention.

Claims

1. A rapid procurement and warehousing system suitable for repair shops, characterized in that, include: The interface module is used for data interaction with the supplier's system; The binding module is used to create and maintain the binding relationship between the repair shop store system and the supplier system; The procurement management module is used to respond to the procurement and warehousing request initiated by the repair shop store system, call the binding module to query the supplier system bound to the repair shop store system, and determine the target supplier system according to the selection operation of the repair shop store system; and call the docking module to access the target supplier system to obtain the target sales order, create a purchase order according to the target sales order, and associate and store the target sales order and the purchase order locally to realize the warehousing registration. The procurement management module is also used to: respond to a reconciliation request, locate the purchase order based on the supplier system name in the invoice, verify the invoice based on the purchase order and the target sales order associated with the purchase order, and obtain the verification result.

2. The system according to claim 1, characterized in that, The docking module is specifically used for: Assign a unique identifier to the supplier system; Configure the interface for accessing the supplier system; All interfaces accessing the same vendor system are associated with the vendor system's ID.

3. The system according to claim 1, characterized in that, The binding module is specifically used for: Provide a binding operation interface for the repair shop store system, and create a binding relationship between the repair shop store system and the supplier system based on the binding operation of the repair shop store user.

4. The system according to claim 1, characterized in that, After the procurement management module obtains the target supplier system in response to the procurement receipt request, it generates a sales order query request based on the identifier of the target supplier system, the identifier of the repair shop store system, and the procurement receipt request, and sends the sales order query request to the interface module. The interface module pre-stores tokens issued by each supplier system. After obtaining the sales order query request, it sends the token of the target supplier system and the query request to the target supplier system, so that the target supplier system can authenticate the maintenance and repair shop system based on the token and determine the access permissions, thereby determining whether the request content of the sales order query request is within the access permissions. If so, the sales order information is returned; otherwise, the sales order query request is rejected.

5. The system according to claim 4, characterized in that, The procurement management module is specifically used for: After receiving the sales order information returned by the docking module, the sales order information is fed back to the repair shop store system; The target sales order is determined based on the selection operation of the repair shop store system, and the purchase order is created based on the target sales order.

6. The system according to claim 5, characterized in that, The procurement management module is specifically used for: Create the aforementioned purchase order; Based on the accessory standard code recorded in the target sales order, map the accessory name in the target sales order to the accessory name in the local inventory list, and fill it in the purchase order; Match the quantity of accessories in the target sales order to the purchase order; Based on the received goods information, the accessories and their quantities in the purchase order are checked. If any discrepancies are found, the discrepancy category is marked.

7. The system according to claim 1, characterized in that, The procurement management module is specifically used for: After the bill is verified, payment information is generated and submitted to the repair shop's store system.

8. The system according to claim 1, characterized in that, The procurement management module is specifically used for: For the purchase orders that have already been settled, mark the purchase order and the target sales order associated with the purchase order.

Images