Your ERP may cover the standard process while the exceptions still live in spreadsheets. Open Mercato gives your team a modular CRM and ERP foundation to turn those exceptions into software you control.
MIT open source
1,928 stars on GitHub
50+ pluginsOdoo offers extensive customization. Reviews also describe the work needed to fit specialized processes. Open Mercato makes custom development a first-class part of the application, with modules and extension points your team can own.
Odoo documents additional code adaptation and testing for customized databases. With Open Mercato, agree a release and test plan for your extensions, supported by access to the application source.
A shipping problem can be a bounded implementation. Start with the workflow that creates daily friction, connect the necessary records and evaluate the next step using real operations.
Start with companies, contacts, deals, quotes and order records.
Use products, variants, sales channels, pricing and tax foundations.
Build the approvals, packing workspaces or domain records that make the process work for your business.
Reuse authentication, permissions, data access and events across your custom modules.
Compare Open Mercato with Odoo's paid Enterprise plans for a multi-app CRM and sales implementation.
| What your team gets | NO CORE SEAT FEESOpen MercatoMIT-licensed application core | Odoo EnterpriseStandard / Custom plans |
|---|---|---|
| Where Open Mercato adds control | ||
| Application core under an MIT licence | ✓ | ×Enterprise licence |
| No per-user licence fee for the multi-app core | ✓Hosting and services extra | ×Paid Enterprise seats |
| Capabilities available in both | ||
| Companies, contacts and CRM pipelines | ✓ | ✓ |
| Quotes and sales orders | ✓ | ✓ |
| Products and variants | ✓ | ✓ |
| Pricing and sales adjustments | ✓ | ✓ |
| Roles and permissions | ✓ | ✓ |
| Custom fields and modules | ✓ | ✓Custom plan |
| External APIs | ✓ | ✓Custom plan |
| Self-hosted deployment | ✓ | ✓Custom plan |
Scope: paid Odoo Enterprise Standard / Custom plans. Odoo Community is a separate open-source edition; One App Free is a different offer. Both platforms support customization and need maintenance. Accounting and specialist ERP requirements are assessed separately.
Reviewed 12 November 2026. Sources: Odoo plans and deployment · Odoo editions and licences · Open Mercato core · Customer records
| What matters | Odoo | Open Mercato |
|---|---|---|
| Starting point | An integrated suite of business applications. | Core CRM, sales and catalog modules plus an extensible application foundation. |
| Custom development | Studio and custom modules, with availability depending on deployment and plan. | TypeScript modules, custom entities, APIs and application extensions. |
| Updates | Customized databases require adaptation and testing during upgrades. | Your team schedules and tests application and dependency updates. |
| Commercial model | Community and commercial editions have different capabilities and terms. | MIT-licensed core, with delivery, hosting and support scoped separately. |
| Specialist ERP scope | Broad suite including accounting and manufacturing applications. | Choose domain implementations and scope accounting, localization and industry requirements individually. |
| Rollout | Select the apps and migration scope for the implementation. | Begin with a bounded workflow and integrate it with the existing system of record. |
MDM NT connected packing, carrier labels and tracking to its existing ERP. The company used a concrete operational problem as the first step in a broader transformation.
Read the MDM NT story ↗
List apps, custom modules, Studio changes, scheduled actions, integrations and the processes they support.
Select one workflow and define record ownership. Decide which financial and operational systems it will connect to.
Map external IDs, customer and product data, document states and required history. Test representative transactions.
Reconcile the pilot, agree operating responsibilities and introduce the next process when the first is working.
Odoo supports extensive customization through configuration, Studio and custom modules. The relevant decision is the cost and ownership of your specific changes, integrations and future upgrades.
Review the apps you actually depend on. CRM and sales foundations are available, while accounting localization, payroll and specialist business rules require a separate fit assessment and implementation scope.
Yes, an implementation can introduce a specific workflow alongside an ERP through integrations. MDM NT's shipping project demonstrates this approach. Your connection and synchronization rules are part of the project.
Your operating team owns release planning and regression testing. Source access and modular extensions provide control over that work, while the deployment still needs active maintenance.
We can help you scope the records, rules and integrations needed to turn it into a working application.
Talk through your process, integrations and implementation needs with the Open Mercato team.