Information synchronization method, device and equipment

Abstract

The present invention provides an information synchronization method, device, and equipment, belonging to the field of computer information processing technology. The information synchronization method for a server of the present invention comprises: receiving order data sent by a client; sending the order data to a target data system among multiple data systems communicatively connected to the server through a first synchronization task; obtaining order business data fed back by the target data system based on the order data through a second synchronization task; and sending the order business data to the client. The technical solution of the present invention realizes real-time updating of order data between an e-commerce platform and third-party merchants, thereby improving the efficiency of order data synchronization and updating.

Description

Technical Field

[0001] The present invention relates to the field of computer information processing technology, and in particular to an information synchronization method, device and equipment. Background Art

[0002] Currently, when e-commerce platforms connect data with third-party merchants, students need to access product and order information. Product information includes basic information, price, and inventory, while order information includes order amount, product details, payment information, shipping status, and logistics information. The current mainstream integration method is for the e-commerce platform to provide a complete interface. The connecting merchant develops code according to the interface specifications, and both parties complete data exchange through the interface using an agreed-upon encryption method. Interface encryption schemes mainly include data encryption, data signing and verification, and token authorization and authentication mechanisms. The advantages of this interface-based integration are ease of use, real-time, security, scalability, and low maintenance costs. However, this requires both parties to have a complete development environment, including technical personnel for interface development, and a complete testing and production environment. However, most third-party merchants do not have interface integration capabilities and do not support data exchange through this method, resulting in low efficiency in order data exchange between e-commerce platforms and third-party merchants. Summary of the Invention

[0003] The present invention provides an information synchronization method, device and equipment, which solve the problem of low efficiency in order data interaction between an e-commerce platform and third-party merchants.

[0004] In order to solve the above technical problems, the technical solutions of the present invention are as follows:

[0005] An embodiment of the present invention provides an information synchronization method for a server, comprising:

[0006] Receive order data sent by the client;

[0007] Sending the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task;

[0008] Obtaining, through a second synchronization task, order business data fed back by the target data system based on the order data;

[0009] The order business data is sent to the client.

[0010] Optionally, sending the order data to a target data system among a plurality of data systems communicatively connected to the server through the first synchronization task includes:

[0011] The order data is sent to a target data system among a plurality of data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task.

[0012] Optionally, obtaining, through a second synchronization task, order business data fed back by the target data system based on the order data includes:

[0013] Through the second synchronization task, according to the second preset synchronization frequency, the order business data read and fed back by the target data system from the order interface table is obtained, and the order interface table includes: multiple order business data, and the order business data includes at least: order logistics information, order product information and order identification information.

[0014] Optionally, after sending the order data to a target data system among a plurality of data systems communicatively connected to the server, the method further includes:

[0015] When the status of the order data changes, the latest status of the order data is sent to the target data system among the multiple data systems connected to the server through a synchronization task; the status of the order data includes: pre-sale return or split order delivery, online cancellation or update of the order.

[0016] Optionally, the information synchronization method further includes:

[0017] Obtaining commodity inventory information in the target data system through a third synchronization task and at a third preset synchronization frequency;

[0018] The commodity inventory information is displayed in a visual manner.

[0019] An embodiment of the present invention further provides an information synchronization device for a server, comprising:

[0020] The first receiving module is used to receive order data sent by the client;

[0021] a first sending module, configured to send the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task;

[0022] A first acquisition module is configured to acquire, through a second synchronization task, order business data fed back by the target data system based on the order data;

[0023] The first sending module is further used to send the order business data to the client.

[0024] An embodiment of the present invention further provides an information synchronization method for a client, the method comprising:

[0025] Generate order data;

[0026] Sending the order data to the server;

[0027] Receive order business data sent by the server, the order business data is obtained through a target data system based on the order data feedback, and the target data system is one or more of a plurality of data systems communicatively connected to the server.

[0028] An embodiment of the present invention further provides an information synchronization device for a client, comprising:

[0029] Generation module, used to generate order data;

[0030] A second sending module, configured to send the order data to a server;

[0031] The second receiving module is used to receive the order business data sent by the server. The order business data is obtained by the target data system through the first synchronization task feedback based on the order data. The target data system is one or more of the multiple data systems that are communicatively connected to the server.

[0032] An embodiment of the present invention further provides a computing device, comprising: a processor and a memory storing a computer program, wherein the computer program executes the above method when executed by the processor.

