Status and diagnostics

Where to look first when something is off, and what to include in a support request so it can be answered in one reply.

Updated August 2, 2026

WooCommerce → Status

Price Anchor adds a section to WooCommerce’s standard status report. It is the fastest way to see the plugin’s actual runtime state rather than what the settings screen says it should be. It covers:

  • the store currency as WooCommerce reports it;
  • the active rate provider;
  • the age and source of the stored rate table;
  • the current repricing job state;
  • whether the scheduler in use is Action Scheduler or WP-Cron.

Because it lives inside WooCommerce’s own report, it travels with the status export your host or a developer will ask for anyway.

Logs

Price Anchor logs through wc_get_logger(), so entries appear under WooCommerce → Status → Logs alongside everything else. Credentials are redacted before writing — an API key never reaches a log file, a status report or a notification email.

Security-relevant boundary decisions are recorded as stable action, capability, route and object identifiers. Nonces, cookies, authorization headers and request bodies are excluded by design: the log records that a decision happened, not the payload that triggered it. That keeps authorization probing visible without turning the log into a second store of sensitive data.

Admin notices

Warnings render inside the Price Anchor screen, next to the controls they relate to, rather than as global nags on every admin page. WordPress and third-party notices stay in the core notice region above the branded header; Price Anchor’s own action feedback appears directly below its tabs, where the related progress and controls are visible.

What to send with a support request

These four things usually make a support request answerable in one reply:

  1. The WooCommerce status report (it includes the Price Anchor section).
  2. One example product: its ID, its source currency, its source price, and the price you expected versus the price you got.
  3. Whether a page cache or CDN is in front of the site, and whether it was purged.
  4. The relevant lines from the Price Anchor log around the time of the problem.

See Troubleshooting for the checks worth running before you send anything.