Lista de comprobación para la recepción de azulejos: compruebe que coinciden los códigos de la orden de compra, los palés y las cajas antes de la instalación

A pallet of tiles arriving at a job site with the right label colors and a familiar-looking carton design tells the receiving team almost nothing on its own. The question that matters is whether every pallet and carton in the shipment can be traced back to the specific purchase order line that was approved for this project, before anyone breaks a strap or allocates boxes to an installation area.

Freeze the Receiving Reference Before Checking the Load

Before comparing anything physical against anything documented, the receiving team needs a single, fixed set of references that will not change mid-check. This matters because purchase orders get revised, packing lists get reissued, and item lists get updated as a supplier relationship moves from quotation to shipment. If the team checks the load against whatever paperwork happens to be on hand, rather than against the current, confirmed versions of these documents, a match can appear valid when it is actually a match against an outdated line item or a superseded revision.

The purchase order itself needs to be identified by its current number, line, and revision, not simply by a general awareness of “the order for this project.” Where a project has gone through sample approval or specification revisions, the receiving check should also confirm whether an approved sample or specification reference applies, since a catalogue description is not the same as an approved specification, and treating it as equivalent removes a layer of control the project relied on earlier in the process.

A supplier item list matters here because it defines the agreed codes and descriptions the shipment will be checked against; without it, a receiving team is left inferring compatibility from product names or visual similarity, which is a different and weaker basis for comparison. The packing list and invoice need their own identifiers and versions confirmed, since a packing list that has been reissued after a partial shipment or a correction will not align with an earlier version still circulating on-site.

Equally, the shipment or container reference anchors the physical delivery event to a specific movement, which becomes important once more than one shipment for the same project is in transit or has arrived close together. Finally, someone on the project side needs to be named as the decision owner for what happens next. Where this role is undefined, exceptions tend to sit unresolved because no one has the standing authority to direct segregation, escalation, or release. Fixing this reference set first means every later comparison in the receiving process is checked against the same fixed target, rather than against whichever document is easiest to find.

Match Shipment and Pallet Identities

Once the reference set is fixed, the next judgment is whether the physical pallets in front of the receiving team can be linked to that reference set at all. This is an identity question, not a quality question. A pallet identifier, whatever system it comes from, exists to connect a physical unit of goods to a body of information about that unit — its origin, its place in the shipment, and the documents that describe what should be inside it. GS1’s General Specifications describe this kind of unique logistics-unit identifier as a way to link a pallet’s physical movement to its associated information, though a project may instead be operating under another agreed pallet identification method established with its supplier. What matters for receiving is not which system is used but whether the identifier present on the pallet can be read, is unique within the shipment, and appears in the shipment register the team is checking against.

Recording the delivered pallet identifier exactly, rather than approximately, is what makes this check meaningful. A team that paraphrases or abbreviates what it sees on a label loses the ability to catch a duplicated or transposed identifier later. Three outcomes are possible at this stage: the identifier matches the register cleanly, the identifier is missing or unreadable, or the identifier is duplicated across more than one pallet. Each of these is a distinct condition requiring a different next step, and the difference matters because a missing label and a duplicated label point to different failure points in the shipment or labeling process.

What a successful pallet match does not do is confirm that the contents of that pallet conform to the order. Identity linkage answers “is this the pallet the shipment register says it is,” not “does this pallet contain what was ordered.” Treating a clean pallet match as evidence of product conformity skips the carton-level and code-level comparison that the identity check was only ever meant to enable.

Cross-Check Carton Codes and Quantities

With pallet identity established, the comparison moves inside the pallet, to the cartons themselves. This is where the frozen reference set from the first step gets applied in detail, because a project schedule typically specifies not just a supplier item code but exact shade, caliber, and batch codes, and a carton count expected per pallet. Each of these carries a different kind of risk if mismatched. A wrong supplier item code usually signals the wrong product entirely. A shade, caliber, or batch mismatch can mean the right product family arrived, but from a different production run than the one approved or than the one used elsewhere on the project, which raises the same kind of visual-consistency question a project addressed earlier through sample approval.

En U.S. International Trade Administration’s guidance on packing lists describes this document’s role clearly: it itemizes the contents of a shipment by package, along with quantities, marks, and dimensions, and it can be used to check the contents of a specific package or carton. That function is exactly what this comparison relies on — using the packing list as the itemized reference against which physical cartons are checked, rather than relying on carton labels alone to tell a complete story.

Codes on a carton label are only meaningful if their structure is known. Where a receiving team encounters a code format it has not seen before, or a code that appears similar to but not identical with what the schedule specifies, the correct response is to have the supplier explain what that code represents, not to assume compatibility because the text or color name looks close enough. ISO 13006, the ceramic tile standard covering definitions, classification, and marking, treats tile marking as a formal scope of product information, which supports treating carton codes as structured technical information rather than incidental labeling — though the standard’s public abstract does not define what any particular supplier’s codes mean in practice, so that explanation still has to come from the supplier directly.

Carton counts complete this check. A count that is short or over what the packing list and pallet schedule indicate is a distinct condition from a code mismatch, and the two should not be recorded as the same type of exception, since a quantity shortfall and a wrong-batch delivery lead to different resolution paths.

