Good supply starts with a clear requirement.

The enquiry is read for what it actually says before anyone starts matching it to a product. What is stated, what is implied and what is genuinely unknown are recorded separately, because conflating the three is how a wrong part becomes plausible.

Where a requirement could be read two ways, both readings are noted rather than one being quietly selected. An enquiry that is ambiguous is not a poor enquiry — it is an ordinary starting point, and treating it as complete is the error.

Photographs, visible markings, vehicle details and configuration are used together rather than in isolation. Any one of them can mislead on its own; in combination they converge quickly. Where they disagree, the disagreement itself is informative and gets raised.

Identification ends when the requirement is specific enough that two people reading it independently would picture the same component. Until then it is still in progress, however confident the initial impression was.

Open questions go back to the buyer in one consolidated message. Not three messages over two days, and not a single question that reveals a second question once answered. Everything unresolved is put on the table together, so it can be answered in one sitting.

This is the stage buyers notice most, and the one that saves the most time. It also makes the state of the enquiry visible: if the clarification list is long, the requirement was less settled than it appeared, and it is better to know that before a commitment than after.

Once the product is settled, the practical terms are settled: how many pieces, by when, to where, and what documentation needs to travel with the goods. These are handled as part of the requirement rather than as an afterthought, because each of them can change what is workable.

Where a timeline cannot be met, that is said plainly at this stage. An honest constraint stated early is far more useful to a buyer than an optimistic one corrected later.

What is supplied is what was described and agreed — not a close equivalent substituted quietly because it was available. Where a substitution genuinely is the sensible option, it is proposed and agreed before it happens, never discovered on arrival.

What was sent is recorded in the same terms the requirement was written in, so the buyer can check the two against each other on receipt without translating between two vocabularies.

Silence during a supply conversation is read as a problem, and usually is not. Status is shared as it changes, and when nothing has changed, that is worth a line too. It costs almost nothing and removes the need for the buyer to chase.

The same applies after supply. If a question comes back about what was sent, it is answered against the record of what was agreed, not against memory.