CN115391065A

CN115391065A - E-commerce data conversion method and E-commerce data conversion system

Info

Publication number: CN115391065A
Application number: CN202211066047.9A
Authority: CN
Inventors: 兰勇; 周富民
Original assignee: Hunan Happly Sunshine Interactive Entertainment Media Co Ltd
Current assignee: Hunan Happly Sunshine Interactive Entertainment Media Co Ltd
Priority date: 2022-09-01
Filing date: 2022-09-01
Publication date: 2022-11-25

Abstract

The application provides a method and a system for E-commerce data conversion, which are used for obtaining E-commerce data of at least one E-commerce platform according to an open interface protocol of at least one E-commerce platform; according to a preset unified standard interface protocol, E-commerce data is sent to an ERP system of a merchant through a unified E-commerce platform interface realized based on the same standard interface protocol; wherein, the ERP system is an Enterprise resource management (Enterprise resource planning) system; processing result data fed back by the ERP system are transmitted back to at least one e-commerce platform; and processing result data is obtained by processing the e-commerce data by the ERP system. According to the scheme, the e-commerce data of different e-commerce platforms are distributed to the ERP system according to the converted uniform standard interface protocol, so that the ERP system can be simultaneously accessed to a plurality of e-commerce platforms only by realizing the uniform standard interface protocol, and the load of the ERP system is reduced.

Description

E-commerce data conversion method and E-commerce data conversion system

Technical Field

The invention relates to the technical field of e-commerce, in particular to an e-commerce data conversion method and an e-commerce data conversion system.

Background

With the development of internet technology, online shopping using an e-commerce platform has become a widely used shopping mode for people. After a consumer selects and purchases goods on the e-commerce platform, the e-commerce platform can generate corresponding order data according to the operation of the consumer, then the order data is sent to an ERP system of a merchant accessing the e-commerce platform, and then the ERP system sends the corresponding goods to the consumer in an express mode according to the order data.

At present, a plurality of different e-commerce platforms exist in the market, each e-commerce platform has a set of customized open interface protocols, and the ERP system of a merchant needs to realize a plurality of open interface protocols when accessing the plurality of different e-commerce platforms, which causes heavy load to the ERP system.

Disclosure of Invention

In view of the above shortcomings in the prior art, the present invention provides a method and a platform for data transformation of an e-commerce to reduce the load of an ERP system.

The application provides a method for converting e-commerce data in a first aspect, which comprises the following steps:

acquiring e-commerce data of at least one e-commerce platform according to an open interface protocol of the at least one e-commerce platform;

according to a preset uniform standard interface protocol, the e-commerce data is sent to an ERP system of a merchant through a uniform e-commerce platform interface realized based on the uniform standard interface protocol; wherein, the ERP system is an enterprise resource management system;

returning the processing result data fed back by the ERP system to the at least one e-commerce platform; and the processing result data is obtained by processing the e-commerce data by the ERP system.

Optionally, the method further includes:

and synchronizing the pre-acquired inventory data of the multiple merchants to the at least one e-commerce platform through the message middleware.

Optionally, the e-commerce data includes order data;

the obtaining of the e-commerce data of at least one e-commerce platform according to the open interface protocol of the at least one e-commerce platform comprises:

selecting a distribution commodity to enter a distribution commodity pool, and putting the distribution commodity on the E-commerce platform;

after the E-commerce platform places an order, pulling order data from the E-commerce platform;

the method comprises the following steps of sending the e-commerce data to an ERP system of a merchant through a unified e-commerce platform interface realized based on the same standard interface protocol according to a preset unified standard interface protocol, wherein the ERP system comprises:

writing the order data into an order message queue;

according to a preset uniform standard interface protocol, sending order data in the order message queue to an ERP system of a corresponding target merchant through a uniform e-commerce platform interface realized based on the same standard interface protocol;

wherein the writing the order data into an order message queue includes:

determining a target merchant corresponding to the order data; the target merchant refers to a merchant to which the commodity contained in the order data belongs;

splitting the order data into a plurality of sub-order data according to the target commercial tenant; each piece of sub-order data corresponds to one target merchant;

writing the sub-order data into the order message queue;

alternatively, the first and second electrodes may be,

and if the order data only corresponds to one target merchant, directly writing the order data into the order message queue.

Optionally, the returning the processing result data fed back by the ERP system to the at least one e-commerce platform includes:

after the ERP system or a supplier background connected with the ERP system finishes delivery processing of the order data, acquiring a processing result of the order data, and performing delivery marking on the order data, thereby marking the order data as delivered; the processing result of the order data comprises an express company and a freight order number;

synchronizing the shipped mark and the processing result of the order data to the e-commerce platform through middleware;

after the e-commerce platform confirms that the order corresponding to the order data is completed, synchronizing the completed information of the order from the e-commerce platform through middleware, and synchronizing the completed information of the order to the ERP system.

Optionally, the e-commerce data includes after-sales order data:

the e-commerce platform responds to the operation of the user after applying for sale and generates the approved after-sale bill data;

pulling the after-sale bill data from the e-commerce platform through a middleware;

writing the order data into an after-sales order message queue;

according to a preset uniform standard interface protocol, sending the after-sale bill data in the after-sale bill message queue to an ERP system of a corresponding merchant through a uniform e-commerce platform interface realized based on the same standard interface protocol;

wherein the writing the order data into an after-sales order message queue includes:

splitting the after-sale single data into multiple sub after-sale single data; each piece of the sub after-sale order data corresponds to one merchant, and the commodities contained in the sub after-sale order data belong to the merchants corresponding to the sub after-sale order data;

writing the sub after-sale list data into the after-sale list message queue;

