ERP integration overview

The ERP integration connects Omnilinker to the ERP system you run on your own premises. A small Windows program, the ERP Sync agent, connects to your ERP database in your network and talks to Omnilinker over the internet.

​

How it works

The ERP Sync agent is a Windows service plus a tray app, installed together on a computer in your network. One agent serves one connection.

• The agent does the ERP work. Inside it, a connector for your ERP connects to the ERP database. Omnilinker never connects to your database itself.
• Your ERP credentials stay in your network. You enter the database connection details in the agent’s tray app, not in the web app. The agent stores them in an encrypted file on its own computer, protected with Windows data protection (DPAPI). Omnilinker never asks for, stores or receives your ERP database password.
• All connections go out from your network. The agent calls Omnilinker; Omnilinker never connects into your network, and the agent opens no network port on its computer. The agent signs in with a key of its own for the connection, which it gets when you connect it with a connection code.
• Omnilinker never runs ERP code. The connector runs only inside the agent. The agent reports what its connector can do, and Omnilinker shows it on the connection’s PC and connector tab. ERP Integration > Supported ERPs shows what each connector can do before you connect it.

​

What the integration does today

The agent reads three lists from your ERP and sends them to Omnilinker, so you can match them to what you already have in Omnilinker. It also sends the ERP’s stock, which Omnilinker shows beside its own, and, once you ask for it, its prices: The agent reads a list when it has never read it, about once a day after that, when the connection’s settings change, and whenever you click Refresh lists. Restarting the service alone does not read a list that is less than a day old. See Reference items.

​

Orders and customers

The integration also works the other way for orders. Omnilinker sends a confirmed order to Wapro as a customer order with a reservation, and finds, creates or asks you to choose the buyer’s customer there. You decide per order source whether it sends automatically, later, or never because another system already imports its orders. Orders you send cannot be changed in Omnilinker any more: you change them in the ERP, or cancel them. Omnilinker also reads back what Wapro did with an order it sent, and shows Wapro’s status, the invoice number and its KSeF number on the order card. The invoice is still issued in Wapro. If Wapro cancels or deletes an order that is still open in Omnilinker, Omnilinker holds its stock again and tells you. On a warehouse Wapro manages, an order’s stock is handed over to Wapro once the order is there. See Orders to your ERP and Customers in your ERP. It needs the connection’s ERP user for writes.

​

Prices

Prices go both ways, in different ways. To your ERP. From Catalog > Products you can send the price saved on a price level of a product to the ERP price level it is mapped to. You can also switch on automatic sending for a price level on a connection: then every change to its prices is sent without anyone pressing a button. That needs the feature Send prices to the ERP automatically, which is off until Omnilinker switches it on for your organization. Both need the connection’s ERP user for writes, and only a price level Omnilinker sets can be sent: a level another system manages is refused. See Prices to your ERP and Who sets a level’s prices. From your ERP. The agent can also read the ERP’s selling prices, so you can compare them with yours on the connection’s Price levels tab: how many are equal, how many differ and how many are missing on either side. It reads them only while a price level is mapped and Read prices from the ERP is on for your organization, and it is off until Omnilinker switches it on for you. On a price level Omnilinker sets, the prices are only compared. You can also let the ERP set a price level: then its prices replace yours for the products linked to it, and a price changed on a level Omnilinker keeps is reported, never copied. See Prices, Compare the ERP’s prices with yours and Prices from your ERP.

​

Not available

• Bundles, and creating price levels. Omnilinker takes the products and their details from your ERP, takes the stock of the warehouses you let it manage (the ERP’s stock of other warehouses is shown beside yours for comparison) and takes the prices of the price levels you let the ERP set. On the other price levels it only compares the ERP’s prices with yours. It does not import bundles and does not create price levels for you. You can create warehouses from the ERP’s warehouses yourself. Earlier versions imported some of these; that import was removed and comes back in a later version.
• Changes to an order’s lines in your ERP, and orders created in it. Omnilinker reads back the status, the invoices and the KSeF numbers of the orders it sent, and only shows them. A change to the order’s lines in Wapro does not come back, and an order created in Wapro does not appear in Omnilinker.
• Writing products or stock to your ERP.

​

Supported ERP systems

The Provider list in the web app also shows these, and Custom. Only Wapro has a working connector in the agent today, so choose Wapro when you create a connection.

​

Set up the integration

Check the requirements first, then work through these steps. Setup is split between the tenant admin, who works in the web app, and the IT person who installs the agent. Once the agent is running, ERP Integration > Overview says what moves and what needs you. See Monitoring to check that the PC is online and that the lists arrived.

​

Next steps