No. It is a build-to-order per-tenant extension. ECOSIRE scopes it to your carrier contracts, builds it in AL, then installs it on your Business Central sandbox and production environments. You are not downloading a generic app — you are getting an extension tailored to your PostNord, Bring, GLS and DHL accounts and your shipping process.

A typical build is one working week from kickoff, depending on how many of the four carriers you need on day one, your return and multi-parcel logic, and label-format requirements. We confirm a firm timeline after a short scoping call and deliver to a sandbox first for your sign-off before touching production.

Your carrier accounts and API credentials (PostNord, Bring, GLS, DHL), your BC environment access (or a sandbox), your package/service types and any return-label rules, and a contact who knows your current shipping process. We handle the AL development, installation and permission-set configuration.

The one-time fee covers the build, installation and go-live support. Carriers change their APIs periodically, so we offer an optional support agreement that covers monitoring those changes, applying fixes, BC version upgrades (the extension is upgrade-safe by design), and adding new carriers or services later. Without an agreement, changes are handled on a time-and-materials basis.

Yes. It is built as a proper per-tenant extension using table extensions, page extensions and event subscribers — it never modifies the base application. That keeps it compatible across Microsoft's monthly and major BC updates. If a base-app event signature changes, the optional support agreement covers re-aligning it.

Yes. Booking and tracking data can sync to Dataverse, letting Power Automate flows, Power BI reports or a customer-facing portal consume tracking events. We can include a sample Power Automate flow and expose the data through the BC OData/REST API as part of the build.