Dolibarr Custom Module Development

A custom module can be appropriate when standard configuration, workflows, and established third-party modules cannot represent an important process adequately. Expected value must justify development and maintenance effort.

Anexum reviews Dolibarr standard modules, settings, dictionaries, extra fields, existing Dolistore modules, APIs, and possible process changes. Custom development is not automatically the best first solution.

Options include custom objects, cards, lists, permissions, menus, numbering, state models, triggers, hooks, scheduled jobs, PDF and ODT documents, dashboards, imports, exports, REST endpoints, and webhooks.

The process is described through roles, triggers, data, rules, exceptions, permissions, and acceptance criteria. Open decisions are made visible before estimation.

Architecture decisions document module structure, data model, extension points, integrations, error handling, migration, security boundaries, and supported Dolibarr and PHP versions.

Testing covers installation, activation, permissions, core workflow, error cases, data migration, documents, APIs, scheduled jobs, deactivation, and upgrades. Customer acceptance uses the agreed acceptance criteria.

Supported versions, maintenance scope, response path, and the procedure for Dolibarr updates are agreed for each module. Dependencies on third-party modules are documented explicitly.

For an Austrian construction company we built DoliConstruct, a construction-industry solution on top of Dolibarr. It connects ÖNORM B 2061 K3 cost calculation, the bill of quantities under ÖNORM A 2063, the offer, the project, and post-calculation in one continuous data flow. Time tracking with Austrian allowances, material consumption per bill-of-quantities position, equipment, and per-site stock all run in the same system. A bmdimport submodule pulls employees and cost centres from BMD accounting, and the BMD payroll export returns the recorded hours. This removes the duplicate data entry between site, office, and payroll.

The same company also runs MobileUI, a mobile PWA for warehouse and site work. Stock staff scan items with the device camera, view stock levels with movement history, and place material requests through a cart with warehouse selection directly on a phone. The interface is built for large touch targets and offline use, so it stays reliable on site and in the warehouse. Both modules are built through the custom directory, tested, and maintained for version compatibility.