Skip to content
E-commerce ⇄ ERP

Channelengine to Dynamics 365 Business Central integration — real-time, two-way sync

Keep Channelengine and Dynamics 365 Business Central in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Channelengine and Dynamics 365 Business Central

Keep the storefront in step with the back office: Channelengine and Dynamics 365 Business Central share products, inventory, and orders in real time, in both directions.

Channelengine 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 Backorders, Order documents, Orders, Products (product content) in Channelengine with Customers, Vendors, Items, Sales Orders 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 Channelengine — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Load Orders and Returns into Postgres or a warehouse for marketplace sales, fulfillment, and margin reporting without manual CSV exports.
  • 02 Push product content from a PIM, ERP, or database into ChannelEngine's Products endpoint so listings stay current across every connected marketplace.
  • 03 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
  • 04 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.

Common sync patterns

Where Dynamics 365 Business Central is the inventory system of record: stock stays accurate

Available quantities from Dynamics 365 Business Central publish to Channelengine, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Channelengine creates the matching record in Dynamics 365 Business Central with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

One product catalog

Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.

What you can sync between Channelengine and Dynamics 365 Business Central

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.

Channelengine objects Dynamics 365 Business Central objects How this pairing syncs
Products (product content) Catalog records created and updated via POST /v2/products and deactivated via DELETE; use a parent/child variant model where the parent is a non-purchasable blueprint. Written into ChannelEngine from a PIM, ERP, or database. Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Products (product content) is specific to Channelengine and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Offers (price and stock) Price and stock updates via PUT /v2/offer/stock and the offers endpoints; separate from product content so fast-changing stock can be pushed often, and supports bulk updates across stock locations. Payments Customer and vendor payment records reconciled against invoices. Offers (price and stock) is specific to Channelengine and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Shipments Fulfillment records; write with POST /v2/shipments to mark an order shipped with tracking, read with GET /v2/shipments. Pushed back from a warehouse or ERP so marketplaces update the buyer. Customers Core master data synced with CRMs so sales and finance share one customer list. Shipments is specific to Channelengine and Customers to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Returns Marketplace- and merchant-initiated returns; read via GET /v2/returns and created with POST /v2/returns. Synced two-way so customer-service and finance systems reconcile with the ERP. Vendors Supplier master data synced with procurement and AP automation tools. Returns is specific to Channelengine and Vendors to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Cancellations Order cancellations; create with POST /v2/cancellations and read with GET /v2/cancellations. Written when stock is unavailable and read back for reconciliation. Items Product and inventory records aligned with e-commerce and warehouse systems. Cancellations is specific to Channelengine and Items to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Backorders Records marking part of an order as temporarily out of stock; create with POST /v2/backorders and read with GET /v2/backorders by merchant reference or since a date. Sales Orders Order headers and lines created from external channels and read back for fulfillment status. Backorders is specific to Channelengine and Sales Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side.

How changes propagate between Channelengine and Dynamics 365 Business Central

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.

Channelengine Dynamics 365 Business Central Sub-second propagation

DetectionChannelengine notifies Stacksync of record changes through webhook events. Webhooks fire on order creation and on return and shipment/cancellation changes.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Dynamics 365 Business Central Channelengine Sub-second propagation

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 Channelengine through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Channelengine: Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.
What ships with Channelengine ⇄ Dynamics 365 Business Central

Connect Channelengine and Dynamics 365 Business Central for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Channelengine–Dynamics 365 Business Central connection.

Real-time

Two-way sync

Changes in Channelengine or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Channelengine or Dynamics 365 Business Central data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Channelengine or Dynamics 365 Business Central record.

Observability

Monitoring

Track your Channelengine ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Channelengine and Dynamics 365 Business Central.

How the Channelengine and Dynamics 365 Business Central connectors work

Channelengine

Integration surface
REST API (Merchant API v2); per-tenant base URL https://{tenant}.channelengine.net/api
Authentication
API key passed as the 'apikey' parameter; ChannelEngine recommends sending it in a request header rather than the URL because some webservers log full URLs
Change detection
Webhooks fire on order creation and on return and shipment/cancellation changes; product content and offers use change-tracking endpoints (GET /v2/products/data and /v2/products/offers) with an acknowledge pattern that returns only changed records, plus polling GET /v2/orders/new
Capabilities
read · write · webhooks
Rate limits
Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.

Dynamics 365 Business Central

Integration surface
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
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks
How it works

How to connect Channelengine to Dynamics 365 Business Central — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Channelengine and Dynamics 365 Business Central with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Channelengine connected
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Channelengine and Dynamics 365 Business Central 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Channelengine ⇄ Dynamics 365 Business Central
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Channelengine Dynamics 365 Business Central
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Channelengine and Dynamics 365 Business Central integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 372 integrations available for Channelengine and Dynamics 365 Business Central.

Popular · 6 of 372
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.