Because this is build-to-order, there is a real lead time — typically around one working week 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.

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.

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.

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.

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.