Dolibarr ERP & CRM is worth a look if you run a small or mid-sized business and want to consolidate contacts, sales, invoicing, stock, and accounting in one open source web application. This article is a source and documentation review of the Dolibarr/dolibarr repository as of the August 9, 2026 snapshot: repository metadata, README, release notes, and open issues. No local installation or runtime testing was performed, so behavior claims come from the repository and its maintainers rather than from hands-on verification.

The short answer

Dolibarr is a reasonable candidate if your business needs modular CRM, sales, invoicing, stock, and accounting without per-user license fees, and you have, or can buy, PHP and database administration skills to deploy and maintain it. The project is actively maintained: the repository was pushed as recently as August 9, 2026, and the evidence shows releases on the 23.0, 22.0, and 18.0 lines. It is not a zero-maintenance product, though. Before production, verify the supported PHP and database versions for your chosen release, test an upgrade on a copy of your data, and confirm that your country’s tax and electronic invoicing requirements are covered by the core or a maintained addon, because European e-invoicing remains an open feature request.

Key facts at a glance

What Dolibarr is, according to the maintainers

The repository describes Dolibarr as an open source web application written in PHP that manages company or foundation activity, including contacts, suppliers, invoices, orders, stocks, agenda, and accounting, aimed at businesses of any size, foundations, and freelancers. The README lists around 100 modules available by default and claims more than 1,000 addons on the DoliStore marketplace, with commercial support available through preferred partners. The module list covers CRM and sales, products and services, stock and warehouses, barcodes, batches and serials, bill of materials and manufacturing orders, point of sale, purchasing, finance and accounting, projects and tasks, HR, document management, LDAP, payment platforms, and REST and SOAP APIs.

Those are maintainer descriptions, and some should be read as claims rather than guarantees: multi-company via an external module, code described as easy to maintain thanks to a trigger and hook architecture, upgrades from any version after 2.8 without breakage, and a CII Best Practices badge shown in the README. The badge’s presence does not confirm a passing result, and upgrade claims should be tested rather than taken on faith. The README is also candid about gaps: task dependencies in projects, a payroll module, and native embedded webmail are listed as not yet supported.

Who should consider Dolibarr

Consider Dolibarr if your operations fit standard, modular business processes and you want one application for customers, quotes, orders, invoices, stock, projects, and accounting without per-user license fees. The module-based design lets you enable only what you need, which keeps initial complexity lower than a monolithic ERP, and the README claims compatibility with MariaDB, MySQL, and PostgreSQL, so existing PHP shops can pilot it with familiar infrastructure.

It is a weaker fit if your requirements start at the edges of the feature list. Payroll is explicitly unsupported in the README, deeper manufacturing planning has been an open feature request since December 2021, and European electronic invoicing (FacturX/XRechnung/ZUGFeRD) is an open request with 53 comments that was still open at the snapshot. If any of those are mandatory for your business, evaluate Dolibarr only with a maintained addon or integration already in hand.

Maintenance signals to weigh

