E-commerce 27 Jan 2026 7 min read

Connecting WooCommerce to Fortnox: which option should you choose?

Most stores do fine with a ready-made connection, set up with their accountant. How to choose between Fortnox's own option, plugins, platforms and a custom integration.

Kristoffer Pihlfelt

Developer and founder, Pihlfelt & Vänner

Once your store handles more than a handful of orders a week, sales, VAT and payments should flow automatically from WooCommerce to Fortnox, the accounting software most Swedish small businesses use. For most stores a ready-made connection is enough, either from Fortnox's own range of integrations or an established plugin, as long as it is configured together with your accountant. An integration platform makes sense when several systems need to talk to each other, and a custom integration when your business rules do not fit any ready-made solution. The hard part is rarely the technology. It is deciding how your sales should be booked, and that decision should come before you choose a tool.

Why the connection matters

Without a connection, each order is entered by hand, or sales are booked in bulk from reports. Both work at small scale but become expensive as volume grows.

  • Time. Manual transfer is routine work that takes time every week and that someone has to remember to do, holidays included.
  • Accounting errors. The wrong VAT rate, the wrong account, an order booked twice or a refund that never makes it across. These errors often surface at the VAT return or year-end close, when they are most expensive to untangle.
  • VAT and OSS. If you sell to consumers in other EU countries and pass the EU-wide threshold for distance sales, you must charge the buyer's local VAT, and many businesses report it through OSS (One Stop Shop, the simplified EU VAT scheme administered by the Swedish Tax Agency). Your books then need to separate sales by country and VAT rate, which a simple connection does not always handle.
  • Payouts from Klarna and Stripe. Payment providers do not pay out order by order. They bundle many orders into one payout, deduct their fees and offset refunds. What lands in the bank therefore matches no single invoice, and without a well-thought-out setup, reconciliation becomes a recurring puzzle.

First decide how sales should be booked

Before comparing solutions, you need answers to a few basic questions. They determine which kind of connection fits.

  • Invoice per order or summarised entries? Some businesses create a customer invoice in Fortnox for every order. Others book sales as one summarised entry per day or per payout. The latter means fewer entries and easier reconciliation, the former more detail per customer.
  • Should customers exist in Fortnox? For B2B customers buying on invoice, usually yes. For consumers it is often unnecessary to build a large customer register in your accounts.
  • Where do products and stock live? One system needs to be the source of truth. Two systems that both think they control stock will give you wrong numbers sooner or later.
  • How are refunds, discounts, gift cards and shipping handled? This is where most connections show their weaknesses.

Four kinds of solution

Fortnox's own connection and integration range

Fortnox offers its own range of integrations that you activate from your Fortnox account. The advantage is that you deal with a supplier you already pay and that setup is often simple. The drawback is that flexibility can be limited: if the approach suits your accounting, fine, otherwise there is little to adjust.

Ready-made WooCommerce plugins

Several established plugins are installed in the store and send orders, payments and sometimes products and stock to Fortnox. They usually offer more settings for accounts, VAT rates and payment methods, and some handle reconciliation of Klarna and Stripe payouts. Quality varies, so look at how actively the plugin is maintained, whether support responds and how many Swedish stores use it.

Integration platforms

An integration platform is a standalone service that moves data between systems, such as the store, Fortnox, the warehouse and carriers. It suits you when you have more than two systems or plan to change e-commerce platform, since the accounting connection is then not tied to WooCommerce. You pay an ongoing fee and get one more supplier to keep track of.

A custom integration with the Fortnox API

Fortnox has an API, an interface through which other systems can read and write data. A custom integration is built exactly around your rules: special VAT setups, multiple warehouses, B2B terms or an ERP system in the middle. It costs more to build and someone has to maintain the code, but you avoid bending your accounting to fit a tool. It mainly pays off when volumes are high or the flow is so specific that ready-made solutions create more manual work than they save.

Questions to ask your accountant

Involve your accountant early. They are the ones who will live with the result, and half an hour of discussion before setup often saves many hours of corrections afterwards.

  • Do you want an invoice per order or a summarised entry per day or per payout?
  • Which accounts should be used for sales per VAT rate, shipping, fees and gift cards?
  • How should Klarna and Stripe payouts be reconciled against the bank?
  • Does OSS apply to us, and how should sales per country be reported?
  • How should returns and partial refunds be booked?
  • Which reports do you need each month to confirm everything adds up?

Risks to be aware of

  • The connection stops working without anyone noticing. An update, an expired authorisation or a change at Fortnox can halt the transfer. Decide who gets the alert and who fixes it.
  • VAT errors are discovered late. Test with real orders across several VAT rates, with a discount and with a refund before going live, and have your accountant review the first month.
  • Dependence on a single supplier. A plugin built by a lone developer may stop being updated. Ask how long it has existed and what happens if it is discontinued.
  • Stock in two places. Let only one system control stock levels.

How to choose

  • Choose Fortnox's own connection if you have a simple store, few payment methods and an accounting setup that suits it.
  • Choose a ready-made plugin if you need more control over accounts, VAT and payouts but have a fairly standard flow. This is the right choice for most stores.
  • Choose an integration platform if more systems need connecting, or if you might change e-commerce platform.
  • Choose a custom integration if your rules do not fit any ready-made solution, or if volume makes every manual correction too costly.

Our recommendation

Start with the accounting, not the tool. Write down how an order, a payment and a refund should appear in Fortnox, agree on it with your accountant, and then choose the simplest solution that handles it. For most stores that will be a well-maintained plugin that is properly configured and tested. We set up and troubleshoot Fortnox connections as part of our WooCommerce development, and when nothing ready-made is enough we build the integration ourselves as part of our API and integration development.

Share: