Device Registry

Where Device Registry belongs

Device Registry sits in the Repair layer of LuperIQ and focuses on Individual device tracking with IMEI, serial, condition, and lock status. For a site owner, the practical value is not the module name by itself; it is whether Individual device asset tracking, IMEI and serial number recording, and Customer-owned vs business-owned classification becomes easier to manage in the real customer or admin path.

For pricing and setup, the useful context is Free and Pro and the place the owner will likely manage it is Repair OS. Those details help the reader understand the module without turning the page into a technical inventory.

Setup checks for Device Registry

• Verify that "Individual device asset tracking" is represented in the live setup before treating Device Registry as ready for customers or staff.
• Verify that "IMEI and serial number recording" is represented in the live setup before treating Device Registry as ready for customers or staff.
• Verify that "Customer-owned vs business-owned classification" is represented in the live setup before treating Device Registry as ready for customers or staff.
• Verify that "Condition grading on intake" is represented in the live setup before treating Device Registry as ready for customers or staff.
• Verify that "Activation/iCloud/FRP lock status monitoring" is represented in the live setup before treating Device Registry as ready for customers or staff.
• Open the Repair OS admin section during setup so the owner knows exactly where this module is managed after launch.

Dependencies and AI connections

Device Registry works best when Device Catalog are already understood, because those surrounding tools shape where the data, settings, or customer actions will land.

Device Registry is documented as a practical module first. If the owner is evaluating AI help around the same area, the safer next step is to start in the Repair OS admin area and only add AI when there is a real task to run.