A build-to-order AL extension that adds pull-based Kanban loops and lean material flow to Business Central, so line-side stock refills on real consumption signals instead of MRP pushes. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A build-to-order AL extension that adds pull-based Kanban loops and lean material flow to Business Central, so line-side stock refills on real consumption signals instead of MRP pushes.
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
Electronic Kanban cards with full lifecycle states (active, in-transit, returned, on-hold) stored in dedicated AL tables
Kanban loop master linking item, supplying supermarket/supplier and consuming line-side bin
Consumption-triggered replenishment via AL event subscribers on item, consumption and bin movement postings
Configurable replenishment source per loop: transfer order, purchase order, or production order
Two-bin and supermarket stocking modelled via table and page extensions on Location and Bin
Line-side / point-of-use stocking locations with trigger-quantity thresholds per bin
Business Central's native planning is push-based: the planning worksheet and MRP/MPS engine generate supply from forecasts and reorder policies. That works for procurement, but it floods the production floor with material nobody is consuming yet. Kanban & Lean Replenishment flips the signal — line-side stock refills only when the floor actually pulls it.
ECOSIRE builds this as a per-tenant AL extension installed directly on your Business Central environment (Online or on-prem). It is not an instant AppSource download — we develop it against your item master, locations and bin structure, deploy it as a signed extension, and support it after go-live.
The extension introduces a Kanban loop master record linking a stocked item to a supplying location (supermarket or supplier) and a consuming line-side bin. Each loop owns a number of electronic Kanban cards sized by your demand and lead time. When consumption is posted — via item journal, consumption journal, or a point-of-use scan — an event subscriber detects the bin drop below its trigger and raises a replenishment signal: a transfer order, purchase order, or production order depending on the loop's replenishment source.
Two-bin and supermarket stocking are modelled natively with table and page extensions on Location and Bin, plus a new Kanban Loop, Kanban Card, and Kanban Signal table set. A Kanban sizing calculator computes card count and quantity from average consumption, replenishment lead time and a safety factor, so loops stay right-sized as demand shifts.
Signals are driven by a job queue entry for time-based sweeps and by real-time event subscribers for consumption postings. Everything is exposed through the BC OData/REST API and custom API pages so MES, scanners, or Power Platform flows can read loop status and confirm card returns.
Honest scope: this is a focused lean-execution layer. It complements — not replaces — BC manufacturing and planning.
Runs pull-based replenishment on the floor and wants line-side stock to refill on real consumption signals instead of MRP pushes, with right-sized Kanban loops they can tune.
Manages supermarkets, two-bin systems and transfer flows; needs visibility of open signals, overdue cards and which loops are over- or under-sized.
Owns the BC environment and needs a properly governed per-tenant extension with permission sets, job queue entries and clean API surfaces rather than ad-hoc customisations.
Buy the license on ecosire.com and download the Kanban & Lean Replenishment module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Kanban & Lean Replenishment, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Pull-based replenishment triggered by real consumption postings | ||||
| Electronic Kanban cards and loops as first-class BC records | ||||
| Two-bin / supermarket stocking with line-side bins | ||||
| Kanban sizing calculator (card count from consumption + lead time) | ||||
| Built and validated against your exact items, locations and bins | ||||
| Installed and supported on your tenant by the builder, with re-validation each BC release | ||||
| OData/REST API surface for MES, scanners and Power Platform |
No. It is a build-to-order per-tenant AL extension. ECOSIRE develops it against your item master, locations and bin structure, then deploys the signed extension to your Business Central sandbox for UAT before promoting it to production. There is no instant marketplace install — that is deliberate, because Kanban loops only work when they reflect your real material flow.
Typical lead time is 2 to 4 weeks from kickoff, depending on the number of loops, your bin/location structure and how many replenishment sources (transfer, purchase, production) you use. We confirm a firm schedule after a short scoping call and a look at your current locations and items. Installation onto your environment and UAT are included in that window.
The one-time build price includes deployment plus a warranty period for fixes after go-live. Because it is a per-tenant extension, we recompile and re-validate it against each Business Central monthly and major release so it stays compatible. Ongoing enhancements, new loops, or a support retainer are available as a separate agreement — you are never locked in, and source ownership terms are spelled out in the handover.
No, and it shouldn't. Native planning stays in charge of forecast-driven procurement and end-item planning. This extension adds a pull-based execution layer for line-side replenishment that fires on consumption. The two coexist: MRP handles the push side, Kanban loops handle the floor-level pull.
Yes. The extension exposes loops, cards and signals through custom OData/REST API pages, so a scanner app, MES, or a Power Apps/Dataverse surface can confirm card returns and trigger replenishment. We can build a lightweight Power Apps shop-floor screen as an add-on if you want point-of-use scanning.
A build-to-order AL extension that adds pull-based Kanban loops and lean material flow to Business Central, so line-side stock refills on real consumption signals instead of MRP pushes.