Separate Delivery Condition from Product Acceptance

A receiving check inevitably surfaces observations about physical condition — a torn carton wrap, a damp corner on a pallet, a label that has partially worn away in transit. These observations matter, but they answer a different question than the identity and code checks above. Condition describes what the shipment looks like on arrival; acceptance describes whether the project treats that shipment, or parts of it, as usable for the work ahead. Collapsing these two into a single judgment made at the loading dock removes a decision that belongs to people with more context than the receiving team typically has at that moment.

The practical discipline here is to record what is observed in neutral, descriptive terms — the location and nature of visible damage, which cartons are opened or wet, which labels cannot be read — without extending that observation into a conclusion about installation suitability, claim liability, or test conformity. A wet carton might indicate nothing more than surface moisture from handling, or it might indicate a condition that affects the tile inside; the receiving record cannot resolve that question by itself, and treating a visible condition as proof of a defect assumes a link that has not been established. Where the project has a documented process for shipping damage, photographs or other references should be preserved consistent with that process, but the receiving check itself is about capturing the observation accurately, not about adjudicating fault.

This separation matters most where multiple issues appear on the same pallet. A pallet with a torn wrap and a correct code match is a different situation from a pallet with an intact wrap and a batch code mismatch, even though both might get flagged during the same receiving pass. Recording them as distinct observations, rather than folding them into one general “problem” note, preserves the information the responsible parties will need to work through afterward. Whether a given condition affects performance, whether a shortfall becomes a commercial adjustment, and whether a code discrepancy requires supplier clarification are all separate decisions that depend on evidence and roles outside the receiving check itself.

Release, Segregate or Escalate by Recorded Status

Once identity, codes, quantities, and condition have been recorded, the receiving team is left with a status for each pallet or carton group, and that status determines what happens next — not as a final commercial or technical decision, but as a routing decision for what the material does while the substantive questions get resolved. Three general states tend to emerge from this kind of check. Material whose pallet and carton identifiers match cleanly against the frozen reference set can move forward to whatever the project’s next product and installation checks require; the traceability match supports that forward movement without itself constituting an installation approval. Material with an unresolved question — a code that needs supplier explanation, a count that needs reconciliation — should be kept physically identifiable and separate from material that has already cleared, so that a pending clarification does not get blended into stock that has already been confirmed. Material with a more significant exception, such as a batch mismatch affecting a meaningful portion of an order or damage that raises a real question about usability, needs to be escalated with its supporting evidence to the buyer, the supplier, and whichever other party the project’s process names as responsible.

Where a project treats these three states as genuinely distinct, rather than defaulting everything to either blanket acceptance or blanket rejection, the routing stays proportionate to what was actually observed. A clean identity and code match does not need the same handling as a code discrepancy, and a code discrepancy does not need the same handling as visible damage combined with a quantity shortfall. What this routing does not do is decide the underlying questions — whether a claim is warranted, whether disposal or return is appropriate, or whether installation can proceed on material still under clarification. Those outcomes depend on contract terms, insurance provisions, and evidence that sit outside the receiving check itself.

The value of the frozen record built through the earlier steps is that it does not get discarded once this routing decision is made. The same pallet-and-carton record that supported the initial traceability check becomes the reference the project uses when it allocates specific pallets to specific installation areas, and again if a code or quantity question resurfaces later — for instance when checking material against a product page such as the one for Porcelánico VGH2012001 during allocation planning. A receiving record built once, accurately, and kept intact carries forward into those later checks instead of requiring the same reconciliation work to be repeated from scratch.

Preguntas frecuentes

Q: Receiving has an earlier purchase order, but the shipment documents refer to a later revision. Which basis should the team use?
A: Confirm and freeze the current order line and specification revision before checking the load. Use that basis with the current supplier item list, packing list, invoice and shipment reference, and identify the project’s decision owner. An obsolete order or catalogue page cannot establish the approved comparison basis for this delivery.

Q: Every pallet ID matches the shipment register. Can the tile now be allocated for installation?
A: The pallet match confirms an identity link, not installation approval. Compare the carton items, exact shade, caliber and batch codes, counts and package marks with the frozen schedule and packing list. When traceability is matched, proceed to the project’s next product and installation checks using the same record for area allocation.

Q: We found an additional carton code with the same color description. Can we record it as equivalent to the expected code?
A: Keep the additional code exactly as observed and request the supplier’s explanation. Similar code text or color names do not establish shade or caliber compatibility. Link the affected cartons to their pallet and order line, and leave allocation or combination for the buyer’s project decision rather than merging the code groups in the receiving record.

Q: Some cartons arrive wet or opened. Does that prove the tiles are unacceptable or establish who is responsible?
A: It establishes an observed delivery condition, not a final acceptance or liability conclusion. Record the condition and its location, with photographs or references if the project uses them. Keep product suitability, test conformity and responsibility decisions separate for the relevant parties and evidence.

Q: How should a quantity difference or unreadable label affect the receiving handoff?
A: Record the specific exception and keep the affected cartons identifiable while clarification is pending. Show expected and observed counts for a quantity difference, or name the identifier that cannot be read. Escalate the evidence to the buyer, supplier or other responsible party; the project decides handling and release, while commercial adjustments and claims remain separate decisions.