Ecwid Connector for Business Central

Key Features

Inbound order sync: Ecwid orders pulled via the Ecwid Store REST API and created as Business Central Sales Orders or posted Sales Invoices, with line-level item, discount, tax and shipping mapping

Customer sync and matching: Ecwid buyers matched to existing BC Customers by email, or auto-created from a configurable customer template (posting groups, payment terms, dimensions)

Product and category publish: BC Items and item categories pushed outbound to Ecwid, including descriptions, attributes and images, driven by AL event subscribers on item changes

Inventory sync: available quantity reconciled from BC (by location or aggregate) to Ecwid stock levels on a Job Queue schedule to reduce overselling

Price sync: BC sales prices / price lists published to Ecwid, with currency and price-group mapping handled per storefront

Shipment write-back: BC posted shipments / fulfillment status written back to the matching Ecwid order so customers see accurate fulfillment state

Multi-storefront support: map several Ecwid stores to one or more BC companies with independent credentials and mapping rules

Job Queue scheduling: each sync direction runs as a BC Job Queue Entry with configurable cadence, retry, and error logging

Dedicated setup page and field-mapping UI: page extension holding Ecwid API tokens, store IDs, number series, and item/customer/payment mappings

Sync log and error visibility: every API call and record outcome recorded in an AL log table with status, message and reprocess action

Permission set scoping: a dedicated permission set gates configuration and execution so only authorized BC users run syncs

Delivered as a per-tenant extension: installs cleanly on BC cloud (SaaS) or on-prem, upgrade-safe across Microsoft's monthly and major releases

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

The Ecwid Connector for Business Central is a build-to-order AL extension that bridges your Ecwid by Lightspeed storefront(s) and Microsoft Dynamics 365 Business Central, so commerce data flows both ways without manual re-keying or CSV imports.

This is not an instant AppSource download. ECOSIRE builds the connector to fit your Ecwid catalog structure, your BC company configuration (item/customer templates, dimensions, posting groups, payment methods), then installs it as a per-tenant extension directly on your Business Central environment (cloud SaaS or on-prem). You get a working, supported integration — not a generic box you have to wire up yourself.

Under the hood the connector calls the Ecwid Store REST API for catalog, order and inventory operations and persists state in dedicated AL tables. Inbound orders are pulled on a Job Queue schedule, matched or created as Customers, and posted as Sales Orders/Invoices. Outbound product, category, inventory and price publishing is driven by event subscribers on BC item and price events plus scheduled reconciliation. A setup page (page extension on the BC role center) holds API credentials, store IDs, number series and field mappings; everything is scoped behind a dedicated permission set so you control who can run or configure it.

Because it is delivered as a tenant extension, it survives BC monthly/major upgrades, can be hotfixed by ECOSIRE without disrupting your base app, and keeps a clear audit trail of every sync. Multi-storefront merchants can map several Ecwid stores to one or more BC companies. Optional Dataverse / Power Platform surfacing of sync status is available on request.

Honest by design: a real lead time, a real human who installs it, and ongoing support.

What you get

A custom AL per-tenant extension (.app) built to your Ecwid catalog and Business Central configuration, installed on your BC environment by ECOSIRE

Configured setup page with your Ecwid API credentials, store IDs, number series and complete item/customer/price/payment field mappings

Job Queue entries provisioned for each sync direction (orders, inventory, prices, product publish) with cadence and retry tuned to your volume

A dedicated permission set assigned to the BC users/roles you nominate

Connection and end-to-end sync testing against your live Ecwid store(s) with sample orders, products and inventory movements verified

Handover documentation covering the configuration, sync schedules, error-log workflow, and a short admin walkthrough session

Who this is for

SMB Ecwid merchant on Business Central

A small-to-mid business selling through one or more Ecwid by Lightspeed storefronts that has standardized finance and inventory on Business Central, and is tired of re-keying online orders and manually updating stock and prices.

BC finance / operations manager

Owns the Business Central company setup and wants online orders posted as proper Sales Orders with correct customers, posting groups and dimensions — plus a clean audit log — rather than spreadsheet imports.

Owner-operator without an in-house AL developer

Runs the store and the back office personally, has no AppSource Ecwid connector that fits, and needs ECOSIRE to build, install and support the integration end-to-end rather than hiring a developer.

How Ecwid Connector for Business Central Compares

Criterion	ECOSIRE	Custom Build	Competitor
Built specifically for your Ecwid catalog and BC company config	Included	Included	Partial support
Installed and configured for you (no self-wiring)	Included	Partial support	Not included
Bi-directional order, inventory, price and shipment sync out of the box	Included	Partial support	Partial support
Delivered as an upgrade-safe per-tenant AL extension	Included	Included	Included
Multi-storefront mapping to one or more BC companies	Included	Partial support	Partial support
Ongoing support, hotfixes and mapping changes from one vendor	Included	Not included	Partial support
No per-order or recurring SaaS bridge fees (one-time build)	Included	Included	Not included
Native Ecwid connectivity without third-party middleware	Included	Included	Partial support

Frequently Asked Questions about Ecwid Connector for Business Central

How long until the connector is live on my Business Central, and what's the process?

Because this is build-to-order, there is a real lead time — typically around 2 to 4 weeks depending on your catalog complexity, number of storefronts, and how custom your BC setup is. The process is: a short scoping call to confirm your Ecwid stores, BC company config and field mappings; ECOSIRE builds and tests the AL extension; we install it as a per-tenant extension on your environment; then we run end-to-end sync tests against your live store before handover. There is no instant AppSource download — a real person builds and installs it.

How do support, fixes and Business Central upgrades work after delivery?

The connector ships as a per-tenant tenant extension, so it survives Microsoft's monthly and major BC releases. ECOSIRE provides post-delivery support for bug fixes and configuration help, and can issue hotfixes by republishing the extension without touching your base app or other extensions. If Ecwid changes its API or you add storefronts, adjust mappings, or change BC posting rules, those are handled as a support request or a small change — covered under an optional ongoing support arrangement we'll discuss for your volume.

Does this work on Business Central cloud (SaaS) and on-premises?

Yes. The extension is built against AL and the Ecwid Store REST API, which works on both BC online (SaaS) and on-premises deployments. SaaS install is done through the standard per-tenant extension upload; on-prem we deploy via your service tier. The Ecwid side only needs an API token and store ID per storefront.

Is it a one-way push or true two-way sync?

It is bi-directional. Orders and customers flow inbound from Ecwid into BC; products, categories, inventory levels and prices are published outbound from BC to Ecwid; and posted shipment / fulfillment status is written back to the Ecwid order. Each direction runs as its own Job Queue entry with its own schedule, so you can, for example, pull orders frequently while reconciling inventory less often.

What do I need to provide, and what are the prerequisites?

You provide: access to your Business Central environment (or a sandbox to build against), Ecwid API credentials and store ID(s) for each storefront, and decisions on mapping — which customer template, item categories, price lists, locations and payment methods to use. A BC sandbox is strongly recommended so ECOSIRE can build and test before touching production. Everything else — the AL development, install, Job Queue setup and permission set — is handled by ECOSIRE.