Booster for WooCommerce plugin review and common issues

Booster’s currency module exchanges prices using configured rates. Check: (1) go to Booster → Products → Prices and Currencies → Currencies — verify currencies are configured with exchange rates; (2) enable “Price Format” so product prices are formatted according to the selected currency; (3) WooCommerce caches product prices — clear all object and page caches after currency configuration; (4) some Booster currency features require JavaScript to be loaded — check for JS errors; (5) verify the currency switcher widget is active and placed on product pages.

Booster PDF requires PHP’s PDF generation capabilities. Check: (1) go to Booster → PDF Invoicing → Settings and verify the PDF library is correctly detected (mPDF or similar); (2) the WordPress uploads directory must be writable for PDF generation; (3) PHP memory limit must be sufficient for PDF rendering (256MB recommended); (4) verify the PDF template is configured — go to Booster → PDF Invoicing → Templates and check the invoice template; (5) disable other PDF invoice plugins that may conflict with Booster’s PDF module.

Booster modules add various hooks and filters to WooCommerce. To identify performance-impacting modules: (1) use Query Monitor plugin to see which hooks are adding the most processing time; (2) disable Booster modules one by one (Booster → Booster Dashboard — toggle modules off) and test page load time after each; (3) the Price & Currency, Cart, and Checkout modules tend to add more processing overhead than display-only modules; (4) enable WordPress object caching (Redis) to reduce the impact of Booster’s additional database queries.

Enable Booster → Products → Prices and Currencies → Price by User Role. Configure price multipliers per role: Wholesale role = 0.7 (70% of regular price), Retail = 1.0 (standard price). Or set fixed prices per product per role in the product edit screen. When a wholesale user views a product, they see the wholesale-adjusted price. When retail customers view the same product, they see the standard price. This enables basic wholesale/retail price differentiation without a dedicated wholesale plugin.

Enable Booster → Cart & Checkout → Cart → Minimum Order Amount. Configure: the minimum cart value (e.g., $50), which user roles the minimum applies to (all users, or exclude admin), whether the minimum applies before or after discounts, and the error message displayed when the minimum is not met. With the minimum configured, the checkout button is disabled (or an error displays) until the cart reaches the configured minimum. Configure a minimum per-product, per-category, or site-wide.

Booster is better when needing multiple features from its module library and wanting to minimize total plugin count. Individual specialized plugins are better when needing deep functionality in a specific area — YITH WooCommerce Gift Cards has more gift card features than Booster’s gift card module; a dedicated PDF invoice plugin has more invoice customization than Booster’s PDF module. The right approach depends on depth needed: Booster for broad, moderate-depth WooCommerce customization; specialized plugins for deep functionality in specific areas.

Booster’s 100+ modules each modify different WooCommerce hooks. Conflicts are most likely between Booster modules and other plugins that modify the same WooCommerce areas. Common conflict areas: currency switching (conflicts with other multi-currency plugins), checkout customization (conflicts with checkout plugins like CartFlows), PDF invoices (conflicts with other PDF invoice plugins). The modular architecture means disabling the conflicting Booster module resolves the conflict without removing the entire plugin.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.