[0033] An embodiment of the present invention further provides a computer-readable storage medium storing instructions, which, when executed on a computer, enable the computer to execute the above method.

[0034] The above solution of the present invention includes at least the following beneficial effects:

[0035] The solution of the present invention receives order data sent by the client; sends the order data to a target data system among multiple data systems communicatively connected to the server through a first synchronization task; obtains order business data fed back by the target data system based on the order data through a second synchronization task; and sends the order business data to the client, thereby realizing real-time update of order data between the e-commerce platform and third-party merchants, and improving the efficiency of order data synchronization and update. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 is a flow chart of a method for synchronizing information on a server provided by an embodiment of the present invention;

[0037] Figure 2 is a flowchart of a method for synchronizing information on a client provided by an embodiment of the present invention;

[0038] Figure 3This is a sales order information synchronization flow chart provided by an embodiment of the present invention;

[0039] Figure 4 This is a flowchart of updating order information synchronization provided by an embodiment of the present invention;

[0040] Figure 5 This is a flowchart of order logistics information synchronization provided by an embodiment of the present invention;

[0041] Figure 6 This is a flowchart of canceling order information synchronization provided by an embodiment of the present invention;

[0042] Figure 7 is a structural diagram of an information synchronization device for a server provided by an embodiment of the present invention;

[0043] Figure 8 is a structural diagram of an information synchronization device for a client provided by an embodiment of the present invention;

[0044] Figure 9 It is a structural diagram of a computing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0045] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0046] like Figure 1 As shown, an embodiment of the present invention provides an information synchronization method for a server, the method comprising:

[0047] Step 11: Receive order data sent by the client;

[0048] Step 12: Sending the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task;

[0049] Step 13: Obtain the order business data fed back by the target data system based on the order data through a second synchronization task;

[0050] Step 14: Send the order business data to the client.

[0051] In this embodiment, the server first receives order data sent from the client. The client can send order data through a web page, APP or API. The order data sent by the client includes order details, such as product information, purchase quantity, user information, payment information, etc. The order data is sent to the server through the network in a specific data format, such as JSON, XML, etc.

[0052] After receiving this data, the server will perform preliminary validity verification to ensure that the data format is correct, the fields are complete, and that it meets the expected business logic requirements;

[0053] After verifying that the order data is correct, the server will determine which data systems the order data needs to be synchronized to based on business logic and configuration information;

[0054] These data systems may include inventory management systems, financial systems, logistics systems, etc. The server executes the first synchronization task to accurately and promptly send the order data to the designated target data system. During this process, the server must ensure the integrity and consistency of the data to avoid data loss or corruption during transmission. After successfully sending the order data to the target data system, the server waits for these systems to process the order and generate corresponding business data, such as inventory change information, payment status, and logistics order numbers. To obtain this business data, the server executes the second synchronization task.

[0055] The second synchronization task includes polling the API of the target data system, listening for response messages in the message queue, or querying the shared database. Once the business data is received, the server will perform necessary verification and integration to ensure that the data matches the original order data and meets the business logic requirements. After successfully obtaining and verifying the order business data, the server will organize the data into a format that the client can understand and return it to the client through the network. After receiving this data, the client will parse and display it so that the user can view the order processing status and results in real time, such as successful payment, inventory reduction, logistics information, etc. In this way, the entire order processing process completes the closed loop from the client to the server, to multiple data systems, and finally returns to the client.

[0056] In an optional embodiment of the present invention, step 12 may include:

[0057] Step 121 : Sending the order data to a target data system among a plurality of data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task.

[0058] In this embodiment, the server will receive the order data sent by the client and, after necessary verification and preprocessing, will trigger the execution of the first synchronization task, which is designed to be specifically responsible for synchronizing the order data to the specified data system; before the synchronization task starts, the server needs to determine which data systems are the target data systems that need to receive the order data based on the business logic and configuration information; these target data systems include inventory management systems, order processing systems, logistics information systems, etc. The first preset synchronization frequency defines the frequency at which the order data is sent to the target data system, and this frequency can be set according to actual needs, such as synchronizing once per second, per minute, per hour or per day; the selection of the synchronization frequency needs to balance the relationship between data real-time and system load to ensure that the data can be updated in a timely manner without causing excessive pressure on the target data system; when all target data systems have successfully received the order data and returned confirmation, the first synchronization task is completed. At this time, the server can notify the client or other related systems of the results of the synchronization operation so that subsequent business processes can continue.

