> 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/public-repair-tracking-widget.md).

# Public Repair Tracking Widget

The Public Repair Tracking Widget is the customer-facing status lookup path. It should provide a limited view of repair progress without exposing the Admin or Workshop portal. The public page must be a read-only projection of the authoritative Repair Order/Repair Item data, not a copy of internal workflow details.

## Tracking customer journey

1. Customer receives or finds the tracking instruction/reference supported by the deployed RepairBox version.
2. Customer opens the public tracking page.
3. The app validates the supplied tracking credential/reference using the installed access method.
4. The server verifies the customer/order association and returns only fields approved for public display.
5. The customer sees the appropriate order/item state and the next step, if that information is maintained.
6. If the customer needs to approve an estimate, pay an invoice, change contact details or request an action, the tracking page should direct them to the separate authorized workflow; it must not imply that viewing the page performs that action.

The exact lookup method (for example, token link, repair reference with additional verification, or authenticated portal) must be confirmed from the deployed widget. Do not treat a sequential Repair Order number alone as a secure token.

## Why order and item status must be separate

A Repair Order can include multiple Repair Items. One device may be ready for pickup while another is still being diagnosed or repaired. A useful public tracking experience distinguishes:

* The overall order's customer-facing state, where supported.
* Each device/item's state when item-level tracking is enabled.
* The next action that applies to the item/order.
* Contact details for the relevant outlet.

Avoid displaying “all repairs ready” when only one item is ready. Do not calculate completion solely from the first or most recently modified item.

## What should be displayed

The public page should use an allowlist of customer-safe fields. Exact options that can be toggled in the deployed widget must be checked in the actual configuration screen; do not assume all rows below are independently configurable.

| Field family                                                  | Customer-facing purpose                           | Restriction                                                                      |
| ------------------------------------------------------------- | ------------------------------------------------- | -------------------------------------------------------------------------------- |
| Human-readable repair reference                               | Lets customer/staff talk about the same repair    | Not a secret and not sufficient access control by itself                         |
| Business/outlet label and public contact                      | Lets customer reach the correct location          | Do not expose private staff details                                              |
| Device summary                                                | Lets customer identify the device                 | Show only the relevant item's data                                               |
| Order/item status                                             | Shows repair progress                             | Use customer-appropriate wording and correct scope                               |
| Received/updated date                                         | Provides limited context when helpful             | Avoid leaking internal operational details                                       |
| Next step                                                     | Explains approval, pickup or contact requirements | Must match actual configured workflow                                            |
| Estimate/invoice/payment summary                              | May show limited financial state if supported     | Do not display provider secrets, card data or another customer's billing records |
| Internal notes, diagnostic-only comments, private attachments | Not intended for public display by default        | Must remain protected by server-side access controls                             |

The public API/controller must return only the approved public fields. Sending a complete staff resource to the browser and hiding fields with CSS is not safe.

## Configure the tracking experience

Use the actual controls present in the deployed RepairBox tracking-widget configuration. Before enabling the page, verify each applicable item:

1. **Access method:** what the customer needs to supply and how the server verifies it.
2. **Enabled state/public route:** how staff enable, disable or publish the public tracking page in this release, if such a control exists.
3. **Visible field selection:** which public fields the page returns. Verify this at the server/API boundary.
4. **Status wording:** how configured internal states are translated to customer-facing progress, if the implementation supports mappings.
5. **Multi-device presentation:** whether each Repair Item is displayed separately and how overall status is summarized.
6. **Business/outlet contact:** which public contact details are shown and how the correct outlet is chosen.
7. **Language/direction:** ensure the actual supported locale settings are tested for LTR/RTL customers.
8. **Link expiry/revocation:** define behavior only if the installed link/token model supports it.
9. **Abuse control:** verify rate limits, enumeration protection and safe invalid-reference responses.
10. **Privacy and caching:** public pages should not leak personalized data through shared cache, referrer logs or analytics.

The available RepairBox source for this review does not expose the exact list of widget settings or UI control names. This guide therefore defines what must be verified without inventing switches or routes that may not exist in your current admin panel.

## Status mapping and customer wording

The business may configure dynamic statuses for order/item workflow. Public tracking should avoid showing internal labels that customers cannot interpret. Examples of customer-friendly wording are below; these are suggested labels, not a statement that the app has these mappings preconfigured.

| Internal workflow meaning  | Possible customer wording                          |
| -------------------------- | -------------------------------------------------- |
| Intake complete            | Repair received                                    |
| Diagnosis not yet complete | Awaiting diagnosis                                 |
| Technician is inspecting   | Diagnosis in progress                              |
| Quote requires decision    | Estimate awaiting your approval                    |
| Repair being performed     | Repair in progress                                 |
| Final checks underway      | Quality checks in progress                         |
| Collection allowed         | Ready for pickup                                   |
| Work closed                | Completed                                          |
| Order cancelled            | Cancelled; contact the shop if you need assistance |

Do not promise a completion date, parts availability, price or service level unless the corresponding data is stored and approved for customer display.

## Privacy and security requirements