alternatively, the first and second liquid crystal display panels may be,

if the after-sales bill data only corresponds to one merchant, directly writing the after-sales bill data into the after-sales bill message queue;

the transmitting the processing result data fed back by the ERP system back to the at least one e-commerce platform comprises:

after confirming that the goods corresponding to the after-sale bill data are received in a supplier background connected with the ERP system or the ERP system, obtaining a message that the goods corresponding to the after-sale bill are received;

taking the received commodity information corresponding to the after-sales order as processing result data, and synchronizing the processing result data to the e-commerce platform through the middleware;

after the E-commerce platform transacts refund business according to the processing result data, obtaining a message of completing the refund of the after-sale bill from the E-commerce platform through a middleware;

and feeding back the message of completing the single refund after sale to the ERP system.

Optionally, the synchronizing, by the message middleware, the pre-acquired inventory data of the multiple merchants to the at least one e-commerce platform includes:

after the ERP system or a supplier background connected with the ERP system updates commodity inventory, updated inventory information is obtained;

if the newly added commodity corresponding to the updated inventory message is a distribution commodity, writing the updated inventory message into an inventory message queue;

and reading the updated inventory information from the inventory information queue through a multi-process script, and synchronizing the updated inventory information to the e-commerce platform through a middleware, so that the e-commerce platform updates own inventory data according to the updated inventory information.

Optionally, the method further includes:

the inventory data of the E-commerce platform is synchronized through middleware at regular time;

and establishing a mapping relation between the synchronous inventory data and a preset commodity mark so as to determine the current remaining inventory of each commodity.

A second aspect of the present application provides an electronic commerce data conversion system, including:

the system comprises an obtaining unit, a processing unit and a processing unit, wherein the obtaining unit is used for obtaining the e-commerce data of at least one e-commerce platform according to an open interface protocol of the at least one e-commerce platform;

the sending unit is used for sending the e-commerce data to an ERP system of a merchant through a unified e-commerce platform interface realized based on the same standard interface protocol according to a preset unified standard interface protocol; wherein, the ERP system is an enterprise resource management system;

the return unit is used for returning the processing result data fed back by the ERP system to the at least one e-commerce platform; and the processing result data is obtained by processing the e-commerce data by the ERP system.

Optionally, the method further includes:

and the synchronizing unit is used for synchronizing the pre-acquired inventory data of a plurality of merchants to the at least one e-commerce platform through the message middleware.

Optionally, the e-commerce data includes order data;

when the obtaining unit obtains the e-commerce data of at least one e-commerce platform according to the open interface protocol of the at least one e-commerce platform, the obtaining unit is specifically configured to:

when the sending unit sends the e-commerce data to the ERP system of the merchant through the unified e-commerce platform interface realized based on the same standard interface protocol according to a preset unified standard interface protocol, the sending unit is specifically configured to:

writing the order data into an order message queue;

wherein, the writing the order data into the order message queue includes:

writing the sub-order data into the order message queue;

alternatively, the first and second liquid crystal display panels may be,

Optionally, when the returning unit returns the processing result data fed back by the ERP system to the at least one e-commerce platform, the returning unit is specifically configured to:

after the ERP system or a supplier background connected with the ERP system finishes the delivery processing of the order data, acquiring a processing result of the order data, and executing delivery marking on the order data, thereby marking the order data as delivered; the processing result of the order data comprises an express company and an invoice number;

Optionally, the e-commerce data includes after-sales order data:

writing the order data into an after-sales order message queue;

splitting the after-sale single data into multiple sub-after-sale single data; each piece of the after-sale order data corresponds to one merchant, and the commodities contained in the after-sale order data belong to the merchant corresponding to the after-sale order data;

writing the sub after-sale list data into the after-sale list message queue;

alternatively, the first and second liquid crystal display panels may be,

if the after-sales order data only corresponds to one merchant, directly writing the after-sales order data into the after-sales order message queue;

when the returning unit returns the processing result data fed back by the ERP system to the at least one e-commerce platform, the returning unit is specifically configured to:

after confirming that the goods corresponding to the after-sale bill data are received in the ERP system or a supplier background connected with the ERP system, obtaining a message that the goods corresponding to the after-sale bill are received;

Optionally, when the synchronization unit synchronizes, through the message middleware, the inventory data of multiple merchants acquired in advance to the at least one e-commerce platform, the synchronization unit is specifically configured to:

after the ERP system or a supplier background connected with the ERP system updates the inventory of the goods, the updated inventory information is obtained;

Optionally, the synchronization unit is further configured to:

The application provides a method and a system for E-commerce data conversion, which are used for obtaining E-commerce data of at least one E-commerce platform according to an open interface protocol of at least one E-commerce platform; according to a preset uniform standard interface protocol, E-commerce data is sent to an ERP system of a merchant through a uniform E-commerce platform interface realized based on the same standard interface protocol; wherein, the ERP system is an Enterprise Resource management (Enterprise Resource Planning) system; processing result data fed back by the ERP system are transmitted back to at least one e-commerce platform; and processing result data is obtained by processing the e-commerce data by the ERP system. The scheme distributes the e-commerce data of different e-commerce platforms to the ERP system according to the converted uniform standard interface protocol, so that the ERP system can be simultaneously accessed to a plurality of e-commerce platforms only by realizing the uniform standard interface protocol, and the load of the ERP system is reduced.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a flowchart of a method for e-commerce data conversion according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of an e-commerce system according to an embodiment of the present disclosure;

fig. 3 is a timing diagram of a service logic provided in an embodiment of the present application;

fig. 4 is a flowchart of processing order data according to an embodiment of the present disclosure;