[0059] In an optional embodiment of the present invention, step 13 may include:

[0060] Step 131, through the second synchronization task, according to the second preset synchronization frequency, obtain the order business data read and fed back by the target data system from the order interface table, the order interface table includes: multiple order business data, the order business data includes at least: order logistics information, order product information and order identification information.

[0061] In this embodiment, the server starts the second synchronization task according to business needs. The main responsibility of this task is to obtain order business data from the target data system at a specific frequency. Before the task is started, a second preset synchronization frequency needs to be set. This frequency determines how often the system performs data acquisition operations to ensure the timeliness of the data and the effective use of system resources. The synchronization frequency may vary depending on factors such as business needs, data volume, and system processing capabilities. It can be every minute, every hour, every day, or a longer time interval. The second synchronization task needs to know clearly which target data system to obtain data from. The order interface table stores multiple order business data records, and each record contains detailed information about a certain order. This information includes at least: order logistics information, which is used to describe the logistics status, transportation method, delivery address, and estimated delivery time of the order goods; order product information, which is used to list the product name, quantity, unit price, total price, product description, picture, etc. contained in the order; order identification information, which is used to uniquely identify the order information, such as order number, order creation time, customer ID, etc. According to the second preset synchronization frequency, the second synchronization The first task periodically performs the following operations: It connects to the target data system, establishing a connection with the target data system through the appropriate communication protocol; queries the order interface table, sending a query request to the target data system, specifying the order business data range to be retrieved, such as the time range and order status; receives and parses data, receiving the returned order business data from the target data system and parsing it into a format that the server or data synchronization system can understand and process; verifies data integrity, checking that the received data is complete and contains all required fields and information; if data is missing or formatted incorrectly, it will be necessary to resynchronize with the target data system or log an error; once all order business data from the target data system has been successfully retrieved and processed, the second synchronization task is complete. At this point, the relevant systems or personnel can be notified of the synchronization results to facilitate subsequent business process processing or data analysis.

[0062] In an optional embodiment of the present invention, after sending the order data to a target data system among a plurality of data systems communicatively connected to the server, the method further includes:

[0063] When the status of the order data changes, the latest status of the order data is sent to the target data system among the multiple data systems connected to the server through a synchronization task; the status of the order data includes: pre-sale return or split order delivery, online cancellation or update of the order.

[0064] In this embodiment, the server monitors the status changes of order data in real time. When a change in the status of order data is detected, such as pre-sales return, split order and delivery, online cancellation or update of order, etc., the server will accurately identify the specific type of change, including parsing the status field in the order data and judging the current status of the order based on the preset enumeration value or status code; after determining the type of status change of the order data, the server will trigger a synchronization task to handle the change, and the synchronization task can synchronize the status change information to other data systems; before triggering the synchronization task or during the execution of the task, it is necessary to determine which target data systems will receive the latest status of the order data, where the target data system can be an ERP system; the data sent by the synchronization task includes the latest status information of the order data, such as the order number, status change time, new status details, and other metadata related to the order status change; the synchronization task establishes a connection with the target data system through an appropriate communication protocol and sends the prepared order status data. The sending process also requires authentication, data encryption, and error handling to ensure data security and transmission reliability. After receiving the order status data, the target data system will verify and process it. If the data is successfully received and processed, the target data system may return a confirmation message to the server, indicating that the synchronization operation is complete. If data reception fails or an error occurs during processing, the target data system may also return an error message so that the server can perform appropriate error handling or retry the operation. When all target data systems successfully receive the latest status information of the order data without any errors or exceptions, the synchronization task is completed. At this point, the server can update the synchronization status flag of the order data so that subsequent operations or queries can accurately reflect the latest status of the order data.

[0065] In an optional embodiment of the present invention, the information synchronization method further includes:

[0066] Obtaining commodity inventory information in the target data system through a third synchronization task and at a third preset synchronization frequency;

[0067] The commodity inventory information is displayed in a visual manner.

