---
title: "Comment by Indie Ship Log on \"Your product configurator should price server-side, not in JavaScript\" | Hashnode"
description: "This is the part I keep relearning on small B2B tools. If the browser can see the tier table, a customer will too. I used to ship the total from the client and"
url: "https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6adf01b7da89bc08440b9b35"
---

[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)

[Indie Ship Log](https://hashnode.com/@indieshiplog)

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

This is the part I keep relearning on small B2B tools. If the browser can see the tier table, a customer will too. I used to ship the total from the client and only check it loosely on submit. Moving the price calc behind the API, and treating the posted number as untrusted, saved me from a messy discount bug. For a single public price I still leave it in the page.

[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/6adf01b7da89bc08440b9b35#reply-6adfa5c34ba8a6158c09c49b)

Exactly this. “Treat the submitted number as untrusted” is the whole game. Keeping one public price for display is fine, the sin is letting that number decide what actually gets charged. Sounds like you landed in the right spot.