FIG. 5 is a sequence diagram of an order delivery method according to an embodiment of the present application;

FIG. 6 is a flowchart illustrating an exemplary process for providing post-sale order data according to an embodiment of the present disclosure;

FIG. 7 is a timing diagram illustrating an exemplary embodiment of an after-sales order processing system;

FIG. 8 is a flow chart of an embodiment of the present application for synchronization of inventory data;

FIG. 9 is a timing diagram illustrating an update of the inventory data according to an embodiment of the present application;

fig. 10 is a schematic architecture diagram of an e-commerce data conversion platform according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 1, a flowchart of a method for data conversion of an e-commerce according to an embodiment of the present application may include the following steps.

First, it is explained that each step in this embodiment may be specifically executed by a pre-constructed unified e-commerce platform.

S101, acquiring the E-commerce data of at least one E-commerce platform according to the open interface protocol of at least one E-commerce platform.

The e-commerce platform in step S101 may be understood as at least one external e-commerce platform connected to the unified e-commerce platform of the present invention.

Each e-commerce platform corresponds to an open interface protocol suitable for the e-commerce platform, and an e-commerce open platform interface of the e-commerce platform is configured based on the open interface protocol. For example, the e-commerce platform may include a pan, a skatecat, a kyoto, and so on, wherein the pan corresponds to an open interface protocol of the pan and an e-commerce open platform interface based on the protocol, and the kyoto corresponds to an open interface protocol of the pan and an e-commerce open platform interface based on the protocol.

The step S101 may be specifically executed by a middleware component (also referred to as a middleware synchronization program) of the unified e-commerce platform. The middleware component can pre-configure the open interface protocol of each external e-commerce platform, so that the middleware component can read e-commerce data of the e-commerce platform through the e-commerce open platform interface provided by the external e-commerce platform.

The e-commerce data described in this embodiment includes various data related to e-commerce activities, such as order data, after-sales order data, commodity inventory data, and commodity data.

And the commodity data can be pulled and synchronized to the unified platform by the middleware, and then matched and associated with the unified platform commodities to establish a corresponding relation.

And S102, according to a preset uniform standard interface protocol, the e-commerce data is sent to an ERP system of a merchant through a uniform e-commerce platform interface realized based on the same standard interface protocol.

The ERP system is an Enterprise Resource management (Enterprise Resource Planning) system.

The unified standard interface protocol is an interface protocol configured in the unified e-commerce platform of this embodiment. In step S102, the middleware component may convert the e-commerce data of different external e-commerce platforms in S101 into e-commerce data conforming to the above-mentioned unified standard interface protocol through the distribution open platform interface of the unified e-commerce platform.

Meanwhile, the ERP system of each merchant accesses the unified e-commerce platform of the embodiment through a unified e-commerce platform interface realized based on a unified standard interface protocol, and the unified e-commerce platform sends the e-commerce data which is converted and accords with the unified standard interface protocol to the ERP system of each merchant through the unified e-commerce platform interface.

It should be noted that the merchant described in this embodiment may be an external merchant cooperating with the unified e-commerce platform, or may be a merchant owned by the unified e-commerce platform.

And S103, returning the processing result data fed back by the ERP system to at least one e-commerce platform.

And processing result data is obtained by processing the e-commerce data by the ERP system.

After the ERP system receives the e-commerce data, the e-commerce data can be processed according to processing logic preset in the system. For example, after receiving order data, processing the order data according to a delivery flow according to the order data, after receiving after-sales order data, processing the after-sales order data according to a refund flow, and the like, the obtained processing result data is fed back to the unified e-commerce platform through the unified e-commerce platform interface, then the unified e-commerce platform transmits the processing result to the middleware component through the distribution open platform interface, and the middleware component feeds back the processing result to the external e-commerce platform through an e-commerce open platform interface of the external e-commerce platform.

Optionally, when the e-commerce data includes order data, in step S102, according to a preset unified standard interface protocol, the e-commerce data is sent to the ERP system of the merchant through a unified e-commerce platform interface implemented based on the same standard interface protocol, which includes:

determining a target merchant corresponding to the order data; wherein, the target merchant refers to the merchant to which the commodity contained in the order data belongs;

splitting order data into a plurality of sub-order data according to a target merchant; each part of sub-order data corresponds to one target merchant;

and according to a preset unified standard interface protocol, sending each part of sub-order data to the ERP system of the corresponding target merchant through a unified e-commerce platform interface realized based on the same standard interface protocol.

Correspondingly, in step S103, returning the processing result data fed back by the ERP system to at least one e-commerce platform includes:

and returning the express delivery data fed back by the ERP system to at least one e-commerce platform.

Optionally, when the e-commerce data includes the after-sale receipt data, in step S102, according to a preset uniform standard interface protocol, the e-commerce data is sent to the ERP system of the merchant through a uniform e-commerce platform interface implemented based on the same standard interface protocol, which includes:

splitting the after-sale list data into a plurality of after-sale lists; each sub after-sale bill corresponds to one merchant, and the commodities contained in the sub after-sale bills belong to the merchants corresponding to the sub after-sale bills;

and according to a preset uniform standard interface protocol, sending each sub-after-sale bill to the ERP system of the corresponding commercial tenant through a uniform e-commerce platform interface realized on the basis of the same standard interface protocol.

Optionally, this embodiment further includes:

and synchronizing the pre-acquired inventory data of a plurality of merchants to at least one e-commerce platform through message middleware.

To facilitate understanding of the present embodiment, please refer to fig. 2, which is a schematic diagram of an architecture of an e-commerce system implemented based on the method of the present embodiment.

