> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.servinix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# RMA backend operations (internal)

> Support-only reference for tracking RMA orders via the BitBrew Fulfillment API, escalating stuck returns, and interpreting Danlaw transaction status codes.

# RMA backend operations (internal)

This article is for Servinix support agents. It covers how to look up an active RMA order in the BitBrew Fulfillment API, what Danlaw transaction status codes mean, and the escalation path for returns that are stuck or disputed.

## Before you start

* You need support-level access to the BitBrew Fulfillment API dashboard or the internal order query tool.
* Obtain the customer's RMA reference number and the carrier tracking number for the return shipment before querying.
* Confirm the shipment has been delivered to Danlaw using the carrier tracking link before escalating — Danlaw cannot process an order that has not arrived.

## Tracking an RMA order

The RMA lifecycle in the backend follows the Danlaw Fulfillment Workflow:

1. **Order submitted** — Servinix sends the RMA/Return order to the BitBrew Fulfillment API. Danlaw processes the order and sends a shipment label to the customer or fleet.
2. **Label sent** — Danlaw generates and dispatches the prepaid return label. BitBrew records this as `LABEL_ISSUED`.
3. **Shipment in transit** — Customer returns the device using the shipment label. No API status change until Danlaw receives the package.
4. **Received** — Danlaw receives the shipment and begins processing the RMA/Return order. Status moves to `RECEIVED`.
5. **Refurbishment** — Device undergoes cosmetic refurbishment and label replacement. Status: `REFURBISHING`.
6. **Flashing** — User data is wiped and firmware is reflashed. Status: `FLASHING`.
7. **Closed** — Device returned to inventory. Status: `CLOSED`. BitBrew notifies Servinix.

## Common Danlaw transaction status codes

| Status code    | Meaning                                             | Typical next action                                       |
| -------------- | --------------------------------------------------- | --------------------------------------------------------- |
| `LABEL_ISSUED` | Prepaid label generated and sent to customer        | Wait for customer to ship                                 |
| `RECEIVED`     | Danlaw has the device; processing started           | No action; monitor progress                               |
| `REFURBISHING` | Cosmetic refurbishment in progress                  | No action                                                 |
| `FLASHING`     | Firmware wipe and reflash in progress               | No action                                                 |
| `CLOSED`       | RMA complete; device back in inventory              | Confirm with customer; initiate replacement if applicable |
| `HOLD`         | Device flagged for manual review (damage, mismatch) | Escalate to Danlaw point of contact                       |
| `REJECTED`     | Device not matching the RMA order or beyond repair  | Contact customer; open replacement or credit case         |

## Escalating a stuck return

Escalate to Danlaw if any of the following apply:

* The order has been in `RECEIVED` status for more than 5 business days with no progression.
* The status is `HOLD` and no update has been received from Danlaw within 2 business days.
* The customer's carrier tracking shows delivery but Danlaw has not updated the order to `RECEIVED` within 2 business days of delivery.

**Escalation path:**

1. Gather: RMA reference number, carrier tracking number, delivery confirmation screenshot.
2. Contact the Danlaw operations point of contact via the internal escalation channel (see the internal Escalation Path article for current contacts).
3. Log the escalation in the Servinix support system against the customer account.
4. Update the customer within 1 business day of escalating with a status summary.

## Result / verify

An RMA is fully resolved when the BitBrew status is `CLOSED` and Servinix reflects the updated device inventory or triggers a replacement shipment. Confirm with the customer that they have received any replacement device or account credit before closing the support case.

## Related

* [Request an RMA / device return](/gps-tracking/maintenance-and-rma/request-an-rma-return)
* [RMA processing timeline](/gps-tracking/maintenance-and-rma/rma-processing-timeline)
* [Device not reporting data](/gps-tracking/gps-troubleshooting/device-not-reporting)
* [Manage cable and accessory orders](/gps-tracking/gps-settings/manage-cable-and-accessory-orders)