Okay
  Public Ticket #4549374
B2B prices
Closed

Comments

  • Andreas started the conversation

    Hello, i am already using B2B King (free version) for my woocommerce store. althougn the free verison is good i am thinking of upgrading to the payed version. Coupe of days before i had a problem with the B2C and B2B prices. this is what happened. Lets say of
    Product A i had
    B2C price 4
    B2B price 2

    so in the fronted, even if viewing as B2C customer, i was viewing the B2B price. i cleared caches,  cleared transients but still the same. the only way to fix it was to manualy update the price in the backend

    so in Product A i did
    B2C price 4
    B2B price 2.1

    and the the price in the frontend was fixed. B2C and B2B customers were able to view the correct price. as i had many products (around 600). i hasd to ryn something like this 'wp post list --post_type=product --fields=ID --format=csv | tail -n +2 | xargs -I {} wp post update {}"", and the p[orblem was fixed. 


    so before moving to the payed version i wonder if you could helo me understand why this happened and how can i prevent of havibg te same problem in the future.

    thank you

  •  2,724
    WebWizards replied

    Hi Andreas,

    Thank you for reaching out!

    The issue you described sounds like a caching problem, though it is not immediately clear where the cache is coming from. A good way to test this if it happens again is to add the product to the cart. Usually, you will see the correct price in the cart because that area is not cached, while the product page itself might still show the cached, incorrect price.

    Are these simple products or variable products? Variable products have a tougher cache to clear, and B2BKing Pro is currently better at clearing that.

     

    If they are simple products, there could be another cache at play here, such as from your hosting provider or another plugin. Sometimes hosting environments have hidden caches or mu-plugins that only clear their cache when a post is updated, which explains why running the bulk update fixed it for you.

    If you'd like, we can also troubleshoot this directly on the site to see what is going on and how to prevent it. For that, we would need a backend login to the site or a staging clone site.

     

    Kind regards,
    Stefan