As shown in fig. 2, the external e-commerce platform is composed of an e-commerce platform online store and an e-commerce open platform interface, and the operation (ordering, after-sale, etc.) of the user (i.e. the consumer) at the e-commerce platform online store generates corresponding e-commerce data.

The unified e-commerce platform comprises an e-commerce operation background, a distribution open platform interface, a middleware synchronization program, a supplier background, a unified e-commerce platform interface and a message queue.

The middleware synchronization program is configured to obtain the e-commerce data of the external e-commerce platform through the e-commerce open platform interface (step S101), transmit the e-commerce data to the e-commerce operation background through the distribution open platform interface, and transmit the e-commerce data to the ERP system of the merchant through the e-commerce operation background through the unified e-commerce platform interface (step S102).

The message queue can be regarded as a module for transferring messages between modules, and the modules can write messages into the message queue or read messages from the message queue for processing.

The supplier background can be regarded as a background management entrance provided by the unified e-commerce platform for each merchant, and the merchant can log in the supplier background to browse information such as orders, after-sales lists, stock and the like on the unified e-commerce platform and operate the information.

The ERP system of the merchant is respectively connected with the unified e-commerce platform and the storage system, and after the ERP system receives and processes e-commerce data, a processing result can be fed back to the e-commerce operation background through the unified e-commerce platform interface and then is fed back to the external e-commerce platform.

The method has the advantages that the ERP system of each merchant is in butt joint with the unified e-commerce platform interface of the unified e-commerce platform, so that the ERP system of each merchant can be in butt joint with a plurality of external e-commerce platforms through the unified e-commerce platform only by realizing the unified standard interface protocol specified by the unified e-commerce platform, and the self open interface protocol of each external e-commerce platform is not required to be realized, so that the load of the ERP system is reduced.

Fig. 3 is a schematic diagram of the overall service logic of the unified e-commerce platform of the embodiment.

After the user pays the order by the online shop of the external e-commerce platform, step S301 is performed.

S301, the middleware slices pull order data.

Specifically, the middleware pulls the order data from the e-commerce platform in a fragmentation mode, that is, the middleware splits a large amount of order data of the external e-commerce platform into a plurality of data fragments, and then pulls one fragment each time until all the order data are pulled.

In some alternative embodiments, the middleware may pull the order data generated by each external e-commerce platform in a segment at intervals (e.g., every 1 hour).

And S3011, failure monitoring and early warning.

Optionally, in consideration of a possibility of an error in the pulling process, S3011 may be executed while S301 is executed, that is, the pulling process is monitored in real time, and once a pulling failure is found, a failure monitoring and early warning is performed, so that the pulling failure is handled in time.

S302, the middleware calls a distribution order interface to transfer orders.

The distribution order interface may be regarded as an interface for interfacing order data specifically in the distribution open platform interface in fig. 2.

Through the distribution order interface, the middleware synchronization program transfers the order data to the operation background of the unified e-commerce platform (i.e. the e-commerce operation background shown in fig. 2).

S303, the ERP draws the order.

The ERP of the merchant may pull the order data from the unified e-commerce platform interface shown in fig. 2 after receiving the notification from the unified e-commerce platform.

After the user applies for after sale on the external e-commerce platform, the middleware synchronization program executes step S304.

And S304, the middleware slices pull the after-sale list data.

Steps S301 and S304 correspond to step S101 of the embodiment shown in fig. 1.

The specific implementation of step S304 is the same as step S301, and is not described again.

S3041, failure monitoring and early warning.

The specific implementation of step S3041 is the same as step S3011 and is not described again.

S305, the middleware calls a distribution after-sale bill interface to transfer the bill.

The post-sale order interface may be regarded as a special interface for post-sale order data in the distribution open platform interface in fig. 2. In other words, the distribution open platform interface may be divided into a plurality of interfaces according to the difference of functions (or according to the difference of data of docking), such as a distribution order interface and a distribution after-sales order interface.

S306, the ERP draws the after-sales bill.

Steps S302 and S303, and steps S305 and S306, correspond to step S102 of the embodiment shown in fig. 1.

The specific implementation of step S306 is the same as step S303, and is not described again.

S307, calling an order delivery interface.

In step S307, the order delivery interface may be regarded as an interface for feeding back a processing result of the order data in the unified e-commerce platform interface shown in fig. 2. That is to say, the ERP system of the merchant receives the order data, and after the delivery is completed, feeds back the processing result of the order data to the unified e-commerce platform through the order delivery interface in the unified e-commerce platform interface. The processing result may be used to indicate that the order corresponding to the order data has been shipped.

And S308, marking delivery by the order and writing the delivery into a delivery message queue.

And after receiving the feedback, the unified E-commerce platform marks the corresponding order data as delivered, and then writes the processing result into a delivery message queue.

S309, the middleware consumes the message queue message and synchronously delivers the logistics.

In step S309, the middleware reads the message written by the unified e-commerce platform from the message queue and then sends the read message to the external e-commerce platform, whereby the external e-commerce platform presents a prompt to the user that the order has been shipped.

Further, the processing result fed back by the ERP system may further include logistics information corresponding to the order data, for example, an express company for transporting the item and an express code corresponding to the item, in which case the middleware may synchronize the logistics information to an external e-commerce platform and synchronously display the logistics information to the user through the external e-commerce platform.

And S3091, failure monitoring and early warning.

The specific implementation of step S3091 is the same as step S3011, and will not be described again.

And S310, calling an after-sale confirmation return interface.

The after-sale confirmation return interface may be regarded as an interface for interfacing a processing result of the after-sale receipt data in the unified e-commerce platform interface shown in fig. 2.

In S310, after receiving and processing the after-sale receipt data, the ERP of the merchant feeds back the processing result to the unified e-commerce platform through an after-sale confirmation return interface.

