How Kabaido structures requests

Whatever you send, Kabaido turns it into a structured result you can read at a glance and act on. The heart of it is a table of line items, one row per thing the customer is asking for.

Intent

Kabaido reads what the customer wants overall: a quote, an order, a service request or information. The intent decides which action card you are offered at the end. When the wording genuinely reads two ways, a warning chip says so and you choose the mode.

Typed line items

Each line carries a description, a quantity, a unit of measure and a domain classification. Attributes such as material, diameter or coating are pulled out into their own typed fields rather than left buried in prose.

Normalised units

Measurements are normalised to consistent units so lines compare cleanly, and the original wording is kept alongside. Abbreviations are expanded to their full meaning.

Every value is cited

Each attribute records the exact place in your request it came from, the source span. You can trace any value back to the text or cell it was read from, so nothing is taken on trust.

What normalising actually does

An enquiry is written in the shorthand of the trade that wrote it. The same dimension arrives as 12mm, 12.0, 12 dia, Ø12 and 1/2in depending on who typed it and what they had open. The same coating arrives as TiAlN, AlTiN, alicrn and "the purple one". Normalising means the typed field holds one canonical value in one canonical unit, so lines compare, filters work and a formula can read it.

The original wording is kept beside the normalised value rather than replaced by it. That matters when somebody queries the quote: the answer to "where did 12.7 come from" is "the customer wrote 1/2in, here is the line".

Missing means a question, never a guess

If a value is not stated, Kabaido leaves it empty and raises a clarification instead of filling the gap. It will not invent a specification, tolerance, price or part number.

This is the single rule that decides whether the output is usable without re-reading the original. If gaps were filled with plausible values, every line would have to be checked against the source before it could be trusted, and checking every line is the work the platform was supposed to remove.

The whole specification, not only the half that was written down

Every line names the full set of parameters its product type is specified by, and marks the ones nobody stated as not stated. A tool line that read a diameter and a flute count says so, and says in the same breath that the cutting length, the end type and the coating are still open. Without that you cannot tell a complete line from a thin one until the quote comes back wrong.

Only parameters your own catalogue schema carries are listed, because a parameter your products do not hold is a question nobody can use the answer to.