The difference between testing a type and testing a batch, and when each matters
Type testing checks whether a design, such as a jam jar, works in principle, while batch testing checks whether a particular production run, such as a run of enamel mugs, actually matches that design.
What question does each kind of testing answer?
Type testing answers a design question. For a glass jam jar, a type test might check whether the jar's shape, thickness, and lid seal work together when the jar is filled, heated, cooled, and opened repeatedly. If the type passes, the producer knows the design can work, at least for the sample tested under those conditions.
Batch testing answers a production question. A batch is a group of jars or mugs made together, from the same materials, by the same process, at about the same time. Batch testing checks whether that particular group matches the type that was tested, because materials, temperatures, and workmanship can vary from one run to the next, even when the design has not changed.
How does a single run fault show the difference?
Glaze crazing in enamel mugs shows why both kinds matter. Suppose a mug design passes a type test, but one production run develops fine cracks in its glaze, while earlier runs do not. The type test cannot explain that difference, because the design is the same; only batch testing, or batch inspection, can reveal that something in that run, such as glaze mix, firing temperature, or cooling, differed.
Sampling is therefore a key decision in batch testing. Testing every mug would be wasteful and destructive, while testing none would leave the run unchecked. The producer should decide in advance how many mugs from each run will be checked, how they will be selected, and what result will lead to holding, reworking, or rejecting the run.
Why can't a type result excuse a faulty batch?
Illustration: a producer makes 60 batches of mugs over a year and imagines that 20 of them, in round illustration terms, show some glaze variation, while the rest look consistent. Those figures, as presented in The difference between testing a type and testing a batch, and when each matters, are invented, not measured. They illustrate why batch records matter: without a record linking each batch to its materials, firing, and test results, the producer cannot tell whether variation is random, seasonal, or tied to a particular glaze supplier.
The illustration also shows why a type test result should not be used to excuse a faulty batch. The type may be sound, but the batch in question may not match the type, and only batch evidence can settle that question for the mugs actually being sold.
How do you decide how much batch testing is needed?
Deciding between type and batch testing depends on variation. If production is stable, materials are consistent, and previous batches have matched the type closely, batch checking may be lighter, focused on key features. If production varies, suppliers change, or faults appear in single runs, batch checking should be heavier, with more samples and clearer hold criteria.
- Define the type, including design, materials, and process, before testing it.
- Define each batch, including materials, process, and production time.
- Decide batch sample size, selection method, and hold criteria in advance.
- Record batch results beside the type result, so differences are visible.
What happens when one kind replaces the other?
A common error is to test a type once and then treat every batch as proven for years, even as suppliers, glazes, and firing conditions change. That error turns a useful type result into a blanket excuse, and it hides batch faults until customers report them.
The opposite error is to batch test exhaustively while never testing the type properly. A producer who checks every batch for a surface fault, but never checks whether the jar design itself seals safely, may ship many batches that share the same design flaw, each batch passing its narrow check while the design fails in use.
How do you write a combined testing plan?
Close by writing a testing plan that names both kinds: the type test, with its date and scope, and the batch plan, with its sampling and hold criteria. That plan should be filed with production records, so a later reviewer can see which evidence supports the design and which supports the batch being sold.
Revisit the plan when a supplier changes, when a batch fault appears, or when production scales up. Scaling up often introduces variation, and a batch plan that worked for small runs may need strengthening for larger ones.
Sources and evidence on the record
- CEN and CENELEC, CEN and CENELEC - European standards including harmonised standards.
- Regulation (EU) 2023/988 (GPSR), EUR-Lex - the general product safety regulation, applicable from 13 December 2024.
Evidence basis: Official sources below frame this guide; the jar and mug examples are general educational material, not findings about any real production run. Applies when: This guide applies when a producer scaling up a kitchen range needs to decide whether to test a product type once, test each batch, or do both, using jam jars and enamel mugs as examples.