2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
List actual states
Use the store and payment integration's documented statuses, including pending, failed, canceled, and completed paths that apply.
Define operational meaning
For each state, record whether staff should wait, review, prepare, or investigate. Keep payment and delivery events distinct.
Trace test orders
Run approved scenarios and compare gateway events, order status, stock behavior, and customer messages. Include one failed or delayed path.
Assign exception ownership
Name the person who handles ambiguous states and the evidence they need. Prevent repeated actions without first checking existing outcomes.
Worked scenario
See the plan in practice.
An authorized payment may await capture while an order remains open. Staff need a documented action instead of guessing from a familiar label.
Review your result
Your acceptance checklist
States explained- Events traced
- Exceptions owned
Use these checks to identify gaps in your order-state operations map. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
- Order statusA label representing an order's current stage in a store's processing workflow.
- Payment authorizationA payment-processing step that checks and, for supported payment flows, reserves an amount for a potential later capture.
- Payment captureThe step that requests collection of a previously authorized payment amount in a supported payment flow.
Primary references
For the underlying concepts and current platform details:
