Two-way sync
Changes in Dynamics 365 Business Central or Nuorder instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central and Nuorder in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Nuorder runs the storefront and takes the orders; Dynamics 365 Business Central owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.
Stacksync syncs Pricing / Price Lists, Payments, Products, Orders in Nuorder with Sales Invoices, Purchase Orders, General Ledger Entries, Journals in Dynamics 365 Business Central field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Dynamics 365 Business Central, order and customer detail from Nuorder — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
As orders are picked, shipped, or invoiced in Dynamics 365 Business Central, tracking and status flow back to Nuorder so buyers see accurate updates.
Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Dynamics 365 Business Central objects | Nuorder objects | How this pairing syncs | |
|---|---|---|---|
| Payments Customer and vendor payment records reconciled against invoices. | Payments Payment status and detail returned alongside Orders (the modified-orders date-range query returns the order plus its payment information); read-oriented in most syncs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Journals Staging records for financial postings created by integrations before posting. | Companies Retailer and customer accounts (buyers, doors); enumerated via /api/companies/codes/list and created through the customer-creation API, commonly synced with a CRM or ERP. | Journals is specific to Dynamics 365 Business Central and Companies to Nuorder — each maps to any object or custom field on the other side. | |
| Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. | Dimensions is specific to Dynamics 365 Business Central and Line Items to Nuorder — each maps to any object or custom field on the other side. | |
| Customers Core master data synced with CRMs so sales and finance share one customer list. | Inventory (ATS) Available-to-sell stock levels updated via /api/inventory/{id} (PUT); usually written from a warehouse or ERP into NuORDER so buyers see accurate availability. | Customers is specific to Dynamics 365 Business Central and Inventory (ATS) to Nuorder — each maps to any object or custom field on the other side. | |
| Vendors Supplier master data synced with procurement and AP automation tools. | Pricing / Price Lists Wholesale and retail price data attached to products through the product data feeds; read out for margin reporting or written in during catalog loads. | Vendors is specific to Dynamics 365 Business Central and Pricing / Price Lists to Nuorder — each maps to any object or custom field on the other side. | |
| Items Product and inventory records aligned with e-commerce and warehouse systems. | Products Fluent-schema catalog records (style, SKU, images, custom fields); brands push them in via /api/product/new (POST) and update via /api/product/{id} (PUT), typically mastered in a PIM or ERP. | Items is specific to Dynamics 365 Business Central and Products to Nuorder — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is written to Nuorder through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Nuorder for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Nuorder connection.
Changes in Dynamics 365 Business Central or Nuorder instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or Nuorder data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 Business Central or Nuorder record.
Track your Dynamics 365 Business Central ⇄ Nuorder sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Nuorder.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Dynamics 365 Business Central and Nuorder with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Dynamics 365 Business Central and Nuorder objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 Business Central and Nuorder: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Payments and Journals), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Dynamics 365 Business Central and Nuorder: One product catalog; Fulfillment and shipment status close the loop; One customer master. Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
Dynamics 365 Business Central: REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL. Authentication: OAuth 2.0 via Microsoft Entra ID. Nuorder: REST API (JSON), with optional SFTP flat-file data feeds. Authentication: OAuth 1.0 — consumer key/secret plus an access token/secret issued per approved application in the NuORDER Portal (Admin > Settings > API Management > Approved Applications). Stacksync manages authentication, retries, and rate limits on both sides.
Nuorder: Sandbox and production are separate hosts (wholesale.sandbox1.nuorder.com vs wholesale.nuorder.com), so credentials and record IDs do not carry across environments. Dynamics 365 Business Central: Posted documents such as posted invoices and GL entries are immutable by design; corrections happen through new postings, which shapes how bi-directional syncs handle financial data. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Nuorder without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dynamics 365 Business Central and Nuorder records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 Business Central and Nuorder connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 Business Central–Nuorder integration in-house.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 372 integrations available for Dynamics 365 Business Central and Nuorder.