[0068] In this embodiment, the server obtains product inventory information from the target data system through a third synchronization task at a third preset synchronization frequency, so that subsequent operations such as inventory monitoring and sales decisions can be based on the latest data. Based on the obtained product inventory information, the server displays this information through a user interface (UI) view. The content displayed in the view typically includes basic product information, inventory quantity, inventory status, etc. Depending on specific needs, advanced information such as inventory trend charts and sales forecasts may also be displayed. In addition to displaying information, the view may also provide a series of interactive functions, such as inventory adjustment, order generation, and alarm settings, to support users' inventory management and business operation needs.

[0069] A specific embodiment of an information synchronization method for a server provided by an embodiment of the present invention is as follows:

[0070] Step 1: Get the order data sent by the client;

[0071] Specifically, after the client places an order on the e-commerce platform, the order data to be shipped is generated after the review and payment process (the shipping order contains order type data) and the order data to be shipped is sent to the server.

[0072] Step 2: Sending the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task;

[0073] Specifically, the server sends the order data to a target data system among multiple data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task.

[0074] Step 3: Obtain the order business data fed back by the target data system based on the order data through a second synchronization task;

[0075] Specifically, the server obtains the order business data read and fed back by the target data system from the order interface table through the second synchronization task according to the second preset synchronization frequency. The order interface table includes: multiple order business data, and the order business data includes at least: order logistics information, order product information and order identification information; in the above process, after receiving the order data, the target data system obtains different interfaces from the order interface table according to the type of order data to process the order data and generate order business data, wherein, when the order data is a sales order, the corresponding interface is the sales data interface, when the order data is a cancellation order, the corresponding interface is the cancellation data interface, and when the order data is an update order, the corresponding interface is the update data interface; when the order type data is a sales order, the server calls the sales interface every 5 minutes to obtain the order information sent by the client, such as Figure 3As shown, the order information is reviewed by the client before being sent; when the order type data is an update order, the server calls the update interface every 5 minutes to obtain the order data sent by the client, such as Figure 4 As shown, for the commodity inventory information stored on the server, a full update is performed every 24 hours; when the order type data is a cancel order, the server calls the cancel interface once every 1 minute to obtain the order data sent by the client, such as Figure 6 As shown; when the status of the order data changes, the latest status of the order data is sent to the target data system in the multiple data systems that are communicatively connected to the server through the synchronization task; the status of the order data includes: pre-sale order return or split order out of the warehouse, online cancellation or update of the order; when the order data is a sales order, the product inventory information is compared with the order data to obtain comparison result data; when the order type data is a canceled order, the server writes the cancellation status to the product inventory information every 1 minute, and changes the order status from pending shipment to expired; when the order type data is an updated order, the server calls the update order interface every 5 minutes to update the inventory, price, validity period and other information to the product inventory information of the server;

[0076] Step 4: Obtain product inventory information in the target data system through a third synchronization task at a third preset synchronization frequency; and display the product inventory information in a visual format.

[0077] Step 5: Send the order processing data to the client.

[0078] In the above embodiment of the present invention, the server needs to be able to connect to multiple data systems, such as an ERP database, through a local area network. The server can execute all the above synchronization task modules through a synchronization tool, and can set a timer to regularly run corresponding synchronization tasks to synchronize related orders or data. The timer can be set to synchronize different synchronization tasks at different frequencies or periods. The synchronization task can respond to the following operations:

[0079] "Execute": Click the "Execute" button and the task will be executed once immediately;

[0080] "Pause" / "Resume": When a task is in the running state, you can click the "Pause" button and the task status will change to "Paused". At this time, click the "Resume" button and the task status will change to "Running".

[0081] "Delete": This button will delete the scheduled task.

[0082] Table 1 is a task description (the execution frequency in the table is the default frequency of program initialization and can be adjusted according to specific business):

[0083] Table 1 Task description table

[0084]

[0085] The above synchronization tools can be implemented through interfaces during the communication between the server and the data system, as shown in Table 2:

[0086] Table 2 Interface List

[0087]

[0088] Order process such as Figure 3 shown.

