Direct answer
To show From $19 instead of $19-$49 for a WooCommerce variable product, filter only the native variable price-range HTML, confirm the product has unequal numeric display prices, obtain the tax-display-aware minimum from WooCommerce, format it with WooCommerce's currency formatter, and prepend escaped plain text. Return the original HTML for every invalid, equal-price, or non-variable case. Never update saved prices or cart totals.
StoreFixKit's From Price for WooCommerce Variations uses that display-only model. Free applies one store-wide switch and prefix. Pro adds bounded product and category assignments plus one short suffix.
A displayed range is not the stored product price
A variable product can have several variation prices. WooCommerce may display a range before the shopper chooses an option, then display the selected variation's price after a choice.
Replacing the initial range is presentation. It should not change:
- variation regular or sale prices;
- sale schedules;
- product data in the database;
- cart or checkout prices;
- tax calculation;
- currency conversion;
- historical orders.
A public support request asks how to hide the WooCommerce price range and show one starting price. Another asks how to display the lowest variation price. These are understandable display jobs, not reasons to build a second pricing engine.
Let WooCommerce supply the minimum display price
The lowest raw database value is not always the number the current visitor should see. Tax display and WooCommerce price filters can affect displayed values.
A focused implementation should use the variable product's public display-price method and WooCommerce's wc_price formatter. It should not run its own variation query or copy currency formatting logic.
This keeps the result aligned with WooCommerce's current currency symbol, decimal rules, and tax-display configuration. It does not guarantee compatibility with every dynamic-pricing or multi-currency extension; those systems must be tested because they may own a different price surface.
Change only a real range
Adding From to every variable product can make an equal-price product less clear. If every available variation displays $29, the original single $29 is already accurate.
The safe decision is:
- confirm the product is a native variable product;
- read its minimum and maximum display prices;
- confirm both are numeric and nonnegative;
- confirm the minimum and maximum are unequal;
- otherwise return the exact original HTML.
Missing or malformed data should never produce $0, a guessed number, or a blank price.
Keep the prefix plain and short
From, Starting at, and Prices from are enough for the common job. A 40-character plain-text bound prevents the setting from becoming an arbitrary HTML or shortcode renderer.
Pro can add a similarly bounded suffix such as per set. The final display may become Starting at $19 per set, but the underlying variation, cart, and order values remain unchanged.
The selected variation remains WooCommerce's job
On a product page, WooCommerce JavaScript can update the price after the shopper selects a variation. A range filter should not intercept that event, animate prices, reset selections, or install another variation script.
That boundary reduces conflicts with variation swatches, themes, and custom selectors. It also means the initial From display may be replaced by WooCommerce's ordinary selected-variation price after a choice, which is the intended behavior.
Product Collection blocks expose a real compatibility boundary
A support report says From-price behavior did not carry into a Product Collection block. A block can obtain price markup through native PHP filters, REST data, JavaScript, cached HTML, or custom rendering.
A focused plugin can responsibly support surfaces that use WooCommerce's native variable price HTML. It should not claim to modify every block, feed, schema object, theme field, REST response, or JavaScript component.
If a block still shows a range:
- purge its cache;
- confirm it renders the native WooCommerce variable price HTML;
- inspect whether another extension replaces the price after the filter;
- record the component that actually owns the visible markup.
Injecting CSS selectors or template replacements to hide unknown markup would be brittle and could leave inaccessible or contradictory prices in the page source.
Product and category assignments need one clear meaning
Free's store-wide switch solves the simple case. Pro can enable the same display on a bounded product or category selection even when Free is off.
The understandable model is:
- Free on means every eligible native variable range receives Free behavior.
- A matching Pro product, product checkbox, or category can enable Pro behavior when Free is off.
- A Pro match can provide its own prefix and one suffix.
- A product exception or opt-out ignores Pro assignments and follows the current Free switch.
An exception therefore does not mean never show From; it means do not use Pro to decide. This distinction belongs in the interface and documentation.
The current Variation Price Display Range for WooCommerce offer confirms paid demand for broader price-display options. That is category evidence, not proof that every merchant needs animation, discount badges, formulas, admin columns, or variation JavaScript.
SEO, schema, and product feeds have separate owners
Visible price HTML is not the only place a price can appear. Product schema, merchant feeds, REST responses, social previews, cached blocks, and search indexes may use other data.
A display-only plugin should not promise to rewrite those systems. After changing the visible range, inspect:
- the shop archive and product page;
- page source and structured data;
- the store's product feed;
- Product Collection and theme blocks;
- cache and CDN variants;
- the cart and checkout after selecting a variation.
If one-price consistency is a business or regulatory requirement, choose a broader catalog-governance workflow and verify each publication channel.
Resource and failure boundary
WooCommerce already has the variable product and cached price data when rendering a native range. The helper needs one settings read and WooCommerce's minimum and maximum display-price calls.
It needs no:
- frontend JavaScript or stylesheet;
- plugin-owned variation query;
- custom table;
- cron event;
- storefront write;
- customer cookie;
- telemetry;
- StoreFixKit call from a public page.
Missing WooCommerce, invalid price data, an equal range, inactive Pro, or an unavailable license API returns the original HTML. Free remains local and independent of billing.
StoreFixKit's From Price documentation contains screenshots, exact setup, assignment meaning, external-surface checks, troubleshooting, rollback, and uninstall ownership.
Beginner launch checklist
Unequal prices
Create or use a test variable product with two purchasable variations at different display prices. Confirm the initial range becomes the chosen prefix plus minimum.
Equal prices
Use a variable product whose variations display the same price. Confirm the original single-price HTML remains.
Selected variation
Choose each variation. Confirm WooCommerce shows its own variation price and the cart receives the correct saved value.
Tax and currency
Test the store's real tax-display and currency configuration. Compare the shown minimum with WooCommerce's own variation values for that visitor context.
Simple product
Confirm a simple product is unchanged.
Blocks and archives
Test the live shop archive, product page, Product Collection block, and theme components. Record which surfaces use native WooCommerce price HTML.
Pro assignments
Test one selected product, one selected category, one product checkbox, one exception, one product opt-out, and the Free switch both on and off.
Rollback
Deactivate Pro and confirm Free behavior remains. Deactivate Free and confirm WooCommerce's original range returns without editing product or order data.
Security and support evidence
Only users who can manage WooCommerce should save global and Pro rules; product assignments require product-edit capability. Every write needs a nonce, capability check, bounded sanitization, and escaped output. WordPress's common plugin issues summarize the review expectations.
Useful support evidence includes the product ID and type, minimum and maximum display prices, tax display, currency, Free switch, Pro assignment, WooCommerce and plugin versions, theme or block, cache/CDN, exact URL, expected result, actual result, and screenshots. Remove customer data, credentials, payment details, and full license keys.
FAQ
Does From price change variation prices?
No. It filters the initial native variable-range HTML only.
Why does an equal-price product stay unchanged?
There is no real range to simplify, so the original WooCommerce value is clearer.
Why does the price change after choosing a variation?
WooCommerce owns selected-variation behavior. This release ships no variation JavaScript.
Will every product feed and block show From price?
No. Feeds, schema, REST, JavaScript blocks, and custom templates can use different price owners.
What happens when Pro expires?
The Free store-wide switch and prefix continue locally. Product and category assignments plus Pro suffix require an active product-bound license.
Focused plugin
Use the one-job implementation.
Show WooCommerce's formatted minimum variation price instead of a minimum-to-maximum range without changing saved product, cart, tax, or order prices.