|
BigCommerce B2B Integration for Dynamics NAVLive NAV and AX prices, stock and orders in your web store |
Product Verticals: Distribution, Manufacturing
Business Processes: Advanced Pricing, Data Integration, E-Commerce, Inventory Management, Order Management, Sales Order Processing, Web Storefront
ProjectThunder connects BigCommerce B2B Edition storefronts to Microsoft Dynamics NAV and Dynamics AX. We build the storefront and the integration between the store and the ERP. Your Dynamics partner keeps owning the ERP and runs the upgrade.
What the integration covers
These are the six things a B2B storefront needs from NAV or AX:
- Who is this customer: the customer account behind the login, plus ship-to addresses. On AX, also the legal entity.
- What do they pay: NAV sales prices and line discounts, or AX trade agreements.
- What can they have: availability by location or warehouse, net of reservations.
- Place the order: returning the real ERP order number. Every order carries an idempotency key, so a retry cannot create a duplicate.
- Where is it: shipment and posting status, with tracking where the carrier provides it.
- What do they owe: posted invoices, open entries and credit position.
How we connect
On NAV we use published page and codeunit web services, with OData for catalog, pricing and availability reads. On AX 2012 we usually write a custom service that answers the exact question the storefront asks, or use AIF. Catalog pages can show a cached price. The cart, quote and checkout use the live ERP price, and no resolved price means no add-to-cart, because NAV falls back to the item card unit price and AX to the released product base price when no customer price exists.
Ready for the upgrade
NAV 2017 extended support ends on 11 January 2027 and NAV 2018 on 11 January 2028. Business Central kept NAV's data model and posting logic, so an integration built on published web services moves to Business Central with the adapter rewritten and the contracts unchanged. On AX, the move to Dynamics 365 Finance and Operations is a bigger jump, so we keep the AX-specific part small and rebuild the store-side adapter against Finance and Operations when you get there.
How a project runs
Discovery generally takes 4 to 6 weeks. Most projects take about three months including planning, longer when several vendors are involved.
About ProjectThunder
A senior B2B e-commerce studio in business since 2004 and a BigCommerce Partner. Our engineers are in the US and Manila, and everyone works California hours.
Read the full guide:
Talk to us: [email protected], 877-609-9029, or