Microsoft Dynamics 365 Business Central handles your inventory, purchasing and sales — but it has no native concept of a recipe, a menu plate, or food-cost variance. This extension fills that gap. ECOSIRE designs, builds and installs it as a per-tenant AL extension on your own Business Central environment (cloud SaaS or on-prem), so it lives alongside your real item ledger, vendors and posted sales rather than in a disconnected app.

We model recipes and sub-recipes as a costed bill-of-materials over your existing Item table, using table and page extensions rather than parallel tables, so a recipe's cost rolls up live from each ingredient's BC unit cost. A menu engineering view classifies every dish on the classic margin-vs-popularity matrix (Star / Plough Horse / Puzzle / Dog) using your actual posted sales lines. On each sale, an event subscriber on the sales posting routine depletes theoretical ingredient quantities and records theoretical-vs-actual food-cost variance against counted stock. Allergen and nutrition tags travel with every recipe and surface on prep sheets.

Because this is built-to-order, it is not an instant Microsoft AppSource download. After purchase, ECOSIRE scopes your recipe structures, menus and outlets, develops the extension, deploys it to your sandbox for sign-off, then installs it on production with the right permission sets and job queue entries for nightly variance and depletion runs. Costing data is exposed over the BC REST/OData API for Power BI and Dataverse / Power Platform flows. You own the result on your tenant; ECOSIRE supports and updates it across Business Central release waves. Typical delivery is a few weeks depending on menu complexity and number of kitchens.