Dragon Guard Handheld WMS is a .NET MAUI application built for rugged Android handhelds, connecting warehouse operators to the Dragon Guard backend for real-time receiving, shipping, item lookup, and inventory movement workflows. Authentication is JWT-based with device-level authorization, and every request carries both a bearer token and a company context header.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_APK/llms.txt
Use this file to discover all available pages before exploring further.
Introduction
Learn what Dragon Guard Handheld WMS does and how it fits into your warehouse operation.
Quickstart
Build and deploy the APK, register your device, and run your first operational flow.
Architecture
Understand the MVVM structure, DI wiring, HTTP client strategy, and startup flow.
API Reference
Full reference for all backend endpoints consumed by the handheld client.
Core Modules
The handheld home exposes four operational modules. Each module connects to a dedicated backend service and follows the same pattern: load a header list, drill into detail, update quantities, and post.Receipts
Receive purchase orders line-by-line with bin assignment and quantity tracking.
Shipments
Process outbound shipments, confirm shipped quantities, and post documents.
Item Inquiry
Look up items by barcode, RFID scan, or manual search with full stock context.
Inventory Movements
Browse movement history and product journal entries for audit and reconciliation.
Authentication & Device Authorization
Register the device
A Supreme Admin registers the device’s MAC address (or
ANDROID_ID on Android 10+) in the tenant’s allow-list before first login.Log in with credentials
The app sends
username, password, deviceId, and deviceName to POST api/auth/grupomas-handheld-login. A Dragon Guard JWT is returned on success.Session is validated
The app enforces exactly one company per session. Zero or multiple companies block login — no silent selection is ever made.
Official release builds ignore any locally saved URL override and always connect to the compiled server address. Debug builds may override the base URL from the Settings screen for local testing.