---
title: "Inshop CRM"
pageType: "tool-profile"
schemaVersion: "1.0"
snapshotId: "tv-20261027-b36ae5d5f795"
generatedAt: "2026-10-27T07:03:11.000Z"
canonicalUrl: "https://toolvitals.com/tools/inshop-crm/"
jsonUrl: "https://toolvitals.com/api/agent/tools/inshop-crm"
indexable: true
---

# Inshop CRM

Inshop CRM / ERP API. It's powerful framework allows to build systems for business with different workflows. It has on board multi language support, clients management, projects & tasks, documents, simple accounting, inventory management, orders & invoice management, possibilities to integrate with third party software, REST API, and many other features.

## Decision context

- Status: zombie
- ToolVitals score: 1/100
- Health score: 2/100
- Shipping score: 0/100
- Score mode: verdict
- Data confidence: 90/100
- Source coverage: 75/100
- Last evidence check: 2026-10-27

## Classification

- Use case: CRM & Sales (crm-sales)
- Category: CRM & Sales (crm)
- Tool mode: Source-visible project
- Openness: OSI-approved OSS
- License: MIT
- Tags: open-source, api-platform, crm, elasticsearch, erp, php, postgresql, symfony, api-first, clients-management, business-workflows, orders, invoicing, accounting, inventory-management, projects-and-tasks

## Public repository signals

- Repository: [inshop/inshop-crm-api](https://github.com/inshop/inshop-crm-api)
- Stars: 261 (adoption context only)
- Forks: 82
- Open issues: 1
- Last commit date: 2025-11-03
- Releases in 90 days: 0

## Source receipts

- [Official website](https://inshopcrm.com/) — checked 2026-10-27
- [Source repository](https://github.com/inshop/inshop-crm-api) — checked 2026-10-27

## Discovery status

- Search indexable: yes
- Reason: sufficient tool evidence

## Interpretation limits

- ToolVitals scores summarize bounded public maintenance, shipping, openness, and evidence signals. They are not user-review ratings.
- GitHub stars and related popularity metrics are adoption context, not quality evidence.
- Missing values mean not collected or not confidently established; they do not mean zero.
- Public signals do not prove security, uptime, support quality, customer satisfaction, or production suitability.
- Verify material decisions against the linked first-party sources and your own requirements.