StoreFence

No. Order notes added by the plugin are private, and nothing is added to emails or the customer's account. They only see your checkout message. In Pro, a soft-blocked customer just sees fewer payment methods.

The free version blocks checkout for every entry you add one by one (a Hard block). Pro adds Soft and Fraud / Abuse levels, bulk import, and blocking straight from an order.

They stay in your list. Fraud entries keep blocking checkout, with your regular checkout message. Soft entries have no effect until Pro is active again, because payment-method restrictions are a Pro feature. Your Pro settings are kept.

None of the payment methods selected under Soft block payment methods are enabled in WooCommerce. Select at least one enabled method; the settings page warns you when this happens.

Before saving and before every lookup, numbers are normalized to +<country code><number>. Formatting characters are ignored, and 00385… is treated as +385…. A number without a country code, such as 091 234 5678, gets your store's base country code and loses its leading 0. A number that can't be read as 7–15 digits is rejected when you add it.

The strictest level wins: Fraud, then Hard, then Soft.

One customer per line: an email, a phone number, or both, separated by a comma, semicolon or tab. A line with both becomes one entry. Header rows and other text, such as names, are ignored. Duplicates and invalid values are skipped and listed after the import. john@example.com, 091 234 5678 jane@example.com +385 98 765 4321

Yes. On the order edit screen, choose Blocklist customer: Soft / Hard / Fraud under Order actions and click Update. The billing email and phone are added as one entry linked to the order, and a private order note records the result.

Users with the manage_woocommerce capability, which by default means Administrators and Shop Managers. To let another role in, use the devnet_storefence_capability filter. It runs per area: entries (the StoreFence page: add, edit, delete, bulk import), order_actions (blocking from an order) and settings (the General Settings). For example, entries and order actions for a custom role, settings for Shop Managers only: add_filter( 'devnet_storefence_capability', function ( $capability, $area ) { return in_array( $area, array( 'entries', 'order_actions' ), true ) ? 'my_custom_capability' : $capability; }, 10, 2 ); Blocking from an order also needs WooCommerce's own permission to edit orders.

Yes, with the devnet_storefence_blocklist_soft_gateways filter. It receives an array of gateway IDs: add_filter( 'devnet_storefence_blocklist_soft_gateways', function ( $gateways ) { $gateways[] = 'my_card_gateway'; return $gateways; } );

The blocked emails and phone numbers, the level, an optional internal reason, the ID of the admin who added the entry and, when blocked from an order, the order ID. Everything is stored in the plugin's own tables in your own database ({prefix}devnet_storefence_subjects and {prefix}devnet_storefence_subject_identifiers for the emails and phone numbers, {prefix}devnet_storefence_blocklist for the entries), and the blocklist is never sent anywhere. Emails and phone numbers are personal data, so cover the blocklist in your privacy policy. The plugin uses the Freemius SDK for licensing and updates. Freemius only collects site and usage information if you opt in when asked after activation, and never your blocklist.