A per-tenant Business Central extension for non-conformance reports, root-cause analysis and corrective/preventive actions — built, installed and supported by ECOSIRE on your tenant, with full workflow and audit trail for ISO 9001. One-time license from $499.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A per-tenant Business Central extension for non-conformance reports, root-cause analysis and corrective/preventive actions — built, installed and supported by ECOSIRE on your tenant, with full workflow and audit trail for ISO 9001.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Microsoft Dynamics 365 Business Central handles items, lots, production orders and vendors — but it has no native quality module for logging non-conformances or driving a closed-loop CAPA process. Quality teams pursuing ISO 9001 end up tracking it all in spreadsheets that disconnect from the ERP and collapse under audit.
NCR card and list as native AL table/page extensions, with table relations to Item, Lot No. Information, Production Order, Sales/Purchase Order and Vendor for full lot-to-supplier traceability
Structured 5-Why and 8D (D1–D8) root-cause workflow with stage tracking from Open through Investigation, CAPA, Verification and Closed
CAPA action records with assigned owner, due date, action type (corrective vs preventive) and effectiveness-verification step
Job Queue–driven escalation: overdue CAPAs auto-notify owners and quality managers on a scheduled background entry
Supplier Corrective Action Request (SCAR) documents linked to the Vendor card, with response due dates and acceptance status
Cost-of-quality capture (scrap, rework, return cost) and recurrence counters surfaced as FlowFields for management dashboards
Non-Conformance & CAPA Management is an AL extension that ECOSIRE builds, installs and supports directly on your Business Central environment. It is not an instant AppSource download — we scope it to your processes, develop it against your tenant, and deploy it as a per-tenant extension you own.
The extension adds a Non-Conformance Report (NCR) card and list, implemented as new AL tables and pages, with table relations to Item, Lot No. Information, Production/Sales/Purchase Order and Vendor so every NCR is traceable to the lot, order and supplier that caused it. A structured 5-Why and 8D root-cause workflow drives each NCR through Open → Investigation → CAPA → Verification → Closed states. Corrective and preventive actions are assignable records with owners, due dates and Job Queue–driven escalation reminders. Supplier Corrective Action Requests (SCAR) link to the vendor, and cost-of-quality plus recurrence are captured as FlowFields for management reporting.
Approvals run on Business Central's native workflow engine and document-approval framework, so sign-offs are enforced and every change is captured by the platform's Change Log for a defensible audit trail. Event subscribers can auto-raise an NCR from a failed inspection or rejected receipt. We ship dedicated permission sets and, where required, expose NCR/CAPA data via the standard OData/REST API or surface it in Power BI and the Power Platform via Dataverse.
Owns the QMS and needs a closed-loop, auditable CAPA process inside the ERP rather than disconnected spreadsheets, with evidence ready for certification audits.
Logs daily non-conformances on the shop floor, runs 5-Why/8D investigations, and assigns corrective actions tied to the actual lot, production order and defect.
Issues SCARs to vendors, tracks supplier response and effectiveness, and uses recurrence and cost-of-quality data to drive supplier scorecards.
Wants a clean per-tenant extension that respects BC's permission model, upgrades safely across BC release waves, and exposes data via standard OData/Dataverse without custom hacks.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Non-Conformance & CAPA Management-Moduls von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Non-Conformance & CAPA Management“ und klicken Sie auf „Installieren“.
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| NCR linked to lot, order and vendor inside the ERP | ||||
| Structured 5-Why / 8D root-cause workflow | ||||
| CAPA assignment, due dates and Job Queue escalation | ||||
| Supplier Corrective Action Request (SCAR) linked to Vendor | ||||
| Cost-of-quality and recurrence tracking | ||||
| Native BC approval workflow + Change Log audit trail | ||||
| Tailored to your exact quality process | ||||
| Customer owns the AL source code | ||||
| OData/REST API + Power BI / Dataverse integration | ||||
| Built, installed and supported for you (no in-house AL team needed) |
This is a build-to-order extension, not an instant AppSource download. Typical delivery is 3–5 weeks: a scoping workshop, AL development against a sandbox, your UAT, then production install. The exact timeline is confirmed after scoping, since it depends on how much your NCR/CAPA flow deviates from the standard pattern and whether Power BI/Dataverse integration is in scope.
The build includes a warranty window and an ongoing support option covering bug fixes, configuration help and compatibility with Business Central's twice-yearly release waves (so the extension keeps installing cleanly as Microsoft updates BC). You own the AL source, so you can also extend it yourself or have ECOSIRE add modules later under a support agreement.
It deploys as a per-tenant extension. We install and test on your Business Central sandbox first, run UAT with your quality team, then publish to production through the Admin Center extension management. Because it is an extension (not customized base code), it layers cleanly over standard BC and is removable.
Yes. We use AL event subscribers to hook into events such as rejected purchase receipts, failed quality inspections or item-tracking flags, so an NCR can be raised automatically with the source lot, order and vendor pre-populated. The exact triggers are agreed during scoping.
It is designed for that. Every status transition is logged, approvals run on BC's native document-approval engine with full approval-entry history, and the platform Change Log captures field-level changes. Auditors get a defensible, time-stamped record from NCR creation through CAPA verification and closure, all inside the ERP.
A per-tenant Business Central extension for non-conformance reports, root-cause analysis and corrective/preventive actions — built, installed and supported by ECOSIRE on your tenant, with full workflow and audit trail for ISO 9001.