Accept and reply to legacy service orders

Fusion Owned License is end of life; these instructions describe existing legacy installations, and labels can vary by build.

IMEI orders: accept new orders

Open **Orders > Accepted IMEI Orders > New Order**.

- **Quick Accept** lists orders from all services. Select individual checkboxes or **Check All**, then choose **Accept** or **Reject**. The documented actions also include **Copy IMEI**, **Connect API**, and **Resubmit order**.

- **Accept Service-wise** filters new orders to the chosen service before acceptance.

- **Verify for API** contains orders held because **Edit services > API connection > Verify before sending to supplier** is enabled. Approve the order here before the cron job processes it.

Check the selected orders and the supplier outcome before Connect API or Resubmit order; a timeout does not prove that the first request was never created.

IMEI orders: reply or review rejection

**Orders > Accepted IMEI Orders** opens **Manual Reply** by default. Use the Accepted IMEI Orders menu to switch modes.

- **Manual Reply**: select orders and reply with a code/message or reject with a reason.

- **Quick Reply**: filter by service, user, date or IMEI and reply to or reject one or multiple orders without opening each order.

- **Bulk Reply**: upload a text file or paste identifiers and replies. Set **Select Service** to one service or all; **Reply separated by** identifies the separator between the IMEI and reply code, such as comma, hyphen, underscore or space. Use **Reply with** for the intended reply or **Reject with** for the rejection message.

**Orders > Accepted IMEI Orders > Rejected Verification** holds applicable provider rejections when the service's **Rejected verification** setting is enabled, so an administrator can review them before they reach the customer.

File orders

Open **Orders > Accepted File Orders**. It defaults to **Reply Accepted Orders**: select orders, choose the reply file, or reject with a reason.

- **Quick Accept**: select one or multiple new orders across services and accept or reject them.

- **Accept Service-wise**: filter new orders to a service before accepting them.

- **Quick Reply**: filter by service, user or date and reply to or reject selected orders.

- **Orders for verification**: review customer verification requests for previously replied or rejected orders, where the service allows that action.

These are the file-order modes; do not substitute an IMEI code reply for a file where the service expects a returned file.

Server orders with an API

Open **Orders > Accepted Server Orders(with API)**. It opens **Manual Reply** by default; the accepted-orders menu also offers **Quick Reply**.

- **Manual Reply**: select orders to reply with a message/code or reject with a reason.

- **Quick Reply**: filter by service, user or date and reply to or reject the selected orders.

- **New orders > Quick Accept**: select orders from all services, then accept or reject.

- **New orders > Accept Service-wise**: filter and accept one service's orders.

- **Rejected Verification**: review provider rejections held by the service's API **Rejected verification** setting; the documented workflow may then select another API connection.

- **Orders for Verification**: review permitted customer requests to recheck replied or rejected orders.

- **Pending Payment**: review the listed Order ID, client and amount.

Manually handled server orders

Open **Orders > Accepted Server Orders**. This is separate from the **(with API)** queue and defaults to **Manual Reply**.

Use **Manual Reply**, **Quick Accept**, **Quick Reply**, or **Accept Service-wise** for the same respective selection/reply stages. Quick Reply filters by service, user and date. **Orders for Verification** contains permitted customer recheck requests. **Pending Order** lists pending orders with Order ID, client and amount.

Remote orders

Open **Orders > Accepted Remote Orders** for remote-service orders.

**Manual Reply** is the default. **Quick Reply** filters by service, user and date. **Bulk Reply** accepts a text file or pasted identifiers/results with **Select Service**, **Reply separated by**, **Reply with**, and **Reject with**, as documented for bulk IMEI replies.

Under **New Order**, use **Quick Accept** for individual or all selected orders, or **Accept Service-wise** to select by service. The documented quick-accept actions also include **Copy IMEI**, **Connect API**, and **Resubmit order**. **Verify for API** holds orders until approval when **Verify before sending to supplier** is enabled. **Rejected Verification** holds applicable provider rejections for review. Review the prior outcome before a resubmit or alternate-provider request.

History and pending payments

The documented history paths are:

- **Orders > IMEI Order History**, with **Pending Payment** for Order ID, client and amount.

- **Orders > File Orders History**.

- **Orders > Server Order History** for the API-server section.

- **Orders > Server Orders History** for the manually handled server section.

- **Orders > Remote Order History**, with **Pending Payment**.

History can filter by group and export records. The archived layout separates the current year and previous five years in the menus, with older records under **Archive orders**. An order detail can link service, API and client information, show the API log, change an API connection, reply/reject or alter a status. IMEI details additionally include MEP, Model, Brand, Country, Provider, Network and PRD.

Changing a local history status does not cancel a supplier's work or establish that a payment settled. Check the order timeline before changing a completed or previously rejected order.