Connection Checklist

1. Open https://your-store.example/wp-json/ and confirm WordPress returns REST API JSON.
2. Confirm the site URL uses a valid HTTPS certificate and matches WordPress Address and Site Address.
3. Temporarily inspect firewall, security-plugin, CDN, and host logs for blocked requests to the OrderTrackify API or /wp-json/ordertrackify/v1/.
4. Resave Settings → Permalinks if WordPress routes return 404.
5. Verify the connecting user can manage WooCommerce.

Brief Service Interruptions

Short-lived gateway errors can occur while OrderTrackify is being deployed. The plugin performs a bounded retry and arranges an automatic follow-up check for a transient network or server response. It keeps the store's last verified connection unchanged during that window, and WordPress never displays a raw proxy or CDN error response. No reconnect action is needed unless a later check reports a persistent authentication or configuration problem.

First-connection Verification

A successful health or heartbeat response includes the connected store identity together with a complete plan, usage, quota, and shipment-access snapshot. If a rolling deployment briefly returns only part of that contract, the plugin keeps the new connection in verification and checks again instead of showing unavailable plan or allowance details. Do not reconnect unless verification later reports a persistent authentication or configuration problem.

Connected but Stale

The plugin sends scheduled and administrator-triggered heartbeats. The SaaS classifies the connection as healthy within two hours, delayed after two hours, stale after six hours, and disconnected after 24 hours without a heartbeat. Check WP-Cron and outbound HTTP if the connection ages while the plugin still shows a key.

Reconnect Safely

Disconnecting clears the local plugin credential but does not erase historical SaaS shipments. Reconnect after changing the WordPress site address, moving the store to another domain, or cloning it into a new environment; authenticated plugin requests are bound to the connected site URL. Start the connection flow again, then use an administrator refresh or wait for the next scheduled heartbeat.