LUCENEX / Documentation
Start here
What the product is, who it fits and what this documentation covers.
Reviewed 9 November 2026 · WMS 8020cd0A self-hosted warehouse system
LuceneX Warehouse Operations is a LuceneX-maintained fork of the open-source ModernWMS project. It combines a Vue web interface, an ASP.NET Core API and a relational data model for warehouse work.
Customers are primarily expected to run the application on their own infrastructure. This public site is a separate documentation and product-introduction project; it does not run the WMS or store warehouse records.
Who it is suitable for
- Small and medium-sized warehouses, distributors and retail stock operations.
- Teams needing receiving, location-based inventory and dispatch in one web interface.
- Organizations with an IT owner or partner able to maintain Docker, databases, backups and updates.
How to read implementation status
“Recorded local QA” means the repository acceptance record describes a fixture-backed test, mainly on 6 November 2026. It does not mean that the workflow has just been re-tested on a production deployment. “Scoped verification” means only the listed actions were exercised. “Known boundary” identifies unfinished or unavailable behavior.
Start here
What the product is, who it fits and what this documentation covers.
02 / GUIDEFeature catalogue
Implemented modules, their actions and the scope of verification.
03 / GUIDEReceiving & putaway
The inbound workflow from an arrival notice to available stock.
04 / GUIDEInventory & warehouse work
Locations, movements, stock locks, adjustments, counting and processing.
05 / GUIDEDispatch & shipping
From shipment creation through picking, packing and receipt confirmation.
06 / GUIDEMaster data & configuration
The records that connect products, partners and physical warehouse space.
07 / GUIDEAccess, roles & approvals
Authentication, action permissions and the limits of approval configuration.
08 / GUIDEReports, exports & printing
Available analysis screens, spreadsheet downloads and label capabilities.
09 / GUIDESelf-hosting & installation
Docker services, persistent SQLite, first startup and deployment acceptance.
10 / GUIDEArchitecture & data
Frontend, API, database providers and the current Cloudflare boundary.
11 / GUIDEAPI & integration reference
Route inventory, authentication and integration contracts to validate.
12 / GUIDELanguages & accessibility
English and Latvian coverage, embedded content and practical limitations.
13 / GUIDEImplementation & verification
What is recorded as tested, what remains open and why the demo is paused.
14 / GUIDESource, licensing & contact
Project provenance, license boundaries and how to discuss implementation.