Linkubit
GuidePublished 19 September 2026 · 5 min read

Why an AI should quote prices only from a catalogue: the four ways prices go wrong in a chat, and the four rules that stop them

A document out of date, a customer's number agreed to, a sum the model did, a listed price called custom — each happened. One authority, attached in code; a verifier on every reply; deals and payment requests priced from the catalogue, never the chat.

What does the Growth plan cost?
CatalogueGrowth plan₹998 / monththe only price it may quote
Growth is ₹998 a month, billed monthly. Want me to send the payment link?Agent
Price verified against the catalogue before sending
In short

An AI that talks to customers should quote prices only from a catalogue the business controls — never from a document that might be out of date, never from the chat, never from its own reasoning. The catalogue is the authority; the AI attaches it to every answer that touches a product; a verifier refuses a reply that states a price the turn did not retrieve; and a deal or a payment request is priced from the catalogue, not from anything the model wrote.

On this page
  1. How prices go wrong
  2. The four rules
  3. Discounts, negotiation, custom quotes
  4. What the customer experiences

How prices go wrong

  • A document says something the price list no longer does. The brochure PDF from March says ₹998; the plan is ₹999 now. The AI answers from the document, because that is where it looked.
  • The customer says a number and the AI agrees. "So it's ₹500?" — "Yes." Now there is a quote in writing.
  • The AI reasons its way to a price. Two items at ₹1,200 with 10% off: the model does the sum, gets it right most of the time, and the exception is a promise.
  • The AI is asked and does not know, so it says "custom". A product with a listed price described as priced on request — a customer who would have bought, sent to a form.

Each of these happened, in a real product or a real conversation, and each is why the catalogue has to be the only place a price comes from.

The four rules

  1. One authority. Products, variants, prices, in one catalogue the business edits. Documents may describe a product; they may not price it.
  2. Attach the catalogue to every answer that touches a product. In code, not by asking the model to look: if the question or a passage names a product, the product's record — with its price — is put in front of the model first. A document that disagrees is out of date and the instruction says so.
  3. Verify the reply. A price in the reply that the turn did not retrieve from the catalogue is refused before it sends. The model cannot state a number it did not look up.
  4. Price the money things from the catalogue, never from the chat. A deal's value is the catalogue price of the products the customer showed interest in. A payment request is catalogue price times quantity; an amount the model writes into the request is ignored.
Linen shirt₹2,450
Cotton kurta₹1,890
Silk stole₹3,200
Here’s the linen shirt — ₹2,450, in sage, white and sand. Which size?Agent
The catalogue is what the agent reads: a product, a price, a picture it may send.

Discounts, negotiation, custom quotes

A discount is a rule a person wrote — "10% for orders above ₹10,000" — and the AI may apply it because the rule, not the model, holds the number. A negotiation is a handover: the customer who asks for a better price gets a person, with the fields filled. A custom quote — freight rates, a bespoke itinerary — is typed by a person into the record and sent as a template, and the deal opens at that number because a person decided it. A rep may always type a custom amount into a payment request; the AI may not.

In Linkubit

The catalogue is the tenant's products with their own fields; a product's long description is a knowledge document, so retrieval and citation are the same as for any document. The knowledge tool attaches every listed product an answer touches, first, and answers from the catalogue alone when no document matches. The verifier allows a price in a reply only when the turn retrieved it. Deals open at catalogue prices; payment requests are priced from product keys and quantities; and the agent may draft a catalogue change for a person to approve, and never make one — an editable catalogue would be an agent that writes a price and then quotes it as authoritative.

What the customer experiences

A straight answer. "The Linen Kurta Set is ₹2,499, in stock in M and L, delivered to Pune by Thursday" — with the picture — in the first minute. Not "pricing varies", not a form, not a number that a person has to walk back tomorrow. That is most of what a customer wanted from the conversation, and it is only possible when the number is one nobody has to check.

Can the AI give a discount?

Only one a person defined as a rule. It cannot invent one, and a customer who asks for more is handed to a person.

What if a product's price is not in the catalogue?

The AI does not quote it. It says the price will come from the team, captures what the customer needs, and a person prices it.

What if my brochure and my catalogue disagree?

The catalogue wins, in code: it is attached first, and the instruction tells the model a document that disagrees is out of date. Fix the brochure when you can; the customer got the right number either way.

Two pallets Mumbai → Chennai, door to door, by Friday: ₹12,500 from the rate card. Shall I send the payment request?Agent
Yes, go ahead.
Order · Sai Traders
Freight BOM → MAA · 2 pallets₹12,500
Pay with UPI
to your account · never ours
Paid ₹12,500 by UPI · deal won · attributed to Meta lead form
A payment request is priced from the same catalogue — the number in the chat is never the number that is charged.

Read next

Try it on your own number. Linkubit answers, qualifies and quotes on WhatsApp from your catalogue, and adds nothing to Meta’s per-message price. Start free — fourteen days of Pro, no card — or read the pricing.