Description
The Conditional Shipping and Payments add-on applies conditional rules at WooCommerce checkout, hiding or showing shipping methods and payment gateways based on criteria such as product category, cart total, weight, shipping country, user role, or combinations of these conditions. Store owners who sell items with logistical restrictions or want to avoid unfeasible orders gain granular control over which options appear to each customer at the time of purchase.
Key Features
- Visual conditional rules
Creates combinable conditions in the admin panel without editing code or WooCommerce hooks. - Shipping method filtering
Hides specific carriers based on country, zip code, weight, or product type in the cart. - Payment gateway restriction
Disables payment methods based on minimum amount, category, user role, or destination. - Cart-based conditions
Evaluates subtotal, item quantity, shipping classes, and specific products to trigger rules. - AND and OR logic
Combines multiple conditions in the same set with operators for complex checkout scenarios.
Benefits of Conditional Shipping and Payments
- Fewer canceled orders
Prevents unfeasible shipping and payment combinations before the customer completes checkout. - More predictable logistics
Ensures bulky or fragile products only appear with compatible carriers. - No-developer setup
Store owners build rules directly from the admin, without relying on custom programming. - Audience-tailored checkout
Shows different options for wholesale, retail, or customers from specific regions, according to the store’s strategy.
Who Is It For?
- WooCommerce stores with a mixed catalog of physical, digital, and perishable products.
- Operations with logistical restrictions by region, weight, or merchandise type.
- B2B businesses that offer differentiated payments based on buyer profile.
Conditional Shipping and Payments solves a recurring problem for those operating heterogeneous catalogs in WooCommerce: the need to restrict shipping and payment combinations without rewriting filters via code. By consolidating these rules into a single interface, store owners gain agility to adjust checkout policies as new products, served regions, or logistics partnerships emerge in the operation.
Frequently asked questions
Is WooCommerce Conditional Shipping and Payments GPL-licensed?
Yes. WooCommerce Conditional Shipping and Payments is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use WooCommerce Conditional Shipping and Payments on multiple sites?
Yes. You can install WooCommerce Conditional Shipping and Payments on as many sites as you want. Only automatic updates through Ultrapack Auto Updater have a limit: from 3 to 80 sites, depending on the plan.
How much does WooCommerce Conditional Shipping and Payments cost at Ultrapack?
WooCommerce Conditional Shipping and Payments costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does WooCommerce Conditional Shipping and Payments include updates?
Yes. The current version of WooCommerce Conditional Shipping and Payments is 3.1.5, published at Ultrapack on Sep 3, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is WooCommerce Conditional Shipping and Payments scanned before publication?
Yes. Every version of WooCommerce Conditional Shipping and Payments goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin WooCommerce Conditional Shipping and Payments?
Requires WordPress 6.8 or higher and PHP 7.4 or higher. Tested up to WordPress 7.0.
What changed in this version
Version 3.1.5 2026.09.02
- Fix - Applied existing wildcard shipping restrictions to object-backed dynamic rates without changing substring matching.
- Fix - Required product edit permission before returning product-specific restriction rules through the Abilities API.
- Fix - Validated product restriction metadata imported from CSV before storing or rendering it.
- Fix - Evaluated Store API pay-for-order payment restrictions against the order being paid.
- Fix - Prevented guest-supplied e-mails from satisfying customer allowlist restrictions.
- Fix - Preserved and anchored wildcard patterns in customer e-mail restrictions.
- Fix - Matched coupon-code wildcards against complete coupon codes.
- Fix - Failed closed when Store API payment gateway validation receives an unavailable gateway.
- Fix - Evaluated billing country and state restrictions against the order on pay-for-order pages.
- Fix - Bounded Date/Time condition parsing before expanding numeric ranges.
- Fix - Kept restrictions in place when a Date/Time condition value cannot be read.
- Fix - Restricted queued store-management notices to users who can manage WooCommerce.
- Fix - Prevented repeated deserialization of restriction metadata during product CSV export.
- Fix - Prevented translations from loading before WordPress initialization.
- Dev - Stopped pull request E2E jobs from receiving release credentials.
- Dev - Authenticated browser requests to test-only E2E helpers with a per-run token.
- Dev - Pinned CI dependencies used by jobs with access to sensitive credentials.
- Dev - Pinned GitHub Actions to immutable commit revisions.
- Dev - Removed redundant and low-value tests.
- Dev - Managed changelog entries with Jetpack Changelogger: pull requests add a file under changelog/ instead of editing changelog.txt.
Version 3.1.4 2026.08.19
- Fix - Restricted product rule toggles to users who can edit the target product.
- Dev - Restored TLS certificate verification and fail-closed error handling in the release deployment script.
- Fix - Applied billing-period restrictions to manual subscription renewals.
- Dev - Re-enabled PHP 8.4 unit tests and fixed the CI matrix so the HPOS job actually runs against the HPOS order datastore.
- Dev - Fixed the build:js script and updated cross-env to v7.
- Dev - Enabled JavaScript linting in CI and migrated the ESLint setup to the flat config format required by ESLint 10, aligning the lint and formatting toolchain with WooCommerce core.
- Fix - Fixed an issue where the Checkout block could receive an undefined payment method callback configuration when no payment gateway restrictions were active.
- Dev - Updated the npm build toolchain to resolve all remaining Dependabot security alerts.
- Fix - Fixed a fatal error that could take down sites running a WooCommerce version older than the required minimum.
- Fix - Corrected all-item package tag rules that use AND matching.
- Dev - Verified the ChromeDriver download against its published checksum in the E2E CI job.
- Fix - Fixed an issue where payment gateway restrictions could stop applying for the remainder of a request after the Cart/Checkout blocks cart data was generated.
- Fix - Fixed an issue where payment gateway and shipping method restrictions could stop applying for the remainder of a request when the debug mode was enabled.
- Dev - Exposed the shared `.ai/commands` to agent tooling and documented the isolated worktree setup.
- Dev - Enabled CSS linting in CI and fixed source style violations.
- Dev - Pinned and verified WP-CLI before release packaging.
- Fix - Corrected all-item package brand rules that use AND matching.
- Fix - Applied instance-specific shipping method restrictions on order-pay pages.
- Dev - Update wp-coding-standards/wpcs to 3.4.1 (security release) in the phpcs lint tooling.
- Dev - Update development Composer dependencies (PHPUnit, Guzzle PSR-7, PsySH, Symfony YAML) to resolve security advisories in the PHP test toolchain.
- Dev - Update development npm dependencies to resolve security advisories in the build toolchain.
- Dev - Hardened the QIT test workflow: pinned the QIT CLI version and stopped workflow inputs from being interpolated into shell source.
- Fix - Prevented "Translation loading was triggered too early" notices when the installed WooCommerce or PHP version is not supported.
- Fix - Prevented unauthorized users from toggling global checkout restrictions.
Version 3.1.3 2026.07.22
- New - Important: WordPress 6.8+ is now required.
- New - Important: WooCommerce 10.6+ is now required.
- Tweak - Bumped WooCommerce tested up to version to 11.0.
Version 3.1.2 2026.06.16
- Tweak - Bumped WooCommerce tested up to version to 10.9.
- Dev - Added initial read-only WordPress abilities for Conditional Shipping and Payments restriction rules.
- Dev - Updated the JavaScript build toolchain to the React 18.3 line and added React 19 readiness guards.
Version 3.1.1 2026.04.20
- Fix - Fixed admin styling compatibility issues with WordPress 7.0.
- Tweak - Bumped WordPress tested up to version to 7.0.
- Tweak - Bumped WooCommerce tested up to version to 10.7.
- Tweak - Added settings link on plugins page.
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
- Download the file
woocommerce-conditional-shipping-and-payments.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
woocommerce-conditional-shipping-and-payments.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 6.8 or higher and PHP 7.4 or higher. Tested up to WordPress 7.0.
Stuck on a step? Open a ticket telling us which one you stopped at.

UAU Ready