Define an exception
Supply the order and fulfillment records, status definitions, freshness timestamps, and exception rules. Define how partial shipments, cancellations, backorders, and duplicate records should appear.
Ask Nema to preserve source timestamps. A carrier status from yesterday may not describe the current order.
Build the queue
Nema can group exceptions by reason, remove exact duplicates, and identify missing owners or conflicting statuses. Each item should include the source and timestamp that support it.
The queue is a review tool. It does not prove current store availability or authorize a refund.
Include the last customer-facing update when it is part of the permitted record. This helps the owner avoid sending a duplicate or contradictory message. Keep internal notes separate from customer copy.
Review in operations
Post the queue in the operations channel. Fulfillment, support, and inventory owners can correct routing before work begins. Nema can update the queue as people resolve missing context.
A practical example
The order export marks a shipment complete, while the fulfillment record shows one item backordered. Nema keeps the case open, links both statuses, and routes it to the fulfillment lead. It also separates two delayed orders that lack recent carrier scans.
The lead assigns owners and approves the internal status update.
Make the rules explicit
Keep status mappings, age thresholds, and ownership rules in the channel guidance or supplied procedure. Review them when carriers, stores, or fulfillment systems change.
Record how each exception ended. A resolved delay, cancellation, reshipment, and data error should not all collapse into "closed." Clear outcomes improve later reporting.
When the queue is large, agree on sorting rules before the review. Age, customer commitment, value, and operational risk can point in different directions. Nema can apply the approved order and show ties, while the lead decides whether a case needs escalation. Keep the untouched records available so the team can audit why an item appeared.
State when the queue was generated and which orders it covers.
Common questions
Can Nema issue refunds?
This workflow does not authorize refunds. A verified, separately governed action would still need the appropriate owner.
Can Nema tell whether an item is available?
Only from a current, verified source. Show the inventory timestamp and avoid availability guarantees.
How are duplicates handled?
Define the order and shipment identifiers that establish a duplicate. Nema can flag near-matches for human review.