A practical guide for Singapore procurement teams on filing semiconductor materials enquiries when two product family names look alike but describe different supplier offerings, including when to pause for written clarification.

Why similar family names cause trouble in a semiconductor materials enquiry

Two product family names can look almost identical on a screen and still describe different things. In a semiconductor materials enquiry, the risk is rarely a dramatic error. It is a quiet one: a line item gets copied from an older spreadsheet, a supplier reply uses a shortened name, and the file now holds two labels that seem interchangeable but are not.

The practical answer is to treat the family name as a filed record, not a passing phrase. Before you compare prices or quantities, write down the exact name as the supplier stated it, the document it came from, and the date. If a colleague later shortens it, the original wording is still recoverable.

This matters because suppliers describe their own ranges in their own words. San Techno, a Singapore-based company, presents its work across semiconductor silicon materials, silicon wafer reclaim services and AC-to-DC power module design as distinct branches rather than one blended catalogue. That structure is a useful reminder: when a supplier separates its offerings, your enquiry should mirror that separation instead of flattening everything into one generic label.

A simple filing habit helps. Give each family name its own row, its own source reference and its own status. Do not let a similar-looking name inherit the history of the first one. If the two names turn out to be the same family, merging them later is easy. Untangling a merged record after a quotation has been issued is much harder.

A fictional comparison: two labels, one spreadsheet row

Consider a fictional example. A procurement team is assembling an enquiry for semiconductor materials. One internal list carries the label "silicon materials, reclaimed" and another carries "reclaimed silicon wafers." On a busy day these read as the same thing, so someone merges them into a single row and sends one request.

The supplier replies with two separate descriptions. The first concerns recovered silicon material that can be processed into reusable raw materials for solar wafers and cells. The second concerns a reclaim service applied to wafers themselves. The team now has one outgoing question and two incoming answers, and no clean way to tell which answer belongs to which internal need.

A better fictional version keeps the rows apart. Row A records the material-oriented need and cites the passage about reusable raw materials. Row B records the service-oriented need and cites the reclaim service description. Each row carries its own question, its own quantity basis and its own clarification status. When the replies arrive, each one is filed against the row it answers.

The lesson is not that one label is correct and the other wrong. It is that a family name should carry enough context to survive being read by someone who was not in the original conversation. A name plus a source plus a one-line description does that. A name alone does not.

Building the enquiry file so similar names stay separate

A workable enquiry file has a small number of fields, applied consistently. The exact supplier wording comes first, copied rather than paraphrased. Next comes the source: which quotation, catalogue page or email introduced the name. Then a short plain-language note on what the family appears to cover, written by your team and clearly marked as your interpretation. Finally, a status field that records whether the name is confirmed, provisional or awaiting clarification.

Keep the status field honest. A name that appears only in a verbal call is provisional. A name that appears in a written supplier document is stronger, but it is still not confirmed until the supplier has agreed it refers to the item you intend to buy. Marking a provisional name as confirmed because the enquiry is urgent is how similar names drift back together.

Group related destinations by reader intent rather than by alphabet. If your team is sourcing material, keep material rows together. If the need is a service applied to existing wafers, keep that separate. If the need is a power module, it belongs in its own group, because module enquiries ask different questions about thermal behaviour and assembly than material enquiries do.

Finally, date every entry. A family name that was accurate last year may have been renamed or re-scoped. A dated record lets you see which entries need refreshing before the next round of questions goes out.

When to pause and ask for written clarification

Not every ambiguity needs a pause. If the two names clearly refer to the same family and the supplier has used both in the same document, note the equivalence and continue. The pause is warranted when a wrong assumption would change what you are asking for, not merely how you describe it.

Three signals justify a written clarification. First, the two names would lead to different questions about quantity, form or handling. Second, the supplier has used one name in a quotation and a different name in a specification, with no stated link between them. Third, an internal colleague has already merged the names and cannot point to the document where the merge was justified.

When you pause, ask a narrow question. Instead of "please clarify your product range," ask whether the name used in the quotation refers to the same family as the name used in the specification, and request a one-line confirmation. Narrow questions get usable answers. Broad ones invite a brochure.

Record the pause in the file. A row that is waiting on clarification is a distinct state, and it should look different from a row that is approved or rejected. That way nobody chases a supplier for a price on an item whose name is still unsettled.

Where power modules and biological products fit the same discipline

The same naming discipline applies outside silicon. A power module enquiry and a botanical extract enquiry can both suffer from collapsed labels, even though the products have nothing else in common.

On the power side, San Techno is developing an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format. The programme addresses heat movement, package stability and reliable operation under repeated electrical and thermal loading. Detailed architecture, materials, dimensions and assembly processes remain confidential. For a buyer, that confidentiality is itself a filing instruction: do not invent a family name for a module detail the supplier has not published. Record what is stated and mark the rest as not disclosed.

On the biological side, San Techno is the brand owner of ST GREEN, a botanical concentrate derived from plant, seed and vegetable-oil extracts that can be blended into four-in-one agricultural formulations. ST GREEN R26 is described as liquid biological extracts for making all bio products. A buyer filing an extract enquiry should keep the brand name, the product name and the formulation description in separate fields, because a shortened brand reference is not the same as a product reference.

The common thread is restraint. Use the supplier's own words, keep each family in its own row, and let a written clarification settle anything that would otherwise be guessed.

A short checklist for the next enquiry

The following checklist is an author heuristic, not a researched standard. Treat the scoring as an example of how a team might review its own file.

One: every family name is copied exactly from a named source. Two: each name has a dated entry. Three: each name has a plain-language note marked as your team's interpretation. Four: no two similar names share a single row unless a written document links them. Five: every provisional name has an owner and a next action. Six: any pause for clarification is visible as its own status. Seven: confidential areas are marked as not disclosed rather than filled in with assumptions.

A team might score each item as met, partly met or not met, and review the file before sending. The score is a conversation aid, not a certification. Its value is that it forces someone to look at the similar names side by side before they leave the building.

If the file passes, send the enquiry with the family names intact. If it does not, fix the rows first. The cost of a short delay is usually smaller than the cost of a reply that answers a question you did not mean to ask.

Keeping the file useful after the reply arrives

The enquiry file does not stop being useful when the reply lands. It becomes the record that explains why you asked what you asked.

File each reply against the row it answers, not against the sender. If a supplier answers two rows in one message, split the content and cite the message once in each row. If a reply introduces a new family name, add it as a new row with its own source and status rather than overwriting the old one. Old names are evidence of how the conversation developed.

When the enquiry closes, keep the file. A later order, a repeat request or a handover to a colleague all depend on someone being able to see which name meant what. A closed file with clear rows is a small asset. A closed file with merged labels is a small liability.

For teams that want to see how San Techno presents its own branches, the products page is the natural starting point. Read it as a supplier's own description of its families, and use it to check whether your internal labels match the way the supplier separates its work. Where they do not match, that is exactly the moment to pause and ask for a written clarification.

Separating Similar Product Family Names in a Semiconductor Materials Enquiry