Browser application
Core Store, Active, Collect and History workflows are implemented in the controlled development environment.
Lugexa is being developed as a cloud-backed web service first. Native apps, QR enhancements and Wallet are complementary future experiences.
These areas have active implementation work, but are not a promise of public availability.
Core Store, Active, Collect and History workflows are implemented in the controlled development environment.
One property, one active identity, multiple device sessions and 24-hour photo retention are implemented development rules.
Property access, named roles, team controls, audit and photo infrastructure are under development and verification.
Mobile layouts and a limited service-worker foundation exist. Add-to-home-screen behaviour still needs device verification.
Planned as enhanced options for camera, QR, device integration and future offline capability, not as the core launch dependency.
Compatible reusable tags can retain their issuing property and visible tag number. Cross-browser camera support still needs verification.
wallet.lugexa.app is the canonical QR and Wallet host. Infrastructure and placeholder behaviour exist, but guest Wallet functionality is not active.
A physical hotel tag intended for staff Store and Collect workflows.
A separate temporary guest-facing collection experience that may be introduced later.
Scanning a tag identifies tag information. It does not prove that a guest owns the luggage.
No Apple Wallet pass, Google Wallet pass, guest authentication, collection validation or revocation is live.
Multi-property administration, larger teams, SSO, custom retention and governance remain unpriced plans.
PMS and other integrations are future possibilities. No specific vendor integration is claimed.
Lost Property and package or parcel tracking remain roadmap concepts outside the current luggage product.
No roadmap item has a published release date. Scope may change before launch.