OMS: The core of the retail e-commerce system

1. OMS and middle console

1. OMS

OMS is mainly engaged in the "in-storage and out-storage" of various business documents to quickly transfer and process information with the upstream and downstream systems. Order is its core data, and it is also the part with the largest quantity and the highest efficiency requirements.

In the figure above, the first layer belongs to the internal related systems, such as the commodity system, procurement management, sales orders generated by the front-end shopping process, return orders initiated after sales, and business documents such as receipt - this we can call the "upstream system" or ERP; Of course, OMS should also be part of the ERP system.

OMS is mainly for the processing of orders, including the rapid flow of upstream systems; But the real production is in the warehouse. Therefore, OMS interacts most closely with the WMS system, and the information transmission with the WMS system is completed through the API interface of the warehousing system, which can be called the "downstream system".

OMS is the composition of an intermediate system service. Horizontally, it will transfer data with the financial invoices-inventory system, so it is surrounded by many systems in the middle, and it is not too much to call it an order center.

2. Middle Desk

The figure above is the system architecture introduction of an OMS product that I saw online. The order center here belongs to the business center.

The picture above is based on a friend sent me a plan for the middle desk, made some simplification; Order management is also part of the business center.

2. Related services and functions

1. Message delivery

Commodity information

The OMS is not only responsible for the issuance and upload of sales orders, but also the transmission of purchase order and return order data, as well as the underlying product information.

The receiving of goods is the initial work of WMS, and the inventory of goods can only be generated after the receiving of goods.

Before using WMS, it is necessary to initialize data, that is, basic information such as commodity information, category and supplier, and inventory initialization. In addition, it is necessary to create and maintain information such as reservoir area and cargo location in the WMS system.

If the warehouse needs to be processed and produced according to raw materials, it needs to be configured in the commodity system, such as the father and son commodity configuration, and the raw material configuration of processed products, which will be issued to the WMS system in advance in the form of BOM.

Supplier information

Supplier information is created in the supplier management module, which includes supplier ID, number, name and status. WMS needs to obtain this part of information when receiving goods for data verification.

In addition, there are supplier inventories in the upstream and downstream systems, and the calculation and statistics of the supplier's commodity costs should be carried out.

There are commodity batch data in the WMS system, and the batch code can be created according to the relevant rules to ensure that the commodity can be distinguished when a product is multiple.

receipt

The documents here refer to the business creation purchase order, return order, and also include the user's sales order, return and exchange order.

After the purchase order and return order are created in the SCM system, they need to be synchronized to the warehouse by the OMS, so that the data verification and statistics can be carried out in the WMS system according to the collected purchase order after the supplier arrives. At the same time, receiving arrangements can also be made when the supplier has booked the delivery application before.

After the sales order is paid and dismantled, it should be sent to WMS, and the warehouse can start processing, picking, packing and sending the invoice after receiving it.

The delivery of documents is generally divided into header and row data, and commodity data is verified according to BOM in the WMS system according to the information of the delivered documents.

All these are completed through the API interface, and our original system will save the message information every time the data is sent and uploaded, so that problems can be viewed, analyzed and solved.

Therefore, when data is synchronized between the OMS and WMS, the XML information sent or returned by the interface must be kept intact.

2. Information upload

There should be a return to the data.

In this example, the OMS receives the data and status sent back by the WMS system. After receiving the data and status, the OMS performs some service processing.

Take the purchase order as an example, when the warehouse completes warehousing, the actual warehousing quantity will be sent back; In this case, the OMS system needs to generate the warehouse entry order based on the returned data and update the inventory of the upstream system. At the same time, it is also necessary to calculate the cost and generate the storage flow, because the data flow to a node needs to be calculated, the system is generally through MQ to achieve asynchronous processing.

Similar to message delivery, the returned information details need to be retained. Some of the returned information needs to be parsed and saved in a relational database for statistical query and display.

3. Order distribution coordination

The rules and policies apply when sending and uploading information.

With the outbreak of services, the number of units increases very fast. Therefore, some rules should be configured in the OMS system to speed up data flow, speed up system response, and give users a better representation.

