What Amity Tech Store Audit Checks—and What It Does Not Certify
What the 84 checks cover
Amity Tech Store Audit for WooCommerce reviews a WordPress and WooCommerce baseline, catalog and product data, shipping zones and methods, visible payment configuration, tax configuration, email configuration, and operational readiness signals. Findings should be read with their severity and explanation; some require action before launch, while others are prompts to review the store against its actual business model.
Current development status
Version 0.7.0 has completed initial scanner and report-rendering tests, including installation from a generated buyer ZIP. It has not completed the full product test matrix, public documentation deployment, or an independent release audit. It must not yet be described as release-ready.
What read-only means
The plugin reads the configuration required to produce findings. It does not modify products, orders, or store settings; create test orders; charge real money; or contact payment services on the user’s behalf. This reduces the risk of running an audit against a live store, but it also means some outcomes require real human testing.
What the audit does not certify
It does not prove that live payments will succeed for every enabled bank, card, or payment method.
It is not legal, tax, security, or PCI certification.
It does not guarantee that email will reach every recipient’s inbox.
It does not replace end-to-end checkout, refund, fulfilment, shipping, and back-office workflow tests.
It does not guarantee that every theme and plugin combination will behave correctly in every environment.
How to use the report
Address high-impact findings first, scan again, and compare the results before and after each change. Convert everything outside the tool’s read-only scope into a human test plan: place an order, send email, reduce inventory, fulfil and ship, then issue a refund.
When sharing a report, include the WordPress, WooCommerce, and Amity Tech Store Audit for WooCommerce versions, the scan date, and the environment. A score is a starting point—not a release decision.