1. Selecting pages to monitor
Monitoring starts from the pages that move a sale forward: a representative product page, cart, checkout, payment step and confirmation signal. URLs are attached to the configured site, not hardcoded into tests.
2. Fast non-mutating read
Stateless checks verify that pages respond, expected content exists, payment methods are not missing and known errors do not block the funnel. These checks run without creating an account, placing an order or collecting customer data.
3. Bounded synthetic journey
When the offer allows it, a synthetic journey verifies that WooCommerce lets a test scenario progress toward expected signals. The purpose is to prove the failure or the return to green, not to make a real purchase.
4. Opening an incident
An incident opens when the breakage affects a useful step: unexpectedly empty cart, unreachable checkout, missing payment, validation error or absent confirmation. The report keeps the error class, step, timestamp and filtered technical elements.
5. Alerts and proof
The alert summarises what is broken and what to check. Proof can be shared as cockpit view, read-only link or PDF depending on the offer. Secrets, cards, buyer emails, addresses and detailed cart contents are excluded.
6. Return to green
When checks turn green again, the incident can be closed and before/after proof shows the correction was verified. CashFlowCanary does not automatically fix the site: it provides the signal, proof and next action.