Send an order to its supplier or fetch a result

Use Orders → Pending Orders → API Connected for supplier-connected work. Before a manual send or fetch, inspect the order, selected supplier service, API status and API Order/Ref. ID. Your staff role must allow the relevant action.

Send or fetch

  1. Filter to the intended product and select the specific order or rows.
  2. Use Forcefully Send only when the order has not already been submitted and you intend to place that supplier request.
  3. Use Forcefully Get when a supplier reference already exists and you want to retrieve its result.
  4. Review the confirmation and per-order results.
  5. Refresh the order and verify its new API status and reference.

A send is refused when an API reference already exists, or the order is already Success or Rejected. A fetch requires an existing supplier reference and is not a substitute for sending an unsent order. The system can also ask you to wait while another receive action is in progress.

Timeouts and uncertain outcomes

A timeout can mean the response was not received after the supplier accepted the request. Check the supplier’s own order record before changing a reference or resending. Sending twice can purchase the service twice.

For a bulk action, keep the processing dialog open and review success/error counts. Cancelling a browser batch stops further requests where possible; it does not undo supplier calls already made.

Expected result: an unsent order obtains the appropriate supplier reference, or an existing request receives an updated result. If nothing changes, inspect the individual error and connection/service mapping before retrying.

Related guides

Understand order and supplier statuses Change an order supplier or reset a reference