[0089] Process description: After downstream customers (drug stores, etc.) place an order on the server platform, an order to be shipped is generated after review and payment. The order information is synchronized to the interface table of the commercial company's ERP system through the ERP docking tool every 5 minutes. The commercial company's technical staff independently develops an order extraction and transfer function to extract the order to the invoicing interface, and completes the subsequent invoicing and delivery process (the invoicing and delivery process within the commercial company's ERP can be arranged according to business conditions).

[0090] Product information update process Figure 4 shown.

[0091] Process description: The commercial company's technical staff provides a view of product information to be updated (including salable inventory, price, expiration date, etc.). The ERP integration tool directly obtains the information to be updated from the view and updates the inventory, price, and expiration date information to the server platform.

[0092] The order logistics information writing back process is as follows Figure 5 shown.

[0093] Process Description: A commercial company technician writes the logistics information for completed ERP outbound orders into the logistics information interface tables (ydc_shipment and ydc_shipment_item). Every five minutes, the ERP integration tool retrieves the logistics information for orders with a rewrite_state of 0 from this table and updates it to the Yaodoucai platform. Upon a successful update, the program automatically changes the rewrite_state to 1. If the update fails, it changes the rewrite_state to 9 (with three retries). If all three retries fail, the rewrite_state is finally changed to 99. Automatic retries will no longer occur, requiring manual intervention.

[0094] When the entire order is shipped, the actual quantity of ydc_shipment_item remains consistent with the original quantity.

[0095] When splitting orders for shipment, the actual shipment quantity of ydc_shipment_item can be inconsistent. This is written back based on the actual shipment. The current version does not involve splitting orders for shipment.

[0096] Pre-sale return, order splitting and delivery process.

[0097] Functional Overview: This process addresses situations where some items are under-delivered in ERP. When shipping a full order, the actual shipment quantity in ydc_shipment_item must match the original quantity. However, this is not the case when shipping split orders. For example, the original order, 81758495870, has two details: a small order quantity of 3 for Ganmaotong (Gaogantong) and 8 for Niuhuang Jiedu Pian (Niuhuang Jiedu Pian). During ERP invoicing, it was discovered that only 6 Niuhuang Jiedu Pian packets were in stock. After communicating with the buyer, only 6 were shipped, and the remaining 2 were canceled. Therefore, the actual shipment quantity in ERP is 3 Ganmaotong (Gaogantong) and 6 Niuhuang Jiedu Pian packets. This data is then written back to the platform in ydc_shipment_item. The original quantity (original_num) remains unchanged; it corresponds to the platform order quantity. The actual shipment quantity (real_num) is filled in. The remaining 8 - 6 = 2 is automatically considered a canceled quantity.

[0098] Online order cancellation process Figure 6 shown.

[0099] Process description: Downstream customers (pharmacy, etc.) cancel orders online on the server platform. The ERP integration tool writes the cancellation status to the order information interface table (ydc_order_header) of the commercial company's ERP system every minute, and changes the order status (field: order_state) from Pending Shipment: 3 to Expired: 100. Subsequent invoicing and delivery processes in the ERP system must determine whether the order has been canceled online to avoid losses to the commercial company caused by online order cancellation at the same time as the goods are shipped.

[0100] The solutions described in the above embodiments of the present invention have the following technical effects:

[0101] (1) No third-party vendor development and maintenance is required; the implementation plan and deployment process are all completed by the server platform.

[0102] (2) Real-time data updates can be achieved in different business scenarios.

[0103] (3) It has strong scalability and can be updated and upgraded at any time according to the different business requirements of third-party merchants.

[0104] (4) Simple deployment, the entire deployment process takes less than 5 minutes.

[0105] (5) It is convenient for third-party merchants to operate and maintain. They only need to initialize the data required by the ERP synchronization tool in their original system. The remaining synchronization and update operations are all automatically completed by the ERP synchronization tool.

[0106] The implementation and deployment process of the technical solution provided by the embodiment of the present invention is mainly completed on the server side, reducing the development and maintenance work of the client; it can realize real-time update of order data between e-commerce platforms and third-party merchants in different business scenarios, and improve the efficiency of order data synchronization and update.

[0107] like Figure 2 As shown, an embodiment of the present invention provides an information synchronization method for a client, the method comprising:

[0108] Step 21, generate order data;

[0109] Step 22: Send the order data to the server;

[0110] Step 23: Receive the order business data sent by the server, wherein the order business data is obtained through a target data system based on the order data feedback, and the target data system is one or more of the multiple data systems in communication with the server.

[0111] In this embodiment, the client generates order data based on the name, quantity, price, delivery address, user information, etc. of the purchased goods; after the order data is generated, the client sends the order data to the server through the network, such as an HTTP request; after the server receives the order data, it processes the order data through a target data system that is in communication with the server to obtain order business data, and sends the order business data to the client through the server.

[0112] like Figure 7 As shown, an embodiment of the present invention provides an information synchronization device 70 for a server, comprising:

[0113] The first receiving module 71 is used to receive order data sent by the client;

[0114] A first sending module 72 is configured to send the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task;

[0115] A first acquisition module 73 is configured to acquire, through a second synchronization task, order business data fed back by the target data system based on the order data;

[0116] The first sending module 72 is further configured to send the order business data to the client.

[0117] Optionally, the first sending module 72 is specifically configured to:

[0118] The order data is sent to a target data system among a plurality of data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task.

[0119] Optionally, the first acquisition module 73 is specifically configured to:

[0120] Through the second synchronization task, according to the second preset synchronization frequency, the order business data read and fed back by the target data system from the order interface table is obtained, and the order interface table includes: multiple order business data, and the order business data includes at least: order logistics information, order product information and order identification information.

[0121] Optionally, after sending the order data to a target data system among a plurality of data systems communicatively connected to the server, the method further includes:

[0122] When the status of the order data changes, the latest status of the order data is sent to the target data system among the multiple data systems connected to the server through a synchronization task; the status of the order data includes: pre-sale return or split order delivery, online cancellation or update of the order.

[0123] Optionally, the information synchronization device 70 further includes:

[0124] The second acquisition module 74 is configured to acquire the commodity inventory information in the target data system through a third synchronization task and according to a third preset synchronization frequency;

[0125] The display module 75 is used to display the commodity inventory information in a visual manner.

[0126] It should be noted that this device is a device corresponding to the above-mentioned server-side method, and all implementation methods of the above-mentioned server-side method are applicable to the embodiments of this device and can achieve the same technical effects.

[0127] like Figure 8 As shown, an embodiment of the present invention provides an information synchronization device 80 for a client, comprising:

[0128] A generating module 81 is used to generate order data;

[0129] A second sending module 82 is used to send the order data to the server;

[0130] The second receiving module 83 is used to receive the order business data sent by the server, and the order business data is obtained by the target data system according to the order data feedback. The target data system is one or more of the multiple data systems in communication with the server.

[0131] It should be noted that this device is a device corresponding to the above-mentioned client-side method. All implementation methods in the above-mentioned client-side method embodiment are applicable to this embodiment and can achieve the same technical effect.

[0132] like Figure 9 As shown, an embodiment of the present invention further provides a computing device 90, including a processor 91, a memory 92, and a program or instruction stored in the memory 92 and executable on the processor 91. When the program or instruction is executed by the processor 91, the various processes of the above-mentioned information synchronization method embodiment are implemented and can achieve the same technical effect. To avoid repetition, they are not described here. It should be noted that the computing device in the embodiment of the present invention includes the above-mentioned mobile electronic device and non-mobile electronic device.

[0133] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0134] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0135] In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0136] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0137] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0138] Stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or the portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the method of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, optical disks, and other media that can store program code.

