Domain-modular marketplace core
Domains (catalog, orders, payments, settlement, admin ops) are separated to keep the core stable and evolvable; business specifics are injected via extension points to avoid tight coupling.
Open Mercato packages the common skeleton of a marketplace into reusable modules: clear domain boundaries for catalog, orders, payments, and admin operations, with extension points for business-specific logic. It is designed as an engineering foundation you can iterate on for years—start with a minimal listing-to-checkout flow, then layer settlement, permissions, ops tooling, and integrations without rewriting the core. For teams that need data ownership, auditability, and deep customization, it turns a marketplace into a maintainable product system rather than a one-off build.
| ✕Traditional Pain Points | ✓Innovative Solutions |
|---|---|
| Hosted platforms like Shopify can bottleneck marketplace-specific needs such as multi-party settlement, permissions, and ops workflows. | Open Mercato treats a marketplace as an evolvable product system: a stable core with workflows and extension points for differentiation. |
| Retrofitting a generic commerce backend like Medusa into a marketplace often misaligns domain boundaries, making extensions brittle. | Admin ops and governance are first-class: listing review, settlement, and dispute handling become orchestrated and auditable instead of hidden scripts. |
1git clone https://github.com/open-mercato/open-mercato.git && cd open-mercato1cp .env.example .env1docker compose up -d1# Either: npm install && npm run dev; or pnpm install && pnpm dev1# Example: npm run migrate && npm run seed| Core Scene | Target Audience | Solution | Outcome |
|---|---|---|---|
| Launch a vertical marketplace faster | startups and product teams | ship listing→checkout→payment→fulfillment using modular domains | spend time on differentiation, not rebuilding the core |
| Internal vendor/service marketplace for enterprises | procurement and business units | orchestrate onboarding, review, settlement, and permissions with auditable workflows | better compliance and traceability |
| Multi-tenant platform operations | teams building a platform product | support tenant isolation and customization via extension points | fewer forks and lower long-term maintenance |
