Build ecommerce that fits around your Fortnox

Why Fortnox is a strong foundation — and where the work begins

Fortnox gives you a reliable core for accounting, invoicing, inventory, and order management. For over 600,000 Swedish companies, it is the system of record. That is a genuine advantage when you launch ecommerce: you already have structured product data, customer records, and financial flows in one place.

The challenge is not Fortnox itself. It is that ecommerce introduces demands Fortnox was not built to handle on its own — live stock visibility across channels, flexible pricing rules, product enrichment for search and conversion, and a frontend experience that meets buyer expectations. These requirements sit outside the ERP, which means you need a platform layer, a data connection, and a delivery plan that ties everything together.

This is where many projects stall. Companies focus on the integration and forget the surrounding work: data quality checks, content and UX, QA cycles, and a phased rollout that protects the live business. We see this pattern regularly and plan for it from the start.

Choosing a platform that fits your Fortnox setup

There is no single correct platform for every Fortnox customer. The right choice depends on your catalogue size, how complex your pricing and customer segmentation is, whether you sell B2B, DTC, or both, and how much control you want over the frontend experience. We work with four platforms that each serve this segment well: Norce, Shopware, Shopify, and Magento with Hyvä.

Shopify is the fastest path to a working store. It suits DTC brands and smaller catalogues where simplicity and speed matter more than deep customisation. Shopware offers strong flexibility for mid-market companies that need multi-channel logic, advanced pricing, or localised storefronts across Nordic markets. Norce is a commerce engine built for companies managing complex product data, multiple brands, or wholesale alongside DTC — common in fashion and distribution. Magento with Hyvä remains a serious option for businesses that need full control over every layer, from catalogue logic to checkout, while keeping frontend performance high.

Each of these platforms connects to Fortnox, but the data architecture and the build effort around it differ. We walk you through those tradeoffs early, before any code is written.

How data flows between Fortnox and your storefront

A typical Fortnox ecommerce integration moves several data types between systems. Products, pricing, and stock levels flow from Fortnox to the ecommerce platform. Orders, customer records, and payment confirmations flow back. The direction, frequency, and conflict-handling rules depend on your business logic — not on a one-size-fits-all template.

We use Junipeer as the integration layer between Fortnox and your chosen platform. Junipeer has a live API connector for Fortnox, and customer-facing integration time is typically one day. That speed matters, but the connector is only the pipe. Before it runs, you need clean product data, agreed stock rules, a clear order-status mapping, and tested exception handling for edge cases like partial shipments or returns.

Common data flows include:

• Product master data and variant structures
• Price lists, including customer-specific pricing for B2B
• Stock levels — either real-time or batched, depending on volume
• Orders and order-status updates
• Customer and company records
• Invoice references and payment reconciliation

The exact scope varies by platform. We document the data map during discovery so there are no surprises at launch.

The work around the integration

Integration gets the most attention, but it is rarely the hardest part of the project. The real effort sits in the decisions and delivery work that surround it. Platform selection is one. Data quality is another — if your Fortnox product data has inconsistent naming, missing attributes, or duplicate records, those problems follow you straight into the storefront.

Then there is UX and content. A connected store with poor navigation, thin product descriptions, or a confusing checkout will not convert, regardless of how clean the data pipe is. We invest time in information architecture, category structure, and content planning as part of every project. QA is equally non-negotiable: we test order flows end-to-end, validate stock sync under load, and verify that edge cases — backorders, mixed VAT rates, partial deliveries — behave correctly before anything goes live.

Rollout planning closes the loop. We prefer phased launches — soft-launch to a controlled audience, monitor data flows and conversion, then scale traffic. This approach reduces risk and gives you real performance data before the full go-live.

Who this is for — and what the first step looks like

This approach fits Swedish SMBs and growth companies that run Fortnox and want to sell online without replacing their business system. It is especially relevant for fashion brands managing seasonal catalogues, wholesalers adding a DTC channel, and any company where Fortnox is the financial backbone and needs to stay that way.

We are not a platform vendor. Nordic Web Team is an independent ecommerce agency that helps you make the right choices across platform, integration, content, and delivery — then executes the build. Our starting point is always a discovery sprint: we map your current Fortnox setup, your catalogue complexity, your channel ambitions, and your internal capacity. From there, we recommend a platform, define the integration scope with Junipeer, and plan the build in phases that match your budget and timeline.

If you are evaluating ecommerce options and want an honest assessment of what fits your Fortnox environment, a discovery conversation is the right first step. No pitch deck — just a structured look at your situation and the options in front of you.