Get your first check running
Install the pilot plugin, connect your store, and verify exactly what is being monitored.
The ZIP is a connector, not a standalone monitoring service. Request pilot access before installation. Purchasing and self-service enrollment are not open.
1. Check compatibility
Use an HTTPS WordPress site with WooCommerce and PHP 8.1 or newer. Check the tested version matrix. Start on staging when your checkout uses custom plugins, subscriptions, memberships or unusual shipping rules.
2. Install the WordPress plugin
Download RevenueGuard 0.1.0. In WordPress, open Plugins → Add New Plugin → Upload Plugin, select the ZIP, install it, and activate it. WooCommerce must be active.
3. Create a store in your dashboard
Sign in with the account supplied by SamSiyu. Choose Connect a store, then enter its HTTPS URL, a published product URL and the checkout URL. Start with an in-stock simple product.
Choose the expected payment gateway ID, such as bacs for bank transfer. The ID must match the installed gateway; ask support if you are unsure. Add country/state/postal code details and require shipping for a physical product. A virtual product can leave that requirement off.
4. Pair the plugin
Copy the server URL, store ID and connection secret shown in the dashboard into WooCommerce → RevenueGuard in WordPress. Enable monitoring, save, and select Send health check now. Keep the secret private. Do not paste it into a support ticket.
The site must answer the signed ownership check before browser runs start. The default hosted server is https://revenueguard.samsiyu.com.
5. Verify your coverage and alerts
Run a check and open its evidence. Confirm that product, cart, checkout, shipping (when required), payment availability and checkout validation pass. An hourly schedule checks one configured path, not every product or customer scenario.
SamSiyu configures independent email delivery for hosted pilot accounts. The optional WordPress mail relay is a fallback: it depends on your store’s mail and cron working. A mail-provider handoff does not guarantee inbox delivery.
Understand the states
- Healthy
- Recent telemetry and a passing configured journey, with no active incident.
- Confirming
- A failed check awaits the fresh-session retry.
- Failed / warning
- A confirmed path failure or a store-health condition needs attention.
- Blocked / stale
- The monitor could not verify the path, or health reports stopped arriving. This is not a healthy result.
- Paused / maintenance
- New browser checks are suspended by your setting.
Useful controls
Edit checks changes the product, interval, device viewport, shipping details and order thresholds. Acknowledge records that you have seen an incident; it does not repair the store. Replace connection secret invalidates the old pairing and requires updating the WordPress plugin.
Disconnect and remove
Pause the store in the dashboard and disable monitoring in WordPress. Deactivation clears the plugin’s scheduled task. Uninstall removes plugin settings without deleting orders. Contact support to delete the hosted store/account data.
Troubleshooting
- No health reports: confirm the server URL, store URL, pairing secret, system clock and WordPress cron. Low-traffic sites need reliable cron scheduling from their host.
- Bot challenge: review your firewall with support. Do not disable your firewall globally.
- Wrong gateway: confirm the gateway ID and whether it is offered for the selected cart/address.
- Shipping failure: verify product type, shipping zones, destination and available rates.
- Email missing: review Alert delivery in the dashboard and check spam folders.