Dynamics NAV to Shopify Integration

The question worth answering honestly is a different one: given where NAV sits in its support lifecycle, should you integrate now or migrate to Business Central first? Nobody writing about NAV and Shopify answers that. We checked the whole first page of results and the date is not on any of them, which is odd, because two of the four questions Google shows alongside those results are about whether NAV is still supported.

Dynamics NAV 2018 was released on 1 December 2017. Mainstream support ended on 11 January 2023. Extended support ends on 12 January 2028. NAV runs under Microsoft's Fixed Lifecycle Policy.

NAV 2017 is a year ahead of that: mainstream ended 12 January 2022, extended ends 12 January 2027.

Be precise about what extended support means, because the shorthand misleads. It is security fixes only. No new features, no new hotfixes on request, no design changes. NAV 2018 is out of mainstream support today and has a fixed end date a little over a year out.

None of that stops a storefront working. It does mean any plan that treats NAV as a permanent platform is planning against a published end date.

We tested this with a web-connected model twice, the same prompt both times, and both runs reached the same shape of answer rather than a verdict. That shape is worth adopting, because it is what your buyers are already being told.

Both runs made it a sequencing decision with two thresholds. If you need a storefront live inside roughly three to six months, integrate NAV now. If a Business Central migration is already funded and likely inside the next year to eighteen months, do the ERP first and connect the storefront to what you will actually be running.

Both runs named the same risk as the largest one: building and paying for the integration twice.

That risk is real and it is manageable. The way you manage it is to keep the ERP-specific work thin and isolated, so that the connector is the part that gets replaced at migration rather than the storefront, the catalog, the customer structure and the buying experience. Those should survive an ERP change untouched. If a proposal embeds NAV-specific logic throughout the storefront, that is where the second bill comes from.

Worth adding: Business Central ships a free first-party Shopify connector, preinstalled on new environments. NAV does not have one and never will. So a migration eventually simplifies this problem rather than repeating it, which is another argument for isolating the NAV-specific layer now.

NAV publishes web services in two flavours, and the version you run decides how much you get.

SOAP web services expose pages and codeunits. Codeunit web services are SOAP only, and they are how you reach business logic rather than just data.

OData services expose pages with metadata, filtering, FlowFilters, server-driven paging and writable pages. For read-heavy work, catalog, customers, pricing and inventory, OData is usually the better path.

The practical dividing line is version. NAV 2015 and later carry the web services surface a modern integration needs. Older releases are a different conversation, and Microsoft's own upgrade documentation reflects the same split: NAV 2015 through 2018 upgrade directly to Business Central, while NAV 4.0, 5.0, 2009 SP1, 2009 R2, 2013 and 2013 R2 require an intermediate hop.

If you are on one of the older ones, the honest answer is that the ERP conversation comes before the commerce one.

A note on vocabulary, because it trips people up mid-project. What NAV calls item cross references, Business Central calls item references. Same concept, renamed. Small thing, real confusion.

NAV customers become Shopify companies, with ship-to addresses as company locations and contacts as buyer logins, so each buyer signs into the account they are authorized to buy for.

Customer price groups and customer discount groups map into Shopify's B2B pricing structures, with anything computed resolved from NAV rather than flattened into a price file that ages.

Items become products with their attributes and units of measure, and item cross references become the alternate part numbers your customers actually search by.

Inventory comes by location, because a distributor with several warehouses needs the storefront to show the one that will ship.

A Shopify order becomes a NAV sales order with line detail, the customer reference and terms attached, written through a codeunit so NAV's own validation runs.

Uncap Connect keeps pricing, inventory, customer data and orders current in both directions, built for B2B so customer-specific pricing, credit terms and tax behave the way they do in your business.

NAV is on-premises, which changes the failure profile. The integration depends on a connection to a server inside your network, and that server has maintenance windows, backups and the occasional bad afternoon.

So orders queue rather than disappear. Transient failures, including the connection simply being unavailable, retry on a backoff. Permanent failures, such as a blocked item or a customer over their credit limit, hold with the payload and the exact NAV error preserved, somewhere your team already looks, and replay without asking the customer to reorder. The buyer's Shopify order stays visible to them throughout.

Getting this right matters more on NAV than on a cloud ERP, because the downtime is more frequent and more scheduled.

A thin, isolated NAV connector layer, so that when you migrate to Business Central the replacement is the connector rather than the storefront.

Company accounts, company locations and buyer logins mapped from the NAV customer structure.

Price group and discount group resolution for the logged-in account, with computed pricing resolved from NAV.

Inventory by location, with the warehouse logic your buyers actually need.

Order creation through codeunit web services so NAV validation applies, with a queue, a held-order path and replay for the times your server is not there.

A storefront, catalog and customer experience built to outlive the ERP underneath them.

Industrial Supply and MRO, where catalogs run past a hundred thousand items and procurement buys through its own systems.

Home Goods, where retail accounts and a consumer channel run from one catalog.

Medical Supply, where contract pricing decides what an account pays before the product does.

NAV is one of four Dynamics products we connect to Shopify. The Microsoft Dynamics integration overview covers Business Central, Finance and Operations, and GP.

Bring your NAV version, your migration plans if you have any, and one account's pricing setup. If a Business Central move is already funded, say so at the start, because it changes what we would recommend building.

Book a strategy session, or start with a Blueprint, the paid discovery engagement that maps the integration surface, the pricing model and the phased plan before development begins.