Whols with Polylang

  • Resolved beatrizgonher

    (@beatrizgonher)


    2 weeks, 1 day ago

    Hello,

    We are using Whols Pro together with Polylang Free on a WooCommerce website with Spanish and Catalan.

    We have a problem with wholesale prices on translated products:

    • Whols Pro is configured with a single wholesale role.
    • The customer has been approved and has the correct wholesale role.
    • Wholesale prices are configured individually for each product.
    • The Spanish and Catalan products are correctly linked as translations.
    • The wholesale prices are correctly set in both product translations.
    • When the customer views the website in Spanish, the wholesale price is displayed correctly.
    • When the same customer switches to Catalan, the regular retail price is displayed instead.

    So the user role and the product prices are correct, but Whols does not apply the wholesale price on the translated Catalan product.

    Could you please confirm whether this is a known limitation when using Whols Pro with the free version of Polylang, and how would we solve this issue?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Madhusudan

    (@madhusudandev)

    2 weeks ago

    Hi @beatrizgonher,

    Thanks for the detailed report — that made it much easier to look into.

    We set up a local test environment with WooCommerce, Whols Pro, and Polylang (tested with both the free and pro versions of Whols) to replicate your exact setup:

    • Single wholesale role, pricing model set to single role
    • A test customer approved with the wholesale role
    • A product created in Spanish, translated and linked to Catalan via Polylang
    • Wholesale price configured individually on both the Spanish and Catalan versions of the product

    In this setup, the wholesale price displayed correctly on both the Spanish and Catalan versions of the product for our test wholesale customer — including when switching languages via the site’s language switcher, not just by URL. We were not able to reproduce the behavior you’re describing, where Catalan falls back to the regular retail price.

    This tells us it isn’t a general limitation of Whols Pro with Polylang — the two do work together correctly in the scenario you outlined. To help narrow down what’s different on your site, could you check a few things?

    1. Are you also using the “Polylang for WooCommerce” add-on (the paid WP Syntex add-on), in addition to Polylang Free? If so, please check the “Synchronize” settings under Polylang’s Languages settings — if “Custom fields” sync is enabled there, saving the Spanish product can silently overwrite the wholesale price data on the Catalan product, which would produce exactly this symptom.
    2. Is any caching plugin active (page cache, object cache, or a host-level cache)? If so, try clearing the cache and testing again in a private/incognito window.
    3. Could you double-check, directly on the Catalan product’s edit screen right now, that the wholesale price field still has a value set?

    If none of that resolves it, please open a ticket with our support team here: https://wpwhols.com/contact-us/ — from there we can look into site-specific details further with you.

    Thanks for your patience, and sorry for the inconvenience this is causing on your store.

    Best regards, The Whols Team

    Thread Starter beatrizgonher

    (@beatrizgonher)

    2 weeks ago

    Hi, i send a ticket in whols pro support: https://wpwhols.com/contact-us/

    Following your previous response, we have checked the points you mentioned:

    • We are using Polylang Free, not Polylang for WooCommerce.
    • There is no caching plugin or hosting cache involved.
    • The wholesale price is correctly saved on both the Spanish and Catalan versions of the product.
    • Polylang’s “Custom fields” synchronization is disabled.
    • The same wholesale customer sees the correct wholesale price in Spanish, but the regular retail price in Catalan.

    The problem occurs everywhere in Catalan: product listings, product pages, cart and checkout.

    We also tested creating/registering a new wholesale customer directly through the professional registration form in Catalan, and the same problem occurs. Therefore, the issue is not related to how the customer was registered: wholesale pricing works in Spanish and always fails in Catalan.

    One additional detail: initially the Whols role had a Catalan translation. We removed that translation because, with the translated role, the behaviour was actually reversed (good y catalán and bad in spanish). After removing the role translation, Spanish works correctly, but Catalan still does not apply the wholesale price.

    Could you please investigate what Whols is doing when the current language is Catalan and advise us on how to fix this?

    We would especially like to know if there is a known compatibility issue or setting we are missing with Whols Pro and Polylang Free.

    One additional finding: We also tested “Wholesale Price Visibility → Testing Mode (Admin & Wholesale)”. In this mode, the administrator sees the correct wholesale prices in both Spanish and Catalan, but a real wholesale customer logged into the frontend still sees the regular retail price in Catalan. 

    Thank you

    Plugin Contributor Madhusudan

    (@madhusudandev)

    2 weeks ago

    Hi @beatrizgonher,

    Thanks for the extra details — that helped us pin this down. Please try the following:

    Immediate fix: In Polylang, go to Languages → Settings → Custom Post Types and Taxonomies, and un-tick “Wholesaler Roles.” Save, then check the Catalan product page again.

    Permanent fix: We’ve identified the code change needed on our side so this stays fixed even if that setting gets re-enabled later. It’ll be included in an upcoming release.

    Please confirm once you’ve tried the Polylang setting change above, and let us know if the wholesale price now shows correctly in Catalan.

    Best regards,
    The Whols Team

    Thread Starter beatrizgonher

    (@beatrizgonher)

    2 weeks ago

    Thank you very much for the support. With this fix it works ok.

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

You must be logged in to reply to this topic.