Open Mercato: Open Source CRM and ERP Framework Explained
What Open Mercato includes, what still needs implementation, and how to decide whether this modular TypeScript foundation fits your organization.
Content directory
Find the right guide by the decision you are making. Every entry is an ordinary, direct link to its English or Polish counterpart.
07
Start with the foundation, ownership, and project shape.
What Open Mercato includes, what still needs implementation, and how to decide whether this modular TypeScript foundation fits your organization.
Understand how Open Mercato routes, services, modules, infrastructure, and data fit together through five source-backed system flows.
Trace module discovery, dependency enforcement, DI, editions, standalone apps, generated registries, and business-module boundaries.
Follow scoped reads, command-backed writes, validation, RBAC, encryption, custom fields, and read-model synchronization.
Understand UMES extension surfaces, typed events, persistent subscribers, realtime bridges, workflows, and compensation boundaries.
Compare search, cache, queue, scheduler, webhooks, storage, provider boundaries, retries, credentials, and operating responsibility.
Review design and i18n rules, AI approval, compatibility classes, generated-file lifecycle, commands, checklists, specs, and glossary terms.
03
Test fit, readiness, risk, governance, and alternatives.
Model the real drivers of Open Mercato implementation and operating cost without mistaking an open source license for a complete project budget.
Assess deployment-specific evidence for security, recovery, operations, performance and ownership before a production decision.
Separate framework security primitives from application, hosting, operational and organizational controls required for a deployment.
03
Plan architecture, migration, integrations, and delivery.
A phase-by-phase guide to discovery, architecture, migration, testing, go-live and ownership in an Open Mercato implementation.
Choose between APIs, events, webhooks, scheduled sync and files while defining ownership, reconciliation and failure behavior.
A rigorous route from source inventory and field mapping through trial migrations, reconciliation, cutover and rollback.