Description
Sooner or later every WooCommerce store gets them. Orders from names that are just random letters. A burst of checkouts testing stolen card numbers. Sign-ups from addresses that disappear an hour later. Each one lands in your orders list, sends you an email and throws off your reports.
OrderSieve looks at every checkout before the order is placed and turns away the ones that were clearly not made by a person, or that come from someone you have already blocked. The checks run in the background, so your customers check out exactly as before. The recommended settings are on as soon as you activate the plugin, and you can fine-tune them from one settings page.
OrderSieve requires WooCommerce 8.0 or later.
What it checks
- A hidden field. The checkout form gets an extra field that people never see. Bots that fill in every field give themselves away. It works on both the classic and the block checkout.
- How fast the checkout was. A person needs a few seconds at least to fill in a checkout form. Checkouts submitted faster than that, 3 seconds by default, are turned away. On the classic checkout the start time is signed and tied to the shopper’s session, so it cannot be forged or reused. On the block checkout it is the moment the shopper first added something to the cart.
- The email address. Addresses from throwaway providers such as mailinator.com or temp-mail.org are rejected, along with any subdomain of them. You can add your own domains to the list.
- How many orders come from one place. Card testers place order after order to find out which stolen card numbers work. Each IP address and each email address may place 10 orders an hour by default. Past that, checkouts from them are turned away until the hour is up.
- How many payments failed. After 5 failed payments in an hour from the same IP address or email address, further checkouts from them are turned away. This counts orders your payment gateway marks as Failed.
- Your own block lists. Block IP addresses and ranges, email addresses and domains, and billing countries. From the logs screen you can block the IP address or email of any blocked attempt with one click. Entries that can never match, such as a mistyped address, are pointed out on the settings screen.
- Fake-looking names (optional). Turn this on to reject billing names with a web address or digits in them, strings like “xkqjzv” or “asdfghjkl”, or the same first and last name. It is off by default, and names written in other scripts or with accents are never judged on their spelling.
Let trusted customers through
IP addresses on your allow list, such as your office, skip every check. So do logged-in customers whose account email is on your allow list, which is handy for wholesale buyers who place many orders. The allow list uses the account email, not the email typed at checkout, so nobody can get past the checks just by typing an allowed address.
What happens to a blocked checkout
The shopper sees your rejection message and the order is not placed. On the classic checkout no order is created at all. On the block checkout the check runs before WooCommerce creates a customer account, holds coupons, reserves stock or takes payment. The unfinished order is cancelled and gets a note with the reason, and you are not sent a “Cancelled order” email about it.
With logging on, which is the default, every blocked attempt is logged with the reason, the email address entered and the IP address.
It fails on the safe side
When OrderSieve cannot tell how long a checkout took, for example for a shopper whose cart was started before the plugin was activated, it lets the order through. A lost sale costs more than a stray junk order, so the time check only ever blocks when it is sure.
Keep an eye on what was blocked
WooCommerce → OrderSieve Logs shows the 100 most recent blocked attempts, with the time, the reason, the email address and the IP address. Each entry has buttons to add its IP address or email to your block list. The same entries are in WooCommerce → Status → Logs under the source ordersieve, whether WooCommerce writes its logs to files or to the database. From the logs screen you can clear the log or run the junk order cleanup straight away.
Clean up junk orders
Blocked block-checkout orders stay in your orders list as cancelled. If you would rather not keep them, turn on the cleanup. Once a day, through WooCommerce’s Action Scheduler, it deletes orders that OrderSieve blocked and that are older than the number of days you choose, in batches of 50 until none are left, so even a large backlog after an attack clears quickly without slowing your site. Orders OrderSieve did not block are never touched, including ones you cancelled yourself. The cleanup is off by default.
What you can adjust
Everything lives on one page under WooCommerce → OrderSieve Settings:
- Turn all checks on or off.
- The minimum time a checkout must take, from 0 to 60 seconds. 0 turns the time check off.
- Whether to block throwaway email providers, and your own list of extra domains, one per line.
- Whether to block fake-looking names.
- Where the visitor’s IP address is read from: the connection itself, or the header set by Cloudflare or another proxy in front of your site.
- The most orders and the most failed payments allowed per IP address or email, and the time window they are counted over. 0 turns either limit off.
- Blocked IP addresses, email addresses and billing countries, and allowed IP addresses and customer accounts.
- The message a blocked shopper sees. Leave it empty and shoppers get the default message in their own language.
- Whether blocked attempts are logged.
- How many days to keep blocked orders before the cleanup deletes them, from 0 to 365. 0 turns the cleanup off.
For developers
Filters let you add domains to the block list, change the rejection message, allow-list shoppers, change how names are judged, or skip the time check, for example on a store that relies on one-click express payments. An action fires on every blocked attempt, so you can count attempts or alert someone. The available hooks are listed in the FAQ below.
Privacy
OrderSieve runs entirely on your own server. It does not call out to any service, load anything from a CDN, collect usage data or set cookies of its own. The time check stores one timestamp in the shopper’s existing WooCommerce session. The order and failed payment limits keep short-lived counts in a single database option, stored under a one-way hash of the IP address or email address that is salted with your site’s secret keys, and each count is removed once its time window ends. When an attempt is blocked and logging is on, the reason, the email address entered and the IP address are written to your WooCommerce logs, where they stay on your server and follow your WooCommerce log retention setting. OrderSieve also saves the shopper’s IP address on each order, so a failed payment reported later by your payment gateway is counted against the right address; when you erase a customer’s personal data, WooCommerce anonymizes it along with the rest of the order. Suggested text for your privacy policy is added under Settings → Privacy → Policy Guide.
When you delete the plugin it removes its settings, its counts, its scheduled cleanup and its log entries.
Installation
- Install WooCommerce 8.0 or later if it is not already active.
- Upload the
ordersievefolder to/wp-content/plugins/, or install it from Plugins → Add New. - Activate OrderSieve. Protection is on straight away with the recommended settings.
- To change them, go to WooCommerce → OrderSieve Settings.
- To see what has been blocked, visit WooCommerce → OrderSieve Logs.
FAQ
Does it work with the block-based checkout?
Yes. Every check works on the block checkout. The hidden field is added there by a small script that loads with the checkout block. A request that does not include the field, such as one sent straight to the Store API, is still screened by all the other checks.
Will real customers be blocked?
It is very unlikely. The automatic checks look for machine behaviour: people do not see the hidden field, take longer than a few seconds to check out, rarely use throwaway email addresses, and do not place 10 orders or fail 5 payments within an hour. The fake name check, which could catch an unusual real name, is off until you turn it on. Every blocked attempt is logged so you can review it, and the rejection message can tell shoppers how to reach you.
Will customers on a shared network hit the order limit?
Shoppers behind the same office or mobile network can share an IP address. The default of 10 orders an hour leaves plenty of room for that. If your store gets many orders from one place, raise the limit, or add the IP address to the allowed list.
Which payment gateways does the failed payment limit work with?
It counts orders that your payment gateway moves to the Failed status. Many card gateways do this when a payment is declined. If yours does not, the order limit still stops a burst of attempts.
Does it work behind Cloudflare or another proxy?
Yes, once you tell it which header your proxy uses. By default OrderSieve reads the IP address the connection comes from, which a visitor cannot fake. Behind Cloudflare, a load balancer or another proxy, that is the proxy’s address, so under WooCommerce → OrderSieve Settings → Visitor IP address choose the header your proxy sets: CF-Connecting-IP for Cloudflare, or X-Forwarded-For or X-Real-IP for most others. The setting shows the IP address OrderSieve currently sees for you, and OrderSieve warns you on its screens when your site looks like it is behind a proxy.
Only choose a header your proxy really sets. On a site without one, anyone can send these headers and pretend to have any IP address, including one on your allowed list.
A private address such as 10.0.0.5 is never counted against the order and failed payment limits, so a proxy on your own network cannot make all your shoppers share one limit. Those orders are still limited per email address.
IPv6 addresses are counted per /64 network, the block of addresses one connection usually gets, so a bot cannot get around the limits by switching to another address in the same network.
Where can I see blocked attempts?
Go to WooCommerce → OrderSieve Logs. It lists the 100 most recent blocked attempts and cleanup runs. The same entries are under WooCommerce → Status → Logs with the source ordersieve.
Will I get emails about blocked orders?
No. On the classic checkout no order is created. On the block checkout the unfinished order is cancelled without sending the “Cancelled order” email.
Does the cleanup delete real orders?
No. It only deletes orders that OrderSieve blocked and flagged, older than the number of days you set, 50 at a time. Orders you cancelled or trashed yourself are never touched.
Does it work with page caching or a custom checkout template?
Yes. If a cached or custom checkout page is missing the signed start time, or it does not match the shopper’s session, OrderSieve uses the age of the shopper’s WooCommerce session instead of blocking the order.
What about express checkout (Apple Pay, Google Pay)?
Express checkout can be very quick, so now and then a one-click payment may beat the minimum time. If that happens on your store, lower the minimum time, set it to 0, or turn the time check off with a filter:
add_filter( 'ordersieve_run_time_trap', '__return_false' );
How can I test that it works?
Add a test domain such as example.com under WooCommerce → OrderSieve Settings → Email check → More domains to block, then place a test order with an @example.com email address. The order is rejected and the attempt shows up under WooCommerce → OrderSieve Logs. Remove the test domain afterwards.
Can I block more email domains from code?
Yes, with the ordersieve_disposable_domains filter. Subdomains of each domain you add are blocked too:
add_filter( 'ordersieve_disposable_domains', function ( $domains ) {
$domains[] = 'example.com';
return $domains;
} );
Which hooks are available for developers?
ordersieve_run_time_trap(filter) –bool $run. Return false to skip the time check.ordersieve_disposable_domains(filter) –string[] $domains. Lowercase domains to block.ordersieve_block_message(filter) –string $message. The message shown to a blocked shopper.ordersieve_client_ip(filter) –string $ip,string $source. The shopper’s IP address used for every check.ordersieve_is_allowlisted(filter) –bool $allowed,array $data. Return true to let a checkout skip every check.ordersieve_is_gibberish_name(filter) –bool $gibberish,string $first_name,string $last_name. Change whether a name counts as fake.ordersieve_blocked(action) –string $reason,string $email,array $data. Fires whenever an attempt is blocked. The reason ishoneypot,time-trap,disposable-email,blocked-ip,blocked-email,blocked-country,card-testing,rate-limitorgibberish-name.$dataholds the email, IP address, billing country and billing name.
What happens if I deactivate the plugin?
Checkouts are no longer screened and the daily cleanup stops. Your settings and logs are kept, so everything picks up where it left off when you turn it back on. Deleting the plugin removes its settings, scheduled cleanup and log entries.
Does the plugin connect to any external service?
No. See the Privacy section above.
Screenshots




