Production Worksheet & Digital Work Instructions

This is a build-to-order engagement, not an instant download. Typical lead time is 2–4 weeks depending on how many operations and routings we configure. The flow is: scoping call and requirements sign-off, build on our side, review on your staging database, then deployment to production with training. You get progress checkpoints throughout — nothing ships to production until you approve it on staging.

Every engagement includes a post-go-live support window for bug fixes and adjustments. Because you receive the full source code and own it, you're never locked in. We also offer optional maintenance/SLA plans covering Odoo version upgrades (e.g. moving your instructions module from 17 to 18 or 19), new operations, and enhancements. Update requests are scoped and quoted transparently.

Odoo 17, 18 and 19, on both Community and Enterprise. The module depends only on the standard Manufacturing (mrp) app, so it works whether or not you have Enterprise. We target your exact running version and test the install on a copy of your database before touching production.

No. The module extends Odoo's native routing and work-order models (mrp.routing.workcenter, mrp.workorder) additively rather than overwriting core behavior, and we install it upgrade-safe. During scoping we review your current MRP customizations so the instruction views and checklist logic layer cleanly on top. If you have existing customizations, we account for them in the build plan.

Yes. Mandatory checklist and acknowledgement steps are enforced with a server-side Python constraint on the work order — the operation cannot be marked Done until required items are confirmed. Every acknowledgement is timestamped and linked to the manufacturing order, giving you an audit trail rather than an honor system.

Each instruction has a controlled lifecycle — draft, approved, active, superseded — with only one active revision per operation at a time. Authors edit a draft, an approver promotes it, and the previous version is retained (never deleted) with author, date and change note captured in Odoo's chatter. Operators always see the current active revision, and you keep full history for compliance.

Yes. All models are exposed over Odoo's standard XML-RPC and JSON-RPC APIs, so a kiosk app, MES, BI tool or reporting layer can read instruction content and acknowledgement/issue records. We can also add scoped API endpoints or automated actions (e.g. push a Slack/email alert on a reported issue) as part of the build.