b2c-checkout-triage
Checkout and payment triage
Outcome: quantify the observed symptom, localize a likely subsystem, and produce an actionable handoff. Do not create test orders, charge/refund payments, change order status, or modify production data as part of inspection.
Scope and impact
Use config_inspect (CLI: b2c setup inspect) and confirm site, UTC time window,
reported symptom, and comparison period. Ask for missing values. Preserve the
same target/window in all calls. No cartridge source is required.
"Orders down" can mean less traffic, checkout errors, abandoned baskets, payment declines, or delayed reporting. Failed order records alone do not measure all checkout attempts or conversion. Do not force every incident into a payment cause. Record breadth, duration, workaround, and owner. Follow the team's severity and update process for live customer impact; do not wait for exact counts to escalate.