# Synthetic sample: operations exception review item

Illustrative output only. The records and identifiers are fictional. No system was queried, ticket created, refund issued or stock allocation changed.

## Ready sample — needs operations review

Reference: EX-1042. Order: ORD-1042.

Observed evidence:
- Sample commerce.csv row ORD-1042: payment=paid; allocation=allocated.
- Sample warehouse.csv row ORD-1042: reserved_units=0.
- The cause of the mismatch is not established.

Proposed owner: operations lead.

Review request: Check the warehouse reservation and the time of both exports. Preserve both source rows.

Duplicate key: ORD-1042:inventory-mismatch.

Action boundary: no refund, reallocation or customer message. The operations lead decides the next step after reviewing the evidence.

## Missing-input path — record cannot be matched

The warehouse row has no order identifier. A similar customer name or amount is not enough to join the records safely.

Keep the row in the intake exception list. Do not attach it to a guessed order.

Request: “Please supply the order identifier and export time, or have the record owner reconcile this row.”

Resume after the source owner confirms the identifier; repeat matching and duplicate checks.

Discuss this workflow: https://leon-ai-workflows.pages.dev/?workflow=operations#contact

Leon S Kennedy — Independent FDE Engineer (Forward Deployed Engineer)