Fortnox logo

Integration between Ongoing WMS and Fortnox

Table of contents


The Fortnox WMS integration is intended to be used by businesses which use Ongoing WMS for their warehousing operations (either via a third-party logistics provider, or if the business is direct customer to Ongoing Warehouse). The integration helps you improve your warehouse efficiency and accuracy. The integration can automatically synchronize Ongoing WMS and Fortnox, meaning less duplicated work.

The data transferred between Ongoing WMS and Fortnox


We have prepared a video about the integration.


The integration contains the following processes and features. The processes can be independently switched on or off. If not otherwise mentioned, all processed are turned on by default.

Article registry

Ongoing WMS pulls article registry updates from Fortnox to the WMS. Fortnox contains the master data. The following data is transmitted:

* The information that determines if an article is a stock article or not is determined by the Lagervara setting on the article in Fortnox. When this setting is set to Ja the article is a stock article, otherwise it is not.

Note: when an article is not a stock article it will not be picked when it appears on orders.

stock article button in Fortnox

Supplier registry

Ongoing WMS fetches new suppliers from Fortnox.

Sales orders

The WMS downloads new and updated orders which are not yet handled. If an order is updated, the change is transferred unless the warehouse workers have started working on it.

Ongoing WMS pulls the following information for the order:

Please note: if you wish to automatically set a transporter service on the order in Ongoing WMS based on the content in e.g. “way of delivery” or "terms of delivery" in Fortnox you have to use transporter assignment.

The delivery address information is also transmitted. That includes:

Notification via SMS and email is turned off by default.

For each order line Ongoing WMS reads the following:

It is possible to set up the integration to automatically set the order type in Ongoing as B2B or B2C based on the customer type in Fortnox. If there already exists order types of type B2B and B2C those will be used, otherwise they will be created by the integration. If there exists multiple B2B/B2C order types the one that was created first will be used.

When an order is fulfilled by the warehouse, the delivered quantity is updated in Fortnox, and invoice is created if none already exists.

Note: If the delivered quantity is less than the ordered quantity when fulfilling an order in Fortnox this will lead to a back order being created. The back order contains the quantity that was not delivered on the original order. If you do not want a back order to be created please contact your Ongoing WMS representative to modify the integration in such a way that the ordered quantity in Fortnox will be updated to the delivered quantity in applicable cases. It is very important that you understand that this will modify the ordered quantity, and hence the ordered quantity will not be the same quantity as it originally was which most likely will be unexpected for the end customer.

Stock balance updates


Ongoing WMS manages the stock balances and continuously synchronizes these with Fortnox.
Note: When using the warehouse module, the "classic" stock balance synchronization cannot be used! This is because the classic variant writes the stock directly on the article in Fortnox, and the warehouse module only allow transactions.

Warehouse module

It is possible to set up the integration to use the warehouse module in Fortnox. When this part of the integration is activated the flag warehouseReady will be activated when reporting an order as fulfilled by the warehouse. Note that if the warehouse module is activated in Fortnox and not in the integration the fulfillment will fail.

Inventory changes and returns on sales orders will be reported as Custom Warehouse Inbound/Outbound Documents in Fortnox.

The following document types are used by Ongoing WMS:

Ongoing WMS transaction type Fortnox Document type
Purchase orderOngoingInboundOrder
Return on sales orderOngoingInboundReturn
Positive inventory adjustmentOngoingInboundInventory
Negative inventory adjustmentOngoingOutboundInventory

Purchase orders

If the module "Lager+" is used in Fortnox it is possible to handle purchase orders in the integration. The WMS will pull purchase orders in status "sent" where the purchase type is "warehouse".

Note: if the integration keys generated for an existing integration were created before the "Lager+" module was activated new keys will need to be generated. This is because the integration keys that were generated before the module was activated does not have permission to access the purchase orders using the API.

Ongoing WMS pulls the following information for the purchase order:

For each purchase order line Ongoing WMS reads the following:

Once the purchase order has been received by the warehouse, they can trigger the purchase order to be reported back to Fortnox. When this happens, the integration will do the following:

  1. Create incoming goods corresponding to the received amount.
  2. Release the incoming goods.
  3. Complete the incoming goods.
  4. Complete the purchase order (only if the purchase order marked as completed by the warehouse, i.e. the status is "Deflection" or "Received").

If the purchase order will be received partially at different dates, it is possible to create incoming goods for each partial receival. This will work so long as the purchase order status in Ongoing WMS is not set to "Deflection" or "Received", since then the purchase order in Fortnox will be marked as completed.

Default settings and considerations

The following needs to be considered before Ongoing WMS can activate the integration.

  1. Synchronization interval.
    Default: Every 15 minutes. It is usually a suitable balance between responsiveness and band-width usage.
  2. Stock level synchronization. Should the available quantity be written to Fortnox from the WMS? At the end of each synchronization interval, Ongoing WMS pushes the stock level to Fortnox if activated.
    Default: No.
  3. When should an order be fulfilled by the Warehouse?
    Default: Placed non-invoiced orders.
  4. Which status should sales orders have to be pulled to the WMS?
    Default: Confirmed
  5. Should the order type in Ongoing be set to B2B or B2C based on the customer type in Fortnox?
    Default: Yes.
  6. Should fulfilled orders be notified to Fortnox?
    Default: Yes. If the answer is yes, answer the following question:
    1. When should orders be reported to the ERP?
      Default: When the sent button is pressed in the WMS. The same as when the transportation is booked.


Fortnox uses OAuth 2.0 in order to allow integrations to access the data needed.
Note: The rights of the keys generated depends on the user that generates them. For example: If you want the integration to access invoices and the warehouse module, then the user that generates the keys must itself be able to access invoices and the warehouse module in Fortnox.
To setup the integration you will need to perform the following steps:

  1. Activate the app Ongoing WMS in the Fortnox Marketplace:

    Ongoing WMS app in Fortnox marketplace
  2. When the app is activated you will be redirected to the Ongoing landing page:

    Ongoing WMS landing page

    Here you will be asked to provide credentials for the WMS where you want to setup the integration. In the box marked System you can provide either the URL of the WMS, for example, or you can provide the Ongoing customer ID which can be found using the info button at the bottom of the page when you are logged in on your WMS:

    1. Ongoing footer info
    2. Ongoing customer ID

    Username and Password corresponds to the user and password for the WMS.

  3. Once the correct information is provided and the login button clicked you will be redirected to Fortnox where you will first be asked to login:

    Fortnox login page

    Note: The user name here is the user name for Fortnox.

  4. The next step is to read through which permissions the integration needs. In order to be able to use the integration all the requested permissions must be accepted. If you are unsure what the different permissions mean please contact us. If the required permissions are denied you will not be able to setup the integration. Also note that the user from the previous step must have the permissions stated here for the generated keys to have the permissions.

    Fortnox permissions request
  5. When the requested permissions are accepted you will be redirected to the previously provided Ongoing WMS and can make some fine tuning of the integration before finally activating it.

  6. Once the integration is activated it will run every 15 minutes.

Fortnox integration partner logo
Ongoing Warehouse AB is integration partner with Fortnox. Fortnox offers a cloud-based platform so that small business owners and accounting firms can manage their finances and administration effectively. The platform is the market leader in Sweden. It also gives customers access to financial services and corporate insurance. Fortnox was founded in 2001 and is headquartered in Växjö. The share is listed on NGM Nordic MTF. For further information see