Quick facts
- Price
- $799.00 USD
- dynamics_365_business_central versions
- —
- Setup time
- 60 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Batch & Potency Compliance
A build-to-order Dynamics 365 Business Central extension that adds potency-aware inventory, auto-adjusted consumption, electronic batch records, and QA quarantine/release gating for chemical, nutraceutical, and pharma manufacturers.
$799.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
Per-lot potency/assay value stored on Lot No. Information via table extension, captured at receipt or QC posting
Automatic consumption adjustment on production orders so each batch reaches its target active concentration
Concentration/dilution calculator that back-solves component quantities from assay strength and target potency
Electronic batch record (batch ticket) linking consumed lots, potencies, operator and QA sign-offs, and deviations
Quarantine status on inbound lots with QA release gating that blocks consumption and shipment until approved
Regulated-substance and hazmat classification carried on the item and lot, surfaced on batch and shipping documents
AL event subscribers on BC posting routines so potency math runs at consumption/output posting without breaking core
Dedicated permission sets separating production operators from QA release authority for segregation of duties
Job Queue entry that flags expiring quarantine holds and approaching retest/expiry dates
OData V4 / REST API pages exposing batch records and lot potency for LIMS, Power BI, and Dataverse integration
Deviation and out-of-spec logging on the batch record with mandatory comment and approver capture
Potency-adjusted cost and inventory valuation so financials reflect actual active content consumed
About this Product
Standard Dynamics 365 Business Central tracks lots and item tracking, but it has no concept of potency. When you buy an active ingredient assayed at 92% and your formula targets 100% active, someone has to manually recalculate how much to consume on every production order. That math, done in spreadsheets, is where regulated manufacturers lose traceability and fail audits.
Why Choose Batch & Potency Compliance
Per-lot potency/assay value stored on Lot No. Information via table extension, captured at receipt or QC posting
Automatic consumption adjustment on production orders so each batch reaches its target active concentration
Concentration/dilution calculator that back-solves component quantities from assay strength and target potency
Electronic batch record (batch ticket) linking consumed lots, potencies, operator and QA sign-offs, and deviations
Quarantine status on inbound lots with QA release gating that blocks consumption and shipment until approved
Regulated-substance and hazmat classification carried on the item and lot, surfaced on batch and shipping documents
Batch & Potency Compliance is a per-tenant AL extension that ECOSIRE builds, installs, and supports directly on your Business Central environment. It stores an assay/potency value on every lot, then automatically adjusts component consumption on the production order so each batch hits its target active concentration. It captures a full electronic batch record (the "batch ticket") tying together consumed lots, their potencies, operator/QA sign-offs, and deviations. Regulated and hazmat substances carry their classification through the whole flow, and no lot ships until QA releases it out of quarantine.
The extension is delivered as proper AL objects: table and page extensions on Item, Item Ledger Entry, Lot No. Information, and Production Order; event subscribers that hook BC's posting routines so potency math runs at consumption posting (no broken upgrades); dedicated permission sets for production vs. QA; a Job Queue entry for quarantine-expiry checks; and OData/REST API pages so your LIMS or Power BI can read batch records. Because it is a per-tenant extension — not an AppSource listing — it is scoped to your tenant, versioned by ECOSIRE, and shipped through your sandbox before production.
This is genuinely build-to-order. After purchase we confirm your formula and assay rules, build against your sandbox, validate with your QA team, then publish to production and support it on an ongoing basis. It is not an instant download.
What you get
- Per-tenant AL extension (.app) built for your Business Central version, published to sandbox then production
- Table and page extensions on Item, Item Ledger Entry, Lot No. Information, and Production Order
- Configurable potency rules: target concentration, assay tolerance, and per-formula adjustment logic
- Permission sets for production and QA roles, plus a Job Queue entry for quarantine/retest checks
- OData/REST API endpoints and a sample Power BI / Dataverse connection for batch and potency data
- Source code handover, validation evidence pack, admin documentation, and post-launch support window
Who this is for
Production Manager
Runs regulated batch manufacturing and needs every production order to hit target potency automatically, with a defensible electronic batch record instead of spreadsheet math.
QA / Regulatory Lead
Owns release-by-QA, quarantine, and audit readiness; needs segregation of duties, deviation logging, and traceable assay-to-batch records for inspections.
Business Central Administrator
Maintains the tenant and wants potency logic delivered as a clean, upgrade-safe per-tenant extension with proper permission sets and API access — not customizations that break on the next BC update.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Batch & Potency Compliance module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Batch & Potency Compliance, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Batch & Potency Compliance Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Per-lot potency/assay value tracking | ||||
| Auto-adjusted consumption to hit target potency | ||||
| Regulated electronic batch record with QA release gating | ||||
| Regulated-substance / hazmat classification carried through flow | ||||
| Upgrade-safe AL extension (event subscribers, no base mods) | ||||
| Built, installed, and supported on your tenant by the vendor | ||||
| Source code handover and no vendor lock-in | ||||
| Tailored to your exact formulas and assay rules |
Frequently Asked Questions about Batch & Potency Compliance
+How long does delivery take, and how is the app installed?
This is build-to-order. After purchase we run a short discovery to confirm your formulas, assay sources, and QA release rules, then build the extension against your Business Central sandbox. Typical delivery is roughly 3 to 5 weeks depending on formula complexity and how many production lines and substance classifications are in scope. We install it as a per-tenant AL extension — published to your sandbox first for validation, then promoted to production by ECOSIRE. There is no AppSource download; the extension is scoped and versioned for your tenant.
+What does ongoing support and updates include?
After go-live you get a support window for defect fixes and questions. Because the extension is delivered as a per-tenant AL app, ECOSIRE versions it and re-tests it against each Business Central major update (the spring and fall waves) so the potency math and posting event subscribers keep working through upgrades. New rules, additional substance classifications, or extra API fields are handled as scoped change requests. You also receive the source code, so you are never locked in.
+Does standard Business Central not already handle this?
Standard BC handles lot and serial item tracking, expiration dates, and basic quality via item tracking — but it has no native concept of potency/assay or auto-adjusting consumption to a target active concentration, and it has no regulated electronic batch record with QA release gating. Those are exactly the gaps this extension fills, built on top of (not replacing) BC's native lot tracking.
+Will this break when Microsoft updates Business Central?
No. We deliver it the supported way: table/page extensions and event subscribers rather than modifications to base objects. That is the architecture Microsoft designed for upgrade safety. We also re-validate the extension against each major BC wave so the posting hooks and potency calculations continue to behave correctly.
+Can it connect to our LIMS, Power BI, or Power Platform?
Yes. The extension exposes batch records and lot potency through OData V4 / REST API pages, so your LIMS can push assay results in and read batch status out, Power BI can report on potency-adjusted batches, and Dataverse / Power Platform flows can be wired to quarantine and release events. We configure a sample connection as part of delivery.
Why Customers Trust ECOSIRE
SOC 2 Aligned
GDPR Compliant
Secure Stripe Payment
30-Day Money Back
Lifetime Updates
LGPL-3.0 License
Related Modules
Request a quote
Batch & Potency Compliance
A build-to-order Dynamics 365 Business Central extension that adds potency-aware inventory, auto-adjusted consumption, electronic batch records, and QA quarantine/release gating for chemical, nutraceutical, and pharma manufacturers.
- Per-lot potency/assay value stored on Lot No. Information via table extension, captured at receipt or QC posting
- Automatic consumption adjustment on production orders so each batch reaches its target active concentration
- Concentration/dilution calculator that back-solves component quantities from assay strength and target potency
- Electronic batch record (batch ticket) linking consumed lots, potencies, operator and QA sign-offs, and deviations