Salesforce Commerce Cloud Connector for Business Central

This is a build-to-order extension, not an instant AppSource download. After we confirm your SFCC setup, catalog complexity, and number of storefronts, typical delivery is two to four weeks. ECOSIRE builds the AL extension, validates it in a sandbox/UAT BC environment against your Commerce Cloud sandbox, then installs it as a per-tenant extension on your production Business Central environment and walks you through configuration.

Yes. Your order includes a post-delivery support window for bug fixes and for keeping the extension compatible with Business Central's monthly service updates and SFCC API changes. Because it ships as a per-tenant extension with source delivered to you, you are never locked into a black-box SaaS. We offer extended support and enhancement retainers separately if you want continued coverage beyond the initial window.

It runs inside Business Central. The sync logic lives in AL codeunits and event subscribers within the extension; scheduled and delta syncs run via the BC Job Queue; external calls go straight to the SFCC REST/OCAPI endpoints using BC's HttpClient. There is no separate middleware server to host, license, or babysit. Optionally we can hand data off to Dataverse for Power Platform reuse.

Yes. Multiple SFCC sites map to distinct BC locations, dimensions, or responsibility centers; each site's currency reconciles to a BC currency code and exchange-rate setup; and Salesforce B2B Commerce contract / customer-specific pricing maps to BC price lists and customer price groups when publishing price books. The exact mapping is configured to your setup during the build.

SFCC refunds post in Business Central as credit memos against the originating customer and document, and SFCC tax classes are mapped to your BC VAT/tax posting groups so amounts post to the correct accounts. Every sync is written to an audit log on the BC side with payload references, so finance can reconcile orders, refunds and tax line by line.