Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter dominiktdk

    (@dominiktdk)

    Howya good people,
    Should we expect any further replies from your end regarding the above issue?
    We were considering getting some pro bundles from you but.. does it normally take so long for you to respond to customers/ potential customers queries?

    Regards,
    Dominik

    Thread Starter dominiktdk

    (@dominiktdk)

    Thanks kindly for your reply,
    Well,
    At the moment my suffix is as follows: {price_including_tax} incl. Vat

    Yes, I am calculating and displaying tax this way. If I change the suffix to text only (i.e. “Ex. VAT”)- I will loose the numeric value of ‘VAT included’ price- which I can not afford (for businesses that deal with both: retail AND trade customers- a visitor expects both prices to be displayed).
    I believe that I am following the best and recommended method of achieving this (as suggested in woocommerce settings: https://prnt.sc/1qlwsc7)…

    Since this seems to be commonly practiced way of displaying the ‘incl VAT’ price- couldn’t you- good people give us- users some better workaround option that would let us keep using the ‘Incl VAT’ numeric price as suffix of the base product- as it is?
    I.e.: Couldn’t your plugin:
    – instead of USING the suffix of the BASE PRODUCT PRICE…
    -> GENERATE the suffixes accordingly based on THESE PRICES: https://prnt.sc/1qm04ay
    ?
    I mean- this should make perfect sense, but if the above is problematic- maybe just let us get rid of the suffixes in the ‘frequently bought together’ tab (as in my example)- so we can at least summarize the tab with information ‘Net value of additional products:’ (configured in your plugin’s ‘Additional price text’ field)

    Many thanks
    Dominik

    Thread Starter dominiktdk

    (@dominiktdk)

    Did you even read the questions I asked???
    You did not answer to any of them I’m afraid…

    Thread Starter dominiktdk

    (@dominiktdk)

    Okay,
    So as I understand- your plugin appears to be compatible only to the lvl where it does not make conflicts with the RM plugin?
    Meaning that any schema markup i.e. done previously with RM plugin is no longer valid after enabling your plugin/ even with ‘compatibility’ enabled?
    In the scenario where both plugins are enabled- yours simply becomes the one and only that contributes to Schema markup?
    *I’m not complaining here.. just trying to wrap my head around the ‘compatibility’ aspect..

    If above assumption is correct- should I have the RM ‘SCHEMA MODULE’ enabled/ disabled/ or it is completely irrelevant?

    Thanks in advance,
    Dominik

    Thread Starter dominiktdk

    (@dominiktdk)

    That’s 100%, Problem solved,
    Keep it up!
    Thanks for help

Viewing 5 replies - 1 through 5 (of 5 total)