🚀 Power Your SMB with ERPNext: The Open-Source ERP Revolution

Serhii Shypylov

• 4 min read

Small and medium businesses (SMBs) need agile, cost-effective tools to thrive in 2025’s competitive landscape. ERPNext, a free open-source ERP, delivers unmatched flexibility to streamline operations, cut costs, and boost productivity without pricey licenses. Ready to transform how your business manages resources? Let’s explore why ERPNext, paired with the Prompt Theme, is the ultimate solution for SMBs!

🌟 Why Choose ERPNext for Your Business

Proprietary ERPs often burden SMBs with high fees and rigid setups. ERPNext offers a customizable, open-source alternative that eliminates vendor lock-in and hidden costs. Integrated with the Prompt Theme, it automates repetitive tasks and scales effortlessly, making it a top IT tool for efficiency. Say hello to streamlined workflows and goodbye to budget-breaking systems!

🔧 Must-Have Features for SMBs

ERPNext provides a comprehensive toolkit to manage your business seamlessly:

  • Financial precision: Handle multi-currency accounting and generate real-time reports.
  • Operational excellence: Manage inventory, sales, procurement, and HR in one platform.
  • No-code simplicity: Customize workflows without technical expertise.
  • Seamless connectivity: Integrate with third-party apps via APIs and access on mobile.

These features empower SMBs to enhance customer service and make smarter decisions.

🌍 Global Scalability, Easy Deployment

ERPNext supports international operations with multi-currency and tax compliance features. Its scalable architecture grows with your business, from startups to global enterprises. Deploy it on Frappe Cloud or use the Prompt Theme’s Docker Compose setup for secure, lightweight hosting. This ensures reliable performance without per-user costs or dedicated servers.

💼 Benefits That Drive Growth

ERPNext, combined with the Prompt Theme, delivers:

  • Time savings: Automate reports, emails, and client communications.
  • Better service: Centralize data for faster, personalized customer responses.
  • Data-driven insights: Analyze market and customer trends for strategic decisions.
  • Cost efficiency: Run on containers for resource-efficient scalability.

📢 Start Your ERPNext Journey Now!

Don’t let costly, inflexible systems slow your SMB down. ERPNext offers a powerful, free ERP solution to fuel growth and innovation. Visit blog.1it.pro for more tech insights or explore 1it.pro for expert solutions. Contact admin@1it.pro today to supercharge your operations!

📌 Guide: Deploy ERPNext with Docker Compose

1. Project Structure

Organize your project for efficient ERPNext deployment.

project/
│
├─ docker-compose.yml
├─ .env
└─ app/
    └─ Dockerfile

2. Configure .env File

Securely store sensitive configurations.

APP_NAME=erpnext
APP_VERSION=v15
APP_HTTP_PORT=8080
DB_MARIA_PORT=3306
DB_MARIA_PASSWORD=secret
APP_PASSWORD=admin123
APP_DB_PARAM=mariadb
APP_NETWORK=erpnext_network

3. Set Up docker-compose.yml

Define services for ERPNext, MariaDB, Redis, and more.

version: "3.8"

