Conditional Logic, Formula Pricing, and Swatches in WowAddons Pro: Three Stores, Worked End to End
Most plugin reviews describe features in the abstract: "conditional logic hides fields", "formula fields calculate prices", "swatches look nice". That tells you almost nothing about whether the feature will survive contact with a real customer. A real customer types a name with a typo, uploads a blurry photo, picks a size that doesn't exist, and expects the price to be right anyway. This article does the opposite of an abstract review. It takes three real store scenarios — a print shop, a gift store, and a furniture maker — and walks through the exact field setup for each one, field by field, condition by condition, formula by formula.
WowAddons Pro, by WowRevenue / WPXPO, is a WooCommerce product add-ons plugin — not an Elementor addon. It offers 25+ product add-on field types including text, checkbox, radio, color picker, color and image swatches, range sliders, file and image uploads, date and time pickers, and popup fields. On top of the fields sit three engines: conditional logic (show or hide a field based on another field's value), real-time dynamic pricing with formula fields, and product recommendations for complementary add-ons. There is also a drag-and-drop option-group builder and an analytics dashboard tracking add-on clicks, add-to-cart events, order counts, and sales amounts. The plugin requires WooCommerce and works with simple and variable products. The free version on wordpress.org is generous — 25+ field types, conditional logic, dynamic pricing, and the live preview builder are included free. The Pro version is available from WP Theme Bazar at ৳2,000 (regular ৳3,000) for a one-time lifetime license — price may change — see the product page for the current price. The official lifetime 1-site license is $299 (promo $164, roughly ৳19,700).
Buy WowAddons Pro: message us on WhatsApp https://wa.me/8801919052411 with the product name — bKash/Nagad accepted, activation within minutes.
How the Three Engines Fit Together
Before the scenarios, one mental model. Think of every product page as a small form with three layers:
- Fields collect information: the name to print, the wood type, the topping.
- Conditions decide which fields the buyer sees: the logo upload appears only when the buyer chooses "upload my own design"; the delivery date appears only for delivery orders.
- Formulas decide what the buyer pays: the base price plus the per-item extras, or an area multiplied by a rate.
A good setup keeps the buyer looking at as few fields as possible at any moment. Every field you hide with a condition is a field the buyer cannot get confused by. Every price the formula calculates instantly is a question the buyer does not have to ask on WhatsApp.
Scenario 1: The Print Shop — A Custom T-Shirt
The product is a plain cotton t-shirt, base price ৳600, with the customer's name printed on the front and an optional logo on the back.
Field 1 — Print text (text field, required, character limit 20). Label it "Name to print" and put the character limit in the help text: "Up to 20 characters". The limit matters — without it, someone will type a slogan and the printer will have to guess. Price: no extra charge for the front print, because it is included in the base price.
Field 2 — Print location (radio: Front only / Front and back, required). Front only adds nothing; front and back adds ৳150. This single field is the trigger for everything that follows.
Field 3 — Logo upload (file/image upload, optional). Condition: show only when Field 2 equals "Front and back". Help text: "PNG or JPG, up to 5 MB, clear image on a plain background". Restrict the file types and size in the field settings — an upload field with no limits is an invitation for a 40 MB phone photo that breaks the order email.
Field 4 — Garment colour (color swatch, required). White, black, navy, red. Swatches beat a dropdown here because the buyer sees the colour instead of reading its name. No price difference.
Field 5 — Size (radio: S / M / L / XL, required). No price difference, but required, so the order can never arrive without a size.
Formula: total = ৳600 base + ৳150 if front-and-back is selected. That is the whole calculation, and it updates live as the buyer clicks. Test the two paths: front only should show ৳600, front and back should show ৳750, and the upload field should appear and disappear with the radio choice. If the upload field stays visible when it should be hidden, the condition is pointing at the wrong value — the most common setup error, and one the live preview builder makes easy to catch.
Scenario 2: The Gift Store — A Build-Your-Own Gift Box
The product is a gift box, base price ৳300 for the box itself, and the buyer fills it.
Field 1 — Box size (radio: Small / Medium / Large, required). Small adds ৳0, Medium adds ৳100, Large adds ৳200. This is the anchor field: everything else is an extra.
Field 2 — Chocolates (checkbox group, optional). Three options, each with its own price: a small chocolate pack ৳150, a premium chocolate pack ৳350, truffles ৳250. Checkboxes, not radios, because the buyer can pick more than one.
Field 3 — Greeting card (radio: No card / Standard card ৳50 / Premium card ৳120, optional). The card choice triggers Field 4.
Field 4 — Message on the card (text field, optional). Condition: show only when Field 3 is not "No card". Character limit 100. If the buyer picks a card but leaves the message blank, the shop writes a standard greeting — decide this with the client and put it in the help text so nobody is surprised.
Field 5 — Wrapping (color/image swatch, optional). Four wrapping paper designs as image swatches, each ৳80. Image swatches work better than colour swatches here because the buyer is choosing a pattern, not a colour.
Field 6 — Ribbon colour (color picker, optional). A free choice, no extra charge, shown only when wrapping is selected. A colour picker is right for this field because the buyer wants any shade, not one of four fixed options.
Formula: total = ৳300 + box size extra + sum of checked chocolate prices + card price + wrapping price. The formula field adds the selected options automatically; your job is to make sure every priced option has its price entered correctly and that no option is accidentally priced at zero. The recommendation engine helps here too: when the buyer adds chocolates, the plugin can suggest the greeting card, which is the single highest-converting suggestion in a gift store.
Test the extremes. The cheapest order is a small box with nothing in it: ৳300. The most expensive is a large box with every chocolate, a premium card, and wrapping: ৳300 + ৳200 + ৳150 + ৳350 + ৳250 + ৳120 + ৳80 = ৳1,450. Place both test orders and confirm the totals before the store goes live.
Scenario 3: The Furniture Maker — A Table Built to Size
The product is a wooden study table, and the price depends on its size and its wood.
Field 1 — Width in centimetres (range slider, required, min 60, max 200). The slider shows the value live, so the buyer sees "120 cm" as she drags. A slider is better than a text box here because it enforces the range — nobody can type 1000 by accident.
Field 2 — Depth in centimetres (range slider, required, min 40, max 100). Same pattern. Keep the two sliders next to each other so the buyer understands they describe one table.
Field 3 — Wood type (image swatch, required). Three options with very different prices per square unit: mango wood, teak, and sheesham. Image swatches show the grain, which is the actual thing the buyer is choosing.
Field 4 — Finish (radio: Matte / Glossy, required). Glossy adds a flat ৳500. Matte adds nothing.
Field 5 — Delivery date (date picker, optional). Minimum lead time 7 days from today — set this in the field settings so nobody orders a table for tomorrow. Help text: "We need at least 7 days to build your table."
Formula: total = (width × depth ÷ 10,000) × rate per square metre for the chosen wood + finish extra. The division converts square centimetres to square metres; getting this conversion wrong is the classic formula error, so test it with real numbers. A 120 × 60 cm table is 0.72 square metres. If the mango-wood rate is ৳8,000 per square metre, the wood cost is ৳5,760, plus ৳500 for a glossy finish — ৳6,260 total. Work that number out by hand before you enter the formula, then check the live preview shows exactly that. If it shows ৳57,600, your conversion factor is off by ten, and you caught it in testing instead of on a real order.
The Details That Separate a Working Setup From a Broken One
Across all three scenarios, the same handful of details decide whether the store works:
- Required fields should be few. Every required field is a place a buyer can abandon the purchase. Require only what the order cannot be fulfilled without.
- Conditions should hide, not just show. The goal is a short form, not a long one with clever reveals. If a field is irrelevant for most buyers, hide it by default.
- Prices belong in the field settings, not in the description text. If the description says "large adds ৳200" but the field adds ৳250, the buyer is misled and the seller loses the argument. One source of truth: the field.
- Uploads need limits. File type, file size, and a clear instruction about what a good upload looks like. Every unlimited upload field eventually receives something unusable.
- Test every path, not just the happy one. The cheapest order, the most expensive order, a missing required field, a file upload, a date in the past. Five test orders now save fifty support messages later.
Reading the Analytics After Launch
Once the store is live, the analytics dashboard becomes the most valuable part of the plugin. It shows add-on clicks, add-to-cart events, order counts, and sales amounts per add-on. Check it monthly with the client. An add-on with many clicks but few orders is priced too high or described badly. An add-on nobody clicks is invisible — move it higher on the page or make it a recommendation. An add-on everyone buys is underpriced. These are business decisions, and the dashboard gives you the numbers to make them instead of guessing.
The same vendor also makes WholesaleX Pro for B2B pricing and WowOptin Pro for popups, which is useful to know when a client's store grows beyond add-ons: the next problem usually arrives in the same ecosystem.
FAQ
Does WowAddons Pro need Elementor? No. It is a WooCommerce product add-ons plugin, not an Elementor addon. It requires WooCommerce and works with simple and variable products.
Can prices change automatically based on what the buyer picks? Yes. Formula fields calculate the total in real time from the buyer's selections, including dimensions, quantities of extras, and conditional choices.
What happens if a buyer uploads a huge file? That depends on your field settings. Always set a file size limit and allowed file types on upload fields, and state the limits in the help text.
Can I use conditional logic in the free version? Yes. The free version on wordpress.org includes 25+ field types, conditional logic, dynamic pricing, and the live preview builder.
How much is the Pro version? From WP Theme Bazar it is ৳2,000 (regular ৳3,000) for a one-time lifetime license — price may change — see the product page for the current price. The official lifetime 1-site license is $299 (promo $164, roughly ৳19,700).
Buy WowAddons Pro: message us on WhatsApp https://wa.me/8801919052411 with the product name — bKash/Nagad accepted, activation within minutes.
