Isolated by the database
Every client’s rows are separated by PostgreSQL row-level security, and the app connects with a role that cannot bypass it. A bug in our code still cannot show your prices to another seller.
How it works
The exchange on the right is not a recording. It is the same arithmetic the real pricing engine performs — paise-accurate, tax in basis points — playing out as it would on your own number.
Mehta Packaging
online
What the books recorded
Step one
“rate for 12x12x8 box, 2000 pcs” is not a form submission. Ordder pulls it apart into the things a quote actually needs, and keeps what it learns across the whole conversation — so an answer given in message four is never asked for again in message five.
Matched against your catalogue, including the way buyers actually abbreviate things.
With the unit — and it knows nos, kg, sqft, mtr, quintal and the rest.
City, area or pincode, so the delivery charge is the right one.
When they need it, which often decides whether you want the order at all.
Size, grade, thickness, finish — whatever your catalogue says matters.
The single most important thing still missing — not a list of six. Asking one at a time is the difference between a conversation and an interrogation.
Step two
This is the part people are right to be suspicious about, so it is worth being exact. The language model reads the enquiry and works out which item is being asked for. It does not decide what that item costs.
Once the item is matched, the money is fixed arithmetic against your own settings: your rate, your GST slab, your delivery rule, your minimum order quantity. Money is held in whole paise, tax in basis points, so nothing drifts by a rounding error.
Where each number comes from
Step three
A negotiation, a product it cannot match, an unusual delivery — the deal goes to a named person with the whole thread attached, and they are told in the app and by email straight away. Not a silent queue somebody has to remember to check.
Turn it on and the AI drafts but never sends. Nothing reaches a buyer until you have read it. Plenty of sellers run this way for the first fortnight and then switch it off.
If a conversation is not converging, it escalates rather than looping. A bot that asks a fourth question has already lost the buyer.
Draft and archived catalogue items are invisible to it. If you have not marked something live, it will not be sold.
A reply that cannot be delivered is retried and surfaced in the app with the reason. No buyer message is ever quietly dropped — we have been burned by that and built against it.
Getting started
The Excel or CSV you already keep. Ordder works out which column is the rate and which is the GST slab, shows you exactly what it will save, and waits for you to confirm. A sheet with only a name and a rate is enough.
Your WhatsApp business number, an email address, or a form snippet for your own site. Any one of them is enough to start; most sellers add the others within a week.
Forward something a buyer actually sent you and watch what comes back. That is a more useful test than any demo we could give you.
Your data
Every client’s rows are separated by PostgreSQL row-level security, and the app connects with a role that cannot bypass it. A bug in our code still cannot show your prices to another seller.
Google Cloud, Mumbai region. Your catalogue, your buyers and your invoices stay in the country.
Your WhatsApp and Zoho tokens are AES-256-GCM ciphertext in the database, with the key held separately. A database dump on its own is worthless.
The full detail is in our privacy policy, including every sub-processor and what each one sees.
Upload your rate list, forward one real enquiry, read what it sends back. If it is wrong you will know immediately — and so will we.