Building material yards
“10 cement and 3 of sand” says neither bag nor cubic metre — but the unit is what makes the price. Tablia infers the unit from the item and from the context of the list, and returns the quote for the salesperson to check.
The customer asks three yards and buys from whoever answers first. How many times does your salesperson call back just to ask whether those are bags or cubic metres?
Book your demoBom Preço Yard
online
Good afternoon! I am pouring a slab, I need a quote for the basics.
Good afternoon! Send the list right here — text, a photo of the paper or a file.
40 type II cement 3 medium sand 2 aggregate 1 1500 hollow brick 8 cells 15 rebar 10mm 10 annealed wire
Got it. That is 6 items — I am checking them against the yard's stock now.
Quote #DB55 is ready. 5 of the 6 items; I marked the annealed wire as missing.
📄 quote-DB55.pdf
Can the sand be washed?
It can. Here is version 2 of #DB55 with washed medium sand; the previous one is now superseded.
📄 quote-DB55-v2.pdf
Illustrative conversation. Store, items and codes are examples.
None of the six lines states the unit. And each one has a different one: bag, cubic metre, thousand, length and kilo.
Store WhatsApp
Good afternoon! I am pouring a slab, here is what I need:
40 type II cement
3 medium sand
2 aggregate 1
1500 hollow brick 8 cells
15 rebar 10mm
10 annealed wire
07:12
What Tablia read
5 of 6 items found. Whatever is missing goes to the salesperson with the customer's original wording — nothing disappears from the quote quietly.
Illustrative example. The list and the catalogue names are fictional.
In a yard the order line is short. What is missing from it — the unit — is exactly what separates a correct quote from one ten times larger.
Forty bags of cement and forty cubic metres of cement are very different orders. Tablia infers the unit from the item and from the context of the other lines, shows the inference on screen and lets the salesperson correct it before the quote goes out.
The unit is the price
Bag, cubic metre, tonne and thousand. Getting the unit wrong does not get the item wrong: it gets the whole quote wrong.
Class changes the product
One cement class is not another, and aggregate 0, 1 and 2 do not do the same job.
Short order, narrow margin
A yard's list has few lines and little description. There is little text left for the search to get it right.
The list is read line by line, even when the line is two words and a number.
The unit comes from the item and from the context of the other lines: cement usually comes in bags, sand in cubic metres, bricks by the unit or the thousand.
Cement class, aggregate 0 and medium sand stay attached to the item, instead of becoming loose text that gets lost in the search.
“Type II cement” finds the TYPE II CEMENT 50KG in your catalogue even with different spelling. Alternative names are searched too.
An item your yard does not carry goes to the salesperson with the customer's original wording, instead of vanishing from the list.
The list can arrive as
Handwriting is the only one that does not go in — returning a wrong quantity that looks right is worse than refusing the file.
What you upload
The stock file your yard already uses, in CSV, XLS or XLSX. Tablia recognises the code, description and price columns with the help of artificial intelligence, and you check the mapping before it takes effect. The unit in your file is the one that counts — it travels with the product.
What it does with what it could not find
The item appears to the salesperson flagged as not found, with the customer's original wording. Tablia does not change the material class to find something similar. The decision is your team's: add it, propose an equivalent, adjust the quantity or say the yard does not carry it.
Nothing is sent to the customer automatically. The salesperson reviews item by item, adjusts quantities, swaps products, sets the price and decides when to send.
It is at that review that the inferred unit is confirmed — and in a yard that is the line between the right quote and one nobody can honour.
Tablia takes on
You decide
It infers the unit from the item and from the context of the other lines in the list, and shows the inference on screen next to the item. Cement usually comes in bags, sand in cubic metres. The salesperson confirms or corrects it before the quote goes to the customer.
It still works, because the search is by meaning and not by identical text. A short line leaves less to go on, and that is precisely why an item with no clear match reaches the salesperson flagged, rather than becoming a guess.
No, and it is better to say so now than in the demo. Tablia reads the quantity and the unit as the order came, and keeps both. Converting between selling units depends on each yard's standard, and that sum stays with the salesperson.
No. You upload the stock file you already have, in CSV, XLS or XLSX, and Tablia recognises the code, description and price columns with the help of artificial intelligence. You check the mapping before it takes effect.
It appears to the salesperson flagged as not found, with the customer's original wording beside it. It does not turn into a similar item and it does not vanish from the list. The decision is yours: add it, propose an equivalent, or say the yard does not carry it.
PDF, a photo in JPG or PNG, a spreadsheet in XLSX or XLS, a document in DOCX, CSV or typed text. The only one that does not go in is a handwritten list: Tablia does not accept handwriting, so it never returns a wrong quantity that looks right.
Never. Nothing is sent without the salesperson. They review item by item, adjust quantities, swap products, set the price and decide when to send. Tablia takes on the typing and the searching; the decision stays with whoever knows the job.
Vamos conversar
In the demo we use a list your yard received this week, against your own catalogue. It is the fastest way to find out whether Tablia can handle what you sell.
Book your demo