Two-way sync
Changes in Channelengine or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Available quantities from Dynamics 365 Business Central publish to Channelengine, so the store shows what can actually ship and stops overselling.
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.
Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Channelengine–Dynamics 365 Business Central connection.
Changes in Channelengine or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Channelengine or Dynamics 365 Business Central data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Channelengine or Dynamics 365 Business Central record.
Track your Channelengine ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Channelengine and Dynamics 365 Business Central.
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 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.
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.
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 Channelengine and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Channelengine's Products (product content) and Offers (price and stock)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Channelengine: 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. 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. Stacksync manages authentication, retries, and rate limits on both sides.
Channelengine: Products use a parent/child model where the parent is a non-purchasable blueprint and only children are sold; nesting is limited to a single level. Dynamics 365 Business Central: Writes use ETags with If-Match headers for optimistic concurrency, so stale updates are rejected instead of silently overwriting ERP data. Stacksync's field mapping accounts for these differences between Channelengine and Dynamics 365 Business Central 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 Channelengine and Dynamics 365 Business Central records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Channelengine and Dynamics 365 Business Central connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Channelengine–Dynamics 365 Business Central integration in-house.
Yes — Stacksync ships production-grade connectors for both Channelengine and Dynamics 365 Business Central. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Channelengine and Dynamics 365 Business Central.