Why a Quantity Column Reads Differently to Purchasing and the Receiving Desk

The column that quietly splits into two meanings

A quantity column looks like the least controversial part of a materials document. It is a number, a unit, and a heading. Yet the same field can be read two ways depending on who opens the file. Purchasing tends to read quantity as the commercial unit it is buying: a box, a cassette, a tray, a carton, a pallet. The receiving desk tends to read quantity as the thing it must count, scan or place on a shelf: individual wafers, individual modules, individual pieces.

Neither reader is careless. Each is answering a different question. Purchasing is asking what was ordered and what will be invoiced. Receiving is asking what physically arrived and what must be recorded against the delivery. When one column serves both questions without saying which one it answers, the number is technically correct and practically ambiguous.

This guide uses a fictional table to show the problem and a small set of fixes: a clearer header, one sample row, and a short cross-check step. The table is invented for illustration. It does not describe any real order, shipment or supplier arrangement, and nothing here implies that a particular service, collection or delivery will take place. The aim is a document that two different desks can read the same way.

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 identity is context for the examples, not a claim about how any specific transaction will be handled.

A fictional table where the number means two things

Imagine a short table with four columns: Item, Description, Quantity, Unit. The row reads: Item A-17, Description "reclaimed wafer lot", Quantity 25, Unit "box".

Purchasing reads this as twenty-five boxes. That is the commercial unit. It matches the purchase order line, the price basis and the invoice. The buyer is comfortable.

The receiving desk reads the same row and sees twenty-five. It looks for twenty-five things to count. If each box holds a cassette and each cassette holds a stack of wafers, the receiver may count twenty-five cassettes, or twenty-five wafers, or twenty-five boxes, depending on what is physically in front of them and what the word "box" seems to point at. The number 25 has not changed. The object being counted has.

The ambiguity is not in the arithmetic. It is in the missing noun. "Quantity" does not say quantity of what. "Unit: box" helps, but only if the reader already knows that the box is the purchasing unit and not the counting unit. A receiver who has never seen the commercial paperwork has no reason to know that.

This is the core of the problem. One field is carrying two jobs: the commercial quantity and the physical count. A single number cannot reliably do both unless the document says so explicitly.

Why purchasing and receiving read the same field differently

The two desks sit at different points in the same process, and each has a legitimate reason to interpret quantity in its own way.

Purchasing works from commitments. Its reference points are the enquiry, the quotation, the purchase order and the invoice. In that world, quantity is a commercial unit because that is what gets priced, approved and paid. A buyer who changes the basis of a quantity mid-process creates reconciliation problems downstream, so purchasing tends to protect the commercial reading.

Receiving works from physical evidence. Its reference points are the delivery note, the carton, the label and the shelf. In that world, quantity is a count of things that can be seen and handled. A receiver who records a commercial unit without knowing the physical count has not really received anything; they have only acknowledged a document.

The gap widens when the two desks never compare notes. Purchasing closes its part of the file once the order is placed. Receiving opens its part when the delivery arrives. If the only shared artefact is a table with an ambiguous quantity column, each desk fills the gap with its own assumption, and both assumptions can be reasonable while still being incompatible.

A useful way to think about it: purchasing is reading a promise, and receiving is reading a parcel. The same number can describe both, but only if the document separates the promise from the parcel.

Fix one: make the header say what is being counted

The first and cheapest fix is the header. Replace a bare "Quantity" with a header that names the unit and the counting basis. For example: "Quantity (boxes, commercial unit)" and a second column "Contents per box" or "Count basis".

The point is not to add columns for their own sake. The point is to make the noun visible. A header that says "Quantity (boxes)" tells the receiver that the number refers to boxes, not to the wafers inside them. A separate field for the count basis tells both desks how the box relates to what is inside.

Where a document must stay short, a single well-worded header can carry most of the load: "Quantity (commercial units, see count basis)". It is less elegant than a clean two-column layout, but it removes the silent assumption that has been causing the mismatch.

A practical test is to hand the revised header to someone who has never seen the document and ask them what they would count. If they hesitate, the header is still doing too little work. If they can say "I would count boxes, and here is where I find the contents", the header is doing its job.

This is author guidance, not a standard. Different teams will word it differently, and that is fine as long as the noun is explicit and the two desks agree on it before the first delivery.

