This is a build-to-order engagement, not an instant AppSource install. After a short scoping call we typically deliver in one working week depending on how many mobile flows, label layouts and integrations are in scope. We build in a sandbox, validate with you, then install the per-tenant extension on production. You'll get a firm timeline in writing before work starts.

Because it's your own per-tenant AL extension, you keep the source-aligned package and permission sets. ECOSIRE provides a post-go-live support window and re-validates the extension against each Microsoft major release, since D365 is on a continuous-update cadence. Changes, new flows or additional carriers are handled as scoped follow-on work — you talk to the engineers who built it, not a generic queue.

No code overlay is used. We extend standard warehouse objects through AL table extensions, page extensions and supported event subscribers, which is Microsoft's recommended path for surviving the continuous-update cadence. We also test on your sandbox before each production deployment and re-validate on major releases.

Yes. The pack flow calls your shipping gateway through the BC REST/OData API for rates, label generation and tracking numbers. We integrate with the carrier or aggregator you already use; if you need a new one we scope it as part of the build. Where Power Platform or Dataverse fits, we can surface work and count data there too.

No. The extension is installed as a per-tenant extension on your own Business Central / D365 tenant, so warehouse work, counts and labels stay inside your environment. Only the specific carrier calls you configure reach out to your shipping gateway, over the connection you approve.

Then we only build the gaps. We scope honestly — if a requirement is met by standard location directives, work templates or document layouts, we configure rather than code, and the extension stays small. You pay for the closure of real gaps, not a rebuild of what Microsoft already gives you.