Description
Every refused or fake cash-on-delivery order costs you shipping both ways. Takeed Refusal Guard is a COD blacklist built from your own orders: it remembers who refused a parcel, and uses that memory as an anti-fraud check when the same person orders again.
How it works
- Mark an order as Refused at delivery (a new order status, also available as a bulk action in the orders list). You can also choose other existing statuses that should count as a refusal.
- The plugin stores the customer’s phone number (normalised) and e-mail address in its own table on your site.
- At the next checkout, if the phone number or the e-mail has at least the number of refusals you set (default: 1), the plugin applies the action you chose:
- Tag only (default): an order note and the order meta
_takrg_risk. Nothing is blocked, nothing is hidden. Safe to try on a live shop. - Hide Cash on Delivery for that customer. Other payment methods stay available.
- Show a neutral notice asking the customer to choose another payment method.
- Tag only (default): an order note and the order meta
Safe by design (new in 1.1)
- Test mode is the default on a new installation. Orders are only tagged, and an activity log shows what the plugin would have done. Switch to Live when the log looks right.
- Safety breaker. If more than 50% of the checkout attempts in an hour are restricted (and there are at least 5 attempts), the plugin returns to “tag only” by itself and tells the administrator. It stays there until you turn it back on.
- Fail-open. If anything goes wrong while the plugin checks a customer, the order goes through.
- Allow-list. Customers you trust are never touched, whatever their refusals.
What makes it different
- Arab and North-African phone formats built in: Tunisia (+216), Morocco (+212), Algeria (+213), Egypt (+20), Saudi Arabia (+966), UAE (+971), Kuwait (+965), Qatar (+974), Oman (+968), Bahrain (+973).
20 123 456,+216 20123456,00216-20-123-456and٢٠ ١٢٣ ٤٥٦are the same customer. A “default country” setting reads numbers typed without a country code. - Safe by default: the default action only tags the order. The plugin never silently blocks a customer.
- Works with the classic checkout and the block checkout (Store API), and with both order storages: HPOS (custom order tables) and the legacy posts storage.
- Free, no SMS or OTP cost, no account, no external service, no upsell, no ads.
- Arabic-friendly: the admin screens use standard WordPress components and mirror correctly in right-to-left languages. Phone and e-mail fields are always left-to-right.
Also included
- A COD risk column in the orders list (legacy and HPOS screens) showing the refusal count of the customer.
- Block-list and patterns: add an e-mail, a phone number or a pattern such as
*@example.comor+21620*. - Order actions on the order screen: mark as refused, or clear a refusal that was a mistake.
- Count refusals from existing orders with one click, and forget old refusals automatically after a number of months you choose.
- Activity log of the last 500 events, with customers masked.
- Settings under WooCommerce > Refusal Guard: threshold, action, counted statuses, default country, add or remove numbers by hand, CSV import and export.
- WordPress personal data exporter and eraser for the stored records.
- Hooks for developers (see the FAQ), so other plugins, such as Takeed order confirmation, can count their own signals.
Privacy
This plugin stores, in a table of your own WordPress database, for every order that was refused at delivery: the phone number (digits only), the e-mail address (lowercase), the order number and the date. Records can also be added by hand or imported by CSV.
- Nothing is sent to the plugin author or to any third party. The plugin makes no external HTTP requests.
- The records are included in the WordPress personal data export (Tools > Export Personal Data) and removed by the erasure tool (Tools > Erase Personal Data), matched by e-mail address and by the phone numbers tied to it.
- A suggested paragraph is added to your privacy policy page (Settings > Privacy).
- The activity log shows customers masked (the first and last digits of a phone number; the first letter and the domain of an e-mail address). Allow-list and block-list entries are included in the export and the erasure when they are exact matches of the person.
- With “Forget refusals after (months)” you choose how long records are kept; the default keeps them until you delete them.
- Deleting the plugin removes its tables (refusals, rules, log) and its options.
Installation
- Install and activate WooCommerce, then this plugin.
- Go to WooCommerce > Refusal Guard and check the default country and the action.
- When a parcel is refused, change the order status to Refused at delivery.
FAQ
Does it block customers?
Only if you choose so, and only cash on delivery. The default action only adds an order note and the meta _takrg_risk, so a wrong match never stops a sale. The other two actions remove or refuse Cash on Delivery for that customer; every other payment method keeps working.
Can it block fake orders?
It targets repeat fake and refused cash-on-delivery orders: once an order is marked as refused, the same phone number or e-mail is recognised on the next order, in any phone format. It is not a general firewall: it does not score IP addresses, devices or card payments.
Is it a blacklist?
Yes, for cash on delivery. The list is filled automatically from refused orders, and you can also add or remove numbers and e-mails by hand or by CSV (import and export are free).
Which customers are recognised?
Same phone number (in any format, see above) or same e-mail address. A person who gives a new e-mail but the same phone number is still recognised.
How does Hide Cash on Delivery work with the block checkout?
Cash on Delivery is removed through the woocommerce_available_payment_gateways filter, which the Store API also uses, and it is refused again when the order is submitted. In the block checkout the customer sees the message when they try to place the order; in the classic checkout the payment method disappears (or the notice appears) as soon as the phone number or the e-mail is entered, through a one-line inline script that loads no file and contacts no server.
A customer cancelled by mistake. How do I fix it?
Change the order out of the counted status and its record is removed. You can also delete a record, or every record of a phone number or e-mail, in the settings page.
Can I import my existing list?
Yes. WooCommerce > Refusal Guard > Import CSV. One row per refusal: phone,email (the header row is optional). Numbers without a country code use the default country. Export gives the same columns plus order, source and date.
Which hooks are available?
do_action( 'takrg_signal', $phone, $email, $order_id, 'takeed' )records a refusal signal from another plugin. The functiontakrg_record_refusal( $phone, $email, $order_id, $source )does the same.apply_filters( 'takrg_refusal_count', $count, $phone, $email )adds signals to the count (for example, Takeed confirmation results).apply_filters( 'takrg_is_risky', $risky, $count, $phone, $email )overrides the decision.apply_filters( 'takrg_counted_statuses', $statuses )changes the statuses that count as a refusal.do_action( 'takrg_refusal_recorded', $id, $row )anddo_action( 'takrg_order_tagged', $order, $count ).
There is no hard dependency between this plugin and any other Takeed plugin.
What is the safety breaker?
A circuit breaker against mistakes. If more than half of the checkout attempts of the last hour were restricted (with at least 5 attempts, and one customer counted once), something is wrong, for example a rule that is too wide. The plugin then only tags orders, shows a notice in the admin and sends the administrator an e-mail (through your own mail setup). The restriction comes back only when you press “Turn protection back on”. The attempt that trips the breaker is still restricted; from the next checkout on, Cash on Delivery is available again.
What happens if the plugin fails during checkout?
The order goes through. Any error while checking a customer lets the order continue, and the error is written to the activity log.
I update from 1.0. Will my shop change?
No. Sites that already used 1.0 keep the action they chose and stay in Live mode. Only new installations start in Test mode.
Does it send data anywhere?
No. There are no external HTTP calls, no tracking and no analytics.
Screenshots
Changelog
1.1.0
- New installations start in Test mode: orders are tagged and an activity log shows what the plugin would have done.
- Safety breaker: more than 50% of the checkout attempts in an hour (at least 5) returns the plugin to “tag only” and notifies the administrator.
- Fail-open: any error while checking a customer lets the order through.
- Allow-list, block-list and wildcard patterns (e-mail and phone prefix).
- Order screen actions: mark as refused, clear a refusal. Bulk action unchanged.
- Count refusals from existing orders. Optional retention in months. Activity log with masked customers.
- Privacy exporter and eraser include allow-list and block-list entries.
- Sites updating from 1.0 keep their action and stay in Live mode.
1.0.0
- First release.