Fix two: add one sample row that shows both readings

A header can still be misread. A single sample row, placed directly under the header, removes most of the remaining doubt because it shows the two readings side by side in a concrete example.

A fictional sample row might read: Item A-17, Description "reclaimed wafer lot", Quantity (boxes) 25, Contents per box 1 cassette, Count basis "cassettes". The receiver now knows that twenty-five boxes means twenty-five cassettes, and that the cassette is the unit to count at the dock. Purchasing still sees twenty-five as the commercial unit that matches the order line.

The sample row does something a header cannot: it demonstrates the relationship rather than describing it. A reader who is unsure can copy the pattern for the next line. A reader who is in a hurry can glance at the example and move on.

Two cautions are worth stating. First, the sample row should be clearly marked as an example, so no one mistakes it for a real line item. Second, the example should use neutral placeholder text rather than a real item code, so it does not accidentally become a record of an actual order.

Where the material is wafer-based, the sample row is a natural place to show how packaged inventory relates to handling, storage, packing and shipment preparation. San Techno's public materials describe real material views from wafer handling, storage, packing and shipment preparation, and a sample row that mirrors those stages helps both desks see where the count actually happens.

Fix three: a short cross-check step before the file closes

Headers and sample rows reduce ambiguity, but they do not remove the need for a human check. A short cross-check step, done once per delivery, closes the loop.

The step can be as simple as three questions asked by the receiving desk and answered against the purchasing record: What commercial unit was ordered? What physical unit arrived? Do the two reconcile through the stated count basis? If the answers line up, the file can close. If they do not, the discrepancy is raised before anything is signed off.

A suggested timing, offered as an example rather than a rule, is to run the cross-check at the point of receipt, before the delivery note is filed. Doing it later means the physical evidence may already be unpacked, moved or mixed with other stock, and the check becomes a memory exercise rather than an observation.

A second suggested habit is to record the cross-check result in one line, for example "25 boxes received, 25 cassettes counted, basis matches". That single line gives both desks a shared reference and makes the next audit or reconciliation easier.

These are author heuristics, not established research. Teams should adapt the timing and wording to their own workflow. The principle is what matters: the two readings of the quantity column should meet at a defined point, not drift apart until someone notices a mismatch weeks later.

Where this fits in a materials workflow

The quantity column is a small artefact, but it sits at the junction of two workflows that often run on different clocks. Purchasing moves at the pace of approvals and orders. Receiving moves at the pace of deliveries and dock schedules. A document that respects both clocks is easier to trust.

For teams working with semiconductor and solar materials, the stakes are practical rather than dramatic. A miscounted lot creates reconciliation work, delays shelf placement and complicates the next conversation with the supplier. A clearly worded quantity field, a sample row and a short cross-check reduce that work without changing the underlying commercial arrangement.

San Techno's public materials describe silicon wafer reclaim services as one of its areas of work, alongside semiconductor silicon materials and AC-to-DC power module design. For readers who want to understand how reclaim fits into a materials programme, the wafer recycling services page is a useful next stop. The same discipline applies there: a document is only as clear as its least ambiguous field.

Where silicon recovery is part of the picture, San Techno's public description notes that it helps recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, and that these materials can be processed into reusable raw materials for solar wafers and cells. That context is why the receiving desk's count matters: the physical unit is the thing that eventually re-enters the value chain.

A short checklist to hand to both desks

The following checklist is offered as an example, not a standard. It is short enough to paste into a handover note and specific enough to settle the question before a delivery arrives.

One: does the header name the unit and the counting basis? Two: is there a sample row that shows both the commercial reading and the physical reading? Three: is the sample row clearly marked as an example and free of real item codes? Four: is there a named point at which the receiving desk cross-checks the count against the purchasing record? Five: is the cross-check result recorded in one line?

If all five answers are yes, the quantity column is doing its job. If any answer is no, the fix is usually small: reword a header, add a sample row, or agree on a cross-check point.

The wider lesson is that a quantity column is not a neutral field. It carries an assumption about what is being counted, and that assumption belongs to whoever wrote the document. Making the assumption visible is the whole task. Once it is visible, purchasing and the receiving desk can read the same number and mean the same thing.

For teams that want to discuss how a materials programme handles these handovers, San Techno can be reached through its published contact channels. The conversation is usually more productive when both desks are in the room.