> 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/standard-vs.-custom-repairs.md).

# Standard vs. Custom Repairs

Repair intake offers two data-entry approaches: **standard/catalog-based** and **custom/manual**. The choice determines how the device and requested repair are described. It does not replace diagnosis, customer approval, technician work, QC or billing.

## Choose standard when a matching catalog record exists

The standard path follows the catalog hierarchy:

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

For example: Mobile → Apple → the correct iPhone model → Screen Replacement as the requested service and Cracked Screen as the reported defect.

Use this path when:

* The exact device/model or approved equivalent is present in the active catalog.
* Relevant services and defects are available for that device.
* You want consistent naming for search, reporting and repeat service workflows.

Steps:

1. Choose the device type.
2. Choose the brand.
3. Choose the matching device/model.
4. Select the service(s) that describe requested work.
5. Select defect(s) that describe the reported or known problem.
6. Record condition, accessories, photos and notes as relevant.
7. Verify the selections before saving.

A selected service is not proof that the repair is technically possible or completed. A reported defect is not a confirmed diagnosis. The technician must record inspection results through the configured diagnosis workflow.

## Choose custom when the catalog does not describe the device

Custom entry is suitable for an unusual model, vintage equipment, a generic device, an incomplete catalog, or a repair that cannot accurately be expressed through existing options.

The RepairBox product model allows manual capture of:

* **Device Type** — broad type of equipment.
* **Brand** — brand name, if known.
* **Model** — the model or identifying description.
* **Problem** — the customer-reported symptom/issue.
* **Service** — the repair requested or anticipated.
* **Notes** — relevant additional details.

These values should remain part of the repair's historical record. **A custom repair must not automatically create or modify shared catalog data.** If the business wants the device/service/defect reused in future jobs, an authorized user should deliberately add it through the catalog management workflow after checking naming, relationships and duplicates.

## How to decide

| Situation                                                                | Recommended choice                        | Reason                                             |
| ------------------------------------------------------------------------ | ----------------------------------------- | -------------------------------------------------- |
| Exact model and relevant service are available                           | Standard                                  | Structured data and consistent reporting           |
| Model is missing or ambiguous                                            | Custom, or request catalog maintenance    | Avoid attaching a repair to the wrong device       |
| Legacy/vintage equipment has no proper model record                      | Custom                                    | Preserve the information actually supplied         |
| Customer describes a symptom but technician has not inspected the device | Either, with symptom recorded as reported | Do not turn the symptom into a confirmed diagnosis |
| A new catalog entry is needed for future jobs                            | Add it deliberately to the catalog        | Keep shared reference data reviewed and controlled |
| Service name is available but not applicable to this device              | Do not select it merely because it exists | Prevent misleading intake and pricing              |

## Pricing and estimates

Do not assume catalog selection guarantees a final price. Use the price and estimate fields that actually exist in the installed intake/billing workflow. Confirm labor/parts, tax, discount and estimate approval rules before quoting the customer. Custom text by itself does not constitute a validated price or an approved estimate.

If the catalog has default service prices, confirm the price is still appropriate for that model, outlet and business policy before using it. Historical repair pricing should not silently change when a catalog value is later edited.

## What is preserved historically

For each Repair Item, record what was known at intake, what was selected from the catalog, what the customer reported, and what the technician later diagnosed. Catalog names and defaults can evolve; repair history should continue to explain what the customer actually brought in at the time.

## Common mistakes

**Wrong model chosen to proceed faster:** stop and use custom entry or ask for catalog maintenance.

**Customer symptom recorded as diagnosis:** retain it as “reported problem” until inspection confirms the fault.

**Custom entry treated as a global catalog request:** do not automatically insert it into the catalog.

**Service selection treated as customer approval:** record any required estimate and approval separately.

**Catalog price treated as guaranteed total:** verify actual estimate, tax, discounts and billing calculation.

## Checklist

* [ ] Standard path matches the physical device and available catalog.
* [ ] Correct services and defects are selected.
* [ ] Custom path is used when the catalog is insufficient.
* [ ] Reported problem remains distinct from diagnosis.
* [ ] Custom values stay on the repair record unless deliberately added to catalog.
* [ ] Price, estimate and approval are confirmed through the billing workflow.

{% hint style="success" icon="tag" %}
**Get RepairBox at a 10% discounted price**

Purchase RepairBox through the [official Gumroad listing](https://codehas.gumroad.com/l/repairbox) to get the product at a **10% discounted price**.
{% endhint %}

{% hint style="info" icon="envelope" %}
**Need a customized version?**

We also offer customized versions for business-specific requirements. Email <info.codehas@gmail.com> with your needs so we can discuss the right approach.
{% endhint %}

## Related pages

* Creating a Repair Order
* Adding Multiple Devices
* Device Catalog
* Services & Defects
* Diagnosis & Repair Workflow
* Estimates & Customer Approvals