• Active development: the repository was created June 26, 2011, and last pushed August 9, 2026, per the snapshot.
• Multiple release lines: the evidence includes 23.0.3, 22.0.5, and 18.0.10 all published in May 2026, which suggests the maintainers backport fixes to older branches.
• Security backports are visible in release notes: 22.0.5 and 23.0.3 list fixes for SSRF via webhooks, SQL injection, and several GitHub Security Advisories, some with external researchers credited. You still have to apply upgrades and test them.
• Open issues stood at 1,126 at the snapshot, and some requests have been open for years, including manufacturing planning (#19661, since 2021) and e-invoicing (#30078, since 2024).
• Regressions happen: issue #37415 reports that in 23.0.0 users could not edit a standard invoice that was not the last reference, and the issue remained open at the snapshot.

Deployment concerns before production

The README positions Dolibarr as a PHP application on MariaDB, MySQL, or PostgreSQL, compatible with any cloud solution that matches those prerequisites. Install routes include packaged installers (DoliWamp for Windows, DoliDeb for Debian and Ubuntu, DoliRpm for Red Hat-family distributions), a Docker image, a generic manual setup on any PHP web server, and commercial ready-to-use SaaS offers with associated costs.

Three things need attention before production. First, PHP and database compatibility: the README badge shows PHP greater than or equal to 7.2, but the README points to the wiki for exact per-release requirements, and release notes reference PHP 8.1 warning fixes while an open bug was reported on PHP 8.2, so verify the support matrix for your planned version rather than trusting the badge. Second, upgrade behavior is a maintainer claim you should test on staging: the README says upgrades work from any version after 2.8 without breakage, with a documented flow of backup, file replacement, and running the install page, plus manual removal of an install.lock file when present. Third, plan where data lives: generated and uploaded documents are stored in a documents directory, and that is also where the install.lock file that gates upgrades is found.

Because no runtime evidence is attached to this review, performance under real data volumes, upgrade behavior, and third-party module compatibility are unknown here and must be established in your own pilot.

Limitations and open feature requests

• European e-invoicing: issue #30078 requests FacturX/XRechnung/ZUGFeRD import and export and cites upcoming obligations; it was still open with 53 comments as of June 28, 2026.
• Manufacturing: bill of materials and manufacturing orders are in the README feature list, but MRP evolution (#19661) has been open since December 2021 with no closure in the evidence.
• Payroll: the README explicitly states that Dolibarr does not yet support a payroll module.
• Batch and serial tracking: issue #27456 proposes data model changes for batch and serial numbers and remains open.
• AI assistant: issue #38356 describes an MCP server and chat assistant that a contributor says is in core on the develop branch, experimental, and targeted around version 24; the issue was open with a long to-do list at the snapshot, so treat it as an experiment rather than a production feature.

Alternatives and evaluation questions

This review does not benchmark Dolibarr against other ERPs, and the evidence cannot settle the comparison for you. Use the questions below to define what a pilot must prove in your environment:

• Which modules will you actually enable, and which are core versus addons in your country and tax regime?
• Do mandatory workflows, such as e-invoicing, payroll, or production planning, exist in core, or do they depend on third-party addons? Who maintains those addons, and what happens if they stop?
• What PHP and database versions are supported for the release you plan to run, and what is the realistic upgrade path two years from now?
• Do the REST and SOAP APIs cover the integrations you need, such as payment platforms, e-commerce, LDAP, and reporting, and who will build and maintain that glue?
• How will you test upgrades and security patches, restore from backup, and manage the documents directory as it grows?

The verdict

Dolibarr is a credible open source ERP/CRM for organizations that fit its modular, standard-process design and can take on PHP hosting and regular maintenance. Active development, multiple release lines, security backports, and a large module ecosystem make it worth a structured pilot for small and mid-sized businesses, freelancers, and foundations. The conditions are equally clear: confirm compliance-critical features such as electronic invoicing and country-specific tax handling, budget for upgrade and patch management, and prove the maintainers’ upgrade claims on staging. If payroll, advanced manufacturing, or mandatory e-invoicing dominate your requirements today, look elsewhere or secure a maintained addon before starting.

Where custom development and maintenance may be needed

Dolibarr’s trigger and hook architecture and REST/SOAP APIs are the natural points for custom work, provided you have PHP development capacity. Common needs include custom modules for process-specific fields, payment and e-commerce integrations, PDF and ODT template changes, data migration from legacy systems, and the ongoing work of applying security patches, running upgrades, and managing PHP and database compatibility over time. The README’s data export and import features help with migration, but mapping your legacy data into Dolibarr’s structure is still a planning exercise.

Sources

• Dolibarr/dolibarr GitHub repository
• Dolibarr 23.0.3 release notes
• Dolibarr 22.0.5 release notes
• Issue #30078: FacturX/XRechnung/ZUGFeRD support
• Issue #37415: cannot edit a standard invoice that is not the last reference
• Issue #38356: AI MCP server and chat assistant

I’m Xiang Peng at XP812, and I help businesses evaluate and maintain PHP-based business software, including deployment, data migration, upgrades, and custom modules. If you are weighing Dolibarr for a specific business, I can help you scope the pilot, identify where custom development is genuinely needed, and plan an upgrade path that does not leave you stuck on an old release.