Changelog
1.1.0
- New name: OrderSieve – Fraud & Fake Order Blocker for WooCommerce.
- New: order rate limiting and card testing protection per IP address and email.
- New: block lists for IP addresses, emails and countries, and an allow list for trusted IPs and customer accounts.
- New: honeypot protection for the block checkout.
- New: optional fake name check.
- New: one-click “Block IP” and “Block email” buttons on the logs screen.
- New: choose where the visitor’s IP address is read from, for sites behind Cloudflare or another proxy. By default only the connection address is trusted, so a visitor cannot fake an IP address with a header.
- New: list entries that can never match are pointed out on the settings screen, and text after a # is a comment.
- New: OrderSieve Settings and OrderSieve Logs pages in the WooCommerce menu, replacing the WooCommerce settings tab and the Tools page. Old links redirect.
- Improved: a much faster logs screen, and a junk order cleanup that clears large backlogs.
- Improved: IPv6 addresses are counted per /64 network, so a bot cannot get past the limits by rotating addresses.
- Improved: erasing a customer’s personal data also anonymizes the IP address OrderSieve saves on their orders.
- Fixed: IPv4 visitors that the server reports in IPv6 form (::ffff:203.0.113.7) now match IPv4 entries in the block and allow lists.
- Fixed: the entry count under each list on the settings screen now matches how the list is read.
1.0.0
- Initial release.