At the same time, there are a lot of states some of which are internal to the warehouse, some of which are business systems, which need to be set up during order processing, which need to be selectively shielded and converted.

4. Order number generation, pulling and dismantling

These services are familiar to everyone, and the single number product is to rely on defined rules to generate a single number that cannot be repeated, which is provided to the front-end shopping process or the background business system call.

At the same time, the rule of the single number will also be associated with the sub-library and sub-table service, so the rule of the single number is very important, it must meet the outbreak of a single amount of growth, can not be repeated, you can save and query order data of different dimensions through the single number.

The pull order is to pull the invoices generated by front-end users to the back-end production database, which is the source of sales order data. For the pull order, you can view the OMS| Order pull previously summarized. The description is not repeated here.

5. Invoice service

Now the paper invoice is less and less, the invoicing information of the electronic invoice does not need to be synchronized to the WMS system, but the calculation of the invoice amount is essential, and needs to be synchronized to the electronic invoice tax platform.

Invoicing services are also required to calculate some after-sale reissues, reissues involved in returns, etc. - although these are closely related to finance, they are inseparable from the OMS system, so they should be part of the OMS.

6. Status update and template

The status of the order is constantly changing according to the fulfillment process, there are changes in the upstream system, there are updates in the WMS system. The whole-process tracking of orders is the statistics and analysis based on the flow of states, and the business department will make improvements according to the life cycle of orders. Status change not only involves logical processing of other business processes, but also requires message notification, such as SMS, email, or wechat.

In the basic service layer of the retail e-commerce system, there is a corresponding gateway to interconnect with the SP. However, the interaction with the user needs to pay attention to the copy and format. Therefore, the template configuration needs to be set in advance so that the OMS can be invoked.

As long as it is related to the user, then we should pay attention to the user experience, not missing or multiple, nor disorderly, to set the relevant rules.

7. Running Water

Here I divide the incoming and outgoing warehouse flow into the OMS system, because it receives all the warehousing operation data, as long as there is an incoming and outgoing warehouse, it involves the increase or decrease of inventory; However, the API interface provided by WMS or the returned data may not distinguish the bill type, which needs to be reprocessed by the upstream system. This problem was needed several years ago when the inventory was checked with the LSCM "warehouse docking platform".

Although the WMS has document types, after LSCM, there are only two major types: outgoing and incoming. The specific information needs to be parsed according to XML packets and reprocessed by the upstream system.

Pipelining is also the basis for the interaction between SCM and the financial system. The financial department calculates the financial cost and generates related statements according to the input and exit process and inventory.

So if you are in charge of OMS, you need to pay attention to this part, some WMS is carried out in the form of adjustment orders, and the documents need to be generated upstream.

8. Inventory

In the retail e-commerce system, inventory is generally divided into three parts, internal ERP, WMS and finance. It has been said before that WMS comes first, ERP is increased or decreased by OMS according to the incoming and outgoing warehouse documents, and finance is generated again according to the incoming and outgoing warehouse flow of OMS.

Therefore, reconciliation is necessary, WMS and ERP work in real time, inventory changes in real time, and there will be time differences, and finance is generated according to the current flow, so there can be accurate ending inventory.

Contact with several WMS systems are through the snapshot backup of the end inventory, if the WMS system is not, need to be developed, as long as there is a pen of data can be calculated the end inventory.

However, when the number of SKUs and the amount of documents is very, very large, the calculation needs time, and the system design needs to be divided into warehouses, categories and other distributed calculation, of course, I only propose here; In the actual production system, we have encountered at most hundreds of thousands of single, hundreds of thousands of SKU scenes a day, and Jingdong and other platforms such as this design is certainly not satisfied, interested students can consider, you can exchange private messages.

Iii. Summary

We all know the term OMS, but in different companies OMS has different functions and covers different services; As long as it is more reasonable to plan according to the business and meet the changes in the business, it is not necessary to care too much about whether it is the order center.

Business-driven technology development, in the design to apply the domain model, which is recently learned from reading, business, technology, data, field, how to do, need to constantly refer to the application cases of successful enterprises combined with actual scenarios to practice.