A supplier may put a UN/LOCODE on a logistics sheet to identify a trade and transport location. That code should not displace the street address and receiving instructions for the actual warehouse. The difference becomes particularly important when a buyer assumes that a location carrying a port function identifies a specific terminal. UNECE’s recommendation gives a direct reason to keep those fields separate.

What the official recommendation says about function

The UNECE UN/LOCODE recommendation, read on 3 October 2026, describes a location’s function attribute. It explains that function code 1 indicates that a port exists within the boundaries of the location; it does not mean the location code denotes only the port. This observation supports a narrow evidence boundary. It does not establish any supplier’s premises, a terminal assignment or the present operation of a transport connection.

Keep three identities in the delivery file

Record the supplier’s actual contracting identity, the intended receiving facility and the transport location as different items. A city or trade location can help logistics participants discuss routing while leaving the final unloading destination unresolved. Ask the supplier to connect the quoted delivery destination to a complete receiving-site record. A code copied from an unrelated shipping template should not become the approved address just because it looks standardized.

In a hypothetical order, a quotation might identify a transport location while an email names a different warehouse within that area. The buyer should retain both and request clarification about the physical handover point. This is a documentation example, not an account of a real shipment. No specific location record was queried for this article, so it provides neither a current code recommendation nor a verified route.

Make ambiguity visible to the logistics owner

When two documents use different names, do not silently normalize them into a single site. Ask whether one describes the wider location and the other a facility, or whether there is a genuine destination change. Retain the supplier’s answer and the date it was given. Actual route selection, transport availability and any contractual delivery interpretation belong to the responsible specialists. A geographic identifier cannot settle those questions by itself.

Recheck the relationship when the site changes

If the supplier moves stock to another warehouse, update the physical site evidence and check whether the transport-location field remains appropriate. Preserve the earlier record so past shipments can still be understood. Never describe a code as a warehouse audit, proof of inventory or delivery guarantee. The practical editorial judgement is to use UN/LOCODE for its location purpose and to require an independently identifiable receiving facility. That combination makes a purchasing file more useful without inventing facts about stock, custody, operational capacity or promised arrival.