Food & Beverage Processing for Business Central

This is build-to-order, so there is a real lead time. After a short scoping call to map your recipes, lot rules, UoM conventions and QC stages, a typical build-and-install runs about 3 to 6 weeks depending on complexity (catch-weight and multi-stage QC add time). We confirm a firm date in writing after scoping. We then install it as a per-tenant extension on your tenant and validate it with you before go-live — there is no instant AppSource download.

Because the solution is delivered as a per-tenant AL extension built entirely with table/page extensions and event subscribers — never by modifying standard objects — Microsoft's monthly Business Central service updates do not break it. Your build includes a post-go-live support window for fixes and questions, and we offer ongoing support/maintenance plans for enhancements, new recipes, regression checks against major BC releases, and admin help. You also receive the full AL source under license, so you are never locked in.

No. It installs as an isolated per-tenant extension that layers on top of standard Item, BOM, Item Tracking and Production Order objects via event subscribers. Your base application, existing data and other extensions are untouched, and the extension can be uninstalled cleanly. We install behind a sandbox validation first whenever your environment allows it.

Yes. All key entities — lots, recipes, QC results, shelf-life and expiry status — are exposed through the Business Central REST/OData API, so the data flows into Power BI dashboards, Power Automate flows and Dataverse / the wider Power Platform. We can set up the initial API pages and a starter integration as part of the build on request.

Both. The extension is the same AL codebase whether you run Business Central online (SaaS) or on-premises. For SaaS we deploy through extension management on your tenant; for on-prem we publish and install against your service instance. We confirm your version and environment type during scoping so the build targets the right runtime.

That is exactly why this is build-to-order rather than a fixed app. The scoping phase captures your real formulas, yield and scrap behavior, catch-weight rules, FEFO logic and inspection stages, and the AL build is tailored to them. If a requirement falls outside the core scope, we quote it transparently before building — no surprises.