Fortnox logo

Integration between Ongoing WMS and Fortnox

Table of contents

Introduction

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.

Video

We have prepared a video about the integration.

Features

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: There is a setting in Fortnox that will lead to a back order being created if the delivered quantity on the order is less than the ordered quantity. 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, you can modify this functionality by navigating to Inställningar->Fakturering->Lager" where the following setting can be found:

button for allowing back orders in Fortnox

This setting should be set to "Ja" if back orders should not be created!

Stock balance updates

Regular

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.

Preparations

To be able to activate the integration following information is needed. Gather the information and speak to your 3PL provider or contact person at Ongoing WMS.

Please see this guide on how to set up an integration between Fortnox and your Ongoing WMS.


Ongoing Warehouse AB is integration partner with Fortnox.