Quoting in Zoho CRM: Price Books, Approval Rules and Blueprint

Quoting is where most CRM implementations quietly stop being a CRM. The pipeline is maintained, the deals are tracked — and then the actual quote is built in a spreadsheet, approved over a message, and emailed as a PDF nobody can trace. Everything the CRM knows about that deal stops at the moment it matters most.

Price books: the feature most estates never switch on

A price book is a named list of products with their prices, attached to the customers or segments it applies to. Once it exists, the rate on a quote is chosen rather than typed, and the difference between list price and quoted price becomes a number the business can see instead of a story someone tells at month end.

Multiple books are normal: domestic and export, distributor and direct, annual and monthly. What matters is that each one is owned by someone who is accountable for the prices in it.

Approval rules, and why they beat approval habits

An approval rule is a condition and a route: when the discount exceeds a threshold, when the value passes a limit, when a payment term is non-standard, send it to this role for a decision. Two properties make it worth configuring:

• It routes to a role, not a person. Approvals do not stop because someone is travelling.
• It leaves a record. Who approved what, when, and on what basis — available a year later without asking anyone to remember.

Blueprint: the stage-by-stage version

Where approvals are less about a threshold and more about a sequence, Blueprint is the CRM feature designed for it. A Blueprint defines the states a record may be in, who may move it between them, and what must be true before it moves. It is the difference between a stage field that anyone can set to anything and a process the system actually enforces.

Templates, and why the PDF matters more than it should

The quote document is often the only artefact a client keeps. Quote templates in CRM control the layout, the terms, the branding and the fields that appear — which means the same deal produces the same document regardless of who built it. Estates that leave this to individual salespeople end up with three versions of the company’s terms of business in circulation.

The handover to finance

The value of the connection is not speed — it is that the figure on the invoice is provably the figure that was approved, because nobody typed it twice.

Frequently asked questions

Should quotes be raised in CRM or in Books?

In CRM, in almost every case. The quote is a commercial conversation attached to a deal; Books picks it up once it becomes a financial document.

Do approval rules slow the sales team down?

Only when the thresholds are set too low. Most teams find that a well-set threshold approves the majority of quotes automatically and routes the genuine exceptions in minutes rather than days.

Can approvals happen on mobile?

Yes — approvals surface in the CRM mobile app, which is usually what turns a two-day delay into a two-minute one.

What about quotes that need a signature?

Zoho Sign attaches to the process, so the accepted quote comes back signed and stored against the record rather than as a scan in someone’s inbox.

Where to start

Look at the last twenty quotes your team sent and check two things: whether the price came from a price book, and whether any approval left a record. Wherever the answer is no, the CRM already has the feature that fixes it.

References

Topic inspiration: the sales and CRM coverage on the Zoho Blog. This article is Kelevo Software’s own analysis and wording, written from our implementation experience; no text has been reproduced from Zoho’s publications.