We implement Open Mercato: ERP, CRM and commerce on an architecture built for AI agents

We are a certified Open Mercato implementation partner. We build on a framework whose extensibility contracts are readable by AI agents, and where every change an agent proposes waits for a person to approve it.

Book a call Odoo services

Open Mercato Certified Agency. Free consultation, no obligations.

What is Open Mercato?

Open Mercato is a TypeScript framework for building CRM, ERP and commerce systems. It is not a finished ERP you configure in an admin panel: it is a set of modules and architectural decisions you build a company-specific system on. The vendor calls that starting point “Start with 80% Done” – authentication, permissions, multi-tenancy, audit trails and data encryption are already built, so the project budget goes into business logic rather than into foundations.

The project was created by Piotr and Tomasz Karwatka, the people behind Vue Storefront and the founders of Divante. The core is MIT licensed and public on GitHub; enterprise features ship in a separate package, outside the open source licence.

The stack is the ordinary web stack, and that is a feature rather than a lack of ambition: Next.js and TypeScript, PostgreSQL and MikroORM, Zod for validation, Redis for caching, Meilisearch for search. A developer who knows those tools already knows half of the system.

AI-native architecture

What sets Open Mercato apart from a classic ERP

ERP-class systems were designed long before anyone wrote code with an AI agent, and their architecture shows it. Open Mercato was designed the other way round: so an agent has somewhere to work, and a person keeps control over what the agent proposes.

Architecture agents can read

Modules declare their extension points and contracts, so an AI agent knows where it is allowed to write code. Instead of guessing, it works where the architecture expects it to.

Control

Approval cards

A write proposed by an AI assistant waits for an explicit approval before it changes any data. The decision stays with a person, not with the model.

Upgrades

Extensions instead of a fork

Customisations live in an overlay layer rather than in a patched core. The system stays upgradable with your own features in place, which is the most common reason implementations get stuck on one version.

Licence

MIT, no per-seat fee

The core is open source under the MIT licence: the code and the data stay yours, and the cost does not grow with every new person in the system. Enterprise features ship as a separate package under a separate licence.

Security

Permissions, audit, encryption

Roles and permissions, an audit trail with undo, and field-level encryption are part of the framework rather than something every project builds again from scratch.

Integrations

MCP and events

The system exposes its tools over the MCP protocol and runs on events internally. Connecting a storefront, a PIM or a data warehouse needs no rebuild of the core.

Scope of work

What we build on Open Mercato

The framework covers the areas we have worked in for years: B2B sales, order handling and product data. An implementation usually starts with one of them rather than with all of it at once.

CRM and sales pipeline
Orders and OMS
Product catalogue
CPQ and quoting
Self-service portals
Process automation

Choosing a system

Open Mercato or Odoo?

We implement both, so we have no interest in pushing the newer one. Odoo is a finished ERP, so an implementation starts with configuration. Open Mercato is a framework, so the system is built on it around your process. Below are the cases where we pick one or the other.

Open Mercato

The process is the company advantage and no off-the-shelf module holds it.
The team works in TypeScript and wants to own the system in house.
A digital product or a platform for many clients: multi-tenancy is standard here.
The company is leaving a low-code platform that stopped scaling.
The pace of AI agents working on the system code matters.

Odoo

A complete ERP is needed: manufacturing, warehouse, purchasing, invoicing.
The implementation should end in configuration, not in construction.
System maturity and a large ecosystem of ready applications matter.
Polish tax reporting, KSeF and JPK, is needed from day one.
The budget should go into the standard, not into a bespoke system.

How we work

What an Open Mercato implementation with Macopedia looks like

01
STEP 1
Workshop and scope
We map your processes and sort them into three groups: what the framework gives you out of the box, what we add as a module, and what this project deliberately leaves out. The workshop ends with a scope and an estimate, not with a declaration.
02
STEP 2
Architecture and decisions
The data model, module boundaries, extension points and integrations. This is the part the AI agents lean on later, so it is made by people at a whiteboard.
03
STEP 3
Iterative build
Short iterations, code review and tests. Agents speed up the repetitive half of the work: scaffolding, unit tests, documentation. Review and accountability stay on our side.
04
STEP 4
Integrations and data migration
We connect the storefront, the PIM, the warehouse, payments and couriers, and move customers, products, stock and documents over from your current system.
05
STEP 5
Go live and grow
Launch, team training and maintenance. We keep the core up to date while your extensions stay where an upgrade does not touch them.

A certified Open Mercato implementation partner

We are in the vendor’s partner programme at the Open Mercato Certified Agency level. The programme names the split of responsibility outright: the vendor answers for platform standards, security and production certification, the partner answers for delivery and for the client relationship. In practice that means one thing: the architectural risk does not sit with the company buying the system.

Behind that stands practice from outside the framework itself. We have been working since 2012, the team is 40+ specialists, and we have over 100 projects behind us: B2B platforms, PIM implementations, e-commerce stores and ERP systems. Open Mercato joins that set exactly where an off-the-shelf system would be the worse answer than one built around the process.

For how we connect a system like this to the rest of the company, see our system integrations page.

Not sure whether your process is a configuration of an existing ERP or a system built around it?

Book a call: we take the process apart into what fits the standard and what has to be built. You leave with a scope, not with a quote for everything.

Book a call

FAQ

Frequently asked questions

How is Open Mercato different from Odoo?

Odoo is a finished ERP: an implementation starts by configuring modules that already exist. Open Mercato is a framework: you get the foundation (authentication, permissions, multi-tenancy, audit, encryption) and build your own system on top of it. The first is cheaper when your process fits the standard. The second wins when the process is the company advantage and no off-the-shelf module can hold it.

Is Open Mercato free?

The core is MIT licensed, so there are no licence fees and no per-seat fees. The vendor sells an enterprise package and a subscription with support, architecture audits and security reviews separately. A project costs implementation work, hosting and optionally that subscription.

Is it a finished system, or do we have to build it?

You build it, but not from nothing. The vendor calls the starting point “80% done”: CRM, orders, catalogue, CPQ and self-service modules are there, the admin console is there, the security layer is there. The project adds the logic nobody else has.

Do AI agents write production code?

They write code that goes through review and tests like any other. The framework guards it from two sides: extensibility contracts tell an agent where it may write, and an approval card holds every data change until a person accepts it. What reaches production is the team’s responsibility, not the model’s.

Will Open Mercato integrate with our store, PIM or Odoo?

Yes. The system runs on events and exposes an API, and we have been building system integrations since 2012, among others with our own Maconnector. We have connected Magento, Akeneo, Pimcore, Odoo, warehouse systems and courier platforms this way.

Do the code and the data stay ours?

Yes. The MIT licence and the option to host the system yourself mean no vendor lock-in: you can change implementation partner without losing the system. It is the same reason we recommend open source in ERP.

Let’s talk about an Open Mercato implementation

Tell us which process the system has to handle and what you run today. We will get back to you within one business day.