# Manage connected products and exception reviews

Bind the correct source site, repair retained updates and acknowledge the exact exception without changing quantities.

Source: https://help.smartfact.ai/manuals/purchasing/connected-products-and-exceptions

Review edition: 25 October 2026

Roles: owner, supervisor

Connected products own the need they submit and, for stock, the physical receipts. **Products** configures their relationship with Purchasing. **Exceptions** records supervisory follow-up. A connection repair or acknowledgement does not place an order or change a stock balance.

## Bind the intended source site

As owner, open **Products** at the real site with recent Accounts verification. Check the source's availability and **Last successful call**. If the source is unavailable or none is registered, ask support to check its registration; this page does not register signing keys or delivery addresses.

For the intended product, set **Accept new requests from this product** and **Connected product's site key**, then choose **Save product settings**. Use the site key supplied by that product, with 1 to 64 letters, digits, underscores or hyphens. With no existing binding, leaving it blank allows the first accepted signed request to establish the binding. With an existing binding, blank keeps its current key.

Switching off acceptance stops new requests while preserving existing orders and their receipt updates. Changing a bound site key requires all open requests and open order lines from that source to be resolved first. Hand those obligations to a supervisor; do not invent a different key to bypass the refusal. Check the source product's own connection instructions, including [StoresFlow](/manuals/storesflow) where applicable.

## Repair an update requiring a person

Under **Product updates**, use **Refresh delivery status** and inspect the relevant retained update. Pending means it is waiting for its next attempt; delivered means the connected product received the update. These notifications tell the product to refresh Purchasing records.

For a parked update, read the stated cause. Recovery changes require reconciliation with the connected product. A registration or binding mismatch needs current **Products** settings and registration checked. A refused address or retained-content problem needs support. Record the actual repair in **What has been checked or repaired?**, then choose **Retry this retained update**.

Repair requires owner authority and recent verification. It preserves the update's identity and makes it pending again; it does not place or send a supplier order. Check the later delivery outcome. If recording loses its answer, use [uncertain results](/manuals/purchasing/uncertain-results) with the retained original action.

## Review the exact exception

As supervisor, open **Exceptions**, then **Needs review**. Open the linked order where present and read the flags in context. Examples include receipt after cancellation, receipt against an earlier revision, changed source need or a source that has not made a successful call for 24 hours. A receipt before recorded supplier communication is shown as information; it is not proof the physical receipt was wrong.

Investigate with the responsible person or product before choosing **Acknowledge with a note**. Enter a useful **Review note** of up to 500 Unicode characters, without line breaks or other control characters, then choose **Record acknowledgement**. The acknowledgement belongs to that exact current exception version. If the exception changed, reload and review its new facts before recording again.

**Reviewed current exceptions** shows acknowledgements for the current facts. Acknowledgement retains who reviewed, when and the note. It changes neither quantity nor draft checks nor source delivery. A changed draft still needs its line review before approval; a parked update still needs the owner repair above.

## Keep the right follow-up separate

For supplier-response exceptions, choose **Review supplier response** or **Supplier response details** and follow [supplier responses](/manuals/purchasing/supplier-responses). For a receipt discrepancy, follow [deliveries](/manuals/purchasing/deliveries), with physical stock corrections in the stock product. Use the exception list's CSV or XLSX download for its current matching scope when handing over several cases.

Give the next owner or supervisor the source and site key, order reference and revision, line and unit, exception evidence and review note, plus the retained update or original action identity. A tidy exception list is not evidence that every outside obligation has been fulfilled.