Open Mercato. What it does. How to implement it.
Open Mercato is a TypeScript framework for business applications. Start with CRM, sales and product catalog modules, then adapt the application to your workflows.
Choose Look inside the market to explore the illustration. Move your pointer or tap to reveal modules. Arrow keys move the reveal, Enter reveals all, and Escape returns to the introduction. Module names and excerpts come from Open Mercato; the market and moving signals are illustrative.
What can you build with Open Mercato?
Customer management
Contacts, companies, deals and activity history. Explore the records available and how they could support the way your sales team works.
Explore CRM capabilitiesQuotes and orders
Connect customer and product data with quotes and orders. Your implementation defines pricing rules and the steps needed to fulfil each order.
See how sales worksProduct catalog
Products, variants and prices in a shared data model. See what it takes to prepare a catalog for use in your sales process.
Explore the product catalogWhat does implementation involve?
The modules give you a starting point. The project defines your workflows, adapts the application and connects it to the systems you already use.
Read the implementation guideChoose the first workflow
Decide what should improve for the team and how users will check that the application works correctly.
Configure and connect
Configure modules, build the missing features, and prepare your data and integrations.
Launch and maintain
Test with users. Agree who will handle hosting, backups, support and updates.
Useful reading before you start
Understand implementation costs
Scope, integrations, migration and the ongoing work of maintaining the application.
Explore the architecture
How modules and data fit together, and where your team can add its own features.
Start working with the code
Installation sources, version requirements and guides to writing your own modules.
Questions before implementation
Is Open Mercato free?
Open Mercato Core uses the MIT license, with no license fee for that code. Budget for adapting the application, hosting and maintaining it. Enterprise features and external services have their own terms. The cost guide explains which parts of a project need an estimate. Read about costs →
Can it connect to our existing systems?
An integration depends on the systems, their interfaces and the data you need to exchange. Check whether a suitable connector exists for your version. When custom work is needed, plan the mapping, update rules and recovery after a failed transfer before committing to the scope. Plan an integration →
Do we need an in-house IT team?
An external team can build and maintain the application, or share the work with your developers. Your business still needs someone who knows the process, chooses priorities and tests the result with users. Agree access to code, support and handover arrangements before work begins. Choose a delivery team →
Where can we host the application?
The application can run on infrastructure your team manages or with a hosting provider. Choose the environment after checking the requirements of your version and modules. Plan for the database, files, backups and monitoring as well as the application itself. Someone must handle updates and recovery. Plan operation and maintenance →
Need help with implementation?
We offer Open Mercato implementation services. Tell us what you want to improve and which systems you use. You can get in touch while you are still exploring the options.