Netvisor logo

Integration between Ongoing WMS and Visma Netvisor

Ongoing Warehouse has developed an integration with the ERP system Netvisor. This integration makes it possible for businesses which use Netvisor to easily outsource their warehouse needs to a 3PL company which uses Ongoing WMS. The integration can also be used by businesses who run Netvisor and who want to run their own warehouse using Ongoing WMS.

With Ongoing WMS, you'll be able to utilize features such as scanning (compatible with any device) to reduce picking errors, efficient picking routes, batch-picking, streamlined return processing, automatic label printing, warehouse maps, support for multiple warehouses, and comprehensive traceability. Moreover, Ongoing WMS is entirely web-based, allowing you to access your warehouse operations from any device, anywhere.

Get started with a free trial of Ongoing WMS today!

Table of contents

Scheduled functions

Some functions in the integration run on a schedule. The article registry, orders and purchase orders are synced automatically from Netvisor to Ongoing WMS.

Article registry

The article registry is read automatically from Netvisor to Ongoing WMS. If a change is made in Netvisor, it will be reflected automatically in Ongoing WMS.

Field mapping

Show field mapping

Ongoing WMS field name Netvisor field name
Article ⇒ Article numberProduct ⇒ Code
Article ⇒ Article nameProduct ⇒ Name
Article ⇒ DescriptionProduct ⇒ Description
Article ⇒ Is stock articleProduct ⇒ Stockable
Article ⇒ BarcodeProduct ⇒ Primary EAN code
Article ⇒ LengthProduct ⇒ Length
Article ⇒ WidthProduct ⇒ Width
Article ⇒ HeightProduct ⇒ Height
Article ⇒ Net weightProduct ⇒ Net weight
Article ⇒ WeightProduct ⇒ Gross weight
Article ⇒ Purchase priceProduct ⇒ Purchase price
Article ⇒ PriceProduct ⇒ Basic price (Unit price)
Article ⇒ Statistics numberProduct ⇒ Tariff heading
Article ⇒ CountryOfOriginCodeProduct ⇒ Intrastat ⇒ CountryOfOrigin
Article ⇒ Article group ⇒ NameProduct ⇒ Group ⇒ Name
Article ⇒ Article group ⇒ CodeProduct ⇒ Group ⇒ ID
Article ⇒ Article structureProduct ⇒ Sub products

Note that the mapping of article structure only works if there is only one integration setup for the goods owner in Ongoing.


By default, all published products that have been updated in Netvisor will be synced to Ongoing WMS. Deleted products will not be synced.


Orders are read automatically from Netvisor to Ongoing WMS. Note that the integration sync orders and not invoices.

Field mapping

Show field mapping

Ongoing WMS field name Netvisor field name
Order info ⇒ Order numberOrder ⇒ Order number
Order info ⇒ Delivery dateOrder ⇒ Delivery date
Order info ⇒ ReferenceOrder ⇒ Our reference
Order info ⇒ Receiver order numberOrder ⇒ Your reference
Order info ⇒ Customer priceOrder ⇒ Total (EUR) including tax
Order info ⇒ CommentOrder ⇒ Text before order rows
Order info ⇒ Free text 1Order ⇒ Text after order rows
Order info ⇒ Terms of deliveryOrder ⇒ Term of delivery
Order info ⇒ Way of deliveryOrder ⇒ Delivery method
Customer ⇒ AddressOrder ⇒ Delivery address ⇒ Name
Customer ⇒ Address2Order ⇒ Delivery address &rArr Place of business
Customer ⇒ CityCustomer ⇒ Delivery address ⇒ City
Customer ⇒ Country codeOrder rArr; Delivery address ⇒ Country of delivery
Customer ⇒ Customer numberOrder ⇒ Customer ⇒ Customer code
Customer ⇒ EmailOrder ⇒ Customer ⇒ Email
Customer ⇒ MobileOrder ⇒ Customer ⇒ Telephone
Customer ⇒ External customer codeOrder ⇒ Customer ⇒ Netvisor key
Customer ⇒ NameOrder ⇒ Customer ⇒ Name
Customer ⇒ Post codeOrder ⇒ Delivery address ⇒ Postal code
Order line ⇒ Article numberOrder line ⇒ Product code
Order line ⇒ Article nameOrder line ⇒ Product
Order line ⇒ Product codeOrder line ⇒ Product netvisor key
Order line ⇒ External order line codeOrder line ⇒ Netvisor key
Order line ⇒ Line priceOrder line ⇒ Total (VAT inclusive)
Order line ⇒ Customs total valueOrder line ⇒ Total (VAT inclusive)
Order line ⇒ Number of itemsOrder line ⇒ Amount
Order text line ⇒ Order line commentComment line ⇒ Product


By default, all orders matching the following filter in Netvisor are synced to Ongoing WMS. Note that if the order exists in Ongoing WMS, it will only be updated if the status of the order in Ongoing WMS allows it to be updated!

Show filters

Netvisor field name Default filter
Order ⇒ Last change timeLater than the last time the integration synced
Invoice statusUndelivered

Purchase orders

Purchase orders in Netvisor are mapped to purchase orders in Ongoing WMS. This allows the warehouse to report received goods to Netvisor.

Field mapping

Show field mapping

Ongoing WMS field name Netvisor field name
Inorder ⇒ Order numberPurchase order ⇒ Order number
Inorder ⇒ ReferencePurchase order ⇒ Our reference
Inorder ⇒ CommentPurchase order ⇒ Order comment
Inorder ⇒ Order datePurchase order ⇒ Purchase order date
Inorder supplier ⇒ Supplier namePurchase order ⇒ Vendor
Inorder line ⇒ Article numberPurchase order line ⇒ Product code
Inorder line ⇒ CountPurchase order line ⇒ Amount
Inorder line ⇒ Row numberPurchase order line ⇒ Netvisor key


By default, only purchase orders in Netvisor with the status "Sent to vendor" will be synced to Ongoing WMS. There must also still be undelivered order rows on the purchase order.

Functions based on user actions

Inbound deliveries

When a delivery is made to the warehouse, this will be recorded on a purchase order. This triggers an update of the purchase order in Netvisor, where the received amount for each purchase order line will be updated. It is possible that the received quantities differ from the advised quantities.

Outbound deliveries

When an order has been set to status Sent or Collected in Ongoing WMS, the corresponding order in Netvisor will be updated with the delivered quantity.

Inventory adjustments

If an inventory adjustment has been made in Ongoing WMS it is possible to create a corresponding stock transaction in Netvisor. This will ensure that the stock in both systems is always up to date. To use this functionality, you will need to provide the integration with an Inventory event type that is necessary when creating stock transactions using the API. To find the available event types, and create new ones, please navigate to Products ⇒ Stock transactions:

Inventory event types

Getting Started

To configure this integration, you must create an API user in Netvisor. To be able to create the API user you must first enable the integration in the Rights of interface resources page. You should select Custom integrations and use the key 06399E380AF3A9FD6E6B4D6E30EC7B46 to find the integration for Ongoing WMS:

Custom integrations

Once you have activated the API you can create an API user in Netvisor. Ongoing WMS will need user ID and private key of the API user, as well as the Organization ID of the Netvisor system. This can be created by following the instructions in API identifiers.