# Review held shop orders and delivery evidence

Inspect original mappings, accepted deductions and exact receiver revisions before resolving work.

Source: https://help.smartfact.ai/manuals/configsheets/shop-orders

Review edition: 25 October 2026

Roles: operator, supervisor, owner, viewer

A shop order combines external observations, retained mapping terms, decisions and delivery evidence. Inspect the exact order and line before choosing a permitted action. The shop's latest status is not by itself proof of what reached StoresFlow.

## Find the reason for held work

Open Shop connections and select the intended shop. Filter Orders and held changes by All orders, Needs a mapping or Needs attention. Use View mapping and held lines to inspect exact SKU identities, conversion and reason. Follow View stock outcomes for retained receiver results.

Read the delivered revision alongside the latest revision and the last shop and stock read times. A new source read can create work without completing its downstream effect. A held line should not be described as deducted simply because other lines in the same order progressed.

## Use the current operational action

Operator authority permits Read the order again, Send refused lines again where offered and retained-event replay. Supervisor authority alone does not grant those Operator actions. A person doing both kinds of work needs both roles.

Only a Supervisor can Decide the deduction for a binned or deleted order. Choose Keep the deduction or Reverse the deduction, give the reason and complete recent Accounts verification. This queues the decision for authoritative reconciliation. A permanently deleted order's recorded decision is final. For a binned order, the next authoritative read checks the current shop state. Owners control connection admission; Authors and Reviewers control mapping releases.

Earlier accepted lines retain their original conversion basis. New lines may use a later reviewed mapping. Inspect the actual provenance instead of applying today's table to every historical line. Removed line membership and refunds need their supported observed workflow.

## Recover an uncertain delivery

Inspect Delivery evidence, event identity, revision, attempts and last issue. Where replay is available, retain and recover the exact original event. Do not create another stock event simply because a delivery acknowledgement was lost. A queued or attempted event is not a confirmed receiver result.

Use Stock outcomes and receiver evidence to establish what actually happened. If the order's detail has expired under protected retention, the screen identifies it as earlier detail expired while retaining the required stock evidence. Do not offer an expired old event as replayable.

Escalate with shop, order, line, mapping and event references. Continue with [Read history, export and recover](/manuals/configsheets/history-export-and-recovery) for retention and restore limits.