S311, judging whether the post-sale order is distributed or not, if so, writing the post-sale order into a message queue.

Optionally, in S311, if it is determined that the post-sale order is not a distribution post-sale order, the processing result fed back by the merchant may be discarded.

The post-sale order is distributed, and it is understood that the corresponding order is the post-sale order processed by the unified e-commerce platform of the present invention. For example, after the user purchases the item a through the unified e-commerce platform, a corresponding order a is generated, and after the user purchases the item a, the user applies for the item for after-sale, because the corresponding order a is processed by the unified e-commerce platform, the after-sale order a corresponding to the item a belongs to the distribution after-sale order.

S312, the middleware consumes the message queue message and calls a confirmation return interface.

In step S312, the middleware reads the processing result written by the unified e-commerce platform from the message queue, and then feeds back the processing result to the external e-commerce platform through the confirmation return interface, so that the external e-commerce platform displays the after-sale processing result to the user.

The confirmation return interface of step S312 may be understood as an interface specifically used for returning goods in the e-commerce open platform interface shown in fig. 2.

And S3121, failure monitoring and early warning.

The specific implementation of step S3121 is the same as step S3011, and is not described again.

Steps S307 to S309 and steps S310 to S312 correspond to step S103 of the embodiment shown in fig. 1.

The following describes the processing flow of order data, after-sales order data, and inventory data by the unified e-commerce platform of this embodiment.

Processing flow of order data:

when order data are processed, the unified e-commerce platform firstly releases distribution commodities to other e-commerce platforms, after a user places an order on the e-commerce platform, the middleware draws the order data to the middle database for storage through the e-commerce open platform API interface, then the middleware sends the order data to the unified standard protocol interface through the unified standard protocol interface, the drawing is synchronized to the unified e-commerce platform, orders are automatically split according to stores according to store ids to which the commodities belong in the order transferring process, the stores enter store backgrounds, the stores can draw and synchronize the orders to respective ERP systems through the open platform API interface, the ERP systems make orders and send the orders, an express company and a delivery order number are transmitted back to the store backgrounds through the API interfaces after the orders are sent, message queue messages are triggered to be written, the middleware then consumes the message queue processing messages, and then returns the delivery order numbers to the platform open APIs through the e-commerce platforms to mark delivery.

Fig. 4 is a schematic flow chart of processing order data by the unified e-commerce platform according to the embodiment of the present application.

S401, selecting a distribution commodity to enter a distribution commodity pool.

The distributed commodity refers to a commodity which is specified by a merchant to be sold through the unified e-commerce platform. The distributed goods may be determined by the merchant ERP system or by the merchant through the vendor background operation shown in fig. 2.

S402, distributing the commodities to be released and put on shelves.

Step S402 specifically includes the external e-commerce platform distributing the goods on the interface of the online store according to the display.

And S403, placing an order.

Step S403 may be understood as that the external e-commerce platform generates corresponding order data in response to the order placing operation of the user.

S404, pulling order data.

Step S404 corresponds to step S301 shown in fig. 3.

As described above, after the order data pulled by the middleware is converted through the distribution open platform interface, the order data may be stored in the order message queue according to step S405, where the order message queue is a queue in the message queue shown in fig. 2, where the order data is specially stored.

And S405, writing order data.

Optionally, in step S405, the unified e-commerce platform may first determine whether the order data needs to be split, and if the order data needs to be split, split the order data into a plurality of sub-order data, and then write the sub-order data into the sub-order data.

The criterion for judging whether the order data is split is that whether the commodities included in the order data belong to the same merchant, if the commodities included in one order data belong to the same merchant, the order data is judged not to be split, and if the commodities do not belong to the same merchant, the order data is judged to be split, and in this case, the order data needs to be split into a plurality of sub-order data including the commodities belonging to the same merchant.

For example, the order data includes the commodities of the first merchant and the commodities of the second merchant, the order data is split into first sub-order data and second sub-order data, wherein the first sub-order data only includes the commodities of the first merchant, and the second sub-order data only includes the commodities of the second merchant.

S406, the order is delivered.

After the order data is written in, the ERP system of the merchant receives the order data through the unified E-commerce platform interface and carries out corresponding delivery processing, and processing results generated after the delivery processing comprise an express company, an invoice number and the like.

And S407, carrying out supplier background order delivery.

In some optional embodiments, considering that an error may occur in the automatic processing of the order data by the ERP system, the merchant may log in the supplier background, and directly operate the order data on the unified e-commerce platform through the supplier background to complete the shipping processing.

And S408, marking the order delivery.

After the shipping processing is completed through S406 or S407, the unified e-commerce platform obtains the processing result, and performs the order shipping marking, that is, marks the order data subjected to the shipping processing as shipped.

S409, order delivery marking.

After the unified e-commerce platform completes the delivery marking, the middleware synchronous processing program synchronizes the processing result fed back by the ERP of the merchant and the delivery marking to the external e-commerce platform, so that the external e-commerce platform also performs the order delivery marking, namely step S409.

S410, the order confirms receiving and is completed.

After the user receives the item corresponding to the order, the user performs an operation of confirming receiving goods on the external e-commerce platform, and then the external e-commerce platform performs step S410.

S411, the order confirms the receiving and is completed.

S412, the order confirms receipt and is completed.

After step S410, the middleware synchronization program obtains the data that the order is completed through the e-commerce open platform interface shown in fig. 2, and synchronizes the data to the unified e-commerce platform. And then the unified e-commerce platform synchronizes the data of the completed order to the ERP of the merchant through the interface of the unified e-commerce platform, and the processing flow of the order data is finished.

