---
title: "Comment by netproxy on \"\"Your product configurator should price server-side, not in JavaScript\"\" | Hashnode"
description: "One detail worth handling on the live-price side is out-of-order quote responses: if option changes fire several quote calls, a slower earlier response can over"
url: "https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6add3273c4f536f4a8697edb"
---

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

[netproxy](https://hashnode.com/@argumentmoney8117)

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

One detail worth handling on the live-price side is out-of-order quote responses: if option changes fire several quote calls, a slower earlier response can overwrite a newer price unless requests are aborted or responses are sequenced against the current configuration.

[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/6add3273c4f536f4a8697edb#reply-6adfa6045c90a3734a4b5dd8)

Good catch, that race is real. I abort the in-flight request on every change with AbortController and tag each response with the config it belongs to, so stale answers get dropped. Probably worth its own follow-up post.
