> For the complete documentation index, see [llms.txt](https://codehas.gitbook.io/the-repairbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codehas.gitbook.io/the-repairbox/device-catalog.md).

# Device Catalog

The Device Catalog provides reusable reference data for standardized repair intake. It lets staff select known equipment rather than retyping the device description for every job. Catalog accuracy directly affects the quality of intake, service selection, reporting and historical repair descriptions.

## Catalog entities and relationships

The RepairBox product model separates these entities:

| Entity             | What it represents                | Examples                                                |
| ------------------ | --------------------------------- | ------------------------------------------------------- |
| **Device Type**    | Broad equipment category          | Mobile, Laptop, Tablet, Game Console, Smartwatch, Other |
| **Brand**          | Manufacturer or product brand     | Apple, Samsung, Lenovo                                  |
| **Device / Model** | A specific catalog device/model   | iPhone 16 Pro, MacBook Pro                              |
| **Service**        | Work the shop can provide         | Screen Replacement, Battery Replacement                 |
| **Defect**         | Reported/observed/diagnosed issue | Cracked Screen, Battery Draining, Not Charging          |

The primary selection flow for a standard repair is:

**Device Type → Brand → Device / Model → related Services and Defects**

Actual filtering is driven by the relationships configured in the catalog. Do not assume every service or defect is valid for every device.

## How catalog data is used during a repair

1. An agent creates/opens a Repair Order.
2. The agent adds a Repair Item and chooses standard/catalog-based entry.
3. The agent selects the appropriate device type, brand and model from the active data.
4. RepairBox presents or allows selection of relevant services/defects according to configured relationships.
5. The agent records customer-reported issues, condition/accessories and notes.
6. The saved Repair Item should preserve the selected/historical device details, even if the shared catalog is later updated.

The catalog is shared reference data; a Repair Item is an operational record. Editing the catalog should not rewrite the facts about a device already received for repair.

## Maintaining each catalog entity

### Device Types

Use categories broad enough to help intake staff navigate quickly. Avoid creating several near-identical category labels for the same equipment. Examples in the product model include Mobile, Laptop, Tablet, Game Console, Smartwatch and Other. Only use the exact values enabled in the installed catalog.

### Brands

Create a brand once and reuse it for the relevant devices. Search for spelling variations and aliases before adding a new record. Do not assume a brand is a device model.

### Devices / Models

A device record should represent a model or sufficiently precise device definition. Check the brand relationship and model naming before saving. Avoid ambiguous labels such as “iPhone” when the repair workflow requires a specific generation/model to pick a service or price correctly.

### Services

Services are operations the business offers or performs. Keep service names consistent and avoid using a fault symptom as the name of a repair action. See Services & Defects.

### Defects

Defects describe problems or faults. They can represent what a customer reports or what a technician observes/diagnoses, depending on the workflow. A customer-reported defect must not automatically be treated as a confirmed technical diagnosis.

## Supported standard repair versus custom repair

If the catalog accurately describes the device, use standard entry. If the device/model is missing or unclear, use custom entry to preserve the correct facts of this repair. A custom device description must not create a catalog record automatically. The business can later decide whether to create a reusable catalog entry through deliberate catalog maintenance.

## Catalog quality checklist

* Use consistent brand/model spelling and naming.
* Check for duplicates before inserting new entries.
* Maintain only services/defects that the business actually offers or tracks.
* Link services and defects to the appropriate devices where the UI supports those relationships.
* Review inactive or obsolete entries through the available management process rather than selecting a wrong model.
* Verify changes with a test intake record.
* Consider outlet differences before treating a price or service as universal.
* Do not modify historical repair data when updating shared catalog records.

## Troubleshooting

**A device/model is missing:** use custom entry for the current repair when appropriate, then ask an authorized catalog manager to review whether a reusable record should be added.

**Wrong services or defects appear:** verify the device relationship and whether the service/defect is active and intended for customer intake.

**Duplicate catalog entries appear:** compare brand/model naming and identifiers before adding more entries; consolidate according to the app's supported catalog maintenance procedure.

**A historical repair name changes unexpectedly:** review whether the repair stores a historical snapshot or displays a live catalog name. Do not assume this behavior without testing; preserve stable historical descriptions in the implementation.

**A custom device appears in the catalog without review:** investigate the custom intake-to-catalog write path. Public/custom repair details should remain request/repair data unless an authorized operation intentionally creates a global catalog record.

## What can and cannot be inferred from this guide

The data model and selection sequence above are the documented RepairBox workflow. The precise field names, edit buttons, filters, import/export actions and bulk operations must be taken from the installed Device Catalog screen. They should not be assumed solely from the presence of a catalog entity.

## Fields and table tools documented in the product guide

The documented Device management form includes these options. If the installed form has changed, follow the current labels and validation.

* **Brand (required):** connects the device to its manufacturer/brand.
* **Device Name (required and unique):** the name shown in catalog selection and repair records.
* **Model (optional):** additional model identifier where it is distinct from the device name.
* **Image (optional):** an image that helps staff recognize the device. The product guide describes a default placeholder when no image is uploaded.
* **Associated defects/services:** links the device to the repairable choices offered for that device, as supported by the current form.

### Search and list management

The documented device list includes:

* **Search** by device name, model or brand.
* **Filters** for narrowing the list, including brand-based filtering where available.
* **Pagination** to navigate larger result sets.

### Edit/delete considerations

The documented form allows staff to edit the brand, name, model, image and associated repairable options. Deleting an obsolete catalog record can affect the choices shown in future booking/intake and may affect linked data. Before deleting a brand/device, check for existing associations and historical records; prefer the supported inactive/archive path if the installed app offers one.

### Maintain brand records

The associated Brand management screen documented in the product guide allows the administrator to create a brand using a name and relevant notes, edit its information and delete a brand. One brand can be associated with multiple devices, and selecting a brand filters the available device/model choices during booking. Deleting a brand may affect linked devices, so verify those links before deletion.

## Test after a catalog change

Create a controlled repair booking/intake and verify the brand filters the intended devices, the correct services/defects appear, and the selected record is saved on the right Repair Item. A custom repair should remain custom; it must not auto-create a reusable device record.

## Related pages

* [Services & Defects](https://codehas.gitbook.io/the-repairbox/services-and-defects.md)
* [Creating a Repair Order](https://codehas.gitbook.io/the-repairbox/creating-a-repair-order.md)
* [Standard vs. Custom Repairs](https://codehas.gitbook.io/the-repairbox/standard-vs.-custom-repairs.md)
* [Embedded Repair Booking Widget](https://codehas.gitbook.io/the-repairbox/embedded-repair-booking-widget.md)

## Related pages

* Services & Defects
* Creating a Repair Order
* Adding Multiple Devices
* Standard vs. Custom Repairs
* General Application Settings
