No. This is a build-to-order extension. ECOSIRE designs it to your specific approval matrix, builds it in AL as a per-tenant extension, and installs it directly on your Business Central environment. There is no public AppSource listing — you get a solution tailored to your production process rather than a generic app.

A standard configuration is usually delivered in about 2 to 4 weeks: a short discovery to map your approval stages, thresholds, and roles; build and internal QA; UAT on your sandbox tenant; then production install and hypercare. More complex multi-plant or heavily customized approval logic can extend this, and we confirm the timeline in writing before work begins.

Because it is built as a per-tenant AL extension following Microsoft's extension model, it is designed to survive Business Central's monthly service updates. ECOSIRE offers an ongoing support and compatibility option that covers monitoring against Microsoft's update waves, fixes, and minor enhancements. The one-time build price covers delivery and initial hypercare; continued support is a separate agreement.

It is delivered as an isolated per-tenant extension using event subscribers and table/page extensions rather than modifying base objects, which is the same model AppSource apps use. During build we test against your installed apps in a sandbox first, so coexistence is verified before anything reaches production.

Yes. The extension exposes approval status and the full audit history through Business Central REST/OData API pages. That lets you build Power BI dashboards on approval cycle times and bottlenecks, or sync the data into Dataverse for Power Automate flows and Power Apps without scraping the UI.

Yes. You receive the AL source in a Git repository as part of the deliverables, so the customization is your retained IP. You are never locked to ECOSIRE — though most clients keep us on for ongoing support because we know the codebase and your update cadence.