Panzo keeps your rates honest over time. Prices live in city-scoped, date-effective versioned price books; a price lock lets one customer and project keep a rate you quoted them; and the terms printed on a quote freeze the moment it is sent. This guide is for owners and commercial leads who set rates and need old quotes to mean what they said.
Versioned price books, by city and date
A price book holds the selling and internal cost rates for your products, scoped to a city because a job in one city rarely costs the same as another. You change prices by publishing a new version, never by editing a rate in place. Once a version is published, its rates become immutable, right down to a direct database write, so history cannot be quietly rewritten.
- Each price book starts as Draft V1; only a draft is editable.
- Publishing needs at least one product rate and an effective date.
- Creating the next version copies the latest published rates into a fresh draft, so you only touch the products that changed. Publishing the new version closes the previous one the day before the new date.
- A quote resolves the right rate for its city and date, and every price-book change is written to the audit log, so "who changed product X from ₹Y to ₹Z" always has an answer.
Tip
Set the validity rules once
Price locks that honour a quoted rate
Rates move, but a client you quoted last month should not be surprised by this month's book. A price lock authorises one exact customer + project + city to keep using a specific price-book version for a limited period, measured from a business event and bounded by the price policy's window.
The identity is deliberately strict: a lock is tied to the project, never to a name, mobile number or the customer's created date. The same customer's unrelated new project never inherits another project's lock, so old pricing cannot leak sideways. When a quote is created, Panzo resolves the price version automatically.
| Situation | Which price applies |
|---|---|
| A valid lock exists for this customer + project + city | The locked (old) version, with days remaining shown |
| No lock, or the lock has expired or was cancelled | The city's current active version |
| A different project for the same customer | Its own resolution; another project's lock is never inherited |
Locks are never deleted. Their lifecycle runs active to expired, cancelled or replaced, and every change is audited, so an expired authorisation stays explainable long after it lapsed. An admin can extend a lock within the policy cap; a request over the cap needs approval and changes nothing until it is granted.
Versioned terms, frozen on each quote
A quotation is a contractual document, so the terms it shows must not drift. In Control Panel, Quote Terms holds your terms and conditions as numbered versions with effective dates. A quote freezes the version in force at the instant it is sent, and shows those exact terms forever after.
| Quote state | What the quote shows |
|---|---|
| Draft | The current terms, live, so a working quote tracks the latest wording |
| Sent / approved / rejected / revised | The frozen snapshot, unchanged, even after newer terms take effect |
Open Quote Terms
In Control Panel, the card at the top says which version is in force.Publish a new version
Choose New Version, label it as the client will see it, set an effective date, copy the clauses forward and edit the copy. Future-dating works, so you can prepare terms in advance.Send the quote
Sending freezes the version in force onto that quote. A later edit to your terms raises a "this quote predates the current terms" note for you, but never swaps the document the client saw.
Note
A known edge
Key takeaways
- Price books are city-scoped and date-effective; published rates are immutable and every change is audited.
- You reprice by publishing a new version, which copies the last one forward so only changes need attention.
- A price lock honours a quoted rate for one customer + project + city, and never leaks to another project.
- The price policy sets, per city, how long a captured rate stays valid after each pipeline event.
- Terms are versioned and freeze onto a quote when it is sent, so you can always show what the client agreed to.