Further, the delivery process after the merchant ERP receives the order data may specifically refer to fig. 5.

S501, the ERP delivers goods and calls a delivery interface.

The shipping interface corresponds to the order shipping interface of step S307 of the embodiment shown in fig. 3.

S502, judging whether the order is distributed or not, if so, writing the order into a delivery message queue.

The distribution order is an order in which the included product belongs to the distribution product described in step S401.

If the order is not a distribution order, the order may be deleted directly in S502.

Steps S501 and S502 correspond to step S406 shown in fig. 4.

And S503, delivering goods by the background of the supplier, judging whether the order is distributed or not, and writing the order into a delivery message queue if the order is distributed.

Because the supplier background belongs to one part of the uniform e-commerce platform, when the supplier background is used for delivering goods, the processing result can be directly written into the delivery message queue without the uniform e-commerce platform interface.

The shipping message queue may be understood as a queue for storing processing results (including express companies, waybill numbers, and the like) of order data in the message queue shown in fig. 2.

S504, the multi-process script consumes and processes the messages of the shipping message queue.

The multi-process script in step S504 may specifically be a Workman multi-process script.

As shown in FIG. 5, the multi-process script described above may be run on a distributed cluster.

And reading a processing result corresponding to each piece of order data from the delivery message queue by the multi-process script.

Step S504 corresponds to step S408 shown in fig. 4.

And S505, calling a distribution open platform interface to synchronize logistics information.

The distribution open platform interface in step S505 may specifically be a distribution platform shipping interface. In this step, the unified e-commerce platform sends the processing result of the order data after delivery (i.e. logistics information, which may be the express company and the invoice number specifically) to the middleware through the distribution open platform interface, and the middleware synchronizes the logistics information to the external e-commerce platform. And the external e-commerce platform can return a result after receiving the logistics information and inform the middleware of receiving the logistics information.

Optionally, when step S505 is executed, failure warning may be performed, that is, warning information is output when synchronization failure is found.

Step S505 corresponds to step S409 shown in fig. 4.

And S506, synchronizing codes of the express logistics companies.

In step S506, the external e-commerce platform may synchronize information such as the delivery company and the invoice number (i.e., the above-mentioned codes) of the unified e-commerce platform through a middleware program at regular intervals before the order is confirmed to be received and completed, so as to display real-time logistics of the goods to the user.

Processing flow of after-sales order data:

when the after-sale receipt data is processed, after a user applies for sale on other e-commerce platforms, a customer service checks and approves after-sale at the background, the middleware pulls the after-sale receipt data to a middle database for storage through an e-commerce open platform API interface, then pulls the after-sale receipt data through the middleware to a uniform standard protocol interface to be synchronous to a uniform e-commerce platform, automatically separates the after-sale receipt according to the shop id to which the commodity belongs in the process of transferring the receipt, allows the after-sale receipt to enter the background of each shop of merchants, allows the merchants to pull the after-sale receipt to be synchronous to respective ERP systems through the open platform API interface, performs an after-sale processing flow in the ERP systems, if the receipt and return are confirmed, triggers to write in a message queue to confirm the receipt message, then the middleware goes to a consumption message queue to process the receipt message, returns the after-sale receipt confirmation receipt through the e-commerce open platform API to confirm the receipt, and then the customer service operates to return to the user.

Fig. 6 is a schematic view of a processing flow for processing the after-sales slip data according to the present embodiment.

And S601, applying for after-sale.

After receiving the commodity, the user can perform an operation after sale application on the external e-commerce platform, and in response to the operation of the user, the external e-commerce platform executes step S601 to generate corresponding after-sale order data.

And S602, auditing the after-sales bill.

The data of the after-sales slip generated by the external e-commerce platform can be checked firstly, and specifically can include manual checking and automatic checking, if the checking is passed, the after-sales slip is reserved, and if the checking is not passed, the after-sales slip is deleted.

And S603, pulling the after-sales bill data.

The middleware pulls the after-sale list data through the e-commerce open platform interface, and the specific implementation manner may refer to step S304 shown in fig. 3, which is not described again.

And S604, writing the after-sales bill data.

The pulled after-sales order data is transmitted to the background of the unified e-commerce platform from the middleware through the distribution open platform interface, and then written into an after-sales order message queue (namely a message queue specially storing the after-sales order data) by the background.

Optionally, as shown in step S405 in fig. 4, in S604, it may also be determined whether the after-sales slip needs to be split, and the after-sales slip data is split into multiple sub-after-sales slip data and then written into the after-sales slip message queue according to the determination result, or directly written into the after-sales slip message queue.

The step S405 may be referred to as both the criterion and the splitting method, and details are not repeated.

S605, the receiving is confirmed.

After the after-sale order data after the e-commerce platform is unified, the ERP of the merchant pulls the after-sale order data through the unified e-commerce platform interface, then step S605 is executed, whether the commodity corresponding to the after-sale order data is received or not is judged, and the confirmation result is fed back to the unified e-commerce platform as the processing result of the after-sale order data.

That is, the processing of the after-sales order data by the ERP of the merchant may specifically be to determine whether the goods corresponding to the after-sales order data have been confirmed by the user for receiving. The processing result may specifically be a received item or an unreceived item.

S606, the supplier background confirms the receiving.

Similarly, in order to avoid an error of the ERP system, similar to step S407 in fig. 4, the merchant may manually confirm that the goods corresponding to the post-sale bill have been received through the supplier background.

And S607, confirming the receipt of the after-sales bill.

After the merchant ERP or the supplier background confirms that the goods corresponding to the after-sale order are received, the unified e-commerce platform obtains the information, and then locally records the processing result of the merchant ERP, namely the goods corresponding to the after-sale order are received.

