Microsoft Dynamics NAV and WooCommerce integration

What moves between them

The primary flow is from WooCommerce into Dynamics NAV. On each order.created or order.updated webhook, ml-connector reads the order and customer data from WooCommerce and creates or updates a corresponding sales order and customer record in Dynamics NAV, mapped to the correct sales dimensions and price lists. A secondary flow syncs product inventory back to WooCommerce: when Dynamics NAV item quantities change (via purchase receipt or sales order fulfillment), ml-connector updates the corresponding WooCommerce product stock level so online availability stays current. Customer records flow bidirectionally so both systems show the same contact and payment details.

How ml-connector handles it

ml-connector stores WooCommerce API keys and Dynamics NAV OAuth 2.0 credentials encrypted and handles webhook events from WooCommerce in real-time. When a WooCommerce order arrives, ml-connector queries the full order and customer details, creates a sales order in Dynamics NAV with line items matched to the correct items (by SKU or product code), and assigns the order to the correct sales dimension and price list based on order source or customer segment. For inventory sync back to WooCommerce, ml-connector polls Dynamics NAV item quantities on a schedule (typically daily) and updates WooCommerce product stock levels. Webhook subscriptions in WooCommerce expire after 5 non-2xx responses, so ml-connector tracks subscription health and re-enables failed webhooks. Refunds and cancellations in WooCommerce trigger credit memo creation in Dynamics NAV if the original order already posted. Every order and inventory update carries a full encrypted audit trail and can be replayed if a downstream sync fails.

A real-world example

A small e-commerce retailer runs WooCommerce on its own WordPress site and Dynamics NAV to manage purchasing from suppliers, warehouse inventory, and finance. Before the integration, the owner manually exported orders from WooCommerce each morning, entered them into Dynamics NAV as sales orders by hand, and checked inventory manually to avoid overselling. When stock ran out in the warehouse, it took a day or two to update the website, leading to customer complaints. With WooCommerce and Dynamics NAV connected, orders appear as sales orders in Dynamics NAV within seconds of purchase, inventory is synced every few hours so the website always shows real stock levels, and the manual order entry step is eliminated.

What you can do

• •Create sales orders and customer records in Dynamics NAV automatically when WooCommerce orders are placed or updated.
• •Sync product inventory from Dynamics NAV to WooCommerce on a daily schedule so online stock levels match your warehouse.
• •Map WooCommerce customers to Dynamics NAV customer records with address, contact, and payment details.
• •Handle OAuth 2.0 authentication to Dynamics NAV and API key authentication to WooCommerce, with encrypted credential storage and automatic retry.
• •Maintain a full audit trail on every order and inventory change so failed syncs can be replayed without data loss.

Questions

Which direction does data move between Dynamics NAV and WooCommerce?

Orders and customers flow from WooCommerce into Dynamics NAV as sales orders and customer records. Product inventory flows from Dynamics NAV back to WooCommerce to keep online stock levels current. Refunds and cancellations in WooCommerce can trigger credit memos in Dynamics NAV if the original order posted.

Does the integration work with on-premises Dynamics NAV or only cloud?

The integration works with both Microsoft Dynamics 365 Business Central online and on-premises Dynamics NAV deployments. For on-premises systems, the administrator must enable OData services and open the OData port (7048) through the firewall. The base URL and authentication method differ between cloud and on-premises, and ml-connector accepts both.

How does the integration handle WooCommerce webhook failures?

WooCommerce disables webhooks automatically after 5 consecutive non-2xx responses. ml-connector monitors webhook health and re-enables failed subscriptions so order flow does not stop. Every order and inventory sync is tracked in an encrypted audit log so if a webhook fails, the records can be replayed once the connection is restored.