No. This is built-to-order. ECOSIRE develops the app in AL as a per-tenant extension scoped to your Business Central environment, installs it on your tenant (sandbox first, then production), and supports it. There is no instant AppSource download — the value is that it's mapped to your bins, license-plate logic and warehouse documents rather than a generic listing.

A typical build runs about one working week from confirmed requirements, depending on the complexity of your bin structure, lot/serial tracking and license-plate rules. We start with a scoping call, build against your BC sandbox for UAT, then schedule a documented production cutover. We give you an honest date after scoping — we don't promise same-day.

Every build includes a defined post-go-live support window for fixes and questions. Because it's an extension (not modified base code), it survives Business Central's monthly and major updates well; we re-test compatibility against new BC releases and patch the extension if Microsoft changes a relevant API or base object. Longer-term support and enhancement plans are available.

It's designed not to. We use table extensions, page extensions and event subscribers instead of overwriting base objects, which is Microsoft's recommended upgrade-safe pattern. You also receive the full AL source, so you're never locked out of your own code, and ECOSIRE validates the extension against each major BC version during your support window.

The app is touch-first and tolerant of brief connectivity gaps — scans are queued and posted to Business Central via the REST/OData API and Job Queue when the connection returns, so a dead spot in the racking doesn't lose a pick. Sustained offline operation across a full shift is a larger scope we'll size during the scoping call if you need it.