Engineering Notes
Practical analysis of WooCommerce checkout, payments, integrations, data, performance and production reliability.
Latest analysis
When WooCommerce has the order but an ERP or fulfilment system does not, trace eligibility, discovery, processing, destination acceptance and identity mapping before replaying anything.
Read the Engineering NoteA slow WooCommerce Orders screen is not one performance problem. Separate list, search, open, save and bulk requests, then attribute latency to database work, PHP, extensions, remote APIs or the browser.
Read the Engineering NoteWhen a WooCommerce webhook appears to fire twice, first prove what actually repeated. Then protect the downstream business operation with atomic idempotency, durable state and reconciliation.
Read the Engineering NoteWhen WooCommerce scheduled actions remain pending, past-due or failed, the queue count is not the diagnosis. Measure age, throughput, arrival rate and failure concentration, then recover the underlying business work deliberately.
Read the Engineering NoteWhen a WooCommerce database keeps growing, shrinking it is not the first job. Compare table deltas, identify the process producing the data, verify retention, and prove the growth rate returns to normal.
Read the Engineering NoteWhen WooCommerce checkout works for some customers but fails for others, treat successful attempts as controls. Compare sessions, requests, logs and order state to find the first point of divergence.
Read the Engineering NoteWhen a payment gateway shows a successful transaction but WooCommerce has no usable matching order or still considers the order unpaid, the problem is transaction reconciliation. Here is how to reconstruct the failure path safely.
Read the Engineering Note