# QLS buy order: check a missing or failed transfer

QLS buy-order recovery starts with the original placed order, its reference and a destination check. Do not retry, resend or replace it until the connection owner confirms whether it arrived.

A missing order can require a matching correction or connection check. A visible error does not tell you whether another attempt created an order.

## Before you check a failed QLS buy order

Open the intended Optiply account and the matching QLS account. Keep the original order number, supplier, placement time and complete error text available.

Keep any existing order in place while you investigate. Replacing an order can create duplicates or change what the supplier receives.

## Steps to check a failed QLS buy order

1. Open the original buy order in Optiply.
2. Check whether the order is placed rather than still a draft.
3. Record its order number, supplier and placement time.
4. Search the intended QLS account for that original order.
5. If it exists, compare its supplier, products and quantities with Optiply.
6. If it is missing, confirm the agreed transfer schedule with the connection owner.
7. Record the full error message and any identifier changes.
8. Contact Optiply Support through the [QLS connection guide](/article/qls-set-up-and-connection).
9. Ask Support to confirm the destination state and safe recovery before a retry or replacement.


### QLS account and product checks

Confirm the destination company and brand with the connection owner. Check the order's products and supplier against that same account.

Check EAN and product identifiers with Support rather than changing them to force export. Product-import options and the outbound order route have different requirements.

QLS supports different buy-order formats. Support must confirm the active route before choosing a recovery action. Do not copy fields from another route.

## Information to include for a failed QLS buy order

| Information | Why it helps |
| --- | --- |
| Original Optiply order number | Identifies the order that should transfer. |
| Supplier and product identifiers | Supports matching checks without changing the records. |
| Placement time and current state | Distinguishes a placed order from a draft or later change. |
| Full error text | Identifies the reported condition without guessing from a number. |
| Destination search result | Shows whether the original order or a duplicate already exists. |
| Previous and current reference | Helps trace any reference change. |
| Any replacement order | Warns the owner before another attempt creates a duplicate. |

Do not include credentials, raw technical logs or unmasked personal details.

## What you see when the QLS order check worked

You know whether the original order is placed and whether it exists in the intended QLS account. Support can choose the next action from that state.

Recovery is complete only after the owner confirms the intended destination order. Sending a support request alone does not confirm transfer.

## Limits of QLS buy-order recovery

A retry can duplicate an order that already arrived. An automatic resend, fixed waiting period or replacement-order remedy is not part of this procedure.

Do not delete the original, change its reference, or place another order to bypass the error. If a replacement already exists, stop further retries.

## If the QLS order check did not resolve the issue

Give Support the information above, including both orders if you already created a replacement. Ask which order to retain before changing either.

If the product or supplier match is wrong, let the connection owner confirm the correction and recovery sequence. Recheck the intended destination afterward.

## Related articles on QLS connection and mapping

- [QLS connection setup](/article/qls-set-up-and-connection)
- [QLS data mapping](/article/integrations-data-mappings-public-qls)
