Amity Tech Store Audit for WooCommerce Documentation

Amity Tech Store Audit for WooCommerce by Amity Tech — Version 0.7.0

1. Introduction

Amity Tech Store Audit for WooCommerce is a read-only WooCommerce auditing plugin. It identifies and explains store configuration and catalog issues before launch, handoff, takeover, or maintenance work.

Amity Tech Store Audit for WooCommerce is developed by Amity Tech. The legal entity is Amity Tech Co., Ltd. (บริษัท แอมมิตี้ เทค จำกัด), Thailand.

Amity Tech Store Audit for WooCommerce reads, analyzes, and reports. It does not automatically repair or operate the store.

2. Requirements

3. Installation

  1. In WordPress, open Plugins and select Add New Plugin.
  2. Upload the Amity Tech Store Audit for WooCommerce installation ZIP.
  3. Select Install Now, then activate Amity Tech Store Audit for WooCommerce.

4. Activation

Activation creates only the default Amity Tech Store Audit settings and version option. It does not scan the site, contact a remote service, or change WooCommerce data.

If WooCommerce is unavailable, Amity Tech Store Audit remains accessible and explains that WooCommerce-dependent checks cannot run.

5. Quick Start

  1. Open WooCommerce > Amity Tech Store Audit.
  2. Alternatively, open Plugins and select Run Scan below Amity Tech Store Audit.
  3. Select Run Scan.
  4. Review Critical findings first, followed by Warnings and Review items.
  5. Use Open settings to navigate to the relevant WordPress or WooCommerce screen.
  6. Make changes manually outside Amity Tech Store Audit.
  7. Run the scan again to refresh the report.

6. Dashboard

The dashboard displays the Store Health Score, result totals, evidence, recommended manual actions, safe navigation links, and changes since the previous scan. Select a status summary card to show only matching findings, select Ignored to review alert suppressions, or select All Status to restore every finding. Use Sort findings to order the visible table by checklist order, severity, change type, category, or check name. Sorting works with the active filter and does not rerun the scan.

History and change detection

Open the History tab to review the 20 most recent manual, scheduled, and WP-CLI scans. The first stored scan is a baseline. Later scans mark findings as new, worsened, improved, resolved, or unchanged.

Trend and informational target

After two valid scans, the dashboard shows the stored Store Health Score as a line and Critical-finding count as bars. Manual, scheduled, and WP-CLI scans use distinct markers. The chart uses the actual stored scan times and does not recompute historical scores.

An optional target from 1 to 100 can be displayed as a visual maintenance reference. It does not alter the score, findings, change detection, or alerts and is not an SLA, security result, availability promise, or launch-readiness guarantee.

Ignoring an alert

For an intentional Critical, Warning, or Review finding, expand Ignore alert, optionally enter a note, and confirm. Ignore suppresses future background email alerts for that check only. It does not change the finding, evidence, exported report, or Store Health Score. Select Restore alerts to reverse the suppression.

Background alerts

Background alerts are disabled by default. Open the Amity Tech Store Audit Settings tab, enter up to five recipient addresses, then create and enable as many as five Daily or Weekly jobs. Each job has its own whole-hour time in the WordPress site timezone and a weekday for Weekly schedules. Identical schedules are stored once. All jobs share the recipients, alert baseline, ignored checks, and bounded history.

Scheduled scans use WordPress Cron. WordPress Cron depends on site traffic unless the host configures a real server cron runner. The displayed next-run time is therefore an expected target, not a delivery guarantee.

Email remains plain text and contains only an optional agency-name identity line, finding titles, statuses, change types, and a link to the Amity Tech Store Audit administration page. Customer, order, payment, credential, logo, remote-image, and finding-evidence data is excluded.

Open the Test Email tab and select Send Test Email to send current non-ignored Critical and Warning titles from the latest stored scan to the saved recipients. Save recipient changes first. The result remains visible inside the Test Email tab. The test does not run a scan or change the alert baseline. A success notice means WordPress accepted the request, not that the message reached an inbox.

7. WP-CLI

WP-CLI is treated as a trusted server-shell context and is loaded only when WP-CLI is present. The commands do not require a WordPress user by default.

JSON output uses a versioned, allowlisted public schema. Redirect CSV or HTML output to a file when needed. Findings can reveal privileged store configuration, so protect generated files and CI logs. A successful command does not mean every finding passed; operational success and finding severity are separate.

8. Audit Categories

9. Severity Definitions

Critical
A condition likely to block an important store function or create a serious customer-facing problem.
Warning
A configuration or data issue that should normally be corrected or confirmed.
Review
A decision Amity Tech Store Audit cannot determine automatically and a person must verify.
Passed
The expected automated condition was detected.
Not applicable
The check does not apply to the current store configuration.

10. Reports

Use Amity Tech Store Audit Settings to add an agency name, same-site agency logo URL, client name, and report brand color. Reports include the bounded trend and optional informational target. Download HTML creates a standalone report. Download CSV exports structured findings. Print / Save PDF opens a print-friendly report; select Save as PDF in the browser print dialog.

