Open-source Order Management System for e-commerce.

OpenOMS is a self-hostable, multi-tenant OMS with 463 API endpoints, 141 dashboard pages, and integrations with 8 marketplaces and 8 carriers. Built with Go and Next.js, designed for teams that need full control over their order operations.

Status: Active Development — Looking for beta testers! Join our Discord

• Custom order statuses, custom fields, and tags
• Order merge and split
• Kanban board view
• Barcode scanning (packing station)
• Automation rules engine (trigger, conditions, actions)
• Print templates (orders, invoices, shipping labels)
• CSV import/export
• Action delays (scheduled automation)

• Product variants and bundles
• B2B pricing tiers
• Multi-warehouse stock management
• Warehouse documents (PZ/WZ/MM)
• Stocktaking (inventory counts)
• Product CSV import with preview
• Product categories with color badges

Carrier rate shopping across all providers.

• Multi-tenant SaaS with PostgreSQL Row-Level Security
• 463 REST API endpoints with OpenAPI 3.1 spec (Swagger UI)
• 141 dashboard pages with dark mode, PWA support, keyboard shortcuts
• Guided onboarding wizard for new tenants (company setup, warehouse, integration, team)
• Registration with invite tokens, license tokens, or payment checkout
• Background workers (21 registered: order pollers, stock sync, tracking, automation)
• RBAC with custom roles
• 2FA / TOTP authentication
• WebSocket real-time updates
• Outgoing webhooks (HMAC-SHA256 signed)
• Audit log
• Self-service returns portal
• Multi-currency with NBP exchange rates
• Customer management (CRM)
• Prometheus metrics (Bearer token auth)
• Security headers (CSP, X-Frame-Options, HSTS, Referrer-Policy)
• Kubernetes secrets encryption at rest, audit logging

Prerequisites: Go 1.25+, Node.js 22+, Docker with Docker Compose, Task, golang-migrate

# 1. Clone
git clone https://github.com/openoms-org/openoms.git
cd openoms

# 2. Configure environment
cp .env.example .env

# 3. Install dashboard dependencies, start infrastructure, run migrations, seed data
task setup

# 4. Start the API server and dashboard
task dev

Verify the API and dashboard are running:

curl http://localhost:8080/health
# Open http://localhost:3000/login

Seed login for local development:

This account is created only by task setup or task seed. Production and other self-hosted deployments should create their own administrator account or use the configured registration/invite flow; no default production password is provided.

task setup       # Full setup: dashboard deps + containers + migrations + seed
task up          # Start PostgreSQL + Redis containers
task down        # Stop containers
task run         # Start API server (port 8080)
task dashboard   # Start dashboard dev server (port 3000)
task dev         # Start API server + dashboard in parallel
task dashboard:install  # Install dashboard dependencies
task migrate     # Run database migrations
task seed        # Load test data
task test        # Run all tests (race detection + coverage)
task lint        # Run golangci-lint on all modules
task fmt         # Format all Go source files
task clean       # Stop containers and remove volumes

openoms/
├── apps/
│   ├── api-server/              # Go backend (ELv2)
│   │   ├── cmd/server/          # Entrypoint
│   │   ├── internal/            # Handlers, services, repositories, workers
│   │   └── migrations/          # 28 migrations (56 SQL files)
│   └── dashboard/               # Next.js frontend (ELv2)
│       └── src/
├── packages/                    # 27 standalone SDK libraries (MIT)
├── deploy/
│   └── helm/openoms/          # Helm chart for k3s/k8s
├── docs/
│   └── system-documentation.md
├── docker-compose.dev.yml
├── docker-compose.prod.yml
├── Taskfile.yml
├── .github/workflows/
│   ├── ci.yml                 # Lint, test, security scan, format checks
│   └── release.yml            # CI/CD workflow that builds Docker images
└── .env.example

All packages are independently usable Go libraries, licensed under MIT.

Full system documentation is available at docs/system-documentation.md.

