Build ecommerce that fits your Dynamics NAV setup

Why Dynamics NAV companies need a clear ecommerce strategy

Dynamics NAV handles the back office well. Financials, purchase orders, warehouse logic, customer records — these are the things NAV was built for, and most companies have spent years refining how they use them. The challenge starts when you need to expose that data to customers through a digital storefront. Product information, pricing rules, stock levels, and order confirmations all need to move between NAV and the ecommerce platform in a reliable, timely way.

This is not just a technical problem. It is a business design problem. Which fields in NAV actually matter for the storefront? How do you handle prices that differ by customer group? What happens when warehouse quantities update mid-day? The answers depend on your specific NAV setup, your customer expectations, and the platform you choose to sell through. Getting those decisions right early saves months of rework later.

Nordic Web Team works with commerce teams who already run Dynamics NAV and want to build ecommerce around it rather than starting from scratch. We bring experience from real NAV-connected projects and an honest view of what each platform option can and cannot do for your particular situation.

Platform options and what they mean for a NAV setup

There is no single correct platform for every Dynamics NAV customer. The right choice depends on your product catalogue complexity, your market ambitions, your team's technical comfort, and your budget. We work with four platforms that each bring something different to the table.

Norce is a Nordic-born commerce platform built for companies with complex product and pricing logic. If your NAV setup serves multiple price lists, customer-specific agreements, or large SKU catalogues, Norce tends to handle that structure well. It is particularly strong in B2B scenarios common among NAV users in the Nordics.

Shopware offers a flexible, open architecture that suits companies wanting deep control over their storefront experience without being locked into a single ecosystem. It works well when your team values extensibility and plans to iterate on features over time.

Shopify gives you speed to market and a mature ecosystem of apps and themes. For NAV companies with a more straightforward product range and a preference for lower operational overhead, Shopify can be a pragmatic starting point — especially for B2C or lighter B2B use cases.

Magento with Hyvä remains a strong option when you need deep customisation and have the technical team to support it. The Hyvä frontend modernises the Magento experience significantly, making it more performant without sacrificing the platform's flexibility.

How data flows between Dynamics NAV and your storefront

The integration between NAV and your ecommerce platform is where most complexity lives. Typical data flows include product master data (descriptions, attributes, images mapped to items), pricing and discount structures, inventory levels from one or more warehouses, customer records and customer-specific pricing, and orders flowing back into NAV for fulfilment and invoicing.

For the integration layer, we use Junipeer, which has a live API connector to Dynamics NAV. This means the technical connection itself can be established quickly — customer-facing integration time is typically around one day. But the connector is only one part of the picture. Before anything connects, you need clean data in NAV, a clear mapping of which fields serve which purpose in the storefront, and agreement on how exceptions are handled.

Common issues we see include product data that is complete enough for internal use but lacks the descriptions, images, or attributes needed for a customer-facing catalogue. Pricing logic that works perfectly inside NAV but needs translation into the ecommerce platform's own pricing engine. And inventory rules that make sense operationally but confuse customers when stock shows as available but is actually reserved. These are data quality and business logic problems, not connector problems.

What the project actually involves beyond integration

Connecting NAV to an ecommerce platform is a necessary step, but it is not the project. A successful launch requires work across several areas that have nothing to do with the API layer. Platform selection is the first decision, and it shapes everything downstream — from what your team needs to learn to how your hosting is managed. Getting this wrong is expensive to reverse.

UX and content work determines whether your storefront actually converts. Product pages need clear information, logical navigation, and a checkout flow that matches how your customers buy. For B2B companies on NAV, this often means supporting features like quick order forms, account-specific pricing display, and reorder functionality.

QA and testing across the full data chain — from NAV through Junipeer to the storefront and back — catches the issues that only appear when real orders flow through the system. We test with production-representative data, not just sample records.

Rollout planning covers go-live sequencing, staff training, monitoring during the first weeks, and a clear plan for the iteration cycle after launch. Most NAV-connected ecommerce projects benefit from a phased approach: start with core product data and ordering, then layer in more complex pricing, customer portals, or additional markets as confidence grows.

Nordic markets and Dynamics NAV

Dynamics NAV has a strong installed base in Sweden, Norway, and Denmark. Many of these companies operate in wholesale, distribution, manufacturing, or specialised retail — industries where product data is complex, pricing is relationship-driven, and order volumes justify automation. The Junipeer connector supports these three markets, making it practical to run a multi-market storefront from a single NAV instance.

Nordic buyers also have specific expectations around payment methods, shipping options, and language handling. Your ecommerce platform needs to support Klarna or Swish for Swedish customers, Vipps for Norwegian buyers, and localised checkout flows for each market. These are platform-level decisions that interact with your NAV data but are not solved by the ERP integration alone.

Nordic Web Team has worked with commerce teams across these markets and understands the operational realities of running NAV in a Nordic context. We do not sell a single answer. We help you evaluate your options honestly, build what matters first, and expand from a stable foundation.