The report intentionally excludes administrator navigation links when prepared for client handoff.

11. Limitations

Amity Tech Store Audit does not replace payment testing, security auditing, legal review, manual checkout QA, accessibility testing, performance testing, email-delivery testing, or professional review of the customer journey.

Version 1 does not promise compatibility with third-party product types, checkout plugins, gateways, shipping providers, custom fields, themes, page builders, or custom WooCommerce implementations.

Amity Tech Store Audit does not provide SEO, tax, accounting, or legal advice. It does not inspect third-party SEO or SMTP-plugin configuration. A different sender domain or supported tax setting may be intentional and is reported conservatively.

A successful wp_mail() result means WordPress accepted the message for processing. It does not prove SMTP connectivity, delivery, inbox placement, or that a recipient read the alert.

12. Troubleshooting

WooCommerce checks are not applicable

Confirm that a supported version of WooCommerce is installed and active.

The scan does not complete

Repeat the scan on a staging site with WordPress debugging enabled and review the server PHP error log. Large catalogs are paginated, but restrictive hosting execution limits can still interrupt a long request.

The agency logo is removed after saving

Use an HTTPS image URL hosted on the same WordPress site. External image hosts are intentionally rejected.

A scheduled scan ran late

Confirm that WordPress Cron is enabled and that the site receives traffic. For predictable execution, ask the host to configure a real server cron job that invokes WordPress Cron.

No alert email arrived

Confirm that at least one job is enabled, at least one valid recipient is saved, and the Amity Tech Store Audit Settings tab shows a next-run time for that job. Amity Tech Store Audit sends only when a Critical or Warning finding is new or worsened. If WordPress accepted the message but it did not arrive, review the site's mail/SMTP configuration with the hosting or email provider.

WP-CLI says no scan is stored

Run wp amity-tech-store-audit scan first. Also confirm that the command is targeting the intended WordPress installation and site in multisite/server automation.

13. Compatibility

The declared minimum versions are WordPress 6.9, PHP 7.4, and WooCommerce 10.8. Compatibility must be confirmed against the exact release and hosting environment before production use.

Amity Tech Store Audit declares compatibility with WooCommerce High-Performance Order Storage (HPOS). It does not access order records or depend on the selected order data store.

Earlier development testing covered the declared minimum stack (WordPress 6.9.5, WooCommerce 10.8.1, and PHP 7.4) and current stacks including WordPress 7.0.2 and 7.0.3 with WooCommerce 11.0.0. The 0.6.0 scheduling changes still require a fresh minimum-stack matrix before release. This does not replace testing on the buyer's exact environment.

14. Support Scope

Support covers reproducible Amity Tech Store Audit defects, documented features, and installation problems caused directly by Amity Tech Store Audit.

Support does not include custom development, theme or page-builder work, hosting/server administration, gateway configuration, shipping-provider setup, third-party plugin configuration, WooCommerce customization, or unrelated WordPress issues.

15. Changelog

0.7.0

Renamed the plugin to Amity Tech Store Audit for WooCommerce with a new slug, text domain, namespace, options, hooks, and WP-CLI command to avoid confusion with an unrelated third-party product.

0.6.1

Added Amity Tech developer attribution and Amity Tech Co., Ltd. legal identification before the 0.7.0 rename, without changing buyer-configurable agency branding.

0.6.0

Added direct Amity Tech Store Audit Settings and Test Email tabs, tab-local test-email feedback, and up to five independently enabled daily or weekly background jobs with automatic migration from the previous schedule.

0.5.0

Added WP-CLI automation, a stable JSON schema, and 12 conservative WooCommerce Core tax, policy, and email-configuration checks for a total of 84.

0.4.0

Added accessible dashboard/report trends, an informational target, simple report color branding, plain-text agency email identity, and site-timezone scheduling controls.

0.3.0

Added bounded scan history, deterministic change detection, finding sorting, alert-only ignore/restore controls, a manual test email, and disabled-by-default scheduled email alerts.

0.2.0

Expanded the read-only checklist from 53 to 72 checks across WordPress, WooCommerce, catalog, shipping, and payment configuration.

0.1.2

Added scan progress feedback and interactive dashboard status filters.

0.1.1

Declared compatibility with WooCommerce High-Performance Order Storage (HPOS).

0.1.0

Initial development version with 53 checks, a deterministic score, dashboard, and HTML/CSV/print reports.

16. Uninstallation

Deactivation preserves all Amity Tech Store Audit data. Uninstallation also preserves data by default.

Deactivation removes every Amity Tech Store Audit scheduled event and preserves settings, scans, history, ignored findings, and alert state. Reactivation restores enabled jobs.

To authorize destructive cleanup, select the permanent-delete checkbox in Amity Tech Store Audit Settings and save before uninstalling. Amity Tech Store Audit then deletes its settings, version option, latest scan, bounded history, ignored findings, alert baseline, and alert status.