# WordPress / WooCommerce Triage Sample

This is a sanitized sample of the handoff format for a focused WordPress, WooCommerce, booking, cache, or payment-plugin triage pass.
It is not a client deliverable and does not contain private site data.

## Input

- Target: WordPress site with WooCommerce, a booking plugin, or a payment gateway
- Reported issue: checkout, booking, email, webhook, availability, or admin flow is blocked
- Available material: staging URL, screenshots, plugin list, theme name, browser error, exported order or booking sample, and the expected result

## Triage Pass

1. Reproduce the broken flow in a safe staging or limited-access environment.
2. Capture browser console, network requests, relevant WordPress/PHP errors, and visible plugin state.
3. Isolate whether the failure is coming from theme code, plugin conflict, cache rules, payment status mapping, timezone, webhook delivery, or form configuration.
4. Apply the smallest useful fix or produce a precise change plan when production credentials or irreversible changes are required.
5. Validate the same flow again and leave rollback notes.

## Checks

- WooCommerce checkout fields, order status transitions, payment method visibility, coupon or fee logic, and transactional emails
- Mercado Pago, Stripe, PayPal, or similar gateway status mapping, sandbox/live mode, webhook URL, and callback errors
- Amelia or booking plugin services, employees, events, availability, shortcodes, timezone, Google Calendar sync, and notification templates
- Elementor/theme JavaScript errors, broken layout states, missing assets, and responsive issues
- Cloudflare, WP Rocket, LiteSpeed, cache plugin exclusions, stale assets, and headers that can break admin or checkout flows
- WordPress cron, email delivery, plugin logs, PHP version warnings, and fatal error traces

## Output

A useful first pass should produce one of these:

- a working fix for the isolated blocker;
- a safe plugin/theme/cache configuration change with before/after notes;
- a patch or snippet ready for review;
- a short report proving the root cause and naming the next required owner action.

## Acceptance Check

Run the blocked flow after the change:

- the same test product, booking, form, or payment path reaches the expected state;
- browser console and network output are captured for the final pass;
- order, booking, email, webhook, or admin status matches the expected result;
- cache and rollback notes are written so the owner can safely keep or revert the change.

## Boundaries

- No destructive production changes without explicit approval.
- No stored credentials, cookies, recovery codes, card data, tax data, or payout information.
- No CAPTCHA bypass, hidden scraping, or platform abuse.
- Payment, legal, KYC, tax, and account-owner actions stay with the human account owner.

## Handoff

Deliverables for a first pass:

- issue summary and likely root cause;
- exact files, settings, or plugin screens touched;
- screenshots, log snippets, or command output used as evidence;
- acceptance check result;
- remaining risk and what needs real owner access or production confirmation.