Connect BigCommerce with Microsoft Dynamics NAV (formerly Navision) to sync orders, customers, products, pricing, and inventory so your store and ERP stay aligned as you scale.
• Product records are mapped between Bigcommerce SKUs and Microsoft Dynamics NAV item numbers, with configurable field mapping for names, prices, barcodes, and tax classes.
• Inventory availability is synced per item and, when applicable, per location, with NAV treated as the inventory owner and Bigcommerce updated on a schedule or near-real-time triggers.
• Bigcommerce orders are exported to Microsoft Navision as sales orders, including customer, billing and shipping addresses, discounts, shipping method, taxes, and payment method references.
• Order line items are validated against NAV items and units of measure; unmatched SKUs, missing customers, and mapping errors are captured in an error queue with detailed logs.
• Shipment confirmations, tracking numbers, invoices, and order statuses are synchronized back to Bigcommerce so order history reflects NAV fulfillment progress.
• Delta-based sync logic sends only changed records where supported, reducing payload size and keeping retries idempotent to avoid duplicate orders or stock updates.
.png)
We map BigCommerce order, payment, tax, and shipping fields to NAV sales documents, then sync on a schedule or near real time. Status and tracking updates can be pushed back to BigCommerce for customer visibility.
Yes – inventory can sync by SKU, warehouse, and stock rules so BigCommerce shows accurate availability. We also handle backorders, safety stock, and low-stock thresholds when needed.
Typical sync covers SKUs, variants, pricing, barcodes, and key attributes, plus category mapping. The exact payload depends on your NAV setup and how your catalog is structured in BigCommerce.
We align NAV price lists and customer pricing with BigCommerce price lists, promotions, or customer groups. Where native logic differs, we implement clear priority rules to avoid mismatched totals.
Most projects take weeks, not months, after requirements are confirmed and data is clean. Timeline depends on custom NAV objects, number of stores, and how many sync directions you need.










