Classify the exception
Identify whether the issue concerns reservation, cutoff, capacity, checkout, provider payment, webhook verification, reconciliation, cancellation, refund, dispute, production, packing, or fulfilment.
Give every unresolved state an owner and next check.
An exception queue is useful when it distinguishes external provider state, internal order state, operational progress, customer communication, ownership, and the evidence required to resolve the case.
Protect idempotency
Retry only through the supported application path. Do not create a replacement order, resend a refund, or replay an external event without checking existing identifiers and recorded state.
Use the right authority
Restrict financial, personal-data, account, provider, and fulfilment actions to their narrow roles. Record actor, reason, request or provider reference, prior state, resulting state, and failure where applicable.
Close with evidence
Confirm the provider and OrderPay states agree, document any lawful customer communication, preserve required audit evidence, and leave unresolved cases visible with a next review time.