WooCommerce Test Order Evidence Log

Symptoms

• A launch or gateway change depends on memory, screenshots, or chat messages instead of a clear test record.
• The team cannot tell which payment method, currency, product type, refund path, or email was tested.
• A production issue appears after a supposedly completed payment test.

Most Common Causes

• Unstructured checkout testing often proves only one happy path and skips failure, pending, refund, webhook, or email behavior.
• Agency handoffs lose context when order IDs, provider transaction IDs, and approval owners are not recorded.
• Testing evidence needs to be private enough for provider data but clear enough for business signoff.

How To Confirm The Cause

• Define fields for order ID, date, tester, gateway, amount, currency, product, coupon, shipping, status path, provider transaction, email result, webhook result, refund or void result, and notes.
• Run one row per meaningful payment path rather than one generic 'checkout tested' row.
• Mark unresolved rows as blockers, not as launch proof.

Fixes

• Adopt the evidence log for gateway launches, migrations, plugin updates, currency changes, and checkout implementation changes.
• Keep provider secrets out of the log while preserving enough identifiers for authorized review.
• Use the log to decide what can launch, what needs retesting, and what belongs to provider support.

How To Verify The Fix

• Review the log before launch and confirm every required payment path has a passed row or documented exception.
• Sample one logged order and confirm WooCommerce, provider, webhook, and email evidence still matches.
• Archive the log with the launch notes so future incidents can compare current behavior with launch evidence.

When To Contact Support

Escalate when the test log reveals live-payment uncertainty, missing provider access, unclear refund state, or gateway behavior the site team cannot explain.