During the week of 2025-12-12, Doodla Farms reported 2–3 instances of duplicate orders being placed through their WooCommerce store. The issue was investigated by Eshock, who identified a likely network/payment gateway timing problem and applied preventive fixes.
This incident occurred in the same window as a broader [1] caused by bot traffic to the Village of Maple Bluff site, which was generating 500 gateway errors across the shared server. The two issues may be related.
No definitive root cause was confirmed. Eshock's assessment:
"He couldn't find any valid reason for the orders being duplicated. It could have been due to a network issue with the payment gateway."
The working hypothesis is that a slow or interrupted response from the payment gateway caused the checkout to be submitted more than once — a known failure mode when the checkout page is cached and the browser retries a stalled POST request.
The concurrent server-level 500 errors (caused by bandwidth spikes from bot traffic) may have contributed to the gateway timeouts that triggered the duplicate submissions.
Eshock made two changes to prevent recurrence:
These are standard mitigations for WooCommerce duplicate order scenarios and do not require further client-facing action.
Checkout page caching should be explicitly disabled on all WooCommerce stores hosted on shared infrastructure. When a server is under load and gateway responses are slow, cached checkout pages create conditions for duplicate POST submissions. This should be part of the standard WooCommerce setup checklist.
Checklist item to add: After any WooCommerce installation or plugin update, confirm that the checkout, cart, and account pages are excluded from page caching rules.
Discussed in weekly ops call with Karly Oykhman and Mark Hope, 2025-12-12.