No — this is build-to-order, not an instant AppSource install. ECOSIRE designs the extension around your store topology and catalog, then installs it as a per-tenant extension. Typical lead time is about one working week depending on the number of Shopify stores, the complexity of your item/variant mapping and how many currencies and locations are involved. We start in your sandbox, validate the mapping with you, and only then cut over to production.

After go-live you get an agreed support window for bug fixes and tuning. Because Shopify periodically versions its Admin API and Microsoft ships Business Central updates twice a year, we offer a maintenance arrangement to keep the extension compatible across those cycles, monitor the error/retry queue, and apply mapping changes as your catalog evolves. You always own the deployed extension on your tenant; we operate and maintain it under the terms we agree.

The native connector is single-store oriented and gives you limited control over mapping and conflict handling. This extension is purpose-built for multiple Shopify stores with per-store credentials, currencies and conflict rules, a dedicated mapping table, event-driven near-real-time push, and a monitored error queue — tailored to your process rather than a generic default.

It runs inside your Business Central environment as a per-tenant AL extension. It uses the Business Central REST/OData v4 API and AL event subscribers internally, and connects outward to each store via the Shopify Admin GraphQL API, with webhooks ingesting inbound events such as new orders. Scheduled reconciliation and retries run through the Job Queue.

Yes. The extension exposes sync-status and error-queue data on Business Central pages, and we can optionally surface that into Dataverse so you can build a Power BI sync-health dashboard or a lightweight Power Apps monitor for your ops team. This is configured as part of the build if you need it.