# Picqer purchase orders: check missing exports and incoming order status

Check the export job and matching Picqer order before resending a missing purchase order; inbound order status is a separate check.

## Task — Interpret an imported Picqer buy order

### Purpose

Distinguish an order coming from Picqer into Optiply from an order sent to Picqer, then check the matching record without creating a duplicate. A partially received incoming order and a failed outgoing order require different checks.

### Prerequisites

Know where the order was created and which Picqer connection and warehouse it belongs to. Use read-only checks first. Keep the original order available; do not delete, recreate or mark it completed merely to make synchronization appear successful.

### Steps

1. Establish the direction: **Picqer → Optiply** is an import; **Optiply → Picqer** is an export. Do not use an inbound schedule as an outbound waiting interval.
2. For an outgoing order, open **Settings → Integrations**, expand the Picqer source and select **Export jobs** when that tab is shown. Refresh job history. It shows recent jobs, not every historical attempt; no tab or no matching job needs a Support check.
3. Open the relevant job and inspect its order-specific success or error details. **Completed with errors** is not success for every order. Match the Optiply order with the returned Picqer reference, then check the order in Picqer, including warehouse, status, products and quantities.
4. If the order is absent, incomplete or the job failed, contact Support before any resend. Describe the direction, approximate attempt time and redacted error. Ask Support to verify whether Picqer accepted an order or any lines before arranging a safe correction.
5. For an incoming order, compare its Picqer status, warehouse and product lines with the agreed import scope. A **purchased** order can remain open while receipts are incomplete; **received** is the completion-status branch. Check receipt lines separately from the order's completion value.

### Fields and directions

- **Export job status:** queued/running is still in progress; completed can include order errors, so inspect the details.
- **Picqer reference:** identifies the remote order to compare, not a fixed waiting time.
- **Incoming completed value:** the import derives this from the source update time for received/cancelled statuses, subject to eligibility and existing-order handling. It is not the last receipt timestamp.
- **Incoming cancelled order:** accepted by the default status selection and assigned completion from the source update time; a configured exclusion can instead remove it from the synchronized order set.

### Expected result

You have distinguished import from export and checked the relevant job and matching order. An incomplete incoming receipt is not mistaken for a failed export, and an uncertain export is not duplicated.

### Limitations

There is no universal two-minute, nightly or next-run export guarantee. A successful job does not replace checking the order's actual lines and destination. If a missing product is omitted while the remaining lines are exported, Picqer can already contain an incomplete purchased order. Key permissions and configured supplier/warehouse handling can affect the result.

### Errors and recovery

For missing product lines, supplier matches or warehouse errors, have Support check the existing order and configuration before any resend. Do not broaden the API key, recreate the order or assume an automatic resend. If goods are no longer expected, follow your normal purchasing closure decision; do not close an order merely to repair a connection.

## Related reading

- [Picqer connection setup](/article/connect-picqer)
- [Picqer data mapping](/article/integrations-data-mappings-public-picqer)
- [Fulfilment warehouse scope](/article/picqer-fulfilment-set-up-and-connection)
