---
title: "Comment by Mahdi Jabinpour on \"\"Your product configurator should price server-side, not in JavaScript\"\" | Hashnode"
description: "Separating information leakage from price integrity is useful. I would make the quote reference carry an explicit pricing-version and expiry policy too: if the"
url: "https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6add11325954ca33689881ff"
---

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

[Mahdi Jabinpour](https://hashnode.com/@mahdi-lumowp)

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

Separating information leakage from price integrity is useful. I would make the quote reference carry an explicit pricing-version and expiry policy too: if the rules change between preview and acceptance, silently recomputing can surprise the buyer even when the server is authoritative. A clear “quote expired, review the new total” step keeps the security boundary and the buying experience aligned.

[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/6add11325954ca33689881ff#reply-6adfa61c3b9bd4b0552f1b73)

Yes. A quote should carry a version and an expiry, and on acceptance you revalidate server-side. If the rules moved, show “quote expired” with the new total instead of silently recalculating. Silent recalculation is how you lose trust.
