This is a build-to-order module, not an instant apps.odoo.com download — you never install it yourself. ECOSIRE designs, develops, installs, and supports it for you. Typical delivery is one working week from a confirmed spec, depending on how many product families, parameter sets, and customer-specific profiles you run and whether a LIMS/portal integration is in scope. We build in a staging environment first, print-test against your real lots, then do a controlled production cutover.

Every engagement includes a post-go-live support window for bug fixes and questions, and we hand over clean, documented source into your Git so nothing is locked to us. We build and test the module against Odoo 17, 18, and 19; when you upgrade your Odoo version we offer a compatibility/upgrade pass so the module and its QWeb report keep working. Ongoing enhancements — new parameters, extra customer specs, additional report layouts — are available under a support retainer or fixed-scope change request.

Both. If you run Enterprise with the Quality (quality_control) app, we build directly on the quality checks and measurements you already capture against each lot. If you are on Community without the Enterprise Quality module, we add a lightweight measurement-capture layer on the lot so results still flow into the same specification and pass/fail engine. The certificate, spec profiles, and API behave identically either way.

Pass/fail is computed in Odoo, not typed by a person. Each specification parameter carries a lower/upper limit (and optional target and method precision), and a stored computed field — using @api.depends on the measured result and the applicable limits — evaluates each parameter and rolls the results up to an overall lot disposition. Because it is driven by the same data the ERP holds, the printed certificate is always mathematically consistent with the record. If a measurement or a customer limit changes, the verdict recalculates automatically.

Yes. Specification profiles are resolved by product and, when present, by customer, so one product can ship against your internal release spec for most customers and a tighter or extended spec for a specific customer — extra parameters, narrower limits, or different reporting rules. The generator picks the correct profile automatically when it builds the CoA for that delivery.

Yes. An automated action generates and attaches the branded PDF CoA to the delivery order (and optionally the invoice) when the picking is validated, and an optional scheduled ir.cron can sweep validated deliveries in bulk and flag any lot missing a required measurement before it can ship. The finished certificate and its structured results are exposed over Odoo's XML-RPC / JSON-RPC API, so an external LIMS, a customer portal, or EDI can pull them without manual export.