How to remove trailing decimal .00's from product pricing

You can do it with the code that @brandon provided here:

http://squarespace.cloud.answerhub.com/questions/152145/can-someone-help-me-change-coding-to-get-rid-of-de.html

Thank you so much @paul2009 and @brandon. Worked a treat!

Good find @paul2009. That's an example of code I don't even remember writing. One time I went looking for a coding solution I couldn't solve, and was happy when I found it on Answers. Then I realized it was my own answer...

Been there too @Brandon!

The Community team have now imported the old Answers post 👍

Thanks @brandon and @paul2009 for this code! It works perfectly when I first save it in the foot code injection, but as soon as I refresh a page, it reverts to the normal pricing with decimals again. I wonder if it's because our prices are in £ rather than $. I've tried swapping the currencies out in the code but I really don't know what I'm doing! Any ideas how I could get it to work?

Here's an example of what I'm working with: https://ellishampers.co.uk/hampers/magnificent-n8-the-marvel

UPDATE:

Just checked that the above linked worked and the decimals had disappeared! Tried in incognito and they came back again. It seems that if I refresh the page the code works, but the first time I load it the decimals are always there. In normal browsing (not incognito), the same applies but every time you load the page, you also see the decimals briefly before they disappear. Worth putting the code in the header for this or is that something that could go wrong?

Thank you! 😊

The code was written in 2016 and like many of the older code samples provided on forums, it therefore understandably doesn’t take into account the introduction of Ajax on many Squarespace templates since that time. Turning off Ajax in Site Styles will fix this but it’s just a workaround. A better solution is to replace

(function() {

with

window.Squarespace.onInitialize(Y, function() {

If like me you’d like to understand why, I wrote an explanation here: https://sf.digital/squarespace-solutions/why-doesnt-my-code-work-until-i-refresh-the-page

Hi, thank you very much for this solution, I've found this to work great for me as well apart from a single instance when I choose two variables of a product to add to cart - such as a size and a color. When two variables are chosen, suddenly the two decimals appear again. Any idea why that might be and if there's a way to solve this?

What's the page @JiriWranovsky?

@JiriWranovsky As the site is set to Private, we need you to set a password in the visibility settings and tell us what it is.

Thanks for the link @JiriWranovsky; I now see what you're referring to.

When a visitor chooses a new variant, Squarespace built-in scripts check the price of the variant. The script then changes the page content to show the new price - even if it is exactly the same as before. The newly updated price includes the fractional element of the price. (There's a longstanding bug here too that removes the sqs-money-native class, but I'll put that to one side because it's not the main issue.)

The code shared above doesn't take account of all this because it's just a 'snippet' of example code to demonstrate how prices can be changed. Like the majority of code you'll find online, it's unsupported and isn't intended for use on a live site.

This particular snippet of code only runs when the page loads. It doesn't run again when the variant changes, which means that the price isn't reformatted to remove the fractional digits. To make it production-ready, the code needs to be restructured so that the function is triggered by several event listeners: on ajax page loading, full page loading and variant dropdown changes. The class in the original code would need to be changed too because of the bug mentioned above. Instead of sqs-money-native, it needs to look for product-price.

As I've said before on this forum, I don't advocate using unsupported code snippets on a production site. If you need robust solutions that won't leave your site vulnerable, I strongly recommend working directly with a Developer that you can trust. There are a number of great developers on this forum who know what they're doing and can be hired for a variety of tasks, from smaller jobs like this to entire sites.