# Dropleather compatibility checks

The **Dropleather → Status** page answers one question: does this WordPress
installation meet the minimum requirements for the plugin?

It is intentionally not an operations dashboard. It does not inspect internal
queues, task leases, worker heartbeats, database tables, disk capacity, clock
drift, or accumulated webhook delivery history.

## Checks shown

### Connection

- Dropleather API connection and response time.
- The authoritative WooCommerce REST key exists, belongs to a WooCommerce
  manager, and has read/write permission.
- Both required order webhooks (`order.created` and `order.updated`) are active.

### WordPress requirements

- WordPress, WooCommerce, PHP, and Dropleather plugin versions.
- Effective WordPress/PHP memory: 128 MB minimum, 256 MB recommended.
- PHP request execution time: 30 seconds minimum, 60 seconds recommended.
- HTTPS and outbound TLS support.
- WooCommerce Action Scheduler and its queue runner.
- A writable WordPress uploads directory.
- JPEG and PNG image processing plus MIME detection. WebP is reported when
  available but is not required.

## Cost and privacy

Results are cached for 60 seconds. A normal uncached check makes one
authenticated Dropleather health request, small local reads for the API key and
webhook registrations, and reads local WordPress configuration. It creates no
products, orders, webhooks, media, tasks, or database records.

The report never reads or displays access tokens, refresh tokens, WooCommerce
consumer secrets, bridge secrets, customer data, signed URLs, or filesystem
paths. Remote errors are stripped of known credential formats and limited to
240 characters.