Trace an order through history and activity
Use **Orders → History** when an order is no longer in its processing queue or you need to compare the original request with its final result. You need access to the order history and detail view.
Find the record
1. Open **Orders → History** (`/orders/history/all`).
2. Filter by **Status**, **Order Date** or **Order Completed Date**. These dates answer different questions.
3. Narrow by **Client**, **Client Group**, **Product**, **Category**, **Connected API**, **Inventory Group**, or **Base Field / IMEI / Serial No.** as needed.
4. Open the matched order and inspect the **Timeline** tab.
5. Compare the current reply, API status and supplier reference.
Use **Order Source** to distinguish how a request arrived. Service-specific fields can appear as additional columns or quick filters, which helps locate an order using information other than its base identifier.
Explain a mismatch
A local status change, a supplier send, a fetch and a customer wallet credit are different events. Read them together before deciding that a transfer failed or a supplier never received an order. A manual reply may explain why a later duplicate supplier response did not replace the result.
**Expected result:** you can identify the relevant order and the sequence that produced its current state. For support, provide the order reference, event time/time zone and relevant safe event details. Do not export an entire customer history when a single order and event are sufficient.