When a Catalogue Heading Is Broader Than the Line Item: A Procurement Question

The enquiry that starts the question

Picture a fictional Singapore procurement desk handling a routine materials enquiry. A document arrives with a heading that reads like a product family, and beneath it a line that carries a seller-specific reference. The heading suggests one thing; the line suggests another. Nobody is necessarily wrong, but the two entries do not line up cleanly, and the buyer has to decide which one the supplier actually meant.

This is an administrative problem before it is a technical one. The heading is broad enough to cover several things, while the line is narrow enough to point at one. Until someone asks, the team is holding two possible readings of the same document.

San Techno Pte Ltd is a Singapore-based company working in semiconductor and solar materials, silicon recovery, specialized power module development, and botanical extracts under the ST GREEN brand. That breadth is exactly why a catalogue heading can be wider than a single line item: a company can legitimately work across several material families, and a heading may describe the family while the line describes one entry within it. The question in this guide is not what any product does, but which catalogue entry a supplier meant when the two do not match.

Why broad headings and narrow lines drift apart

A heading is often written for navigation. It groups related items so a reader can find a section quickly. A line item is written for identification. It points at one thing a seller recognises. When the two are produced by different people, at different times, or for different audiences, they can drift.

There is a documented reason this happens with brand names in particular. Material prepared for ST GREEN notes that results appear under the same products registered in different brands for different countries, and that brand names may differ to meet the registration needs of different national authorities. That is a brand-naming observation, not a statement about catalogue headings, but it illustrates the general pattern: the same underlying item can appear under more than one label depending on where and for whom the document was written.

For a procurement reader, the practical lesson is modest. A mismatch between heading and line is not automatically an error, and it is not automatically a red flag. It is a signal that the document needs one clarifying question before anyone records it as agreed.

The one question to ask

The goal is a single, answerable question that resolves the ambiguity without inviting a sales conversation. A workable form is:

"Your document lists [heading] as the section and [line reference] as the line. Which catalogue entry did you intend this enquiry to refer to, and should we record the heading or the line as the item under discussion?"

That question does three things. It quotes both entries so the supplier can see exactly what the buyer is looking at. It asks for a choice rather than an open description. And it asks how the reply should be recorded, which turns the answer into something the team can file.

Keep the question free of assumptions about specification, availability or price. The point is to fix the reference, not to open a negotiation. If the supplier answers with a third term that appears in neither the heading nor the line, ask them to map it back to one of the two entries before the team records anything.

A fictional administrative comparison table

The table below is an example of how a team might lay out the ambiguity for internal review. It is illustrative only. It contains no specifications, no prices and no supplier names, and it is not a template for evaluating any particular product.

Column one, Document entry: the heading as written. Column two, Line reference: the seller-specific line as written. Column three, Reading A: the enquiry is about the family described by the heading. Column four, Reading B: the enquiry is about the single item named in the line. Column five, Status: open until the supplier replies.

For a fictional semiconductor materials enquiry, Reading A might treat the heading as the subject and the line as an example within it. Reading B might treat the line as the subject and the heading as mere navigation. Both readings are internally consistent, which is precisely why the table records them side by side rather than picking one. The status column stays open, and the question from the previous section is logged against it.

The same layout works for a fictional solar grade silicon enquiry or a wafer reclaim enquiry, because the structure depends on the document, not on the material. What changes is only the wording of the heading and the line.

Recording the reply so it survives the week

A reply that lives only in an inbox is a reply the team will re-litigate. Record it in four short fields, kept next to the comparison table.

First, the question as sent, quoted in full. Second, the reply as received, quoted rather than paraphrased. Third, the resolution: which entry the supplier confirmed, stated in the supplier's own words with the team's reading alongside. Fourth, the date and the initials of the person who logged it.

Two habits keep this honest. Quote rather than summarise, because a paraphrase is where a heading quietly becomes a line item. And record the supplier's exact term even when it is awkward, because a later reader needs to match it against the original document.

If the supplier's reply is itself ambiguous, do not resolve it by inference. Send the question again with the reply quoted back, and ask for a one-line confirmation. A short second exchange is cheaper than a disputed record months later.

Where the same question recurs across a materials portfolio

The heading-versus-line question is not confined to one product family. A company that works across several material areas will naturally produce documents where a broad heading sits above a narrow line, and a procurement team that sources across those areas will meet the pattern more than once.

San Techno's own materials work spans silicon recovery from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, with those materials processable into reusable raw materials for solar wafers and cells. It also includes an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format, and an AC-to-DC Power Module Design offering. Each of these areas could plausibly appear under a family heading with a more specific line beneath it.

That breadth is a reason to keep the clarifying question generic. A team that has asked it once for a semiconductor materials enquiry can reuse the same wording for a power-module enquiry, changing only the quoted entries. The method travels; the document does not.

A short checklist before the enquiry moves forward

The following checklist is an author heuristic, not a researched standard. Treat the items as prompts rather than pass marks.

One: both the heading and the line are quoted exactly as written in the document. Two: the comparison table records both readings without preferring either. Three: the clarifying question asks which entry was meant and how to record the reply. Four: the reply is quoted, not paraphrased, and dated. Five: any third term introduced by the supplier is mapped back to one of the two entries. Six: the status field is closed only when a one-line confirmation is on file.

A team might reasonably run through this list in a few minutes for a simple enquiry, or hold it open across a longer exchange. The timings are examples, not benchmarks. What matters is that the record shows the question was asked and the answer was captured, so a later reader can see how the team arrived at its reading.

Keeping the question separate from the commercial conversation

It is tempting to fold the clarifying question into a broader exchange about the enquiry. Resist that where you can. A reference question and a commercial conversation have different success conditions: the first is settled by a clear answer, the second by agreement on terms. Mixing them makes the record harder to read and invites the reference question to be answered implicitly rather than explicitly.

Where a team does need to move from reference to substance, the product pages are the natural next stop, because they set out the families a heading might refer to. Reading them before drafting the question can help a buyer recognise whether the line sits inside the heading or alongside it. That recognition is administrative, not technical, and it does not settle which entry the supplier meant.

For direct follow-up on a specific enquiry, San Techno can be reached on the published phone and WhatsApp numbers. Keep the reference question and the contact separate in your notes, so the record of what was asked stays clean.