---
title: "Comment by Indie Ship Log on \"\"Your product configurator should price server-side, not in JavaScript\"\" | Hashnode"
description: "The integrity half is the one I keep underestimating. I used to think hiding the price list was the whole problem, then realized a tampered total on submit is w"
url: "https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6addb09703f6b5700ad9cecb"
---

[Discussion](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec)

Comment ["Your product configurator should price server-side, not in JavaScript"](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec)

[Oct 25](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6addb09703f6b5700ad9cecb)

The integrity half is the one I keep underestimating. I used to think hiding the price list was the whole problem, then realized a tampered total on submit is worse if the server just trusts it. Sending the config and letting the server recompute on confirm is the version I would actually ship. The bit about a price change being a data change, not a deploy, would have saved me a few Friday releases.

[Dominik Groński](https://hashnode.com/@grodev)

[Oct 26](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6addb09703f6b5700ad9cecb#reply-6adfa5ddba2907af020b0d07)

Recompute on confirm is the key line. And pricing as data instead of deploys was half the reason I wrote this, good to hear it maps to real pain. No more Friday releases just to change a number.
