Bring your store
Share your store URL and setup when early access opens.
Your plugins change.
Keep an eye on them.
A closer watch on the plugins, themes, and customer data that make your WooCommerce store yours.
Early access. Join the list for the first release.
Plugins & themesCheckout scriptsCustomer access
WooCommerce security, in one place.
Product concept for the upcoming integration. Illustrative data.
Planned coverage
Built around your WordPress stack.
We’re building checks for the code you install, the changes you ship, and the data your store handles.
Know which files changed. And when.
A plugin update and an unexpected edit can look similar from the storefront. A file baseline gives you a clearer place to start.
- Changes to monitored plugin and theme files
- Injected code and unfamiliar files
- Evidence tied to the affected component
Example signalReview
A plugin file no longer matches.
wp-content/plugins/harbor-invoice-tools/export.php- Before
- Approved baseline · version 041
- Observed
- Current file · hash changed
Compare with the approved release before deciding what to restore.
Illustrative example · Synthetic dataFollow the code around checkout.
Themes, payment extensions, and custom snippets all meet here. Keep track of scripts and the destinations they contact.
- Scripts added to cart and checkout flows
- Unexpected external destinations
- Changes after a plugin or theme release
Example signalReview
Checkout loads a new external host.
/checkout/ · script inventory- Before
- Approved script sources
- Observed
- New host: unexpected.test
Check the plugin or theme change that introduced this destination.
Illustrative example · Synthetic dataAn order should belong to its customer.
Test the access boundaries around custom endpoints and account flows using dedicated identities and synthetic records.
- Order and account data exposed across users
- Overly broad integration permissions
- Custom REST routes with missing access checks
Example signalReview
An order crosses account boundaries.
GET /wp-json/harbor/v1/orders/1042- Before
- Signed in as Customer A
- Observed
- Customer B’s test order returned
Enforce ownership at the server boundary, then retest both accounts.
Illustrative example · Synthetic dataA useful check. A clear next step.
The workflow we’re building, from a defined scope to useful evidence.
Build your baseline
Connect the supported components and review what is in scope.
Work from the evidence
See the changed file or affected route, review the fix, and check again.
Early accessGet a note
Get a note
when it’s ready.
Leave your email for rootscan for WooCommerce. Add your store URL so we know what you’re building on.
Product updates, when there’s news.No store credentials needed.
Need app testing today? Get early access
We’ll let you know when it’s ready.
Before you
get started.
A few details, in plain language.
Can I use it today?
The dedicated WooCommerce product is coming soon. Join the early-access list to hear when it is ready. Core application and API testing is available separately.
Is this for WooCommerce or WordPress?
This page focuses on WooCommerce stores, including the WordPress plugins and themes they depend on. If you run a WordPress site without a store, you can also register interest through the WordPress page.
Will it replace backups and plugin updates?
No. Keep your backups, updates, hosting protections, and access controls. rootscan is being built to add evidence about suspicious changes and application behavior.
Which plugins will be supported?
Compatibility and connection requirements will be published with early access. Add your store URL to help the team understand your setup; do not send credentials.
What will it cost?
WooCommerce pricing has not been announced. Joining the list does not start a subscription.