And S608, confirming the receipt of the after-sales order.

After the unified E-commerce platform confirms that the after-sale order corresponds to the commodity for receiving, the middleware synchronous processing program synchronizes the processing result to the external E-commerce platform.

And after the processing result of the after-sale bill data is received, namely after the goods corresponding to the after-sale bill are confirmed to be received, the external e-commerce platform can handle the refund service for the user applying for after-sale.

And S609, completing the single refund after sale.

After the refund service is successfully processed, the external e-commerce platform executes the step S609 to confirm that the refund of the after-sale bill is completed.

S610, the refund of the after-sales order is completed.

And the middleware synchronous processing program synchronizes the information of completion of the single refund after sale to the unified E-commerce platform.

S611, the refund of the after-sales order is completed.

And the ERP system of the merchant pulls the refund completion message of the after-sale order from the unified e-commerce platform through the unified e-commerce platform interface, and the processing flow of the after-sale order data is finished.

In the above processing flow, the flow of the merchant confirming that the article corresponding to the after-sales slip has been received may specifically refer to fig. 7.

S701, confirming the goods receiving and refunding, and calling a unified E-commerce platform interface.

And after receiving the after-sales order data, the merchant ERP system processes the after-sales order data to obtain a processing result. As described above, the post-sale order data may be processed to confirm whether or not the product corresponding to the post-sale order is received, and thus the processing result may be a message to confirm that the product is received and to refund.

And after the merchant ERP obtains the processing result, feeding the processing result back to the unified e-commerce platform through the unified e-commerce platform interface.

S702, judging whether the after-sales order is distributed or not, and writing the after-sales order into a refund message queue if the after-sales order is distributed.

Steps S701 and S702 correspond to step S605 shown in fig. 6.

The method for determining whether the post-sale bill is distributed or not may refer to step S311 shown in fig. 3, and is not described again.

And S703, confirming the receiving and refunding by the background of the supplier, judging whether the received and refunded bill is a distribution after-sale bill, and writing the bill into a refunding message queue if the received and refunded bill is a distribution after-sale bill.

Step S703 corresponds to step S606 shown in fig. 6.

S704, the multi-process script consumes and processes the messages of the message queue.

The specific implementation process of step S704 is consistent with step S504, and is not described again.

S705, calling the interface of the distribution open platform to confirm receiving and refunding.

The distribution open platform interface in step S705 may specifically be an interface for confirming receiving and refunding by an external distribution platform.

The unified e-commerce platform calls a distribution open platform interface to feed back a processing result of receiving and refunding the goods to the middleware, and the middleware feeds back the processing result to an external e-commerce platform.

And the external E-commerce platform can return the result after receiving the processing result, namely, the unified E-commerce platform is informed of receiving the processing result of the after-sales order data, and the processing result of the after-sales order data is the message for confirming the receipt and refund.

Consistent with the embodiment shown in fig. 5, when S705 is executed, failure early warning may be performed, and for a specific method, please refer to the failure early warning shown in fig. 5, which is not described again.

The inventory data processing flow comprises:

when inventory data is processed, when the inventory of each merchant changes in the ERP, the inventory is synchronized to the store background through the open platform, inventory change message queue writing and middleware consumption message queue message events are triggered, the inventory of the merchant is synchronously updated to each e-commerce platform, and unified real-time synchronous updating of the inventory is achieved.

Please refer to fig. 8, which is a flowchart illustrating a method for processing inventory data according to an embodiment of the present disclosure.

As shown in fig. 8, both the merchant ERP system and the provider background may perform an operation of updating the inventory of the goods, so as to update the inventory information of the goods on the unified e-commerce platform. The merchant ERP system updates the inventory information after updating, and sends the updated inventory information to the unified e-commerce platform through the unified e-commerce platform interface, and then the unified e-commerce platform updates.

After the inventory information of the unified E-commerce platform is updated, the unified E-commerce platform writes the commodity inventory information into a commodity inventory information queue specially used for storing the commodity inventory information, then the middleware synchronously processes the information in the commodity inventory information queue, and the updated inventory information is synchronously sent to each external E-commerce platform through an E-commerce open platform interface, so that the external E-commerce platform can display the latest commodity inventory information to a user (consumer).

And the commodity inventory information is used for recording the inventory of the commodities which are specifically updated at this time and the inventory of the commodities after updating.

Fig. 9 is a timing chart of the product inventory updating process.

And S901, updating the commodity inventory.

In step S901, the ERP system of the merchant may automatically update the inventory of the goods according to the entered information of the goods.

And S902, judging whether the commodity is a distributed commodity or not, and writing the commodity into an inventory message queue if the commodity is the distributed commodity.

And the merchant ERP system sends the updated inventory information to the unified E-commerce platform through the unified E-commerce platform interface, then the unified E-commerce platform judges whether the newly added commodity is a distributed commodity, if so, the updated inventory information is written into an inventory information queue, and if not, the inventory information is deleted.

An inventory message queue refers to a queue dedicated to storing inventory messages.

Steps S901 and S902 correspond to merchant ERP updating the inventory of goods.

And S903, updating the stock of the background commodities of the supplier, judging whether the commodities are distributed commodities, and writing the commodities into a stock message queue if the commodities are distributed commodities.

The definition of the distributed goods can be referred to step S401 shown in fig. 4.

S904, the multi-process script consumes and processes the information of the inventory information queue.

The specific implementation process of step S904 is consistent with step S504, and is not described again.

And S905, calling a distribution open platform interface to update the inventory of the external e-commerce platform.

