What it is

GreaterWMS is an open-source inventory and warehouse management system written in Python and built around Django, Django REST Framework, and a Quasar Vue.js frontend. The project is presented as a warehouse management system for supply chain operations, with topics covering inventory, warehouse management, and SCM. Its origin is described as a system derived from a Ford Asia Pacific after-sales logistics warehousing supply chain process, and it is positioned for organizations that need a customizable base platform rather than a fixed commercial package.

The concrete problem it addresses is the difficulty of adapting closed commercial WMS software after implementation. The README says businesses can become locked to a vendor when they need secondary development, with high cost and long cycles. GreaterWMS is designed to be modified by the operating company, supporting inventory, warehouse, ERP, IoT, and distribution integrations as an extensible foundation.

Key capabilities

• Manages inbound receipt, outbound shipment, inventory, and storage locations through modular business components.
• Uses a separated Django REST Framework API and Quasar Vue.js client, allowing front-end and back-end changes to proceed independently.
• Supports PDA, mobile, desktop, web, and WeChat mini programs from one backend through the OneAPP idea.
• Handles customization cases described in the README, including multi-warehouse control, cold-chain IoT temperature control, batch and expiry management, and multi-owner tenant isolation.
• Provides batch management, FIFO control, and traceability for manufacturing and pharmaceutical scenarios, including integration with IoT devices and MES systems.

Who uses it and how

• Third-party logistics and cloud warehouse operators use it as a base for multi-warehouse control, cold-chain temperature monitoring, batch expiry control, and tenant isolation for multiple cargo owners.
• Pharmaceutical distribution companies use customized batch modules for expiry warnings, IoT temperature and humidity monitoring, and GSP compliance workflows.
• Manufacturing teams use batch management and FIFO controls for parts traceability and connect the system to MES workflows for material pull processes.

Getting started

Typical setup begins by cloning the GitHub repository, installing Python dependencies with pip, and starting the backend with Daphne. The frontend is installed with npm and run with Quasar, while request addresses are configured in templates/public/statics/baseurl.txt.

When to use it — and when not to

GreaterWMS is useful when a business needs an Apache-2.0 licensed WMS foundation that can be modified for inventory, warehouse, ERP, IoT, or distribution integrations instead of buying a closed commercial system. Self-hosters must operate the Python/Django backend, choose and maintain SQLite, MySQL, or PostgreSQL, and manage the Quasar frontend build and API configuration. The README does not describe a hosted service or Docker deployment path, and the 3.0 work is still being refactored on the Bomiot framework, so teams needing a turnkey managed product or a fully stable 3.0 release may need to evaluate the current source carefully.

git clone https://github.com/GreaterWMS/GreaterWMS.git
cd GreaterWMS

pip install -r requirements.txt
daphne -b 0.0.0.0 -p 8008 greaterwms.asgi:application

cd templates
npm install
quasar dev