Business Central is a different product from Dynamics NAV 2018. The store already takes orders. We will tell you whether those orders should become salesOrders on API v2.0, and why a NAV SOAP integration will not get you there.
Australian team. We look at the store and the BC environment before anyone talks about a connector.
01
What you have
02
What is safe to keep
03
Connect or leave
The store still takes orders. Finance still lives in a Microsoft ERP. That is why the connection has been left as a CSV, a NAV-era SOAP page, or someone re-keying sales orders after checkout.
Dynamics 365 Business Central is Microsoft’s cloud — and on-prem — ERP for SMBs: finance, sales, purchasing, inventory. It is the successor product line to Dynamics NAV. Successor is not the same as “same API”. NAV 2018 and Business Central are different products.
Microsoft ships an Australian localisation: GST posting, BAS business units, withholding tax, ABN, EFT, Peppol PINT A-NZ e-invoicing, and payment-times reporting, with further PTR and TPAR work planned in the 2026 wave 1. Australia (en-AU) is on Microsoft’s country availability list. That is localisation, not an install-base figure, and it is not why you should hire us.
You might recognise one of these:
You do not need a new storefront. You need a clear read on which Microsoft product you actually run.
Business Central has a real API. Preferred is the built-in REST API v2.0 at /api/v2.0/, with OAuth 2.0. Microsoft also documents OData V4 on published pages and queries, and SOAP — SOAP “replaced by OData V4”, with support to be removed in a later release. Connect apps are point-to-point using the standard REST API. The stall is rarely “BC has no API”. It is treating NAV as BC.
We published a B2B nopCommerce store for NESS Corporation, fully integrated with Microsoft Dynamics NAV 2018. NAV sent customers, pricing and products to the store. The store sent web orders, line items and freight back. SOAP Page integration moved to Codeunits returning JSON. Checkout used NAV payment terms, billing from NAV, and order history including credit notes. That is NAV 2018. It is not Business Central, not Dynamics 365, and not API v2.0. We will not use it as proof we have delivered BC.
v2 resources include customers, items, salesOrders, salesOrderLines and salesInvoices. Typical store jobs: sync customers and items; POST salesOrders with the web order as the external document number; POST salesInvoices where the merchant invoices from the store; pull stock from items or locations via the API or custom API pages. Basic auth and access keys were deprecated for BC online from October 2022. A leftover NAV access-key habit will not pass.
If the current connection is SOAP pages from a NAV-era partner, Microsoft is already telling you to move. OData V4 is the documented replacement for SOAP. New ecommerce work should be REST API v2.0 and OAuth 2.0, not another SOAP page.
GST, BAS, ABN, EFT and Peppol PINT A-NZ sit in Microsoft’s AU local functionality. The integration has to respect those posting and tax fields. It does not become “we localise Business Central”. We connect the store to the environment you already run.
None of that makes the customer list or the item master worthless. It does mean “point the NAV integration at BC on Monday” is usually the wrong first move.
We start with which Microsoft product you run, not with “Dynamics”.
Business Central online or on-prem, API v2.0 availability, leftover SOAP or OData pages, AU localisation in use, and the store (nopCommerce, AbleCommerce, Shopify, or another CMS). If you are still on NAV 2018, we will say so — that is a different job.
There are three honest outcomes. We recommend one, not all three.
Customers and items down; salesOrders up with a stable external document number. salesInvoices only when the store owns invoicing. Stock from items or locations when the site must show a number. NAV-era SOAP pages do not get a second life because they still respond.
Source, the Entra app and scopes, a short record of what posts which way, and a connection someone else can understand.
We will not tell you NESS is a Business Central case. We will not say we already integrate Dynamics 365. If you already know you want an AppSource ecommerce connector and nothing custom, that marketplace is a better fit. If you want an honest design for the environment and the store you already have, talk to us.
A store URL and which Microsoft ERP is enough to start.
The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a connector estimate pulled from thin air.
NESS Corporation is a B2B nopCommerce store fully integrated with Microsoft Dynamics NAV 2018. Related Microsoft ERP work. It is not Business Central, not Dynamics 365, and not a case we will retitle. We have not published a named CoSource ecommerce case for Business Central. Windsor is Peach and Xero. A BC environment still starts with its own assessment.
Thirty minutes. Bring a store URL and which Microsoft product you run. We will tell you whether to build on API v2.0, treat it as NAV 2018, or leave the current path alone for now.
Book a free 30-minute discovery call