services:
  backend:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}
    deploy:
      restart_policy:
        condition: on-failure
    volumes:
      - sites:/home/frappe/frappe-bench/sites
      - assets:/home/frappe/frappe-bench/sites/assets
    networks:
      - default

  configurator:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-configurator
    command:
      - configure.py
    environment:
      DB_HOST: db
      DB_PORT: "3306"
      REDIS_CACHE: redis:6379/0
      REDIS_QUEUE: redis:6379/1
      REDIS_SOCKETIO: redis:6379/2
      SOCKETIO_PORT: "9000"
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

  create-site:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-create-site
    deploy:
      restart_policy:
        condition: on-failure
    volumes:
      - sites:/home/frappe/frappe-bench/sites
      - assets:/home/frappe/frappe-bench/sites/assets
    entrypoint:
      - bash
      - -c
    command:
      - >
        wait-for-it -t 20 db:3306;
        wait-for-it -t 20 redis:6379;
        export start=`date +%s`;
        until [[ -n `grep -hs ^ common_site_config.json | jq -r ".db_host // empty"` ]] && \
          [[ -n `grep -hs ^ common_site_config.json | jq -r ".redis_cache // empty"` ]] && \
          [[ -n `grep -hs ^ common_site_config.json | jq -r ".redis_queue // empty"` ]];
        do
          echo "Waiting for common_site_config.json to be created";
          sleep 5;
          if (( `date +%s`-start > 20 )); then
            echo "could not find common_site_config.json with required keys";
            exit 1
          fi
        done;
        echo "common_site_config.json found";
        bench new-site frontend --admin-password=${APP_PASSWORD} --${APP_DB_PARAM}-root-password=${DB_MARIA_PASSWORD} --install-app erpnext;
    networks:
      - default

  db:
    image: mariadb:10.6
    container_name: ${APP_NAME}-db
    healthcheck:
      test: mysqladmin ping -h localhost --password=${DB_MARIA_PASSWORD}
      interval: 1s
      retries: 15
    deploy:
      restart_policy:
        condition: on-failure
    command:
      - --character-set-server=utf8mb4
      - --collation-server=utf8mb4_unicode_ci
      - --skip-character-set-client-handshake
      - --skip-innodb-read-only-compressed
    environment:
      MYSQL_ROOT_PASSWORD: ${DB_MARIA_PASSWORD}
    volumes:
      - db-data:/var/lib/mysql
    ports:
      - "${DB_MARIA_PORT}:3306"
    networks:
      - default

  frontend:
    image: frappe/erpnext-nginx:${APP_VERSION}
    container_name: ${APP_NAME}-frontend
    deploy:
      restart_policy:
        condition: on-failure
    environment:
      BACKEND: backend:8000
      FRAPPE_SITE_NAME_HEADER: frontend
      SOCKETIO: websocket:9000
      UPSTREAM_REAL_IP_ADDRESS: 127.0.0.1
      UPSTREAM_REAL_IP_HEADER: X-Forwarded-For
      UPSTREAM_REAL_IP_RECURSIVE: "off"
    volumes:
      - sites:/usr/share/nginx/html/sites
      - assets:/usr/share/nginx/html/assets
    ports:
      - "${APP_HTTP_PORT}:8080"
    networks:
      - default

  queue-default:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-queue-default
    deploy:
      restart_policy:
        condition: on-failure
    command:
      - bench
      - worker
      - --queue
      - default
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

  queue-long:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-queue-long
    deploy:
      restart_policy:
        condition: on-failure
    command:
      - bench
      - worker
      - --queue
      - long
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

  queue-short:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-queue-short
    deploy:
      restart_policy:
        condition: on-failure
    command:
      - bench
      - worker
      - --queue
      - short
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

  redis:
    image: redis:6.2-alpine
    container_name: ${APP_NAME}-redis
    deploy:
      restart_policy:
        condition: on-failure
    volumes:
      - redis-data:/data
    networks:
      - default

  scheduler:
    image: frappe/erpnext-worker:${APP_VERSION}
    container_name: ${APP_NAME}-scheduler
    deploy:
      restart_policy:
        condition: on-failure
    command:
      - bench
      - schedule
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

  websocket:
    image: frappe/frappe-socketio:${APP_VERSION}
    container_name: ${APP_NAME}-websocket
    deploy:
      restart_policy:
        condition: on-failure
    volumes:
      - sites:/home/frappe/frappe-bench/sites
    networks:
      - default

volumes:
  assets:
  db-data:
  redis-data:
  sites:

networks:
  default:
    name: ${APP_NETWORK}
    external: true

4. Create Dockerfile for ERPNext

Use the official ERPNext image for simplicity.

FROM frappe/erpnext-worker:${APP_VERSION}
WORKDIR /home/frappe/frappe-bench
COPY . .
CMD ["bench", "start"]

5. Best Practices

  • 🔑 Secure sensitive data in .env files.
  • 🌐 Isolate services with a dedicated network.
  • 💾 Use volumes for persistent data storage.
  • 🔄 Set restart: on-failure for reliability.
  • 🐳 Leverage lightweight images for efficiency.

6. Verification

  • Run docker-compose up -d to start services.
  • Access ERPNext at http://localhost:8080.
  • Log in with the admin password and verify modules (accounting, inventory, etc.).

🚀 Optimize with Prompt Theme

Deploy ERPNext with the Prompt Theme for automated, scalable management. Visit blog.1it.pro 1it.pro for more setup guides!

UA EN RU

Зв'язатися з нами

Telegram Email