In step S905, the unified e-commerce platform calls the distribution open platform interface to transmit the commodity inventory message to the middleware, and then the middleware synchronizes the commodity inventory message to the external e-commerce platform, so that the external e-commerce platform updates its own commodity inventory accordingly.

After the external E-commerce platform receives the commodity inventory message, the result can be returned, namely the unified E-commerce platform is informed of receiving the commodity inventory message.

When S905 is executed, failure early warning may also be performed, and a specific method may refer to failure early warning in the embodiment shown in fig. 5, which is not described again.

The distribution open platform interface in step S905 may specifically be an external distribution platform inventory update interface.

Optionally, in step S905, since there are multiple external e-commerce platforms, before the update, it may be determined to which external e-commerce platform the to-be-updated commodity inventory belongs, and then the commodity inventory of the corresponding external e-commerce platform is updated.

And S906, timing and synchronizing the commodities of the external E-commerce platform.

The middleware can regularly pull the current stock data of the platforms from the external e-commerce platforms and then synchronize the pulled stock data to the unified e-commerce platform.

And S907, synchronizing the external E-commerce platform commodities and establishing a mapping relation with the unified E-commerce platform commodity identification.

After receiving the inventory data of the external E-commerce platform, the unified E-commerce platform establishes a mapping relation between the data and the commodity mark of the unified E-commerce platform, thereby determining the current remaining inventory of each commodity and realizing the unified management and synchronization of the commodity inventory.

Referring to fig. 10, an embodiment of the present application further provides a unified e-commerce platform, as shown in fig. 10, which specifically includes the following units.

An obtaining unit 1001, configured to obtain e-commerce data of at least one e-commerce platform according to an open interface protocol of the at least one e-commerce platform;

the sending unit 1002 is configured to send, according to a preset unified standard interface protocol, e-commerce data to an ERP system of a merchant through a unified e-commerce platform interface implemented based on the same standard interface protocol; wherein, the ERP system is an Enterprise Resource management (Enterprise Resource Planning) system;

a return unit 1003, configured to return the processing result data fed back by the ERP system to at least one e-commerce platform; and processing result data is obtained by processing the e-commerce data by the ERP system.

Optionally, the method further includes:

a synchronizing unit 1004, configured to synchronize, through message middleware, the pre-acquired inventory data of the multiple merchants to at least one e-commerce platform.

Optionally, the e-commerce data includes order data;

when the sending unit sends the e-commerce data to the ERP system of the merchant through the unified e-commerce platform interface realized based on the same standard interface protocol according to the preset unified standard interface protocol, the sending unit is specifically configured to:

and according to a preset uniform standard interface protocol, sending each part of sub-order data to the ERP system of the corresponding target merchant through a uniform e-commerce platform interface realized on the basis of the same standard interface protocol.

Optionally, when the return unit returns the processing result data fed back by the ERP system to at least one e-commerce platform, the return unit is specifically configured to:

Optionally, the e-commerce data includes after-sales order data:

splitting the after-sale list data into a plurality of after-sale lists; each sub-after-sale bill corresponds to one merchant, and the commodities contained in the sub-after-sale bill belong to the merchants corresponding to the sub-after-sale bills;

The working principle of the unified e-commerce platform provided by this embodiment may participate in relevant steps in the method for e-commerce data conversion provided by this embodiment, and the beneficial effects are the same as those of the method for e-commerce data conversion, and are not described again.

Those skilled in the art can make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of e-commerce data conversion, comprising:

according to a preset uniform standard interface protocol, the e-commerce data is sent to an ERP system of a merchant through a uniform e-commerce platform interface realized based on the uniform standard interface protocol; the ERP system is an enterprise resource management system;

2. The method of claim 1, further comprising:

synchronizing the pre-acquired inventory data of a plurality of merchants to the at least one e-commerce platform through message middleware.

3. The method of claim 1, wherein the e-commerce data comprises order data;

writing the order data into an order message queue;

wherein the writing the order data into an order message queue includes:

writing the sub-order data into the order message queue;

alternatively, the first and second electrodes may be,

4. The method according to claim 3, wherein the transmitting the processing result data fed back by the ERP system back to the at least one e-commerce platform comprises:

5. The method of claim 1, wherein the e-commerce data comprises after-market order data:

writing the order data into an after-sales order message queue;

according to a preset unified standard interface protocol, sending the after-sale bill data in the after-sale bill message queue to an ERP system of a corresponding merchant through a unified e-commerce platform interface realized based on the same standard interface protocol;

writing the sub after-sale list data into the after-sale list message queue;

alternatively, the first and second electrodes may be,

taking the received commodity information corresponding to the after-sales bill as processing result data, and synchronizing the processing result data to the e-commerce platform through the middleware;

after the e-commerce platform transacts the refund service according to the processing result data, obtaining a message of completing the refund of the after-sale bill from the e-commerce platform through a middleware;

and feeding back the information of the completion of the single refund after sale to the ERP system.

6. The method according to claim 2, wherein the synchronizing pre-acquired inventory data of multiple merchants to the at least one e-commerce platform through messaging middleware comprises:

if the newly added commodity corresponding to the updated inventory message is a distributed commodity, writing the updated inventory message into an inventory message queue;

7. The method of claim 6, further comprising:

8. An electronic commerce data conversion system, comprising:

9. The system of claim 8, further comprising:

and the synchronization unit is used for synchronizing the pre-acquired inventory data of the multiple merchants to the at least one e-commerce platform through the message middleware.

10. The system of claim 8, wherein the e-commerce data comprises order data;

writing the order data into an order message queue;

wherein the writing the order data into an order message queue includes:

writing the sub-order data into the order message queue;

alternatively, the first and second electrodes may be,