The API server exposes an interactive OpenAPI 3.1 specification via Swagger UI at /swagger/ when running.

cp .env.example .env
# Edit .env with production values (strong secrets, real credentials)

docker-compose -f docker-compose.prod.yml up -d --build

The production compose file includes PostgreSQL, Redis, automatic database migrations, the API server, and the Next.js dashboard. All services include health checks and restart policies.

A Helm chart is provided for k3s/k8s deployments:

helm upgrade --install openoms deploy/helm/openoms \
  -n openoms \
  --set apiServer.image.tag=latest \
  --set dashboard.image.tag=latest \
  --set migration.image.tag=latest

The CI/CD pipeline (.github/workflows/release.yml) builds Docker images, scans them with Trivy, and deploys to k3s via Helm on push to main. A release fallback workflow also checks merged PRs that touch release-relevant paths and dispatches release.yml only if GitHub does not create a release run for the merge commit.

• PostgreSQL 16+
• Redis 7+ (required outside development unless ALLOW_IN_MEMORY_STATE=true is explicitly set for a single-node self-hosted deployment)
• Reverse proxy (nginx / Caddy / Traefik / ingress-nginx) for TLS termination

The Docker images are stateless and can be deployed behind a load balancer or on single-node setups like k3s.

• Allegro integration (OAuth2, offers, orders, "Wysylam z Allegro" shipments)
• InPost integration (Paczkomaty, courier, label generation, tracking, webhooks)
• Dashboard with Kanban board, dark mode, and PWA support
• Order, product, and customer management
• Automation rules engine (triggers, conditions, actions, delays)
• Packing station with barcode scanner
• Reports and CSV export
• 2FA/TOTP, RBAC with custom roles
• Carrier rate shopping across all providers
• Product CSV import with preview
• SMS notifications (SMSAPI)
• Marketing automation (Mailchimp)
• Print templates (orders, invoices, shipping labels)
• Onboarding wizard (4-step guided setup for new tenants)
• DHL, DPD, GLS carrier SDK audit and verification
• Erli marketplace SDK rebuild and verification
• Supplier portal (public, token-based)
• Supplier product enrichment and category mapping

• 7 additional carriers (DHL, DPD, GLS, UPS, Poczta Polska, Orlen Paczka, FedEx)
• 10 marketplaces (Amazon, eBay, WooCommerce, Kaufland, OLX, Empik, Erli, Shoper, PrestaShop, Shopify)
• Repricing engine (4 pricing strategies)
• Multi-warehouse with PZ/WZ/MM documents
• Invoicing (Fakturownia, inFakt, wFirma) + KSeF e-invoicing
• Product variants and bundles
• Multi-currency (NBP exchange rates)

• Public SaaS (hosted version)
• Mobile application
• Plugin/extension marketplace
• Customer self-service portal
• BaseLinker data import

• Discord: discord.gg/3Z5hzeH5 — ask questions, report bugs, suggest features
• Issues: GitHub Issues
• Website: openoms.org

We're looking for beta testers — Polish e-commerce sellers who want to try OpenOMS on real orders. Join Discord for details.

Contributions are welcome. See CONTRIBUTING.md for full details.

1. Fork the repository
2. Create a feature branch (git checkout -b feature/your-feature)
3. Run tests (task test) and linting (task lint)
4. Open a pull request against main

Please open an issue first for large changes or new features.

This project uses a two-repository deployment model:

• Public repo (openoms-org/openoms): Builds Docker images on every push to main, pushes to GHCR, runs Trivy security scans, and has a post-merge fallback that dispatches the release workflow if the normal push trigger is missing
• Enterprise repo (private): Deploys to production via Helm with environment-specific values overlay

Docker images are public on GHCR:

• ghcr.io/openoms-org/openoms-api
• ghcr.io/openoms-org/openoms-dashboard
• ghcr.io/openoms-org/openoms-migrate

• Core applications (apps/): Elastic License 2.0
• SDK packages (packages/): MIT License

Built in Poland. Open by default.