specific input field similar to coupon in WooCommerce cart

Hi @sdnazdi

I hope you are doing well,

I am afraid it is not possible, you can compare strings and create conditionals based on the input: https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#Forminator-Conditional-Logic

Then create an extra calculation field for example:

– Discount applied {calculation-1} = Formula 10/100, set visibility based on the input, and Null in case it doesn’t exist to prevent the 0 in calculation 2.

– Final Price {calculation-2} = valor_product – valor_product * {calculation-1}

But it is a simple solution where we can’t control if the coupon is used or not in the past or track it, for a more complex control a plugin such as Woo is more appropriate.

Best Regards
Patrick Freitas

Hi @sdnazdi

There is no option to support such verification but the “visibility condition” solution suggested by my colleague doesn’t really requite it.

What you could do would be to add a single “input” type field where user enters coupon code (not selects it but just enters – types it in manually or copy-paste) and then this would be used to use calculations.

I’ve created example form for you so you could get a better idea how it works. You will find the form here

https://pastebin.com/JEUdU5xH

so you can import it to your site and test.

In general:

– there’s “input” field which is a text field where user can “freehand” enter something
– then there is a hidden “base price” calculation field where you set your base price;

– then you have two calculation fields;

first one is for “fixed” discount so in my example it’s just a value of 150 (so base price would be lowered by 150 if this is applied)

second one is for “percentage” discount so in my example it’s 10%, therefore it calculates 10% of base prices

– these two calculation fields have visibility conditions set based on the input field; conditions are based on “is” rule and the value defined there is your coupon code; since you can add multiple rules, you can define multiple codes this way and this determines which of these fields (discounts) would be applied; user does NOT see these coupons on front-end and in page source; so they can’t know them

– finally, there’s one more calculation fields which simply subtracts sum of both discounts (due to visibility rules that sum will always be equal to only one of the discounts based on the coupon because the other one will be zero and “zero+something” is always that “something”) from the base price.

In this example I set base price of 500, fixed discount to be 150 and percentage discount to be 10%. If you put “abc” text (coupon code) into input field, you’ll see that discount is 150 and final price to pay is 350; if you put “def” text (coupon code) into input field, you’ll see that discount is 50 (10% of 500 = 50) nd price to pay is 450.

Best regards,
Adam

Hi @sdnazdi

I can add as many as rules “any” for different coupons in visibility condition.

Yes, you definitely can. For as long as you keep the “Show if ANY” rule set instead of “Show if ALL” – it will work. This way you can define multiple coupon codes and users will not know them unless you actually tell them the codes.

Best regards,
Adam