myWMS vs Sentry WMS

myWMS is an open-source framework for developing warehouse management systems. It supplies a data model and basic inventory-management services for WMS suppliers building systems for specific needs. Its communication interfaces connect to external systems, while internal interfaces allow plug-in modules to be exchanged. The maker describes the framework as independent of hardware and operating systems, and compatible with third-party products and modules. It is written in Java, and its source has been available under the GNU General Public License since March 2009. The maker offers myWMS LOS as a free download, including a demo for decision-makers. That demo uses a database the maker says should be replaced with a high-performance database for production use. Listed downloads include a Windows installer, an EAR package for JBoss, and source code. Documentation includes a user manual and a process description with an end-to-end example. The project started in 2001 as a research project initiated by Fraunhofer IML and funded by North Rhine-Westphalia. Platforms listed are Linux, Windows, web, and self-hosted; mobile app and barcode scanning are also listed. The demo plan costs nothing.

Sentry WMS is a free, open-source warehouse management system for e-commerce fulfillment. It covers receiving, storage, picking, packing, shipping, and counting, while relying on an existing database or ERP to manage orders, products, or customers. Pick Walk supports batch picking across multiple orders with serpentine walk path optimization. Inventory functions include bin-level cycle counts with variance detection and an administrator approval workflow, along with transfers and adjustments tracked by reason. The connector framework provides a starting structure for ERP, commerce, and other HTTP API connections, but the project does not ship first-party connectors for named systems such as NetSuite, QuickBooks, Shopify, or BigCommerce. The documented stack includes a React web admin panel, a React Native mobile app, a Flask API, and Docker Compose deployment. Android setup uses a sideloaded APK connected to the operator's API server. Production deployment requires configured secrets; HTTPS requires a reverse proxy in front of the HTTP-only API. CSV or JSON bulk imports are limited to 5,000 records per import. Version 1.7.0 and later are Apache License 2.0; earlier tagged releases remain MIT-licensed.