Hi,
Thanks for the very detailed report, it gives us a good starting point. One small correction first: the AJAX response of the plugin still returns a "price" field (not "price_value"), so that part of the AI's analysis was off. The real issue is the one you spotted right after it: the product form on the page is missing the product_id input, so the AJAX call goes out without a product_id and the server replies "No product id". Without a product_id, the JavaScript then tries to read the price out of an empty response, which is the "Cannot read properties of null (reading 'price')" error you see in the console.
This is a known side effect of the product form restructuring that happened in HikaShop 6.4.0. HikaShop 6.4.1 already includes the fixes for it, both on the form side and on the JavaScript helper that the Price Calculations plugin uses to read the form. So in principle, on 6.4.1 it should be working out of the box.
The two most common reasons it still doesn't work after the update are:
1. A cached copy of HikaShop's main JavaScript file is still being served to your browser, so the fix is technically deployed on the server but your browser is still running the old version. Could you try a hard refresh on the product page (Ctrl + Shift + R on Windows/Linux, Cmd + Shift + R on Mac), and also clear the Joomla cache from System > Maintenance > Clear Cache? Then reload the product page and check whether the calculation comes back.
2. Your Joomla template has a custom override of the HikaShop product view. Joomla template overrides take precedence over HikaShop's own files, so if the override was created before the 6.4.0 restructuring, it can keep the old form structure on the page and prevent the fix from taking effect. To check: in your Joomla files, look for a folder like templates/<your_template>/html/com_hikashop/product/ . If you see files like show_default.php, show.php, quantity.php inside it, then you do have overrides for the product page. If that is the case, the simplest test is to rename that "product" folder temporarily to "product_backup" and reload the product page, to see whether the calculation comes back. If it does, the overrides are the culprit and they need to be regenerated from the 6.4.1 versions.