Skip to content
Start a project
PricingEngineeringHow we work1 Nov 20264 min read

Why every price lives in one place, and what reads it

A price typed twice will differ twice. How one price list feeds the website, the proposals and the deals, and what stops a signed document changing.

Valentir Engineering Desk

Architecture diagram: Why every price lives in one place, and what reads it

A price typed in two places will, sooner or later, differ between them. In a studio that sends proposals that is not cosmetic: it is a quote that contradicts the website, or an invoice that contradicts the quote.

So there is one price list. The owner edits it on the Pricing page of the admin panel and nowhere else. The public website, new proposals and documents, and new deals all read it. This page does not print a single price, on purpose, because that would be one more place to go stale. The current numbers are on the pricing page.

What is in the list#

Packages, each with a price range or "custom", payment milestones and a warranty. Care plans, each with a monthly fee, a count of hours and a first-response target. A few terms: how many days an invoice is due, the review window and the reply window. Amounts are whole rupees and exclude GST. GST is always its own line on a document or an invoice, so nothing in the list adds it.

What the list enforces when it is saved#

  • A package's payments add up to exactly 100 per cent. The first is due when the deal is signed and no other is. The rest follow the project in order: design approved, build delivered for testing, acceptance signed.
  • Priced packages run upward and may touch but not overlap. A custom package has no price numbers at all and comes last.
  • Ids never change once saved. Anything a deal or a document points at cannot be deleted, only archived.
  • A save made from a stale page is refused, so two people editing cannot overwrite each other.

Every save is a version, with a note, who saved it, when, and a SHA-256 of the whole list. Bringing an old version back is itself saved as a new version.

Why a signed document does not change#

A deal stamps the package and the version of the list, and keeps its own copy of the payment schedule. A started deal never reads the price list again. A document keeps a snapshot of the package, which can be refreshed while it is a draft and is frozen when it is approved. A signed document therefore never changes when the prices do, and a draft made on older prices raises a "prices changed" finding in review.

The split between payments is worked out by the same arithmetic the invoices use, so a proposal and the invoices that follow it are built from one calculation, not two. One worked example from the test file both repositories share: an amount of 123457 rupees split 20, 20, 40 and 20 per cent gives 24691, 24691, 49383 and 24692. Each share is rounded to the rupee and the last row takes what is left, so the rows always add back to the total.

How the website stays in step#

The website reads the list from the admin. If the admin cannot be reached at the moment a page is rebuilt, the site does not rebuild that page from its bundled copy. It keeps serving the last good page and tries again on the next visit, because a page rebuilt from a copy that might be old would then be kept for an hour. The bundled copy is used only while the site is being built, or when no admin is configured at all. A release check compares the bundled copy with the live list.

Two tests tie the repositories together. The admin and the website share one file of test vectors, the rounding and package-lookup cases; the two copies are byte for byte the same (checked on 01-11-2026), and the website's test fails if they ever differ. Another scans the website's code and fails if a rupee amount is typed into it, sample data aside.

The cost#

One list means one wrong entry is wrong everywhere at once. Versions, the "what changed" lines and restore exist for that reason. They reduce the damage; they do not remove the risk. And a document that keeps its old prices after the list changes is the intended behaviour, but it can surprise someone who expected the new number.

Valentir Technologies LLP is a software studio in Noida. The estimator reads this list too, and a note on how it is built shows how it avoids ever printing a number the list does not hold.

Get our notes by email

We email our notes when we publish something worth your time.

We use your email only to send these notes, when we publish something worth your time. How we handle it is on our privacy page.

Search on Google and want more notes like this in your results? Add Valentir as a preferred source on Google.

If you want to argue with any of this, that is what hello@valentir.in is for.

Start here

Tell us what you want to build.

One call, a deterministic technical scope, and a 100% fixed price. From architecture to launch, we engineer software that drives real business results.

Contact UsChat on WhatsApp