[0139] In addition, it should be noted that, in the apparatus and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. Moreover, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but it is not necessary to perform them in chronological order, and some steps can be performed in parallel or independently of each other. For those of ordinary skill in the art, it will be understood that all or any steps or components of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or a network of computing devices in hardware, firmware, software or a combination thereof, which can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present invention.

[0140] Therefore, the purpose of the present invention can also be achieved by running a program or a group of programs on any computing device. The computing device can be a well-known general-purpose device. Therefore, the purpose of the present invention can also be achieved simply by providing a program product containing program code for implementing the method or device. That is to say, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any well-known storage medium or any storage medium developed in the future. It should also be pointed out that in the device and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. In addition, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but do not necessarily need to be performed in chronological order. Certain steps can be performed in parallel or independently of each other.

[0141] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. An information synchronization method, characterized in that: For a server, the method includes: Receive order data sent by the client; Sending the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task; Obtaining, through a second synchronization task, order business data fed back by the target data system based on the order data; Sending the order business data to the client; causing the client to generate order data; sending the order data to the server; receiving the order business data sent by the server, wherein the order business data is obtained through feedback from the order data by the target data system; The step of sending the order data to a target data system among a plurality of data systems in communication with the server through the first synchronization task includes: Sending the order data to a target data system among a plurality of data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task; Specifically, the server receives the order data sent by the client, verifies and pre-processes it, and then executes the first synchronization task; the first synchronization task is used to synchronize the order data to the specified data system; before the first synchronization task starts, the server determines the target data system that needs to receive the order data based on business logic and configuration information; the target data system includes at least one of the inventory management system, order processing system, and logistics information system; the first preset synchronization frequency is the frequency at which the order data is sent to the target data system, which is selected by balancing the relationship between data real-time and system load; after all target data systems have successfully received the order data and returned confirmation, the first synchronization task is completed, and the server notifies the client or related system of the result of the synchronization operation; After sending the order data to a target data system among a plurality of data systems communicatively connected to the server, the method further includes: When the status of the order data changes, the latest status of the order data is sent to a target data system among multiple data systems in communication with the server through a synchronization task; the status of the order data includes: pre-sale return or split order delivery, online cancellation or update of the order; The step of obtaining the order business data fed back by the target data system based on the order data through the second synchronization task includes: Obtaining, through a second synchronization task and at a second preset synchronization frequency, order business data read and fed back by the target data system from an order interface table, wherein the order interface table includes: a plurality of order business data, and the order business data includes at least: order logistics information, order product information, and order identification information; The information synchronization method further includes: Obtaining commodity inventory information in the target data system through a third synchronization task and at a third preset synchronization frequency; Displaying the commodity inventory information in a visual manner; Wherein, when the order data is a sales order, the commodity inventory information is compared with the order data to obtain comparison result data; When the order type data is a canceled order, the server will write the cancellation status to the product inventory information every 1 minute and change the order status from pending shipment to expired; When the order type data is an update order, the server calls the update order interface every 5 minutes to update the inventory, price, and validity period to the commodity inventory information of the server.

