StoreOps Auditor for WooCommerce

Description

StoreOps Auditor for WooCommerce helps store owners, developers and agencies identify configuration issues, catalog gaps, checkout concerns and launch verification tasks.

• Cached audit dashboard with weighted store and category scores.
• Configuration checks for WordPress, WooCommerce pages, payments, shipping, tax, email, security, SEO, updates and scheduled actions.
• Catalog scans in batches of 50 products or variations, with counts and links to up to 20 sample parent products for each finding.
• Searchable findings with status and category filters, explanations and recommended actions.
• Persistent manual launch checklist.
• Non-sensitive system report with copy control.
• Compatible with WooCommerce High-Performance Order Storage (HPOS). No order-history queries.

StoreOps audits are read-only with respect to store configuration. Only its own audit results, settings and checklist data are saved. It does not automatically fix settings, update software, send test messages or place orders.

An enabled gateway does not prove a payment works. An enabled email does not prove delivery. Policy-page detection does not establish legal compliance. StoreOps Auditor does not provide legal advice.

Privacy and external services

StoreOps Auditor processes audit information locally inside your WordPress installation. Version 1 does not transmit store information to StoreOps servers. No external account, telemetry or external service is used. Update findings use metadata already stored by WordPress; StoreOps does not refresh it with network requests. WordPress and other installed plugins may independently use external services.

Audit data excludes customer/order records, payment credentials and raw exception messages. System reports contain site addresses and software versions; review the report before sharing it.

Permissions

Users need manage_woocommerce or manage_options. Every action checks permissions and a nonce. Audit data is not exposed through a public API.

Scoring and limitations

Scores begin at 100, deduct 10 for each critical finding and 4 for each warning, and stop at zero. Manual and information statuses do not change the score. Scores are indicators, not certification.

Catalog scanning includes published, private, draft and pending products and variations. New records created after a scan starts are included on the next run. Concurrent catalog changes can affect counts. Duplicate SKU detection uses WooCommerce’s product lookup table, which must be current. Saved results reflect the last completed audit; ordinary page loads do not scan the catalog.

Interrupted audits can be resumed by the administrator who started them. Abandoned sessions expire after one hour. A previous completed report remains available during a new audit. No background scheduled audits run in version 1.