A procurement thread usually gets messy at one exact point: someone copies a catalogue line into an email, names the model, and lets the supplier infer which of several available sizes was meant. The reply comes back as a price, and now two parties are talking about numbers that were never the same thing.

A cleaner structure is a four-column inquiry row. Each row is one pricing question, not one product.

model | selected size | finish | expected quantity

Illustrative input, not a real product record:

WY-XX | W1200 x D600 x H450 mm | finish code supplied by the supplier | 6

Expected result: the supplier can answer one row without guessing which dimension set, which surface treatment, and how many pieces are in scope. If any of the four cells is empty, that row is not ready to send.

Why the four columns and not one free-text line

The failure mode is not that people forget the model. It is that the model is the only thing they remember. A catalogue listing can show a product under a category such as coffee table, dining table, sofa, or dining chair, with dimensions, materials, and finish confirmed at inquiry. That means the model identifier alone is not a specification. It is an index into a specification you still have to pin down.

Edge cases worth testing before the row is trusted:

One model, several sizes. If the catalogue shows more than one size under the same model, each size gets its own row. Two rows with the same model and different sizes is correct. One row with a size range is not, unless the supplier has explicitly confirmed a range is orderable.

Finish not yet chosen. Leave the finish cell as a marked open item rather than writing a plausible word. A row with an invented finish will be quoted against the wrong assumption.

Unit unspecified. If a dimension in the source does not state its unit, do not convert it. Flag the axis and ask. Recorded values keep their units; when axis, dimension, or unit is unclear, it needs verification.

Quantity as expected, not final. Calling the number expected rather than confirmed tells the supplier it may move, which is honest and useful.

This Python 3 check takes one row exported from a sheet. Keep the dimension unit in its own field. If the selected size is a range, record separately whether the supplier has offered that range as an orderable option.

def missing(row): issues = [field for field in ("model", "size", "unit") if not row.get(field)] if not row.get("finish") and not row.get("finish_pending"): issues.append("finish") quantity = row.get("quantity") if type(quantity) is not int or quantity <= 0: issues.append("quantity") if row.get("is_range") and not row.get("range_confirmed"): issues.append("range_confirmation") return issues example = dict(model="WY-XX", size="W1200 x D600 x H450", unit="mm", finish="sample A", quantity=6) assert missing(example) == [] assert missing({**example, "unit": "", "quantity": 0}) == ["unit", "quantity"] assert missing({**example, "finish": "", "finish_pending": True}) == [] assert missing({**example, "is_range": True}) == ["range_confirmation"] 

A row with a marked pending finish can be sent as a question. It cannot be treated as a confirmed finish for ordering. The check only reports the named fields; it does not interpret a supplier’s dimension string.

What this workflow can and cannot establish

It can establish that the inquiry is internally unambiguous: one model, one size, one finish intent, one quantity. It cannot establish that the size fits the room, that the finish is available, or that the price will hold. Those are supplier and site questions. The four columns only remove the ambiguity that procurement itself introduces.

When the advice changes

If a supplier's own quotation form already forces model, size, finish, and quantity as separate fields, do not rebuild it as free text. Use their form and keep the four-column table as an internal check so the row you type into their system matches the row you reasoned about.

If the project is early enough that the size is genuinely undecided, the correct row is not a guessed size. Split it into two candidate rows and state that the choice is open. A supplier can price both; they cannot price a coin flip.

By Weiya