2. An information synchronization device, characterized in that: For servers, including: The first receiving module is used to receive order data sent by the client; a first sending module, configured to send the order data to a target data system among a plurality of data systems communicatively connected to the server through a first synchronization task; A first acquisition module is configured to acquire, through a second synchronization task, order business data fed back by the target data system based on the order data; The first sending module is further configured to send the order business data to the client; enable the client to generate order data; send the order data to the server; and receive the order business data sent by the server, wherein the order business data is obtained through feedback from the target data system based on the order data. The step of sending the order data to a target data system among a plurality of data systems in communication with the server through the first synchronization task includes: Sending the order data to a target data system among a plurality of data systems communicatively connected to the server according to a first preset synchronization frequency through a first synchronization task; Specifically, the server receives the order data sent by the client, verifies and pre-processes it, and then executes the first synchronization task; the first synchronization task is used to synchronize the order data to the specified data system; before the first synchronization task starts, the server determines the target data system that needs to receive the order data based on business logic and configuration information; the target data system includes at least one of the inventory management system, order processing system, and logistics information system; the first preset synchronization frequency is the frequency at which the order data is sent to the target data system, which is selected by balancing the relationship between data real-time and system load; after all target data systems have successfully received the order data and returned confirmation, the first synchronization task is completed, and the server notifies the client or related system of the result of the synchronization operation; After sending the order data to a target data system among a plurality of data systems communicatively connected to the server, the method further includes: When the status of the order data changes, the latest status of the order data is sent to a target data system among multiple data systems in communication with the server through a synchronization task; the status of the order data includes: pre-sale return or split order delivery, online cancellation or update of the order; The step of obtaining the order business data fed back by the target data system based on the order data through the second synchronization task includes: Obtaining, through a second synchronization task and at a second preset synchronization frequency, order business data read and fed back by the target data system from an order interface table, wherein the order interface table includes: a plurality of order business data, and the order business data includes at least: order logistics information, order product information, and order identification information; Among them, also include: Obtaining commodity inventory information in the target data system through a third synchronization task and at a third preset synchronization frequency; Displaying the commodity inventory information in a visual manner; Wherein, when the order data is a sales order, the commodity inventory information is compared with the order data to obtain comparison result data; When the order type data is a canceled order, the server will write the cancellation status to the product inventory information every 1 minute and change the order status from pending shipment to expired; When the order type data is an update order, the server calls the update order interface every 5 minutes to update the inventory, price, and validity period to the commodity inventory information of the server.

3. A computing device, characterized in that include: A processor and a memory storing a computer program, wherein when the computer program is executed by the processor, the method according to claim 1 is performed.

4. A computer-readable storage medium, characterized in that The invention stores instructions which, when executed on a computer, cause the computer to execute the method according to claim 1 .

Images