AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsoms-erp
oms-erp is a Java-based open-source order management and ERP system designed for omni-channel retail. It integrates order, inventory, and financial management through a microservice architecture (Spring Cloud, Istio, Kubernetes) to support rapid deployment and enterprise digital transformation.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | FJ-OMS/oms-erp |
| Owner | FJ-OMS |
| Primary language | Java |
| License | Apache-2.0 — OSI-approved |
| Stars | 1.9k |
| Forks | 354 |
| Open issues | 1 |
| Latest release | PRE (2022-08-25) |
| Last updated | 2025-12-24 |
| Source | https://github.com/FJ-OMS/oms-erp |
What oms-erp is
Built on Spring Cloud microservices with support for multi-tenancy, distributed workflows (Zeebe, Activiti), Redis caching, MyBatis ORM, distributed transactions (Saga), and Kubernetes/Serverless orchestration. Includes GitLab integration, CI/CD pipelines, API testing, and performance monitoring capabilities.
Get the oms-erp source
Clone the repository and explore it locally.
git clone https://github.com/FJ-OMS/oms-erp.gitcd oms-erp# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires MySQL, Redis, and Spring Boot expertise; full stack deployment on Kubernetes/Istio demands DevOps capability or managed container service.
- SQL schema import mandatory (skyer-order, skyer-tags, skyer-channel modules); data model coupling may complicate future customization.
- Multi-tenancy support is built-in but operational separation, network policies, and RBAC rules require careful design review.
- Workflow engines (Zeebe/Activiti) introduce orchestration complexity; process definitions and state management must align with business requirements upfront.
- Distributed transaction handling (Saga pattern) adds latency and eventual-consistency semantics; unsuitable for strongly-consistent financial ledger operations without additional safeguards.
When to avoid it — and what to weigh
- Minimal Documentation & Stale Release Cycle — Latest release is marked 'PRE' (August 2022); setup instructions are incomplete ('暂无' / 'not available'). Requires significant reverse-engineering or vendor support engagement.
- Non-English-First Codebase — README, UI labels, and configuration are predominantly Chinese. Teams without Chinese-language proficiency or access to vendor support will face high onboarding friction.
- Unvalidated Performance & Scaling Claims — Claims of 50% capital turnover improvement, cost reduction to 'millions of RMB', and 2–10% internal loss reduction are unsubstantiated by public benchmarks or case studies.
- Limited Active Community & Vendor Lock-in Risk — Only 1 open issue and 354 forks suggest low community engagement. Maintenance depends heavily on vendor relationship; no independent SLA or commercial support documented.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license allowing commercial use, modification, and redistribution with attribution and liability disclaimer.
Apache-2.0 permits commercial use and derivative works. However, no formal commercial support SLA, warranty, or indemnity is documented. Vendor engagement (contact: WeChat 'blowbing') is recommended before production deployment. Redistribution must retain the Apache license; any bundled third-party dependencies must be audited for license compliance.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Moderate |
| Documentation | Limited |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | Medium |
No public security audit, penetration test results, or vulnerability disclosure policy provided. Multi-tenancy implementation requires verification of data isolation, RBAC enforcement, and cross-tenant query filtering. Distributed transaction (Saga) orchestration and eventual consistency semantics may introduce race conditions in financial data; cryptographic signing and audit logging should be reviewed. Redis caching and inter-service communication require encryption and authentication configuration review.
Alternatives to consider
Odoo (ERP/OMS module suite)
Mature, English-first, extensive third-party marketplace, strong community, formal SLA/support. Steeper learning curve; less cloud-native than oms-erp out-of-box.
SAP S/4HANA Cloud (with order management add-on)
Enterprise-grade, omni-channel order orchestration, financial integration baked-in, 24/7 support. Significantly higher cost; vendor lock-in; less suitable for startups or cost-constrained orgs.
Shopware OrderManagement (open-source e-commerce platform)
Open-source, cloud-native Kubernetes-ready, active community, inventory sync and financial reporting. Lighter-weight than oms-erp; may require custom SAP connectors for complex enterprise financials.
Build on oms-erp with DEV.co software developers
Contact the vendor (WeChat: blowbing) for a live demo, technical architecture review, and TCO assessment before committing resources. Devco can assist with integration planning, Kubernetes deployment, and custom connector development.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
oms-erp FAQ
Is oms-erp production-ready out-of-the-box?
Can we run oms-erp in our private cloud without external vendor lock-in?
What is the total cost of ownership (TCO) for a mid-market e-commerce business?
Does oms-erp support real-time financial consolidation with SAP?
From evaluation to production software
Bringing oms-erp into production usually means new services, new interfaces, and new failure modes. DEV.co is a software development agency that builds all three and stays on for the open-source crm maintenance.
Ready to Evaluate oms-erp?
Contact the vendor (WeChat: blowbing) for a live demo, technical architecture review, and TCO assessment before committing resources. Devco can assist with integration planning, Kubernetes deployment, and custom connector development.