* Use HTTPS.
* Enforce authorization/token/reference checks on the server for each lookup.
* Do not use the numeric database ID as a secret.
* Apply rate limits and enumeration protections where supported.
* Return a safe invalid/unauthorized response that does not reveal other customers' orders.
* Do not expose staff-only notes, internal diagnosis fields, contact details beyond the approved policy, or private attachments.
* Avoid logging full access tokens or putting them into analytics.
* Prevent public responses from being stored in shared caches when they contain repair-specific data.
* Treat copied tracking links as credentials if possession of the link grants access.
* Confirm that outlet/business scope is enforced.
* Keep payment, approval and account-edit actions in their separate authorized flows.

## Test scenarios before go-live

* A valid lookup for a single-device repair.
* A multi-device order with different item statuses.
* Invalid/missing reference or token.
* A reference that belongs to a different customer.
* An order with internal notes and private attachments.
* Awaiting-approval, ready-for-pickup, cancelled and completed states.
* A customer opening an older link after status changes.
* Rate-limited repeated random lookups.
* A status update made while the customer page is open.
* A public user attempting to change URL/reference values to access another order.

## Troubleshooting

**Customer cannot find a repair:** check the actual access method, reference/token, order creation path and customer/outlet association.

**Public state is stale:** check the stored order/item state, API response and cache. Do not add a public-specific manual status that can drift from the Repair Item.

**One device appears but another does not:** check whether the public view includes all permitted Repair Items and whether it intentionally hides certain items. Do not read order completion from only one item.

**Internal details are visible:** disable/restrict public tracking as appropriate and fix the server-side response allowlist immediately.

**Reference guessing exposes records:** a repair number alone is insufficient. Require the supported secure access mechanism and add rate limiting.

**The page has no expected configuration switch:** do not assume the control exists; check the actual deployed UI and code. Document only controls present in that release.

## Go-live checklist

* [ ] Access mechanism verified from current code/UI.
* [ ] Public API exposes an explicit allowlist.
* [ ] Order/item states display correctly for multiple devices.
* [ ] Internal notes and private attachments remain inaccessible.
* [ ] Invalid references do not reveal other customer records.
* [ ] Customer-facing status and next-step wording is accurate.
* [ ] HTTPS, caching, rate limits and logging are safe.
* [ ] Link expiry/revocation is tested if the implementation supports it.
* [ ] Public tracking is not confused with estimate approval or payment.

## Tracking behavior documented in RepairBox

The product guide describes a public Track Repair widget in which a visitor enters the **Repair ID** and can view the repair status and repair log. The result can be printed or downloaded as a PDF. Use the currently generated Track Repair embed snippet from the App Settings **Embedding Code** area where that feature is available.

Because the documented flow accepts a repair ID as the lookup input, treat that ID as a record reference—not a secret credential. Before enabling public access, verify precisely which fields the current version returns. Private customer addresses, staff-only notes, sensitive diagnosis, internal attachments, financial/provider metadata and unrelated Repair Items must not be exposed. If access depends only on a repair ID, the business should assess enumeration/privacy risk and limit the public response accordingly.

## Set up and test the tracking embed

1. Open App Settings and find the Embedding Code area if exposed by this deployment.
2. Choose the Track Repair widget and copy the snippet generated by the application.
3. Add the snippet to the appropriate customer-facing page on the business website.
4. Test with a known Repair ID in a clean browser session.
5. Verify the displayed status and log correspond to the correct repair and contain only approved customer-visible fields.
6. Test invalid/random IDs and confirm they do not reveal another customer's record.
7. Verify print and PDF download if those actions are present in the deployed widget.
8. Update a test repair status and confirm the tracking result reflects the saved source record.

Do not invent widget URL parameters or assume token expiry/second-factor settings exist unless those controls appear in the installed UI.

## Print/PDF behavior

The documented tracking result can be printed or downloaded as PDF. Treat this output as a data export: inspect it for private notes, internal-only fields and customer information before enabling it publicly. Apply the same public-field restrictions to the PDF/print view as to the tracking page itself.

{% 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

* [General Application Settings](https://codehas.gitbook.io/the-repairbox/general-application-settings.md)
* [Embedded Repair Booking Widget](https://codehas.gitbook.io/the-repairbox/embedded-repair-booking-widget.md)
* [Repair Tracking](https://codehas.gitbook.io/the-repairbox/repair-tracking.md)
* [Customer Portal](https://codehas.gitbook.io/the-repairbox/05-customer-portal.md)
* [Notification Settings](https://codehas.gitbook.io/the-repairbox/notification-settings.md)

## Related pages

* [Embedded Repair Booking Widget](https://codehas.gitbook.io/the-repairbox/embedded-repair-booking-widget.md)
* [Repair Tracking](https://codehas.gitbook.io/the-repairbox/repair-tracking.md)
* [Customer Portal](https://codehas.gitbook.io/the-repairbox/05-customer-portal.md)
* [Notification Settings](https://codehas.gitbook.io/the-repairbox/notification-settings.md)
* [Creating a Repair Order](https://codehas.gitbook.io/the-repairbox/creating-a-repair-order.md)
