AovUp Rate & Gateway Rules for WooCommerce

Yes. The rules apply on WooCommerce's own available-methods filters, which both the classic checkout and the blocks use.

Add a payment rule: Methods = your invoice or bank transfer method, "Show these methods only when the conditions match", condition "Customer role (B2B groups) is one of: Any wholesale role" (or your trade role).

Yes. Add a shipping rule: Methods = the methods to hide, "Hide these methods when the conditions match", condition "Cart weight is more than 30", or "Shipping classes: cart contains any of: Bulky".

A customer whose order is VAT exempt in WooCommerce (for example after a verified VAT number with AovUp EU & UK VAT Validation), and the customers the AovUp Tax Exemption editions exempt:

• AovUp Tax Exemption for WooCommerce (the free edition, 1.0.0 or newer): an account it exempts, by its account flag (until the end date set there) or one of the tax-exempt roles chosen in its settings. The rules ask that plugin itself, so this also works before the checkout.
• AovUp Tax Exemption from aovup.com, 1.1.8 or newer: a customer it exempts as a shopper, because one of its rules matches them (role, user, country or coupon) or because they claimed the exemption at checkout with a tax number the store checked. That is the decision that also removes the tax from the shipping. Only rules that match the shopper alone count: a rule that needs all of its conditions and also has a product, category or tax-rate condition doesn't, even when it removes the tax from that customer's items. Versions up to 1.1.7 don't tell other plugins their decision: update Tax Exemption to use this condition.
• AovUp Tax Exemption from WooCommerce.com, 1.0.1 or newer: a customer it exempts on the whole order (by its rules that don't depend on a product).

The amounts in your rules (the cart subtotal limits) are in your store's base currency. WooCommerce has no common way to convert them, so let your currency switcher convert them with the aovup_spr_amount filter. It gets the amount, what it is and the currency to convert to (the order's currency on the "Pay for order" page, otherwise the shop's current currency), and returns the amount in that currency, converted in proportion (amount × exchange rate). An order paid for in your base currency is never converted.

At the whole cart, the same as payment rules: every item (also virtual ones, which don't ship, and items in other shipments), and the cart's subtotal, number of items and weight. So "Cart subtotal is at least 100" means the same in a shipping rule and a payment rule. Only the address is the shipment's own. If your store splits the cart into several shipments (several addresses, vendors or warehouses) and you want each one judged on its own items, return true from the aovup_spr_shipping_rules_use_package filter.

WooCommerce shows its usual "no shipping options" message. Check your rules, or use Pro's checkout messages to tell customers why.

The customers it hides them from can't pay: WooCommerce only tells them that no payment methods are available. This happens with a rule such as "Show bank transfer only to trade customers" when bank transfer is the only method your store has switched on: guests and retail customers are left with nothing. The rule editor warns you when a payment rule covers every payment method that is switched on. Leave at least one method that every customer can use, or use Pro's checkout messages to tell customers what to do.

The checkout keeps working. A rule that can't be checked counts as not matching: a "show only when" rule hides its methods, a "hide when" rule hides nothing, and a Pro fee rule adds nothing. The error is written to WooCommerce > Status > Logs (source "aovup-spr"), at most once an hour per rule, with the plugin or filter it came from.

No. The plugin makes no outside requests.