When one purchase order arrives as several production runs, the buyer’s real question is not whether the tiles look acceptable on top of a pallet, but whether each run can be verified on its own terms before it enters the project. A single PO number does not make a single lot, and treating it that way can push shade or dimensional differences into the field where they are hardest and most expensive to separate.
Split the Order Into Declared Production Runs
The first judgment a buyer has to make is whether the order is being treated as one homogeneous lot or as a set of distinct production runs that happen to share a purchase order number. These are not the same thing. A production run reflects a specific manufacturing event — a defined firing, batch of raw materials, or production window — while a purchase order is a commercial instrument that can span several such events without saying so. Керамічна плитка — Частина 1: Вимоги до випробувань та оцінки places batching before sampling and inspection, which means the sequence a buyer should expect is: first the material is divided into declared, identifiable lots, and only then is sampling and inspection performed against those lots. If that sequence is reversed or skipped — if sampling happens against an undeclared mixture of runs — the resulting inspection result describes a population that does not correspond to anything physically traceable later.
This matters because the consequence of an undeclared split shows up downstream, not at the moment of order confirmation. Where an order is produced in a single run, one sample and one inspection record can reasonably stand for the whole quantity. Where an order is produced across several runs, that same single sample and single inspection record can only ever describe the run it was drawn from, and extending its conclusions to the rest of the shipment is an assumption, not a verified fact. The buyer’s task at this stage is not to accept the supplier’s aggregate quantity and delivery date at face value, but to ask directly: how many production runs make up this order, and what quantity, pallets, and carton groups belong to each one? Without an answer to that question, every subsequent step — sample comparison, inspection scope, area allocation — is built on an undefined foundation.
The condition that changes this judgment is order size relative to a single production run’s typical output. A small order may be fully covered by one run without any split occurring; a larger order, or one placed against tight scheduling, is more likely to require the supplier to draw from more than one run to meet the requested quantity and date. The buyer cannot assume which situation applies without asking, and the supplier’s declaration — not the buyer’s inference from box counts — is what establishes how many runs are actually in play.
Request Run-Level Identity and Packing Evidence
Once the order is understood to include more than one declared run, the next judgment is whether each run can be identified physically, not just described on paper. Identity evidence and packing evidence serve different purposes and both are needed. Identity evidence — a code legend explaining what each character or field in a batch code represents — tells the buyer how to read a label. Packing evidence — the mapping of pallets and cartons to a specific run — tells the buyer where that identified material physically sits within the shipment. One without the other leaves a gap: a buyer who can decode a batch label but cannot connect it to specific pallets still cannot segregate material if a problem is found in one run.
Технічна документація компанії RAKO shows that production batches are identified across client documents, pallet labels, packages, and delivery notes, and that batches identified this way may differ from one another in shade and in dimensions. This is a manufacturer-specific illustration of a general point: batch identification systems are not standardized across suppliers, and a code format from one supplier cannot be assumed to apply to another’s. A buyer receiving a shipment with batch codes on the cartons needs the supplier’s own legend to interpret those codes correctly — which field indicates shade, which indicates caliber or size, which indicates the quality grade — because guessing at the structure risks treating two different runs as identical or two identical runs as different.
The condition that changes how much of this evidence matters is how the order will be installed. Where a project uses material from a single run across a small area, a coarse identification (run number alone) may be sufficient. Where multiple runs will be present in inventory or across a larger project footprint, the buyer needs the finer packing-level mapping, because the practical unit of action during installation or a later claim is the pallet or carton, not the abstract run number.
| Evidence item | Connect it to | Decision it supports | Межа |
|---|---|---|---|
| Run or lot declaration | PO line, product and quantity scope | Defines the units being compared and sampled | Supplier definition must be explicit |
| Supplier code legend | Shade, caliber/size, quality and batch fields | Makes labels interpretable | Code format is not universal |
| Pallet and carton mapping | Each declared run and packing record | Locates and segregates material | Mapping does not prove physical conformity |
| Run-linked sample record | Sample origin and approved comparison basis | Supports a bounded physical comparison | One run’s sample does not represent another |
| Inspection or test evidence | Named run, method/reference and result | Supports the stated inspection decision | Scope must not exceed sampled or tested material |
| Area and replacement allocation | Project location and retained stock | Controls visual continuity and later retrieval | Final suitability remains a project decision |
Tie Every Run to Samples and Inspection Results
Identity evidence tells the buyer what a run is called and where it sits in the shipment; it does not tell the buyer what that run actually is in physical terms. That connection has to come from linking each declared run to the specific samples drawn from it and the specific inspection performed on those samples. ISO 10545-1 supports a batch-linked sampling and inspection basis — meaning the standard’s logic assumes sampling is performed against a defined lot, not against an order as a whole. A sample drawn from one run and an inspection report describing results for “the order” or for an unnamed combined population cannot be read as evidence about every run in that order, even if the report’s language suggests otherwise.
The mechanism behind this is straightforward: physical variation in raw material, glazing, or firing conditions is what separates one production run from another in the first place. If that variation did not exist, there would be no reason to declare multiple runs at all. Sampling exists to characterize that variation within a defined population. When the population sampled is smaller than the population being shipped — for example, when one run is sampled and its result is applied to the whole combined order — the inspection record no longer describes what it claims to describe. This is not a hypothetical concern; it is the direct consequence of separating an order into multiple runs and then failing to keep the sampling and inspection records aligned to that separation.
For the buyer, the practical requirement is to obtain, for each run, a record showing which samples were taken from that run, what inspection or test was performed, which method or reference was used, and what result was obtained. Where a supplier can only produce one inspection record covering an unspecified mixture of pallets, that record should be treated as evidence about the sampled material only, not about the full shipment. The condition that changes the acceptable scope of a single inspection record is whether the runs it might cover are known to be materially similar — same raw material batch, same production window — or whether they are genuinely distinct production events; the buyer cannot assume similarity without the supplier’s own run declaration confirming it.
Allocate Runs to Project Areas and Replacement Stock
Even where every run has been identified and linked to its own sample and inspection record, a separate judgment remains: how should material from different runs be assigned to different parts of the project? This is a project-layout decision, not a technical one, and it depends on visual intent as much as on physical measurement. RAKO’s product guidance advises against combining differently identified shade or declared size on the same surface, which reflects a general principle applicable beyond any single manufacturer: where a continuous visual field is intended — a single floor plane, a single wall elevation — introducing material from more than one run into that field creates a risk of visible discontinuity that a run-level inspection record alone cannot rule out, because inspection samples represent a run’s population and do not guarantee that every piece within a run is visually indistinguishable from every piece in another run.
The condition that governs this decision is the continuity of the visual field itself. Where a project’s areas are naturally separated — different rooms, different floors, distinct sections divided by transitions — assigning one run per area removes the risk of within-field mixing regardless of how similar the runs measure. Where the design calls for one continuous field larger than a single run’s available quantity, the buyer faces a different situation: either runs must be confirmed similar enough for that specific field through a controlled physical comparison, or the field itself needs to be reconsidered in relation to available run quantities.
Replacement stock adds a second layer to this same allocation question. Material set aside for future repairs or extensions needs to retain its run identity for as long as it might be used, because a repair made years after installation with material from an unidentified or different run reintroduces the same shade and dimensional risk the original allocation was meant to avoid. A buyer requesting run-level packing evidence at delivery should also confirm that any reserved stock carries forward the same identifiers, rather than being stored as generic surplus once the installation is complete. This is where the project information the buyer supplies — area layout, quantities per space, anticipated replacement needs — becomes part of what a supplier such as VITAGRES would need in order to match declared runs to specific areas during quotation or order review, rather than treating the order as a single undifferentiated quantity.
Release, Segregate, Reinspect or Hold by Affected Run
The decision a buyer ultimately has to make, once evidence has been requested and reviewed, is what to do with the shipment. That decision is not binary. Four distinct actions are available, and the correct one is tied to the specific run or pallet the evidence concerns, not to the shipment as a whole: release, where a run’s identity, packing, sample, and inspection evidence are all consistent and adequate; segregation, where a run’s evidence is incomplete or its identity conflicts with another run’s, and physical separation is needed before any further decision; reinspection, where an existing inspection record does not cover the run in question or its scope is ambiguous; and hold, where evidence for a specific run cannot yet be resolved and the material should not proceed into the project until it is.
The reasoning that connects these four actions to the earlier evidence-gathering steps is that each action responds to a gap or a confirmation at the run level, not at the order level. A buyer who finds that one run’s inspection record is missing has no basis for holding runs whose records are complete and consistent; equally, a buyer who finds one run’s shade sample does not match the approved reference has no basis for releasing that run simply because other runs in the same order passed review. Treating the order as a single unit at this stage — rejecting everything because one run failed, or accepting everything because most runs passed — discards the run-level distinctions the earlier steps were built to establish.
This is also the point where the limits of a general framework become explicit. What this article’s reasoning supports is the sequence: declare runs, gather identity and packing evidence, link that evidence to samples and inspection, allocate by area and replacement need, then decide run by run. What it cannot supply is the actual content of those records for a specific order — VITAGRES’s production responsibility for a given shipment, the number and definition of runs within it, the quantities and codes involved, the sample plan applied, the inspection results obtained, or who holds authority to release or hold the shipment. A buyer moving from this framework toward a live order — whether reviewing a product such as the Керамограніт VGL1172008 or preparing a wider supplier inquiry for a distributor or project order — still needs those specific answers from the supplier before any of the four actions can be applied with confidence to the material actually on the dock.
Поширені запитання
Q: We have one purchase order. Why request a separate evidence package for each production run?
A: One purchase order does not establish one homogeneous lot. Ask for the declared run list, each run’s quantities and product identifiers, and its pallet-to-carton mapping using the supplier’s code legend. This identifies the actual groups to be sampled, compared and considered for release within the same order.
Q: The supplier sent one inspection report for the combined order. How can we assess its run coverage?
A: Ask the supplier to connect the inspected samples, selection origins, applicable reference and results to the named runs. A report for an unnamed combined population does not show run-level coverage, and a sample from one run does not represent another. Keep the decision within the material identified by the inspection or test evidence.
Q: Several runs are planned for one continuous tile area. What should we resolve before shipment?
A: Resolve the area allocation and any required physical comparison before treating the combined stock as suitable for that field. Use the run-linked shade and caliber information to decide whether to allocate runs separately or conduct a controlled review of the proposed mix. Preserve the run identity of replacement stock so later retrieval stays connected to the area allocation.
Q: If one run has an unresolved inspection issue, must the whole order receive the same disposition?
A: Decide by the affected run or pallet where the evidence supports that separation. Use the identity mapping to distinguish the unresolved material from unrelated runs, then record release, segregation, reinspection or hold through the authorized shipment decision. This avoids accepting or rejecting other material solely because it shares the purchase order.